File Content Conversion - Multiple KeyField

Hi Experts,
I have the following structures with 2 keyfields
<Structure1>
  keyfield1 - value 1
  keyfield2 - value 1
<Structure2>
  keyfield1 - value 1
  keyfield2 - value 2
<Structure3>
  keyfield1 - value 2
  keyfield2 - value 1
<Structure4>
  keyfield1 - value 9
  keyfield2 - value 1
Pls advise me, is it possible to have multiple keyfield in our FCC?
If so, advise me how to handle this.
Thanks in advance.
Regards
Bala.

Bala,
The best thing would be if it is a fixed length file then take field1 and field2 as concatened and as one field which would be your key field. Once when you pick up you can take a substring in the mapping for this field and can map. If you are reading a csv then go with the same approach and take a substring after comma.
Regards,
---Satish

Similar Messages

  • Receiver File Content Conversion - Multiple Hier. Levels, Several Files

    you can create several files using single message execution.
    one source message structure and target multiple messgae types(0..1) occurance
    and same thing you can implement in your Interface mapping.
    1 -> Multiple Inbound interfaces
    your target final strcture would be with Header,lineitems.
    your JDBC->XI Intermedicate.
         XI Intermediate ->XI final (this final structure will create the your file)
    that way you can design your scenario.
    Regards,
    Venu.

    Hello Venu, thanks for answering,
    When you talk about intermediate structure you are referring to the approach I mentioned in the link above or to something that can be done using the same scenario structure I have right now?
    I am going I little bit deeper in my scenario just in case I havent been so clear in my first explanation:
    Lets suppose I have 3 stores: 1001,1002,1003
    For each store there are 2 items: 999,888
    So XI retrieves the information from the DB thru a stored procedure. This is the output:
    STORE--PLU
    1001--999
    1001--888
    1002--999
    1002--888
    1003--999
    1003--888
    Please note the information is coming in a flat structure. In the beginning I tried to separate it into several outputs (selects) as shown below but I relaized that was not possible to be handled by XI:
    STORE--PLU
    query 1
    1001--999
    1001--888
    query2
    1002--999
    1002--888
    query
    1003--999
    1003--888
    That would have been the best approach as I would have generated one single file for each message and thats it, but unfortunately, Xi does not work that way with MSSQL Queries. So I had to made something up based on the answers I got from the SDN experts (Link is below in first message). There was when I used context handling for generating the structures myself within one single message.
    In the scenario shown above I would have just needed to generate the following structure for creating messages from the source:
    Level1: Main Node
    Level 2: Header
    Level 2: Body
    But now, As I am forced to generate my 3 structures within 1 single message, I had to insert one more node to wrap header and body in per iteration (as a file would do):
    Level1: Main Node
    Level2: File
    Level3: Header
    Level3: Body
    And that is the problem I am asking help for, that allegedly, XI File Content conversion can just handle up to 2 levels.
    Thanks again for answering Venu.
    Regards.
    Edited by: Anibal Granado on May 12, 2010 11:34 PM

  • File Content Conversion - Error in keyfield Value

    Hello experts,
    I am doing file content conversion for a file to file scenario. The input file is a csv file which is converted to xml using the file content conversion. The key field of input file is used for implementing conversion.
    While testing the FCC, I noticed that if the keyfield value is wrong for a record in the file, the record is ignored altogether without throwing any errors or warnings. Is there any way to notify if any records have been ignored as a result of incorrect keyfield value??
    Thanks in advance!
    RR

    There seems to be NO way to handle it in FCC.
    File Content Conversion - Key Field Value
    u can think of work arounds by handling it in mapping....
    -santosh.

  • File Content Conversion in Reciever Adapater for multiple element

    Hi folks,
    My Source file structure  is
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:file_sender_mt xmlns:ns0="urn:filetofiledemo">
       <recordset>
          <data1>
             <name1>a</name1>
             <age1>b</age1>
          </data1>
          <data>
             <name>c</name>
             <city>d</city>
             <age>e</age>
          </data>
       </recordset>
    </ns0:file_sender_mt>
    in my file reciever adapter i am uisn file content conversion and these are the parameters that i have given
    reordesetStructure -->
    recordset,data1,data,FileNameNode
    Name                                value
    recordset.fieldSeparator            '0x09'       
    data1.fieldSeparator                '0x09'
    data.fieldSeparator                 '0x09'
    data.endSeparator                   '0x09'
    '0x09' is the hex vale for tab
    My o/p file is coming as
    a     b
    c     d     e
    the desired o/p is 
    a     b     c       d     e
    Any idea on this
    Thanks
    Amit

    Hi Amit,
    You can try using this approach.
    You can create two data types.
    The input data type is of the input file format.
    The output data type can have all the five tags (Name1, Age1, Name, City and age) under one header tag(data1), instead of two tags(Data1, data) in the input file.
    Then in the receiver channel u can define the reordesetStructure -->
    recordset,data1,FileNameNode
    This will produce the output data in one line.
    Regards
    Neetu

  • File content conversion in Sender Adapater for multiple occurances

    Hi ,
    I am mapping from flat file to idoc .
    My flat file is a tab demilited
    Since the idoc would have structure
    like header , lineitem , schedule
    in my flat file conversion
    i am giving recordset structure
    as header,1,lineitem ,,schedule,
    since lineitem would be repeated many times
    Bt if  i give * i need to give a keyfieldname
    which would mean that keyfieldname has to appaer in header and schedule .
    since in my case my Column values in header , lineitem and schedule are different
    how can i do the file conversion in this case
    i can doing something like this
    header.keyFieldValue ""
    schedule.keyFieldValue ""
    header.keyFieldInStructure ignore
    schedule.keyFieldInStructure ignore
    i am not even sure if thats the correct way
    Thanks
    Amit

    Hi Amit,
    Take a look at these...
    /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/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    cheers,
    Prashanth
    P.S Please mark helpful answers

  • Problem with file content conversion for multiple substrcture. Please help!

    Hi Experts,
       I am using file content conversion in file sender communication channel. The input file is a flat file with data like this:
       A01 AA8I0NBVDA      20090704     84900
       A02 AA8I0NBVDA      20090704     84900
       A03 AA8I0NBVDA      20090704     84900
       I want the data in sender side after content conversion to be like this:
      <ns:Receive_Schedules xmlns:ns="http://mynamespace">
         <ScheduleData>
              <line>A01 AA8I0NBVDA      20090704     84900</line>
              <line>A02 AA8I0NBVDA      20090704     84900</line>
              <line>A03 AA8I0NBVDA      20090704     84900</line>
         </ScheduleData>
    </ns:Receive_Schedules>
    I have tried many options in file content conversion but getting the data like this:
    <ns:Receive_Schedules xmlns:ns="http://mynamespace">
         <ScheduleData>
              <line>A01 AA8I0NBVDA      20090704     84900</line>
         </ScheduleData>
           <ScheduleData>
              <line>A02 AA8I0NBVDA      20090704     84900</line>
           </ScheduleData>
           <ScheduleData>
              <line>A03 AA8I0NBVDA      20090704     84900</line>
           </ScheduleData>
    </ns:Receive_Schedules>
    Following are the settings/properties have configured in content conversion:
    Document Name     Receive_Schedules
    Document namespace     http://mynamespace
    Document Offset     <no value>
    Recordset Name     <no value>
    Recordset namespace     <no value>
    Recordset structure     ScheduleData,*
    Recordset sequence     Ascending
    Recordsets per message     1
    Key field Name     <no value>
    Key Field Type     String
    ignoreRecordsetName     true
    ScheduleData.endSeparator     'nl'
    ScheduleData.fieldNames              line
    ScheduleData.fieldSeparator     'nl'
    How to get the desired message? What changes I need to do in content conversion settings? Please help!
    thanks
    Gopal
    Edited by: GOPAL BALIGA on Jul 1, 2009 12:11 PM

    Hi Ranjan,
      My structure is like what you ahve defined.
      scheduledata...1.1
    ...line....0...Unbound
      I also tried the parameters you gave but still getting the same.
      <ns:Receive_Schedules xmlns:ns="http://mynamespace">
    <ScheduleData>
    <line>A01 AA8I0NBVDA 20090704 84900</line>
    </ScheduleData>
    <ScheduleData>
    <line>A02 AA8I0NBVDA 20090704 84900</line>
    </ScheduleData>
    <ScheduleData>
    <line>A03 AA8I0NBVDA 20090704 84900</line>
    </ScheduleData>
    </ns:Receive_Schedules>
    Following are the settings/properties have configured in content conversion:
    Recordset structure ScheduleData,*   -
    > Is the value correct?
    Recordset sequence Ascending  -
    > Is the value correct?
    Recordsets per message 1  -
    > Is the value correct?
    ignoreRecordsetName true
    ScheduleData.fieldSeparator nl
    ScheduleData.fieldNames line
    ScheduleData.endSeparator nl
    Edited by: GOPAL BALIGA on Jul 2, 2009 5:28 AM

  • File Content Conversion with Multiple structures

    Here is the scenario
    Legacy to XI -> XI to R/3 (App Server)
    txt file and fixed length.
    <b>Test file</b>
    100WELCOME    0430000960603201321
    2000000000040008000803
    <b>Table2</b>
    RecordType
    PriorityCode
    Destination
    BankOrginNo
    CreationDate
    CretionTime
    Spaces
    <b>Table2</b>
    RecordType
    Destination
    BankOrginNo
    ReferenceCode
    ServiceCode
    RecordLength
    CharactersPerBlock
    PartialCompression
    CompressionSpaces
    <b>Content Conversion Parameters:</b>
    Document Name: Details
    RecordsetName  : recordset
    Recordsetstructure  : Table1,1,Table2,*
    Recordsetsequence: Ascending
    RecordsetperMessage: *
    Keyfieldname          : KF
    Kefieldtype          : String(Case-Sensitive)
    Table1.keyFieldValue     :'1'
    Table1.fieldFixedLengths:1,2,10,10,6,4,47
    Table1.fieldNames :RecordType,PriorityCode,Destination,BankOrginNo,CreationDate,CretionTime,Spaces
    Table2.keyFieldValue     :'2'
    Table2.fieldFixedLengths: 1,10,10,10,3,3,4,1,38
    Table2.fieldNames:RecordType,Destination,BankOrginNo,ReferenceCode,ServiceCode,RecordLength,CharactersPerBlock,PartialCompression,CompressionSpaces
    ignoreRecordsetName     :true
    When I am trying with first structure it is working fine, where as 2 structures it is not.
    in the adopter monitoring it show it pics the file from Legacy(file adopter display green), where as SXMB_MONI it is not showing any thing.
    can any body help on this do I need to maintain any other parameters for file content conversion.
    Thanks
    M

    HI,
    I can see that.
    The number of characters in the file for TABLE2 is lesser then the number of field size given.
    for eg. if the table2 fixed field length sum is 20 ,your file contains only 10 characters. Please give complete data for table2
    Test file
    100WELCOME 0430000960603201321
    <b>2000000000040008000803</b>
    Table2.fieldFixedLengths: 1,10,10,10,3,3,4,1,38
    Ragards
    vijaya
    Message was edited by: vijaya kumari

  • File content conversion: nodes have multiple occurence and is jumbled

    Hi,
    Here is one structure used in file content conversion.
    Header
    Dataline1
    Dataline1
    Dataline1
    Dataline2
    Dataline2
    Dataline2
    Header, Dataline1 and Dataline2 are nodes containing more than one fileds.
    We have mentioned 'fieldSeparator', 'EndSeparator' and 'keyFieldValue' for each of the nodes Header, Dataline1 and Dataline2 .
    Now the requirement has changed and the source file structure is as given below.
    Header
    Dataline1
    Dataline2
    Dataline1
    Dataline2
    Dataline1
    Dataline2
    Now with the same communication channel, the content conversion picks up only the first occurence of Dataline1, Dataline2 ie only this much
    (Header
    Dataline1
    Dataline2)
    is being picked or read.
    The other occurences are lost, even though logically it should pick all of them, since 'keyFieldValue' is specified for each node..
    Should I give any extra parameters in the communication channel for file content conversion.? or else what is the best way to proceed

    Hi John !
    Have you checked the recordset structure in the file content conversion parameters?? like "Header,1,Dataline1,,Dataline2, " to specifiy that it should be 1 header structure, N dataline1 and N dataline2 ??
    Regards,
    Matias.

  • 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 Problem

    Hi
    I have a flat file having 10 fileds with fixed length of field 7 characters
    abc  bcd  dce  cef  ecf  fgi
    123  234  343  233 434 343
    322  222  222  222 222 222
    +++++++++++++++++++++++++++++++
    XML CODE FOLLOWS
    +++++++++++++++++++++++++++++++
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_send xmlns:ns0="http://OTO-Continue.com">
      -<SEND>
       <abc>343</abc>
       <bcd>343</bcd>
       <dce>434</dce>
       <cef>3434</cef>
       <ecf>343</ecf>
       <fgi>434</fgi>
      </SEND>
      </ns0:MT_send
    As per the client req I'm going with FCC. The file is picking fine with the FILE. But not picking with the FCC.
    The parameters which I gave are as follows.
    SOURCE I feel it is fine since file is picking fine and keeping the same for FCC also.
    PROCESSING
    QOS -- Exactly Once
    Poll Interval -- 10
    Processing Mode -- Delete
    Empty-File Handling -- Process empty files
    CONTENT CONVERSION Parameters
    Document Name -- (am giving sender data type name) DT_send
    Document NSpace -- http://OTO-Continue.com
    Recordset Name -- SEND
    Recordset Structure -- SEND,*
    Recordset Sequence -- Ascending
    Recordset per Message -- 0
    And in the table the parameters am settings are
    SEND.fieldNames                 abc,bcd,cde,def,efg,ghk
    SEND.fieldFixedLengths      7,7,7,7,7,7       (because each and every field has 7 characters)
    SEND.keepIncompleteFields       No
    SEND.fieldFixedLengthType      char
    SEND.fieldContentFormatting     trim
    SEND.fieldEndSeparator            'nl'
    This was the configuration. But this is not working I monitored the Communication Channel and file is not reading and not getting deleting.
    What actually went wrong in above configuration. Why it is not working.
    Thanks.

    Hi Swarna,
    CONTENT CONVERSION Parameters
    Document Name -- ?
    DocumentNSpace -- ?
    Recordset Name -- ?
    Recordset Structure -- ?
    Recordset Sequence -- Ascending
    Recordset per Message -- ?
    Document Name - <Message Type> eg:- (MT_ABC)
    DocumentNSpace - Name space of your MT
    Recordset Name - The root node( Which has one occurence)
    Recordset Structure - The parent node of the fields(can have multiple occurences)
    Recordset Sequence -- Ascending
    Recordset per Message -- 1/* (No.of records per each record set)
    In your structure
    +++++++++++++++++++++++++++++++
    XML CODE FOLLOWS
    +++++++++++++++++++++++++++++++
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_send xmlns:ns0="http://OTO-Continue.com">
    -<SEND>
    <abc>343</abc>
    <bcd>343</bcd>
    <dce>434</dce>
    <cef>3434</cef>
    <ecf>343</ecf>
    <fgi>434</fgi>
    </SEND>
    </ns0:MT_send
    There is no root node,  so in your FCC you need to mention your RecordsetName and you can ignoreRecordSetName in result structure. Check the following blog simulates your requirement.
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    Regards,
    Prasanna

  • 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 Content Conversion Error in PI 7.1 (file to Proxy)

    Hi
    I am working on File to Proxy Scenario and I gave the File content conversion as below, File is picking up by the PI Server when I look at Communication Channel Monitoring, However when I open the Message ID in the CC monitoring it says as
    404 Not Found
    The requested resource does not exist.
    and I do not see any message SXMB_MONI(Because the content is not converted), Can anyone give an idea how to debug this
    Thanks 
    PR
    Please find the details below which I gave in the content Conversion
    Document Name : MT_TW_AK
    Document NameSpace : http://aiwcd.com/Claims_Management(CM)_Rel2.0
    RecordSet Name : FROISROIAcknowledgement
    RecordSet Structure : Header,1,Record,*,Trailer,1
    Recordset Sequence : Ascending
    KeyField Name :TransactionSetID
    Key Field Type : String (Case Sensitive)
    IgnoreRecordsetName : true
    Header.fieldNames :TransactionSetID,SenderID,ReceiverID,DateTransmissionsent,TimeTransmissionsent,OriginalTransmissionDate,OriginalTransmissionTime,TestProductionCode,InterchangeVersionID
    Header.fieldFixedLengths: 3,25,25,8,6,8,6,1,5
    Header.keyFieldValue     : H
    Record.fieldSeparator :
    Record.fieldNames : TransactionSetID,RecordSequenceNumber,DateProcessed,TimeProcessed,InsurerFEIN,ClaimAdministratorPostalCode,ClaimAdministratorFein,AcknowledgementTransactionSetID,ApplicationAcknowledgmentCode,InsuredReportNumber,ClaimAdministratorClaimNumber,JuridictionClaimNumber,MaintenanceTypeCode,MaintenanceTypeCodeDate,RequestCode,FreeFormText,NumberofErrors,MaintenanceTypeCorrectionCode,MaintenanceTypeCorrectionCodeDate,JurisdictionBranchOfficeCode,ClaimAdministratorAlternatePostalCode,NumOfErrors
    Record.fieldFixedLengths: 3,9,8,6,9,9,9,3,2,25,25,25,2,8,3,60,2,2,8,2,9,19
    Record.keyFieldValue : A
    Trailer.fieldNames:TransactionSetID,DetailRecordCount,TransactionCount
    Trailer.fieldFixedLengths: 3,9,9 
    Trailer.keyFieldValue     : T
    ignoreRecordsetName: true

    PR,
    Can you check the error in sender communication channel?
    Go to RWB ---> Component Monitoring ---> Adapter Engine ---> Communication cahnnel monitoring --> it displays new page. Then give your file sender communication cahnnel name. There you will definitely see some error.
    The error what you are getting is a different to this one. Can you please check the error what I have given above path.
    Regards,
    ---Satish

  • Sender adapter: File content conversion suggestion

    Hi all,
      I require your suggestion on File content conversion with Sender File adapter. I am having a scenario where I would be getting multiple orders data i.e., header and item information in a single file. Suppose, we have given a chance to design the source structure. So, which would be the better way for having the source structure so that it would be easy for file content conversion and mapping. Is it like Method 1 or Method II?
    Method I:
       Orderno,FieldA,FieldB,FieldC
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
       Orderno,FieldA,FieldB,FieldC
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
       Orderno,FieldA,FieldB,FieldC
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
    Method II:
       Orderno,FieldA,FieldB,FieldC
       Orderno,FieldA,FieldB,FieldC
       Orderno,FieldA,FieldB,FieldC
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
       Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
      If you suggest method I, can you let me know how the content conversion parameters look like?
    Thanks in Advance,
    Adithya K
    Message was edited by:
            Adithya K

    Adithya,
    Looking at your input file I think a structure as below would be better.
    <Order_Data>
      <Orderno>
          <Orderno/>
          <FieldA/>
          <FieldB/>
          <FieldC/>
      </Orderno>
      <Items>
          <Orderno/>
          <OrderItem/>
          <Field1/>
          <Field2/>
          <Field3/>
          <Field4/>
          <Field5/>
      </Items>
    </Order_Data>
    Content Conversion Parameters for this would be:
    RecordSet Structure        OrderData,,Orderno,1,items,
    OrderData.fieldNames       Orderno,items
    OrderData.fieldSeparator   'nl'
    OrderData.endSeparator    'nl'
    Orderno.fieldNames          Orderno,FieldA,FieldB,FieldC
    Orderno.fieldSeparator       ,
    Orderno.endSeparator       'nl'
    items.fieldNames              Orderno,OrderItem,Field1,Field2,Field3,Field4,Field5
    items.fieldSeparator           ,
    Items.endSeparator           'nl'
    ignoreRecordsetName        true
    Depending on which are your key fields you will  have to put two more parameters:
    Orderno.keyFieldValue
    items.keyFieldValue
    Hope this would be of some help.
    Thanx,
    Manju.

  • File Content Conversion - Key Field Value

    Hi Experts,
    I am using File to Idoc scenario for my mapping. In the receiver Communication channel, I am using File Content Conversion. My scenario is as follows :
    I have a recordset with Header and Line items with Key Field Indicator as 'H' and 'L'. In some cases, the value for this Key Field is coming in as something other than 'H' and 'L'. I need to throw an exception when this Key Field is not 'H' or 'L'.
    In the 'Content Conversion' tab, my attributes are as:
    Header_Structure.keyFieldValue = 'H' and Line_Structure.keyFieldValue = 'L'. Is there any more attributes that I need to add ?
    Please advise. Thanks a lot.
    Regards,
    Freddy.

    >>multiple key field values in FCC configuration i.e Line_Structure.keyFieldValue = H or L
    AFAIK it is not possible but lets wait for other experts to comment on this...
    >>Can keyFieldInStructure (add, ignore) parameter help me in this case ?
    No. this parameter is only used when you want to include key filed in ur XML structure(add) or not (ignore)...
    Chk this:
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm

  • File content conversion for file with hierarchical structure

    Hi
    I want to read a flat file in the following message structure using file content conversion.
    Message structure is :
    01 ( occurence = 1)
    _ 1B (occurence = unbounded)
    _ 1G (occurence = unbounded)
    _1H (occurence = 1)
    _1N ( occurence = unbounded)
    99 (occurence = 1, trailer record)
    In short there will be one 01 ( header record) in file. There will multiple 1B records. Under one 1B record there will multiple 1G records. Under each 1G record there will be one 1H recoprd and multiple 1N record. At the end there will one 99 record.
    File format : Fixed length
    Data in the text file would be as follows :
    01Test
    1BF0001MS005       4855390859  
    1GF000172075F31501  GBPINV 040806
    1HF000172075F 
    1NF000172075F0011MS0051125002FOOUKSTFOOD
    1NF000172075F0021MS0056540003ICOMSIEARCA 
    1BF0111TT005       3454390859  
    1GF011172075F31501  INRINV 040806
    1HF011172075F 
    1NF011172075F0011MS0051125002FOOUKSTFOOD
    1NF011172075F0021MS0056540003ICOMSIEARCA 
    99002187004855390859
    Is it possible to do above using file content conversion or is there any method to do it. Please suggest.
    Thanks
    Varun

    you cant acheive this heirarchy using the file adapters cont. conv, cos it supports only to a single level.
    Maybe you can have a module or use the conversion agent !!
    Some good reads on the Conv. agent!!!
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    /people/paul.medaille/blog/2005/11/18/conversion-agent-a-free-lunch
    /people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi
    /people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield

Maybe you are looking for