HTTP_XI_IDOC SCenario Error

Hi all,
I am getting the Error in SXMB_MONI as "Message has Error Status on outbound side".Till today morning it was working fine.Now what happened to it we could not found out.I am trying to publish data over HTTP as Aync comm.It is reaching to XI and showing black&white flag and not passing to R/3 and showing Red Flag at other end.Plz suggest us to resolve this problem today.
Your suggestion is higly appreciated.
Advance Thanks
SRidhar Raju Mahali

Hi Sridhar,
  Check if the RFC destination (between XI & R/3) is OK (uid/pwd expiry/change ,role change etc).
it would be better to analyse if you add the log with complete details
hope this fixes your issue
Regards
Vishnu

Similar Messages

  • Rfc to file scenario error in sm58

    rfc to file scenario error in sm58
    i get the error as com.sap.aii.afccommunication.RfcAfwException
    :look up of alternative

    hey
    >>i have a doubt do we have to use
    starting new task or back ground destination
    well it depends upon the logic ur gonna implement,both are used for async RFC so u have to see ur requirement and then decide.
    have a look at the following
    http://help.sap.com/saphelp_nw2004s/helpdata/en/22/042578488911d189490000e829fbbd/frameset.htm
    thanx
    ahmad

  • IDOC-XI-FILE Scenario: Error in ABAP Mapping

    Dear All,
    I am working on IDOC-XI-Flat FIle scenario in which I am using ABAP Mapping as per document "How To Convert an IDoc-XML
    structure to a flat file and vice versa in XI 3.0".
    I created one customized Idoc for this. The Idoc is reacing XI but its flat file is not getting created. Its giving me following error:
    <SAP:Stack>Error in mapping program Z_ABAP_MAPPING_PACKING_LIST (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    I have also gone thru threads posted for the same topic earlier but still I am not been to resolve this error.
    Please help me out in resolving this error.
    Regards,
    N.Jain

    HI,
       Log saying that, u have problem in the mapping program.
      i.e Z_ABAP_MAPPING_PACKING_LIST
       the problem is due declaration of data.
       i hope that, you have some methods.
       those are declared under intialization section in mapping program.
      please use start of selection before the method.
    other wise, it will come under intilization section.
    warm regards
    mahesh.

  • MM-SUS Scenario---Error while posting the PO in SUS System from R/3 system.

    Hi All,
    An error occurred within an XI interface: Exception occurred:BBP_PD:004 -Partner 0000003000 not found E:BBP_PD:147 -Enter a country for partner 0000003000 with type 'Sold-to Party' Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57
    The above is problem occurred in SUS system. I have checked the message SXMb_MONI Tcode for XML message.
    Can any one suggest what could be the problem and the solution for the same.
    we are working on MM-SUS scenario (Plan Driven Procurement).
    Thanks
    Jagan

    Hi
    <b>Please go through the links below -></b>
    purchase order doesn't create in srm sus
    purchase order not create in sus
    Enter a country for partner with type 'Sold-to Party'
    BBP_BUPA_SUPPLIER:101
    Unable to determine logical system of sender
    Help MM-SUS!
    SUS-MM:PO not transferred to SUS--message:'sold to party'
    Error in SUS PO creation
    Re: PO error in SUS-MM Scenario
    Cancellation from SUS hangs in XI interface
    Regards
    - Atul

  • Error while transfering PO in extended Scenario -- error 06 053 in R/3

    Hi,
    while transfering a PO from SRM to R/3 in extended Scenario we get an error in RZ20(SRM):
    "No selectable items exist for purchase requisition xxx" --> error number 06 053
    Whats happening here?
    The PR is released in R/3 and yet not transfered into another PO.
    Material and Material Group are the same, there is no contract involved and no differences within PO to PR.
    Any ideas how to solve this problem?
    Thanks and best regards
    Andreas

    Hi muthu,
    thanks, that seems not to be the problem.
    By using the fbgendat report in backend I found out, that R/3 seems to interprete my SRM PO as a local PO?!
    Might there be a problem in SRM when calling the function module BBP_PO_BAPI_STATE within method set_po_bapi_state_in_be  (class CL_BBP_BS_ADAPTER_PO_CRT)?
    Seems R/3 does not interprete my PO out of SRM as a SRM PO?
    Does the RFC User needs additional roles for setting the BAPI_PO_STATE in R/3? (the RFC User does not have sap_all in R/3!)
    Best regards
    Andreas

  • Standalone Scenario - Error during Creation of Local Purchase Order

    Hi All,
         I am trying to setup Standalone Scenario, i have created all the master data locally, i am able to Order SC, but after workflow approval SC goes into error 'Error during creation of local purchase order from shopping cart XXXXXXXXX'
         I have created following configuration setting for local PO number
    1) In SPRO -> Cross-Application Basic Settings -> Number Ranges -> Define Number rang. for Schopping Carts and Follow-on Doc. --- i have number ranges for PO follow-on doc. i.e.
    inrerval No = PO, from number = 0004000000, to number = 0004999999, ext. = unchecked
    2) In SPRO -> Cross-Application Basic Settings -> Number Ranges -> Define Ranges per backend system for follow-on documents PO, PR etc
    3) In sourcing (SPRO -> Cross-Application Basic Settings -> Sourcing -> Define Interactive Sourcing for product categories) ---  sourcing is never carried out.
    Can anybody help?
    Regards,
    SAP Guy.
    Edited by: SAP Guy on Apr 23, 2008 2:32 AM

    Hi SAP Guy,
    Following steps are must for Local number range
    1) Create number range for local PO
    2) Maintain your logical system in 'Define number range per backend system for follow on document'
    3) Define Transaction Type for BUS2201, define document type (e.g. EC1)
    4) Assign Document type (EC1) in Org attribute BSA.
    Hope this helps.
    Regards,
    Manish.

  • R/3(MM) -XI- SUS Scenario Error

    Hello,
    I'm working on SRM Integration: R/3(MM) to SUS Scenario
    Whenever i post a PO message to SUS from R/3 (MM module), I see the following error in SXMB_MONI:
    ERROR:
    <?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/SRM/Basis/Global">StandardMessageFault</SAP:ApplicationFaultMessage><SAP:Stack>The application triggered an exception
    </SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>
    TRACE:
    "An error occured within an XI interface: SLD system SNT_BS is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line:92 "
    Can anyone help me resolve this problem ?
    Thanks,
    Regards,
    Sridhar

    Hi,
    Thanks for the reply Vishnu. No i didn't create those OSS messages
    I just now found the reason and resolved the problem.
    Let me describe the reason for the problem:
    In the SRM box, values for the "System Landscape Directory Names" (Business System Names) in the "Definition of backend systems in B2B" were not entered.
    Txn : SPRO
    SAP Reference IMG> Supplier Relationship Manager>Supplier Self Services>Technical Settings>Define Backend Systems.
    Regards,
    Sridhar

  • Sender RFC Scenario Error:Payload Is Missing

    I am facing an issue in 'RFC2JDBC' scenario which is mentioned below:
    here our scenario is 'RFC2JDBC'.here our 'RFC' is having 2 fields in tables parameter
    i.e. empno & empname.
    the results of the 'RFC' is coming as:
    Personnel Number  Employee Name
    00000100                 Rasmiraj
    00000200                 Tanmay
    00000300                 Kanhu
    00000400                Debabrata
    00000500                shantanu
    i am triggering the 'rtfc' through a program.
    when i am triggering the 'RFC',in monitor of PI it's coming as sucessful.however in the payload one of the field value is missing i.e. employee name.(same also updating in the legacy database)
    in the payload it's appearing as:
    [  <?xml version="1.0" encoding="UTF-8" ?>
    - <rfc:ZSAM_SEND_RFC_PI xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
    - <EMP_DTLS>
    - <item>
      <EMPNO>00000100</EMPNO>
      <EMPNAME />
      </item>
    - <item>
      <EMPNO>00000200</EMPNO>
      <EMPNAME />
      </item>
    - <item>
      <EMPNO>00000300</EMPNO>
      <EMPNAME />
      </item>
    - <item>
      <EMPNO>00000400</EMPNO>
      <EMPNAME>a</EMPNAME>
      </item>
    - <item>
      <EMPNO>00000500</EMPNO>
      <EMPNAME />
      </item>
      </EMP_DTLS>
      </rfc:ZSAM_SEND_RFC_PI> ]
    please,suggest.(here,we are using sender 'RFC' communication channel & an 'RFC'destination of type 'T'(with parameter registered server program,gateway host,gateway service)

    Hi rasmiraj tripathy,
    I am also facing the same problem (Sender or Payload is missing) while integrating R3 to B1 using IDOC. When I resend IDOC, it capture by B1iSN but doesn't work, it gives me error. When I look into xml document, it is found that there is no receiver payload.
    My R3 system is non-unicode and it is difficult to change it to unicode as it requires updation.
    Can you please confirm that this error is coming due to Non-Unicode, and can be resolved by setting it to Unicode.
    Note: There is no double definition of any object.

  • IDOC to SOAP asynchronous scenario Error handling

    Need an expert!!!!!!!!! advise on  error handling for IDOC--PI--
    SOAP scenario.This is a asynchronous scenario where PI is calling a Legacy system using SOAP adapter.My question is how i can do error handling in this scenario.If i get an alert in pi with payload variable that would be fine, do i need to use BPM and if that is tthe case what will be steps.
    Appreciate your help.
    Manish

    Hello Manish,
    My question is how i can do error handling in this scenario.
    Use the standard alert framework. Search on SDN / SAP Help for details.
    do i need to use BPM and if that is tthe case what will be steps.
    BPM is not required to raise alerts, as this is an async call.
    Regards,
    Neetesh

  • Idoc to file scenario error

    Hell Experts,
    I have done desgin and configuration from Idoc to File Scenario in XI Intergration server.
    Source is R/3 and Target system is File. I have successfully configured each and every step. Send Idoc from R/3 to Intergration server and run sxi_cache. But  I didn't get successful results, always the error message shows in SXMB_MONI as follows:
    Ackn Status  contains system error
    During the application mapping com/sap/xi/tf/_CUST_MMAP_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeExcep
    tion in Message-Mapping transformatio~
    Exception of class CX_XMS_SYSERR_MAPPING
    My system Patche level as follows:
    SAP_BASIS     640        0012        SAPKB64012
    SAP_ABA     640     0012                SAPKA64012
    PI_BASIS     2004_1_640 0009        SAPKIPYI69
    SAP_BW     350     0009                SAPKW35009
    The above error is related to patches problems or any Mapping  problems ?
    Please  help me.
    Advanced Thanks.
    Regards,
    Chandra

    Hi,
      This may be a mapping issue, try this:
    a)in interface mapping see if grids are formed at source and target after executing the test option,
    b)also take the xml of the idoc from sxmb_moni , copy it and paste it at the source of the mapping ( use the src tab now) and execute the mapping, is your file structute formed?
    i am not sure of the patch levels.
    Regards,
    Anirban.

  • File to IDOC scenario error...

    Hi all,
    we hhave created an File to Idoc scenario .
    we are getting the following error in SXMB_MONI t-code.
    <?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>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1>BUS_SENDER</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert sender service BUS_SENDER to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    can any one plz say wat this error might be..
    TIA
    Regards,
    Raj

    Hi,
    The problem occurs when sender and receiver business system or business service does not have a logical system name.
    ID - Integration Directory
    Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
    If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
    If business system type = Third-Party, then add the logical system in business system level and Save.
    If the business service does not have the logical system name in ID, it needs to be configured as follows.
    Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
    Apply and activate.
    hope this will help you.
    regards
    Aashish Sinha
    PS : reward points if helpful

  • IDoc to File Scenario Error ( IS - Retail )

    Hi all ,
    I was trying scenario IDoc (SAP ECC 6.0) (IS-Retail) to File scenario .
    When i trigerred IDoc from ECC system , it's showing sent successfully to external system or program.
    But the problem is it's not coming inside XI sxmb_moni .
    I have checked the ALE Configuration and SLD configuration .
    Everything is fine.
    When i run the TCODE WE05 for IDocs List in XI , it's getting stucked there and the Error showing is
    "IDoc: 0000000000000028 Status: IDoc with errors added
    External segment name E2WBB01003 cannot be interpreted "
    Even i tried with other IDoc WPDWGR it is showing the same error
    "IDoc: 0000000000000029 Status: IDoc with errors added
    External segment name E2WPW01 cannot be interpreted"

    Hi Ashwin,
    Please check :
    1.The SAP system from which you want to import the  IDocs contains function modules for calling metadata.
    2.You can import IDocs from SAP Release 4.0 and higher.Support Packages Required for IDoc Imports:
    Release    Minimum  Support Package Requirement
    40B                   SAPKH40B48
    45B                   SAPKH45B26
    46A                   SAPKB46A20
    46B                   SAPKB46B12
    46C                   SAPKB46C05
    3.check for the authorizations required to import.
    Also see SAP Notes 677732 (authorizations), 672745 (missing function modules), 212011 (access to IDoc metadata), and 718320.
    check http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
    *Pls: Reward points if helpful*
    Regards,
    Jyoti

  • IDOC to JDBC Scenario error

    Hi All,
    I am doing a IDOC to JDBC Scenario.I am done with IR and ID.
    The Table in the DB is TABLE1 with Field1 and Field2.
    Now when I run thescenario it throws an error ,
    2009-03-19 12:41:06 Success INSERT INTO  TABLE1 (Field1, Field2) VALUES (KM247850, FINJTIA)
    2009-03-19 12:41:06 Error Unable to execute statement for table or stored procedure. 'TABLE1' (Structure 'Statement') due to java.sql.SQLException: [EUDNT038]The name "KM247850" is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted.
    But it has successfully generated the SQL Query which I think is perfect.
    But whats the error which follows that?
    How do I resolve it?
    Thanks,
    Venu

    Hi,
    It could be due to wrong structure of JDBC, compare your target structure with this blog..
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
    Regards,
    Sarvesh

  • IDOC---JDBC scenario error: "INTERNAL" HTTP_RESP_STATUS_CODE_NOT_OK

    i have a IDOC-XI--JDBC   scenario,
    the scenario fails at  the Call Adpater Pipeline step............giving following error:
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>401</SAP:P1>
      <SAP:P2>Unauthorized</SAP:P2>
    <SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Authorization error when sending using HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
    pls help me.....
    Message was edited by:
            sudeep dhar

    but this error occurs after few message pass successfully.....
    means at an interval this error happens...then again few messgae pass successfully,
    This is the error which i get in MONI:
    ERROR_CATEGORY: INTERNAL
    ERROR_ID: HTTP_RESP_STATUS_CODE_NOT_OK
    and in the pipeline step i can see the error:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>401</SAP:P1>
      <SAP:P2>Unauthorized</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      </SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Authorization error when sending using HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

  • Seeburger IDOC-to-File scenario: Error using Classifier module

    Hello,
    I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
    In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
    localejbs/SeeClassifier        classifier
    localejbs/CallBicXIRaBean      bic
    CallSapAdapter                 0
    classifier   attID             classifierAtt
    classifier   destSourceMsg     MainDocument
    classifier   showInAuditLog    true
    bic          classifierAttID   classifierAtt
    bic          destEncoding      UTF8
    bic          destSourceMsg     MainDocument
    bic          destTargetMsg     MainDocument
    bic          mappingName       AUTO
    bic          newLine           true
    bic          srcEncoding       UTF8
    After conversion in XI, the file fails to write to the folder because of this error:
    Message processing failed. Cause: javax.resource.ResourceException: ---
    Conversion of synchronous request from module chain ended with errors
    ---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
    See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
    Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
    BICMapping Error: The mapping [not specified] you are trying to load cannot
    be found in the right path! Maybe you forgot to compile or to activate the
    mapping!
    When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine.  But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
    I am only facing this problem for the IDOC-to-File scenario.  Somehow the same configuration works for a File-to-IDOC scenario.
    I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be.  Has anyone encountered this problem before?
    Any suggestions would be appreciated.
    Thanks,
    Arianne

    Hi Yomesh,
    Here is the payload.
    <?xml version="1.0" encoding="UTF-8"?>
    <LIST>
      <S_ISA>
        <D_I01>00</D_I01>
        <D_I02/>
        <D_I03>00</D_I03>
        <D_I04/>
        <D_I05>ZZ</D_I05>
        <D_I06>CELORGS01</D_I06>
        <D_I05_2>ZZ</D_I05_2>
        <D_I07>AVX</D_I07>
        <D_I08>032008</D_I08>
        <D_I09>1718</D_I09>
        <D_I10>X</D_I10>
        <D_I11>00401</D_I11>
        <D_I12>000000008</D_I12>
        <D_I13>0</D_I13>
        <D_I14>T</D_I14>
        <D_I15>^</D_I15>
        <S_GS>
          <D_479>PO</D_479>
          <D_142>CLS01</D_142>
          <D_124>058895921</D_124>
          <D_373>20080320</D_373>
          <D_337>1718</D_337>
          <D_28>8</D_28>
          <D_455>X</D_455>
          <D_480>004010</D_480>
          <S_ST>
            <D_143>850</D_143>
            <D_329>800001</D_329>
            <S_BEG>
              <D_353>00</D_353>
              <D_92>SA</D_92>
              <D_324>4500005037</D_324>
              <D_373>20051110</D_373>
            </S_BEG>
            <S_CUR>
              <D_98>BY</D_98>
              <D_100>USD</D_100>
            </S_CUR>
            <S_FOB>
              <D_146>CC</D_146>
              <D_309>OR</D_309>
              <D_352>FREE CARRIER</D_352>
              <D_334>02</D_334>
              <D_335>FOB</D_335>
              <D_309_2>DE</D_309_2>
            </S_FOB>
            <S_ITD>
              <D_336>01</D_336>
              <D_333>3</D_333>
              <D_351>45</D_351>
            </S_ITD>
            <G_SN9>
              <S_N9>
                <D_128>L1</D_128>
                <D_369>GEN</D_369>
                <S_MSG>
                  <D_933>TEST</D_933>
                </S_MSG>
                <S_MSG>
                  <D_933>MESSAGE</D_933>
                </S_MSG>
              </S_N9>
            </G_SN9>
            <G_SN1>
              <S_N1>
                <D_98>BY</D_98>
                <D_66>92</D_66>
                <D_67>6310</D_67>
                <S_PER>
                  <D_366>BD</D_366>
                  <D_93>Graham Crawford</D_93>
                </S_PER>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>BT</D_98>
                <D_66>92</D_66>
                <D_67>6310</D_67>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>SE</D_98>
                <D_93>3M COMPANY</D_93>
                <D_66>92</D_66>
                <D_67>0000019591</D_67>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>ST</D_98>
                <D_93>SAMPLE</D_93>
                <D_66>92</D_66>
                <D_67>6310</D_67>
              </S_N1>
            </G_SN1>
            <G_SPO1>
              <S_PO1>
                <D_350>00010</D_350>
                <D_330>10.000</D_330>
                <D_355>EA</D_355>
                <D_212>10</D_212>
                <D_639>PE</D_639>
                <D_235>BP</D_235>
                <D_234>230-1812-01JDS</D_234>
                <D_235_2>EC</D_235_2>
                <D_234_2>A00000000000002</D_234_2>
                <G_SPID>
                  <S_PID>
                    <D_349>F</D_349>
                    <D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
                  </S_PID>
                </G_SPID>
                <S_REF>
                  <D_128>CO</D_128>
                  <D_127>4500005037-00010</D_127>
                </S_REF>
                <G_SSCH>
                  <S_SCH>
                    <D_380>10.000</D_380>
                    <D_355>EA</D_355>
                    <D_374>002</D_374>
                    <D_373>20051208</D_373>
                  </S_SCH>
                </G_SSCH>
              </S_PO1>
            </G_SPO1>
            <G_SCTT>
              <S_CTT>
                <D_354>1</D_354>
              </S_CTT>
            </G_SCTT>
            <S_SE>
              <D_96/>
              <D_329>800001</D_329>
            </S_SE>
          </S_ST>
          <S_GE>
            <D_97>1</D_97>
            <D_28>8</D_28>
          </S_GE>
        </S_GS>
        <S_IEA>
          <D_I16>1</D_I16>
          <D_I12>000000008</D_I12>
        </S_IEA>
      </S_ISA>
    </LIST>
    Thanks,
    Arianne

Maybe you are looking for