Content Conversion: keyFieldValue

In <i>Recordset Structure</i>, I specified a substructure with *, the rest with 1.
Do I <b>HAVE TO </b>specify keyFieldValue value for all the substructure with 1 occurrence.
I mean, is that <b>compulsory</b> to specify it for one-time-occur substructure.
What happens if I specify these one-time-occur substructures with the same value for keyFieldValue?
Thanks
null

in case you have a structure with different nodes then to distinguish the data between these nodes, you will need a key field.
Note: you cannot have the same keyfield for two different nodes ie records.
Do look into the following links to give you an idea about FCC and keyfields;
Sender -
/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 - TAB delimited
/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
Receiver-
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion

Similar Messages

  • File content conversion - keyFieldValue

    Hello everybody,
    Is there a way to generate more than one Detail.keyFieldValue in the File Content Conversion? , the reason for this question is that I have a file like this.
    00      value     value     value     value     value
    01      value     value     value     value     value     
    01     value     value     value     value     value
    02     value     value     value     value     value      
    69     value     value     value     value     value
    99     value     value     value     value     value
    And the Structure should be like this.
    Header
             00     value     value     value     value     value
    Detail
            01      value     value     value     value     value
            01     value     value     value     value     value
            02     value     value     value     value     value
            69     value     value     value     value     value
            99     value     value     value     value     value
    In my header the keyFieldValue is 00, but in the Detail could be 01 and 02 and 69 and 99 as just one Detail?
    Regards,

    I have performed this type of mapping before... Below is the approach that i followed..
    You have to do a 2 level mapping..
    Construct the below XML msg to read the flat file into an intermediate XML structure...
    <DT_XXX>
    .<Recordset>
    ..<Rec_00> 1.1
    ..<Rec_01> (0..unbounded)
    ..<Rec_02>  (0..unbounded)
    ..<Rec_69> (0..unbounded)
    ..<Rec_99>(0..unbounded)
    </Recordset>
    <DT_XXX>
    Rec_00.keyfield = 00
    Rec_01.keyfield = 01
    Rec_02.keyfield = 02
    Rec_69.keyfield = 69
    Rec_99.keyfield = 99
    Rec_00.endSeperator - 'nl'
    Rec_00.fieldFixedLengths - provide
    Rec_00.fieldNames - Field1,field2....
    Rec_00.processFieldName - fromconfiguration
    Then as Step2, perform a mapping to convert this into the required XML structure...
    <DT_XXX>
    <Header> </Header>
    <Details>
    <Rec_01>
    <Rec_02>
    <Rec_69>
    <Rec_99>
    </Details>
    <DT_XXX>

  • Spaces getting trimmed in file content conversion

    Hi all,
    I am converting a flat file to an XML file by XI. The problem which i am facing in file content conversion is that the spaces in flat file data are getting trimmed to one space in the XML in SXMB_MONI.
    The data in flat file is like SOUTHSEA and HANTS is having nearly 8 spaces.
    But the data in XML is:
    <b><u>SOUTHSEA HANTS PO5 2LZ PO5 2LZ020327</u></b> i.e. in XML, there is only 1 space between SOUTHSEA and HANTS.
    The following parameters i have used in file content conversion:
    .keyFieldValue '*'
    .fieldSeparator 'nl'
    .fieldNames RECORD_DATA
    .ignoreRecordsetName true
    I am taking each record of the flat-file in a single record RECORD_DATA in XML.
    <b>So can anyone tell me why the big spaces are getting trimmed to a single space eg. between SOUTHSEA and HANTS etc.</b>
    Thanks in advance.
    Rajeev Gupta

    Hi,
    try :
    NameA.fieldContentFormatting = <b>nothing </b>
    as the default is <b>trim </b>
    refere:
    http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • File Contente Conversion w/o keyFieldValue

    Hi folks,
    Iu2019ve the following flat file for my sender file adapter:
    HD00287u2026
    12332341999933459
    41324321453213242
    TR
    HD00288u2026
    12332341999933459u2026
    41324321453213242u2026
    15332341999933459u2026
    41325421453213242u2026
    TR
    Where HD is the header key field and TR the trailer key field; however for the body lines I donu2019t have any key field to match each body line.
    Is it anyway to convert this flat file in XML with the File Content Conversion of file adapter? Iu2019ve been searching and I think the standard parameters donu2019t fulfill this requirement, I must have a key field, but maybe Iu2019m wrongu2026 maybe you know some workaround.
    My second approach would be an ejb module to include u201CBDu201D key on each line without HD or TR. Afterwards, the standard module converts the flat file in a XML with the configuration of the file content conversion.
    Let me know if it is possible to do it with file content conversion. No problem with ejb, but I donu2019t want to create an enhancement if the standard fulfill the requirement.
    Thanks in advance,
    Ricardo.

    Hi
      I think the blog 1825, can be used to try out something in ur scenario..
    you have Header and Trailer.. so thats standard..
    for rest of the lines, you can create a structure like hbatch in the blog
    like below (define this 10 times)
    --<htbatch0>         (Zero to unbounded)
    <key0>
    <Value0>
    --<htbatch1>   (Zero to unbounded)
    <key1>
    <Value1>
    for all 10 digits (say 0,1,2...9) specifying the first digit to be the Key (as like blog)
    by doing this, the first digit is considered as Key and all similar lines are grouped
    Not sure, how the FCC behaves, but I expect..
    that all the data will be converted into the above structure, but sorted based on starting digit
    all lines starting with 0 in first set of groups <hbatch0>
    all lines starting with 1 in next set of groups and so on..
    If this works, the next thing is that your sequence of your data would be re-arranged (sorted)
    Regards
    Vishnu

  • What are the content conversion parameters

    Hi All
    This link contains the text file.
    http://www.census.gov/foreign-trade/schedules/d/dist.txt
    what are the content conversion parameters are required to convert that text to xml.

    <sen_dt>
         <prefix>
              <heads>
                   <dc>               
                   <pc>
                   <name>
              <main>
                   <dcno>
                   <pcno>
                   <name1>
    <rec_dt>
         <prefix>
              <District_code>             District code      optional
              <port_code>              port code          1
              <name>                   name              
         <main>
              <District_code_no>
              <port_code_no>
              <name1>
    content conversion
         document name:<sen_dt>
         document namespace:http::----
         document offset:--
         recordset name:input
         recordset structure:heads,1,main,*
         recordset sequence:Ascending
         recordset per message:----
         keyfield name:---
    prefix.fieldfixedlengths:---
    prefix.endSeparator:---
    prefix.fieldNames;---
    prefix.keyFieldvalue:--
    prefix.keyFieldlnStructure:---
    main.fieldFixedLengths:9,
    main.fieldSeparator:|
    main.endSeparator:'nl'
    main.fieldNames:district code,port code,name
    main.keyFieldValue:
    main.keyFieldlnStructure:

  • 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

  • File-Sender: Verification of file content during file content conversion

    Hello,
    I have a question regarding „file verification“ when using the file-sender adapter.
    I got a flat file (.csv) that I convert into XML with the file-sender adapter and file-content-conversion.
    In the file there is a column “RecTyp” that is my KeyFieldValue. Possible values for RecTyp are “B”, “D”, “U”, “T”.
    So far so good. All this works perfectly.
    If (due to an error) there is another value in RecTyp than the 4 mentioned above (B;D;U;T) the file adapter ignores this row today. And here begins my issue:
    I want to change this behavior. That means in detail, I want to check if there is another value in my KeyFieldValue “RecTyp” than specified. If this is the case an exception should be thrown. The whole message should not be delivered.
    We had the idea to use the module-processor for this verification….
    But may be there are other suggestions. Or may be some one can provide an appropriate module that is already written, etc….
    Does anyone have an idea?
    Kind regards,
    Tobias

    Hi,
    It is better to pick the file in generic way i.e Row by Row and then go with the validation with the help of Adapter Modules or in the Mapping.
    For more-
    /people/sravya.talanki2/blog/2005/08/16/configuring-generic-sender-file-cc-adapter
    Thanks,
    Moorthy

  • Error in configuring File Sender Adapter with File Content Conversion

    Hi
    i am designing a File to File scenario using file content conversion in which the input is comma separated file and output is a XML document.
    mentioned below are the configuration information:
    Recordset Name: Substr
    Substr.fieldSeparator: ,
    Substr.endSeparator: 'nl'
    Substr.fieldNames: Name, Password
    Substr.keyFieldValue: Name
    and the error i can see in adapter framework is:
    Sender Adapter v0830 for Party '', Service 'FileContentConversion':
    Configured at 14:30:45 2005-04-07
    Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
    Mandatory parameter 'Substr.fieldNames': no value found
    plz help me ASAP.
    thanks and regards,
    Varun Joshi

    Hi Varun...
    Regarding ur error.....the name and password u send in csv is not getting recognised.. so u have to check the data type structure.
    there must be a recordset name and subelement must be recordset structure..the data type must be
    <datatypename>
          <recordsetname>
               <recordsetructurename>
                  <name>
                   <password>
    please try in this format and ur name and password will get recognised

  • Content conversion in Sender JMS Adapter

    Hi,
    Scenario is file to IDoc
    My source file is   ' ; ' separated file coming from MQ via JMS adapter. now  I need to convert this to XI.
    Source DT looks like
    Root
    HEADER  (Occurance 1)
         Field 1
         ISOCURCD
         TRANKODE
         IDENTIFIER
         DATO
         TIME
    DETAIL(Occurance 1 to unbounded)
         ISOCURCD
         TRANKODE
         EFFDATE
         COMMDATE
         DKKVAL1
         USDVAL1
    TRAILER(Occurance 1)
         ISOCURCD
         TRANKODE
          TRANCOUNT
    According to How to use content conversion in JMS guide from SDN i have configured the content conversion parameters in the module of JMS sender adapter.
    In the processing sequence  given the module name as localejbs/AF_Modules/MessageTransformBean and module Key as Plain2XML.
    And in module configuration
    Parameter Name                      Parameter Value
    Transform.Class                          com.sap.aii.messaging.adapter.Conversion
    Transform.ContentType                     text/xml;charset=utf-8
    xml.keyFieldName                          TRANKODE
    xml.keyFieldType                          CaseSensitiveString
    xml.recordsetName                          Root
    xml.documentName                                   MT_ROOT
    xml.documentNamespace                          http://XXX.XXX.XX/xi/XXXXX
    xml.processFieldNames          fromConfiguration
    xml.conversionType                                   StructPlain2XML
    xml.recordsetStructure          HEADER,1,DETAIL,*,TRAILER,1
    xml.HEADER.fieldNames           Field1,ISOCURCD,TRANKODE,IDENTIFIER,DATO,TIME
    xml.HEADER.fieldSeparator                     ";"
    xml.HEADER.keyFieldValue                     H
    xml.fieldSeparator                                      ";"(if i don't use this then the file is not being picked and getting an error in the CC monitoring of RWB saying xml.field separator missing.)
    Similarily for Detail and Trailer records as well.
    But when I run the scenario, the file is being picked up but I am not getting any payload into the inbound message.
    Can you please help me where I have configured wrongly. And one more thing will this configuration help for ; separated file .
    Thanks & Regards,
    Kumar
    Edited by: Kumar on Dec 19, 2007 11:11 AM
    Edited by: Kumar on Dec 19, 2007 11:15 AM

    HI,
    Have you gone through the below pdf i think it will help to find ur mistake.
    How to use conversion modules in JMS - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
    Thnx
    Chiarg

  • Problem when using keyfield in sender file content conversion

    Hi all,
    I am using FCC at sender side.
    My recordset structure is as follow::
    <MT_TW_TLOG>
      <Transaction>
       ---<SalesItem> 1...unbounded
           <XF_SOURCESYS>
           <XF_STORECODE>
           <XF_TYPE>
           <XF_VOIDFLAG>
       ---</saleItem>
       ---<SalesReturn> 1...unbounded
           <XF_SOURCESYS>
           <XF_STORECODE>
           <XF_TYPE>
           <XF_VOIDFLAG>
       ---</saleReturn>
       ---<SalesTotal>
           <XF_SOURCESYS>
           <XF_STORECODE>
           <XF_TYPE>
           <XF_VOIDFLAG>
       ---</saleTotal>
       ---<SalesTender> 1...unbounded
           <XF_SOURCESYS>
           <XF_STORECODE>
           <XF_TYPE>
           <XF_VOIDFLAG>
       ---</saleTender>
    </Transaction>
    FCC specification that i have used is::
    Recordset name::       Transaction
    Recordset Structure::  salesItem,,salesReturn,,salesTotal,1,SalesTender,*
    Recordset Sequencee::  
    Variable
    Key field name::XF_TYPE
    key fiel type::String(Case-sensitive)
    then i have given following information::
    salesItem.fieldnames ::all field names
    salesItem.fieldSeparator::,
    salesItem.keyFieldvalue::2
    salesItem.processFiledNames::fromConfiguration
    salesReturn.fieldnames ::all field names
    salesReturn.fieldSeparator::,
    salesReturn.keyFieldvalue::2
    salesReturn.processFiledNames::fromConfiguration
    salesTotal.fieldnames ::all field names
    salesTotal.fieldSeparator::,
    salesTotal.keyFieldvalue::2
    salesTotal.processFiledNames::fromConfiguration
    salesTender.fieldnames ::all field names
    salesTender.fieldSeparator::,
    salesTender.keyFieldvalue::2
    salesTender.processFiledNames::fromConfiguration
    My source file is a text file.
    So when i am transfering following data,
    scenario works fine.
    PCTW,TWS001,2,1
    PCTW,TWS001,2,10
    PCTW,TWS001,3,2
    PCTW,TWS001,1,3
    PCTW,TWS001,4,4
    Third field is my XF_TYPE.
    But if i change the order of records as follows::
    PCTW,TWS001,3,1
    PCTW,TWS001,3,10
    PCTW,TWS001,2,2
    PCTW,TWS001,1,3
    PCTW,TWS001,4,4
    It fails at adaper monitor and throws following error::
    2006-11-01 10:42:00 UTC: Error: Conversion of complete file content of 'try.txt' to XML format failed around position 0: Exception: ERROR consistency check in recordset structure validation (line no. 3: missing structure(s) before type 'SalesItem'
    Please provide some help on it.
    Thanks & Regards,
    Nilima

    Hi Nilima,
    Just go through this Weblog.
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    and specially the hilighted ( circled text ) in this and its description below.
    Hope this will be helpful
    Reward if helpful.
    Regards
    Sachin

  • File adapter content conversion

    Hi all,
      We are having File to File Scenario
      We are facing problem in Content conversion in File
      Adapter(Sender)
      The source file is in text format and fields are
      seperated by '|' character
      The source file structure is :
      Header|No. of Records
      Data Record1 
      Data Record2
      Data Recordn
      Trailer|No. of Records
         where Data Recordn is of type Field1|Field2|Field3|Field4
         and the number of data records is variable
         e.g.
         Header|5
         2|144012|20050801|20050801
         212|012|20050801|20050801
         244012|2|20050801|20050801
         2144|144012|20050801|20050801
         212|012|20050801|20050801
         Trailer|5
      Now , we need to ignore the contents of Header and Trailer Records
         For Header , we are setting the property Document Offset to 1
         Hence the Header record is ignored
         However , we are facing problems in ignoring the Trailer record
         We want to know :
         1. Is there a direct way ( or some propety ) wherein we can ignore the last record of the file ,
            which in this case is Trailer record
         2. We also tried the following :
              a. We set the Recordset Structure to : row,*,trailer,1
              b. However in this case , the keyField is required for row ;
                 but since the number of data records is variable ,
                 the keyFieldValue cannot be specified
           How should we go about in this case
    Please guide us on this
    Regards
    Shikha

    Hi all
    Thanks for replies
    Actually , we are able to ignore header and that is not an issue
    Now if we need to discard the trailer record , we believe that RecordSet Structure should be <b>row,,trailer,1</b> or <b>header,1,row,,trailer,1</b>
    However , since structure is <b>row,*</b> ; we need to specify the <b>keyField</b> column for row ( data records )
    Since <u>number of data records</u> is variable , we are not able to set the <b>keyFieldValue</b> for <u>row ( data record )</u>
    Can you'all please guide us on this as we are stuck on this .
    Regards
    Shikha
    Message was edited by: Shikha Jain

  • 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

  • File Content Conversion in Sender Adapater

    Hi Folks ,
    I am doing a file 2 file scneario using content conversion at  both end
    My i/p and o/p is file is tab delimited
    My source xml structure is
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:file_sender_mt xmlns:ns0="urn:filetofiledemo">
       <recordset>
          <data1>
             <keyfield/>
             <age1/>
          </data1>
          <data>
             <name/>
             <keyfield/>
             <age/>
             <loc>
                <keyfield/>
             </loc>
          </data>
       </recordset>
    </ns0:file_sender_mt>
    Data and location have the mapping 1.. unbounded
    while data1 has the mapping 1.1
    When I am trying to read it as a tab delimited flat file.
    These are the parameters that i have set
    Document Name  file_sender_mt
    Document Namespace urn:filetofiledemo
    Recordset Name recordset
    Recordset Structure data1,1,data, ,loc,
    Key Field Name keyfield
    data1.fieldNames keyfield,age1
    ignoreRecordsetName true
    recordset.fieldSeparator '0'
    data1.fieldSeparator '0x09'
    data1.keyFieldValue 01
    data1.endSeparator '0'
    data.beginSeparator '0x09'
    data.fieldSeparator '0x09'
    data.fieldNames name,keyfield,age
    data.keyFieldValue 02
    loc.fieldSeparator '0x09'
    loc.beginSeparator '0x09'
    loc.endSeparator '0'
    loc.keyFieldValue 03
    loc.fieldNames keyfield
    My file is getting picked up . I dont see any message in message monitoring and neither anything in moni .
    No error in adapater
    but the file is not getting created .
    if i change the message protocol to file and send t above xml file . the scneario works fine
    any reasons for the above behaviour
    Thanks
    Amit

    I have found you cant use nested element in sender adapater
    so i have chnage my source structure to
    Now if i give my i/p file as
    01 age1
    02 25 03
    file is getting pciked up
    bt if i give it as
    01 age1 02 25 03
    which is the structure i expect my i/p file it is failing  to read with the error
    Error: Conversion of complete file content to XML format failed around position 0: Exception: ERROR converting document line no. 1 according to structure 'data1':java.lang.Exception: ERROR in configuration: more elements in file csv structure than field names specified!
    Does The special character ´0´ is not a separator character.
    not work for sender adapater bcoz in reciever i am able to get o/p in one line and tab delimited
    any idea
    and since i have given my keyfield as the second field in data
    02 would come at the second palce
    Thanks
    Amit

  • 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

Maybe you are looking for