SAP ABAP Message Class AREN_MIGRATION_TOOL (Archiving engine migration tool message class)
Basic Data
Hierarchy
☛
SAP_ABA (Software Component) Cross-Application Component
⤷
CA-FS-ARE (Application Component) Archiving Engine
⤷
ARFA_ARCHIVING_MIGRATION (Package) Migration Tool for Archiving Engine
SAP_ABA (Software Component) Cross-Application Component⤷
CA-FS-ARE (Application Component) Archiving Engine⤷
ARFA_ARCHIVING_MIGRATION (Package) Migration Tool for Archiving Engine 
Attributes
| Message class |  |
AREN_MIGRATION_TOOL |
| Short Description |  |
Archiving engine migration tool message class |
| Changed On |  |
20130531 |
| Last Changed At |  |
092249 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  001 |
Error while opening archiving file | The short text describes the object sufficiently | |
| 2 | 002 |
Archiving object &1 does not exist | The short text describes the object sufficiently | |
| 3 | 003 |
Only active archiving objects can be migrated | The short text describes the object sufficiently | |
| 4 | 004 |
Number of selection fields must be more than 0 | The short text describes the object sufficiently | |
| 5 | 005 |
Maximum number of selection fields must be less than 20 | The short text describes the object sufficiently | |
| 6 | 006 |
Transport request &1 is not modifiable | The short text describes the object sufficiently | |
| 7 | 007 |
Transport request &1 does not contain any modifiable tasks for user &2 | The short text describes the object sufficiently | |
| 8 | 008 |
Namespace &1 does not exist | The short text describes the object sufficiently | |
| 9 | 009 |
Only archiving scenario can be migrated | The short text describes the object sufficiently | |
| 10 | 010 |
User &1 is not authorized to create program | The short text describes the object sufficiently | |
| 11 | 011 |
User &1 is not authorized to change archiving object &2 | The short text describes the object sufficiently | |
| 12 | 012 |
Include program &1 already exists | The short text describes the object sufficiently | |
| 13 | 013 |
Object &1 of type &2 generated successfully and included in request &3 | The short text describes the object sufficiently | |
| 14 | 014 |
Unable to generate object &1 due to error in building code | The short text describes the object sufficiently | |
| 15 | 015 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 16 | 016 |
Header selection include &1 generated | The short text describes the object sufficiently | |
| 17 | 017 |
AOBJ entry updated for object and included in request &1 | The short text describes the object sufficiently | |
| 18 | 018 |
Basic IRM customization is maintained and included in request &1 | The short text describes the object sufficiently | |
| 19 | 019 |
Application log maintained for archiving object &1 migration | The short text describes the object sufficiently | |
| 20 | 020 |
Object &1 creation/modification failed | The short text describes the object sufficiently | |
| 21 | 021 |
Report &1 generated successfully and included in transport request &1 | The short text describes the object sufficiently | |
| 22 | 022 |
Report &1 already exists | The short text describes the object sufficiently | |
| 23 | 023 |
Unable to add entry for report &1 into TADIR | The short text describes the object sufficiently | |
| 24 | 024 |
Unable to delete entry for report &1 from TADIR | The short text describes the object sufficiently | |
| 25 | 025 |
Migration report started for object &1 | The short text describes the object sufficiently | |
| 26 | 026 |
&1 package not allowed | The short text describes the object sufficiently | |
| 27 | 027 |
Package &1 does not exist | The short text describes the object sufficiently | |
| 28 | 028 |
Migration report already successfully executed for this object | Space: object requires documentation | |
| 29 | 029 |
Program &1 already exists in a different package | The short text describes the object sufficiently | |
| 30 | 030 |
Inconsistency in the residence time definition | The short text describes the object sufficiently | |
| 31 | 031 |
Logging not possible | The short text describes the object sufficiently | |
| 32 | 032 |
Package &1 differs from the original archiving object package &2 | The short text describes the object sufficiently | |
| 33 | 033 |
Object generation failed. See the log for details | The short text describes the object sufficiently | |
| 34 | 034 |
IRM CUST entries not inserted. Maintain IRM CUST entries manually | The short text describes the object sufficiently | |
| 35 | 035 |
Generated report &1 contains syntax errors, &2 in the line &3 &4 | Space: object requires documentation | |
| 36 | 036 |
Selection text maintenance failed for object &1 | Space: object requires documentation | |
| 37 | 037 |
The namespace does not exist | The short text describes the object sufficiently | |
| 38 | 038 |
The naming is in the customer namespace | The short text describes the object sufficiently | |
| 39 | 039 |
The naming belongs to the STD namespace | The short text describes the object sufficiently | |
| 40 | 040 |
Wrong naming. Check your entry | The short text describes the object sufficiently | |
| 41 | 041 |
Object &1 of type &2 generated successfully | The short text describes the object sufficiently | |
| 42 | 042 |
Object &1 cannot be reloaded | The short text describes the object sufficiently | |
| 43 | 043 |
Input field scenario name is an obligatory parameter | The short text describes the object sufficiently | |
| 44 | 044 |
Input field package is an obligatory parameter | The short text describes the object sufficiently | |
| 45 | 045 |
Input field preprocessing application type is an obligatory parameter | The short text describes the object sufficiently | |
| 46 | 046 |
Input field write application type is an obligatory parameter | The short text describes the object sufficiently | |
| 47 | 047 |
The application type for write already exists | The short text describes the object sufficiently | |
| 48 | 048 |
The application type for preprocessing already exists | The short text describes the object sufficiently | |
| 49 | 049 |
Same application types for WRI and PRE. Enter different appl types | The short text describes the object sufficiently | |
| 50 | 050 |
User &1 is not authorized to create function group and function modules | The short text describes the object sufficiently | |
| 51 | 051 |
User &1 is not authorized to create structures | The short text describes the object sufficiently | |
| 52 | 052 |
Function group &1 creation failed | The short text describes the object sufficiently | |
| 53 | 053 |
Function module generation failed | The short text describes the object sufficiently | |
| 54 | 054 |
Generation of structure &1 failed | The short text describes the object sufficiently | |
| 55 | 055 |
Activation of structure &1 failed | The short text describes the object sufficiently | |
| 56 | 056 |
Original template structure &1 doesn't exist | The short text describes the object sufficiently | |
| 57 | 057 |
Function group &1 already exist. Kindly provide different namespace | The short text describes the object sufficiently | |
| 58 | 058 |
PPF application &1 already exists in the system. Provide different value | The short text describes the object sufficiently | |
| 59 | 059 |
An error occured during generation of FM's in PPF API for appl type &1 | The short text describes the object sufficiently | |
| 60 | 060 |
Problem occured during transport of PPF appl type &1: check TR &2 | The short text describes the object sufficiently | |
| 61 | 061 |
The build code of area &1 in &2 phase failed | The short text describes the object sufficiently | |
| 62 | 062 |
Reduce the namespace input to &1 characters | Space: object requires documentation |
History
| Last changed on/by | |
20130531 | SAP |
| SAP Release Created in | 732 |
