FIle Content Conversion IDOC to Flat file

Dear Experts ,
Getting the below error in the reciever channel . The mapping is generating all the segments in the target structure but when writing to the destination its giving me this error . can some one let me knoe what exactly does this mean [ Column value 'ZXYGRX' too long (>1 for 6. column) ] .
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value 'ZXYGRX' too long (>1 for 6. column) - must stop', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value 'ZXYGRX' too long (>1 for 6. column) - must stop', probably configuration error in file adapter (XML parser error)'
Thanks in advance
Regards
Ganga

once you have to check the below steps:
first one you have to check lenght of the field "ZXYGRX" .might be the field length is more than specified lenght.
second one is ,value is paaing/not.if there is any empty tag coming from source then target structure tag will not be created and because of which ur payload structure and FCC configuration is not matching.
refer below links:
http://forums.sdn.sap.com/thread.jspa?threadID=1736330
http://forums.sdn.sap.com/thread.jspa?threadID=1002255
http://forums.sdn.sap.com/thread.jspa?threadID=1896862

Similar Messages

File Content Conversion i.e Flat file 2 Flat file

Hi guys,
I am new 2 SAP XI
and i am trying 2 do "Flat File To Flat File".
Input File contains following data:
Name:varun
Surname:rajaraman
Address:B-2
Employee no:8204
i.e Each Data is in separate Row.
Output File Should contain the following data:
I am varun rajaraman staying at B-2 bearing employee no. 8204.
(name,surname) (address) (Employee No.)
i.e data should be in a single row.
So, i have a problem of reading the data from input file i.e data from each row and transfering it into output file along with which i need 2 insert "i am " ,"staying at", etc.
pls tell me the procedure in detail.
Thanks and regards
santhosh rajaraman

Hi,
Check this links for file content convertion.
File content conversion sites
/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

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

File Content Conversion doesn't pull file

Hi all,
I have a Comm Channel using File Content Conversion - it does not pick up the file (no message in msg monitor). If I copy the Comm Channel, turn off File Content Conversion, and change the Sender Agreement to use the copied Comm Channel, the file is picked up and a message appears in the message monitor.
Any ideas? Does File Content Conversion expect certain file names/types/etc...?
Also, side question - when I change the sender agreement (or anything else in the CD), SXI_CACHE shows "Unable to refresh cache contents" with various errors, one of them being "LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM"; another said something about IF_HTTP_.. HTTP Communication error or something.
I'll do more searching on this on and post a new topic if necessary...
Thanks,
Brian

I'll try setting those logging settings (don't have access).
In the meantime, here is my content conversion:
Content Conversion info - converting a 3 line type flat file to XML
Example of file layout:
H060412
IC11030416          Example yada yada   EA 110137
IC11030417          Example yada yada   EA 131206
T000002
>First letter is key field RecType (H=header, I=detail, T=trailer)
Doc name:   Material <--msg type
Doc ns:     urn:......
Doc offset: <blank>
RS name:    Material <--data type
RS ns:      <blank>
RS struc:   Hdr,1,Dtl,*,Trl,1
RS seq:     ascending
RS/msg:     1
Key field: RecType
Key type:   String case-sensitive
Hdr.fieldFixedLengths     1,6
Hdr.endSeparator        'nl'
Hdr.fieldNames          RecType,GteamsDate
Hdr.keyFieldValue       H
Dtl.fieldFixedLengths     1,1,18,20,4,6
Dtl.endSeparator        'nl'
Dtl.fieldNames          RecType,ActivityInd,CatalogNum,Description,UOM,ProductClass
Dtl.keyFieldValue       I
Trl.fieldFixedLengths     1,6
Trl.endSeparator        'nl'
Trl.fieldNames          RecType,RecCount
Trl.keyFieldValue       T
Brian

File Content Conversion in EDI to File without Seeburger

<b>Hello Friends,
I am using just 2 fields Name and Address in 864 Transaction code.Can anybody help me how to do File Content Conversion from EDI to Xml.as i am using only 2 levels of hierarchy..Please explain me the step by step process </b>

Dear Kayanth,
My advice to you is if your implementing organization has more then one EDI scenario today or plan to add more EDI scenario to the business is to use the Item Field Content master with the XI.
This tool is powered by NetWeaver and allows to translate all standard EDI messages from txt file to XML.
The tool is represented today by Informatica and is used as a java file deployed in the file adapter.
This will sit-well with the XI development methodology of getting the whole EDI message into the XI in an XML format because in the future you might need more then two fields in the message so modifying the interface will take less time.
Try to look to the future of the implementing organization when it comes to interfaces.
"Quick & Dirty" is not always the best way....usually in the long run - its the worst...
Good luck.
Nimrod.G

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

File content conversion for Pipe delimited file

Hi
i have a scenario ( file-xi-proxy) in whch file is coming in a pipe delimited.
my data type is like
DT_ XXXXX
AwardInfo
Header contains some fileds
DetailRecord contains some fileds
trailer contains some fields
what are content conversion parameters i have to use
venkat

Sedamkar,
Expecting you have one header, multiple details and one trailer then give recordset structure in sender file communication channel as:
Header,1,DetailRecord ,*,trailer,1
In content conversion you should give parameters:
Header.fieldSeparator : |
Header.endSeparator : 'nl'
DetailRecord.fieldSeparator : |
DetailRecord.endSeparator : 'nl'
trailer.fieldSeparator : |
trailer.endSeparator : 'nl'
You may need to change the parameters also according to your strcuture and the file layout. See this SAP help for file content conversion:
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Regards,
---Satish

Create substructures via file adapter - file content conversion

I have a need to create a structure as follows using file content conversion from a flat file
source:
H1~00
S1~1A
L1~1B
S1~2A
L1~2B
S1~3A
L1~3B
<?xml version="1.0" encoding="UTF-8"?>
<ns:x_MT xmlns:ns68="urn:abt.com/IAM">
<DocHeader>
      <Label />
      <type />
</DocHeader>
<DocItem>
      <Ship>
        <Label />
        <type />
      </Ship>
      <Lines>
        <Label />
        <type />
      </Lines>
   </DocItem>
</ns:x_MT>
I can successfully create a x_MT but I do not get the heirarchy (DocItem node) and therefore I'm having trouble on the mapping side.
My file content conversion is as follows:
Document Name: x_MT
Document Namespace: urn:abt.com/IAM
Recordset Name: x_DT
Recordset structure: DocHeader,1,Ship,,Lines,
Recordsets per message: *
Key Field Name: label
DocHeader.fieldSeparator     '0x7E'
DocHeader.endSeparator             'nl'
DocHeader.fieldNames             label,type
DocHeader.keyFieldValue         H1
Ship.fieldSeparator     '0x7E'
Ship.endSeparator     'nl'
Ship.fieldNames             label,type
Ship.keyFieldValue      S1
Lines.fieldSeparator     '0x7E'
Lines.endSeparator     'nl'
Lines.fieldNames     label,type
Lines.keyFieldValue     L1
What I get is a structure without the node DocItem and therefore appears like a flat structure and mapping fails since I have multiple 'Lines' and only the last one gets mapped.
I've read all the weblogs around this topic and none seemed to address more than one node. Please help.
Thank you,
Parimala

Hi Parimala,
As per SAP help document the structure created by content conversion would look like this..
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
<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>...
If you require a <DocItem> node then you have to handle this in mapping.
Regards
Anand

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

File-Sender: Verification of file content during file content conversion

Hello,
I have a question regarding file verification when using the file-sender adapter.
I got a flat file (.csv) that I convert into XML with the file-sender adapter and file-content-conversion.
In the file there is a column RecTyp that is my KeyFieldValue. Possible values for RecTyp are B, D, U, T.
So far so good. All this works perfectly.
If (due to an error) there is another value in RecTyp than the 4 mentioned above (B;D;U;T) the file adapter ignores this row today. And here begins my issue:
I want to change this behavior. That means in detail, I want to check if there is another value in my KeyFieldValue RecTyp than specified. If this is the case an exception should be thrown. The whole message should not be delivered.
We had the idea to use the module-processor for this verification.
But may be there are other suggestions. Or may be some one can provide an appropriate module that is already written, etc.
Does anyone have an idea?
Kind regards,
Tobias

Hi,
It is better to pick the file in generic way i.e Row by Row and then go with the validation with the help of Adapter Modules or in the Mapping.
For more-
/people/sravya.talanki2/blog/2005/08/16/configuring-generic-sender-file-cc-adapter
Thanks,
Moorthy

Sender File Content Conversion. Pls suggest

Hi All,
I have to do the Sender File content conversion for the below file.
First Line is for Sender. Second Line is for Receiver. Third ,Fourth and Fifth lines are Invoice Numbers which can be more also.
The issue is coming that there is no Key Field defined for third ,fourth and Fifth line .
GB283032086         LANGFORD LODGE ENGINEERING
GB762702827         AIRBUS UK LIMITED
D58785          20030407         71.82
D58786          20030407         49.10
D58787          20030407         49.10
Pls let me know how will I do Sender File content conversion (to make it in XML) form.
Regards

Hi Rachit,
              In that case you can use temporary source structure to hold contents from the source flat file and using FCC you split the content by 'nl' and store it in one node (For rg:-<SDATA>) then using mapping you can map that to original source structure and then to target structure, here you need to use intermediate mapping (i.e two mappings) to archive the target structure.
Temp source structure
<SDATA>GB283032086 LANGFORD LODGE ENGINEERING </SDATA>
<SDATA> GB762702827 AIRBUS UK LIMITED </SDATA>
<SDATA>D58785 20030407 71.82 </SDATA>
<SDATA>D58786 20030407 49.10 </SDATA>
<SDATA>D58787 20030407 49.10 </SDATA>
Map the above to the actual source structure and the to target, hope it helps you to overcome your problem
[FCC for unequal entries|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID0137316650DB10272139644103542695End?blog=/pub/wlg/2740]
[Key field problem|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID0137316650DB10272139644103542695End?blog=/pub/wlg/3228]
Regards,
Prasanna
Edited by: PrasannaKrishna Mynam on Dec 1, 2009 8:14 AM
Edited by: PrasannaKrishna Mynam on Dec 1, 2009 8:17 AM

Can we handle content convertion for TabDelimiter flat file in JMS

Hi,
Is it possible to handle content conversion for TabDelimiter flat file in JMS (Not in FILE adapter).
If possible .. can you please explain.
Regards,
Siva.

Hi, Siva:
Yes, this is possible.
The way that JMS adapter to handle content cnversion is similar to the way file adapter does.
Different from file adapter, you do not have to specify "Content Conversion" as transport protocol, you need to use transformation bean (localejbs/AF_Modules/MessageTransformBean) in Module tab.
Check page 23 of the following link:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a05b2347-01e7-2910-ceac-c45577e574e0
Liang

Help required File Content Conversion.

Hi All,
Kindly help me in this topic i.e. File Content Conversion.
- What is File Content Conversion?
- Is knowledge of any programming language required?
- What is its function?
- How do I use it?
Thanks in Advance.
Regards,
Sreedhar, Av

Hi Sreedhar,
Reward points if this helps
What is File Content Conversion?
File content conversion is used for converting flat files (fixed lenght, comma seperated) into XML messages for further processing by an integration engine. The internal XI processing (mapping, routing etc) is based on XML messages hence you need messages to be converted to XML.
SAP By default understands xml data structure. If your file is coming in an xml format you can process it as it is.
In case of file that is coming with a delimiter then you need to have File content conversion for SAP adpater to conver file into an XML structure which will then go to next step of Message Mapping.
Is knowledge of any programming language required?
No
What is its function?
Check these blogs for content conversion,
/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
*How do I use it? *
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Reward points if this helps
Regards
Pragathi.

File is not creating on the Receiver for File Content Conversion

Hi,
i have created a scenario with this blog
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
for sender side i am using File Content Conversion to read .txt file and on receiver side i need xml file i have done that.
when i placed the file in the sender folder it gets picked up and i checked in Communication Channel monitporing in Runtime WorkBench it is processed Successfully. but no XML File is created on the Receiver side. i am unable to see the messages on SXMB_MONI also.
Please suggest some ideas to solve this.
Thanks,
Giridhar.C

Hi Giridhar.
unable to see the messages on SXMB_MONI also
If the file got picked and in Communication Channel monitoring RWB you can see that it is processed without any errors ,, then i feel it should come in come.Please check the Audit log in RWB, there you can see the error message if any.
Please check the connection parameters in FTP and make sure that the same sender folder is
not being used by any other scenario.If you have done any recent changes then do a cache refresh .
Please post if you see any error in content conversion.
Regards
Srinivas

Trailing spaces problem during file content conversion

I have developed a proxy to file scenario.And am using file content conversion for creating the file. The file is to be a fixed length file.
File Structure
<Header>
<Item>
<Item Trailer>
<File Trailer>
Each tab in the file has the last character mapped to spaces.
Eg: Header00000001 2006011700000000020060<blank   space>
Item00000001        2006011700000000020060<blank   space>
The problem is that during file content conversion. XI does not preserve trailing spaces at the end of the line i.e.if a particular line in the file ends with space. It terminates the line at the last non-space character (in this case at 060).
However we are required to maintain these trailing spaces at the end of each line.
I have tried preserve white space in data type that does not work.
I know that xslt mapping may solve the problem but I am looking for a workaround with my current graphical mapping.
Looking for suggestions !!
Thanks,
Rashida

Hi,
I have the problem quite opposite to this where we are getting the trailing spaces at end of each record which should not come.
File structure is
<Record>
- <Data>
<Content>11/09/2007@210@ZACSL007@GBB-56436@PS01@29@1044@19@646@0</Content>
</Data>
</Record>
............. n records
<Header>
<File_Name>UK01</File_Name>
</Header>
Record structure in communication channel used is
Header, Data
Data.fieldFixedLengths     1024
Data.addHeaderLine     0
Header.addHeaderLine     0
Header.fieldFixedLengths     0
Header.fixedLengthTooShortHandling     Cut
Data.fixedLengthTooShortHandling     Cut
Header.endSeparator     '0'
Actually if the length of record is less than 1024, rest of the length is being filled with spaces which should not occur.
Many advanced thanks.
Jitender

FIle Content Conversion IDOC to Flat file

Similar Messages

Maybe you are looking for