/LIME/UTIL - Nachrichtenklasse f�r Paket /LIME/UTIL
The following messages are stored in message class /LIME/UTIL: Nachrichtenklasse f�r Paket /LIME/UTIL.
It is part of development package /LIME/PLT_UTIL in software component AP-LIM. This development package consists of objects that can be grouped under "Utilities".
It is part of development package /LIME/PLT_UTIL in software component AP-LIM. This development package consists of objects that can be grouped under "Utilities".
Message Nr ▲ | Message Text |
---|---|
001 | Field name &1 already exists in dependent structures |
002 | Data element &1 does not exist or is not active |
003 | Field name can have a maximum of &1 characters |
004 | Include &1 has an entry &2 |
005 | Index number must have &1 characters |
006 | Do not use blank or special characters |
007 | Enter the index for the index table |
008 | Select fields for the new index table |
009 | Index number &1 is reserved. Select a different one |
010 | Index table &1 already exists |
011 | Index and shadow tables were generated successfully |
012 | Structure &1 was modified successfully |
013 | Field name and/or data element name is missing |
014 | Field &1 is still used in tables, cannot be deleted |
015 | Maintain field names in customer namespace |
016 | You do not have authorization for this function |
017 | No authorization for object &1 |
018 | Field &1 cannot be deleted |
019 | Function group was regenerated. Restart |
020 | Function group could not be generated |
021 | Structure &1 was activated with warnings |
022 | Structure &1 could not be activated |
023 | Select a line |
024 | Field name is from include structure &1 |
025 | Table type &1 could not be created |
026 | & & & & |
027 | Table type &1 could not be activated |
028 | Structure &1 could not be generated |
029 | Field name is reserved for customer systems |
030 | Function not possible for selected lines |
031 | Include &1 cannot be deleted |
032 | Table type &1 is generated |
033 | Structure &1 is enhanced with new fields |
034 | Structure &1 is generated |
035 | Table &1 is generated |
036 | Structure &1 is adjusted and partly activated. Conversion necessary |
037 | Maintain index in customer namespace |
038 | Index must start with numbers |
039 | Structure &1 already exists |
040 | Table &1 was deleted |
041 | Index must start with a letter (excluding Z,X,Y). |
042 | LIME source code successfully generated |
043 | Enter the minimum age of the documents (in days) |
044 | Enter the end date of the archiving |
045 | &1 error found |
046 | Table &1 could not be activated |
047 | &1 data records were processed |
048 | &1 header data records read from archive file |
049 | Field name enhanced with prefix ZZ |
050 | Enter the document year for archiving |
051 | Table &1 is not intended for archiving |
052 | &1: &2 of &3 data objects postprocessed |
053 | Characters &1 are reserved for customer namespace |
054 | An index table with the same fields already exists |
055 | Error when opening database cursor |
100 | Error in archiving class &1 |
101 | Class &2 is not registered for handle &1 |
102 | Handle & is not intended for read access |
103 | Archive handle & is not intended for write access |
104 | Archive handle 0 is not intended for write access |
105 | Internal error in function modules for archiving |
106 | No index can be structured for this archiving object |
107 | Archived table &1 does not match database table |
108 | Index was structured |
109 | No archive data found |
110 | Action canceled |
111 | Number of deleted entries: &1 |
201 | Missing entry in shadow table: '&2' (GUID: '&1') |
202 | Object (type &1, IDX &2, GUID &3) exists only as parent in tree (node &4) |
203 | Object (type &1, IDX &2, GUID &3) has incomplete path in tree (node &4) |
204 | Inconsistency cannot be corrected |
205 | Error while removing inconsistency |
206 | Incomplete information, inconsistency cannot be removed |
207 | Missing entry in index table: '&2' (GUID: '&1') |
208 | GUID Node '&1' exists in /LIME/QUAN but not in /LIME/TREE |
209 | Entry in index table '&2' (GUID: '&1') without use in /LIME/TREE |
210 | &1: &2 relations, &3 inconsistencies |
211 | Obsolete TREE entry (GUID: '&1' Level: '&2') |
212 | Several nodes (node '&1', node '&2') for object (type: '&3', GUID '&4') |
213 | Different objects (&1, &2) with same GUID in nodes (&3, &4) |
214 | Log_Quan entry (&1, &2) without log_tree entry with time stamp < &3 |
215 | &1: wait &2 seconds |
216 | /Lime/Quan entry (stock: &1, parent &2) without /lime/tree entry |
217 | Objects exist but their index tables ('&1') are missing |
218 | Objects exist but their shadow tables ('&1') are missing |
219 | /Lime/Quan entry (&1/&2, &3) with different /lime/tree entry |
220 | Inconsistent /LIME/NTREE entry for GUID: "&1" |
222 | Inconsistent /LIME/NQUAN and /LIME/NTREE entries for GUID_STOCK: '"&1" |
223 | Inconsistent /LIME/NSERIAL and /LIME/NQUAN entries for GUID_USID: "&1" |
224 | Inconsistent entry in /LIME/NLOG_TREE and /LIME/NTREE for GUID: '&1' |
300 | Wrong release (&1) for conversion; system expects 4.0 to 4.10 |
301 | Wrong release for conversion; SCM_BASIS does not exist. |
302 | Block cannot be inserted in /LIME/NTREE; see long text |
303 | Block cannot be inserted in /LIME/WIDTH_TEMP; see long text |
304 | Block cannot be inserted in /LIME/NLOG_TREE; see long text |
305 | Block cannot be inserted in /LIME/NQUAN; see long text |
306 | Block cannot be inserted in /LIME/NLOG_QUAN; see long text |
307 | Block cannot be inserted in /LIME/NSERIAL; see long text |
308 | Block cannot be inserted in /LIME/NLOG_SER; see long text |
310 | Incorrect data from analyze; no entry found for GUId &1 |
311 | Error in convert_tree; child &1 does not fit under parent &2 |
312 | SUB entry without corresponding ADD entry in LOG_TREE, GUID &1 |
313 | No parent found in /LIME/LOG_TREE for data record with GUID &1 |
314 | Multiple entries found in convert_tree: GUID &1 |
315 | Error in convert_logtree; no parent found for node with GUID &1 |
316 | Error in convert_logtree; entry GUID &1 cannot be inserted |
317 | Error in convert_tree; hiererchy level cannot be determined for GUID &1 |
318 | Incorrect entry; function module called with step &1 |
319 | Tables for new LIME hierarchy do not exist; check tables |
320 | Error occurred at XPRA |
321 | Error in convert_logtree; /LIME/NTREE cannot be read |
322 | XPRA may/cannot be executed; upgrade not active |
323 | You cannot insert data in /LIME/CUST_WIDTH; see longtext |
324 | Access of function module /LIME/CONV_410_TO_LIME_100 is not permitted |
325 | Conversion is not possible; component SCM_BASIS exists more than once |
330 | Conversion of &1 successful in client &2 |
331 | Data analysis successful in client &1 |
332 | Data conversion successful in client &1 |
400 | LIME source code successfully generated |
401 | Data element &1 could not be assigned to any namespace |
402 | Database error when updating &1 |
403 | Syntax error in include &1, row &2, error text: &3 |
404 | Shadow table &1 does not exist |
405 | Structure &1 does not exist in DDIC |
406 | Field &1 does not exist in structure &2 |
407 | Index table &1 is ignored due to DDIC inconsistencies |
408 | Index table &1 is used during generation |
409 | 'INSERT REPORT &1' failed |
500 | Function module &1 does not exist |