APPLICATIONCALL.PARSE_APPLICATION_DATA

Hi XI Masters,
I am getting the following error message in R/3 while processing an XI message by ABAP Proxy.
System Error
Code: APPLICATIONCALL.PARSE_APPLICATION_DATA
Error when handling Request Message; XSLT error: CX_XSLT_RUNTIME_ERROR: XSLT program and source line: /1SAI/XS000000000000000000003:
If any one faced the same error, please share your experience.
Regards,
Rajesh.

Hi,
The inbound message (data) and the Proxy that have been generated are not incompatable....
Can u post the complete error. I can help u out in telling what the exact problem might be... ( which data element is creating a problem/ incompatable....)
U can refer to the following thread where they has the same exception <b>APPLICATIONCALL.PARSE_APPLICATION_DATA</b>( b'cos of improper date formats...)So urs should also be a simlilar problem i guess..
Inbound Proxy Error in Target System
Cheers,
Siva Maranani.

Similar Messages

  • ABAP proxy regenration

    Hi,
    I've got the following problem with ABAP proxy objects (acting as receiver).
    We are using XI 3.0 to connect to WAS 6.20.
    APPINT     200_620     0006     SAPK-20006INAPPINT     SAP Exchange Infrastructure 2.0     Add-On Support Pack.
    We have changed the max length size of one tag (leaf in the deep structure) in the message. The new max length is longer than before (was 10 is 12). Proxy was regenerated and activated.
    On the ABAP side this field has new size (12).
    After sending a message with value 000071108000 in this tag I've got the following error:
    <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <SAP:Context />
      <SAP:Code p1="Request Message" p2="CX_XSLT_DESERIALIZATION_ERROR" p3="/1SAI/XS00000000000000000009: 0000000252" p4="Tree Position: abap.values.1.1.2.2.2.14.10 ABAP Classname: CX_SY_CONVERSION_DATA_LOSS Data String: 000071108000">APPLICATIONCALL.PARSE_APPLICATION_DATA</SAP:Code>
      <SAP:Text language="EN">Error when handling Request Message; XSLT error: CX_XSLT_have_ERROR: XSLT program and source line: /1SAI/XS00000000000000000009: 0000000252; Tree Position: abap.values.1.1.2.2.2.14.10 ABAP Classname: CX_SY_CONVERSION_DATA_LOSS Data String: 000071108000</SAP:Text>
      </SAP:ErrorHeader>    
    Pls help.
    Regards
    Artur

    Hi Artur,
    you can also check if the tables that you've changed
    are reflected in transports have you checked that?
    there's a report for invoking those changes: SAP note 853554
    Let me know if you check it
    Regards,
    michal

  • Error when calling inbound proxy

    Hi all,
    I´m facing the following problem in the R/3 monitoring:
    <SAP:Code p1="Request Message" p2="CX_XSLT_RUNTIME_ERROR" p3="/1SAI/XS00000000000000000035: 0000000000" p4="Error Text: No valid source context supplied Kernel ErrorId: CX_XSLT_RUNTIME_ERROR">APPLICATIONCALL.PARSE_APPLICATION_DATA</SAP:Code>
      <SAP:Text language="EN">Error when handling Request Message; XSLT error: CX_XSLT_RUNTIME_ERROR: XSLT program and source line: /1SAI/XS00000000000000000035: 0000000000; Error Text: No valid source context supplied Kernel ErrorId: CX_XSLT_RUNTIME_ERROR</SAP:Text>
      </SAP:ErrorHeader>
    I'm pulling a file from an external server and I pass the data to R/3 thru ABAP proxies. The point is that I am splitting the message in different parts, using the parameter Recordsets per Message, and mostly all of them are processed correctly, but in a few of them i´ve got that error. And if I process that parts of the file, that have caused the error, separately, they surprisingly work fine..
    I really do not know what happens and i really need help because I do not know what else to try or what could be the reason of this error.
    Thanks a lot!!

    the problem is INbound Message and the proxy genereted are not compatiable, can u check the field "S00000000000000000035: 0000000000;" whch field is atking this value from file, while passing to the R/3 check the lengths of this field....you will not c this error in MM, but you have to chcek the length of each field in proxy with data coming.......
    copy the payload from SXMB_MONI and directly try to send the data from SPROXY you will get the error detail....
    U can refer to the following thread where they has the same exception APPLICATIONCALL.PARSE_APPLICATION_DATA( b'cos of improper date formats...)So urs should also be a simlilar problem i guess..
    https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/thread.jspa%3FforumID%3D44%26threadID%3D45455

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

    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

  • 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') &gt; 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.

  • PARSE_APPLICATION_DATA Error during XML = ABAP conversion: Response Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SAS0446CC11CC6EC1AD4789 Line 24 An error occurred when deserializing in the simple transformation program /1SAI/SAS0446CC11CC6EC1AD4789

    Hi Experts ,
    i have a scenario proxy to soap  where i am getting error while getting the response .
    we are sending the request successfully and getting response .some times we are getting in proxy level error below
    PARSE_APPLICATION_DATA Error during XML => ABAP conversion: Response Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SAS0446CC11CC6EC1AD4789 Line 24 An error occurred when deserializing in the simple transformation program /1SAI/SAS0446CC11CC6EC1AD4789 (Cha
    Please help us to fix this bug in proxy response.
    Regards
    Ravi

    Hello Ravinder,
    Can you please post the complete stack trace, it seems to be some fields are getting truncated i,e data sent from the program to the proxy object might be violating some length restrictions.
    Please check your message interface field lengths and what is being passed to the proxy.
    Regards,
    Ravi.

  • XIProxy:PARSE_APPLICATION_DATA , error in soap sender communication channel

    HI
    I am having soap toABAP proxy synchronous interface , when i test from  soap UI tool i am getting the below errro . can any body help me with this error
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
                   <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
         at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1178)
    regards
    sandeep
    Edited by: pendyalas on Jul 27, 2011 5:01 PM

    Hello,
    can you check the message format defined in repository.
    Regards
    Vivek

  • PARSE_APPLICATION_DATA Error during XML  error ID: CX_ST_DESERIALIZATION_ER

    Hi All,
              Iam Getting the error for Parse Application Data -error ID: CX_ST_DESERIALIZATION_ERROR;  Pls check the log file..
    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 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error during XML => ABAP conversion (; error ID: ; ( )) PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXS00000000000000000026 XML Bytepos.: 1465 XML Path: ns1:YMMSTNPSR_FILEUPLOAD(1)STNPSRTAB(1)item(2)MATSTNVAL(24) Error Text: The argument '?007-08-14' cannot be interpreted as a number. Kernel ErrorId: CONVT_NO_NUMBER)) Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXS00000000000000000026 XML Bytepos.: 1465 XML Path: ns1:YMMSTNPSR_FILEUPLOAD(1)STNPSRTAB(1)item(2)MATSTNVAL(24) Error Text: The argument '?007-08-14' cannot be interpreted as a number. Kernel ErrorId: CONVT_NO_NUMBER)) An error occurred when deserializing in the simple transformation program /1SAI/TXS00000000000000000026 The argument '?007-08-14' cannot be interpreted as a number.</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    can u please help me..
    Thanks & Regards,
    NVR

    NVR,
    Two things...y date is coming as "?007...."   "?" can u pls. check first character in date...
    Second are you assigning this value to Number field? number cannot access "-" as a separator...
    Please check.
    Nilesh

  • Proxy error - APPLICATIONCALL.OUTBOUNDFRAMEWORK

    Hi,
    I am executing a proxy synchronous method from R/3. Can anyone help with some trouble shooting, I get the following error from the cx_ai_system_fault:
    Code: APPLICATIONCALL.OUTBOUNDFRAMEWORK
    Errortext: Internal error in outbound framework (error ID BUSINESS_SYSTEM  )
    Thanks,
    Leanne

    Hi Leanne
    Which system are you invoking Outbound proxy from? Did you define that system in SLD? If you trying to use a different R/3 or B/w as backend system please make sure you have the following steps done -
    1. fullfil OSS Note 439915
    2. In integration admin -> add an entry for sending / reciving system under category RUNTIME under configuration
    3. Maintain logon parameters for backend system in SPROXSET.
    Is this outbound or inbound proxy you are getting error with
    Cheers..
    Vasu
    <i>** Reward Points if found useful **</i>

  • PARSE_APPLICATION_DATA error in Delins Idoc

    Hi trying to send an Idoc Delins from R/3 backend system to SUS system
    getting error in SUS system the error is 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>XIProxy</SAP:Category>
    <SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
    <SAP:P1 />
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>Error during XML => ABAP conversion (; error ID: ; ( ))
    PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Request
    Message; error ID: CX_ST_REF_ACCESS; (/1SAI/TXS00000000000000000004 XML
    Bytepos.: 2041 XML Path: ns0:PurchaseOrderRequest(1)PurchaseOrder(2)Item(10)PurchasingContractReference(4)ItemID(2) Error Text: Error accessing
    the ref. node 'ITEM_ID')) Error during XML => ABAP conversion (Request
    Message; error ID: CX_ST_REF_ACCESS; (/1SAI/TXS00000000000000000004 XML
    Bytepos.: 2041 XML Path: ns0:PurchaseOrderRequest(1)PurchaseOrder(2)Item(10)PurchasingContractReference(4)ItemID(2) Error Text: Error accessing
    the ref. node 'ITEM_ID')) Error accessing the ref.
    node 'ITEM_ID'</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    I have applied the note number 980867 but still no change in the result.
    Regards,
    Anand

    Hi Anand,
    could be an issue with the XI Content and the mapping not being up2date.
    I would check with the XI colleague, if the settings and the content is ok.
    Thanks,
    Claudia

  • PARSE_APPLICATION_DATA Error during XML - NFe2

    Pessoal, bom dia.
    Estou em um projeto de NFe 2.0
    O cenário  ABAP conversion (Response Message; error ID: CX_ST_MATCH_ELEMENT; (/1SAI/TXS4DFEC4071863FF72A429 XML Bytepos.: 0 XML Path: Error Text: Elem.'nfeStatusServicoNFResponse2' esperado))
    Alguem já passou por isto? Ou pode me ajudar?
    Obrigado.

    XML passado para SEFAZ-MG:
    <?xml version="1.0" encoding="utf-8" ?>
    - <n0:nfeStatusServicoNF2 xmlns:n0="http://sap.com/xi/NFE/006" xmlns:prx="urn:sap.com:proxy:XID:/1SAI/TAS4DFEC4071863FF72A429:700:2008/01/11">
      <n0:cUF>31</n0:cUF>
      <n0:tpEmis>1</n0:tpEmis>
      <n0:tpAmb>2</n0:tpAmb>
    - <n0:nfeDadosMsg>
    - <n1:consStatServ versao="2.00" xmlns:n1="http://www.portalfiscal.inf.br/nfe">
      <n1:tpAmb>2</n1:tpAmb>
      <n1:cUF>31</n1:cUF>
      <n1:xServ>STATUS</n1:xServ>
      </n1:consStatServ>
      </n0:nfeDadosMsg>
      </n0:nfeStatusServicoNF2>
    Retorno da SEFAZ:
    The XML page cannot be displayed
    Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
    Invalid at the top level of the document. Error processing resource 'file:///D:/Documents and Settings/BHX10108/Configuraçõ...
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Inbound Message -->
    Atenciosamente,
    Al.

  • SCAN não retorna status do serviço

    Bom dia,
    Desde 14/08/2011 às 08:05:56 o nosso tipo de emissão SCAN não está retornando STATUS de ativo, e também não é realizada a consulta do status do mesmo.
    Dei uma olhada no GRC/PI/Java/ECC... e aparentemente está tudo ok
    Quando o SCAN parou pela primeira vez, deu o seguinte erro:
    PARSE_APPLICATION_DATA Error during XML => ABAP conversion: Response Message; CX_ST_MATCH_ELEMENT in /1SAI/TXS2731B33DE5F5A8813C20 Line 268 Elem.'nfeStatusServicoNFResponse2' esperado
    Pesquisando sobre o erro, achamos 2 trheads:
    http://forums.sdn.sap.com/click.jspa?searchID=73768752&messageID=10193658
    http://forums.sdn.sap.com/click.jspa?searchID=73768752&messageID=10151927
    Elas sugerem a aplicação das notas abaixo:
    1501345 - Xi runtime: Manifest
    1522630 - Xi runtime: Payload ignored due to parsing error
    1162160 - CX_ST_MATCH_ELEMENT in XML Inbound processeing
    Inclusive um dos usuários comenta que após aplicada a 1522630 o problema foi resolvido... (Mas não sei se isso irá funcionar)
    Outro check que realizei foi do erro retornado no status do serviço do SCAN agora, e o GRC retorna o seguinte erro:
    MAPPING.JCO_COMMUNICATION_FAILURE "COMMUNICATION FAILURE" during JCo call. Error when opening an RFC connection
    Pesquisando sobre o erro, encontrei algumas sugestões:
    1) Alguns sugerem a exclusão da conexão RFC AI_RUNTIME_JCOSERVER para TCP/IP (SM59) no GRC e criar novamente... mas não sei se isso iria funcionar...
    2) Em outras pesquisas, alguns falam que a Conexão entre ABAP e JAVA foi quebrada... isso é a razão para o erro JCO_COMMUNICATION... e a sugestão é reiniciar o Java...
    3) Em outra pesquisa: Quando há muitas mensagens a serem processadas simultaneamente. O número padrão de processos paralelos em VisualAdmin -> JCO Provider RFC ->  AI_RUNTIME_) e ver se isso ajuda.
    Obs.: À alguns dias, tivemos um problema que ocorreu com a SEFAZ-GO, a mesma colocou nossa faixa de IP's em uma Blacklist (ainda não sabemos porque) e daí ela nos retornava que estava "fora do ar". Será que poderia ser isso? Como posso checar isso?
    O nosso S.P. é o:
    SLL-NFE     100     0018     SAPK-10018INSLLNFE     xNFE 1.0
    Alguém poderia nos auxiliar? Pois isso não gera impacto em nossos processos desde que a SEFAZ (GO/PR/SP/MT) não fique inativa, pois caso isso ocorra o nosso processo de emissão de NF-e em SCAN não irá funcionar e a emissão de NF-e irá parar.
    Qualquer dúvida estou à disposição.
    Edited by: MATEUS PARREIRA GUIMARÃES on Sep 1, 2011 7:12 PM
    Edited by: Fernando Ros on Sep 2, 2011 10:24 PM - trocado code por quote para melhor visualizaçã

    Boa tarde a todos!
    Pessoal incluindo mais informações as já enviadas pelo Mateus; quando fazemos um check pela SXI_monitor esta
    retornando sempre o mesmo retorno:
    Qualquer dica ou nota agradecemos,
    Pamplona
    CENTRAL
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>SystemError</SAP:MessageClass>
      <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
      <SAP:MessageId>8AB8CC05-D44B-11E0-8D74-000000729692</SAP:MessageId>
      <SAP:RefToMessageId>E0D44B74-1BE5-7BF1-975B-0024E8437829</SAP:RefToMessageId>
      <SAP:TimeSent>2011-09-01T03:36:13Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">SEFAZ_2_SCAN</SAP:Party>
      <SAP:Service>Producao</SAP:Service>
      <SAP:Interface namespace="http://sap.com/xi/NFE/006">SRVSC_nfeStatusServicoNFSoapIn_SYNC_IB</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
      <SAP:Service>GRPCLNT200</SAP:Service>
      <SAP:Interface namespace="http://sap.com/xi/NFE/006">SRVSC_nfeStatusServicoNF_SYNC_OB</SAP:Interface>
      </SAP:Receiver>
      <SAP:Interface namespace="http://sap.com/xi/NFE/006">SRVSC_nfeStatusServicoNFSoapIn_SYNC_IB</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemErrorAckRequested="true" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>BestEffort</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTPEXCEPTION - HTTP 403 Forbidden----

  • Lote com status  02 - Enviado ao PI

    Boa Tarde,
    Estamos com 3 lotes que apresentaram o seguinte Status - 02 Enviado ao PI, e não consigo liberá-los para envio para a SEFAZ.
    O erro apresentado no SXI_MONITOR é o seguinte:
    <?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/TXS93D66C51A914A80B8BD3</SAP:P3>
      <SAP:P4>XML Bytepos.: 705 XML Path: ns1:nfeRecepcaoLoteResponse(1)ns1:nfeRecepcaoLoteResult(1)ns2:retEnviNFe(1)ns2:xMotivo(4) Error Text: Ocorreu um perda de dados durante a conversão de Rejeição: Erro não catalogado - Could not allocate space for object 'dbo.NFe_Fila'.'PK_NFe_Fila_1' in database 'NFe_In' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additi. Kernel ErrorId: CONVT_DATA_LOSS</SAP:P4>
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Fehler bei der Konvertierung XML => ABAP (Request Message; FehlerId: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXS93D66C51A914A80B8BD3 XML Bytepos.: 705 XML Path: ns1:nfeRecepcaoLoteResponse(1)ns1:nfeRecepcaoLoteResult(1)ns2:retEnviNFe(1)ns2:xMotivo(4) Error Text: Ocorreu um perda de dados durante a conversão de Rejeição: Erro não catalogado - Could not allocate space for object 'dbo.NF ) ) Ocorreu um erro na deserialização em o programa ST /1SAI/TXS93D66C51A914A80B8BD3. Ocorreu um perda de dados durante a conversão de Rejeição: Erro não catalogado - Could not allocate space for object 'dbo.NFe_Fila'.'PK_NFe_Fila_1' in database 'NFe_In' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additi.</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Mas não consigo reestartar a mensagem.
    Alguém saberia como solucionar este problema?
    Obrigado
    Migdon Silva

    Bom dia Migdon,
    O erro de banco de dados aconteceu na Sefaz SP no dia de hoje, este erro CX_ST_DESERIALIZATION_ERROR aconteceu no proxy do PI para o ABAP devido à descrição do erro no campo xMotivo excedeu o tamanho máximo definido no esquema XML (255 caracteres).
    Como é comum das Secretarias estrapolarem este limite nos erros tipo 999, o GRC foi modificado para truncar este valor e eliminar o problema de proxy através da SAP Note 1319911 (SP09).
    Para resolver o incidente, você deverá acrescentar linhas falsas na tabela de histórico de lote (/xnfe/bat_hist), conforme xemplo:
       BATCHID      = <seu lote>
       ERTIME       = <current time stamp with format YYYYMMDDHHMISE,99999>
                          Ex.:20090522160000,9999999  --> um bom valor de ERTIME é
    pegar o maior atual para o lote e acrescentar 1 segundo.
       BATSTAT      = 02                                                   
       ERROR_STATUS = 01    "General error                                 
    Após acrescentar esta linha você pode ir no GRC Web Monitor e fazer o restart do lote, que será enviado normalmente.
    Atenciosamente, Fernando Da Rós
    Edited by: Fernando Da Ros on May 22, 2009 9:05 PM

  • XI to Bw error

    Hi Gurus,
      I am getting following error message when the data is been sent XI to BW system.
    TCODE: SXMB_MONI
    Error during XML => ABAP conversion (; error ID: ; ( )) PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXS00000000000000000018 XML Bytepos.: 56906 XML Path: ns1:_-BI0_-QI6AZXML_DELAY_001_RFC(1)DATA(2)item(31)_-BIC_-ZSTPBUILD(27) Error Text: Data loss occurred when converting INVALID,INVALIDTH
    Can anybody help me to sort this error or give some idea whats this  error about?

    Rajan,
    Go through this links where they might help you to resolve your issue:
    BW in XI
    Process Integration (PI) & SOA Middleware
    /people/kamaljeet.kharbanda/blog/2005/09/16/xi-bi-integration
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21d8aa90-0201-0010-5e83-a3798b9a5ee0
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8c10aa90-0201-0010-98a0-f071394bc9ae
    Also can you tell us which scenario you are trying to do?
    ---Satish

  • Handling of SOAP Faults in SOAP Clients consuming PI Web services

    Hi there,
    the following is in regards to SOAP fault error handling in a SOAP client that consumes a Web Service published by PI.
    I have been reading a number of threads and blogs in regards to this topic and I am still left with some open questions which I hope to get some final answersclarifications through this thread.
    In particular the blogs
    Handling Web Service SOAP Fault Responses in SAP NetWeaver XI      - Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
    XI: Propagation of meaningful error information to SOAP Client     - XI: Propagation of meaningful error information to SOAP Client
    have caused by attention.
    Both of these threads are realating to the Fault Message type one can use to return errors back to a SOAP Client (.Net, Java, etc.).
    In our scenario we published a number of Web Services through PI that provide functionality to integrate with an R3 back-end system using inbound ABAP Proxies.
    The services are standardised and will be consumed by a number of .NetJava applications and systems. The reason for the use of ABAP proxies is the customer specific application logic that is executed in the backend system. The Web services are synchronous and don't use ccBPM in the middle. Transformations are performed in PI combined with various lookups to set default values before the message is passed into the ABAP Framework of the R3 back-end system. The lookups are done against the R3 back-end system using the PI RFC Lookup feature.
    The inbound proxies currently return application errors as part of the response message back to the SOAP client. For more critical errors we introduced the use of Fault message types as the method to return the information back to the SOAP Client. This is all working satisfactory.
    The questions I have are as follows.
    1. When an error occurs at the IE level (e.g. mapping error), ABAP Proxy framework level (e.g. conversion from XML to ABAP format) or Adapter Framework level (Adapter releated error) a different SOAP fault message structure is returned to the SOAP Client than the one    used for the application errors. The SOAP fault message structure used in this case is the standard SOAP fault used by PI to return system errors back to the caller. For those SOAP fault messages there is no payload generated that could be mapped to the SOAP fault structure used for the application errors. This would be preferrable as there would be only one Fault message structure used for both inbound ABAP proxy generated fault messages and PI generated fault messages.
    Also the error messages generated by PI can be quite cryptic and difficult to interpret at the client end and could be filtered     ranslated during message mapping if the payload of the PI generated SOAP fault message could be accessed in a message mapping.
    Point 3 of the above thread 2759 indicates that this would be possible but doesn't outline how. Could somebody please clarify this for me as I don't believe that this is really possible ???.
    My idea instead was to use the PI SOAP fault message structure to also return application errors. Therefore I would create a Fault message type that matches the PI SOAP fault structure. This would enable the SOAP Client to handle only one SOAP Fault error structure. Would that be something to look into instead ?????.
    2. We have been looking at using the integrated WEB AS SOAP adapter instead of using the AF Sender SOAP adapter. While playing with this we encountered differences in the content returned through the SOAP fault generated by PI. A sample is below. Shouldn't the content of these SOAP faults be the same if the error that caused it is the same. Also the SOAP fault returned by the IE SOAP adapter is much more    useful in this particular case. Both errors below are the same, a conversion error from XML to ABAP took place in the inbound ABAP proxy framework of the back-end system.
    SOAP fault returned when using SOAP Sender adapter of AF
    <!see the documentation>
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
                   <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIProxy:PARSE_APPLICATION_DATA:
         at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
         at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:916)
         at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    SOAP fault using integrated SOAP adapter of PI IE
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>System Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context/>
                   <code>ABAP.PARSE_APPLICATION_DATA</code>
                   <text>Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXSBE20FF604BAFEF8D990A XML Bytepos.: 564  XML Path: ns1:CreatePORequest(1)POHEADER(2)COMP_CODE(1) Error Text: Data loss occurred when converting ############################## Kernel ErrorId: CONVT_DATA_LOSS))</text>
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    I have been reading threads for hours without being able to find one that answers questions 1 or provides a blog that outlines the approach one should take for error handling in SOAP clients that consume PI Web Services (and covers both PISystem generated faults and faults raised in Proxies).
    There may already be a blog or thread and I just missed it.
    Any comments are welcome.
    Thanks. Dieter

    Hi Dieter,
    As Bhavesh already mentioned fault messages are used for application errors. The same is described in SAP XI help:
    http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
    In case of system error (e.g. field length too long in proxy call or error in XI/PI mapping) there seems to be no standard way of handling it and propagating the response to the consumer of webservice.
    Each system error is not recognized by SOAP adapter and SOAP adapter exception is raised.
    The only bizzare solution that I can see is developing an adapter module and transport wrong message to standard fault message before delivering it to adapter engine:
    http://help.sap.com/saphelp_nw04/helpdata/en/a4/f13341771b4c0de10000000a1550b0/frameset.htm
    Kind regards,
    Wojciech
    btw nice thread

Maybe you are looking for