When should message protocol be FILE CONTENT CONVERSION

HI one and all,
What doubt keeps haunting me is when should message protocol be selected FILE CONTENT CONVERSION.
for what format of sender information IS THIS USED ?
Ur answer is awaited.
Thanking you,
Ranjith.

Ranjith,
Consider the below cases u are sending XML file as
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Test_MT xmlns:ns0="urn:test">
   <EmpProfile_Msg>
      <Empno>1001</Empno>
      <EmpName>J</EmpName>
      <DepartmentName>SAP</DepartmentName>
   </EmpProfile_Msg>
</ns0:Test_MT>
But while writing the output u need the file as
1000 , J, SAP
Then u have to go for File Content Conversion at the Receiver adapter.
Similarly ,consider the other way around u are sending the file input as
1000 , J, SAP   and u want XML , then u have to do FCC in sender adapter.
Hope it clears!!!
Best regards,
raj.

Similar Messages

  • 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

  • 'nl' Not Working for fieldSeparator in File Content Conversion

    I have a receiver communication channel where I want to create a file with each field being a new line.  The xml (Message Protocol: File) output looks like this:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:complus_receiver_messageType xmlns:ns0="http://graybar.com/test/complus_rec
    eiver"><cp><myrequest>AAFADFASFADFADSFDASFADFAAA</myrequest><myheader>DELADV</myheader></cp></ns0:complus_receiver_messageType>
    When I turn on Message Protocol of File Content Conversion, and follow the SAP documentation on the parameters, the 'nl' is getting sent literally.
    - I have Recordset Structure of: cp
    - I have content conversion parameters of:
    cp.fieldSeparator 'nl'
    cp.fieldNames myrequest,myheader
    cp.addHeaderLine 0
    My file output looks like this:
    AAFADFASFADFADSFDASFADFAAA'nl'DELADV0001
    Note that the 'nl' is not processing as a new line.  Ideas?

    Hi,
    Receiver FileContent conversion params dosen't have <b>fieldNames</b>
    cp.fieldNames myrequest,myheader
    so why don't u remove this and try once again...
    Recordset Structure of: cp
    cp.addHeaderLine 0
    cp.fieldSeparator 'nl'
    Hope this weblog helps you...
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    Cheers,
    Siva Maranani.

  • File content  conversion is not creating the exact strcuture as Datatype

    Hi,
    We are facing issue .
    I have  sender DT type
    <FIle_DT>
    < HeaderDetail>
          <Field1>
            <Field2>
                          <Linietemdetails>
                                                        <Field1>
                                                    <Field2>
    </Linietemdetails>
    </ HeaderDetail>
    </File_DT>
    but when I am preocessing  the file content conversion - > when its pulling the data  from  the file this structure become
    <FIle_DT>
    < HeaderDetail>
          <Field1>
            <Field2>
    </ HeaderDetail>
                         <Linietemdetails>
                          <Field1>
                          <Field2>
                      </Linietemdetails>
    </File_DT>
    I want  same  above one after content conversion. I tired allt he options availble . please  help
    In file content conversion   I give 
    RecordSet Structure -->HeaderDetail,,LineItemDetail,
    HeaderDetail.keyFieldValue     H
    HeaderDetail.endSeparator     'nl'
    HeaderDetail.fieldFixedLengths     1,4,8,25
    HeaderDetail.keyFieldInStructure     ignore
    LineItemDetail.keyFieldValue     L
    LineItemDetail.endSeparator     'nl'
    LineItemDetail.fieldFixedLengths     1,3,1,10,10,24,3,25
    LineItemDetail.keyFieldInStructure     ignore
    LineItemDetail.keepIncompleteFields     YES
    ignoreRecordsetName     true
    Please help
    regards
    Ram

    Hi Babu,
    Thanks a lot for your input.
    Actually My requirement is this its file to Multiple idoc scenarios.
    Here I am getting flat file HeaderDetails and LinItemdetails. its having Multiple Headerdetail then Line Item Details, I want to create idoc  for each HeaderDetail and all the Next LineItemdetails should go to that IDoc.  If we can find some solution then it will also  work for me.
    For ex.
    My source would be
    FIle_DT>
    < HeaderDetail1>
    <Field1>
    <Field2>
    </ HeaderDetail>
    <Linietemdetails11>
    <Field1>
    <Field2>
    </Linietemdetails11>
    <Linietemdetails12>
    <Field1>
    <Field2>
    </Linietemdetails12>
    < HeaderDetail2>
    <Field1>
    <Field2>
    </ HeaderDetail>
    <Linietemdetails21>
    <Field1>
    <Field2>
    </Linietemdetails21>
    <Linietemdetails22>
    <Field1>
    <Field2>
    </Linietemdetails22>
    < HeaderDetail3>
    <Field1>
    <Field2>
    </ HeaderDetail>
    <Linietemdetails31>
    <Field1>
    <Field2>
    </Linietemdetails>
    </File_DT>
    I want target structure like this .
    <Idoc>
    <HeaderDetail1>
    <LineItemdetail11>
    <LineItemdetail12>
    <LineItemdetail13>
    </Idoc>
    <Idoc>
    <HeaderDetail2>
    <LineItemdetail21>
    <LineItemdetail22>
    <LineItemdetail23>
    </Idoc>
    <Idoc>
    <HeaderDetail3>
    <LineItemdetail31>
    </Idoc>
    If anyway you can help me how to go and how to do this grouping then it would be really great for me.
    regards
    ram

  • 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

  • Purpose of message protocol file and file content conversion

    hi
       i am currently working in idoc to file scenario, 
          In what cases we will go file and file content conversion in message protocol for file adapter.
    can anyone specify the real significance of it? bcoz this may help me and continue my scenario in its suitable path.
    Regards
    Saravanakumar PK

    Hi,
    In XI (internal) all XML message are based on the XI Message Protocol.
    See: http://help.sap.com/saphelp_nw70/helpdata/en/b6/0b733cb7d61952e10000000a11405a/frameset.htm
    XI Protocol is nothing but an SAP XI extension of SOAP protocol and SOAP protocol is nothing but a SOAP request in a HTTP protocol. SOAP request is nothing but SOAP extension of an XML message. Hence finally it drill downs to the fact that XI message is in fact an XML message with some extra information in the header which are SAP specific like the SAP Runtime, SAP Hoplist, etc...
    File Content Conversion
    Integration Engine understands only XML messages.Now if u r handling normal text file such as 'tab separated' file,'# separated' file, or a CSV file, you need to convert the content of the file to XML and File Content Conversion mechanism helps to do this job.This File Content conversion mechanism(option)is present with the File Adapters.both Sender and Receiver.
    How to do FCC:
    http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    /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/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/2006/04/03/xi-in-the-role-of-a-ftp
    Thanks
    Swarup

  • File content conversion record set per message

    Dear All,
    Problem:- File is of huge size because of which file content conversion is taking longer time and is failing.
    File format:-
    Header
    Detail
    Detail
    Header
    Detail
    Detail
    Detail
    Detail
    Header
    Detail
    Detail
    Trailer
    Trailer has total count of all detail record,header record and there are few checks as well as wrt other fields.
    We need to do all the above validation on the file and if it successful it shud process it otherwise alert shud be raised.
    As a step:-
    I have used record set per message for splitting up the file because of huge size this functionality is working fine but because of spitting of file i am not able to do trailer validation as XI is creating multiple records with different message ID's
    Is any other approch which will help to achieve both Spliting as well as validation
    chirag

    Chirag,
    simplest scenario I can think of is splitting the 2 reqs.
    1. create 2 folders, one for "in process" files and other for "validated" files.
    2. create 2 scenarios:
    2.1. your current sender system to in process folder (whatever to File).
           => In this you just do the validation, without FCC. You could create a simple module for that or even do it at mapping runtime, as you said (mapping may be easier to handle errors), and throw a runtime exception (which will eventually trigger an alert).
           => At the end, only files that go successfully throug the validation will be located in the "In Process" folder.
    2.2. do a simple file to file scenario (from "In Process" to "Validated" folder), this time executing FCC & splitting messages if necessary.
    Of course, this will only work if the module/mapping is able to process the large file anyway (hopefully yes, since it will still be a flat file and not XML yet).
    BR,
    Henrique.

  • Issue w/ File content conversion (Receiver side)

    Folks, there seems to be an issue with the conversion. I've read several of threads on this forum, but none helped! Although the file is generated with 8 bytes there seems to be nothing in the file.
    However when 'File' message protocol is used, the xml file is generated correctly as expected. All my other settings are fine.
    Here is the scenario:
    1) created Message type -
    MTX
    ..Material
    ..BaseUnit
    ..MatGrp
    ..Division
    2) comm. channel created for -
    Transport protocol: File (NFS)
    Message protocol: File content conversion
    Recordset Structure: MTX
    parameters:
        MTX.fieldSeparator: ,
        MTX.endSeparator: 'nl'
    Should recordset struc. and parameters have 'ns0' prefix, i.e.,
    Recordset Structure: ns0:MTX
    parameters:
        ns0:MTX.fieldSeparator: ,
        ns0:MTX.endSeparator: 'nl'
    What esle is missing? any thoughts are welcome.
    Thanks and appreciate your responses.

    Hi ABAP JUNOON,
    Could you please create another Test scenario and
    try
    MTI_XXX
         - DATA(0..unbounded)
             - fields?
    i mean, without redundant RS(Record Structure).
    and use 
    Transport protocol: File (NFS)
    Message protocol: File content conversion
    Recordset Structure: DATA.
    it will written the complete output file.
    some people create the Reciver data type for  test scenario's as follows.
    MTI_XXX
       -RS
         - DATA(0..unbounded)
             - fields?
    i mean with redundant RS
    in this case file is generated, but nothing will be appear.
    so plz take care while creating the reciver data type with FCC.
    and the following case also will work i.e
    MTI_XXX
       -RS
         -Header(0,1)
             - fields?
         - DATA(0..unbounded)
               - fields?
         - Trailer(0,1)
             - fields?
    Regards
    Mahesh.

  • Receiver File Content Conversion concerns

    Dear SAP experts,
    Need your advise regarding File Content Conversion.
    I have here the XML,
    <?xml version="1.0" encoding="UTF-8" ?>
    <ns0:CSV xmlns:ns0="http://pg.com/xi/tom/connect/edi">
    <SLI_root> ---> this is the root node of 'CSVFileName' and 'SLI'
    <CSVFileName>Globus_20080306</CSVFileName>
    <SLI> ---> this is the root node of the below fields
    <PERIO>20071222</PERIO>
    <EAN>737052018164</EAN>
    <ILN>4304452000004</ILN>
    <SALES>16</SALES>
    <TURNO>120</TURNO>
    <PERFL>W</PERFL>
    <SUBSFL>X</SUBSFL>
    <SALUN>ST</SALUN>
    <CURRENCY>EUR</CURRENCY>
    <STOCK>000000000</STOCK>
    <STOUN>ST</STOUN>
    </SLI>
    <SLI>
    <PERIO>20071222</PERIO>
    <EAN>737052018232</EAN>
    <ILN>4304452000004</ILN>
    <SALES>3</SALES>
    <TURNO>38.699997</TURNO>
    <PERFL>W</PERFL>
    <SUBSFL>X</SUBSFL>
    <SALUN>ST</SALUN>
    <CURRENCY>EUR</CURRENCY>
    <STOCK>000000000</STOCK>
    <STOUN>ST</STOUN>
    </SLI>
    <SLI>
    </SLI_root>
    </ns0:CSV>
    CSV --> The Message Type of the XML.
    SLI_root is under CSV
    CSVFileName and SLI are under SLI_root
    PERIO, EAN, ILN.. etc. are under SLI
    SLI_root is under CSV.
    CSVFileName and SLI are under SLI_root.
    PERIO, EAN, ILN,... fields are under SLI.
    The parameters i've set in Content Conversion are:
    Recordset Substructure: SLI_root,SLI
    SLI_root.endSeparator: 'nl'
    SLI_root.fieldSeparator: 'nl'
    SLI.addHeaderLine: 3
    SLI.headerLine: PERIO;EAN;ILN...
    SLI.fieldSeparator: ;
    My output should be,
    PERIO;EAN;ILN;SALES;TURNO;PERFL;SUBSFL;SALUN;CURRENCY;STOCK;STOUN
    20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;00000000;ST
    20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;00000000;ST
    20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;00000000;ST
    The parameters i've set in Content Conversion are:
    SLI_root.endSeparator: 'nl'
    SLI_root.fieldSeparator: 'nl'
    SLI.addHeaderLine: 3
    SLI.headerLine: PERIO;EAN;ILN...
    SLI.fieldSeparator: ;
    SLI.endSeparator: 'nl'
    When i've run my scenario, the output is this,
    Globus_20080306;20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;000000000;ST
    20071222;737052018232;4304452000004;3;38.699997;W;X;ST;EUR;000000000;ST
    20071222;737052018263;4304452000004;1;12.9;W;X;ST;EUR;000000000;ST
    20071222;737052018294;4304452000004;1;10.45;W;X;ST;EUR;000000000;ST
    The header lines are not present and the value of CSVFileName (Globus_20080306) was inserted in my values.
    Kindly advise what is wrong on my parameters set.
    Or is there something missing in my configs.
    Or i will change my structure of XML ?
    Thank you very much!
    Fred

    Hi Raj,
    Im just 4months working in SAP XI, and i still consider myself as a beginner.
    I've only used Receiver File Adapter in my scenario (NO Sender File Adapter)
    These are the configurations i've made in the Receiver File Comm Channel.
    For the Parameters TAB:
    File Receiver
    Transport Protocol: File System (NFS)
    Message Protocol: File Content Conversion
    Adapter Engine: Integration Server
    File Access Parameters:
    Target Directory: * specified directory
    File Name Scheme: .csv
    Processing Parameters:
    File Construction Mode: Create
    Write Mode: Directly
    File Type: Text
    Adapter-Specific Message Attributes
    - Use Adapter-Specific Message Attributes
    - File Name
    Run Operating System Command After Message Processing
    Command Line: chmod 664 %F
    Content Conversion Parameters:
    Recordset Structure: SLI
    SLI.addHeaderLine: 3
    SLI.headerLine: PERIO;EAN;ILN;....
    SLI.field Separator: ;
    SLI.endSeparator: 'nl'
    Adapter Status: Active
    For the Identifiers TAB: (i've had no configs on that)
    For the Module TAB:
    Processing Sequence:
    Number: 1
    Module Name: CallSapAdapter
    Type: Local Enterprise Bean
    Module Key: 0
    That's all in my configs in Receiver File Adapter.
    Is it ok if you check this?
    I've read a SAP Blogs, https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/6400. [original link is broken] [original link is broken] [original link is broken]
    I've read in it that there must be set-up in the Module TAB to get the Filename in the Dynamic Configuration.
    Kindly advise.
    Thank you very much for your usual support.
    Fred

  • 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

  • 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

  • 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

  • File Content conversion - IDOC to Fixed length File

    Hi,
    Scenario : SAP R/3(IDOC) -> XI -> Fixed Length file
    IDOC is sending from SAP R/3, XI has to do the mapping and send a Fixed length File to /tmp in XI.
    When I am using the message Protocol as "File" in the Receiver communication channel, XML file is writing to /tmp. When I am using "File Content Conversion" as a message protocol,Empty File is writing. Can anybody tell me why empty file is creating. Can we use File content Conversion in this scenario. Is there any additional parameter or settings required?
    Receiver communication channel settings:
    Message Protocol: File Content Conversion
    File type       : Binary
    Recordstructure : MT_V_PER01
    Name                             Value
    MT_V_PER01.fieldFixedLengths     25,35
    MT_V_PER01.fieldNames            PERSNR,NAME
    File Data Type : DT_V_PER01,
    Message type   : MT_V_PER01
    IDOC type      : WP_PER01.
    Expecting your expert advice.
    Thanks
    vineesh

    Hi Moorthy,
    I am getting success messages in Audit log as below:
    2006-09-29 12:08:53 Success Trying to put the message into the send queue.
    2006-09-29 12:08:53 Success Message successfully put into the queue.
    2006-09-29 12:08:53 Success The message was successfully retrieved from the send queue.
    2006-09-29 12:08:53 Success The message status set to DLNG.
    2006-09-29 12:08:53 Success The message was successfully transmitted to endpoint http://nslcxi08:8010/sap/xi/engine?type=entry using connection AFW.
    2006-09-29 12:08:53 Success The message status set to DLVD.
    2006-09-29 12:08:53 Success The message was successfully delivered.
    I have checked the Payload maindocument,the IDOC structure contains data.
    <?xml version="1.0" encoding="UTF-8" ?>
    - <WP_PER01>
    - <IDOC BEGIN="1">
    - <EDI_DC40 SEGMENT="1">
      <IDOCTYP>WP_PER01</IDOCTYP>
      <MESTYP>WP_PER</MESTYP>
      <STDMES>WP_PER</STDMES>
      <SNDPOR>SAPLCD</SNDPOR>
      <SNDPRT>LS</SNDPRT>
      <SNDPRN>LCDCLNT210</SNDPRN>
      <RCVPOR>LXDCLNT250</RCVPOR>
      <RCVPRT>LS</RCVPRT>
      <RCVPRN>LXDCLNT250</RCVPRN>
      </EDI_DC40>
    - <E1WPP01 SEGMENT="1">
      <PERSNR>0000100006</PERSNR>
    - <E1WPP02 SEGMENT="1">
      <NAME>Consumer</NAME>
      </E1WPP02>
      </E1WPP01>
      </IDOC>
      </WP_PER01>
    Thanks
    Vineesh

  • Problem in file content conversion from XML to CSV

    Hi Experts,
    I am finding problem in file content conversion. I need to convert the following XML file into CSV file:
      <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_CROSS_REF xmlns:ns0="urn:dabur:idoc2file:pos">
          <Update_type>2</Update_type>
          <PLU>00000000</PLU>
          <Cross_ref_PLU>7777777</Cross_ref_PLU>
          <Capture_PLU />
          <Package_size />
          <Package_desc />
      </ns0:MT_CROSS_REF>
    The output file data has to be like:
    2,00000000,7777777,,,,
    The problem I am facing is while specifying the content conversion parameters in communication channel i dont know what recordset structure i should mention as all the records are directly under root. If I mention recordset structure as "ns0:MT_CROSS_REF" and parameters as
    ns0:MT_CROSS_REF.fieldSeparator   ,
    ns0:MT_CROSS_REF.endSeparator    'nl'
    i get error in communication channel monitoring and no file is posted.
    Please help me as to what correct parameter i should mention in my case.
    Thanks,
    Regards,
    Yash

    Hi Chirag,
    I cannot change the xml file as it comes after mapping idoc to a message type. How can I add ROOT in the xml? My message type is like MT_CROSS_REF and it has those 6 fields as in the XML (Update_type, PLU etc.). I do the mapping of these fields from a IDOC and get the XML.
    I hope you got my point.
    Thanks,
    Yash

  • 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

Maybe you are looking for