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>

Similar Messages

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.

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
●      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
●      <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
●      <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.
●      <RecordType>.fieldLengthExceeded
Specify how you want to handle fields that exceed the configured field length. Permitted values for the parameter value are:
○       error (default)
Interrupts processing of message with error
○       cut
Cuts off superfluous characters
○       ignore
Ignores the field length restriction
Further Entries
●      <RecordType>.beginSeparator
Enter a string. The string is placed in front of the first field of a recordset.
●      <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.
●      contentType
Enter the MIME type of the converted payload. The default value is text/plain.
●      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.
○       none (default)
Does not insert a header line
○       fromXML
The header line is generated from the element name of the first recordset of the XML document
○       fromConfiguration
The header line is determined by the configuration parameter headerLine.
●      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.
●      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.
●      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.
●      Tabulator: \t
●      Carriage Return (CR): \r
●      Line Feed (LF): \n
●      Arbitrary character: \x<code>
<code>indicates the hexadecimal character code of the character to be displayed.
Regards,
Phani

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

File Content Conversion in Receiver Adapter

Hello Friends,
I have following message in reciever adapter. How to set the parameter to output flat file? I set but it dosent function:
Record structure: Category, Items, Item
Category.fieldSeparator   ,
Category.endSeparator    ,
Items.fieldSeparator        ,
Items.endSeparator         ,
Item.fieldSeparator          ,
Item.endSeparator           ,
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:UpdateCategories xmlns:ns0="urn:N02_TestComplexCategory">
- <ns0:Category>
<ns0:RootCategoryID>14</ns0:RootCategoryID>
<ns0:RootCategoryParentID>34</ns0:RootCategoryParentID>
<ns0:RootCategoryName>abcd</ns0:RootCategoryName>
- <ns0:Items>
- <ns0:Item>
<ns0:CategoryID>ID1</ns0:CategoryID>
<ns0:CategoryParentID>14</ns0:CategoryParentID>
<ns0:CategoryName>CAT1</ns0:CategoryName>
<ns0:Attributes />
</ns0:Item>
- <ns0:Item>
<ns0:CategoryID>ID2</ns0:CategoryID>
<ns0:CategoryParentID>14</ns0:CategoryParentID>
<ns0:CategoryName>CAT2</ns0:CategoryName>
<ns0:Attributes />
</ns0:Item>
</ns0:Items>
</ns0:Category>
</ns0:UpdateCategories>
Thanks
Zhiping

Another message:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:UpdateCategories xmlns:ns0="urn:N02_TestComplexCategory">
- <ns0:Category>
<ns0:RootCategoryID>14</ns0:RootCategoryID>
<ns0:RootCategoryParentID>34</ns0:RootCategoryParentID>
<ns0:RootCategoryName>abcd</ns0:RootCategoryName>
- <ns0:Items>
- <ns0:Item>
<ns0:CategoryID>ID1</ns0:CategoryID>
<ns0:CategoryParentID>14</ns0:CategoryParentID>
<ns0:CategoryName>CAT1</ns0:CategoryName>
- <ns0:Attributes>
- <ns0:Attribute>
<ns0:AttributeType>1</ns0:AttributeType>
<ns0:AttributeValue>1</ns0:AttributeValue>
</ns0:Attribute>
- <ns0:Attribute>
<ns0:AttributeType>2</ns0:AttributeType>
<ns0:AttributeValue>2</ns0:AttributeValue>
</ns0:Attribute>
- <ns0:Attribute>
<ns0:AttributeType>3</ns0:AttributeType>
<ns0:AttributeValue>3</ns0:AttributeValue>
</ns0:Attribute>
</ns0:Attributes>
</ns0:Item>
- <ns0:Item>
<ns0:CategoryID>ID2</ns0:CategoryID>
<ns0:CategoryParentID>14</ns0:CategoryParentID>
<ns0:CategoryName>CAT2</ns0:CategoryName>
- <ns0:Attributes>
- <ns0:Attribute>
<ns0:AttributeType>1</ns0:AttributeType>
<ns0:AttributeValue>1</ns0:AttributeValue>
</ns0:Attribute>
- <ns0:Attribute>
<ns0:AttributeType>2</ns0:AttributeType>
<ns0:AttributeValue>2</ns0:AttributeValue>
</ns0:Attribute>
- <ns0:Attribute>
<ns0:AttributeType>3</ns0:AttributeType>
<ns0:AttributeValue>3</ns0:AttributeValue>
</ns0:Attribute>
</ns0:Attributes>
</ns0:Item>
</ns0:Items>
</ns0:Category>
</ns0:UpdateCategories>

File Content Conversion - Receiver Adapter

Hi To All
I have an XML Structure
<LIST>
     <Seg1>
          <Element1>123</Element1>
     </Seg1>
     <Seg2>
          <Element1>ABC</Element1>
          <Element2>DEF</Element2>
          <Element3>GHF</Element3>
        </Seg2>
<LIST>
I'm using File content conversion in receiver Adapter
I want my output like this.
ABCDEFGHF
I don't need the Segment Seg1.
In my parameters RecordsetStructure only I have Seg2 and the details for this Segment
but When I receive a file, the adapter convert with segment 1.
123
ABCDEFGHF
can you help me?.

easiest alternative is mentioned here already, drop it in the mapping.
You can also try to write a java pgm and invoke it as an OS command. that cuts the segment1 out before passing it to content conversion. ..more painful..but will work.
Regards
Ravi Raman

Adapter error in file content conversion

Hi Friends,
I am using FILE receiver adapter, transport protocol- NFS, msg protocol-File content conversion.
Sending msg is an idoc. File is being sent to application server of the XI system (for test purpose)
The message is shown as successful in SXMB_MONI but no file is created .
In message monitoring for adapter engine an error is shown -
"<b></b>file adapter receiver channel <comm channel name> is not initialized. Unable to proceed MP: eception caught with cause com.sap.aii.af.ra.ms.api.Recoverable Exception. Channle has not been correctly initialized & cannot process messages "<b></b>
However if i change the message protocol to FILE then it works correclt & a xml file is saved in system.
It seems the problem is with using file content conversion in the adapter farmework.
Can someone please help.

Hi
I have configured in a similar manner
Below is the XML Message
<?xml version="1.0" encoding="UTF-8"?>
<ns0:FileMatFlat_MT xmlns:ns0="http://ztest.com/test/idoc2file">
<RecordSet>
<Row>
<Author>SivaSakthi</Author>
<Transfered_By>SIVASAKTHI</Transfered_By>
<Long_Mat_Num>0000056090</Long_Mat_Num>
<Material_Number>0000056</Material_Number>
<Material_Desc>TESTING132123KLOSDFJ</Material_Desc>
</Row>
</RecordSet>
</ns0:FileMatFlat_MT>
My FCC parameter;
RecordStructure : Row
Row.addHeaderLine 1
Row.fieldSeparator #
Row.endSeparator 'nl'
My Output looks like
Row
SivaSakthi
Can some one please tell me why the others are not coming.

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

XML to flat file conversion using file content conversion in reciever CC

Hi,
Iam working on Idoc to File scenario.
Iam having a problem in the communication channel of reciever.
Iam using File content conversion in Reciever Adapter.
My xml format is asfollows:--
- <Header>
<FILLER1>KTP</FILLER1>
<YEAR_IDOC>YEAR 2006</YEAR_IDOC>
<FILLER2>FIRSTWEEKNUMBER</FILLER2>
<WEEK_IDOC>51</WEEK_IDOC>
<FILLER3>NUMBER WEEKS 26</FILLER3>
<PLANT_CODE>FACTORYM019</PLANT_CODE>
</Header>
- <Record>
<First_material>731000</First_material>
<First_quantity>0000.0</First_quantity>
<First_quantity>0001.9</First_quantity>
<First_quantity>0000.0</First_quantity>
<First_quantity>0000.0</First_quantity>
<First_quantity>0020.0</First_quantity>
<First_quantity>0000.0</First_quantity>
<First_quantity>0000.0</First_quantity>
<First_quantity>0000.0</First_quantity>
<First_quantity>0018.0</First_quantity>
<First_quantity>0000.0</First_quantity>
<Second_material />
<Seond_quantity>000000</Seond_quantity>
<Second_quantity>0011.0</Second_quantity>
<Seond_quantity>000000</Seond_quantity>
<Seond_quantity>000000</Seond_quantity>
<Seond_quantity>000000</Seond_quantity>
<Seond_quantity>000000</Seond_quantity>
<Second_quantity>0049.0</Second_quantity>
<Seond_quantity>000000</Seond_quantity>
<Seond_quantity>000000</Seond_quantity>
<Second_quantity>0067.0</Second_quantity>
<Third_material />
<Third_quantity>000000</Third_quantity>
<Third_quantity>000000</Third_quantity>
<Third_quantity>000000</Third_quantity>
<Third_quantity>0008.0</Third_quantity>
<Third_quantity>000000</Third_quantity>
<Third_quantity>000000</Third_quantity>
</Record>
The file format should be as follows:--
KTP   YEAR 2006 FIRSTWEEKNUMBER 51   NUMBER WEEKS 26 FACTORYM019
731000 0000.0 0001.9 0000.0 0000.0 0020.0 0000.0 0000.0 0000.0 0018.0 0000.0
        0000.0 0011.0 0000.0 0000.0 0000.0 0000.0 0049.0 0000.0 0000.0 0067.0
        0000.0 0000.0 0000.0 0008.0 0000.0 0000.0
Could some one help me in resolving this issue.
Regards
Praveen

Hi Praven,
couldn't you simply modify your target DATA type so it will be easier to handle?
For example something like:
<Header>
</Header>
<Record>
<Material>
<Number>..</Number>
<quantity>..</quantity>
<quantity>..</quantity>
</Material>
In this way file content conversion will be easier (easy)!
Regards,
Sergio

File Contentent Conversion

Hi Frnds,
I am receiving Flat file(.txt) from File Sytsem i hav to read that file using file adapter i have to use File Content Conversion , but i never worked on that help me on this
Flat File:
000000009900000201;17;2007;413.000 ;361.000 ;362.000 ;361.000 ;384.000 ;400.000 ;400.000 ;400.000 ;377.000 ;361.000 ;362.000 ;361.000 ;363.000 ;374.000 ;373.000 ;373.000 ;374.000 ;363.000 ;361.000 ;362.000 ;361.000 ;366.000 ;373.000 ;374.000 ;373.000 ;372.000 ;361.000 ;361.000 ;362.000 ;361.000 ;361.000 ;361.000 ;362.000 ;361.000 ;365.000 ;373.000 ;374.000 ;373.000 ;373.000 ;361.000 ;361.000 ;362.000 ;361.000 ;368.000 ;373.000 ;374.000 ;373.000 ;370.000 ;361.000 ;362.000 ;361.000 ;361.000 ;0.000 ;0.000 ;19200.000.
My Output Format
<Records>
    <Record>
        <Field1>
        <Field2>
        <File3>..........<Field58>
text file may contain single record or multiple recored it 1:unbounded but if first number starts with 000000009900000201 number sequece..
How to use FCC for above structure help me on this
Regards
Raja Sekhar

In the Content conversion parameter (in the sender communication Channel)
specify the paremeters as shown below if ur source structure is like this
<MT_Source>
   <Records>
     <Record>
       <Field1>
       <Field2>
       <File3>..........<Field58>
   </Record>
</Records>
</MT_Source>
Document Name :MT_Source
Document Namespace:Specify the namespace under which u have created ur source message type
RecordSet name:Records
RecordSet structure:Record,*
Record.fieldSeparator:,
Record.fieldNames:Field1,Field2,Field3(Specify all Fields separated by comma)
Record.endSeparator :'nl'
choose + to add extra parameters specified above
for detail about File content conversion at sender adapter see this link [http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm]

Problem with file content conversion in receiver file adapter

Hi All
I have a problem with file content conversion in receiver file adapter.
This is my recordset structure: Header_Record,1,Claim_Record,*,Check_Rec,1
These are the content conversion parameters:
Header_Record.fieldSeparator = ,
Header_Record.endSeparator = 'nl'
Claim_Record.fieldSeparator = ,
Claim_Record.endSeparator = 'nl'
Check_Rec.fieldSeparator = ,
Check_Rec.endSeparator = 'nl'
In SXMB_MONI, i can see that the data is correctly extracted from proxy, and correctly mapped to receiver message, and i see a checkered flag (success).
But, Adapter status is RED with the following error message:
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
In communication channel monitoring, i get the following error message:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages
What is going wrong here? Can anyone please tell me?
Thanks
Chandra

Posted in Incorrect forum.
Posted again in Process Integration forum

Error in Receiver File adapter using File content Conversion

Hi,
I am getting the following error in the receiver file adapter.
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'statement.fieldFixedLengths' or 'statement.fieldSeparator' is missing
I am using the below parameters for FCC:
Recordset Structure - statement
statement.endSeparator - 'nl'
statement.fieldSeparator - '0X09'
statement.fieldNames -xblnr,wrbtr,newbs,kostl,newko,prctr,xref1,rke_wwfud,rke_wwst3,blart,bukrs,bldate,budat,gjahr,monat,ctype,waers,bktxt,posnr,wbs_element,mwxkz,businessplace,businessplace,c_waers,c_wrbtr,g_ctype,g_waers,g_wrbtr,h_ctype,h_waers,h_wrbtr,trade_id,lob,sgtxt,zuonr,reason_rev,ldgrp,tcode,lifnr
ignoreRecordsetName - true
Please let me know where i am going wrong.
Thanks,
Aparna

Hi Aparna,
I feel the problem in your content conversion parameters is with
statement.fieldNames and ignoreRecordsetName
When you are confirguring receiver file adapter for file content conversion the above one is not required. Please refer below link for details on configuring content conversion in file adapter
[http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/frameset.htm]
Hope this helps !!
Regards,
Amit

File Content Conversion Parameters in FIle Adapter

Hi
I am doing a scenario - XML file to Text file using File content conversion parameters in Receiver File Adapter Channel.
I given FCC Parameters like:
DATA.addHeaderLine - '0'
DATA.fieldSeparator - ,
DATA.endSeparator - 'nl'
But im getting error in Receiver File Adapter as - fieldSeparator not specified.
i would be greatful if any one help me.
Regards
Rajesh

Hi Rajesh,
There are lot of blogs which explain File Content Conversion in different scenarios:-
/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
I hope this helps.
Regards.
Praveen

Problem with Sender Adapter File Content Conversion

Hi all!
I have a question about file content conversion in sender file adapter.
I have file like:
{field1
field2
field3
field4
$
{field5
field6
field7
field8
And i need to get file like:
<dealings>
<deal>
<field1>{field1</field1>
<field2>field2</field2>
<field3>field3</field3>
<field4>field4</field4>
<field5>-}*</field5>
</deal>
<deal>
<field1>{field5</field1>
<field2>field6</field2>
<field3>field7</field3>
<field4>field8</field4>
<field5>-}*</field5>
</deal>
</dealings>
I put content conversion parameters:
deal.fieldSeparator = $
deal.fieldNames = field1,field2,field3,field4,field5
And i get a file like:
<ns:mt_swift_file>
<dealings>
<deal>
<field1>{field1</field1>
</deal>
<deal>
<field1>field2</field1>
</deal>
<deal>
<field1>field3</field1>
</deal>
<deal>
<field1>field4</field1>
</deal>
<deal>
<field1>-}*</field1>
</deal>
<deal>
<field1/>
</deal>
<deal>
<field1>{field5</field1>
</deal>
<deal>
<field1>field6</field1>
</deal>
<deal>
<field1>field7</field1>
</deal>
<deal>
<field1>field8</field1>
</deal>
<deal>
<field1>-}*</field1>
</deal>
</dealings>
</ns:mt_swift_file>
What i do wrong?
As i understand, XI put string to a separate tag after symbol 'nl', but how can i get structure without unnecessary tags?

Hi,
Check some links for FCC
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
File Receiver with Content Conversion
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
How to send a flat file with various field lengths and variable substructures to XI 3.0
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
File Content Conversion for Unequal Number of Columns
Content Conversion ( The Key Field Problem )
The specified item was not found.
File Receiver with Content Conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani

File Content Conversion in JMS Adapter

Similar Messages

Maybe you are looking for