Do you have any question about this error?
Message type: E = Error
Message class: MDG_ID_MATCH_API_BS - Messages belonging to Key Mapping
Message number: 021
Message text: ID value &1 contains delimiter of key structure
The ID value &V1& for <DS:DE.MDG_IDS_TYPE_CODE_BS>object ID type</> &V2&
( <DS:DE.MDG_OBJECT_TYPE_CODE_BS>object type</> &V3&) contains a string
that is identical to the delimiter <DS:SIMG.MDG_IDM_007>assigned to the
key structure</> of object ID type &V2&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Key Mapping cannot be stored with the given ID value.
Do one of the following:
Change the ID Value
Adjust the delimiter for the key structure
This can only be done, if no key mapping for object type &V3& has been
created yet.
Error message extract from SAP system. Copyright SAP SE.
MDG_ID_MATCH_API_BS021
- ID value &1 contains delimiter of key structure ?The SAP error message
MDG_ID_MATCH_API_BS021
indicates that there is an issue with the ID value being processed in the Master Data Governance (MDG) system. Specifically, the error states that the ID value contains a delimiter that is part of the key structure, which is not allowed.Cause:
The error typically arises when the ID value being used in a transaction or API call contains characters that are defined as delimiters in the key structure of the relevant data model. In SAP MDG, certain characters (like slashes, commas, etc.) are reserved for separating different parts of a key, and their presence in an ID value can lead to confusion or misinterpretation of the data.
Solution:
To resolve this error, you can take the following steps:
Identify the ID Value: Check the ID value that is causing the error. This will usually be indicated in the error message as
&1
.Check for Delimiters: Review the ID value for any characters that are defined as delimiters in the key structure. Common delimiters include:
- Commas (
,
)- Slashes (
/
)- Semicolons (
;
)- Other special characters
Modify the ID Value: If you find any delimiters in the ID value, you will need to modify it to remove or replace those characters. Ensure that the new ID value adheres to the expected format and does not include any reserved characters.
Test the Changes: After modifying the ID value, re-attempt the operation that triggered the error to see if it resolves the issue.
Consult Documentation: If you are unsure about which characters are considered delimiters for your specific data model, refer to the SAP MDG documentation or the data model configuration in your system.
Check Configuration: If the issue persists, it may be worth checking the configuration of the data model in MDG to ensure that the key structure is correctly defined and that there are no inconsistencies.
Related Information:
By following these steps, you should be able to resolve the MDG_ID_MATCH_API_BS021
error and successfully process the ID value in your SAP MDG system.
Get instant SAP help. Start your 7-day free trial now.
MDG_ID_MATCH_API_BS020
ID value is missing for object type &1/object ident. type &2/bus.sys. &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MDG_ID_MATCH_API_BS019
Object types &1 and &2 belong to a different secondary mapping context
What causes this issue? <DS:DE.MDG_OBJECT_TYPE_CODE_BS>Business ObjectType</> &V1& must be mapped to business object type &V2...
MDG_ID_MATCH_API_BS022
RFC connection &1 failed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MDG_ID_MATCH_API_BS023
Program cannot be started in production systems
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.