Web Service Message - Error while processing inbound third party communication

[#1]

Hi all,

We have an SAP ERP / C4C web service integration. And I ´m having an error in Web Service Message monitoring that display this:

Message:    "Error while processing inbound third party communication"

Long Text:  "Exception: Error in message header mapping; agent class is CL"

Error context:

<ERROR_CONTEXT>

  <ERROR_INFO>

    <EXCEPTION_INFO>

      <TYPE>CM_MBF_IPA</TYPE>

      <ERROR_TEXT>Exception: Error in message header mapping; agent class is CL_COD_ORG_REPL_REQ_IPA</ERROR_TEXT>

      <CX_PROXY_INBOUND_APP_ERROR>

        <ERROR_PART href="#o694"/>

        <ID>APPLICATION_ERROR</ID>

        <RETRY_MODE>M</RETRY_MODE>

        <ERROR_CLASS_NAME>CX_APC_STANDARD_FAULT_MESSAGE</ERROR_CLASS_NAME>

      </CX_PROXY_INBOUND_APP_ERROR>

      <CM_AP_PROCESS_AGENT_TOOLS_BTM>

        <PREVIOUS_MESSAGE href="#o657"/>

        <SENDER_PARTY>FEDCLNT120</SENDER_PARTY>

        <SENDER_CONTACT_PERSON>No data available</SENDER_CONTACT_PERSON>

        <SENDER_PHONE_NUMBER>No data available</SENDER_PHONE_NUMBER>

        <SENDER_SYSTEM>No data available</SENDER_SYSTEM>

        <BUPA_INT_ID/>

        <BUPA_FORMATTED_NAME/>

      </CM_AP_PROCESS_AGENT_TOOLS_BTM>

      <CM_MBF_IPA>

        <MESSAGE_ATTRIBUTE_01>Error in message header mapping; agent class is CL_COD_ORG_REPL_REQ_IPA</MESSAGE_ATTRIBUTE_01>

        <MESSAGE_ATTRIBUTE_02/>

        <MESSAGE_ATTRIBUTE_03/>

        <MESSAGE_ATTRIBUTE_04/>

        <SENDER_TECHNICAL_ID/>

        <INVALID_MESSAGE_FIELD/>

        <IF_T100_MESSAGE.T100KEY>

          <MSGID>MBF_A2X_CORE</MSGID>

          <MSGNO>013</MSGNO>

          <ATTR1>MESSAGE_ATTRIBUTE_01</ATTR1>

        </IF_T100_MESSAGE.T100KEY>

      </CM_MBF_IPA>

    </EXCEPTION_INFO>

  </ERROR_INFO>

  <PROVIDER_INFO>

    <PROCESSING_UNIT>Sector 4: Provider</PROCESSING_UNIT>

    <PROCESSING_MODE>Asynchronous</PROCESSING_MODE>

    <PROCESSING_TYPE>Remote</PROCESSING_TYPE>

    <WORK_PROCESS_NUMBER>72</WORK_PROCESS_NUMBER>

    <WORK_PROCESS_PID>22325</WORK_PROCESS_PID>

  </PROVIDER_INFO>

</ERROR_CONTEXT>"

Do you know where i could find information about this kind of error? I notice that the payload message was recived ok. So i think I must be something from the C4C side.

Regards,

Sergio Agüero.

[Former Member · Accepted solution]

Hi Sergio,

In the payload of message in C4C you will have <SenderParty> and <RecipientParty>. If it is an inbound service interface in C4C, check if “SenderParty = ERP system” and “RecipientParty = My System (C4C)”.

The Recipient Party in payload should be same as My System in communication arrangement in C4C, if it is not the case, please correct the partner profile in ERP so that payload will send RecipientParty = My System.

Best Regards,

Cristiano Rosa

[Former Member · Accepted solution]

Hi Sergio,

We're integrating ERP and C4c and during BP replication, we're encountering the  similar issue   'agent class is CL_BUPA_ERP_REPL_IPA.

Issue : Exception: Error in message header mapping; agent class is C

Step : 1 when I trigger a message from SOAP UI to C4C via PI

We are getting the below error in C4C system

Exception: Exception: Error in message header mapping; agent class is C

Please have a look in to my Payload .

<?xml version="1.0" encoding="UTF-8" ?>

- <ns0:BusinessPartnerERPBulkReplicateRequestxmlns:ns0="http://sap.com/xi/SAPGlobal20/Global">

- <MessageHeader>

<ID /><UUID /><CreationDateTime>2015-11-03T18:12:44Z</CreationDateTime>

- <SenderParty>

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

</SenderParty>

- <RecipientParty>

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

</RecipientParty>

</MessageHeader>

- <BusinessPartnerERPReplicateRequestMessage>

- <MessageHeader>

<ID>0000000000198107</ID>

</MessageHeader>

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

<InternalID>1002</InternalID><SenderSequenceNumberValue>20151103151305</SenderSequenceNumberValue><CategoryCode>2</CategoryCode><LifeCycleStatusCode>2</LifeCycleStatusCode><FirstLineName>BALFOUR BEATTY GROUND ENG LTD</FirstLineName><CompanyLegalFormCode /><CustomerABCClassificationCode /><NielsenRegionCode /><IndustrialSectorCode />

- <ContactPerson actionCode="04">

<InternalID>23213</InternalID><FamilyName>Al Nile Engineering Consultants</FamilyName><BirthDate /><MaritalStatusCode /><FunctionCode /><DepartmentCode /><VIPCode />

</ContactPerson>

- <SalesArrangement actionCode="04"partnerFunctionListCompleteTransmissionIndicator="true">

<SalesOrganisationID>1000</SalesOrganisationID><DistributionChannelCode>10</DistributionChannelCode><DivisionCode>10</DivisionCode><SalesOfficeID /><SalesGroupID /><LifeCycleStatusCode>2</LifeCycleStatusCode><IncotermsClassificationCode>FH</IncotermsClassificationCode><IncotermsTransferLocationName>Free on board</IncotermsTransferLocationName><PriorityCode /><CustomerGroupCode /><CashDiscountTermsCode>0001</CashDiscountTermsCode><CurrencyCode>USD</CurrencyCode>

- <PartnerFunction actionCode="04">

<PartnerInternalID>1002</PartnerInternalID><DefaultIndicator>false</DefaultIndicator>

</PartnerFunction>

- <PartnerFunction actionCode="04">

<BusinessPartnerRelationshipCatagoryCode>RE</BusinessPartnerRelationshipCatagoryCode><PartnerInternalID>1002</PartnerInternalID><DefaultIndicator>false</DefaultIndicator>

</PartnerFunction>

- <PartnerFunction actionCode="04">

<BusinessPartnerRelationshipCatagoryCode>RG</BusinessPartnerRelationshipCatagoryCode><PartnerInternalID>1002</PartnerInternalID><DefaultIndicator>false</DefaultIndicator>

</PartnerFunction>

- <PartnerFunction actionCode="04">

<BusinessPartnerRelationshipCatagoryCode>WE</BusinessPartnerRelationshipCatagoryCode><PartnerInternalID>1002</PartnerInternalID><DefaultIndicator>false</DefaultIndicator>

</PartnerFunction>

- <BlockingReasons>

<OrderBlockingReasonCode /><DeliveryBlockingReasonCode /><BillingBlockingReasonCode /><SalesSupportBlockingIndicator>false</SalesSupportBlockingIndicator>

</BlockingReasons>

</SalesArrangement>

- <Role actionCode="04">

<RoleCode>Z001</RoleCode>

</Role>

- <BlockingReasons>

<OrderBlockingReasonCode /><DeliveryBlockingReasonCode /><BillingBlockingReasonCode /><SalesSupportBlockingIndicator>false</SalesSupportBlockingIndicator>

</BlockingReasons>

</BusinessPartner>

</BusinessPartnerERPReplicateRequestMessage>

</ns0:BusinessPartnerERPBulkReplicateRequest>

We are very critical stage , please help me  out .

Thanks ,

santosh.seera

[TiagoRibeiro · Accepted solution]

Hello Praveen,

Did you manage to solve this issue?

I am having same problem. I've checked sender party ID and recipient party and they are both fine.

Also from other threads i've seen we must check that Message Header ID should be in upper case and it is correct.

If you could provide any insights would be very helpful. Or anyone who has the solution for it.

Thanks in advance

João Ribeiro

[vinaykumardigaveedi]

Hi Experts,

I am facing the same issue . I have maintained everything as per this blog.

Please help me to resolve this issue.

https://answers.sap.com/questions/13163811/issue-with-incoming-payload-in-c4c.html

Thanks

Vinay

[ssuratharajan]

Hi All,

Kindly post the correct answer for this discussion if any , we are getting this error for all the inbound messages from ECC to C4C.

Regards,

Suratharajan S

[TiagoRibeiro]

Hello Suratharajan,

Sergio's solution is correct and the only one possible if i am not mistaken.

1. If we take the iflow and check the mapping file, we may confirm that in the message header mapping, only the Sender Party ID and Receiver Party ID are mapped between both systems.

2. Check if "My System" (visible in each Communication Arrangement, business data tab) is the same as the Logical System ID created in ERP (as suggested by Sergio)

3. Check in "Communication Systems" if

System Instance ID = Business System ID = IDOC Logical System ID

In my case, the problem was with the IDOC Logical System ID, was not the same. After correcting this, the problem has been solved.

Hope it helps and solves your problem.

Cheers,

João Ribeiro