Purpose of message protocol file and file content conversion

hi
i am currently working in idoc to file scenario,
In what cases we will go file and file content conversion in message protocol for file adapter.
can anyone specify the real significance of it? bcoz this may help me and continue my scenario in its suitable path.
Regards
Saravanakumar PK

Hi,
In XI (internal) all XML message are based on the XI Message Protocol.
See: http://help.sap.com/saphelp_nw70/helpdata/en/b6/0b733cb7d61952e10000000a11405a/frameset.htm
XI Protocol is nothing but an SAP XI extension of SOAP protocol and SOAP protocol is nothing but a SOAP request in a HTTP protocol. SOAP request is nothing but SOAP extension of an XML message. Hence finally it drill downs to the fact that XI message is in fact an XML message with some extra information in the header which are SAP specific like the SAP Runtime, SAP Hoplist, etc...
File Content Conversion
Integration Engine understands only XML messages.Now if u r handling normal text file such as 'tab separated' file,'# separated' file, or a CSV file, you need to convert the content of the file to XML and File Content Conversion mechanism helps to do this job.This File Content conversion mechanism(option)is present with the File Adapters.both Sender and Receiver.
How to do FCC:
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2006/04/03/xi-in-the-role-of-a-ftp
Thanks
Swarup

Similar Messages

Issue w/ File content conversion (Receiver side)

Folks, there seems to be an issue with the conversion. I've read several of threads on this forum, but none helped! Although the file is generated with 8 bytes there seems to be nothing in the file.
However when 'File' message protocol is used, the xml file is generated correctly as expected. All my other settings are fine.
Here is the scenario:
1) created Message type -
MTX
..Material
..BaseUnit
..MatGrp
..Division
2) comm. channel created for -
Transport protocol: File (NFS)
Message protocol: File content conversion
Recordset Structure: MTX
parameters:
    MTX.fieldSeparator: ,
    MTX.endSeparator: 'nl'
Should recordset struc. and parameters have 'ns0' prefix, i.e.,
Recordset Structure: ns0:MTX
parameters:
    ns0:MTX.fieldSeparator: ,
    ns0:MTX.endSeparator: 'nl'
What esle is missing? any thoughts are welcome.
Thanks and appreciate your responses.

Hi ABAP JUNOON,
Could you please create another Test scenario and
try
MTI_XXX
     - DATA(0..unbounded)
         - fields?
i mean, without redundant RS(Record Structure).
and use
Transport protocol: File (NFS)
Message protocol: File content conversion
Recordset Structure: DATA.
it will written the complete output file.
some people create the Reciver data type for test scenario's as follows.
MTI_XXX
   -RS
     - DATA(0..unbounded)
         - fields?
i mean with redundant RS
in this case file is generated, but nothing will be appear.
so plz take care while creating the reciver data type with FCC.
and the following case also will work i.e
MTI_XXX
   -RS
     -Header(0,1)
         - fields?
     - DATA(0..unbounded)
           - fields?
     - Trailer(0,1)
         - fields?
Regards
Mahesh.

File Content conversion - IDOC to Fixed length File

Hi,
Scenario : SAP R/3(IDOC) -> XI -> Fixed Length file
IDOC is sending from SAP R/3, XI has to do the mapping and send a Fixed length File to /tmp in XI.
When I am using the message Protocol as "File" in the Receiver communication channel, XML file is writing to /tmp. When I am using "File Content Conversion" as a message protocol,Empty File is writing. Can anybody tell me why empty file is creating. Can we use File content Conversion in this scenario. Is there any additional parameter or settings required?
Receiver communication channel settings:
Message Protocol: File Content Conversion
File type : Binary
Recordstructure : MT_V_PER01
Name Value
MT_V_PER01.fieldFixedLengths 25,35
MT_V_PER01.fieldNames PERSNR,NAME
File Data Type : DT_V_PER01,
Message type : MT_V_PER01
IDOC type : WP_PER01.
Expecting your expert advice.
Thanks
vineesh

Hi Moorthy,
I am getting success messages in Audit log as below:
2006-09-29 12:08:53 Success Trying to put the message into the send queue.
2006-09-29 12:08:53 Success Message successfully put into the queue.
2006-09-29 12:08:53 Success The message was successfully retrieved from the send queue.
2006-09-29 12:08:53 Success The message status set to DLNG.
2006-09-29 12:08:53 Success The message was successfully transmitted to endpoint http://nslcxi08:8010/sap/xi/engine?type=entry using connection AFW.
2006-09-29 12:08:53 Success The message status set to DLVD.
2006-09-29 12:08:53 Success The message was successfully delivered.
I have checked the Payload maindocument,the IDOC structure contains data.
<?xml version="1.0" encoding="UTF-8" ?>
- <WP_PER01>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<IDOCTYP>WP_PER01</IDOCTYP>
<MESTYP>WP_PER</MESTYP>
<STDMES>WP_PER</STDMES>
<SNDPOR>SAPLCD</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>LCDCLNT210</SNDPRN>
<RCVPOR>LXDCLNT250</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>LXDCLNT250</RCVPRN>
</EDI_DC40>
- <E1WPP01 SEGMENT="1">
<PERSNR>0000100006</PERSNR>
- <E1WPP02 SEGMENT="1">
<NAME>Consumer</NAME>
</E1WPP02>
</E1WPP01>
</IDOC>
</WP_PER01>
Thanks
Vineesh

Can't get File content conversion to produce CSV file

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

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

Receiver File Content Conversion concerns

Dear SAP experts,
Need your advise regarding File Content Conversion.
I have here the XML,
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:CSV xmlns:ns0="http://pg.com/xi/tom/connect/edi">
<SLI_root> ---> this is the root node of 'CSVFileName' and 'SLI'
<CSVFileName>Globus_20080306</CSVFileName>
<SLI> ---> this is the root node of the below fields
<PERIO>20071222</PERIO>
<EAN>737052018164</EAN>
<ILN>4304452000004</ILN>
<SALES>16</SALES>
<TURNO>120</TURNO>
<PERFL>W</PERFL>
<SUBSFL>X</SUBSFL>
<SALUN>ST</SALUN>
<CURRENCY>EUR</CURRENCY>
<STOCK>000000000</STOCK>
<STOUN>ST</STOUN>
</SLI>
<SLI>
<PERIO>20071222</PERIO>
<EAN>737052018232</EAN>
<ILN>4304452000004</ILN>
<SALES>3</SALES>
<TURNO>38.699997</TURNO>
<PERFL>W</PERFL>
<SUBSFL>X</SUBSFL>
<SALUN>ST</SALUN>
<CURRENCY>EUR</CURRENCY>
<STOCK>000000000</STOCK>
<STOUN>ST</STOUN>
</SLI>
<SLI>
</SLI_root>
</ns0:CSV>
CSV --> The Message Type of the XML.
SLI_root is under CSV
CSVFileName and SLI are under SLI_root
PERIO, EAN, ILN.. etc. are under SLI
SLI_root is under CSV.
CSVFileName and SLI are under SLI_root.
PERIO, EAN, ILN,... fields are under SLI.
The parameters i've set in Content Conversion are:
Recordset Substructure: SLI_root,SLI
SLI_root.endSeparator: 'nl'
SLI_root.fieldSeparator: 'nl'
SLI.addHeaderLine: 3
SLI.headerLine: PERIO;EAN;ILN...
SLI.fieldSeparator: ;
My output should be,
PERIO;EAN;ILN;SALES;TURNO;PERFL;SUBSFL;SALUN;CURRENCY;STOCK;STOUN
20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;00000000;ST
20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;00000000;ST
20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;00000000;ST
The parameters i've set in Content Conversion are:
SLI_root.endSeparator: 'nl'
SLI_root.fieldSeparator: 'nl'
SLI.addHeaderLine: 3
SLI.headerLine: PERIO;EAN;ILN...
SLI.fieldSeparator: ;
SLI.endSeparator: 'nl'
When i've run my scenario, the output is this,
Globus_20080306;20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;000000000;ST
20071222;737052018232;4304452000004;3;38.699997;W;X;ST;EUR;000000000;ST
20071222;737052018263;4304452000004;1;12.9;W;X;ST;EUR;000000000;ST
20071222;737052018294;4304452000004;1;10.45;W;X;ST;EUR;000000000;ST
The header lines are not present and the value of CSVFileName (Globus_20080306) was inserted in my values.
Kindly advise what is wrong on my parameters set.
Or is there something missing in my configs.
Or i will change my structure of XML ?
Thank you very much!
Fred

Hi Raj,
Im just 4months working in SAP XI, and i still consider myself as a beginner.
I've only used Receiver File Adapter in my scenario (NO Sender File Adapter)
These are the configurations i've made in the Receiver File Comm Channel.
For the Parameters TAB:
File Receiver
Transport Protocol: File System (NFS)
Message Protocol: File Content Conversion
Adapter Engine: Integration Server
File Access Parameters:
Target Directory: * specified directory
File Name Scheme: .csv
Processing Parameters:
File Construction Mode: Create
Write Mode: Directly
File Type: Text
Adapter-Specific Message Attributes
- Use Adapter-Specific Message Attributes
- File Name
Run Operating System Command After Message Processing
Command Line: chmod 664 %F
Content Conversion Parameters:
Recordset Structure: SLI
SLI.addHeaderLine: 3
SLI.headerLine: PERIO;EAN;ILN;....
SLI.field Separator: ;
SLI.endSeparator: 'nl'
Adapter Status: Active
For the Identifiers TAB: (i've had no configs on that)
For the Module TAB:
Processing Sequence:
Number: 1
Module Name: CallSapAdapter
Type: Local Enterprise Bean
Module Key: 0
That's all in my configs in Receiver File Adapter.
Is it ok if you check this?
I've read a SAP Blogs, https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/6400. [original link is broken] [original link is broken] [original link is broken]
I've read in it that there must be set-up in the Module TAB to get the Filename in the Dynamic Configuration.
Kindly advise.
Thank you very much for your usual support.
Fred

Multiline file content conversion-- error

Hi All
I am sending a txt file to CSV format (txt file), I have done IR and ID without errors. Adaptor Monitor shows that
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
I have given '.fieldFixedLengths' or '.fieldSeparator' in the Content conversion parameters in the receiver dommunication channel.
Could you please let me know what could be wrong?
Thanks,
Ram

Thanks Krishnamoorthy, Bhavesh, Priyanka for your reply
The Problem is the file is picked up from the source but not reaches the destination
Sender Communication Channel Details:
Source File format----test.txt (Notepad)
Source Datatype:
FILEINPUT
Record
 Row
 FirstName
 LastName
 MiddleName
 City
 Place
 State
 Country
Content conversion paramerters:
Row.fieldNames---FirstName,LastName,MiddleName,City,Place,State,Country
Row.fieldSeparator---,
Row.endSeparator---'nl'
Transport Protocol---NFS
Message Protocol---File Content Conversion
Receiver Communication Channel Details:
Target File format----Test.txt
Target Datatype:
FOUTPUT_TEST
Record
 Row
 FirstName
 LastName
 MiddleName
 City
 Place
 State
 Country
Content conversion paramerters:
Row.addHeaderLine-----0(zero)
Row.fieldSeparator------,(comma)
Record.fieldSeparator-----'nl'
Row.endSeparator-----'nl'
Transport Protocol---NFS
Message Protocol---File Content Conversion
I am sending a text file and I want to receive it as a text file.
In both, Sender communication channel and Receiver communication channel I am using file content conversion.
Thanks
Ram

Upload flat file (Content Conversion Parameters)

Hello,
I am still trying to upload a flat text file to XI. Its a non separator file.
Here the error message from the XI adaper engine:
Sender Adapter v1508 for Party '', Service 'IXI_FileSystem_CSV':
Configured at 15:36:12 2005-08-03
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: 
Mandatory parameter 'CONTROL.keyFieldValue': no value found
Here all my settings:
Message protocol: File Content Conversion
Document name: CMA_FILEINPUT1
Document namespace: http://www.xyz/ogsd
Recordset name: RECORD
Recordset structure: CONTROL,1,SEGMENT,*
Key Field Name: SEGMENT.DUMMYKEY
Key Field Type: String (cs) -> default
Fields:
CONTROL.fieldNames:TABNAM,MANDT,DOCNUM,DOCREL,....
CONTROL.fieldFixedLengths:10,3,16,4,2,1,1,...
SEGMENT.fieldNames:DUMMYKEY,DUMMY,LOCATIONID,...
SEGMENT.fieldFixedLengths:12,51,10,18,4,10,
SEGMENT.keyFieldValue:E2BPBULOCM03 (string that occurs in the first field DUMMYKEY of SEGMENT)
The message type looks like this:
CMA_MSGTYP1 1:1
RECORD 1:1
 CONTROL 1:1
 TABNAM
 MANDT...
 SEGMENT 0:unbounded
 DUMMYKEY
 DUMMY
 LOCATIONID...
Why do i get that error message? How to fill Key field name correctly? In my opinion i dont need key fields for CONTROL because of the occurence of one.
Any idea?

Thanks to all. So "Key Field Name" is just symbolic?
Here are my new settings:
Message protocol: File Content Conversion
Document name: CMA_FILEINPUT1
Document namespace: http://www.xyz.de/ogsd
Recordset name: RECORD
Recordset structure: CONTROL,1,SEGMENT,*
Key Field Name: KF
Key Field Type: String (cs) -> default
Fields:
CONTROL.fieldNames:TABNAM,MANDT,DOCNUM,DOCREL,....
CONTROL.fieldFixedLengths:10,3,16,4,2,1,1,...
SEGMENT.fieldNames:DUMMYKEY,DUMMY,LOCATIONID,...
SEGMENT.fieldFixedLengths:12,51,10,18,4,10,
SEGMENT.keyFieldValue:E2BPBULOCM03 (from DUMMYKEY)
CONTROL.keyFieldValue: HRETZU (from TABNAM) 
Both key fields are the first entries in the substructures.
Now this error is coming up:
Sender Adapter v1508 for Party '', Service 'IXI_FileSystem_CSV':
Configured at 16:41:24 2005-08-03
Last message processing started 16:41:24 2005-08-03, Error: Conversion of complete file content to XML format failed around position 0 with java.lang.Exception: ERROR converting document line no. 2 according to structure 'SEGMENT':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this
last retry interval started 16:41:24 2005-08-03
length 30,000 secs
What is that for a new parameter(lastFieldsOptional)?

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 -
"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 "
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.

When should message protocol be FILE CONTENT CONVERSION

HI one and all,
What doubt keeps haunting me is when should message protocol be selected FILE CONTENT CONVERSION.
for what format of sender information IS THIS USED ?
Ur answer is awaited.
Thanking you,
Ranjith.

Ranjith,
Consider the below cases u are sending XML file as
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Test_MT xmlns:ns0="urn:test">
 <EmpProfile_Msg>
 <Empno>1001</Empno>
 <EmpName>J</EmpName>
 <DepartmentName>SAP</DepartmentName>
 </EmpProfile_Msg>
</ns0:Test_MT>
But while writing the output u need the file as
1000 , J, SAP
Then u have to go for File Content Conversion at the Receiver adapter.
Similarly ,consider the other way around u are sending the file input as
1000 , J, SAP and u want XML , then u have to do FCC in sender adapter.
Hope it clears!!!
Best regards,
raj.

Mail Adapter and File content conversion.

I have a scenario to send data from SAP to 4 different boards. I have used a Multi mapping for this scenario. I am using Proxy for SAP to xi and SOAP, File and Mail adapter for the external connections.
Questions:
1) I need to send a mail in CSV or Excell format in one scenario. I have used AF_StrictXml2Plain Module but its not working? any thoughts?
2) In the file adapter I have to add the YYYYMMDD (current Date) to the file name? when I use timestamp i get the time too, any way of getting only date? I cant use the Variable substitution as i dont have date in my payload.
3) Receiver File content conversion:
My Message Type Looks like this
MT_XX_XX
     Row
        title
        xxx
I have used these parameters:
Recordset Structure: Row
Row.addHeaderLine : 0
Row.fieldSeparator : ,
Row.endSeparator: 'nl'
am I doing something worng, the file content conversion doesnt work.
Please let me know
Thanks in advance

Hi,
Make sure u are using the bean before the mail adapter bean.
Before using the file content conversion make sure that there are no substructures in it , in order to use addheader line as 0. else use addheaderline 3 and give the headerline as comma seperated values
for e.g if this is the type then addheader line= 0
Type 1 :
Record_Mt
     Row
         field1
         field2
else if this the type then addheaderline = 3
*Type 2: *
Record_Mt
     Row1
         field1
         field2
     Row2
         field1
         field2
add module like this
localejbs/sap.com/AF_Modules/StrictXml2PlainBean
with the module key e.g. key
for type 1 struct (as above )add parameter- key as singleRecordType and value as Row with comma seperated value. (remember header line is 0)
for type 2 structure (as above )add parameter- key as recordTypes and value as Row1, Row2 with comma seperated value. (remember header line is 3)

File content conversion record set per message

Dear All,
Problem:- File is of huge size because of which file content conversion is taking longer time and is failing.
File format:-
Header
Detail
Detail
Header
Detail
Detail
Detail
Detail
Header
Detail
Detail
Trailer
Trailer has total count of all detail record,header record and there are few checks as well as wrt other fields.
We need to do all the above validation on the file and if it successful it shud process it otherwise alert shud be raised.
As a step:-
I have used record set per message for splitting up the file because of huge size this functionality is working fine but because of spitting of file i am not able to do trailer validation as XI is creating multiple records with different message ID's
Is any other approch which will help to achieve both Spliting as well as validation
chirag

Chirag,
simplest scenario I can think of is splitting the 2 reqs.
1. create 2 folders, one for "in process" files and other for "validated" files.
2. create 2 scenarios:
2.1. your current sender system to in process folder (whatever to File).
=> In this you just do the validation, without FCC. You could create a simple module for that or even do it at mapping runtime, as you said (mapping may be easier to handle errors), and throw a runtime exception (which will eventually trigger an alert).
=> At the end, only files that go successfully throug the validation will be located in the "In Process" folder.
2.2. do a simple file to file scenario (from "In Process" to "Validated" folder), this time executing FCC & splitting messages if necessary.
Of course, this will only work if the module/mapping is able to process the large file anyway (hopefully yes, since it will still be a flat file and not XML yet).
BR,
Henrique.

File Content Conversion (receiver) and special characters

Hi all,
I have a scenario that has a file receiver channel with content conversion. The record structure in the flat file is field-width delimited (hence no field separator) and the parameter 'fieldLengthTooShortHandling' has the value 'Cut' because the receiving system needs only specific widths for the fields. Hence if the field value exceeds the length permitted, the extra characters are clipped.
I observed that some characters are not handled properly while creating the text file. For example, one of the fields contained a "minus" character (not the hyphen). The flat file was created successfully. I opened the file in notepad and found that the "minus" character has appeared correctly and the column count in that record was as expected. However when the same file was opened in Textpad, the minus character was displayed as â | | ('a' with caret, bar, bar) So, all the fields after this field were shifted ahead by 2 characters and hence the total column count of the record had gone beyond the actual one.
All this started due to the error reported by the receiver system which processes the flat file. Due to shift of characters in the flat file, the processing failed. Moreover that system cannot process the special characters (like minus or non-Latin accented characters etc.) So although there is no issue in XI interface as such, I just want to know if anyone has more informtion on why the characters are displayed differently as mentioned above.
Regards,
Shankar

Define data type like
order_recordset
order_row 1..unbound
f1
f2
All are same except communication channel configuration,
Message Protcol : File content select, then below you got additional parameters.
there you fill
Document name : Your sender message type.
Document namespace : Give your scenario namespace
Recordset name : order_recordset ( mentioned in the data type)
Recordset structure : order_row, *
Name Value
order_recordset.fieldSeparator : 'nl'
order_row.fieldSeparator : ,
order_row.endSeparator : 'nl'
based on your text file you fill the above parameter values.

Error in mapping and in file content conversion

Dear All,
I am configuring one file-xi-rfc scenario in which the structure of the input file is as follows:
EDI_DC40 2 DELVRY03 SHPCON
E1EDL20 020 0083710164
E1EDL18 020 PIC
E1EDL18 020 PGI
E1EDL18 020 GWT
I want to pick only VBELN from the segment E1EDL20 and post ot to the RFC. In the input file, the above structure is getting repeated for different VBELN.
Please help in configuring the sender DT, MM and in doing File Content Conversion.
Waiting for your reply.
Warm Regards,
N.Jain

Hi,
Check Below Links which will help u to do content convertion at Sender side and Receiver side.
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani
Reward Points if Helpful

Question about File Content Conversion and parent-child relationships...

Hello!
 I have read probably every blog, article and SAP Help document on the topic, but I am stuck on this one. I am trying to convert a General Ledger flat file to an IDoc using the classic file --> IDoc scenario. The setup is done and working, but the IDocs are formatted incorrectly and I believe at least part of the reason is how I am converting the file content.
The root of my problem is that the flat file has a parent-child relationship between the document header and the document item and I want to maintain that since the IDoc type (FIDCCP01) has the same structure in the BKPF and BSEG segments.
Here is the flat (non-XML) file layout that is coming into the file adapter:
FileHeader
DocumentHeader
DocumentItem
DocumentHeader
DocumentItem
and so on (until the number of documents is complete
I would really like the content to be converted so that the line items stay under their parent document headers like this:
<FileHeader></FileHeader>
<DocumentHeader>
 <ItemHeader>
 </ItemHeader>
</DocumentHeader>
<DocumentHeader>
 <ItemHeader>
</ItemHeader>
</DocumentHeader>
But I keep getting this, where it lists the document headers first (one after another), and then all of the line items after the document headers like this:
<FileHeader></FileHeader>
<DocumentHeader></DocumentHeader>
<DocumentHeader></DocumentHeader>
<DocumentHeader></DocumentHeader>
<ItemHeader></ItemHeader>
Is is possible to maintain that parent-child relationship from the flat file and pass it over to the XML?
Thanks,
John

Hi,
Check some links on FCC.
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani
Reward points if Helpful

Problem with File content conversion and parameters

Hi experts,
What is the use of file content conversion that is available in file adapter? For what cases we can use it?
What do the different content conversion parameters mean?
Kindly help
Thanks
Gopal

Hi,
We use the file content convertion to conver the flat file that is text file into XML,
File adapter cant understand the format the file is,so we have to declare the content convertion parameters.
Check some links which will tell how the convertion is done.
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani
Reward points if helpful

Purpose of message protocol file and file content conversion

Similar Messages

Maybe you are looking for