temporary key is mapped to existing key

[Former Member]

Dear Experts,

We are using ECC integration with C4C, Numbering of customer master data for ECC and C4C are different, ECC number stored with external key in C4C, later we want to have same number range for customer in ECC and C4C, for this made changes in PI where KUNNER is mapped to internal id of C4C and in C4C defined number range for “General business Partner” as external, number range is same as ECC.

Now we getting error in C4C as “temporary key is mapped to existing key”

Tim Finn

In-Application Sequencing (inbound): Mapping of temporary keys to final keys failed [CL_BUPA_ERP_REPL_IPA]

Pay load

<ns0:BusinessPartnerERPBulkReplicateRequest xmlns:ns0="http://sap.com/xi/SAPGlobal20/Global">

<MessageHeader>

<ID>B91AABC6AA6211E68F61000006B6E7A6</ID>

<UUID>B91AABC6-AA62-11E6-8F61-000006B6E7A6</UUID>

<CreationDateTime>2016-11-14T13:06:07Z</CreationDateTime>

<SenderParty>

<InternalID schemeAgencyID="310" schemeID="LocalSystemID">SEVCLNT410</InternalID>

</SenderParty>

<RecipientParty>

<InternalID schemeAgencyID="310" schemeID="LocalSystemID">0M1UQED</InternalID>

</RecipientParty>

</MessageHeader>

<BusinessPartnerERPReplicateRequestMessage>

<MessageHeader>

<ID>0000000031419122</ID>

</MessageHeader>

<BusinessPartner actionCode="04" contactPersonListCompleteTransmissionIndicator="true" roleListCompleteTransmissionIndicator="true" salesArrangementListCompleteTransmissionIndicator="false">

<ReceiverInternalID>0001100132</ReceiverInternalID>

<SenderSequenceNumberValue>20161114130606</SenderSequenceNumberValue>

<CategoryCode>2</CategoryCode>

<LifeCycleStatusCode>2</LifeCycleStatusCode>

<FirstLineName>LSMW LOAD</FirstLineName>

<Role actionCode="04">

<RoleCode>Y002</RoleCode>

</Role>

</BusinessPartner>

</BusinessPartnerERPReplicateRequestMessage>

</ns0:BusinessPartnerERPBulkReplicateRequest>

[guilherme_steyer2]

Hello,

This blog explains how to achieve this requirement

https://blogs.sap.com/2015/04/10/sap-c4c-integration-achieving-bp-replication-with-account-id-equal-...

Regards,

Guilherme Steyer