HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received

[Robert_d_Hoedt]

Hi,

I'm trying to send message from S4 via ABAP Proxy to CPI.

I have done some entries in SXMB_ADM to make sure that messages are sent to CPI

I have set up a type-G connection in SM59 with URL of IntegrationSuite.

I have develop object in SPROXY'

I have configured iFlow in CPI with XI Sender Adapter

Now i try to test from sproxy and do manual COMMIT WORK.

I look in CPI monitoriing but i see no message.

I check in SXMB_MONI in S4 and there i find an error :

- <SAP:Error SOAP:mustUnderstand=" 1" xmlns:SAP=" http://sap.com/xi/XI/Message/30" xmlns:SOAP=" http://schemas.xmlsoap.org/soap/envelope/"> <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>M</SAP:Retry> </SAP:Error>

I have done some searching but I found no help regarding this issue for CPI.

Hoping for some helpfull suggestions

Kr, Robert

[Ryan-Crosby]

Refer to the comment I left on the previous thread for a clue on where to look.

[Robert_d_Hoedt]

Hi Ryan,

I'm sorry but your answer is way too cryptical for me.

Regards,

Robert

[Ryan-Crosby]

Hi Robert,

BE = best effort (meaning request/response or synchronous) and EO = exactly once (meaning request or asynchronous). Your original question mentioned asynchronous communication which should never expect a response.

[Robert_d_Hoedt]

Hi Ryan,

Thanks for clarifying.

I am indeed trying to set up asynchronous scenario S4 via ABAP Proxy to CPI.

And i think all my objects are asynch. If i test from SPROXY i see a request tab but no response tab. So that seems not to be the problem.

Regards

Robert

[Robert_d_Hoedt]

Some details for asynch

In CPI i have an XI adapter with message protocol XI3.0.

Also QoS is Exactly Once. (also tried with At Least Once)

[Ryan-Crosby]

If the CPI settings have the correct QoS then something is off in your proxy definition, somewhere.

[Ryan-Crosby]

Have you tried calling the interface from a sample program to see what happens? If so, can you share the code?

[VijayKonam]

The URL makes all the difference. Did you maintain the XI sender adapter based iFlow URL or just the Integration Suite base uRL in your SM59? Also, are you maintaining receiver id so that the right IS_URL parameter is getting used? You need to clearly mention you SXMB_ADM configuration. Otherwise, we would not know if you are really hitting CPI at all.

[Robert_d_Hoedt]

view-zender-ontvangerdefinitie-wijzigen.pngview-configuratie-van-integration-engine-weergeven.png

[Robert_d_Hoedt]

rfc-destination-to-xisender-cloud.png

[Robert_d_Hoedt]

Hi Vijay,

I added some screenshots of my configuration in SXMB_ADM, and SM59. The url that i used in SM59 is the URL for the iFlow in CPI:

https://xyz-yyyy-zzzz-1cea9t7h.it-cpi024-rt.cfapps.eu10-002.hana.ondemand.com/cxf/ReceiveXIMessage

Regards

Robert

[Robert_d_Hoedt]

And from the trace in sxmb_moni it looks like the destination is found:

<SAP:SITE_ID>CPI_OUT</SAP:SITE_ID>

<SAP:IS_URL>dest://TO_XISENDER_CLOUD</SAP:IS_URL>

[prathmesh009]

Hello Robert,

This was the same issue i have facing while working on Proxy to Rest Synchronous Scenario (on SAP PO 7.5 Dual Stack System)

The cause for this error is we are might be calling wrong SLD path from SAP.

Goto Tcode > SXMB_MONI and trace your call to the proxy

Here you can see the URL Destination on which you or trying to send data might be wrong. Please check or cross verify the same by following below step.

Please refer to tcode : sldapicust.

Check the following two things and try to execute the flow once, Let me know if needed more assistance.

Regards,

Prathmesh Sutar

[Ryan-Crosby]

the host in the SM59 destination should only have the host name... it should not include the protocol. The host information should also be copied from your CPI flow that has the associated XI sender channel.