Solution : https://service.sap.com/sap/support/notes/418886 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues in CRM/EBP systems where products replicated from an R/3 back-end are not recognized during subsequent downloads. Errors including "No corresponding product found" and "Change data on set & in the original system" occur primarily due to logical system discrepancies or product GUID mismatches. Solutions include maintaining consistent logical systems across downloads and avoiding direct copies for creating product data in CRM/EBP systems. Also, ensure CRM and R/3 systems match in logical system mappings and use downloads instead of manual copying for product data transfers to avoid inconsistencies and ensure system integrity.
Key words :
crm/ebp system successfully, production crm/ebp system, com_product502 client_copy_product reason, crm/ebp system, /3 back-end system, crm system landscape, prerequisites preliminary note, data inconsistency exists, logsys crm/ebp, -> logsys crm/ebp
Related Notes :
| 897804 | CRM Client Copy Additional information |
| 872533 | FAQ: Middleware |
| 757093 | FAQ: Analyzing CRM Client Copy problems |
| 575414 | No detailed message during initial download (ERP => CRM) |
| 431831 | Missing set types after client copy |
| 369684 | Hierarchy may only be changed in the original system |