Solution : https://service.sap.com/sap/support/notes/1052964 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues related to the syndication of Business Partner, Customer, or Vendor Master Data from SAP NetWeaver MDM to ERP systems using PI. Common problems include IDoc inbound errors and incorrect data sequencing. For a successful transfer, two IDocs must be maintained in a specific order; the ADRMAS (address data) should precede either CREMAS or DEBMAS (master data). Ensure mappings are configured to prevent data overwrites, with placeholders indicating absent data. Components like customizing values, object keys, and formatted numbers must be verified for accuracy. The note also highlights the importance of implementing the correct IDoc message functions and handling fields with no data singularly via the no-data sign ("/").
Key words :
message replaces previous messages 009 => original, ale inbound function modules treat, sap delivered standard xslt mappings, follwing debmas / cremas idoc correctly, wrong customer / vendor account number, delivered standard syndication maps, imported 018 => resend existing data, missing customer / vendor key, customer / vendor account number, missing message function code
Related Notes :
| 1412742 | MDM Customer Content Information (Release MDM 7.1+) |
| 1318478 | MDM Vendor Content Information (Release MDM 7.1+) |
| 1252884 | MDM Customer Content Information (Release 5.5) |
| 1252883 | MDM Vendor Content Information (Release 5.5) |
| 1035773 | MDM Business Partner Content Information |
| 384462 | Master data and addresses |