Symptom
In the following table, you can see some of the most common error messages returned during the inbound processing when there are key mapping issues in the payload:
| Message text | Technical number |
| Object Identifier type 888 still exists for ID value | 006(BS_SOA_COMMON) |
| Object identifier type 927 still exists for ID value | 006(BS_SOA_COMMON) |
| External Address ID already used for Business Partner Guid & | 009(BP_DATAREPL_FND) |
| Address doesn't exist | 010(AM) |
| Business partner &1 already exists | 286(R1) |
| Address is still being used and may not be deleted | 455(R1) |
| BP role &1 does not exist for partner &2 | 657(R11) |
| Task insert is not supported for existing customer | 007(CVI_EI) |
| Task insert is not supported for existing vendor | 042(CVI_EI) |
Not always an error will be raised. Sometimes, wrong key mapping will just cause unexpected behaviors:
- Partner Functions not created or updated
- A Business Partner appears multiple times in the same payload
Read more...
Environment
- Sales and Distribution (SD)
- Logistics Execution (LE)
- SAP ERP Central Component
- SAP ERP
- SAP enhancement package for SAP ERP
- SAP enhancement package for SAP ERP, version for SAP HANA
- SAP S/4HANA
Product
SAP ERP Central Component all versions ; SAP ERP all versions ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions
Keywords
KBA , LO-MD-BP-WS , Web Service for Business Partner , CA-MDG-KM , Key Mapping , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview