Opportunity replication from C4C to ECC – confirmation from ECC to C4C issue – Duplicate Opportunity

[Former Member]

We use Opportunity functionality in C4C. And, in our ECC on prem system, we use the Inquiry document type, for Opportunity transactions in ECC.

We have bi-directional replication of Opportunities between C4C and our ECC on prem system (again, Inquiry document type in ECC). We use SAP Cloud Platform Integration (CPI, formerly known as HCI) for replication between C4C and ECC

We are currently facing an issue, where an Opportunity is created in C4C, and replicated to ECC, and a duplicate opportunity is created in ECC in some cases.

Here is the issue:

1. An opportunity is created in C4C

2. The iDoc is transferred successfully to ECC

3. The opportunity (inquiry) is created on ECC

4. Outbound confirmation Idoc sometimes not getting created because of issues like connectivity etc.

5. So the confirmation does not come back to C4C because of above reasons.

6. When a change is subsequently made to the opportunity in C4C, the iDoc again is transferred to ECC

7. A *new* opportunity (inquiry) is created on ECC. That opportunity is a duplicate.

Previously, we had integration between C4C and CRM on prem, for bi-directional replication of opportunities between C4C and CRM on prem. (We have since decommissioned CRM, and replaced the CRM opportunities with ECC Inquiries.)

When we had the replication between C4C and CRM, we did not face this same scenario, where duplicate opportunities were being created.

We have two questions:

1. What may be the difference in the integration between C4C and CRM, and C4C and ECC? (For example, possibly the CRM One Order framework is handling the replication differently than ECC is handling it?)

2. Is there a solution to this issue with the replication between C4C and ECC, so that duplicate opportunities (inquiries) are not created in ECC? More specifically, can ECC or C4C detect an update vs new opportunity ?

[ShivanandBH]

Dear Siva,

In standard C4C integration with SAP ERP, we have Opportunity follow-up scenario. C4C doesn't actually support Opportunity replication to SAP ERP, this is supported with SAP CRM though.

Opportunity follow-up scenario works in such a way that, simple edit and save of the opportunity do not trigger outbound replication. A specific action to trigger ERP Sales Quote/Order is required for outbound replication. And these actions are not enabled in C4C Opportunity until the confirmation is received from ERP.

Is there some sort of customization done at your end to support "Opportunity Replication"?, if so then kindly provide us information on exact interfaces being used in this whole scenario.

Regards,

Shivanand B H

[Former Member]

Hi Shivanand,

Sorry for the delay. Please find the information about implementation in HCI/CPI between C4C and ECC below:

i) From C4C to ECC, we have ns3:OpportunityReplicationBulkRequest as source element and mapped to INQUIRY_CREATEFROMDATA203 Target element.

ii) From ECC to C4C, we have COD_REPLICATE_SALES_ORDER01 as source element and mapped to ns3:OpportunityReplicationConfirmation target element.

Let me know if you need any more information regarding this.

[ShivanandBH]

Dear Siva,

Based upon your inputs on how you have achieved the Opportunity replication, kindly go through below notes,

The best possible ideal solution would be to resolve all of your connectivity issues, so that confirmation messages are processed fine.

1. What may be the difference in the integration between C4C and CRM, and C4C and ECC? (For example, possibly the CRM One Order framework is handling the replication differently than ECC is handling it?)

It seems that in CRM whenever the C4C documents are replicated, it maintains the C4C document ID and considered as external id, so next update message would be recognized that its for an existing document. Though here I would suggest you to investigate a bit more with ERP/CRM experts.

2. Is there a solution to this issue with the replication between C4C and ECC, so that duplicate opportunities (inquiries) are not created in ECC? More specifically, can ECC or C4C detect an update vs new opportunity ?

One possible way to restrict users from editing such Opportunities in C4C until the confirmation is processed in C4C with PDI Solution, logic here would be to check whether the external id is filled or not AND whether external replication is triggered, if the replication is triggered but external id isnt filled then make the document read-only for users.

I hope this helps.

Regards,

Shivanand B H