Adapter file Receive - conversion file problem

Hi everybody,
In an adapter file receiver, I want to convert an XML structure to a "flat file".
here is my xml structure
<ns1:MT006_blabka>
  <RECORD>
    <LIGNE>TEST1</LIGNE>
    <LIGNE>TEST2</LIGNE>
  </RECORD>
  <FILE>
     <FILENAME>fichier.dat</FILENAME>
     <DIRECTORY>//server1/root/</DIRECTORY>
   </FILE>
</ns1:MT006_blabla>
and the text file I want to receive is
<BOF>
TEST1
TEST2
<EOF>
The problem is with the paramter of conversion I use I receive
<BOF>
TEST1
TEST2
<EOF>
I always receive an empty line at the end
The record set define in conversion are "RECORD,FILE"
in parameter i put
RECORD.fieldSeparator      value :  'nl'
FILE.fieldFixedlengths  value : 0,0
My problem is to eliminate the empty line at the end of the file.
Is there someone who can help me ?
Thank you in advance for your collaboration.
Regards
Eric.

Hi,
You will have to modify your target structure from this
<ns1:MT006_blabka>
<RECORD>
<LIGNE>TEST1</LIGNE>
<LIGNE>TEST2</LIGNE>
</RECORD>
<FILE>
<FILENAME>fichier.dat</FILENAME>
<DIRECTORY>//server1/root/</DIRECTORY>
</FILE>
</ns1:MT006_blabla>
To this
<ns1:MT006_blabka>
<RECORD>
  <Struct>
      <LIGNE>TEST1</LIGNE>
       <LIGNE>TEST2</LIGNE>
</Struct>
</RECORD>
<FILE>
<FILENAME>fichier.dat</FILENAME>
<DIRECTORY>//server1/root/</DIRECTORY>
</FILE>
</ns1:MT006_blabla>
use the content conversion as
recordset structure = RECORD,Struct,File,
Record.fieldSeparator = 'nl'
Struct.fieldSeparator = 'nl'
file.fieldFixedLengths =  0
file.fixedLengthTooShortHandling = Cut

Similar Messages

  • File receiver - Get file size

    Hi all,
    In my scenario, the message mapping is such that the target message may or may not have child nodes created depending on certain conditions. I am using file receiver channel to write this target message as xml file on another server.
    The issue I am facing is - suppose child nodes are not created, the target message has only root node, and nothing else. i.e. it is empty.
    But still the file gets written on destination, because file adapter doesn't seem to have intelligence to look into the payload. So I have to manually delete such 'almost-empty' files.
    Although PI 7.0 has feature of ignoring empty files, the file I am talking of is really not of 0 kb size, as it contains namespace and root node tag. It has very small size of 1 kb, this is fixed and thus the file is easily distinguished from other larger files which contain child nodes. File size is a parameter that can be certainly used as a key here, but don't know how.
    Does anyone have any idea on -
    1) How to check file size before file receiver adapter writes it,
    2) How to prevent such file from getting written, or
    3) run a script which can detect the file size and delete them periodically / or every time file receiver writes files ?
    Regards,
    - Shankar.

    Hi,
    We have an option of empty file handling in receiver file adapter..
    <i>      Select the Handling of Empty Messages:       Write Empty File
    An empty file (length 0 bytes) is put in the target directory.
           Ignore No file is put in the target directory.</i>
    But your case namespace and root node only are available you said.
    In this type of situations ..
    We can handle in the following way..
    If target side root node having the recordset node
    root
      recordset 0..unbound
         child1 0.1
         child2   0.1
    Then create a UDF
    map from left side one node -
    exists --- UDF ---to right side root node
    In UDF
    //handle business logic and
    ....ResultList.SUPPRESS.
    if your target side does not have any recordset type of structure then..
    In messages tab change the occurrences of msg to 0..unbound and use the above UDF.
    Regards
    Chilla..

  • Problem in file content conversion, file 2 xml scenario

    Hi,
    Could some one help me in finding out the error in my file to xml scenario, please do consider the following things what I did for this scenario.
    1.My sender file structure is flat file with , seperated 4 fields. On receiver end expecting xml file.
    2.Did file content conversion at sender file adapter and given parameters as follows.
         Document name             : MT_FileInput
         DocumentnameSpace     : http://file/praveenworkshop
         Recordset Name             : DT_Record
         Recordset Structure        : DT_Row,*
         KeyfieldType                   : String( default)
        DT_Row.fieldnames          : FirstName,LastName,City,PostCode
        DT_Row.fieldSeparator      : ,
        DT_Row.processConfiguration: FromConfiguration
        Dt_Row.endSeparator       : 'nl'
    3. I did check in Adapter Monitor that Both Sender and receiver adapter are showing green and It was showing  'Adapter is up and running: But no messages processed'
    4. I did check the SXMB_MONI which was showing " Scheduled for Outbound processing"
    5. In SXMB_MONI outbound processing payload was picking up the file and also inbound processing showing the same.
    6. my source folder and destination folder are very simple c:/praveenfiles/input and c:/praveenfiles/output
        files are source file praveen.txt and destination file praveenOP.xml
    Please help me in finding out the error to see the output file in my output folder.

    Hi Praveen,
    Hope these bloga are useful to you..
    File content conversion sites
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    /people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
    /people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    /people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
    /people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
    /people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
    /people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
    Thanks,
    Satya

  • Skip field in file content conversion (file adapter)

    hy guys,
    I have a log file and want to convert it into xml. that works fine.
    the problem is: can I skip some fields that I do not need in the xml with file content conversion
    the fields I want to skip are the same in every record of the log file.
    thanks.

    Ralf,
    You can only ignore lines in the begiining of the file using Document Offset option.
    If you have the unwanted field in the end of the record and you are in SPS12 (PI 7.0), you can use the option additionalLasstFields in FCC parameters. have a look into the blog /people/sukumar.natarajan/blog/2007/06/12/content-conversion-in-sender-file-adapter--2-new-useful-parameters
    Easier, is to ignore those fields in mapping.
    Also, you can try to remove those fields using a shell script which can be called from the File adapter.
    Regards,
    Jai Shankar

  • XI File Adapter sending/receiving zip files

    Can the XI File Adapter create a zip file to send outbound from XI and/or can it also translate a zip file inbound into XI?

    Hi Kirk.
    What you can do is use the OS command option on the adapter in order to unzip the file after the File\FTP adapter completes its file transfer to the specified path.One of my colleagues used a freeware zip app. that excepts an os command actions.
    I know it works for file receiver but not sure about the sender. check SAP Note 801926 for more sender adapter parameters.
    Regards
    Nimrod Gisis

  • File Receiver - Writing files

    Hi,
    I have a scenario in which i have picked up 2 files using the file sender.
    eg:
    xi_input.xml     -
    > main payload
    xi_input.pdf      -
    > attachment
    When i use the File receiver adapter i want to write only the attachment to the targer folder.
    Is this possible ?
    Regards,
    Vignesh

    Thanks Bavesh.
    I am also seding both the files to a SOAP rreceiver also.
    In that case also I dont want the main payload to be transfered.
    the fiel xi_input is only used 2 trigger the scenario.
    In the case of SOAP receiver we dont have to do any swapping right ?
    I really dont care if the main payload reached the destination.
    Will the SOAP receiver adapter take the attacment and dump the main payload
    Regards,
    Vignesh

  • File Content Conversion: Sender Problem

    Hi,
    I'm getting a very typical error in my Sender Communciation channel.
    Channel CC_FILE_SENDER_2: Empty document found. Proceed without sending message
    I've gone through a few threads and I know that the problem is with the Key Field and using * in the Recordset Structure but I cannot solve it. If I use * in the Recordset structure it fails,when I use a specific number it works. Any ideas
    Here is my Communication Channel details
    Document Name: MT_SENDER
    Document namespace: http:\\sender
    Recordset Structure: FileHeaderRecord1,1,FileHeaderRecord2,1,FileHeaderRecord3,1,FileDetailRecord,*,FileTrailerRecord1,1
    Recordset Sequence: Ascending
    Key Field Name: RType
    And the configuration:
    FileHeaderRecord1.fieldNames:             RType,Filler,Code,Filler2
    FileHeaderRecord1.fieldFixedLengths:  10,31,6,69
    FileHeaderRecord1.keyFieldValue:         V 
    FileHeaderRecord2.fieldNames:            RType,Filler
    FileHeaderRecord2.fieldFixedLengths:  3,113
    FileHeaderRecord2.keyFieldValue:        HDR1
    FileHeaderRecord2.fieldNames:            RType,Filler,Date,File,Filler2,Num,Filler3
    FileHeaderRecord3.fieldFixedLengths: 3,2,5,6,21,3,76
    FileHeaderRecord3.keyFieldValue:        UH1
    FileDetailRecord.fieldNames:                 RType,Filler,TCode,Filler1,Amount,Filler2,ZGC,Filler3,Date,Filler4
    FileDetailRecord.fieldFixedLengths:       14,1,2,18,11,18,9,28,5,10
    FileDetailRecord.keyFieldValue:             9
    FileTrailerRecord1.fieldNames:              RType,Filler,TCode,Filler1,Date
    FileTrailerRecord1.fieldFixedLengths:   14,1,2,12,5
    FileTrailerRecord1.keyFieldValue:          UT1
    ignoreRecordsetName:                           true
    This is a copy of my file....
    VPR456SCL1                               852086                                                                               
    HDR1 SED456RD  345344500428            F     04 094520428     BS   09452                                                       
    UHL1 09452ESBCL1    00000000         004                                                                               
    85208681123787085              000000000000500FREW RTYU POSWS123704375                            09452                     
    85208681123787085              000000000000600FREW RTYU POSWS123705307                            09452                     
    85208681123787085              000000000000600FREW RTYU POSWS123705671                            09452

    Hi,
    problem is in your keyfield value,
    FileHeaderRecord1.fieldNames:             RType,Filler,Code,Filler2
    FileHeaderRecord1.fieldFixedLengths:  10,31,6,69
    FileHeaderRecord1.keyFieldValue:         V
    keyfield name is RType and it is given a fixedlength of 10 characters, but your keyfieldvalue is "V
    " which is not 10 char long that is the reason your adapter is failing to pick it.
    same for all the other recordsets, the fieldvalue shd match the fixed length given.
    Eg:- give keyfieldvalue like this "V         ". it will work.

  • File Content Conversion Mapping problem

    Hi,
    I tried a file to file simple scenario using FCC on the Sender Side,but I repeatedly get a message mapping error.
    I tried changing the different parameters in filesender file adapter, checked message mapping for errors .
    1.My Mapping is Correct.
    2.The parameters in the FCC are correct.
    Is there any way where we can debug the the Message Error.
    Regards,

    HI,
    but I repeatedly get a message mapping error.
    what error message ur getting.
    what is ur file strucutre
    what FCC u r using.
    give me the details
    chirag
    Hi,
    These are the following details:
    1.error message: There is an exception in mapping
    2. File structure: A comma separated text file
                   e.g : Somya, 24.
    3. I am using sender file FCC.
    My data type is as follows:
                         FileInput
                             Recordset
                                 Row
                                      Name
                                      Age
    The Sender FCC used is:
                              Document Name: FileInput
                              Recordset Name: Recordset
                              Recordset Sturcute: Row,*
               Row.fieldNames:  Name,Age
               Row.fieldSeparator: ,
               Row.endSeparator: 'nl'.          
    Do Help.
    Regards,

  • File content conversion (file to file)

    Hi Guys,
    Sender File
    @! is the delimiter
    LEVEL1@!227833338@!08710@!REPAIR@!20080101@!99990909@!0000212897@!0000000001000@!0000000500000@!R400@!A@!Assigned
    LEVEL2@!227833338@!08710@!000099071608@!Blind@!20020115@!20020115@!R400@!1@!3@!20020430@!99990909@!SLC-@!VESSELLS@!A@!Assigned
    LEVEL3@!227833338@!08710@!000099071608@!0010@!Blind@!20020115@!20020115@!20020430@!20020430@!10000414@!Assigned
    LEVEL1@!4501065777@!00010@!SUPERHEAT@!20071206@!99990909@!0000219169@!00000001000@!0000002000000@!R020@!A@!Assigned
    LEVEL2@!4501065777@!00010@!000009416742@!Alky@!20080107@!99990909@!R020@!E@!2@!20080101@!99990909@!LAT@!COKE@!A@!Assigned
    LEVEL3@!4501065777@!00010@!000009416742@!0010@!v-895@!20080107@!99990909@!20080101@!99990909@!10001577@!Assigned
    Sender Structure
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:CostObjects xmlns:ns0="http://*****************">
       <LEVEL1>
          <LevelID/>
          <PONumber>35435454</PONumber>
          <POLineNo>545</POLineNo>
          <ShortText>AAAAAAA</ShortText>
          <StDate>20080101</StDate>
          <EndDate>20080101</EndDate>
          <Vendor/>
          <POValue/>
          <ExpectedValue>4343</ExpectedValue>
          <Plant/>
          <Status>A</Status>
          <OrderType>Assigned</OrderType>
       </LEVEL1>
       <LEVEL2>
          <LevelID/>
          <PONumber>35435454</PONumber>
          <POLineNo>545</POLineNo>
          <Level2ID>457899</Level2ID>
          <Level2Desc>bbbbbbbbb</Level2Desc>
          <L2StDate>20080101</L2StDate>
          <L2EndDate>20080101</L2EndDate>
          <L2Plant>y001</L2Plant>
          <L2Priority>3</L2Priority>
          <L2SAPStatus>a</L2SAPStatus>
          <L2ActStDate>20080101</L2ActStDate>
          <L2ActEndDate>20080101</L2ActEndDate>
          <L2FuncLoc>LAR</L2FuncLoc>
          <L2FuncDesc>LOS ANGLES</L2FuncDesc>
          <L2Status>1</L2Status>
          <L2OrderType>Assigned</L2OrderType>
       </LEVEL2>
       <LEVEL3>
          <LevelID/>
          <PONumber>35435454</PONumber>
          <POLineNo>545</POLineNo>
          <Level2ID>457899</Level2ID>
          <Level3ID>10</Level3ID>
          <Level3Desc>cccccccc</Level3Desc>
          <L3StDate>20080101</L3StDate>
          <L3EndDate>20080101</L3EndDate>
          <L3ActStDate>20080101</L3ActStDate>
          <L3ActEndDate>20080101</L3ActEndDate>
          <L3WorkCenter>los</L3WorkCenter>
          <L3OrderType>Assigned</L3OrderType>
       </LEVEL3>
    </ns0:CostObjects>
    Receiver Structure
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:TCostObject xmlns:ns0="http://**************">
       <LEVEL1>
          <L1RecordIndicator>&lt;L1&gt;</L1RecordIndicator>
          <L1ID>35435454545</L1ID>
          <L1Desc>AAAAAAA</L1Desc>
          <L1StartDate>20080101</L1StartDate>
          <L1EndDate>20080101</L1EndDate>
          <L1Hours>0</L1Hours>
          <L1Costs>4343</L1Costs>
          <L1Status>A</L1Status>
          <L1OrderType>Assigned</L1OrderType>
       </LEVEL1>
       <LEVEL2>
          <L2RecordIndicator>&lt;L2&gt;</L2RecordIndicator>
          <L1ID>35435454545</L1ID>
          <L2ID>457899</L2ID>
          <L2Desc>bbbbbbbbb</L2Desc>
          <L2StartDate>20080101</L2StartDate>
          <L2EndDate>20080101</L2EndDate>
          <L2Hours>0</L2Hours>
          <L2Costs>0</L2Costs>
          <L2OrderType>Assigned</L2OrderType>
          <L2Plant>y001</L2Plant>
          <L2Priority>3</L2Priority>
          <L2SAPStatus>a</L2SAPStatus>
          <L2CostObject/>
          <L2CostObjectDesc/>
          <L2ActStartDate>20080101</L2ActStartDate>
          <L2ActEndDate>20080101</L2ActEndDate>
          <L2AreaID>01</L2AreaID>
          <L2FuncLoc>LAR</L2FuncLoc>
          <L2FuncLocDesc>LOS ANGLES</L2FuncLocDesc>
          <L2UnitName/>
          <L2MaintCatCode/>
          <L2MiscInfo1/>
          <L2MiscInfo2/>
          <L2SAPExempt/>
          <L2ShortWorkOrderID/>
          <L2Status_AorI>1</L2Status_AorI>
          <L2LaborTaxFlag/>
          <L2EquipTaxFlag/>
          <L2MaintTaxFlag/>
       </LEVEL2>
       <LEVEL3>
          <L3RecordIndicator>&lt;L3&gt;</L3RecordIndicator>
          <L1ID>35435454545</L1ID>
          <L2ID>457899</L2ID>
          <L3ID>10</L3ID>
          <L3Desc>cccccccc</L3Desc>
          <L3PlanStartDate>20080101</L3PlanStartDate>
          <L3PlanEndDate>20080101</L3PlanEndDate>
          <L3ActStartDate>20080101</L3ActStartDate>
          <L3ActEndDate>20080101</L3ActEndDate>
          <L3OrderType>Assigned</L3OrderType>
          <L3WorkCenter>los</L3WorkCenter>
          <L3WorkAmtScheduled/>
          <L3UnitofWork/>
          <L3DurationScheduled/>
          <L3UnitofDuration/>
          <L3NoofEmp/>
       </LEVEL3>
    </ns0:TCostObject>
    The receiver file look more or less the same as sender file but with delimiter @# and the fields are different
    <L1>@#...........
    <L2>@#..........
    <L3>@#............
    <L1>@#...........
    <L2>@#..........
    <L3>@#............
    Sender file adapter content conversion:
    LEVEL1.fieldNames     LevelID,PONumber,POLineNo,ShortText,StDate,EndDate,Vendor,POValue,ExpectedValue,Plant,Status,OrderType
    LEVEL1.fieldSeparator     @!
    LEVEL1.endSeparator     'nl'
    LEVEL1.processFieldNames     fromConfiguration
    LEVEL1.keyFieldValue     LEVEL1
    LEVEL2.fieldNames     LevelID,PONumber,POLineNo,Level2ID,Level2Desc,L2StDate,L2EndDate,L2Plant,L2Priority,L2SAPStatus,L2ActStDate,L2ActEndDate,L2FuncLoc,L2FuncDesc,L2Status,L2OrderType
    LEVEL2.fieldSeparator     @!
    LEVEL2.endSeparator     'nl'
    LEVEL2.processFieldNames     fromConfiguration
    LEVEL2.keyFieldValue     LEVEL2
    LEVEL3.fieldNames LevelID,PONumber,POLineNo,Level2ID,Level3ID,Level3Desc,L3StDate,L3EndDate,L3ActStDate,L3ActEndDate,L3WorkCenter,L3OrderType
    LEVEL3.fieldSeparator     @!
    LEVEL3.endSeparator     'nl'
    LEVEL3.processFieldNames     fromConfiguration
    LEVEL3.keyFieldValue     LEVEL3
    ignoreRecordsetName     true
    Receiver Adapter content conversion:
    LEVEL1.fieldSeparator     @#
    LEVEL2.fieldSeparator     @#
    LEVEL3.fieldSeparator     @#
    LEVEL1.endSeparator     'nl'
    LEVEL2.endSeparator     'nl'
    LEVEL3.endSeparator     'nl'
    The file is not being picked up.I am sure sender file adapter is correct as I have used this for (file to soap) and the scenario works file.I am not sure of receiver file adapter,do we have to use adavanced mode in receiver file adapter?Can you guys plz help me.Let me know if you have any questions
    Thanks

    Can someone let me know what are the parameters to give in FCC receiver file adapter.
    Thanks

  • File Content Conversion : File to File Scenario

    hi all,
    I have a Input file
    It has the following structure:
    <?xml version="1.0" encoding="utf-8"?>
    <n0:rfc_proxy_message_type xmlns:n0="http://kpr.com/sample">
    <Name>abhishek</Name>
    <Age>10</Age>
    </n0:rfc_proxy_message_type>
    I use a File to File Scenario,  with Sender and receiver FTP adapters.
    I would like to convert this file at the recieveing end into a flat file  as follows:
    Name     Age
    abhishek  10
    How can I do so?
    Can anyone please help.
    Thanks,
    Best Regards
    Abhishek

    Hi,
    Your Xml file should be like this.
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:Employee_MT xmlns:ns0="http://sap.com/demo">
       <Recordset>
          <item>
             <Name>vinod</Name>
             <Id>12</Id>
             <Age>30</Age>
             <***>male</***>
          </item>
       </Recordset>
    </ns0:Employee_MT>
    In the content conversion parameters mention the following
    Document name:    Student_MT
    Document Namespace:   enter your namespace
    RecordsetName:    Recordset
    Recoedset Structure:   item,*
    item.endSeparator = 'nl'
    item.fieldSeparator= ,
    item.fieldnames= Name,Id,Age,***
    Hope this helps you.

  • File Content Conversion File-File scenario

    Dear experts,
    I have been tweaking with file to file scenario where a simple file goes in source as text delimited and comes out in target as xml.
    I know ,i finally get my scenario get working with these settings :
    ROOT.fieldSeparator ,
    ROOT.fieldNames Store_Id,TRDT,SKU,SALE_RETURN,PRICE_OVERRIDE,PROMOTION_NUMBER,PROMO_DETAIL_ID,MIX_MATCH_NUMBER,DISCOUNT_ID,QUANTITY,EXTENDED_SELLING_PRICE,EXTENDED_ORIGINAL_PRICE,DIFFERENCE_PRICE
    ROOT.fieldContentFormatting trim
    ROOT.endSeparator 'nl'
    ROOT.missingLastfields add
    ROOT.processFieldNames fromConfiguration
    ignoreRecordsetName true
    Now my question is where i can find all properties that are probable in ROOT.Other thing is  i kept on getting mapping related errors until i reached
    at this stage of properties definition.But there was no tracking as of why i got that error.The error was :
    Mapping "http://TPOCTEST_SFILE/OM_TPOCTEST" failed to execute: MappingException: Runtime Exception when executing application mapping program com/sap/xi/tf/_MM_TPOCTEST_; Details: com.sap.aii.mappingtool.tf7.IllegalInstanceException; Cannot create target element /ns0:MT_TPOCTEST_T/Record. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD
    I resolved once i made settings on top but this was only a hit and trial.I dont know what actually was the reason behind this error.
    I also used Test option of mapping and found things working.

    Hi Aditya,
    That error indicates that when you were facing problems with your FCC the system did not generate XML that worked with the mapping that you have OM_TPOCTEST.  The error is showing that you have a target node named Record which I'm guessing is set to 1...unbounded but your FCC did not generate XML that would map in such a manner that 1 or more nodes named Record would be created in your target message.
    Regards,
    Ryan Crosby

  • Receiver File content conversion with nested structure

    Hi Guys,
    I have the below nested structure and have to convert it using receiver file content conversion.
    <Header> [o, unbounded]
       <A>a</A>
       <B>b</B>
    </Header>
    <record>   [0, unbounded]
       <field1>
            <X1>x</X1>
            <Y1>y</Y1>
       </field1>
       <field2>
             <X2>x</X2>
             <Y2>y</Y2>
       </field2>
    </record>
    The file is a comma separated one. Please let me know how to configure the content conversion.
    Thanks

    Hi Mukesh,
    Have a look at the Shabz's blog for the receiver File content conversion : File Adapter (Receiver) - Are we "really" sure about the concepts?
    Thanks,
    Pooja

  • Can't get File content conversion to produce CSV file

    Hi Guys
    Have no problem at all getting XML file created via an RFC
    Structure is something like this
    From MONI message monitor inbound message    payload
    <?xml version="1.0" encoding="UTF-8" ?>
    - <rfc:Z_XI_005_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
    - <IP_CUSTOMER_HEADER>
      <CUSTOMERID>100853</CUSTOMERID>
      <COMPANY>Bram Van Tuyl Coldstore</COMPANY>
      <SHORT_NAME>VAN TUYL</SHORT_NAME>
      <STREET>Middelkampseweg 1</STREET>
    etc
    </IP_CUSTOMER_HEADER>
      </rfc:Z_XI_005_RFC>
    Receiver Grouping  payload
    <?xml version="1.0" encoding="UTF-8" ?>
    - <rfc:Z_XI_005_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
    - <IP_CUSTOMER_HEADER>
      <CUSTOMERID>100853</CUSTOMERID>
      <COMPANY>Bram Van Tuyl Coldstore</COMPANY>
      <SHORT_NAME>VAN TUYL</SHORT_NAME>
      etc.
    With no conversion xml file is created on output directory 
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:MT_customer_header xmlns:ns1="http://avenue.com/xi/test"><customerid>100853</customerid><company>Bram Van Tuyl Coldstore</company> 
    etc
    Now trying to use File content conversion with the simplest possible conversion -- just insert a colon after all the fields in the structure.
    Following parameters
    Adapter type FILE
    receiver box checked
    Message protocol  File Content conversion
    File access etc as before
    Content conversion parameters
    Recordset :  IP_CUSTOMER_HEADER
    (have also tried Z_XI 005_RFC)
    Name
    CUSTOMERID.fieldSeparator  :        (colon)
    MONI shows message received by XI and processed correctly  but NO outfile gets written to the target directory.
    what am I doing wrong --it's probably something stupid.
    The data into XI is a ONE RECORD structure -- not a table etc.
    Cheers
    jimbo

    Hi guys -- both solutions STILL not working
    all I'm now getting is just a file with garbage in it
    Payload is fine on XI system
    Here's the payload
    <?xml version="1.0" encoding="UTF-8" ?>
    - <rfc:Z_XI_005_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
    - <IP_CUSTOMER_HEADER>
    - <item>
      <CUSTOMERID>65013</CUSTOMERID>
      <COMPANY>OY PANDA AB</COMPANY>
      <SHORT_NAME>PANDA</SHORT_NAME>
      <STREET>P.O.Box 3</STREET>
      <STREET2 />
      <STREET3 />
      <STREET4 />
      <POSTCODE>3331 GT</POSTCODE>
       etc etc  until end of customer mmaster details
    </item>
      </IP_CUSTOMER_HEADER>
      </rfc:Z_XI_005_RFC>
    Without conversion file is generated on target directory
    Here's the XML output file  sent to the directory
    (for testing I only usec the ist 3 fields)
    Not sure why <item>   disappeared  - maybe that has something to do with it ?
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns1:MT_customer_header xmlns:ns1="http://avenue.com/xi/test">
      <CustomerId>65013</CustomerId>
      <company>OY PANDA AB</company>
      <shortname>PANDA</shortname>
      </ns1:MT_customer_header>
    RFC call from R3 system  is fine (otherwise I wouldn't get the message into XI. Transaction SM58 as well on R3 shows no RFC errors
    Converted file is just a blank with nl character at the end ??????
    cheers
    jimbo

  • Com.sap.sql.DuplicateKeyException in file receiver channel

    Hi experts,
    I am currently testing the following scenario:
    xml file -> file sender ->file receiver -> csv file
    No mapping is used. Both channels are on the same PI 7.1 system.
    The transformation seems to work so far. The only problem I have is that my receiver channel does not post the message to the directory because of this error:
    Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id f167e134-145e-4b2c-2d47-e431b8b34fd8(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: [200]: Duplicate key.
    Is it not possible to use file sender and file receiver in the same scenario? Thanks for any help.
    Best regards.
    Oliver.

    Hi André,
    I am using the test option so the message can be processed multiple times. Anyway, I also tried using deletion but I still get the same error. I also tried a completely new file but still no change. When I check the comm channel I see that there is always created a new message id and when I search the rwb it posts two entries. One from the sender step and one from the receiver step. Seems to be alright to me.
    Regards.
    Oliver.

  • 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

Maybe you are looking for