on 11-21-2018 9:01 AM
Hello all
We have a requirement to enable business partner replication bi-directional between C4C and ERP with the contact master data kept distinct.
From ERP to C4C we have achieved it by suppressing the mapping and setting the @contactPersonListCompleteTransmissionIndicator to false in the iflow.
We are now struggling to find a similar way out for the C4C to ERP scenario. Since the @contactPersonListCompleteTransmissionIndicator is only an indicator and not mapped to any field on the ERP side. And also because there doesn’t seem to be a field like that on the ERP side, we made a shot in the dark by simple removing the mapping for contact persons and un-deploying the BusinessPartnerContactAddressReplication from C4C to ERP. Result: change on account in C4C is saved, it does not carry any contact information into ERP, so far so good, but as a side effect all existing contacts in ERP are deleted.
Can you suggest anyway to handle this requirement: simply keep ERP and C4C Contact masater data mutually exclusive.
I have reviewed the KBA: https://launchpad.support.sap.com/#/notes/0002626072
and the blog ERP to C4C Integration Checklist for Customer Projects
both of which touch the ERP to C4C scenario but not the other way around.
Appreciate your inputs.
reddy.dedeepya manideepsatya shivanand.hangaragi sikandernarula123
Hi n.kumar.nandyappa
We decided to live with a one way replication from ERP. Also because it became a requirement from a governance perspective that customer master is maintained only in ERP at least most parts of it. And the additional sales related information maintained in C4C was not needed in ERP.
However, I remember investigating further about this and potentially using the MSGFN field on the contact node. We did not get it to work but if you can investigate the different possibilities with that, maybe there is a way out.
All the best.. Suraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.