SAP PI - ECC Server Proxy

[itabhishek9]

Hi SDNites,

I am working on Async / Sync bridge where I have to send a async file to ECC synchronous proxy and the response from the proxy will generate a new file.

I have configured File to Proxy where on the receiver communication channel I have used AF_Modules/RequestResponseBean and AF_Modules/ResponseOnewayBean. But when a request is sent from PI to ECC I am getting the bubble exception.

Below are the details of the error,

15.05.2015 15:17:27.227 Error Error during parsing the received XMB message.

15.05.2015 15:17:27.227 Error SOAP: Call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]

15.05.2015 15:17:27.229 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]

15.05.2015 15:17:27.229 Error SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.srt.BubbleException: HTTP Response Received. Status Code = 500 [null "null"]

Any pointers will be of great help.

Regards,

Abhi

[ManishaRD25]

Hello,

Did you see this blog and followed it.

http://wiki.scn.sap.com/wiki/display/XI/File-RFC-File(Without%20BPM)?original_fqdn=wiki.sdn.sap.com

Regards,

Manisha

[former_member187024]

Anyone has solution for this as the mapping operation used by me is correct.

I've created two message mappings one mapping for request message type of outbound interface to inbound interface and another mapping for response message type of inbound interface to outbound interface and mapped it into single operation mapping using both request and response tabs

This error is coming on response mapping program i.e. from mapping inbound response message type to outbound response message type.

[former_member187024]

I'm also working on the same scenario.

I've got the 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>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 {http://schemas.xmlsoap.org/wsdl/}definitions; HTTP 200 OK</SAP:AdditionalText>

<SAP:Stack />

After reading several threads i came to know about do not use SOAP envelope in communication channel

at receiver and sender end. Both should be checked. I did that and it caused a new error which is :

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

- <!--

 RResponse Message Mapping 

--> 

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Category>Application</SAP:Category>

<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>

<SAP:P1>com/sap/xi/tf/_MAP_MSG_CUST_STATUS_OUTPUT_</SAP:P1>

<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>

<SAP:P3>on: Cannot create target element /ns0:CUSTOMER_OUT</SAP:P3>

<SAP:P4>PUT_OB. Values missing in queue context. Target X~</SAP:P4>

<SAP:AdditionalText />

<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MAP_MSG_CUST_STATUS_OUTPUT_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:CUSTOMER_OUTPUT_OB. Values missing in queue context. Target X~</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

[itabhishek9]

Hi Inaki,

Thanks for the response.

I have already put the breakpoint into ECC using the same login which has been configured in PI but it is not stooping at the point. Also there is no log gerenrated in SXMB_MONI on ECC end and there is no dump in ST22.

Regards,

Abhi

[iaki_vila]

Hi Abhishek,

First of all you should assure that the message is arriving to ECC. Enable the ECC monitoring to let you monitor by sxi_monitor. Then you can check if the message is comming. Check st22 transaction in the st22 if there are any exception. Also you can set an external breakpoint in the ECC first line code, you must use the same user that you have defined in the channel.

In this way you check if at least the configuration for the incoming message in the proxy is right.

Regards.

[sateesh_adma]

Hello Abhishek,

Have you checked these