SAP ABAP Message Class /LIME/UTIL (Message Class for Package /LIME/UTIL)
Basic Data
Hierarchy
☛
SAP_AP (Software Component) SAP Application Platform
⤷
AP-LIM (Application Component) AP-LIM Logistics Inventory Management Engine
⤷
/LIME/PLT_UTIL (Package) Utilities
⤷
⤷
Attributes
| Message class | /LIME/UTIL | |
| Short Description | Message Class for Package /LIME/UTIL | |
| Changed On | 20050219 | |
| Last Changed At | 204947 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Field name &1 already exists in dependent structures | Space: object requires documentation | ||
| 2 | Data element &1 does not exist or is not active | Space: object requires documentation | ||
| 3 | Field name can have a maximum of &1 characters | Space: object requires documentation | ||
| 4 | Include &1 has an entry &2 | Space: object requires documentation | ||
| 5 | Index number must have &1 characters | Space: object requires documentation | ||
| 6 | Do not use blank or special characters | Space: object requires documentation | ||
| 7 | Enter the index for the index table | Space: object requires documentation | ||
| 8 | Select fields for the new index table | Space: object requires documentation | ||
| 9 | Index number &1 is reserved. Select a different one | Space: object requires documentation | ||
| 10 | Index table &1 already exists | Space: object requires documentation | ||
| 11 | Index and shadow tables were generated successfully | Space: object requires documentation | ||
| 12 | Structure &1 was modified successfully | Space: object requires documentation | ||
| 13 | Field name and/or data element name is missing | Space: object requires documentation | ||
| 14 | Field &1 is still used in tables, cannot be deleted | Space: object requires documentation | ||
| 15 | Maintain field names in customer namespace | Space: object requires documentation | ||
| 16 | You do not have authorization for this function | Space: object requires documentation | ||
| 17 | No authorization for object &1 | The short text describes the object sufficiently | ||
| 18 | Field &1 cannot be deleted | Space: object requires documentation | ||
| 19 | Function group was regenerated. Restart | Space: object requires documentation | ||
| 20 | Function group could not be generated | Space: object requires documentation | ||
| 21 | Structure &1 was activated with warnings | Space: object requires documentation | ||
| 22 | Structure &1 could not be activated | Space: object requires documentation | ||
| 23 | Select a line | Space: object requires documentation | ||
| 24 | Field name is from include structure &1 | Space: object requires documentation | ||
| 25 | Table type &1 could not be created | Space: object requires documentation | ||
| 26 | & & & & | The short text describes the object sufficiently | ||
| 27 | Table type &1 could not be activated | Space: object requires documentation | ||
| 28 | Structure &1 could not be generated | Space: object requires documentation | ||
| 29 | Field name is reserved for customer systems | Space: object requires documentation | ||
| 30 | Function not possible for selected lines | Space: object requires documentation | ||
| 31 | Include &1 cannot be deleted | Space: object requires documentation | ||
| 32 | Table type &1 is generated | Space: object requires documentation | ||
| 33 | Structure &1 is enhanced with new fields | Space: object requires documentation | ||
| 34 | Structure &1 is generated | Space: object requires documentation | ||
| 35 | Table &1 is generated | Space: object requires documentation | ||
| 36 | Structure &1 is adjusted and partly activated. Conversion necessary | Space: object requires documentation | ||
| 37 | Maintain index in customer namespace | Space: object requires documentation | ||
| 38 | Index must start with numbers | Space: object requires documentation | ||
| 39 | Structure &1 already exists | Space: object requires documentation | ||
| 40 | Table &1 was deleted | Space: object requires documentation | ||
| 41 | Index must start with a letter (excluding Z,X,Y). | Space: object requires documentation | ||
| 42 | LIME source code successfully generated | Space: object requires documentation | ||
| 43 | Enter the minimum age of the documents (in days) | Space: object requires documentation | ||
| 44 | Enter the end date of the archiving | Space: object requires documentation | ||
| 45 | &1 error found | Space: object requires documentation | ||
| 46 | Table &1 could not be activated | Space: object requires documentation | ||
| 47 | &1: &2 data records were processed (buffered: &3, &4) | Space: object requires documentation | ||
| 48 | &1 header data records read from archive file | Space: object requires documentation | ||
| 49 | Field name enhanced with prefix ZZ | Space: object requires documentation | ||
| 50 | Enter the document year for archiving | The short text describes the object sufficiently | ||
| 51 | Table &1 is not intended for archiving | Space: object requires documentation | ||
| 52 | &1: &2 of &3 data objects postprocessed | The short text describes the object sufficiently | ||
| 53 | Characters &1 are reserved for customer namespace | Space: object requires documentation | ||
| 54 | An index table with the same fields already exists | The short text describes the object sufficiently | ||
| 55 | Error in archiving class &1 | Space: object requires documentation | ||
| 56 | Class &2 is not registered for handle &1 | The short text describes the object sufficiently | ||
| 57 | Handle & is not intended for read access | The short text describes the object sufficiently | ||
| 58 | Archive handle & is not intended for write access | The short text describes the object sufficiently | ||
| 59 | Archive handle 0 is not intended for write access | The short text describes the object sufficiently | ||
| 60 | Internal error in function modules for archiving | Space: object requires documentation | ||
| 61 | No index can be structured for this archiving object | Space: object requires documentation | ||
| 62 | Archived table &1 does not match database table | Space: object requires documentation | ||
| 63 | Index was structured | Space: object requires documentation | ||
| 64 | No archive data found | Space: object requires documentation | ||
| 65 | Action canceled | Space: object requires documentation | ||
| 66 | Number of deleted entries: &1 | Space: object requires documentation | ||
| 67 | Missing entry in shadow table: '&2' (GUID: '&1') | Space: object requires documentation | ||
| 68 | Object (type &1, IDX &2, GUID &3) exists only as parent in tree (node &4) | Space: object requires documentation | ||
| 69 | Object (type &1, IDX &2, GUID &3) has incomplete path in tree (node &4) | Space: object requires documentation | ||
| 70 | Inconsistency cannot be corrected | Space: object requires documentation | ||
| 71 | Error while removing inconsistency | Space: object requires documentation | ||
| 72 | Incomplete information, inconsistency cannot be removed | The short text describes the object sufficiently | ||
| 73 | Missing entry in index table: '&2' (GUID: '&1') | The short text describes the object sufficiently | ||
| 74 | GUID Node '&1' exists in /LIME/QUAN but not in /LIME/TREE | The short text describes the object sufficiently | ||
| 75 | Entry in index table '&2' (GUID: '&1') without use in /LIME/TREE | Space: object requires documentation | ||
| 76 | &1: &2 relations, &3 inconsistencies | Space: object requires documentation | ||
| 77 | Obsolete TREE entry (GUID: '&1' Level: '&2') | The short text describes the object sufficiently | ||
| 78 | Several nodes (node '&1', node '&2') for object (type: '&3', GUID '&4') | The short text describes the object sufficiently | ||
| 79 | Different objects (&1, &2) with same GUID in nodes (&3, &4) | The short text describes the object sufficiently | ||
| 80 | Log_Quan entry (&1, &2) without log_tree entry with time stamp < &3 | The short text describes the object sufficiently | ||
| 81 | &1: wait &2 seconds | The short text describes the object sufficiently | ||
| 82 | /Lime/Quan entry (stock: &1, parent &2) without /lime/tree entry | Space: object requires documentation | ||
| 83 | Objects exist but their index tables ('&1') are missing | The short text describes the object sufficiently | ||
| 84 | Objects exist but their shadow tables ('&1') are missing | The short text describes the object sufficiently | ||
| 85 | /Lime/Quan entry (&1/&2, &3) with different /lime/tree entry | The short text describes the object sufficiently | ||
| 86 | Inconsistent /LIME/NTREE entry for GUID: "&1" | The short text describes the object sufficiently | ||
| 87 | Inconsistent /LIME/NQUAN and /LIME/NTREE entries for GUID_STOCK: '"&1" | The short text describes the object sufficiently | ||
| 88 | Inconsistent /LIME/NSERIAL and /LIME/NQUAN entries for GUID_USID: "&1" | The short text describes the object sufficiently | ||
| 89 | Inconsistent entry in /LIME/NLOG_TREE and /LIME/NTREE for GUID: '&1' | The short text describes the object sufficiently | ||
| 90 | Wrong release (&1) for conversion; system expects 4.0 to 4.10 | Space: object requires documentation | ||
| 91 | Wrong release for conversion; SCM_BASIS does not exist. | Space: object requires documentation | ||
| 92 | Block cannot be inserted in /LIME/NTREE; see long text | Space: object requires documentation | ||
| 93 | Block cannot be inserted in /LIME/WIDTH_TEMP; see long text | Space: object requires documentation | ||
| 94 | Block cannot be inserted in /LIME/NLOG_TREE; see long text | Space: object requires documentation | ||
| 95 | Block cannot be inserted in /LIME/NQUAN; see long text | Space: object requires documentation | ||
| 96 | Block cannot be inserted in /LIME/NLOG_QUAN; see long text | Space: object requires documentation | ||
| 97 | Block cannot be inserted in /LIME/NSERIAL; see long text | Space: object requires documentation | ||
| 98 | Block cannot be inserted in /LIME/NLOG_SER; see long text | Space: object requires documentation | ||
| 99 | Incorrect data from analyze; no entry found for GUId &1 | Space: object requires documentation | ||
| 100 | Error in convert_tree; child &1 does not fit under parent &2 | Space: object requires documentation | ||
| 101 | SUB entry without corresponding ADD entry in LOG_TREE, GUID &1 | Space: object requires documentation | ||
| 102 | No parent found in /LIME/LOG_TREE for data record with GUID &1 | Space: object requires documentation | ||
| 103 | Multiple entries found in convert_tree: GUID &1 | Space: object requires documentation | ||
| 104 | Error in convert_logtree; no parent found for node with GUID &1 | Space: object requires documentation | ||
| 105 | Error in convert_logtree; entry GUID &1 cannot be inserted | Space: object requires documentation | ||
| 106 | Error in convert_tree; hiererchy level cannot be determined for GUID &1 | Space: object requires documentation | ||
| 107 | Incorrect entry; function module called with step &1 | The short text describes the object sufficiently | ||
| 108 | Tables for new LIME hierarchy do not exist; check tables | Space: object requires documentation | ||
| 109 | Error occurred at XPRA | Space: object requires documentation | ||
| 110 | Error in convert_logtree; /LIME/NTREE cannot be read | Space: object requires documentation | ||
| 111 | XPRA may/cannot be executed; upgrade not active | Space: object requires documentation | ||
| 112 | You cannot insert data in /LIME/CUST_WIDTH; see longtext | Space: object requires documentation | ||
| 113 | Access of function module /LIME/CONV_410_TO_LIME_100 is not permitted | Space: object requires documentation | ||
| 114 | Conversion is not possible; component SCM_BASIS exists more than once | Space: object requires documentation | ||
| 115 | Conversion of &1 successful in client &1 | The short text describes the object sufficiently | ||
| 116 | Data analysis successful in client &1 | The short text describes the object sufficiently | ||
| 117 | Data conversion successful in client &1 | The short text describes the object sufficiently | ||
| 118 | LIME source code successfully generated | The short text describes the object sufficiently | ||
| 119 | Data element &1 could not be assigned to any namespace | The short text describes the object sufficiently | ||
| 120 | Database error when updating &1 | The short text describes the object sufficiently | ||
| 121 | Syntax error in include &1, row &2, error text: &3 | The short text describes the object sufficiently | ||
| 122 | Shadow table &1 does not exist | The short text describes the object sufficiently | ||
| 123 | Structure &1 does not exist in DDIC | The short text describes the object sufficiently | ||
| 124 | Field &1 does not exist in structure &2 | The short text describes the object sufficiently | ||
| 125 | Index table &1 is ignored due to DDIC inconsistencies | The short text describes the object sufficiently | ||
| 126 | Index table &1 is used during generation | The short text describes the object sufficiently | ||
| 127 | 'INSERT REPORT &1' failed | The short text describes the object sufficiently | ||
| 128 | Function module &1 does not exist | The short text describes the object sufficiently |
History
| Last changed on/by | 20050219 | SAP | |
| SAP Release Created in | 401 |