on 09-09-2015 2:51 PM
Hi C4C Experts,
We're encountering below error during master data replication from ERP using PI. We are simply using the standard mappings from ESR content.
<ERROR_TEXT>Exception: Error in message header mapping; agent class is CL_BUPA_ERP_REPL_IPA</ERROR_TEXT>
The weird thing is that our Employee replication is working perfectly fine but the rest of the master data (debmas, matmas, etc.) are failing due to this error in C4C.
Saw some relevant contents here in SCN but nothing really solves our issue.
Appreciate any helpful insights regarding this matter.
Thank you in advance.
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi João, I think we have different cause of error. Yours looks like a master data issue regarding base quantity as well as ID mapping for Product Category. In our case, the Receiver Partner Number (RCVPRN) in ECC that is mapped to the RecipientParty.InternalID field in the C4C structure was different from the tenant ID in C4C. It must be exactly the same.
Hi Mark,
We have the same problem, we can't find missing configuration in ERP. You can give us some details? We tried with next transactions: SBGRFCCONF, DRFIMG, and all looks fine but XML not brings SENDER PARTY and RECIPIENT PARTY. In SRT_UTIL we can see that:
On HCI we made changes in mapping and with constants fill this fields: (We use this scenario, because our ERP is S/4HANA on-Premise)
Mapping Recipient party and Sender Party.
And all works fine:
But we need to fix configuration in ERP and return to original and standar integration. We think, your solution is all we need, Please help us with details, thank you.
Best regards,
Carlos Andres.
Hello Mark,
If you see the Payload in C4C, you might see the inconsistency in the Sender and Receiver Partner. Sender must have ERP logical port which is defined in your Communication System while Receiver must have your short Tenant ID.
Looking at the error, it looks this is not happening in your case. Kindly confirm.
Regards,
Chandan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mark,
For C4C inbound, ping test from PI must be successful. Kindly check what is wrong in the configuration on PI.
Per my experience, such errors occurs due to some inconsistency in the Header data coming up payload in C4C. Can you also please compare the Payload for the non working scenario with your working Employee replication Payload?
Try to see if there is any thing different/unexpected in the Header of the Payload.
Regards,
Chandan
User | Count |
---|---|
7 | |
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.