Error in RTW for file content conversion

Hi,
In my scnario there are one header,0..unbounded master,0..unbounded detail,one trailer.
proxy to file scnario.
when the file is finally generated that is for particulam one employee.
mapping is successful.
what shoul i do for when 2 employee records coming from ABAP side?
file contain conversion:
record Structure : Header,1,Master,,Detail,,Contact,,Earnings_History,,TAMS,*,Trailer,1
Name and value all things are correct in Content parameter.
but one error is coming.
the error is :
MP: Exception caught with cause javax.resource.ResourceException: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: (4408) Parameter 'xml.1.fieldFixedLengths' or 'xml.1.fieldSeparator' is missing (4409)
How i solve this error??
Regards,
Sanghamitra

Hi,
Have you provided the field separator and endSeparator for each recordset structure??? Its saying fieldSeparator is missing. Please provide fieldseparators like ...
Header.fieldSeparator -','
Master.filedSeparator-','
Master.endSeparator-'nl'
Regards
Priyanka

Similar Messages

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

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

DT for File Content Conversion scenario

Hi Guys,
I am working on IDOC to file scenario in which I want to know which type of DT should I go for?
DT_Type
....Row
......Filed1
......Filed2
......Field3
...Row
DT_Type
Or
DT_Type
..Details
....Row
......Filed1
......Filed2
......Field3
...Row
..Details
DT_Type
I am going for Receiver Content conversion as I need to produce Flat like, I have about 30 filed names and I am wondering is it possible not ot mention field names in Content conversion?
What is the parameter to place to get a new line after each record? I am using row.endSeparator as 'nl' I am getting some special character instead of starting a new record in next line.
Thanks
Rajeev

HI,
The SOURCE IDOC strcuture is:
IDOCNAME----
1..1
>IDOC--
1..1
>BEGIN--
required
>EDI_DC40--
1..1 (it has sub nodes but not required)
>E1KNAM1--
1..1
>SEGMENT----
Required
>Werks----
0..1
>Z1KNU2----
0..1 (SUB SEGMENT OF E1KNAM1)
>ZNUM----
0..1
>Z1ADD----
0..7 (SUB SEGMENT OF E1KNAM1)
>PostCode----
0..1
>E1KAVVM----
0..999(SUB SEGMENT OF E1KNAM1)
>VTWEG----
0..1
>LOVEM----
0..1
>E1KAVPM----
0..999(SUB SEGMENT OF E1KNAM1)
>KUNN2----
0..1
>Z1KAN--0..1 (SUB SEGMENT OF E1KAVPM---(SUB SEGMENT OF E1KNAM1))
>NAME1----
0..1
Target File structure is:
MT_Type----
1..1
Row--
0..Unbound
Filed1----
0..Unbound
Filed2----
0..Unbound
Filed3----
0..Unbound
Filed4----
0..Unbound
Filed5----
0..Unbound
Filed6----
0..Unbound
if IDOC contains one IDOC data then it has to generate one file .. If IDOC contains more than one IDOC information then it has to generate one file with multiple IDOC informaiton in it.
how this can be achieved?
Thanks
Rajeev

Key field values for file content conversion at sender communicationchannel

Hi all,
I am working on scenario File to Idoc.In this scenario at the sender side we configure the file content conversion for .CSV file.
In the flat file i am having more than one orders, XI will pick the file and creates a separate Idoc for each sales order at r/3.
We have similar fields "Order Item Number" both header and item.
If we got '00000' on the Header item then it should create a new idoc at the r/3 side other wise it will create line item.
Order item number will be 00000 for header but it will differ from order item to item.
source structure
Order Header
Order type
Sold-to-code
PO number
Order item number
Order date
AdresName1
AdresName2
Street and House number
Postal Code
City
Country Code
Filler
Order Item
Order type
Sold-to-code
PO number
Order item number
Order date
Product code
Order quantity
Item text
Filler
Now I have some questions....
I don't have standard filed values to give the key fileds at source structure.
I need to create the Idoc at r/3 system for each individual record.
Is it possible to create new idoc with out using the Key filed value?
If it is possible then how can i proceed with fcc?
please give me your valuable suggestions
Best Regards,
satya
Edited by: satyatanuku on Mar 3, 2010 1:41 PM
Edited by: satyatanuku on Mar 3, 2010 1:42 PM
Edited by: satyatanuku on Mar 3, 2010 1:44 PM

Hi,
Just check the Content Conversion Parameters- Recordset Structure.
If you have filled in this parameter with
Header,1,Item,1
then change it to
Header,1,Item,3
Regards
Chandra

Inconsistent Data for File Content Conversion

HI XI Friends,
Its IDOC to File Scanario,
File is of .txt file..
my IDOC contains 14 segments
some times some segements will not come with Idoc..
first three characters represent segment numbers..
structure of txt file
00112345       address1 street1
00212345       office1      street1
00312345       homw2     city2     street2
if that IDOC doent contain 002..then .txt file should be..
00112345       address1 street1
00312345       homw2     city2    street2
all Segement in that idoc are optional..
if I use Fixed lengh in File Content Conversion then ther would be blank row for 002 if that IDOc doent Conatin
00112345       address1 street1
00312345       homw2     city2    street2
please guide me...how to use content conversion in this case..
regards
Munna

Hi ,
Thank you very much for your response..
.txt file is of fixed lenths with no field Seperator
IDOC contains number segements..
the resultant txt file if we created first 3 segements data..
00112345 address1 street1
00212345 office1 street1
00312345 homw2 city2 street2
if we create 001 segment and 003 segement the text file should be
00112345 address1 street1
00312345 homw2 city2 street2
but for new row of each segment ... endseperator 'nl' after first segemnt in Content conversion parameter and 002 segement values..and again endSeperator 'nl'...
if we are not sending 002 segement data in the IDOC ..then it will give blank
00112345 address1 street1
00312345 homw2 city2 street2
my requirement is if we dont send 002 segement data then no blank row .how to check if the segement is having data or not and also how to declare it in Content Conversion parameters of File Adapters.
please guide me
regards
Munna

Unequal Number of rows for File Content Conversion

hi xi friends,
in my idoc to file ..
please help me in content conversion parameter for unequal number of rows .
the message type for external system..
root
row1
    f1
    f2
    f3
row2
    f4
    f5
row3
    f6
if i send idoc with data for all three rows
the resultant txt file
f1-valuef2-value f3-value
f4-valuef5-value
if i send idoc with data for row1 and row3
the resultant txt file
f1-valuef2-value f3-value
f6-value
if i send data for row2 and row3
the resultant txt file
   f4valuef-5vaue
   f6-value
in static message mapping ,i eleminated the rows which are not getting the data from idoc
eg:if the data for row2 does not exist ,then i elimated in message mapping.
all the fileds are fixed lenths like f1 3char and f2 8char etc..
and i dont require header names.
please guide me how to declare in Content Conversion for this unequal number of rows of fixed lenth columns.
regards
Munna

Hi Jai,
Thanks alot for your responses..
message mapping look like this,
IDoc-------------------root
segment1--------------     row1
f1------------------- f1
f2------------------- f2
f3------------------- f3
segment2--------------row2
f4------------------- f4
f5------------------- f5
segment3--------------row3
f6------------------- f6
(actually the idoc contains no of segments..i provided sample one above)
test data for f1=1111 f2=AAA f3=ccccc f4=222 f5=BB f6=33
all fields are fixed lenths
if idoc contains all three segments data
then reultant .txt file should be
1111AAAccccc
222BB
33
if idoc contains segment1 and segment3 data
then reultant .txt file should be
1111AAAccccc
33
if idoc contains segment2 and segment3 data
then reultant .txt file should be
222BB
33
in message mapping I eleminated the target message type segments
if that idoc doent contain data.eg:if the idoc doent contain data for segment2,
i eleminated in message mapping.
please guide me how to declare File content conversion parameters for this unequal number of rows
of rows.
regards
Munna

PI 7.1 Error:- Receiver Adapter with File Content Conversion

Hi,
I am doing XML to Flat file scenario in PI 7.1.
I have done Recevier side below configuration:_
Recordset Structure - Contact,*
Contact.fieldNames Name,LastName
Contact.fieldFixedLengths 10,20
But still it is throwing error in Recevier Communication channel monitoring.
ERROR-
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
Do the needful.
Thanks,
Anshul

you never give the occurrence in the receiver recordset structure.
i.e it will never be,
a,*,b,*,c,1,d,1 etc but it would be just a,b,c,d
ex. /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion

DT and MT definition to be used for File Content Conversion

Hi FCC gurus
would just like to ask, my scenario is Flat File (fixed length) to IDoc
the flat file structure is below:
HHeader.......(Fixed Field until 427characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
DFile ......... (Fixed Field until 404characters)
DText ......... (Fixed Field until 235characters)
DFile ......... (Fixed Field until 404characters)
DText ......... (Fixed Field until 235characters)
-------No Space, for illustration only PO2--------
HHeader........ (Fixed Field until 427characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
DFile ......... (Fixed Field until 404characters)
DText ......... (Fixed Field until 235characters)
DFile ......... (Fixed Field until 404characters)
DText ......... (Fixed Field until 235characters)
-------No Space, for illustration only PO3--------
HHeader........ (Fixed Field until 427characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
HText ......... (Fixed Field until 234characters)
DFile ......... (Fixed Field until 404characters)
DText ......... (Fixed Field until 235characters)
DFile ......... (Fixed Field until 404characters)
DText ......... (Fixed Field until 235characters)
where:
HHeader = Header
HText = Header Text
DFile = Order Detail File (Line Item)
DText = Order Detail File Text (Line Item Text)
As shown above, 1 flat file can contain 3 purchase orders in it structured exactly like the structure definition above.
I need to map this to 1 IDoc for each purchase order
so my target structure should be:
- ORDERS05
   - IDoc (PO1)
   - IDoc (PO2)
   - IDoc (PO3)
Of course I need to use FCC for this, I'm just a little confused on how I will define the Data Type and Message Type for this.
For the Data Type should i define it like this:
DT_ORDERS
   HHeader-Field1 (Element)
   HHeader-Field2 (Element)
   HHeader-Field3 (Element)
   HText-Field1 (Element)
   HText-Field2 (Element)
   HText-Field3 (Element)
   DFile-Field1 (Element)
   DFile-Field2 (Element)
   DFile-Field3 (Element)
   DText-Field1 (Element)
   DText-Field2 (Elemen
t)
OR
should i define the Data Type like this:
DT_ORDERS
    HHeader (Element)
       HHeader-Field1 (Sub Element)
       HHeader-Field2 (Sub Element)
       HHeader-Field3 (Sub Element)
    HText (Element)
       HText-Field1 (Sub Element)
       HText-Field2 (Sub Element)
       HText-Field3 (Sub Element)
    DFile (Element)
       DFile-Field1 (Sub Element)
       DFile-Field2 (Sub Element)
       DFile-Field3 (Sub Element)
    DText (Element)
       DText-Field1 (Sub Element)
       DText-Field2 (Sub Element)
Kindly advise which one is the correct definition   (Or if I am missing something out e.g. Recordset element betweend DT_ORDERS and HHeader)
Thanks in advance
Edited by: HJ Dlec on Aug 13, 2010 4:13 AM
Edited by: Prateek Raj Srivastava on Aug 13, 2010 2:29 PM

>Kindly advise which one is the correct definition
Second approach is fine..
>(Or if I am missing something out e.g. Recordset element betweend DT_ORDERS and HHeader)
Yes do this as well

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

Error regarding File content conversion

Hello all,
I am getting the below mentioned error,
com.sap.aii.af.ra.ms.api.MessagingException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value '')', 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: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value '')', probably configuration error in file adapter (XML parser error)'
My scenario is rfc -> file.In receiving adaptor it is giving me this error. I am not able to understand whats going wrong with it.I have checked the parameters specified for file content conversion i think they are fine.
Please can anyone help me to get out of this..
ZZSP.addHeaderLine      0
ZZSP.fieldFixedLengths     6,8,2,6,8,2,148
ZZSP.fixedLengthTooShortHandling     Cut
ZZSP.endSeparator     'nl'
ZZRP.addHeaderLine      0
ZZRP.fieldFixedLengths     3,1,2,4,2,6,1,2,2,7,9,2,7,8,5,5,6,12,8,4,6,6,3,2,67
ZZRP.fixedLengthTooShortHandling     Cut
ZZRP.endSeparator     'nl'
ZZTOT.addHeaderLine     0
ZZTOT.fieldFixedLengths     3,1,2,2,2,10,35,2,2,10,35,12,12,12,12,12,12,1,14
ZZTOT.fixedLengthTooShortHandling     Cut
ZZTOT.endSeparator     'nl'
ZZSUB.addHeaderLine      0
ZZSUB.fieldFixedLengths     3,1,2,10,3,2,2,3,3,6,3,25,25,6,1,12,12,12,12,12,25
ZZSUB.fixedLengthTooShortHandling     Cut
ZZSUB.endSeparator     'nl'
ZZLIN.addHeaderLine      0
ZZLIN.fieldFixedLengths     3,1,2,5,2,12,23,2,8,3,6,2,9,3,5,3,3,4,4,1,9,12,12,10,10,12,3,10,1
ZZLIN.fixedLengthTooShortHandling     Cut
Edited by: Siddhesh Pathak on Nov 3, 2008 2:19 PM
Edited by: Siddhesh Pathak on Nov 3, 2008 2:19 PM
Edited by: Siddhesh Pathak on Nov 3, 2008 2:20 PM

ur FCC is not configured correctly, I can not see fieldNames in the FCC.
wat is the strucutre of ur file?
r u having any key field in ur file?
refer sample example:
Content Conversion (Pattern/Random content in input file)
How to send a flat file with various field lengths and variable substructures to XI 3.0
chirag
Edited by: Chirag Gohil on Nov 3, 2008 7:34 PM

Error whil doing File Content Conversion

Hi all,
I had configured a sender for File Content Conversion and I am getting the follwoing error.
Sender Adapter v1014 for Party '', Service 'bs_xml_sender':
Configured at 05:39:05 2007-04-27
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Format error in 'xml.recordset' argument: incomplete structure (name,number) pair.
Any ideas why I am getting this error.

Here is the detailed error message.
"Messages:16:40:41 Start of test
- Cannot produce target element /ns:mt_receiver/PO_NUM. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
16:45:01 End of test
16:45:10 Start of test
- Creating Java mapping com/sap/xi/tf/_mm_Sender_Receiver_
- Loaded class com.sap.xi.tf._mm_Sender_Receiver_
- Call method execute of the application Java mapping com.sap.xi.tf._mm_Sender_Receiver_
- *** START APPLICATION TRACE ***
- Document start
- Start tag [ns:mt_receiver]
- Add raw attribute [ xmlns:ns="http://xml2xml"]
- Cannot produce target element /ns:mt_receiver/PO_NUM. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
16:45:12 End of test

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

Doubt regarding Sender adapter file content conversion to RFC

Hi Experts,
Below is the my Source and Target XML structure ( i have creaated source structure same as target RFC structure), This scenario is working fine when i give XML file as input. File -> XI -> RFC , xml file is able to update the information in R3.
How should i configure sender file adapter for file content conversion for above structure(in this case input is fixed lenth text), and i could able to change source structure according to our req, without changing target RFC strucuture.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_HSA_IDNumber xmlns:ns0="urn:passhe.com/UpdateIdNumberISA32">
   <COMMIT_I>X</COMMIT_I>
   <IDENTIFICATION>
      <STUDENT>6500001191</STUDENT>
      <ID_TYPE>FS0030</ID_TYPE>
      <ID_NUMBER>testxml</ID_NUMBER>
      <VALID_FROM>20070421</VALID_FROM>
      <VALID_TO>20091231</VALID_TO>
   </IDENTIFICATION>
</ns0:MT_HSA_IDNumber>
I have configured sender file adapter with FCC like :
Document name as: MT_HSA_IDNumber
Document name space as: urn:passhe.com/UpdateIdNumberISA32
Record structure as: COMMIT_I,1,IDENTIFICATION,1
COMMIT_I.fieldNames : COMMIT_I
COMMIT_I.fieldFixedlengths: 1
IDENTIFICATION.fieldNames: STUDENT,ID_TYPE,ID_NUMBER,VALID_FROM,VALID_TO
IDENTIFICATION.fieldFixedlengths: 12,6,60,8,8
i am getting error like this: even when i change source structure like below metioned:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_HSA_IDNumber xmlns:ns0="urn:passhe.com/UpdateIdNumberISA32">
   <COMMIT>
      <COMMIT_I>X</COMMIT_I>
   </COMMIT>
   <IDENTIFICATION>
      <STUDENT>6500001191</STUDENT>
      <ID_TYPE>FS0030</ID_TYPE>
      <ID_NUMBER>idnumber1</ID_NUMBER>
      <VALID_FROM>20070421</VALID_FROM>
      <VALID_TO>20091231</VALID_TO>
   </IDENTIFICATION>
</ns0:MT_HSA_IDNumber>
Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'COMMIT_I.fieldFixedLengths' or 'COMMIT_I.fieldSeparator' is missing Consistency check: no. of arguments in 'COMMIT_I.fieldFixedLength' does not match 'COMMIT_I.fieldNames' (0 <> 1)
Please help me out
thanks
dhanush

Hi Dhanush,
Try giving the Sender FCC this way for the source structure you have mentioned above.
Record structure as: COMMIT,1,IDENTIFICATION,1
COMMIT.fieldNames : COMMIT_I
COMMIT.fieldFixedlengths: 1
Hope this helps.
Thanks and Regards,
Induja

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

Error in RTW for file content conversion

Similar Messages

Maybe you are looking for