File content conversion using the Meaasge Transform bean

Hi
I have a scenario file with pipe delimited file.
What are content conversion parameters required
venkat

Sedamkar,
In file content conversion you give these parameters;
Header.fieldSeparator:|
Header.endSeparator:'nl'
DetailRecord.fieldSeparator:|
DetailRecord.endSeparator:'nl'
TrailerRecord.fieldSeparator:|
TrailerRecord.endSeparator:'nl'
In recordset structure you give as:Header,1,DetailRecord,*,TrailerRecord,1
Regards,
---Satish

Similar Messages

  • File content conversion using SOAP adapter

    Hi,
         I'm using a receiver SOAP adapter in my IDOC to file scenario and need to do file content conversion in the receiver side.
    Are any standard modules available for file content conversion in the SOAP adapter or do I need to write custom EJB modules for this.
    Please note that I have to use a SOAP adapter, can't use any other adapter.
    Thanks in advance
    Shiladitya

    Hi,
    XML Document Conversion Type
    ●      Enter recordTypes as the parameter name.
    Under Parameter Value, enter the complete, comma-separated list of all names of recordset types that occur in the document to be converted.
    If you decide to use this method, you can define a different conversion type for each recordset type that occurs in the XML document.
    For example, you could name the recordset types as follows: RecordType1,RecordType2,RecordType3.
    ●      Enter singleRecordType as the parameter name.
    Under Parameter Value, enter the name of a recordset type that is to be used to convert all elements that occur in the XML document.
    If you decide to use this method, define the same conversion type for each recordset type that occurs in the XML document.
    You must enter exactly one parameter only. Whichever parameter you choose, you automatically exclude the second parameter.
    You define further parameters for each recordset type.
    In the remainder of this documentation the parameters are specified by the prefix <RecordType>. In your configuration, replace this name with the name of the recordset type.
    Conversion Type List with Separators
    &#9679;      <RecordType>.fieldSeparator
    Enter the field separator that is written between the individual fields of a record.
    This specification is mandatory.
    Conversion Type List with Fixed Field Length
    &#9679;      <RecordType>.fieldLengths
    Specify a character string that contains a list of fixed field lengths that are separated by commas and which determines the number and the length of fields generated in the text file.
    For example, you want to write a recordset with three elements that have field widths of five, ten, and fifteen characters. Enter:
    <RecordType>.fieldLengths = 5,10,15
    This specification is mandatory.
    &#9679;      <RecordType>.fieldLengthExceeded
    Specify how you want to handle fields that exceed the configured field length. Permitted values for the parameter value are:
    &#9675;       error (default)
    Interrupts processing of message with error
    &#9675;       cut
    Cuts off superfluous characters
    &#9675;       ignore
    Ignores the field length restriction
    Further Entries
    &#9679;      <RecordType>.beginSeparator
    Enter a string. The string is placed in front of the first field of a recordset.
    &#9679;      <RecordType>.endSeparator
    Enter a string. The string is appended to the last field of a recordset as a concluding character. The default is \r\n.
    &#9679;      contentType
    Enter the MIME type of the converted payload. The default value is text/plain.
    &#9679;      addHeaderLine
    Only define this parameter if you have already defined singleRecordType.
    Define whether a header line is to be added to the result of the conversion.
    &#9675;       none (default)
    Does not insert a header line
    &#9675;       fromXML
    The header line is generated from the element name of the first recordset of the XML document
    &#9675;       fromConfiguration
    The header line is determined by the configuration parameter headerLine.
    &#9679;      headerLine
    Only define this parameter if you have already set addHeaderLine=fromConfiguration.
    The value that you define is placed in front of the result of the conversion as a header line.
    &#9679;      fixedLineWidth
    Enter the maximum line length n (in characters) that can be written to the resulting document. The separator specified by lineSeparator is inserted in the resulting document every n characters.
    &#9679;      lineSeparator
    Only define this parameter if you have already defined fixedLineWidth.
    Specify the string that is written to the resulting document at the end of each line that is written with fixedLineWidth. The default is \r\n.
    Use of Special Characters
    You can use special characters in the following parameters: <RecordType>.fieldSeparator, <RecordType>.beginSeparator, <RecordType>.endSeparator, headerLine, and lineSeparator.
    &#9679;      Tabulator: \t
    &#9679;      Carriage Return (CR): \r
    &#9679;      Line Feed (LF): \n
    &#9679;      Arbitrary character: \x<code>
    <code>indicates the hexadecimal character code of the character to be displayed.
    Regards,
    Phani

  • Query regarding file content conversion using file adapter

    Hi All
    I have a question regarding file content conversion in file adapter.
    I have a file coming in the following format.
    AA,111,222,333
    BB,444,555,666
    CC,777,888,999
    My incoming message structure has a hierarchy. The CC record is a structure part of BB record. BB record is a structure part of AA record. It is like this:
    AA,111,222,333
    <<BB,444,555,666>>
    <<<<CC,777,888,999>>>>
    After file content conversion, in the resulted xml, i am getting a flat hierarchy instead of nested hierarchy.
    Is it possible to get a nested hierarchy as a result of file content conversion?
    Please let me know
    Thanks
    Chandra

    Hi Udo
    According to your suggestion, I am trying to use mapping.
    I am getting a flat file and i am reading it.
    This is my source structure:
    AA,11,22,33
    BB,44,55,66
    CC,77,88,99
    This is my required targer structure:
    AA,11,22,33
    <<BB,44,55,66>>
    <<<<CC,77,88,99>>>>
    To explain this, BB record can have multiple records of CC records.
    AA records can have multiple records of BB record.
    I am using removecontext node function.
    CC (Source)  (removecontext)-> CC (target structure)
    But here, when i rightclick on source CC field in the mapping editor, i cannot see any other context except root node. So, how can i proceed here??
    Many Thanks
    Chandra

  • File Content Conversion -All the input content was not shown in output file

    Hi Experts,
    In my scenario, I need to send data from .XML file to .txt file, using File Content Conversion at Receiver communication channel. This is File to File scenario.
    This is my Input xml file.
    <ns:FILEINPUT_MT xmlns:ns="http://File2FileTest">
      <RECORD>
        <Row>
          <FirstName>Susie</FirstName>
          <LastName>Tony</LastName>
          <City>London</City>
          <Country>UK</Country>
        </Row>
      </RECORD>
    </ns:FILEINPUT_MT>
    <b>Processing Parameters</b>
    Target Directory = C:/Test
    File Name Scheme = xi_output.txt
    File Construction Mode = Add Time Stamp
    File Type = Binary
    <b>Content Conversion Parameters</b>
    Recordset Structure : RECORD
    RECORD.endSeparator = ‘nl’
    RECORD.fieldSeparator = ;
    After ‘Activate’ and providing the input xml file, xi_output.txt file was generated. But the file content was shown only with ‘Susie’ i.e. with First Name only. I need xi_output.txt file should have all the four fields (FirstName, LastName, City, Country)
    Could some one help me to resolve the issue?
    Thanks in advance
    Sree

    Check these blogs...Might help you.
    /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/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    /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/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
    /people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
    Link for SAP Help
    http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm

  • File Content Conversion on the Receiving side

    Is there a way in which if I want a Pipe Delimited File as a result, after the last field also I get a pipe with next record starting in the next line.

    Hi,
    For | (Pipe), use corresponding hex code as fieldSeparator i.e. 0x7C as fieldSeparator.
    For FCC on receiver side refer -
    [Simple FCC|http://www.riyaz.net/blog/index.php/2008/02/19/xipi-file-content-conversion-for-simple-structure/], [Complex FCC|http://www.riyaz.net/blog/index.php/2008/02/20/xipi-file-content-conversion-for-complex-structures/]
    For separotor at the end of line you can try using a dummy field or use combination of pipe and newline i.e. '0x7C' and '0x0D' (stands for carriage return) or 'nl' as endSeparator
    Edit: You might consider using 'nl' as beginSeparator parameter and 0x7C as endSeparator. This will do the trick. However, this would add a blank line in the beginning of the file.
    Hope this helps.
    Regards,
    Riyaz
    Edited by: Riyaz Sayyad on Aug 21, 2008 3:00 PM

  • Error in File content conversion in the target

    hi
    I'm doing a content conversion at target.
    my target structure while sending is like:
    <MT>
       <Header>
            <a>
      </Header>
       <BODY>
         <b>
      </BODY>
        <filename_output>
        <filename>
    </MT>
    however in the target i have to ignore the last 2 fields: <filename_output> and <filename>.
    I'm able to do it.
    The problem is coming that in the target structure,when we open in Textpad, 2 trailing empty lines are there at the end.
    we need to remove these lines.
    Any idea how to do it?

    Hi Alok,
    Try with parameters given in this blog:
    /people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12
    If didnot work try: FileName.endSeperator = '0'  as given in this thread: Re: Blank Lines While writing files
    else give .endSeparator as two backspaces (if you have two new lines). The ascii code is '0xBS'. see this code:
    http://www.december.com/html/spec/ascii.html
    ---Satish

  • File Content conversion at the sender adapter without Key field

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

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

  • File Content Conversion on the Sender Adapter in PI 7.1

    Hi Experts
    I am working on a file to Proxy scenario where my file is fixed format length which will have only one Structures (Details Records) that would be coming from the text file but in the message type I have delcared Header, Detail , Trailer,
    However I would be receiving the only Detail part (No header and Trailer) in some instances  what value should I give for the header and trailer in the Content conversion part,
    Thanks
    PR

    Since you are going to get values only some instances  for header and trailer node, you can create
    Header  structure   &  Trailer structure  - make the occurence 0 to 1
    Note: if your Header and Trailer values are empty for some instances then no worries. You declare FCC fields for header and trailer similar to Details.
    Refer SAP FCC help link.

  • File Content Conversion at the receiver side

    Hello All,
    I have a field which has to be truncated at 50th character. What content conversion parameters do I need to add ...?!?!?
    Thanks,
    Smita

    Hi Smita,
    As understood by your question you want a target field to be of 50 character,
    either you can apply substring function in your mapping to that target node.
    It would be much more clear if you mention hows your source file structure is it fixed length or delimiter separated, if it fixedlength file you can apply this parameter in Content conversion <b>fixedLengthTooShortHandling</b> with value <b>Cut</b> nad mention your required length.
    Rewards point if it is helpful,
    Thanks
    Anu Singhal

  • How do we do File content conversion using SFTP SEEBURGER Adapter

    HI All,
              Can we do FCC using SFTP SEEBURGER adapter. If yes how?
    XIer

    Dynamic attributes are part of the XI message. They provide options for dynamical configuration of SFTP receiver channels (Outbound direction) using parameters that have been dynamically added or set by modules and mappings before the SFTP adapter. These attributes can be set using the Attribute Mapper module for example. Besides, the SFTP adapter dynamically adds specific parameters to the XI message on Inbound case, which can be used by the modules and mappings after SFTP adapter.
    Check also
    /people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping
    /people/daniel.graversen/blog/2006/10/05/dynamic-configuration-in-adapter-modules
    Regards
    Naycho

  • File Content Conversion using Sender to Mapping

    I have a sender that is mapping a flat file CSV and it maps it correctly, but when it is being send to the message mapping program it fails on the input parse with an exception:
    Mapping transformation: Cannot produce target element /ns0:G8328_09B_Document/ns0:G8328_09BMessageType. Check xml instance is valid for source xsd
    I am using an external definition as my input for the message mapping if I import the messge from the monitor payload and change the ns: to ns0: in the test tool it maps find.  Can anyone tell me how to get the File adapter to generated ns0: instead of  ns: in the input message coming out of the adapter.
    Payload from the file adpater:
    <ns:G8328_09B_Document xmlns:ns="http://nike.com/DEYTEL/RFCToJDBCInterface">
    - <ns:G8320_09BMessageType xmlns:ns="http://nike.com/DEYTEL/RFCToJDBCInterface">
    - <G8328_09B>
      <VKORG>1000</VKORG>
      <AUART>ZG2</AUART>
      <XBLNR>0061623534</XBLNR>
      <VBELN>0010790092</VBELN>
      <NETWR>178.99</NETWR>
      <WAERK>USD</WAERK>
      <VBTYP>O</VBTYP>
      </G8328_09B>
    - <G8328_09B>
      <VKORG>1000</VKORG>
      <AUART>ZRE</AUART>
      <XBLNR>0061651916</XBLNR>
      <VBELN>0010790093</VBELN>
      <NETWR>37.37</NETWR>
      <WAERK>USD</WAERK>
      <VBTYP>O</VBTYP>
      </G8328_09B>
    </ns:G8320_09BMessageType>
    </ns:G8328_09B_Document>
    Payload gernerated from the Test tool:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:G8328_09B_Document xmlns:ns0="http://nike.com/DEYTEL/RFCToJDBCInterface">
       <ns0:G8328_09BMessageType>
    <G8328_09B>
      <VKORG>1000</VKORG>
      <AUART>ZG2</AUART>
      <XBLNR>0061623534</XBLNR>
      <VBELN>0010790092</VBELN>
      <NETWR>178.99</NETWR>
      <WAERK>USD</WAERK>
      <VBTYP>O</VBTYP>
      </G8328_09B>
    - <G8328_09B>
      <VKORG>1000</VKORG>
      <AUART>ZRE</AUART>
      <XBLNR>0061651916</XBLNR>
      <VBELN>0010790093</VBELN>
      <NETWR>37.37</NETWR>
      <WAERK>USD</WAERK>
      <VBTYP>O</VBTYP>
      </G8328_09B>
       </ns0:G8328_09BMessageType>
    </ns0:G8328_09B_Document>
    The test tool mapping I remove the ns and replaced it with ns0.
    Thanks for any help.
    Arjun.

    Hi Arjun,
    A few points....
    1. Namespace prefix being different does not cause mapping errors.
    2. In your case, note the name space <b>xmlns:ns="http://nike.com/DEYTEL/RFCToJDBCInterface"</b> missing in XML generated 
    using IR.
    3. The difference in Msg type names. After FCC it is G832<b>0</b>_09BMessageType where as in test tool it is G832<b>8</b>_09BMessageType.
    Correct points 2 and 3, your issue will be solved.
    Regards,
    Jai Shankar

  • File content Conversion in j2se at the receiver side

    Hi ,
    I need to do a file content conversion using j2se adapter at the recevier side.
    my structure is something like
    <name>
        <name1>
        <name2>
    </name>
    <address>
         <address1>
         <address2>
    </address>
    and the output should be like
    #tname1$name2
    #sadress1.address2
    Please do the needfull
    Thanks & Regards,
    Hamsa

    Hi Hamsa,
    #tname1$name2
    #sadress1.address2
    Lot of # and $, so can you paste the FCC parameters that you have tried in the File adapter?
    In j2se also we can use the same. If you are not sure on how to use, paste the FCC parameter here and someone will be able to make the J2SE version out of it
    Regards
    Suraj

  • Using File Content Conversion converting XML format to text format

    Hi All,
                 I am able to convert to Text format using file content conversion, But the requirement is to convert the same for the structure with additional subnodes  as in the example (also complex nested structures)
    <ns0:SendXSDEmployeeDetails xmlns:ns0="http://ehro.eds.com/FRAMEWORK/FileToFile/FileCConverion">
        <Employee>
                  <Employee_ID>2</Employee_ID>
                   <Employee_Name>KannanKumar</Employee_Name>
                     <Address>
        <Street>13th Cross Reddy</Street>
        <City>Bangalore</City>
        <Pincode>641026</Pincode>
        <Phone_No>
            <t1>9901934934</t1>
            <t2>9901934934</t2>
        </Phone_No>
    </Address>
       </Employee>
    </ns0:SendXSDEmployeeDetails>
    can any one help on this please
    I have already seen the blogs :
    /people/krishnakumar.ramamoorthy3/blog/2007/01/27/generic-mapping-to-convert-nested-xml-to-flat--receiver-file-adatper
    /people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
    <b>Can any one help to do  this in simple way</b><br>

    Hi,
    Like correctly pointed by JaiShankar, the Sender File Adapter currently does not supoort such stracutures.
    the strcuture supported is described in this link,
    http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
    Regards
    Bhavesh

  • File Sender adapter with File content conversion

    Hi
    I'm having problems picking up a flat file that has some junk characters in the file.
    I'm usign a file sender adapter with file content conversion. The adapters shows the following error-
    Conversion of complete file content of  to XML format failed around position 0: sun.io.MalformedInputException
    this is the sample data with junk char's -
    A20099201009999009999060815160505051700130008151vÿÿÿÿ³  r 0OK0476                     31N016227241915840IV  00840 ÿÿÿ ÿ ÿÿÿÿÿÿÿÿ ÿ ÿÿÿ             
    There is not much in the file content conversion. This is a fixed length file, I'm just pickign it up & passing it to an inbound proxy. All my processing is in the proxy.
    I'd appreciate any suggestions.
    Thanks
    Rachana

    Hi Rachana,
    Do you use a specific "encoding" like UTF-8 or ISO-8859-1 in your Sender CC?
    To be simple, Encoding is linked to country, you can find all "iso-nnnn" via google or some of them in sap help.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
    Moreover, with your source file opened thanks to Notepad (for instance), use option "save UNDER", you will the encoding use by your file
    Mickael

  • File Content Conversion - Error in keyfield Value

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

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

Maybe you are looking for