SAP ABAP Message Class /AIN/IDMAPPING (/AIN/IDMAPPING)
Basic Data
Hierarchy
☛
AIN (Software Component) AIN 710: Add-On Installation
⤷ AIE-AII (Application Component) Infrastructure
⤷ /AIN/IDMAPPING (Package) Auto-ID ID Mapping
⤷ AIE-AII (Application Component) Infrastructure
⤷ /AIN/IDMAPPING (Package) Auto-ID ID Mapping
Attributes
Message class | /AIN/IDMAPPING | |
Short Description | ||
Changed On | 20141109 | |
Last Changed At | 140331 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Target ID type and version are not supplied | The short text describes the object sufficiently | |
2 | 002 | Source ID type and version not found | The short text describes the object sufficiently | |
3 | 003 | No ID mapping entry can be created for ID type &1, encoding type &2 | The short text describes the object sufficiently | |
4 | 004 | Error during database update. Contact your system administrator | The short text describes the object sufficiently | |
5 | 005 | Error during creating an instance for class &1 (ID type &2, enc.type &3) | The short text describes the object sufficiently | |
6 | 006 | Error during calling instance for class &1 (ID type &2, enc.type &3) | The short text describes the object sufficiently | |
7 | 007 | No value found for GUID &1 (ID type &2, enc.type &3) | The short text describes the object sufficiently | |
8 | 008 | Mapping table for ID type/enc.type &1 / &2 to &3 / &4 doesn't exist | The short text describes the object sufficiently | |
9 | 009 | Error during select in table &1. Contact your system administrator | The short text describes the object sufficiently | |
10 | 010 | Please provide RFC destination for plant and storage location retrieval | The short text describes the object sufficiently | |
11 | 011 | Technical error calling &1 in &2 | The short text describes the object sufficiently | |
12 | 012 | Error during activation of table &1 | Space: object requires documentation | |
13 | 013 | Regeneration cancelled by user | The short text describes the object sufficiently | |
14 | 014 | Entries already exists, no regeneration possible | The short text describes the object sufficiently | |
15 | 015 | Mapping table is delivered by SAP, no regeneration possible | The short text describes the object sufficiently | |
16 | 016 | DATA_ELEMENT attribute have not been defined | The short text describes the object sufficiently | |
17 | 017 | Error occured while modifying table /AIN/TID_TYPTABL | The short text describes the object sufficiently | |
18 | 018 | Source ID with ID type &1 and encoding type &2 could not be found | The short text describes the object sufficiently | |
19 | 019 | Mapping of ID with ID type &1 and encoding type &2 could not be found | The short text describes the object sufficiently | |
20 | 020 | Mapping of ID with ID type/enc.type &1/&2 to &3/&4 could not be found | The short text describes the object sufficiently | |
21 | 021 | Target ID of conversion from ID type/enc.type &1/&2 to &3/&4 not found | The short text describes the object sufficiently | |
22 | 022 | Error when creating database table &1 for ID mapping of encoding type &2 | The short text describes the object sufficiently | |
23 | 023 | Error &2 when writing database table &1 for ID mapping | The short text describes the object sufficiently | |
24 | 024 | Error when activating database table &1 for ID mapping | The short text describes the object sufficiently | |
25 | 025 | Error when writing index &2 of database table &1 for ID mapping | The short text describes the object sufficiently | |
26 | 026 | Error when activating index &2 of database table &1 for ID mapping | The short text describes the object sufficiently | |
27 | 027 | Target ID with ID type &1 and encoding type &2 could not be found | The short text describes the object sufficiently | |
28 | 028 | "&1" (&2) or "&3" (&4) already mapped, each ID can only be assigned once | The short text describes the object sufficiently | |
29 | 029 | Error creating mapping between "&1" (&2) or "&3" (&4) | The short text describes the object sufficiently | |
30 | 030 | Given element values are not unique, more than one target ID found | The short text describes the object sufficiently | |
31 | 031 | Could not delete ID with ID type &1 and encoding type &2: ID not found | The short text describes the object sufficiently | |
32 | 032 | Could not find database table for deletion of ID with ID type &1 enc. &2 | The short text describes the object sufficiently | |
33 | 033 | Unable to lock ID mapping, no database table for ID type &1 encoding &2 | The short text describes the object sufficiently | |
34 | 034 | Internal error in lock of ID mapping for ID type/encoding &1/&2 to &3/&4 | The short text describes the object sufficiently | |
35 | 035 | ID mapping locked for ID type/encoding &1/&2 to &3/&4 | The short text describes the object sufficiently | |
36 | 037 | No components / elements provided, impossible to retrieve encoding type | The short text describes the object sufficiently | |
37 | 038 | RFC error when calling &1: | The short text describes the object sufficiently | |
38 | 039 | Error when calling RFC destination &1: &2 | The short text describes the object sufficiently | |
39 | 040 | Mapping Table for ID type &1 and encoding type &2 does not exist | The short text describes the object sufficiently | |
40 | 041 | Attribute &1 for ID type &2 and encoding type &3 not defined | The short text describes the object sufficiently | |
41 | 042 | Unable to update attributes: &1 | The short text describes the object sufficiently | |
42 | 043 | Maintain the attribute value &1 and its description in customizing. | The short text describes the object sufficiently | |
43 | 044 | Location type &1 and ID &2 is already mapped to a different ID | The short text describes the object sufficiently | |
44 | 045 | Vocabulary attribute header &1 not found in customizing | The short text describes the object sufficiently | |
45 | 046 | No unique ID type could be determined for id &1&2. | The short text describes the object sufficiently | |
46 | 100 | *******************Data Filtering************************* | The short text describes the object sufficiently | |
47 | 101 | No business partner of type person could be determined for user &1. | The short text describes the object sufficiently | |
48 | 102 | More than one business partner of type person was determined for user &1. | The short text describes the object sufficiently | |
49 | 103 | No business partner of type organization could be determined for user &1 | The short text describes the object sufficiently | |
50 | 104 | No company prefix is maintained for business partner &1 | The short text describes the object sufficiently |
History
Last changed on/by | 20141109 | SAP | |
SAP Release Created in | 510 |