You have an existing account hierarchy in C4C replicated from ECC. Now you wish to update this existing account hierarchy. You observed that IDoc and inbound webservice message are processed successfully. The outdated customer is not part of the webservice message. Therefore, you expect that this customer is not part of updated account hierarchy. But this account is listed in the account hierarchy in C4C.
SAP Cloud for Customer
The recommended process is as follows:
- The report RCOD_CUSTHIER_TIM_SLIC_SYDATUM should be scheduled daily. It will create change pointers for future time slice changes (incl. phasing out of a customer from an account hierarchy).
- The report RBDMIDOC should be scheduled daily. It creates the IDocs based on the change pointers.
The initial load report RCOD_CUSTHIER_EXTRACT extracts only the currently valid account hierarchy entries and won't delete entries. To overcome the situation you can run the report RCOD_CUSTHIER_TIME_SLICES. It will calculate all change pointers for the given reference date range. Afterwards the report RBDMIDOC must be executed as well.
account hierarchy, C4C, ECC, replicated successfully, outdated customer not part of webservice message, outdated customer still in account hierarchy, , KBA , LOD-CRM-INT-ERP , Integration of C4C with ERP , LOD-LE-BP-HIE , Business Partner Hierarchy , Problem