MDG_ID_MATCH_API_BS - Messages belonging to Key Mapping
The following messages are stored in message class MDG_ID_MATCH_API_BS: Messages belonging to Key Mapping.
It is part of development package MDG_BS_ID_MATCHING_API in software component CA-MDG-KM. This development package consists of objects that can be grouped under "MDG Key Mapping: API".
It is part of development package MDG_BS_ID_MATCHING_API in software component CA-MDG-KM. This development package consists of objects that can be grouped under "MDG Key Mapping: API".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 |
| 001 | At least one input parameter must be filled in method &1 |
| 002 | Key mapping does not support main context ID &1 |
| 003 | A fatal internal error occurred in the key mapping API (method &1) |
| 004 | Object types &1 and &2 belong to different main context IDs |
| 005 | Object type is missing |
| 006 | Key mapping does not support object type &1 |
| 007 | Object identifier type is missing |
| 008 | Object identifier type &1 does not exist |
| 009 | Business system ID is missing |
| 010 | Key mapping API could not be instantiated |
| 011 | Key mapping API could not determine local business system ID |
| 012 | Object identifier type &1 does not exist for object type &2 |
| 013 | Authorization for starting the reorganization program is missing |
| 014 | Object identifier types &1 and &2 belong to different object node types |
| 015 | No central registry defined for object type &1 |
| 016 | Object identifier type &1 still exists for ID value &3 |
| 017 | Object identifier type &1 passed multiple times |
| 018 | One business object contains different bus. sys. in its identifier data |
| 019 | Object types &1 and &2 belong to a different secondary mapping context |
| 020 | ID value is missing for object type &1/object ident. type &2/bus.sys. &3 |
| 021 | ID value &1 contains delimiter of key structure |
| 022 | RFC connection &1 failed |
| 023 | Program cannot be started in production systems |