File Content Conversion in EDI to File without Seeburger

<b>Hello Friends,
                 I am using just 2 fields Name and Address in 864 Transaction code.Can anybody help me how to do File Content Conversion from EDI to Xml.as i am using only 2 levels of hierarchy..Please explain me the step by step process </b>

Dear Kayanth,
My advice to you is if your implementing organization has more then one EDI scenario today or plan to add more EDI scenario to the business is to use the Item Field Content master with the XI.
This tool is powered by NetWeaver and allows to translate all standard EDI messages from txt file to XML.
The tool is represented today by Informatica and is used as a java file deployed in the file adapter.
This will sit-well with the XI development methodology of  getting the whole EDI message into the XI in an XML format because in the future you might need more then two fields in the message so modifying the interface will take less time.
Try to look to the future of the implementing organization when it comes to interfaces.
"Quick & Dirty" is not always the best way....usually in the long run - its the worst...
Good luck.
Nimrod.G

Similar Messages

  • File Content conversion at the sender adapter without Key field

    Hi All,
    I have a requirement ....We are using Message Transform Bean at the sender adapter (we are not going for FCC as we are tranforming a decryption) ..its is a flat file...
    we dnot have a key field for one of the node .....we have total 5 nodes under parent node and one of the node does not have key field ....
    NOTE: I guess we have to do either Java mapping or XSLT ..but not getting proper weblogs with program...
    and not well versed with coding...i got few codes which were either not fulfilling requiremment or they use stream tranformation where it is decaprecated in NWDS and does not allow to compile it properly .
    Can somebody get me a code for Java which uses Abstract tranformation ...which can full fill below requirement
    parent node
                  Node1
                       node 1a
                       node 1b
                  Node 2
                  Node 3
    Input Flat file is in below format
    example:
    Employee Headre Flat files
    Employee Detail Flat Files(this repeates numerous times as much as number of employees)
    Employee  Trailer Flat Files
    Loan Headre Flat files
    Load Detaisl Flat Files (this repeates numerous times as much as number of employees)
    Loan Trailer Flat files
    Assitance much appreciated thanks .
    Regards
    Kiran

    Hi Stefan,
    I will rephrase the question i guess its communication gap...
    1) we have an existing interface in 3.0..we are not copying the same interface to 7.1 as it was not according to standards and they are phasing out that system.
    2) In 3.0 they are reading the Flat files under one record .. the structure is as follows:
    Parent Node
               Node
                   Row
    They are reading all the flat files row by row.
    and even in receiver they are reading in the similar fashion
    3) In the current structure according to the FS we have to create a structure defined by them which is as below
          Employee
              Header
              Details   node 1
                 Details  node 1a
                  Details  node 1b
              Trailer
              Loan Header
              Loan Detail
              Loan Trailer
    Receiver structure is
    Employee
          Node (this will have the receiver fields which is about 30 fields)
    4) We have pulled a sample file from 3.0 for the existing interface as we din get the sample file for existing one in FS and Iam not sure whn are they gonna send it.
    5) In the existing interface payload we have everything matching even the field lengths and postions and even key fields and key fields we got from the FS
    6) problem is we donot have key fields for the Details node 1a and 1b even in FS or the existing payload and we got an update from the FS consultant that we will be receiving these fields but without keyfields...
    see i donot have any problem taking out the details 1a and 1b out of the details header and create the structure ,,,,but the main issue is without key field we will not be able to generate the 1a and 1b nodes or read it in the FCC or MTB (i have to use MTB as we are decryting the file from the sender).
    Or is there any other method apart from java mapping or module development to handle these files

  • How to do Content Conversion for this structure?

    Hi,
       Urgent required. I have the following structure as below. There is a headerData, itemData and textData. The data that wll come into headerData could be more than one, and the same applies to the itemData and textData. The File adapter is not able to pick this file structure. It is a fixed length file at the receiver end. Could any one tell me how to do the File Content Conversion (FCC) for the structure without using the FCC module. Points to be awarded to best answer. Thaanks in advance.
    The structure :
    <headerData>
    aaaaa
    bbbb
    cccc
    </headerData>
    <headerData>
    aaaaa
    bbbb
    cccc
    </headerData>
    <headerData>
    aaaaa
    bbbb
    cccc
    </headerData>
    <itemData>
    fff
    ggg
    hhh
    </itemData>
    <itemData>
    fff
    ggg
    hhh
    </itemData>
    <itemData>
    fff
    ggg
    hhh
    </itemData>
    <textData>
    fff
    ggg
    hhh
    </textData>
    <textData>
    fff
    ggg
    hhh
    </textData>
    <textData>
    fff
    ggg
    hhh
    </textData>

    HI,
    Use the following content conversion:
    I assume the data coming in the file is of below format:
    Here the key field name is K for 01,02 and 03
    01,aa,bb,cc
    01,aa,bb,cc
    02,ff,gg,hh
    02,ff,gg,hh
    03,hh,ff,hh
    03,hh,ff,hh
    If you data in the file is coming in the above way then your FCC will be
    Recordse strucutre: headerData,,temData,,textData,*
    Keyfield Name: K
    headerData.fieldNames: a,b,c
    headerData.fieldSeparator: ,
    headerData.endSeparator: 'nl'
    headerData.keyFieldValue: 01
    Similarly for itemData and text Data
    Refer the below weblog for the same:
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    Thnx
    Chirag Gohil

  • EDI Flat file Content Conversion

    Hi Experts,
    I have got a question on File Content Conversion, Please have  look the following structure, is it possible with FCC or what is the best possible solution for this, which is very big favour to me.
    Some information about this structure,
    This is EDI message in flat file structure, each segment has got 700 characters as a row, LIN item is repeating many times,
    ST ,XQ , N1 , DTM, LIN, P04, N9,ZA , ZA ,ZA , etc are segments, LIN item is repeating, at the end CTT is last segment. Again from ST segment to CTT segment comes 3 more times.
    ST 0000001     4444444
    XQ H            20100531
    N1 xxxxxxxx                            u 00000
    N4 aaaaaaaa, kk                  xx87654
    DTM600                                                        20100531
    LIN           CB224790                        HH002720033676                  PP00027200336760                ZZ0
    P0400001000000000         000000000  000000000  000000000000000000000000
    N9 VN0000000594
    ZA QA238.00000000000CT         LJXX
    ZA QN1.0000000000000CT         LJXX
    ZA QO000000000000000CT         LJXX
    ZA QP210.00000000000CT         LJXX
    ZA QS61.000000000000CT         LJXX
    ZA QW208.00000000000CT         LJXX
    LIN           CB320275                        SS004330033052                  PP00043300330521                ZZ0
    P0400001000000000         000000000  000000000  000000000000000000000000
    N9 VN0000000594
    ZA QA36.000000000000CT         LJXX
    ZA QN1.0000000000000CT         LJXX
    ZA QO000000000000000CT         LJXX
    ZA QP120.00000000000CT         LJXX
    ZA QS8.0000000000000CT         LJXX
    ZA QW36.000000000000CT         LJXX
    CTT00005300000000000000000000  00000000
    ST 0000001     4444444
    XQ H            20100531
    N1 xxxxxxxx                            u 00000
    N4 aaaaaaaa, kk                  xx87654
    DTM600                                                        20100531
    LIN           CB224790                        HH002720033676                  PP00027200336760                ZZ0
    P0400001000000000         000000000  000000000  000000000000000000000000
    N9 VN0000000594
    ZA QA238.00000000000CT         LJXX
    ZA QN1.0000000000000CT         LJXX
    ZA QO000000000000000CT         LJXX
    ZA QP210.00000000000CT         LJXX
    ZA QS61.000000000000CT         LJXX
    ZA QW208.00000000000CT         LJXX
    LIN           CB320275                        SS004330033052                  PP00043300330521                ZZ0
    P0400001000000000         000000000  000000000  000000000000000000000000
    N9 VN0000000594
    ZA QA36.000000000000CT         LJXX
    ZA QN1.0000000000000CT         LJXX
    ZA QO000000000000000CT         LJXX
    ZA QP120.00000000000CT         LJXX
    ZA QS8.0000000000000CT         LJXX
    ZA QW36.000000000000CT         LJXX
    CTT00005300000000000000000000  00000000
    Please I am really requesting you get appropriate answer and quick response please
    Thanks in Advance
    Regards
    Sandya

    Hi Suresh, Raj,
    Thanks for quick reply, but we haven't got Seeburger Adapter in our landscape. Please one small clarification please this message looks to me, we can do with FCC, but i need some experties from you guys.
    1. ST segment comes in one line with 700 characters - has got 5 fields 1..1 cardinolity
    2. XO segment comes in another line with same length 700 ch,  but 8 fields different lengths 1..1 cardinality
    10 LIN segment comes in another line 700 characters, but 0..n
    Can't we take structure as follows:
    Header     --    0..n
        SegID  ---    1..1
        field 2 -
        1..1
        field 3 -
        1..1
        field 4 -
        1..1
        field 5 ---      1..1
        Row2   -
       1..1
           SegID -
       1..1
           field2  -
       1..1
        Row6    -
        1..n  (for LIN segment)
           SegID ---   1..1
           field 2  ---  1...1
    Please can you give me your experties please??
    Regards
    Sandya

  • File content conversion in File-to-RFC without  BPM

    Hi,
    I am using FCC for file to RFc scenario.
    My input record is in the following format:
    Header record
    data rec1
    data rec2
    Trailer record..
    The parameters are used in File content conversion:
    Recordset Name : Header,item
    Recordset Structure: Header,1,item,*
    key field name : data1
    and in additional parameters:
    Header.fieldNames            HI,GenDate,Ftype,Fname,Fdate
    Header.keyFieldValue       Fname
    Header.fieldFixedLengths 1,8,1,50,8
    Header.endSeparator        nl
    item.endSeparator             nl
    item.fieldNames                  DATA1,DATA2,DATA3,DATA4
    item.keyFieldValue             item
    item.fieldFixedLengths       231,240,241,120
    item.lastFieldsOptional       YES
    Can anyone check whether any parameters are left, b'cos the file is not being read with this settings. and in the C.C its just showing file processing successfully but not able to see the actual file.

    Hi,
    I assume you have header, item and trailer structure in source file.
    Source Data Type will be as follows.
    RecordSet
    --> Header
          --> KeyField(Value OH)
          --> H1
          --> H2
    --> Item
          --> KeyField (Value OL)
          --> I1
          --> I2
    -->Trailer
          --> KeyField (Value OT)
          --> T1
          --> T2
    Where Item Strucutre can come multiple times.
    Please use following settings.
    Recordset name: RecordSet
    RecordSet Structure: Header,1,Item,*,Trailer,1
    Key Field Name: KeyField
    Header.fieldNames: KeyField,H1,H2
    Header.fieldFixedLengths: 2,3,4
    Header.processFieldNames: fromConfiguration
    Header.keyFieldValue: OH
    Header.LastFieldsOptional: YES
    Item.fieldNames: KeyField,I1,I2
    Item.fieldFixedLengths: 2,5,6
    Item.processFieldNames: fromConfiguration
    Item.keyFieldValue: OL
    Item.LastFieldsOptional: YES
    Trailer.fieldNames: KeyField,T1,T2
    Trailer.fieldFixedLengths: 2,8,9
    Trailer.processFieldNames: fromConfiguration
    Trailer.keyFieldValue: OT
    Trailer.LastFieldsOptional: YES
    Regards,
    Gouri

  • File content conversion without field separator

    Hi experts,
    in my scenario I'm sending a txt file to an external receiver.
    Each field of the file must be separated from the others with differents field separators according with the requirement of the receiver, for example:
    field1;field2:field3, field4; ecc....
    For this reason I've created in the source message many "FieldSeparator" fields. These fields will be populated by ABAP program.
    I thought that it was possible to omit parameter fieldSeparator in content conversion, but testing the interface I receive an error because fieldSeparator is missing.
    Is possible to omit fieldSeparator or to specify a fieldSeparator null?
    The fields in the target file must be of variable lenght, so I cannot use FieldFixedLenght.
    The only solution I found is to create in the target message structure a single string with each field concatenated, is the only possible solution?
    Thanks
    Fabio Boni
    Edited by: Fabio Boni on Oct 21, 2010 5:47 PM

    Sorry...posting error earlier..
    The seperator can be concatenated at the end of each field in mapping.So seperator will be part of field value.
    But with receiver FCC, you need to either mentione fieldfixedlenght or fieldseperator.Please check if space is going to to work for you as separator.
    Edited by: nagarjuna _s on Oct 21, 2010 6:36 PM

  • Send a file without File Content Conversion

    Hi,
    I need to send an IDOC flat file that I pick from File system to a FTP server through XI. I was just wondering if there was a way by which I could avoid doing File Content Conversion on both the send and receiver file adapters?
    In my scenario, I am just passing this file through XI. I am not making any changes to it but to send it thru XI, I will have to convert from flat IDOC file ( file generated from File port in ECC) to XML and then from XML to Flat file.
    Can anyone guide??

    Hi William,
    <i>As a matter of fact, <b>no IR object is needed</b>. You can make up any interface name and namespace in the ID.</i>
    This sounds interesting..!!
    Can I just note down the steps in this case and can you validate the same..
    1. No IR objectd needed.
    2. File adapters ~~ Both sender and reciver , make the protocol as FILE
    3. Receievr Determination , Interface determination , Sender Agreement , Receiver Agreement ~~~ Give dummy Interface as well as Namespace values?
    Regards,
    Bhavesh

  • Problem with File Content Conversion

    Hi All
    I am facing a problem with file content conversion.
    This is my sample file structure:
    Header_Record (Occurance - 1)
    Field1 in Header
    Field2 in Header
    Item(Occ-1 to n)
    Field3 in Item
    Field4 in Item
    <<ItemType>> (Structure in Item) (Occ - 0 to n)
    <<Field5>> in ItemType
    <<Field6>> in ItemType
    <<ItemTypeCategory>> (Structure in ItemType)(Occ - 0 to n)
    <<<<Field7>>>> in ItemTypeCategory
    <<<<Field8>>>> in ItemTypeCategory
    Footer_Record (Occurance-1)
    Field9
    Field10
    There is a key field 'Type' in all the above records with unique value in each record.
    Now, I defined Field content conversion as follows:
    Recordset Structure: Header_Record,1,Item, * , ItemType, * ,ItemTypeCategory, * ,Footer_Record,1
    Recordset Sequence: Ascending
    KeyField Name: Type
    Following are parameters defiled:
    Header_Record.Keyfieldvalue: 00
    Header_Record.fieldseperator: ,
    Header_Record.fieldnames: Field1,Field2
    Header_Record.endseperator: 'nl'
    Item.keyfieldvalue: 05
    item.fieldseperator: ,
    item.fieldfieldnames: field3,field4
    item.endseperator: 'nl'
    ItemType.keyfieldvalue: 10
    itemType.fieldseperator: ,
    itemType.fieldfieldnames: field5,field6
    itemType.endseperator: 'nl'
    ItemTypecategory.keyfieldvalue: 15
    itemTypecategory.fieldseperator: ,
    itemTypecategory.fieldfieldnames: field7,field8
    itemTypecategory.endseperator: 'nl'
    Footer.keyfieldvalue: 20
    Footer.fieldseperator: ,
    Footer.fieldfieldnames: field5,field6
    Footer.endseperator: 'nl'
    Now, i pass the following file:
    00,111
    05,222
    10,333
    15,444
    20,555
    What i expect out of my FCC is this (Sample output to show the hierarchy of field values):
    00,111
    05,222
    <<10,333>>
    <<<<15,444>>>>
    20,555
    But, I am getting this output (Hierarchy is missing. All the structures are in the same order without hierarchy):
    00,111
    05,222
    10,333
    15,444
    20,555
    Field values are being identified according to field content conversion, but, the hierarchy of the fields is missing.
    Can you please tell me how should i change my FCC config?
    Sorry for this long question.
    Many Thanks
    Chandra
    Edited by: Chandra Sekhar H on Jan 30, 2009 7:10 PM
    Edited by: Chandra Sekhar H on Jan 30, 2009 7:16 PM
    Edited by: Chandra Sekhar H on Jan 30, 2009 7:17 PM

    You will always get a flat structure from FCC. If you want hierarchichal strucuture, you have to create a target and map. You will get only like -
    Root
    --Recordset
    Group1
    Fields
    Grop2
    Fields
    Group3
    Fields
    VJ

  • File is not creating on the Receiver for File Content Conversion

    Hi,
    i have created a scenario with this blog
    /people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
    for sender side i am using File Content Conversion to read .txt file and on receiver side i need xml file i have done that.
    when i placed the file in the sender folder it gets picked up and i checked in Communication Channel monitporing in Runtime WorkBench it is processed Successfully. but no XML File is created on the Receiver side. i am unable to see the messages on SXMB_MONI also.
    Please suggest some ideas to solve this.
    Thanks,
    Giridhar.C

    Hi Giridhar.
    unable to see the messages on SXMB_MONI also
    If the file got picked and in Communication Channel monitoring RWB you can see that it is processed without any errors ,, then i feel it should come in come.Please check the Audit log in RWB, there you can see the error message if any.
    Please check the connection parameters in FTP and make sure that the same sender folder is
    not being used by any other scenario.If you have done any recent changes then do  a cache refresh .
    Please post if you see any error in content conversion.
    Regards
    Srinivas

  • Using XSLT mapping to avoid File content conversion

    Hi all,
    Can we avoid FCC by using XSLT mapping? I have a scenario in which I have to avoid FCC in the adapter and save the file in a excel/csv format. I have been through the different blogs and forums in SDN.
    I have been through Michal Krawczyk's Blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2803. [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    Got a bit confused whether that blog serves my purpose. Expecting your valid inputs.
    Thanks and regards,
    Harikumar. S

    Hi,
    There are multiple ways in which you can avoid Content Conversion in the Sender / Receiver File adapters.
    I think there was a heated discussion already regarding this in one of your earlier threads,
    Read/Write csv files without file converter
    Basically, if you want to avoid content conversion on the sender file adapter,
    1. Write an Adapter Module. or,
    2. Use a Java Mapping.
    If you want to avoid content conversion on the receiver File adapter,
    1,. Use a Adapter Modules or,
    2. Use Java Or XSLTmapping ( XSLT can be used if the input to the mapping is XML and output needs to be say a Excel File etc).
    Regards
    Bhavesh

  • File Content Conversion in Sender File

    how to convert a fixed length flat file without end seperator sent to XI to a xml form?
    Pleasegive me the idea of Sender Adapter configuration details (esp endSeperator)

    Hi,
    For file content convertion if there are fixed lenth then no need to give the feildseperator,just give the fixed lenths for all the feild in FCC.
    check below links for FCC
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    /people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    /people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
    /people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
    /people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
    /people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
    Regards,
    Phani.
    Reward Points If Helpful

  • Problem with Sender Adapter File Content Conversion

    Hi all!
    I have a question about file content conversion in sender file adapter.
    I have file like:
    {field1
    field2
    field3
    field4
    $
    {field5
    field6
    field7
    field8
    And i need to get file like:
    <dealings>
    <deal>
    <field1>{field1</field1>
    <field2>field2</field2>
    <field3>field3</field3>
    <field4>field4</field4>
    <field5>-}*</field5>
    </deal>
    <deal>
    <field1>{field5</field1>
    <field2>field6</field2>
    <field3>field7</field3>
    <field4>field8</field4>
    <field5>-}*</field5>
    </deal>
    </dealings>
    I put content conversion parameters:
    deal.fieldSeparator = $
    deal.fieldNames = field1,field2,field3,field4,field5
    And i get a file like:
    <ns:mt_swift_file>
    <dealings>
    <deal>
    <field1>{field1</field1>
    </deal>
    <deal>
    <field1>field2</field1>
    </deal>
    <deal>
    <field1>field3</field1>
    </deal>
    <deal>
    <field1>field4</field1>
    </deal>
    <deal>
    <field1>-}*</field1>
    </deal>
    <deal>
    <field1/>
    </deal>
    <deal>
    <field1>{field5</field1>
    </deal>
    <deal>
    <field1>field6</field1>
    </deal>
    <deal>
    <field1>field7</field1>
    </deal>
    <deal>
    <field1>field8</field1>
    </deal>
    <deal>
    <field1>-}*</field1>
    </deal>
    </dealings>
    </ns:mt_swift_file>
    What i do wrong?
    As i understand, XI put string to a separate tag after symbol 'nl', but how can i get structure without unnecessary tags?

    Hi,
    Check some links for FCC
    Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
    Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
    File Receiver with Content Conversion
    Content Conversion (Pattern/Random content in input file)
    NAB the TAB (File Adapter)
    Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
    Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
    How to send a flat file with various field lengths and variable substructures to XI 3.0
    Content Conversion (Pattern/Random content in input file)
    NAB the TAB (File Adapter)
    File Content Conversion for Unequal Number of Columns
    Content Conversion ( The Key Field Problem )
    The specified item was not found.
    File Receiver with Content Conversion
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
    Regards,
    Phani

  • File Content Conversion Generate Incomplete XML

    Dear Expert,
    I am doing the File Content Conversion ...
    Process in sender file adapter is working fine. However, when I check in the receiver folder, the XML file is incomplete after 4 records ...
    The Flat File structure :
    20100120;SAPQL0;0000000013380325
    20100120;SAPQL0;0000000013380332
    20100120;SAPQL0;0000000013380333
    20100120;SAPQL0;0000000013380334
    20100120;SAPQL0;0000000013380337
    20100120;SAPQL0;0000000013380338
    20100120;SAPQL0;0000000013380402
    20100120;SAPQL0;0000000013391225
    20100120;SAPQL0;0000000013394988
    20100120;SAPQL0;0000000013416842
    20100120;SAPQL0;0000000013420424
    20100120;SAPQL0;0000000013420616
    20100120;SAPQL0;0000000013420621
    20100120;SAPQL0;0000000013420624
    20100120;SAPQL0;0000000013420627
    The XML result was truncated(incomplete) :
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_EDIFILE_LOG xmlns:ns0="http://zasp.edi.siemens.com/zedi/contentconversion">
    <Record>
      <EDIFILE>
        <credate>20100120</credate>
        <port>SAPQL0</port>
        <idocnumber>0000000013380325</idocnumber>
      </EDIFILE>
      <EDIFILE>
        <credate>20100120</credate>
        <port>SAPQL0</port>
        <idocnumber>0000000013380332</idocnumber>
       </EDIFILE>
       <EDIFILE>
        <credate>20100120</credate>
        <port>SAPQL0</port>
        <idocnumber>0000000013380333</idocnumber>
       </EDIFILE>
       <EDIFILE>
        <credate>20100120</credate>
        <port>SAPQL0</port>
        <idocnumber>0000000013380334</idocnumber>
       </EDIFI
    Please kindly suggest, which area should I check and correct...
    Thank you very much expert.
    Best Regards,
    Y

    Dear All,
    I believe that the file adapter has finished writing the file. Not sure, How to check whether the adapter is still working or not since from the SXMB_MONI, I see the mssage processing has been completed.
    Further information
    The data type structure :
    1. DT_EDIFILE_LOG     
    1.1         Record --> occurence 1               
    1.1.1      EDIFILE --> occurence 1..unbounded
    1.1.1.1   credate --> occurence 1
    1.1.1.2   port  --> occurence 1
    1.1.1.3   idocnumber --> occurence 1
    In content conversion parameters :
    Recordset Name : Record
    Recordset Structure : EDIFILE,*
    Thank you very much for your suggestion.
    Best Regards,
    Y
    Edited by: Yonisiwa on Jan 22, 2010 3:34 PM

  • Doubt regarding Sender adapter file content conversion to RFC

    Hi Experts,
    Below is the my Source and  Target XML structure ( i have creaated source structure same as target RFC structure),  This scenario is working fine when i give XML file as input. File -> XI -> RFC , xml file is able to update the information in R3.
    How should i configure sender file adapter for file content conversion for above structure(in this case input is fixed lenth text), and i could able to change source structure according to our req, without changing target RFC strucuture.
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_HSA_IDNumber xmlns:ns0="urn:passhe.com/UpdateIdNumberISA32">
       <COMMIT_I>X</COMMIT_I>
       <IDENTIFICATION>
          <STUDENT>6500001191</STUDENT>
          <ID_TYPE>FS0030</ID_TYPE>
          <ID_NUMBER>testxml</ID_NUMBER>
          <VALID_FROM>20070421</VALID_FROM>
          <VALID_TO>20091231</VALID_TO>
       </IDENTIFICATION>
      </ns0:MT_HSA_IDNumber>
    I have configured sender file adapter with FCC like :
    Document name as: MT_HSA_IDNumber
    Document name space as: urn:passhe.com/UpdateIdNumberISA32
    Record structure as: COMMIT_I,1,IDENTIFICATION,1
    COMMIT_I.fieldNames : COMMIT_I
    COMMIT_I.fieldFixedlengths: 1
    IDENTIFICATION.fieldNames: STUDENT,ID_TYPE,ID_NUMBER,VALID_FROM,VALID_TO
    IDENTIFICATION.fieldFixedlengths: 12,6,60,8,8
    i am getting error like this: even when i change source structure like below metioned:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_HSA_IDNumber xmlns:ns0="urn:passhe.com/UpdateIdNumberISA32">
       <COMMIT>
          <COMMIT_I>X</COMMIT_I>
       </COMMIT>
       <IDENTIFICATION>
          <STUDENT>6500001191</STUDENT>
          <ID_TYPE>FS0030</ID_TYPE>
          <ID_NUMBER>idnumber1</ID_NUMBER>
          <VALID_FROM>20070421</VALID_FROM>
          <VALID_TO>20091231</VALID_TO>
       </IDENTIFICATION>
    </ns0:MT_HSA_IDNumber>
    Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'COMMIT_I.fieldFixedLengths' or 'COMMIT_I.fieldSeparator' is missing Consistency check: no. of arguments in 'COMMIT_I.fieldFixedLength' does not match 'COMMIT_I.fieldNames' (0 <> 1)
    Please help me out
    thanks
    dhanush

    Hi Dhanush,
    Try giving the Sender FCC this way for the source structure you have mentioned above.
    Record structure as: COMMIT,1,IDENTIFICATION,1
    COMMIT.fieldNames : COMMIT_I
    COMMIT.fieldFixedlengths: 1
    Hope this helps.
    Thanks and Regards,
    Induja

  • Supress Column Heading - File Content Conversion in Sender Adapter

    Hi,
    Let me give a more clear picture about my scenario.  I need to convert CSV File to XML output:-
    My source file has column heading and values.  The sample data is mentioned hereunder:-
    PERNR;KID;PNALT;NACHN;NAME2;VORNA
    ;1200;1200;Angus
    I have created a data type as under:-
    DT_LegacyEmployee (Category - Complex Type)
         Employees (Category - Element, Occurence - 1)
              Header (Category - Element, Occurence - 0...1)
                   PERNR_H
                   KID_H
                   PNALT_H
                   NACHN_H
                   NAME2_H
                   VORNA_H
              Employee (Categroy - Element, Type - DT_LegacyEmployee_Row, Occurence - 0...unbounded)
                   PERNR
                   KID
                   PNALT
                   NACHN
                   NAME2
                   VORNA
    The file conversion parameters in the file sender adapter are mentioned hereunder:-
    Document Name - MT_LegacyEmployee
    Document Namespace - http://abc.com/xi
    Recordset Name - Employees
    Rescordset Structure - Header,1,Employee,*
    Recordsets per Message - 1
    Key Field Type - String (Case Sensitive)
    Employee.fieldSeparator - ;
    Employee.endSeparator - 'nl'
    Employee.fieldNames - PERNR,KID,PNALT,NACHN,NAME2,VORNA
    I dont' have a key field value.  How do we remove the header and show only the values in the xml output.  I have searched the forum topics as well checked many blogs related to file content conversion, but nothing helped.  Kindly advice how to fix this issue.  Thanks in advance.
    Regards.
    Praveen

    Hi Praveen,
    Change your File Adapter as below
    Document Name - MT_LegacyEmployee
    Document Namespace - http://abc.com/xi
    Recordset Name - Employees
    Rescordset Structure - Employee,*
    Recordsets per Message - 1
    Key Field Type - String (Case Sensitive)
    Employee.fieldSeparator - ;
    Employee.endSeparator - 'nl'
    Employee.fieldNames - PERNR,KID,PNALT,NACHN,NAME2,VORNA
    There is no need for the Header required in the data type.
    DT_LegacyEmployee (Category - Complex Type)
    Employees (Category - Element, Occurence - 1)
    Employee (Categroy - Element, Type - DT_LegacyEmployee_Row, Occurence - 0...unbounded)
    PERNR
    KID
    PNALT
    NACHN
    NAME2
    VORNA
    Now the trick is in the mapping program
    Lets assume your mapping looks like
    MT_LegacyEmployee ---> MT_TargetEmployee
    - Employees ---> Records
       - Employee ---> Record
         - PERNR  ---> TargetPERNR
         - .. so on
    When you do a mapping from Employee ---> Record apply the following logic.
    (PERNR)--->
                 (TestEquals =) --->(NOT)--->
    (Constant) --->                                (IF)
    (PERNR)                       (IF Without Else) ---> (Record)
                                                   (THEN)
                                (Employee)--->
    When doing this make sure RightClick on PERNR and Select Context ---> Employees.
    By default context would be from Employee and it will give you an error of XSD format. So make sure you are changing the context.

Maybe you are looking for