C4C- ERP Integration / Considerations for Initial Data Load
Initial Data Load
It is common that customer would want to create their own Extension fields in C4C UI.
Because C4C typically assign the C4C number and stores the mapping to ERP, it is recommended that all data is loaded via the
interface, and not via the C4C data migration workbench.
All Extension Fields that need to be exchanged between can be integrated using the middleware.
Those fields that will not result populated in integration can be populated later using the Mass maintenance tool.
If for some reason, the migration workbench is chosen for Initial data Load, then it is mandatory to maintain ID mapping for all Accounts.
When migrating accounts there can be a lot of dependencies between accounts, relationships to other business partners; that can prevent one account from being properly saved when sent from ERP to C4C.
Use Trx. BD12 to load all accounts, first without any
sales area data (which include relationships).
Filters are applied in transaction BD64.
This will create all the general data of the accounts, so that they can be referenced in a second load, to create the
Then take out any filters, and run BD12 to send all the accounts to C4C again.
Keep in mind that all idocs are processed individually and it takes certain time. So leverage the option of selecting a subset of accounts to be entered then in BD12. Don´t run BD12 without a selection of data, unless you truly want to replicate all (or a very high percentage of ) accounts existent in ECC.