error message "customer already exists" in S4 when updating prospect in C4C

[mloeckx]

Hey,

We have the scenario where we successfully replicate a prospect from C4C to S4. When changes are done in S4 to this prospect these are also successfully transferred to C4C.

When we update the prospect in C4C and save, we the prospect in S4 should be updated. However we get the message in the web service monitor in S4 --> customer XXXX already exists. We can't see anything wrong in the payload and use action code 04 in CPI.

Can you help us why the update is not happening?

[banderson · Accepted solution]

Dear Customers,

In this instance , I have checked the specifc case of the customer, the incident he created and the feedback he received from the Integration team. This was as follows;

We checked this issue from our own side and found the following as a cauesation.

We have understood that you have updated the action code in CPI.

Kindly unmap actionCode in CPI as create/update handling happens in S4 itself, and hence no additional handling required in CPI standad iflow.

If you have any further input Maarten please share.

Otherwise, its great to see the issue has been resolved.
Could you please mark this question as answered.

Kind regards,

Brad

[banderson]

Hi Maarten,

I would like you to create an incident for this issue , so we can check exactly what is going on here.
Please create this from the launchpad and assign to Component LOD-CRM-INT-S4H
Some useful information you could include when creating this would be as follows;
-Confirm your C4C tenant URL
-Provide the IDs for the Outgoing messages in C4C and the Incoming message in S4 Hana
-Steps to reproduce
-If its an issue effective on your productive tenant (check to see if this is also prevalent on your test, and if so we can use the test system to check this behaviour)
Follow me on the community page , and drop me a direct message when you have created the incident so I can keep an eye on this.
When we get to the bottom of this then , we can update this post to help others you may have issue with this in the future.
Many thanks,

Brad

[mloeckx]

The problem was indeed that an action code had been mapped. Once it was removed, we were able to update the customer.