cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Outbound Proxy to CPI

babruvahana
Contributor
0 Kudos

Hi Experts,

Our Requirement is to trigger a outbound proxy from SAP to CPI.

Steps followed:

  • Created WSDL from NWDS.
  • Created consumer proxy in SAP using the same WSDL.
  • Completed the SOAMANAGER configurations and the ping is successful.

We are able to trigger a message from SOAP UI using the same WDSL and credentials and it is successfully reaching CPI. But Messages are not reaching to CPI when proxy is triggered from SAP ECC system. When we trigger the proxy from SAP it is failing in SAP with the below error when checked in SXMB_MONI.

Error Log:

***************

<?xml version="1.0" encoding="UTF-8" standalone="true"?>
<!-- Call Integration Server -->
-<SAP:Error xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1/>
<SAP:P2/>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4/>
<SAP:AdditionalText/>
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element {http://schemas.xmlsoap.org/soap/envelope/}Envelope missing in SOAP message header (SAP XI Extension) </SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error> 

***************

Any leads to resolve this will be highly appreciated.

Regards,

Pavan

Accepted Solutions (1)

Accepted Solutions (1)

babruvahana
Contributor

Hi manoj.khavatkopp , anilyakkali bhaskar.mamilla ,

Thanks a lot for your response.

WSDL and SOAMANGER configurations are valid and didn't have any issues.

In ECC, they were not selecting the logical port while triggering the consumer proxy. So the messages weren't reaching CPI. We are able to resolve it now by including the logical port in the ABAP program 🙂

Regards,

Pavan

Answers (4)

Answers (4)

sumanth171
Active Participant

Hi Pavan,

Hope you found the solution and if not adding to Bhaskar's comment, what is the ping test result from SOAManager? You can check the system logs as well in CPI for more information.

Regards,

Anil

manoj_khavatkopp
Active Contributor

Hi Pavan ,

You have configured sender channel as SOAP , so accordingly config has to be done in SOAMANAGER , and these message should I appear in SXMB_MONI . If it's actually a proxy interface then you need to configure XI as sender channel in CPI.

Thanks,

Manoj k

former_member306381
Participant

Hey Pavan,

  • It could be an issue with Outbound Service Consumer and SOAMANAGER Configuration.
  • can you check the binding happened correctly?
  • Is the service active in SOAMANAGER?
  • Did you maintain the endpoint correctly?Hope you have done it?

Regards,

Bhaskar

sumanth171
Active Participant
0 Kudos

Hi Pavan,

Please check if your wsdl has a response section in it and if CPI interface is async, since there won't be any response you can see this error.

Regards,

Anil

babruvahana
Contributor
0 Kudos

Hi Anil,

Yes, the WSDL has a response section and I am able to get the response in SOAP UI. But Messages are not reaching to CPI when proxy is triggered from SAP ECC system.