ABAP Proxy PARSE_APPLICATION_DATA ERROR - Deserialisation error

Hi All,
Can some one please help me to resolve this issue, XML --> ABAP proxy scenario. PI sent message successfully, but I am getting error on SAP target system.
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<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/SASF1B34BDF7BC867BECB1E Line 127</SAP:P3>
<SAP:P4>An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E (Data loss occurred when converting ON Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 6025 XML Path: ns1:MT_HCM092_EmpPersonalData(1)PersonalDataUpdation(34)GBDEP(6)</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion: Request Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SASF1B34BDF7BC867BECB1E Line 127 An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E (Data loss occurred when converting ON Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 6025 XML Path: ns1:MT_HCM092_EmpPersonalData(1)PersonalDataUpdation(34)GBDEP(6) An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E Data loss occurred when converting ON</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The error is shown for the field GBDEP. It is of type char(3) both in the source system and the target system.
Still i am getting this error.
Kindly help me in resolving the issue.
Regards,
Sridevi S

Hi Klaus,
     Thanks for the t-code.
     I couldn't figure out any issue in that program. Below is the line of code in the program for the field GBDEP which is same as for the other fields.
    <tt:cond s-check="not-initial('ROOT.GBDEP')">
     <tt:ref name="ROOT">
      <GBDEP tt:ref="GBDEP">
       <tt:deserialize>
        <tt:assign to-var="_C_NIL" val="' '"/>
        <tt:d-cond>
         <tt:attribute name="xsi:nil">
          <tt:read var="_C_NIL" map="xml('true', '1') > val(C('2'))"/>
         </tt:attribute>
        </tt:d-cond>
       </tt:deserialize>
       <tt:cond-var check="_C_NIL!='2'">
        <tt:value maxLength="3"/>
       </tt:cond-var>
      </GBDEP>
kindly help.

Similar Messages

ABAP Proxy PARSE_APPLICATION_DATA ERROR

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" ?>
- 
- <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

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" ?>
- 
- <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

XI 3.0 SP14 Synchronous SOAP- XI- ABAP Proxy - fails with "System Error"

Hi All,
The synchronous response message fails at the stage "Receiver Identification".
It seems that the synchronous response XML has no "sender" attribute, so obviously the receiver determination fails.
In the message monitor I can see the correct payload coming from the ABAP proxy, so that part looks OK.
I have the same scenario working perfectly on another system landscape, so there might be a configuration side to it.
Thanks is advance,
Ofer
Message was edited by: Ofer Even-Tsur

Hi,
for the error information SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
looks like xi is not able to find a reciever of best case. Open up the scenario in COnfiguration, open up the modify(add spaces) and activate reciever determination / reciever communication channel.
cheers,
naveen

Synchronous scenario(ABAP proxy to HTTP_AAE) getting error exception as "Message Expired Exception"

Dear All,
I have done all the configuration for ABAP proxy scenario using AAE/ICO as per the below "how to guide" using SOAP as sender adapter using xi protocol. My SAP PI is 7.4 dual stack system. here third party is not a webservice its HTTP based we server so no wsdl.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?overridelayout=t…
However after running the scenario from ECC I am getting the exception as "Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message 53289257-97e0-06d0-e100-00000a70d384(OUTBOUND) expired.". I do not have any connection problem to third party(bank) URL. moreover I am able to get the response from bank using classical scenario s in PI, but the response message is not getting pushed to ECC, rather its reaming in PI SXMB_MONI with status "Log version".
Thats the reason I am trying to do using ICO, but using ICO PI is not even sending the request out of PI to bank. Please see the below receiver communication channel message log.
Thanks,
Farhan

Hi,
As per the log, the message has started 23:18:02 and failed at 23.23:02 it took 5min time, if message is not process certain time this kind of errors comes up. Have you changed adapter type for existing SOAP communication channel or created new? provide complete log of the message from starting time to ending time if possible.

ABAP Proxy Sync scenario with error No Implementing class registered error

I am working in a ABAP proxy to Proxy scenario. The connectivity is between SEM and PI systems(SEM->PI->SEM). Outbound synchronus interface is used to create proxy (Client Proxy) its a SAP standard interface. This scenario is configured as below,
1) Sender and receiver business system is the same for SEM with same client.
2) No Message and Interface mapping is used.
Please let me know, if the configuration is correct. if then, how to solve this error?
Regards,
User PI.

>>The connectivity is between SEM and PI systems(SEM->PI->SEM).
SEM->PI->SEM makes no sense. Why do you need PI here?
Any way, the error message implies the server proxy is not implemented (or activated) correctly.

ABAP Proxy throws HTTP-400 error

Hi,
I've created an ABAP Proxy/Enterprise Service in ECC6.0 to consume a webservice that is created in NetWeaver 2004s. Now, when I want to test the proxy, it gives me the error message:
SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 400 : Bad Request")
The error originates from class CX_AI_SYSTEM_FAULT
I don't know if it is related to the proxy or with some system settings on ECC 6.0/Netweaver2004s.
Any help or document reference is appreciated.
Regards.

I investigated a little and here are a couple of things you could try:
- In note 1139406, they are talking about a scenario with HTTP error 404... I realize it is different than the 400 you get, but it may be worth checking if you have a similar problem as described there - it may give a clue what your problem is.
- Try to check if the endpoint URL to which the request is sent is correct... it may be missing the style parameter, like ?style=document. Go to SOAMANAGER and take a look at the system settings, perhaps there is a wrongly formulated URL that is missing the style parameter.
Hope this helps a little...

Error Handling in Inbound ABAP Proxy with EOIO

Hi,
The scenario
I have a File to ABAP Proxy scenario and since the requirement is that the messages have to be processed in a single queue in the SAP system (i.e. EOIO), the sender file channel was configured to be EOIO. This ensures that all messages that enters the SAP system are put in a single queue and then processed one after the other.
The Issue
Now if one of the messages that enter SAP system fails during the processing in the ABAP program, the queue gets stuck and all messages after that go into a scheduled state. And one has to manually clear the errored message in order to continue processing the other waiting messages.
The Question
I know this is a default behavior in an EOIO scenario, however is there any way in which if a message fails in the ABAP program then one can automatically push it out of the queue and keep processing the other messages after it ?
Thanks
Bharath

As a general rule I only use EOIO when there is a possibility of dependancy between messages (message 1 must be first and finsihed before message 2 starts). Assuming your just moving the errored message asside, I would assume that EOIO should be just EO.
Alternatively, change the ABAP proxy to handle the error and return a clean status. Exception handling (try/catch) should be used were ever dangerous code is being used.
If alerting in the proxy end point is to much trouble - change your proxy to a sync scenario return the error to PI and fire alerts from there <- I think this should be avoided but it will work.
The main point is the exception handling so that the proxy fails "gracefully".

Error while activating ABAP proxy object

Hello,
I can see all the interfaces of PI7.0 in my ECC6.0 system.
I am able to create abap proxy object of a interface.
But when I try to activate that I am getting error as
"RFC system error for destination GTADIR_SERVER".
Pl can you suggest. appreciate quick help in this.
thanks in advance,
Sharada

Hi,
For more details take a look at note: [1063482 - Creating Dictionary objects - RFC error GTADIR_SERVER|https://service.sap.com/sap/support/notes/1063482]
It is written that: Message SGSUB 104 is not an error message, but is merely irrelevant information for customers. You can continue to create objects nevertheless.
To get rid of this annoying error you have to implement the corresponding support package.
Regards,
Jakub

ABAP Proxy error

Dear Friends,
I am facing a problem when i use a ABAP client proxy (asynchronously)
An error is raised during proxy method call-
<CODE>SERIALIZE_APPLICATION_DATA</CODE>
<b> <ERRORTEXT>Conversion error ABAP => XML (Request Message; error ID: CX_ST_INVALID_XML;
(/1SAI/TAS00000000000000000005 XML Bytepos.: 0 XML Path:
Error Text: Executing the operation '&OPERATION&' leads to an invalid XML document) )</ERRORTEXT></b>
The same proxy runs fine in upstream system (dev) but doesnot run in downstream system (QA) even though all proxy objects have been transferred.
This proxy & another proxy from the same calling report program is serialized in a queue.The first proxy is raising this error, but the second proxy call is successful.
Can someone help,
Thanks
Prasenjit

Hi Guru,
All the fields in the data type have string - also this roxy works fine in devpt. system- but it doesnt work in downstream QA system.
Other proxy interfaces in the QA system work fine.
The error message when i single test the proxy is as follows-
- <CX_XMS_SYSTEM_ERROR>
<ID>SERIALIZE_APPLICATION_DATA</ID>
<P1>Request Message</P1>
<P2>CX_ST_INVALID_XML</P2>
<P3>/1SAI/TAS00000000000000000005</P3>
<P4>XML Bytepos.: 0 XML Path: Error Text: Executing the operation '&OPERATION&' leads to an invalid XML document</P4>
<INFO />
<CATEGORY>XIProxy</CATEGORY>
<AREA>ABAP</AREA>
<CX_ST_ERROR>
<ST_PROGNAME>/1SAI/TAS00000000000000000005</ST_PROGNAME>
<X-ML_OFFSET>0</X-ML_OFFSET>
<X-ML_PATH />
<ST_IC>2</ST_IC>
<ST_TIMESTAMP>20070907163313</ST_TIMESTAMP>
</CX_ST_ERROR>
Any other possible solutions ?
thanks
Prasenjit

Error while invoking the ABAP Proxy via SOAP Adapter

Hi,
My scenario involves SOAP Client invoking a webservice hosted in PI which in turn invokes the ABAP Proxy asyncronously.
SOAP Client -> PI -> ECC (ABAP Proxy) . This works fine.
Next , I have exposed the ECC Service Interface as webservice using SOA Manager transaction. Now, once the service is created using SOAManager, i replaced the XI Adapter with SOAP Adapter and provided the target URL as the URL provided by the SOAManager.
SOAP Client -> PI -> ECC (ABAP Proxy via SOAP Adapter)
With this approach, i am encountering the below error message
2009-05-29 12:17:55 Error Adapter Framework caught exception: null
2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
Any ideas on the above errror message? Any pointers or inputs will be appreciated.
Thanks,
Vinayak Kamath

> 2009-05-29 12:17:55 Error Adapter Framework caught exception: null
> 2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
This is a generic error message which does not have any information about the error which has occurred.
Do you see any error messages in the SOAP client?
Regards
Stefan

OBJECTS_OBJREF_NOT_ASSIGNED error while executing ABAP proxy

Hi ,
I am getting the following error when i try to execute an abap proxy .
Unit ID in Background RFC     001EC9D184F702ECAA8DBC7401DC13E0
Name of First Function Module     SRT_SEQ_SCD_DLV_TRM_QRFC_NEW_C
Inbound Destination Name     WS_SERVICE_02DCA4961A0B_IN
Transaction Code                     SE38
Name of qRFC Queue                     SRTQC_001EC9D184F702ECAA8DBC6FE29753DB
Created On                     28.01.2009
No. of Predecessors                   1
Created At                                    12:44:10
Executed At                     12:44:13
Created At (Time Stamp)     20.090.128.114.410,9989340
User name                                     DEVELOPER
Tcode/program                      CL_SOAP_SCHEDULER_QRFC_NEW====CP
ID of Lock in Background RFC     001EC9D184F702DCAA8DBCA25EC41F5E
Lock Reason                     System error; not executed
Background RFC Scheduler ID              1
Message number                       341
Language Key                            EN
Status Text                               Unit has execution errors
Execution State                             Access using a 'ZERO' object reference is not possible.
Number of Called Function Modules     1
Number of Locks                                    1
Commit Check Disabled               X
Message Class                                  0
Message Variable                             OBJECTS_OBJREF_NOT_ASSIGNED
Executed On                             28.01.2009
and in ST22 transaction i am getting the following dump
Runtime Errors : OBJECTS_OBJREF_NOT_ASSIGNED
Exception         :CX_SY_RF_IS_INITIAL
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught in
    procedure "WSRM_CLONE_FOR_SPECIFIC_OPS" "(METHOD)", nor was it propagated by a
     RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    An attempt was made to access a component (variable: "ME->M_CTX") with a 'ZERO'
    object reference (points to 'nothing').
    An object reference must point to an object (an instance of a class)
    before it can be used to access a component.
    Either the reference has not yet been set or it was set to 'ZERO' using
    a CLEAR statement.
Please help in solving this issue.
Thanks&Regards,
Hamsa Shree

Hi
Runtime Errors : OBJECTS_OBJREF_NOT_ASSIGNED
Check with the SAP Notes Note
557770 - SAP BP: Short dump OBJECTS_OBJREF_NOT_ASSIGNED
may be you get the exact help
Regards
Abhishek

Error while create abap proxy

Hi,
I need to create abap proxy in sap system to push the data from sap system to XI.
when i create ABAP PROXY in sap system in Tcode SPROXY,System displays a error
"objects from other name spaces missing" .
So i am not able to activate the abap proxy.
kindly let me know how to solve this error.
Regards,
Ganesh

Are you using the message type created in external system?
Are any of your Data type element refer structure to other namespace.
Error mention that it does not find the detail structure of any of Datatype element. Check all link are available properly.
Gaurav Jain
Points if answer is helpful

Error while generating ABAP proxy

Hi,
We created a WSDL using lotus notes (Domino) tools. While creating a proxy object using ABAP (transaction SE80), we get the error message "Cannot generate proxy (object missing in WSDL, see long text)" Message no. SPRX084.
We looked at OSS notes and applied 1046046 - Proxy generation problem with external definitions and all dependent notes as we are on a lower support pack. (WAS 6.40. SAPKB64019).
We are wondering if it is anything to do with the format/defintions in the WSDL. Can anyone send me a sample WSDL file that has been used to create an ABAP proxy object successfully. We would like compare the domino generated file. Please note that XI is not involved, we are using ABAP to call a webservice in the internal network application.
Thanks,
Girish

Hi,
I've implemented this proxy without problem and it's working fine in my case (I didn't have to store WSDL file localy and do any changes in it - Netweaver 7.2). If it's not SAP issue as Brad proposed then maybe network admins have set filters that are blocking communication with this service
Best regards
Marcin Cholewczuk

Error while usinjg the JDBC to ABAP Proxy Scenario

Hello Rocks,
This is my scenario like JDBC --- Pi --- ABAP Proxy
while i am given a sender side jdbc XSD structure is like this
VWENTITYAGGREMENT
Row             1-unbound occurence
      POOL_ID   0-1 occurence
      CUST_ID
      AGREEMENT
       PRODUCT_ID
        CONTRACT_TYPE
        CONTRACT_TYPE_DESCR
        AGRMNT_STATUS
        STATUS_DESCR
          EFFDT
         TERMINATION_DT
         ADD_DT
         ADD_TM
while i am writing a select query in Sender JDBC CC is like this
SELECT POOL_ID,CUST_ID,AGREEMENT,PRODUCT_ID,CONTRACT_TYPE,CONTRACT_TYPE_DESCR,AGRMNT_STATUS,STATUS_DESCR,EFFDT,TERMINATION_DT,ADD_DT,ADD_TM FROM vwEntityAgreement.
Here i am getting this Error message like this :
Error Description: Database-level error reported by JDBC driver while executing statement 'SELECT POOL_ID,CUST_ID,AGREEMENT,PRODUCT_ID,CONTRACT_TYPE,CONTRACT_TYPE_DESCR,AGRMNT_STATUS,STATUS_DESCR,EFFDT,TERMINATION_DT,ADD_DT,ADD_TM FROM vwEntityAgreement'. The JDBC driver returned the following error message: 'com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'POOL_ID'.'. For details, contact your database server vendor.
So please give me your valuable inputs !
Regards,
Ravi.

Invalid column name 'POOL_ID'.'. For details, contact your database server vendor.
Did you confirmed the name POOL_ID as suggested?
Why is the tablename different (check the case) in the query that you make and in the XSD structure that you mentioned......check if this is causing the problem.
Regards,
Abhishek.
Edited by: abhishek salvi on Jun 4, 2010 10:24 AM

Error while executing sender ABAP proxy program in ECC

Hi,
We have lot of proxy to file scenarios, most of them are working fine. I am having issue with 2 interfaces, when I execute sender ABAP proxy program, we are getting following errors in ECC:
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:Stack>com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=ED1CLNT290;TS=;AN=CustTrPowersellS_Out;ANS=urn:maines-net:OTC_079E:PowersellCustomerTerms; at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:237) at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:167) at com.sap.aii.af.service.cpa.InboundRuntimeLookup.<init>(InboundRuntimeLookup.java:88) at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBinding(AbstractLookupManager.java:519) at com.sap.aii.adapter.soap.web.MessageServlet.getBinding(MessageServlet.java:875) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:439) at etc etc
Configuration should be fine because many scenarios are working. Can you please help me where could be the error?
Let me know if you need more info.
Regards,
N@v!n

Hi Naveen,
We saw your solution about this issue. We are also facing same issue. I wanted to know where we have to update scenario as simple scenario or integrated scenario.
And could you please tel me what is the main diff between in these two.
As we are are using PI 7.31 java stack so for this version what we have to use.
Thanks,
Shivdeep Kumar

ABAP Proxy PARSE_APPLICATION_DATA ERROR - Deserialisation error

Similar Messages

Maybe you are looking for