cancel
Showing results for 
Search instead for 
Did you mean: 

BP Replication [CO_COD_UTIL_BP_REPLICATION] Error - soap:MustUnderstand

shahbhat
Advisor
Advisor
0 Kudos

Hi,

We are using a report COD_UTIL_BP_REP_LOAD in ECC to trigger a consumer proxy CO_COD_UTIL_BP_REPLICATION for replicating BP from ECC to C4C using CPI as middleware.

We are getting the following error message on ECC upon triggering this web service [ t-code used to check the logs is SRT_UTIL_LOG]:

In t-code SRT_MONI, following error is logged:

We also checked the payload in SRT_MONI and tested it manually in CPI mapping and it's working successfully.

Here's the screenshot of the Messaging config in SOAMANAGER for the consumer proxy:

It's setup by default when we configured the logical port.

Here's the error in the CPI Message Processing Log:

It seems like an issue with SAP standard config for the consumer proxy web service as we are using SAP standard web services and IFlows. The only change we did was to create a logical port and activated it.

NOTE: We have successfully setup and tested the inbound and outbound connectivity between the systems using connectivity webservices and IFlows.

sriramsbg
Active Contributor
0 Kudos

Hi Bhat

Could you share the SP level of component CODERINT 600 on your ERP system?

Regards

SS

shahbhat
Advisor
Advisor
0 Kudos

s.sriram Here it is:

Accepted Solutions (1)

Accepted Solutions (1)

shahbhat
Advisor
Advisor
0 Kudos

Here's the correct Messaging config as per SAP which fixed the issue:

Answers (1)

Answers (1)

sriramsbg
Active Contributor
0 Kudos

Hi Bhat

Refer to the SAP note 2547679 & 2680219, If you are facing same issue you may have to contact SAP.

Regards

SS

shahbhat
Advisor
Advisor
0 Kudos

s.sriram It's not an authentication issue as the notes suggest. We ruled that one out after doing our due diligence. It definitely seems an issue with how the async request is being created by SAP standard code. It adds two properties which CPI is failing to comprehend. Regardless, we will create an incident with SAP regarding this.

Thanks