on 07-13-2010 10:07 PM
Hi Guys,
Can some one please help me to resolve this issue, XML --> ABAP proxy scenario. PI sent message successfully, but I am getting error on SNC target system.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
<SAP:P1>Request Message</SAP:P1>
<SAP:P2>CX_ST_DESERIALIZATION_ERROR</SAP:P2>
<SAP:P3>/1SAI/TXSF8E9D07F84DB493AAA0A Line 3340</SAP:P3>
<SAP:P4>An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A (Data loss occurred when converting 00900012300355698 Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 529 XML Path: ns2:ProductActivityNotification(1)ProductActivity(2)Item(3)ShipToLocation(1)StandardID(2)</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion: Request Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/TXSF8E9D07F84DB493AAA0A Line 3340 An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A (Data loss occurred when converting 00900012300355698 Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 529 XML Path: ns2:ProductActivityNotification(1)P An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A Data loss occurred when converting 00900012300355698</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks in Advance
Regards
San
San,
There is an error with the XML data ... have you changed the data structure after the generation of the proxy? If yes, regenerate the proxy.
Regards,
Neetesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Niteesh,
I haven't got any kind of trasformation issues with xml, on PI box all are checked flags. I did validate xml file every thing looks okay. But this inbound proxy on SNC side an issue like above. If I am wrong please correct me, I don't think we need to regenerate proxy on SNC side.
Many Thanks
Regards
San
Hi Folks,
I have got application error while doing in Inbound proxy scenario. This inbound message is ProductActivityNotification, this message has got fault message. This message is triggering for faults. How to control this fault message or how to divert this error as an alert to RWB. Please give me your ideas step by step. Error as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SAPGlobal20/Global">ProductActivityNotificationFault</SAP:ApplicationFaultMessage>
<SAP:Stack>Application has thrown an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please find the fault message has got following values
<?xml version="1.0" encoding="utf-8" ?>
- <n0:ProductActivityNotificationFault xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:RAS:/1SAI/TAS653D9A9CCD9A8EF3AF9B:701:2009/02/10">
- <standard>
<faultText>Proxy Class (Generated)</faultText>
- <faultDetail>
<severity>information</severity>
<text>Start of inbound processing: ProductActivityNotification (ID )</text>
<id>000(/SCA/BIF_PROACT)</id>
</faultDetail>
- <faultDetail>
<severity>error</severity>
<text>Message ID is missing</text>
<id>032(/SCA/BIF_MI)</id>
</faultDetail>
</standard>
</n0:ProductActivityNotificationFault>
Will you please focus bit light on this error message please?
Regards
San
Hi Neetesh Raj,
In my scenario, inbound proxy has got falut message. This fault message throwing this error. Please check on SXMB_moni on Target system, xml message-->Call inbound proxy -->main document, open this you can see fault details, Check with all your fault message fields, there must be couple of / one filed mapping is not proper for target, check on target side, what kind of field and type etc., map on ESR accordingly, the problem will resolve.
Have a great time.
Regards
San
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.