JMS content conversion issue

Hi ,
I am facing issue in JMS content conversion
my file looks like as below...
field1¤field2¤
field1¤field2¤
field1¤field2¤
field1¤field2¤
in module i have used this
AF_Modules/MessageTransformBean   PLAIN2XML
Transform.Class                com.sap.aii.messaging.adapter.Conversion
Transform.ContentType     text/xml;charset=utf-8
xml.conversionType           SimplePlain2XML
xml.documentName            MT_data  
xml.documentNamespace  http://xyz.com    
xml.fieldNames                   field1,field2
xml.fieldSeparator              ¤
xml.processFieldNames     fromConfiguration
xml.structureTitle                records
but i am getting following error
Error occurred while processing message: . Detailed error (if any):  com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Transformer Conversion3.0.5226 Error initializing Class: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: (4408) Parameter xml.fieldFixedLengths or xml.fieldSeparator is missing (4409) Consistency check: no. of arguments in xml.fieldFixedLength does not match xml.fieldNames (0 <> 2) : TransformException: Transformer Conversion3.0.5226 Error initializing Class: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: (4408) Parameter 'xml.fieldFixedLengths' or 'xml.fieldSeparator' is missing (4409) Consistency check: no. of arguments in 'xml.fieldFixedLength' does not match 'xml.fieldNames' (0 <> 2)
ironically when i use file adapter, its reading the file properly and converting XML as expected?
Did anyone face this issue.....
is this issue because of an extra ¤ .. is so... why its not giving issue with File??

You need an additional hierarchy level:
root
-> row
  -> data
In your example:
<?xml version="1.0" ?>
<ns1:HQ_reply_MT xmlns:ns1="urn:abc.com:HQToSAP">
<b><row></b>
<Data1> PIPXSDI3070 00000 00342YSDI3070PROCESS_MQSERIES HQXPLOR10 XPLOR.ORDER.RESULTS 0000 000000000000000086312 Invalid Process flag : 2. 065</Data1>
<b></row></b>
</ns1:HQ_reply_MT>
Regards
Stefan

Similar Messages

  • JMS Content Conversion with spaces

    Hi
    I am using the JMS Content Conversion to transalte MQ messages ( they come from the Mainframe ),to XML Format.
    These messages are in fixed lenghts structure , the fields contain blanks (spaces)
    The adapter cannot deal with it,only fixed lenghts without spaces , the monitor gives the following error
    XI inbound processing failed for message at 2006-08-24|07:45:25.518+0200. JMS and XI identifiers for message are ID:414d51204445564d41494e31202020207aabe04420c2ea13 and bd95c760-3333-11db-b915-001125a56002 respectively. JMS adapter will rollback database and JMS session transactions
    Have some1 dealed with this issue? managed to solve it?
    Thx,Shai

    Hi Shai.
    Before you call him ,try to use the simple convertion in the sender JMS comm. channel,then after you got the first XML structure to the XI ,use a simple\advanced java function from the message mapping and get rid of the spaces if they bother you.
    Can you post the fixed width message you get from JMS I'd like to have a look.
    By the way ,how did you resolve the File content convertion with 4 levels?
    Regarding Yaki's phone...well I'm sure your Boss have it.
    8-)
    Again ,good luck.
    Nimrod
    Message was edited by: Nimrod Gisis

  • JMS content conversion adapter module

    Hi All,
    In JMS Content conversion module Xml2Plain how do u put two new lines 'nl'.
    I am using localejbs/AF_Modules/MessageTransformBean in adapter module.
    If I put xml.record.fieldSeparator in parameter name and in parameter value if I put one 'nl' it gives me one new line. Now I require two new lines in my output text so I put 'nl' 'nl' in parameter value but it takes only one new line.
    e.g
    Vivek
    mumbai
    India
    John
    Delhi
    India
    Now I want the output as:
    Vivek
    mumbai
    India
    John
    Delhi
    India
    Thanks in advance.
    ravijeet

    try,
    xml.record.fieldSeparator '0x0D''0x0D'
    or
    xml.record.fieldSeparator '0x0A''0x0A'

  • Sender JMS content conversion

    Hi
       In the sender JMS content conversion, I do not want Recordset name hence I specified,
    Parameter Name: xml.ignoreRecordsetName
    Parameter Value: true
    But am still getting the Recordset name in the payload...
    Is this working for someone or a bug?
    Thanks in advance!
    Amulya

    >
    Amulya Lewis wrote:
    > Hi
    >
    >    In the sender JMS content conversion, I do not want Recordset name hence I specified,
    > Parameter Name: xml.ignoreRecordsetName
    > Parameter Value: true
    > But am still getting the Recordset name in the payload...
    > Is this working for someone or a bug?
    >
    > Thanks in advance!
    > Amulya
    when using the MessageTransformBean do note that xml.ignoreRecordsetName does not work

  • Testing JMS content conversion

    Hi Experts,
    I have a scenario MQ-->PI--ECC.
    MQ sends a flat file and there is JMS content conversion used in sender JMS channel. On MQ side channels are not yet setup. Now I need to test if JMS content conversion is working properly. I cannot test by triggering flat file from RWB.
    Is there a way I can trigger a file from any third party tools and test the content conversion. Do you have any suggestions to make this test possible.
    Thanks,
    Avinash.

    Hi Avinash
    One option is to create a temporary File/FTP sender channel and use it in the sender agreement replacing the JSM channel. In the File/FTP channel, use the MessageTransformBean to achieve content conversion. This way, you can test out the content conversion parameters, and once the JMS server is ready, you can just swap it.
    Rgds
    Eng Swee

  • Receiver JMS Adapter Content Conversion issue

    Scenario :
    R/3 -->XI -->MQ(XML2Plain)
    Hi
    We are using Receiver JMS Adapter to send the Message from XI to MQ.
    The XML has to be converted to plain file. And Content conversion is
    being done.
    With the new development, the message type defined consist of 8 fields
    with fixed length. The XML message goes successfully from XI to MQ
    without any content conversion. But once simple content conversion is
    being done for Receiver JMS adapter, even though the message is
    received but it’s empty (without any data records). The adapter
    monitoring everything seems fine and it gives the status that message
    converted to binary and the message is delivered to MQ. Though on
    checking the messages there is no data records.
    Below is my content conversion configuration done in Module tab. Kindly
    revert back what can be the problem as have done exactly the same way
    as described in Content Conversion How to Guide for receiver JMS.
    localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean  XML2Plain
    localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
    localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService Local Enterprise Bean exit
    XML2Plain Transform.Class com.sap.aii.messaging.adapter.Conversion
    XML2Plain TransformContentType text/plain;charset=utf-8
    XML2Plain xml.addHeaderLine 0
    XML2Plain xml.addHeaderLine SimpleXML2Plain
    XML2Plain xml.fieldFixedLengths 8,10,10,20,40,40,8,8
    XML2Plain xml.fixedLengthTooShortHandling Cut
    regards.
    santosh.

    Hi,
    check localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
    this is not CallJMSService.
    And also check the receiver Structure, if it is falt structure its ok, else
    see the below link if it has the complex structure , how to handle..
    See the below links
    /people/alessandro.guarneri/blog/2006/01/04/jms-sender-adapter-handling-too-short-lines
    /people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
    content conversion
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
    Regards
    Chilla..

  • Receiving file adapter content conversion issue

    Guys,
    Could someone please help me with a Receiving file adapter issue?
    My output structure is something like this:
    Vendor_file_MT (occurence 1)
    --Recordset (occurence 0..unbounded)
    Vendor (occurence 1)
    Field1
    Field2
    Field3
    Field73
    Field74
    My content conversion is very simple:
    Recordset Structure: Vendor
    Parameters:
      Vendor.fieldFixedLengths   30,30,30, (...) ,1,27
      Vendor.fixedLengthTooShortHandling   Cut
      Vendor.endSeparator   'nl'
    If I don't do the content conversion, it works fine, I get all the fields in the XML format.
    When I do the content conversion however, I get multiple lines but only the very first field of each line.
    What could be the problem? What am I missing here? Any idea?
    Your help would be much appreciated.
    Thanks,
    Viktor

    Varga:
    Its little strange that its not working even after adding that.  Did you check the receiver channel in your RWB for any logs. Add the statement in my previous post and Also try to clear the Cache and activate the channel again..See if it works
    Glad it worked
    Edited by: Guru on Apr 21, 2008 3:15 PM

  • Sender JMS Content Conversion - How to process multiple records

    Hi All,
    I use a Sender JMS Channel with Content Conversion.
    My message structure is like this
    <root>
        <rec>    </rec>
        <rec>    </rec>
    </root>
    I have fixed length flat file with multiple records.
    i have given the parameters FixedFieldLength, FieldNames and StructureTitle.
    Which parameter i need to use specify the RecordDelimiter
    Because my input file will have more than record
    my input file -
    xxxx
    yyyy
    if i dont specify any delimiter value, in the module parameter,then for each newline of the file, a new mesage is created.
    <root>
      <rec>xxxx</rec>
    <root>
    <root>
      <rec>yyyy</rec>
    <root>
    But i want the output to be like this
    <root>
    <rec>xxxx<rec>
    <rec>yyyy</rec>
    </root>

    hi,
    You can do your FCC for sender JMS by going through page 5 of this document.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50061bd9-e56e-2910-3495-c5faa652b710

  • Content Conversion issue for header record

    Hi,
    We have a very urgent question on an issue here with one of our XI objects. 
    This is an inbound interface from an external system into R/3 & BW.  The inbound file has a header record (with about 8 fields) and detail records (about 900 fields per detail record). Data going into R/3 & BW don't have header records and everything goes in as detail records. One field from the header of this source file should be passed to the target structure at the detail level. Also, we are NOT using BPM.
    Can someone help us how we could define the file content conversion parameters for File adapter.
    Thanks in advance ......
    Prashant

    I'm so sorry, I wasn't subscribed to this thread and I didn't realize there were responses.
    If you have a message type made up of a Header with 1 occurence and Detail with 1 to unbounded occurunces, you'd want to do the following in content conversion:
    Document Name - your message type
    Document Namespac - your message type namespace
    Recordset Structure - Header,1,Detail,*
    Recordset Structure - Ascending
    Then you'll need to set some of the parameters, depending on the layout of your incoming file. 
    As for the problem of having hundreds of fields, I'm less sure about that.
    Would it be possible to break your detail data type down into smaller data types.  Each with fewer fields.  You'd still have to maintain every field in content conversion, but at least they'd be in seperate parameters, instead of all 900 in one tiny box.
    Here's a very rough example of what I mean:
    If you have 900 fields, instead of making 1 data type of detail, you could make 9 data types, Detail1, Detail2, Detail3, Detail4, Detail5, Detail6, Detail7,Detail8, Detail 9, each with 100 fields in them (or more with even less fields).
    Setting things up the file content conversion would be more complex in this scenario, so it might be a toss up if it's worth it to break it up this way or not if it meant configuring quite a few more parameters.
    For example,
    You'd have to declare your recordset structure like Header,1,Detail1,,Detail2,,Detail3,* etc, and you'd have to make sure to set the .endSeparator to '0' for all of the first 8 details, so it would recognize that they were all on one line.
    I hope this helps a little bit.

  • JMS Content Conversion - Need to control RecordSet per Message

    Hi All,
    I have done a simple JMS to JMS scenario with content conversion.
    I need to control  RecordSet per Message ( similarlly we do for the FILE . that is , Recordset Structure = Records, 500 and Recordset per message = 1)
    How to achive this in JMS adapter.
    Regards,
    B.Jude

    There doesnt seem to be an option for that in the messagetransforbean
    http://wiki.sdn.sap.com/wiki/display/XI/HowTo...ContentconversionmodulewithJ2EEJMS+adapter

  • JMS Content Conversion

    Hi all,
    is possible to do content conversion in JMS Adapter of a file whit the following structure?
    -Root
    --Header
    ---A
    ---B
    ---C
    --Content
    ---Record_A
    D
    E
    F
    ---Record_B
    G
    H
    Record_C
    I
    J
    And if it's possible....how to do it?
    Thanks all
    Mane

    Hi,
    Refer to these links
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
    Check the how to guide provided by prabhu and also this link on the XMl To TeXtCoversion Module,
    http://help.sap.com/saphelp_nw04/helpdata/en/44/748d595dab6fb5e10000000a155369/content.htm
    Regards,
    Kumar.
    **reward points if helpful!!!

  • Doubt in jms content conversion

    Hi ,
    I m doing content conversion in sender jms channel.
    My input is of the format
    AAAAAAA#bbbbbbb#ccccccc#
    I want to map it to XML Structure
    <Root>
    <Record>
      <item>AAAAA </item>
    </Record>
    <Record>
      <item>bbbbb</item>
    </Record>
    <Record>
      <item>CCCC</item>
    </Record>
    </Root>
    Is it possible?

    Resolved

  • XI File Content Conversion Issue

    Peace to All,
    I am having this funny problem in File Content Conversion:
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:ZIN_MT. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
    What did I do:
    DATA TYPE1.
    Structure1:                 TESTOUT_DT           Complex Type
                                             REC               Element                      1-1
                                                   Name11   Element xsd:string        1-1
                                                    Name12   Element xsd:string       1-1
    Structure2:              TESTIN_DT    Complex Type
                                                     Name21   Element xsd:string        1-1
                                                    Name22   Element xsd:string       1-1
    Mapping:
                              name11-name21
                            name12-name22
    Configuration of Sender File :
        DocumentName            :  TESTOUT_DT
        Document NameSpace  : http:/myspace.com/test1
        RecordSetName            :          Recordset
        Recordset Structure       : Rec,1
    Rec.fieldNames                 :name11,name12
    Rec.fieldSeparator             :,
    Rec.endSeparator             :'nl'
    So when I test it it picks up the file but is unable to map it to destination.
    Can anyone help me to find out why?.
    One more hint is that I am using Third party Business System and I use the same for both file CC sender channel and Filereceiver channel.
    I will appreciate your help.
    Thanks

    Many thanks to your guidance...SDN is the best...It worked
    Moving forward I encountered another issue, when I extend it a Trail to it and end up with this mapping:
      ZOUT_MT  11      -ZIN_MT 11
         Recordset 1--1
                 Rec 1unboundedTest01 1-----unbounded
                       key(string)           1...1----
    key 1..1(string)
                       name11(string)    1..1----
    name21   1..1(string)
                       name12(string)    1..1----
    name22  1..1(string)
                 Trail 1...1   -
    Trail 1---1  
                       key(string)   1..1 -
    key 1..1(string)
                        test(string) 1...1 -
    test1..1 (string)
    In Config: Sender File CC
    Doc Name                     :ZOUT_MT
    Doc namspace               : http://mytest.com/test1 
    RecordsetName              : Recordset
    Recordset Structure         : Rec,*,Trail,1
    Key Field Name               : key
    Recordset per message    : 1
    Rec.fieldNames      :   key,name11,name12
    Rec.fieldSeparator  : ,
    Rec.endSeparator  : 'nl'
    Rec.processConfiguration:  FromConfiguration
    Rec.keyFieldValue          : 1
    Trail.fieldNames: key,test
    Trail.endSeparator:  'nl'
    Trail.processConfiguration : FromConfiguration
    Trail.keyFieldValue           : 1
    Trail.fieldSeparator           : ,
    From all this work above , when I put the file having:
       1,111,112
       1,222,223
       1,333,334
       1,99
    The output file in empty (null)...
    Does anyone out there understand why the output file is becoming null..
    here is the log I get in workbecnh (commuunication channel)
    Audit Log for Message: c1a434f5-ad9f-4a26-08c1-e7d579a5927a
    Time Stamp     Status     Description
    21.01.2009 11:48:22     Success     Channel ztest_sender_cc: Entire file content converted to XML format
    21.01.2009 11:48:22     Warning     Channel ztest_sender_cc: Empty document found. Proceed without sending message
    21.01.2009 11:48:22     Success     File "/mylocation/interface/SCM/somefolder/in/shilpagirlsinput.txt" deleted after processing

  • Content Conversion Issue - sender File adapter..!!

    Hi All ,
    Input file:
    GRP|HD|7001|7001A00443|012|
    GRP-LN|DTL|1|ZTAS|3|002|209782010|0001|EN
    GRP-LN|TXT|Customer: KR Test, Case 3
    GRP-LN|TXT|Power            : -2.25
    GRP-LN|DTL|2|ZTAS|4|002|209782035|0001|EN
    GRP-LN|TXT|Customer: CL Test, Case 4
    GRP-LN|TXT|Sphere Power            : -2.25
    T     7
    I have 4 segments (Header,Detail,Text,Trailer) with "|" as the field separator and HD,DTL,TXT,T are the Keyfields
    I need to get the xml structure like below heirarchy. Text segment has to come under Detail structure. Header,Detail and Trailer has to be in the same position.
    Recordset
    --Header
    --Detail
    Text
    --Trailer
    After completion of content conversion, I am getting the XML structure in the below format. All the segments are coming in the same hierarchy.
    Recordset
      -Header
      -Detail
      -Text
      -Trailer
    Text segment has to come under Detail segment. I used the below parameters for FCC.
    Recordset Structure: Header,1,Detail,,Text,,Trailer,1
    Recordset Sequence: Variable
    Header.fieldSeparator
    Header.keyFieldValue
    Header.fieldNames
    Detail.fieldSeparator
    Detail.keyFieldValue
    Detail.fieldNames
    Text.fieldSeparator
    Text.keyFieldValue
    Text.fieldNames
    Trailer.fieldSeparator
    Trailer.keyFieldValue
    Trailer.fieldNames
    Kindly suggest me wat went wrong and how to solve it by content conversion.?
    Thanks
    Deepthi

    Hi All,
    Thank you for your replies.
    I thought of doing it in mapping . My map is like
    DTL -
    > E1EDP01
    TXT----
    >  -
    EIEDPT2
    According to my scenario when ever DTL comes then E1EDP01 has to come and EIEDPT2 has to repeat untill next DTL comes.
    Ex: 1DTL and  4TXT segments .So the output will be..
    DTL -> E1EDP01
    TXT -
    > -
    EIEDPT2
    TXT  -
    > -
    EIEDPT2
    TXT  -
    > -
    EIEDPT2
    TXT -
    > -
    EIEDPT2
    DTL -> E1EDP01
    TXT -
    > -
    EIEDPT2
    TXT  -
    > -
    EIEDPT2
    TXT  -
    > -
    EIEDPT2
    TXT -
    > -
    EIEDPT2
    Right now I couldn't able to generate the above target XML. Everytime I am getting all the TXT segments under one DTL segment like below.
    DTL -> E1EDP01
    TXT -
    > -
    EIEDPT2
    TXT  -
    > -
    EIEDPT2
    TXT  -
    > -
    EIEDPT2
    TXT -
    > -
    EIEDPT2
    TXT -
    > -
    EIEDPT2
    TXT  -
    > -
    EIEDPT2
    TXT  -
    > -
    EIEDPT2
    TXT -
    > -
    EIEDPT2
    Any suggestions how we can get rid of in mapping?
    Thanks
    Deepthi

  • File Content Conversion issue in PI 7.1

    Hi Experts
    I am working on a file to Proxy scenario, I am getting a flat file with , separated but my file will have multiple nodes and I need to do the content conversion and map it to the following structure
    Interface Header
      InterfaceName
      UserID
      Date
      Time
    Journal Entries (1 - Unbounded)
        DocumentHeader
           DocumentDate
           DocHeadetext
           postingDate
        DocumentLineItems
          lineItemno
          lineitemText
          postingkey
    InterfaceTrailer
      Noofrecords.
    Here the problem :I have declared the InterfaceHeader, DocumentHeade,DocumentLineItems and Interface trailer but for Journal entries node what are all the parameters to declare in the content conversion
    please let me know if there are any solutions for this coples structure (content conversion)
    Thanks
    PR

    <?xml version="1.0" encoding="UTF-8"?>
    <!-- New document created with EditiX at Thu May 12 18:57:06 EDT 2011 -->
    <xsd:schema targetNamespace="http://pi.dvn.com/fa/app/ecc/journalEntries/10" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pi.dvn.com/fa/app/ecc/journalEntries/10">
         <xsd:element name="MT_JournalEntryVouchers" type="DT_JournalEntryVouchers"/>
         <xsd:complexType name="DT_JEHeader">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Header structure</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="documentDate">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="docHeaderText" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="25"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="postingDate">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="companyCode">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="currency" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="5"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="documentType">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="transactionCode">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="20"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="referenceNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="16"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accrualReasonForReversal" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accrualReversalDate" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="taxCalculationFlag" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JELineItems">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Line Items structure</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="lineItemNumber">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="lineItemText" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="50"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="postingKey">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="companyCodeLineitem">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accountNumber">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="17"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="transactionAmount">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="costCenter" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="accountType">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="wbsElement" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="8"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="quantity" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="unitOfMeasure" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="productionDate" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="tradingPartner" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="6"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="materialNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="18"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentKeyTerms" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="4"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentBlockKey" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentMethod" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="paymentMethodSupplement" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="baselineDate" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="witholdingTaxCode" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="payer_payeeNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="jointVenture" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="6"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="equityGroup" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="partnerAcctNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="recoveryIndicator" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="billingIndicator" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="orderNumber" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="12"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="profitCenter" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="partnerProfitCenter" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="10"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="assignment" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="18"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="referenceKey" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="12"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="transactionType" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="amountInLocalCurrency" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="amountInGroupCurrency" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="13"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="taxCode" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="2"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="splGLIndicator" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="1"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="assetTransactionType" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="3"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="xref2" minOccurs="0">
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:maxLength value="12"/>
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JournalEntryRecord">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Record Set for Journal Entry</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="InterfaceHeader" type="DT_InterfaceHeader"/>
                   <xsd:element name="journalEntries" type="DT_JEDocument" maxOccurs="unbounded"/>
                   <xsd:element name="InterfaceTrailer" type="DT_InterfaceTrailer"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JEDocument">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Document Data Type</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="documentHeader" type="DT_JEHeader"/>
                   <xsd:element name="documentLineItems" type="DT_JELineItems" maxOccurs="unbounded"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_InterfaceTrailer">
              <xsd:sequence>
                   <xsd:element name="numberOfRecords" type="xsd:string" minOccurs="0"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_JournalEntryVouchers">
              <xsd:annotation>
                   <xsd:documentation xml:lang="EN">Journal Entry Voucher Interface structure</xsd:documentation>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="JournalEntryRecordSet" type="DT_JournalEntryRecord"/>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:complexType name="DT_InterfaceHeader">
              <xsd:sequence>
                   <xsd:element name="interfaceName" type="xsd:string"/>
                   <xsd:element name="userID" type="xsd:string" minOccurs="0"/>
                   <xsd:element name="runDate" type="xsd:string" minOccurs="0"/>
                   <xsd:element name="runTime" type="xsd:string" minOccurs="0"/>
                   <xsd:element name="testRun" type="xsd:string" minOccurs="0"/>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

Maybe you are looking for