Content Conversion in JMS Adapter

Hi All,
I am having a scenario JMS - XI - JDBC.
Now I have to do the content conversion in the incming records.
The sample incoming data is as follows:-
<Field1>,<Field2>, ...,<Fieldn>        -->Row1
{<Field1A>,<Field2A>, ...,<FieldnA>}   -->Row2
{<Field1A>,<Field2A>, ...,<FieldnA>}   -->Row3
<Field1B>,<Field2B>, ...,<FieldnB>     -->Row4
{<Field1C>,<Field2C>, ...,<FieldnC>}   -->Row5
{<Field1C>,<Field2C>, ...,<FieldnC>}   -->Row6
{<Field1C>,<Field2C>, ...,<FieldnC>}   -->Row7
Now at the target, we have 3 oracle tables, in which the data from the Row1 &4 will go to Table 1, Row2&3 --> Table2 and Row5,6 &7 --> Table3.
The source data type that i m using is of the structure:-
<TC>
  <GT>
    <Field1>
    <GS>
      <Field1A>
    </GS>
    <Field1B>
    <Field2B>
    <GDS>
      <Field1C>
    </GDS>
  </GT>
</TC>
Please help me out in the modules configuraton, how this can be handled.
Thanks in advance, hope to receive some solution at the earliest.
Rocky.

Hi Rocky,
Please have a look at these threads..
JMS Adapter: Content Conversion
JMS Adapter Content Conversion
JMS Content Converrsion
Hope these help you!
cheers,
Prashanth

Similar Messages

  • File Content Conversion in JMS Adapter

    Hello,
    I am trying to use module parameters to convert File to XML in Sender JMS adapter. I have followed the instructions in the SAP document (3.1 Example of a Simple Conversion in a Sender Communication Channel)
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50061bd9-e56e-2910-3495-c5faa652b710
    The problem I am facing is instead of creating one xml message for all the lines in the file; it is creating one message per line. Not sure what I need to do get all the lines in to one xml message.
    Please let me know if any of you have faced similar issue.
    Thanks
    AV

    The Parameter xml.recordsetsPerMessage can only be used if it is a complex structure. I mean it needs a recordSet with Keys..etc and What I am trying to do is a simple FCC using
    Transform.Class=com.sap.aii.messaging.adapter.Conversion
    Transform.ContentType=text/xml;charset=utf-8
    xml.conversionType=SimplePlain2XML
    xml.documentName=PurchaseOrder_Root
    xml.documentNamespace=http://namespace
    xml.fieldFixedLengths     =2,10,10,3,..
    xml.fieldNames = DATA1,DATA2,DATA3....
    xml.processFieldNames=fromConfiguration
    xml.structureTitle=PurchaseOrder
    <b>I am expecting</b>
    <PurchaseOrder_Root>
    <PurchaseOrder>
    <DATA1>  </DATA1>
    <DATA2>  </DATA2>
    </PurchaseOrder>
    <PurchaseOrder>
    <DATA1>  </DATA1>
    <DATA2>  </DATA2>
    </PurchaseOrder>
    </PurchaseOrder_Root>
    <b>When I use the above Module Config it is giving me </b>
    </PurchaseOrder_Root>
    <PurchaseOrder>
    <DATA1>  </DATA1>
    <DATA2>  </DATA2>
    </PurchaseOrder>
    </PurchaseOrder_Root>
    </PurchaseOrder_Root>
    <PurchaseOrder>
    <DATA1>  </DATA1>
    <DATA2>  </DATA2>
    </PurchaseOrder>
    </PurchaseOrder_Root>

  • Content conversion in sender adapter.

    Hi,
    I have a problem with the content conversion in sender adapter.
    I need only process the csv file with the exact number of columns containing the structure, if the csv file contains more o less columns in the csv file, I want that this files are not relayed by the adapter and remain on the server.
    Thank you very much for your help.

    @ Hareen
    This can be achieved at mapping level. You need to check the number of columns that are comming in the file using Count function. If the number of count is equal to the value specified then will process the message else raises a mapping exception.
    Are you talking about "count" function in the message mapping? that function won't count the number of fields / columns, but would count the number of occurrence of a particular field.

  • 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

  • Content Conversion in Mail Adapter

    Hi folks,
    I would like to know whether it is possible to do content conversion when using a mail adapter.
    The scenario is :
    We will receive file as an attachment in a mail. We have to read the file and do the content conversion. Then we have to map the data to an Idoc.Now we r struck that how can we convert the content of the mail attachment. Please help how can we achieve this.
    Thanks in advance.
    Best Regards,
    Noorul

    hi,
    yes you can do it:
    this document describes the same thing with jms adapter:
    https://websmp101.sap-ag.de/~sapdownload/011000358700001186732005E/HowToConveModuleJMS.pdf
    my weblog about e-mail attachments:
    /people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

  • Content conversion at JMS sender communication channel

    Hi friends,
                    I have to convert fixed length flat structure to xml message.Therefor i have to do content conversion at the JMS sender comm channel.Can someone please explainthe procedure?
    data in the queue would be like as follows.
    9999000000124646q12233appej500rc11147822zord

    Hi Manikandan,
    The structure conversion can handle files containing rows with different structures. In
    each row there is a key field to identify the structure. The rows with identical key fields of
    course have identical structures.
    Let us assume that we have a sample file with four rows. Each row has a two-byte key
    field; the first row has a second field with ten bytes; the structure of the second and third
    rows is the same and comprises two additional fields with three bytes each; the last row
    has a second field with five bytes:
    AA1234567890
    BBABCABC
    BBXYZXYZ
    CC12345
    The configuration for the conversion could look like this:
    Module Configuration
    Module Key Parameter Name Parameter Value
    Plain2XML Transform.Class com.sap.aii.messaging.adapter.Conversion
    Plain2XML Transform.ContentType text/xml;charset=utf-8
    Plain2XML xml.conversionType StructPlain2XML
    Plain2XML xml.processFieldNames fromConfiguration
    Plain2XML xml.documentName MyDocument
    Plain2XML xml.documentNamespace http://xi.com/test
    Plain2XML xml.recordsetName MyRecordset
    Plain2XML xml.recordsetStructure NameA,1,NameB,*,NameC,1
    Plain2XML xml.keyFieldName MyKey
    Plain2XML xml.keyFieldType CaseSensitiveString
    Plain2XML xml.NameA.fieldNames MyKey,field-nameA
    Plain2XML xml.NameA.fieldFixedLengths 2,10
    Plain2XML xml.NameA.keyFieldValue AA
    Plain2XML xml.NameB.fieldNames MyKey,field-nameB1,field-nameB2
    Plain2XML xml.NameB.fieldFixedLengths 2,3,3
    Plain2XML xml.NameB.keyFieldValue BB
    Plain2XML xml.NameC.fieldNames MyKey,field-nameC
    Plain2XML xml.NameC.fieldFixedLengths 2,5
    Plain2XML xml.NameC.keyFieldValue CC
    In xml.recordsetStructure, you add a name for each different structure followed by the
    number of occurrences or an asterisk for unbounded occurrences. For each structure
    name, you configure the structure separately in a separate namespace such as
    xml.NameA.fieldNames and so on.
    If your source file is a CSV file, replace each xml.XXX.fieldFixedLengths with
    xml.XXX.fieldSeparator.
    the result of this conversion looks like this:
    <ns:MyDocument xmlns:ns="http://xi.com/test">
    <MyRecordset>
    <NameA>
    <MyKey>AA</MyKey>
    <field-nameA>1234567890</field-nameA>
    </NameA>
    <NameB>
    <MyKey>BB</MyKey>
    <field-nameB1>ABC</field-nameB1>
    <field-nameB2>ABC</field-nameB2>
    </NameB>
    <NameB>
    <MyKey>BB</MyKey>
    <field-nameB1>XYZ</field-nameB1>
    <field-nameB2>XYZ</field-nameB2>
    </NameB>
    <NameC>
    <MyKey>CC</MyKey>
    <field-nameC>12345</field-nameC>
    </NameC>
    </MyRecordset>
    </ns:MyDocument>
    Regards,
    Vinod.

  • Supress Column Heading - File Content Conversion in Sender Adapter

    Hi,
    Let me give a more clear picture about my scenario.  I need to convert CSV File to XML output:-
    My source file has column heading and values.  The sample data is mentioned hereunder:-
    PERNR;KID;PNALT;NACHN;NAME2;VORNA
    ;1200;1200;Angus
    I have created a data type as under:-
    DT_LegacyEmployee (Category - Complex Type)
         Employees (Category - Element, Occurence - 1)
              Header (Category - Element, Occurence - 0...1)
                   PERNR_H
                   KID_H
                   PNALT_H
                   NACHN_H
                   NAME2_H
                   VORNA_H
              Employee (Categroy - Element, Type - DT_LegacyEmployee_Row, Occurence - 0...unbounded)
                   PERNR
                   KID
                   PNALT
                   NACHN
                   NAME2
                   VORNA
    The file conversion parameters in the file sender adapter are mentioned hereunder:-
    Document Name - MT_LegacyEmployee
    Document Namespace - http://abc.com/xi
    Recordset Name - Employees
    Rescordset Structure - Header,1,Employee,*
    Recordsets per Message - 1
    Key Field Type - String (Case Sensitive)
    Employee.fieldSeparator - ;
    Employee.endSeparator - 'nl'
    Employee.fieldNames - PERNR,KID,PNALT,NACHN,NAME2,VORNA
    I dont' have a key field value.  How do we remove the header and show only the values in the xml output.  I have searched the forum topics as well checked many blogs related to file content conversion, but nothing helped.  Kindly advice how to fix this issue.  Thanks in advance.
    Regards.
    Praveen

    Hi Praveen,
    Change your File Adapter as below
    Document Name - MT_LegacyEmployee
    Document Namespace - http://abc.com/xi
    Recordset Name - Employees
    Rescordset Structure - Employee,*
    Recordsets per Message - 1
    Key Field Type - String (Case Sensitive)
    Employee.fieldSeparator - ;
    Employee.endSeparator - 'nl'
    Employee.fieldNames - PERNR,KID,PNALT,NACHN,NAME2,VORNA
    There is no need for the Header required in the data type.
    DT_LegacyEmployee (Category - Complex Type)
    Employees (Category - Element, Occurence - 1)
    Employee (Categroy - Element, Type - DT_LegacyEmployee_Row, Occurence - 0...unbounded)
    PERNR
    KID
    PNALT
    NACHN
    NAME2
    VORNA
    Now the trick is in the mapping program
    Lets assume your mapping looks like
    MT_LegacyEmployee ---> MT_TargetEmployee
    - Employees ---> Records
       - Employee ---> Record
         - PERNR  ---> TargetPERNR
         - .. so on
    When you do a mapping from Employee ---> Record apply the following logic.
    (PERNR)--->
                 (TestEquals =) --->(NOT)--->
    (Constant) --->                                (IF)
    (PERNR)                       (IF Without Else) ---> (Record)
                                                   (THEN)
                                (Employee)--->
    When doing this make sure RightClick on PERNR and Select Context ---> Employees.
    By default context would be from Employee and it will give you an error of XSD format. So make sure you are changing the context.

  • Problem with File Content Conversion (Receiver FIle Adapter)

    Hi Experts,
    I have following structure in receiver side:
    MT_Test
       F1
       F2
       F3
       F4
    Now I want a CSV file in target side in below format:
    F1,F2,F3,F4
    I have provided below config in receiver file adapter under content conversion tab:
    Recordset Structure : MT_Test
    MT_Test.fieldSeperator= ,
    MT_Test.endSeperator= 'nl'
    But this is generating blank CSV files in target directory..What might be the reason.. I have checked the msg in adapter engine, the XML file is correct and contains valid values for the fields..Its something like below:
    <?xml version="1.0" encoding="UTF-8" ?>
    <MT_Test>
       <F1>Hai</F1>
       <F2>Hello</F2>
       <F3>Bye</F3>
       <F4>Hi</F4>
    </MT_Test>
    I should get CSV file as
    Hai,Hello,Bye,Hi
    But I am getting a blank file with above said config parameters in content conversion tab.
    What might be the reason for getting blank CSV files in target side???
    Thanks,
    Adi

    Hi Adi,
    >>My target structure in below format:
    <?xml version="1.0" encoding="UTF-8" ?>
    - <MT_Test>
    <F1>Hai</F1>
    <F2>Hello</F2>
    <F3>Bye</F3>
    <F4>Hi</F4>
    </MT_Test>
    So, try to edit Data type and include hierarchy level above <F1>.
    Finally your Target Structure will resembles like this.
    <?xml version="1.0" encoding="UTF-8" ?>
    - <MT_Test>
    <Structure>
    <F1>Hai</F1>
    <F2>Hello</F2>
    <F3>Bye</F3>
    <F4>Hi</F4>
    </Structure>
    </MT_Test>
    FCC Parameters will be like this.
    Structure.fieldSeparator = ,
    Structure.endSeparator = 'nl'
    Hope you were clear.
    Thanks,
    Siva.

  • Content Conversion for J2SE Adapter

    Hi,
    I have configured the J2SE Adapter properly,
    Still content conversion is not taking place for my file and it is going unconverted to xi.
    Following is the process.
    I have the file as:
    <b>0000665811     0111     500.00     20071217</b>
    I Require the xml as
    <b><ns0:Mt_Customer_Balance_Info xmlns:ns0="http://aoa.nestle.com/fi">
       <RECORDSET>
          <CUSC>0000665811</CUSC>
          <CRCA>0111</CRCA>
          <OBAL>500.00</OBAL>
          <DATE_REPORT>20071217</DATE_REPORT>
       </RECORDSET>
    </ns0:Mt_Customer_Balance_Info></b>
    I have configured as follows:
    <b>mode=FILE2XMBWITHROWCONVERSION
    xml.processFieldNames=fromConfiguration
    xml.fieldSeparator='0x09'
    xml.lastFieldsOptional=NO
    xml.endSeparator=nl
    xml.fieldNames=CUSC,CRCA,OBAL,DATE_REPORT
    xml.structureTitle=RECORDSET
    xml.documentName=FILE
    xml.documentNamespace=http://aoa.nestle.com/fi</b>
    Can you help me regarding this?

    hi anupam,
    u may refer this and see if u have done the configuration correctly.
    http://help.sap.com/saphelp_nw04/helpdata/en/88/0f453cf1fcc85ee10000000a11402f/frameset.htm
    regards,
    latika.

  • File Content Conversion in Receiver Adapter Help

    Hi,
    I need to have a flat file at receiver side with the following structure.
    Product
    LineItem
    Notes
    Product
    LineItem
    Notes
    But i am getting as
    Product
    Product
    LineItem
    Notes
    Notes
    Please suggest me the changes to be made in File Content Conversion Parameter
    Your Help will be appreciated.
    Thanks in advance,
    Ashok

    Singh,
    I think we wont give field names in the receiver file adapter. Please find the details below:
    RecordSet Structure: Product,LineItem,Notes.....
    Parameters:
    Product.fieldFixedLengths:30,10...
    Product.endSeparator:'nl'
    LineItem.fieldFixedLengths:30,10..
    LineItem.endSeparator:'nl'
    Notes.fieldFixedLengths:30,10...
    Notes.endSeparator: 'nl'
    Thanks
    Ashok

  • 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
    &#9679;      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.
    &#9679;      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

  • Message Conversion in JMS adapter

    Hello Friends,
    I have a scenario where in I will be getting the message from MQ, and the message will look like
    <b>SOURCE</b>
    <Root><MessageHeader><MessageID><MessageIDSystem>SCV</MessageIDSystem><MessageIDType>FE</MessageIDType><MessageIDIdentifier>CUSTOMER_MASTER</MessageIDIdentifier></MessageID><MessageReleaseNo>0004</MessageReleaseNo><MessageVersionNo>00</MessageVersionNo><MessageOrigApplID>SCV</MessageOrigApplID><MessageDestApplID>BROKER</MessageDestApplID><MessageInterfaceID>IDD088</MessageInterfaceID></MessageHeader><MessageBody><SCVData>53435646453030340130303030303401323030372d31312d31362031393a34303a343401313336333938323401330130010154414730303101574542555345525f52454c4154494f4e0155504441544501323030372d31312d31362031393a34303a343301544147303138013836373134013332353030303039343239013332353030303035323338013332353030303035323339010131014e014e01494e41435449564501350154414730303101504552534f4e01494e414354495641544501323030372d31312d31362031393a34303a343401544147303032013332353030303039343239015941553b56414e4553534101333235013301494e41435449564501323030352d30342d30332031383a34363a3136015343563234324d4947524154494f4e01323030372d31312d31362031393a34303a3433014a43473031370133515955493630554b36355136015041015441473031390131013332353030303039343239015041303030303934323901013101544147303033015941550156414e455353410156590101014601013530372d34333032383838013530372d363736383332380149544350545940435750414e414d412e4e4554013201013530372d343330323839310101544147303031014c494e4b01494e414354495641544501323030372d31312d31362031393a34303a3434015441473030360130303432013332353030303035323338013332353030303039343239015343563234324d4947524154494f4e013530372d34333032383838013530372d343330323839310101323030352d30342d30332031383a34363a313601393939392d31322d33312030303a30303a3030015343563234324d4947524154494f4e01494e41435449564501323030372d31312d31362031393a34303a3433014a43473031370149544350545940435750414e414d412e4e4554013530372d343330323839310154414730313901320133323530303030353233380150413b494e5445524558503b48454144510101320154414730313901310133323530303030353233380150413030303035323338010131015441473031390134013332353030303035323338013832373032313030010134015441473031390131013332353030303039343239015041303030303934323901013101</SCVData></MessageBody></Root>
    and the ascii data in this message needs to be converted into XML format.
    JMS Adapter is picking this message from MQ and posting it to XI.
    Also there is an adapter module develped for this conversion and it is working fine for most of the messages, but it failing for this above message.
    Can you please help me out in this issue and how to test that adapter module.
    Thanks & Regards,
    Kumar

    hi kumar,
    >>Can you please help me out in this issue and how to test that adapter module.
    put brek points in ur adapter module and then run ur scenario and debug. this is how u test ur adapter module.
    this will also help u to see why is it running for certain msgs n failin for others. at different steps/points check the value for variables etc while debugging.
    Also put some statements to write audit log entries in ur code for module. this will also help in debugging.
    [reward if helpful]
    regards,
    latika.

  • Content Conversion in File Adapter

    Hi All
    Can anyone tell me that in case of content conversion file adapter , up to what level (the deepness in hirerachy) the content conversion is possible both at sender communication channel and at receiver communication channel side.

    <documentName>...
       <recordset>
    <NameA>
    <field-nameA1>field-value</field-nameA1>
    <field-nameA2>field-value</field-nameA2>
    <field-nameA3>field-value</field-nameA3>
    </NameA>
    <NameB>
    <field-nameB1>column-value</field-nameB1>
    <field-nameB2>column-value</field-nameB2>
    <field-nameB3>column-value</field-nameB3>
    </NameB>
       </recordset>
       <recordset>
       </recordset>
    </documentName>
    That is the XML taken from SAP help and that is exactly the maximum level. Note that documentName is nothing but your MT name.

  • Blogs for File content conversion in File Adapter

    hi all,
    Can some one give me the links for File Content Conversion for File to File Scenario. please.
    Thanks in advance.

    Hi
    For Sender
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    /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/sap.user72/blog/2005/01/06/how-to-process-csv-data-with-xi-file-adapter
    /people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
    SAP Help for sender
    http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
    For Receiver:
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    SAP Help for receiver
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm

  • Doubt regarding file content conversion Recever File adapter.

    target structure.
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:MT_ChangeOfAddress xmlns:ns1="urn:passhe.com/ChangeOfAddressISA28">
         <BUSINESS_PARTNER>
              <item>
                   <CAMPUSCODE>65</CAMPUSCODE>
                   <STUDENTNUMBER>6500000192</STUDENTNUMBER>
                   <ST_OBJID>732298498</ST_OBJID>
              </item>
         </BUSINESS_PARTNER>
    </ns1:MT_ChangeOfAddress>
    target structure is look like this.
    MT_ChangeOfAddress
         BUSINESS_PARTNER  (1,1)
              item       (0 to unbounded)
                  CAMPUSCODE (0,1)
                  STUDENTNUMBER (0,1)
                        ST_OBJID      (0,1)
    I have given below parameters in recever file adapter (file content conversion)
    Recordset Structure : item
    item.fieldNames  : CAMPUSCODE,STUDENTNUMBER,ST_OBJID
    item.fieldSeparator: , (comma)
    i am getting first two digits in my output file: that  file has only first two digits that is : 65
    may i know how hould i define file contente conversion recever adapter to get proper data in file adapter.
    thanks,s
    Dhanush

    Hi,
    Go through these blogs:
    /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/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/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
    Thanks,
    Satya

Maybe you are looking for