SAP ABAP Message Class S_ILM_SWISS_KNIFE (SN Object Extension Tool AKA "Swiss Knife")
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-ILM-CDE (Application Component) Context Data Extractor
⤷
S_ILM_SN_OBJECT_EXTENSION (Package) SN Meta and File Extension Tool (AKA "Swiss Knife")
⤷
⤷
Attributes
| Message class | S_ILM_SWISS_KNIFE | |
| Short Description | SN Object Extension Tool AKA "Swiss Knife" | |
| Changed On | 20110908 | |
| Last Changed At | 153500 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Table or structure &1 does not exist in DDIC | The short text describes the object sufficiently | ||
| 2 | Error during DDIC activation of table/structure &1 | The short text describes the object sufficiently | ||
| 3 | Cannot find administration data for object &1, client &2, and system &3 | The short text describes the object sufficiently | ||
| 4 | Table name &1 in metadata file does not match table name entered in UI | The short text describes the object sufficiently | ||
| 5 | An error occurred during the transformation of metadata: &1 | The short text describes the object sufficiently | ||
| 6 | Table name &1 in data file does not match table name entered on the UI | The short text describes the object sufficiently | ||
| 7 | Specify system ID, client, archiving object, and table name(s) | The short text describes the object sufficiently | ||
| 8 | Table &1 already exists in DDIC; metadata upload is not possible | The short text describes the object sufficiently | ||
| 9 | TXI preference cannot be taken into account during metadata upload | The short text describes the object sufficiently | ||
| 10 | Data and metadata uploads are permitted only for objects with SN_ prefix | The short text describes the object sufficiently | ||
| 11 | Table &1 is already registered in SN_META for archiving object &2 | The short text describes the object sufficiently | ||
| 12 | Start creation of a new archiving file | The short text describes the object sufficiently | ||
| 13 | Table &1, segment &2 was added to archiving file | The short text describes the object sufficiently | ||
| 14 | Talbe &1, segment &2 from file &3 was added to archiving file | The short text describes the object sufficiently | ||
| 15 | New archiving file with session number &1 was created successfully | The short text describes the object sufficiently | ||
| 16 | Current SN_META contains metadata of the specified table(s) | The short text describes the object sufficiently | ||
| 17 | Specify (.txt) file or directory but not both | The short text describes the object sufficiently | ||
| 18 | Missing authorization for object S_ARCHIVE | The short text describes the object sufficiently | ||
| 19 | File &1 cannot be opened | The short text describes the object sufficiently | ||
| 20 | File &1 cannot be read | The short text describes the object sufficiently | ||
| 21 | Missing read authorization for file &1 | The short text describes the object sufficiently | ||
| 22 | Archiving object &1 does not exist (AOBJ) | The short text describes the object sufficiently | ||
| 23 | System ID (legacy system) must be at least 3 characters long | The short text describes the object sufficiently | ||
| 24 | Client (legacy system) must be at least 3 digits long (nnn) | The short text describes the object sufficiently | ||
| 25 | Local file paths are not permitted in background processing | The short text describes the object sufficiently | ||
| 26 | TXI structure must exist in DDIC for "TXI structure" option: &1 | The short text describes the object sufficiently | ||
| 27 | Archiving object &1 is not "ILM-enabled": Entry in IRM_CUST, ... | The short text describes the object sufficiently |
History
| Last changed on/by | 20110908 | SAP | |
| SAP Release Created in | 703 |