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.

Similar Messages

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

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

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.

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

Reciever content conversion for File adapter.

Hi ,
I am doing Idoc to file scenario,it is working fine without any FCC in the reciever file adapter but its failing when I use FCC.getting the error like
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'STRUC.fieldFixedLengths' or 'STRUC.fieldSeparator' is missing "
I know this error is because of FCC problem.
I am getting this xml structure without FCC in the rec file adapter
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:DataRec_MT xmlns:ns0="http://xyz.....">
- <SET>
- <STRUC>
<PERNR>0000185</PERNR>
<ENAME>xyz m xyz</ENAME>
<NACHN>xyz</NACHN>
</STRUC>
</SET>
</ns0:DataRec_MT>
I want to get 00000185||xyz m xyz ||xyz format
I am using these FCC parameters
STRUC.fieldNames fld1,fld2,fld3 etc
STRUC.fieldSeparator ||(do I need to put this in ' ' ?)
STRUC.endSeparator 'nl'
do I need to add any more parameters or not supposed to use any parameters.
please help.
I tried with different combinations but no luck.
i have DT created with stucture like
DT_xyz
Recset
Record set structure.
and I maintained all with the same case for field names,recordset structure,record set etc
I searched blogs and links,and I will keep on.
and what if if we dont get a value for a field in the record structure?whole FCC gonna fail?
thank you,
Babu

Ramana and Raj,
I tried both options but,still getting error.
Recordset structure : STRUC
STRUC.fieldSeparator ||
STRUC.endSeparator 'nl'
or
Recordset Structure: STRUC
Try with these parameters
STRUC.addHeaderLine=0
STRUC.fieldSeparator = ||
STRUC.endSeparator = 'nl'
I get this error in File CC
Channel has not been correctly initialized and cannot process messages
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'STRUC.fieldFixedLengths' or 'STRUC.fieldSeparator' is missing 
and when I furthur click on the message ID in CC I get this error
Success File adapter receiver: processing started; QoS required: ExactlyOnce
2007-08-01 08:02:57 Error File adapter receiver channel CC_File_RECV is not initialized. Unable to proceed: null
2007-08-01 08:02:57 Error Exception caught by adapter framework: Channel has not been correctly initialized and cannot process messages
2007-08-01 08:02:57 Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages
any suggestions?
thank you.

File Content Conversion - Sender File Adapter - Record Delimeter ~

The inbound file has file has ~ as record delimeter. I am using the FCC at sender file adapter to covert this file into XML. Somehow, the file adapter is not able to interpret "~" as my record delimeter even thoough I specified "record.endSeparator = ~" in FCC.
Would someone help me with a solution?

Raju,
You can also try to use the '0x7E' as endSeperator condition.
I am not sure if the HTML tag will work but this should do the trick. This should be the HEX corresponding entry
char description hex char code html
" ~ " "Tilde" "0x7e" "~" &!tilde; (without !)
greets.
in adition to this see SAP help
http://help.sap.com/saphelp_nwpi71/helpdata/en/44/655453b48a4ddfe10000000a1553f7/frameset.htm
Special Characters in Strings for Separators
In all strings for separators (NameA.fieldSeparator, NameA.beginSeparator, NameA.endSeparator), you can specify non-printable ASCII characters. These characters can each be inserted individually in the strings in the form ´0xHH´ (including the quotation marks), where HH represents the character encoded as a hexadecimal value.
Please also ensure that the "recordSet Structure" also need to be configured Correctly
for example:
Header,1,Detail,*
Header.fieldSeperator --> %parameter%
Detail.fieldSeperator --> %parameter%
Detail.endSeparator --> '0x7e'
Greets

Doubt: addHeaderLine File Content Conversion Recever File adapter.

Hi,
Below XML Target Structure ( Recever File Adapter- FCC)
<?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>
Recever File Adapter- FCC : i have done below configurations.
BUSINESS_PARTNER.addHeaderLine = 1 ( i tryed with value 2 also) and also tryed with item.addHeaderLine = 1 ( i tryed with value 2 also) i am not getting Header line in my out put file and rest fine
Recordset Structure: BUSINESS_PARTNER,item
BUSINESS_PARTNER.fieldNames : item
BUSINESS_PARTNER.fieldSeparator: ,(comma)
item.fieldNames : CAMPUSCODE,STUDENTNUMBER,ST_OBJID
item.fieldSeparator : , (comma)
BUSINESS_PARTNER.addHeaderLine = 1 ( i tryed with giveing value as 2) and also tryed this way also item.addHeaderLine = 1 ( i tryed with giveing value as 2) i am not getting XML Header line in my out put file and rest is working fine. please help me out.
Thanks,
Dhanush

Dhanush,
According to help.sap.com standard structure
<root>...
<nameA>
<value1>value</value1>
<value2>value</value2>
<value3>value</value3>
</nameA1>
<nameB>
<value4>value</value4>
</nameB>
</root>...
I guess if you reduce it to one level like by removing item or BUSINESS_PARTNER it should work.
http://help.sap.com/saphelp_erp2004/helpdata/en/0b/9a50465ccf84479e39a6d50c90fb3f/frameset.htm
Gaurav Jain

Content Conversion in File Receiver Adapter

Hi,
I am doing a Content Conversion in File Receiver Adapter.
Input to the Adapter is:
<ns1:FileResponse_MT xmlns:ns1="http://www.bpmtest.com/bpm">
 <OrderID>123</OrderID>
 <Quantity>98</Quantity>
 <Price>76.23</Price>
</ns1:FileResponse_MT>
Desired output is: OrderID# Quantity# Price (123#98#76.23)
I tried to accomplish this with different settings in Recordset Structure and Conversion Parameters but could not achieve it, every time an empty file is produced.
Would appreciate any help on this.
Best Regards,

Hi,
Enclose your structure with a parent element like this.
<ns1:FileResponse_MT xmlns:ns1="http://www.bpmtest.com/bpm">
<parent>
<OrderID>123</OrderID>
<Quantity>98</Quantity>
<Price>76.23</Price>
</parent>
</ns1:FileResponse_MT>
Then give the parameters, it will work.
parent.fieldSeparator = '#'
parent.endSeparator = 'nl'
Regards,
P.Venkat

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.

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

Problems with content conversion in File Receiver Adapter

Hello, everybody.
 I have a RFC-to-File scenario with file content conversion. Everything is working well except that my file is generated with 2 blank lines at the top of it.
 The function module has 3 importing parameters (1 optional) and the file content comes from an internal table.
 Is it caused by the function module parameters? If yes, how can I avoid this, once I really need them? If not, does anyone have any idea?
 Thanks a lot,
 Marcos.

Hi, Raj.
Here they are the function module parameters:
Importing parameters:
 ICARRIER TYPE CHAR1
 FPATH TYPE IPATH
 IFILE LIKE VBAK-BNAME
Tables
 IYLASDS_RECPT LIKE YLASDS_RECPT
The structure YLASDS_RECPT has only one field with a single line of the file. I am using this field as the Recordset Name inside file adpater parameters.
There is no mapping between RFC and FTP messages.
Thanks a lot,
Marcos.

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 in File Adapter

Similar Messages

Maybe you are looking for