cancel
Showing results for 
Search instead for 
Did you mean: 

BP Replication issue

kinsbrunner
Active Contributor
0 Kudos

Hi all,

I am on a ERP-C4C integration scenario through PO and, when trying to move Accounts from ERP into C4C, we are facing some messaging issues.

IDOCs are in green status on WE05 on ERP side, they get into PI and are then forward to C4C. The issue is that PI is getting an error: "Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Web service processing error; more details in the web service error log on provider side (UTC timestamp 20150624202822; Transaction ID 00163E0924E81EE586D5F1E6C66557D8)"

Also, we tried creating a SoapUI project and tried to manually do everything and he received from C4C the following issue:

<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
   <soap-env:Header/>
   <soap-env:Body>
      <soap-env:Fault>
<faultcode>soap-env:Server</faultcode>
<faultstring xml:lang="en">Web service processing error; more details in the web service error log on provider side (UTC timestamp 20150624204712; Transaction ID 00163E0924E81EE586D646065992D9B7)</faultstring>
<detail/>
      </soap-env:Fault>
   </soap-env:Body>
</soap-env:Envelope>

We are not sure what's going on and we have no idea if there is somewhere in C4C where we could get further details. WebService log in C4C does not seem to have any clue as there are no registries about this run.

Any idea?

Thanks and regards.

Alejandro.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Alejandro,

  1. Have you generated Communication Arrangements on C4C side ?
  2. Have you double checked that URL in communication channel receiver is the same you find in the CommArrang (inbound tab) involved in the communication ?
  3. Have you imported C4C certificate in SAP PI ?
  4. Can you have a look at Log Viewer in the NWA ? I think you can grab there further info about this error.
kinsbrunner
Active Contributor
0 Kudos

Hi Francesco,

1. Yes

2. Yes, already checked and they are equal

3. Yes, just rechecked with Basis consultant

4. Yes, nothing additional.

Let me know in case you have any idea!

Thanks and regards.

Alejandro.

Pragya_Pande
Contributor
0 Kudos

Last thing on it - I found this error on the latest bp replication to C4C "SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message ID"...check the config on the service..perhaps this will help..

http://scn.sap.com/thread/3390497

0 Kudos


Hi Pragya, hi Alejandro

if this is the error... then we should check the following settings on PI Receiver Agreement-> Communication Channel:

1) the URL should have the query parameter ?MessageId

2) Conversion Parameter "Use Encoded Headers" and "Use Query Strings" should be flagged - all other conversion parameters shall be un-flagged

Best regards,

Berthold

kinsbrunner
Active Contributor
0 Kudos

CORRECTTTTTT!!!!

Thanks Berthold, brilliant!!!!

Also, thanks to all the others who have been supporting and helping!

0 Kudos

Awesome  - thanks, !!!

Former Member
0 Kudos

Hi Ginger,

This behavior I believe is buggy a bit. When applying a Communication Channel template from pre-delivered content - only "User Query String" is applied to new Communication Channel but User Encoded Headers checkbox is left blank (which obviously shouldn't be).


Or is there any specific version of Integration Content that needs to be imported into ESR in order to get this fixed?

Cheers,

Ilja.

Answers (1)

Answers (1)

chandansb
Active Contributor
0 Kudos

Hello Alejandro,

You mentioned,

IDOCs are in green status on WE05 on ERP side, they get into PI and are then forward to C4C.

Does this mean your message are trying to reach/reaches C4C? Do you see any error in C4C Web Service Monitoring?

Yes many time we do not get detailed error. I will suggest you to check the configurations that you did in PO. Green status in ERP suggests ERP - PO connection is successful. Check the connection between PO- C4C. I am not PO expert but we maintain the C4C Inbound URL in PO adapter. Check the ping test for this, if possible.

Regards,

Chandan

kinsbrunner
Active Contributor
0 Kudos

Chandan,

I understand IDOCs are reaching C4C as PI is throwing the fault code message.

There are no registries on Web Service Monitoring...

Isn't there any other way to see inbound communications into C4C in order to confirm if issue is in PO or C4C?

Regards.

Alejandro.

chandansb
Active Contributor
0 Kudos

Hello Alejandro,

When I look at this situation, my understanding is that C4C has it's inbound communication URL created automatically so there should not be any issue with it. Only issue on the C4C side might be the authentication. But this doesn't looks like authentication issue. But it look much on the PO side. So for standard integration scenario, I will try to analyze if my PO colleague have maintained the configuration as per expectation. Something like if he has mentioned the inbound URL from C4C communication arrangement where it needs to be and try to see if the ping test is successful from PO to C4C. (Not sure if there is any option of ping test in PO, kindly confirm)

Will keep you posted if I get anything else to share with you for this.

Regards,

Chandan

Pragya_Pande
Contributor
0 Kudos

Dear Alejandro,

Are you getting nothing with any of the status filters in web monitor?

If so then chances are that the call has got rejected due to configuration mismatch. It may happen due to the url issue as Chander has pointed out. Also check the payload and see if the service definitions match. If still no clue then send me the tenant url in a message. I will have a look.

Best Regards,

Pragya

kinsbrunner
Active Contributor
0 Kudos

Pragya,

Just sent you the information to pragya.pande@sap.com.

Hope you can provide us some clue to solve this!

Thanks and regards.

Alejandro.

Pragya_Pande
Contributor
0 Kudos

Hello Alejandro,

I could find only oneBusinessPartnerERPReplicationInin message in C4C. It has error - unsupported content and has not payload. Please check in PI of you are sending a payload.

There were 2 more errors for BP from C4C to ERP and they had got error that 'couldn't retrieve inbound binding'...

I could not see any log for the message id or the timestamp in the error.
Have you completed the codelist mapping and the mappings on the PO?

Best Regards,

Pragya

kinsbrunner
Active Contributor
0 Kudos

Pragya,

I am not sure on what to do.

CLM has been done, I first did automatic and then did some manual adjustments.

Let me know in case you have any clue or advice on what to do.

Thanks and regards.

Alejandro.

Pragya_Pande
Contributor
0 Kudos

Is this the first scenario you have tried for integration? Has any other worked?

Has there been any extension fields created for the account?

If these don't help then I guess opening an incident would be a good idea.

kinsbrunner
Active Contributor
0 Kudos

1) Yes, it's the first scenario.

2) Yes, there was a field extension. It was done through KUT and then, WS adapted from KUT options. Then dowloaded the new WSDL and PI consultant updated it on PI.

I think I will go through an incident as this is not advancing.

Thanks!

Pragya_Pande
Contributor
0 Kudos

One last thing since you say it is the 1st scenario you are trying- please deploy the connectivity iflow and test the connectivity from both ends- c4c and erp.
that will rule out any connectivity configuration errors

0 Kudos

If you know you have connectivity, we can also check C4C to see if anything came into the SAP network.  This is not something you can do, but we will need to do it.

- should they create an incident and request this - what do you think?

0 Kudos

Hi Alejandro,

for me this looks more like a mapping error. It can be either while sending/mapping the message from XI to SOAP Adapter (PI internal) or while sending the SOAP message to CfC.So you can do two things:

1) check if you see error details in PI Monitor on Java Stack (thats where the SOAP Adapter is)

2) Provide me the CfC tenant URL - so that I can check the CfC backend.

Best regards,

Berthold


kinsbrunner
Active Contributor
0 Kudos

Pragya,

Suddenly we realized that Test Connectino from C4C is not working anymore...

Error is: SOAP:1.023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_SSL_ERROR")

Seems to be something changed related to certificates :s

Any idea?

We are checking once again everything with Basis.

Regards.

Alejandro.

kinsbrunner
Active Contributor
0 Kudos

Ok, WebDispatcher was down.

Now we are on the same page as before.

E2E connectivity report on ERP is running succesfully as well as C4C Test Connection...

kinsbrunner
Active Contributor
0 Kudos

Ginger,

I am currently having connectivity. Would it be possible for you to check what you are asking. Also, I already have an incident created (3100877540).

Thanks in advance.

Regards.

Alejandro.

0 Kudos

Please do what Berthold recommended.

kinsbrunner
Active Contributor
0 Kudos

Berthold,

I think that if it would be a mapping issue, it would be much clear, shouldn't it show some more specific error?

1) I reached the PI consultant and he showed me that the PI monitor has the error I reported on my initial message.

2) I sent the tenant ID into berthold.wocher@sap.com Kindly let me know if that is not your mail.

Regards.

Alejandro.