2999512 - Error "Object Identifier type 888 still exists for ID value" or "Object identifier type 927 still exists for ID val" is raised during Business Partner replication

•  Error "Object identifier type 888 still exists for ID val" message 006(BS_SOA_COMMON) raised during Business Partner replication
•  Error "Object Identifier type 927 still exists for ID value xxxx"

SAP S/4HANA Cloud

1. Replicate a Business Partner using the Business Partner Webservice
2. The system will raise the error "Object identifier type 888 still exists for ID val"  message number 006(BS_SOA_COMMON) or "Object Identifier type 927 still exists for ID value xxxx"

• Issue in the Key Mapping
• This issue can also be caused if the internalIDs in the payload contain the leading zeros e.g. 0000010001 is sent instead of 10001. As per the Help Portal Documentation "The internal ID shall be provided without leading zeros."
• Issue can occur when a Customer Contact is removed from the source system but is not processed in the target system, thereafter when a new customer contact is added & processed on the target system the error is produced
• Issue is also caused when the partner does not have a customer role in the target system

*Ensure that the internalID(s) in the payload do not contain the leading zeros

Steps for Removing Key Mapping

1. Open the "Manage Key Mapping" App 
2. Check the mapping maintained for the Business Partner
3. Check that the Business Partner in fact exists
4. If the BP does not exist amend the incorrect mapping

Blog Troubleshooting Business Partner Key Mapping Issues

Help Portal Documentation

Business Partner, 006(BS_SOA_COMMON), 006, BS_SOA_COMMON, "Object identifier type 888 still exists for ID val", internalID, Leading Zeros, The internal ID shall be provided without leading zeros, S4_PC, S4_1C, X4BC, S4HC, S/4HC, customer, 927, 8888 , KBA , LO-MD-BP , Business Partners , Problem

SAP S/4HANA Cloud Public Edition all versions ; SAP S/4HANA Cloud all versions