SAP Knowledge Base Article - Public

3430901 - How to Perform Data Replication to C4C

Symptom

You are preparing your C4C and your data to receive a data load and wants to know the best practices for it.

Environment

SAP Cloud for Customer.

Cause

When doing a data load into C4C, we ask you to follow some practices in order to prepare the tenant and also prevent possible unexpected scenarios while monitoring the tenant during the process.

Resolution

Before you do the data load, please open a case with the below details:

  1. How much volume are you going to replicate?
  2. Which objects are they going to replicate? (ex: Accounts, products)
  3. is the replication going to be BRG or OData, ECC, A2X (Web Services) or Data Workbench?
  4. What time is the replication going to start and end (with the time zone)? 

Please take note on the following as well:

  1. Don’t use the same PDI user to trigger the replication.
  2. Don’t deploy PDI changes while doing the replication.
  3. Don`t do massive changes on the UI or adaptation changes while the replication is happening (this will slow down the replication).
  4. For every error the system will try 7 times before message cancelled automatically if you are replicating ECC. Make sure there are no data errors (as this slow down depending on the volume- eg: 500k errors= 3.5k attempts).
  5. Try to perform the replication in batches.
  6. Do the data sanity checks before replicating it to C4C.
  7. If you have any external system like CPI, S4 or external ERP, make sure it is checked on those systems as well so doesn`t get the calls on waiting status, which could also slow down the replication.
  8. When facing slowness, provide detailed examples (with the time frame period, affected User ID, etc) in the case so we can check this further.

Keywords

data load, replication, odata, load, erp, cpi, a2x, performance , KBA , LOD-CRM-PRF , Performance , How To

Product

SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions