cancel
Showing results for 
Search instead for 
Did you mean: 

Fault Message from SOAP

Former Member
0 Kudos

Hi,

i have abap proxy 2 soap in Sync, i made error intentionally as below; the follwoing error was shown by SXMB_MONI.

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

- <!-- Request Message Mapping

-->

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

<SAP:Category>XIServer</SAP:Category>

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

<SAP:P1>/ CPIC-CALL: 'ThSAPOCMINIT' not register transaction program</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. / CPIC-CALL: 'ThSAPOCMINIT' ot register transaction program</SAP:Stack>

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

</SAP:Error>

How can i catch the error message at Sender ABAP Proxy Side?

Do i create Fault Message both Outbound and Inbound?

if so, how can i map to Fault Message Structure for Inbound from above error message due to returned error structure looks different against Fault Message?

Regards;

ogawa

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Ogawa,

Go to SM59 of XI Box->TCP/IP Connections->AI_RUNTIME_JCOSERVER ... test this connection.

If jco is connecting properly then there may be some problem with j2ee server. If its not connecting then try restarting the system. This may work.

If there is any error, then Try to recreate the same or restart the System or take the basis help.

For more-

I hope this helps....

Regards,

Abhy

Former Member
0 Kudos

hi,

thanks for the note...

here is actual applicatoin error comming from soap.

i got Request Message Mapping for response as below.

how can i send this message to sender side(abap proxy)?

I created Fault Message by using Exchange_Data in IR, and i assigned this to Message Interface(Outbound/Inbound),,

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

- <!-- Request Message Mapping

-->

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

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

<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>application fault</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="">Message</SAP:ApplicationFaultMessage>

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Regards;

ogawa

Message was edited by: ogawa Dennis

Message was edited by: ogawa Dennis

Former Member
0 Kudos

How your payload looks like? I have the same problem and that's my current solution.

You have to define a type that matches your payload in error case. Then you have to add this type as fault message type (external message) to your interface definition. Then you need a message mapping for this fault type and then you have to add this to the relevant interface mapping.

Here is my thread: