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

Similar Messages

Content Conversion in JMS Adapter

Hi All,
I am having a scenario JMS - XI - JDBC.
Now I have to do the content conversion in the incming records.
The sample incoming data is as follows:-
<Field1>,<Field2>, ...,<Fieldn>        -->Row1
{<Field1A>,<Field2A>, ...,<FieldnA>}   -->Row2
{<Field1A>,<Field2A>, ...,<FieldnA>}   -->Row3
<Field1B>,<Field2B>, ...,<FieldnB>     -->Row4
{<Field1C>,<Field2C>, ...,<FieldnC>}   -->Row5
{<Field1C>,<Field2C>, ...,<FieldnC>}   -->Row6
{<Field1C>,<Field2C>, ...,<FieldnC>}   -->Row7
Now at the target, we have 3 oracle tables, in which the data from the Row1 &4 will go to Table 1, Row2&3 --> Table2 and Row5,6 &7 --> Table3.
The source data type that i m using is of the structure:-
<TC>
<GT>
    <Field1>
    <GS>
      <Field1A>
    </GS>
    <Field1B>
    <Field2B>
    <GDS>
      <Field1C>
    </GDS>
</GT>
</TC>
Please help me out in the modules configuraton, how this can be handled.
Thanks in advance, hope to receive some solution at the earliest.
Rocky.

Hi Rocky,
Please have a look at these threads..
JMS Adapter: Content Conversion
JMS Adapter Content Conversion
JMS Content Converrsion
Hope these help you!
cheers,
Prashanth

File content conversion - sender adapter for Header and detail records

Hi Experts,
I am receiving a field of fixed length content format.(Header)The first line of the file will follow the structure X having some fields and (DetailRecord)subsequent lines in the file will follow structure Y having somes fields.There is no record identifier for Header and Detail records.In one file first line is Header records and remaining subsequent line is DetailRecord.What are the parameters we have to set for sender file content conversion parameters as i donot have any key field and key field value.And in one file we have only one header records ( first line) and n number of detail records from 2nd line onwards.
Thanks
Deepak

Hi
Refer the below fourm link,
Flat file whitout id
Regards
Ramg.

File content conversion sender adapter

Hi Friends,
I am doing File to IDoc scenario.
I am using File Content Conversion for File Adapter.
My structure look like this
MT_File
HEADER1 1..1
--header1
-- header2
HEADER2 1..1
--header3
DETAILS 1..unbounded
--details1
--details2
--details3
TRAILER1 1..1
-- trailer1
TRAILER2 1..1
-- trailer2
----trailer3
In File Content conversion parameeters..
Document Name :MT_File
Document Namespace :urn:test:FileFcctoIdoc
RecordSet name :
RecordsetStructure :HEADER1,1,HEADER2,1,DETAILS,*,TRAILER1,1,TRAILER2,1
RecordSet Structure: Ascending
RecordSet Per message : *
Key Field Name :header1,header3,details1,trailer1,trailer3
ignoreRecordsetName     : true
HEADER1.fieldNames      :header1,header2
HEADER1.keyFieldValue      : H1
HEADER1.fieldFixedLengths :5,10
HEADER1.endSeparator   :'nl'
HEADER2.fieldNames             :header3
HEADER2.keyFieldValue         : *D
HEADER2.fieldFixedLengths     :5
HEADER2.endSeparator         :'nl'
DETAILS.fieldNames               :details1,details2,details3
DETAILS.keyFieldValue         : 3
DETAILS.fieldFixedLengths     :5,5,5
DETAILS.endSeparator         :'nl'
TRAILER1.fieldNames               :trailer1
TRAILER1.keyFieldValue         : *S
TRAILER1.fieldFixedLengths     :5
TRAILER1.endSeparator         :'nl'
TRAILER2.fieldNames               :trailer2,trailer3
TRAILER2.keyFieldValue         :SE    TRAILER2.fieldFixedLengths    :5,5
TRAILER2.endSeparator         :'nl'
File is :
H1hh1hhhhhhhhh2
*Ddd*
Xddd1dddd2dddd3
Xddd4dddd5dddd6
Xddd7dddd8dddd9
*Sss*
SEKss2
in RWB, Channel CC_FILE_Sender_FccDemo: Empty document found. Proceed without sending message
I think the problem is in FCC paramters..
Could please have a look and correct me
Regards
Ram

Ram,
The problem which i can see is your key field values in your test file. Remember you should have the key field value in each new line at the same place.
For example you have given your text file as shown below...
File Given By You is :
>H1hh1hhhhhhhhh2
>*Ddd *
>Xddd1dddd2dddd3
>Xddd4dddd5dddd6
>Xddd7dddd8dddd9
>*Sss *
>SEKss2
Compair the above file with the below one..
>H1hh1hhhhhhhhh2
>*Ddd *
>Xddd1dddd2dddd3
>Xddd4dddd5dddd3
>Xddd7dddd8dddd3
> *Sss *
>SEKss2
If you notice, for details I have given key field value 3 in each line & at same place.
One more thing just use the KeyFieldName only one ( just follow the same blog which I have given, to understand how to use the KeyFieldName )
e.g.
Document Name :MT_File
Document Namespace :urn:test:FileFcctoIdoc
RecordSet name :
RecordsetStructure :HEADER1,1,HEADER2,1,DETAILS,*,TRAILER1,1,TRAILER2,1
RecordSet Structure: Ascending
RecordSet Per message : *
Key Field Name : KF
Regards,
Sarvesh

Sender File Content Conversion with re-occuring record pairs

Hi,
Our FCC works fine with the following structure:
Header1: H1F1, H1F2, H1F3,... (1:1)
Header2: H2F1,H2F2,H2F3,..... (1:1)
Notes: NF1,NF2,NF3,.............(1:1)
Line1:L1F1,L1F2,L1F3,.............(1:N)
Line1:L1F1,L1F2,L1F3,
Line1:L1F1,L1F2,L1F3,
Line1:L1F1,L1F2,L1F3
Line2:L2F1,L2F2,L2F3,............(1:N)
Line2:L2F1,L2F2,L2F3,
Line2:L2F1,L2F2,L2F3,
Line2:L2F1,L2F2,L2F3,
But we have structure as below:
Header1: H1F1, H1F2, H1F3,... (1:1)
Header2: H2F1,H2F2,H2F3,..... (1:1)
Notes: NF1,NF2,NF3,.............(1:1)
Line1:L1F1,L1F2,L1F3,.............(1:N)
Line2:L2F1,L2F2,L2F3,.............(1:N)
Line1:L1F1,L1F2,L1F3,
Line2:L2F1,L2F2,L2F3,
Line1:L1F1,L1F2,L1F3,
Line2:L2F1,L2F2,L2F3,
Line1:L1F1,L1F2,L1F3,
Line2:L2F1,L2F2,L2F3,
Lin1 and Line2 occur as multiple pairs making it as multiple line items. When we use content conversion parameters as below:
Header1.fieldNames          H1F1,H1F2,H1F2,...
Header1.fieldFixedLengths     10,5,10,.....
Header1.keyFieldValue          H1
Header1.keyFieldInStructure     add
Header1.endSeparator          'nl'
Header1.lastFieldsOptional     YES
and same for Header2, Notes, Line1, Line2
It picks up only first Header1, Header2, Notes, Line1 and Line2 in a recordset.
Does anyone have idea how could we do this content conversion? Any help would be appreciated.
Reagrds,
N@v!n

Hi Navin,
You can check the below links :-
Complex File Content Conversion - with random multiple occurrences
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts
Complex content conversion File sender
These might be of some help.
Regards,
Rohit

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

File Content Conversion : Sender Channel

Hi
I am trying to do content conversion in the Sender Channel from a flat file to a XML.
My Target XML(message structure) looks like
<H1>
<H2>
      <D>Detail Record</D>
      <L1>line</L1>
      <L1>line</L1>
</H2>
<H2>
      <D>Detail Record</D>
      <L1>line</L1>
      <L1>line</L1>
</H2>
</H1>
Here the element <H2> is only needed to group <D> and the following <L1> elements of each new occurrence of <D>.
Now my problem is that the element <H2> is not getting created.
and the message after content conversion is looking as follows
<H1>
      <D>Detail Record</D>
      <L1>line</L1>
      <L1>line</L1>
      <D>Detail Record</D>
      <L1>line</L1>
      <L1>line</L1>
</H1>
What should I do to get the desired result.

@Yes Bhavesh you are right.
Hi Jai,
       I am trying the other way round.i.e from flat file to a XML message.As I said I was trying to do it for Sender Channel where is the after content conversion I want a XML file.The example is a what I framed out of my actual problem.
if flat file is as follows ,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
DetailRecord1
Line1
Line2
Line3
DetailRecord2
Line4
Line5
then the XML must look like
<H1>
<H2>
<D>DetailRecord1</D>
<L1>Line1</L1>
<L1>Line2</L1>
<L1>Line3</L1>
</H2>
<H2>
<D>DetailRecord2</D>
<L1>Line4</L1>
<L1>Line5</L1>
</H2>
</H1>
I identify the different types records in the flat file
as follows,
Record starting with "Detail" is considered as <D> element
Record starting with "Line" is considered as <L> element.
Hope I did clarify.

Strange Problem with File Content Conversion (Sender)

Hi,
I have a strange problem. I have a sender file adapter with content conversion (csv -> xml). The adapter produces the following error during the processing...
- 2006-02-06 16:34:00 CET: Error: Conversion of part of file content of 'OE_Extractor_47_ISW112_SC-Ireland.csv' to XML format failed around position 1202: IOException: Stream closed
After the 4th or 5th try the adapter processes the file correctly.
Why does it works after several tries and not at the first time? (The file is not changed during the adapter is trying to convert it)
Thanks
Thomas

I found the problem, something was wrong with the ftp server

File Content Conversion Sender. Enclosured info

Hi experts,
I have to read a plain file like this:
x
x
x
x
x
<START-OF-FILE>
a;b;c;d;
a;b;c;d;
a;b;c;d;
<END-OF-FILE>
x
x
x
x
x
Where 'x' means unuseful and unformatted lines, and 'a','b','c','d' are the fields to be parsed to xml.
I wonder whether there is a way, using FCC in the file sender adapter, to gather only the lines enclosured between '<START-OF-FILE>' and '<END-OF-FILE>'. There is no key field I can use.
Many thanks in advance,
Paco

Hi Francisco,
I think u need to write a UDF to achieve the requirement.
And, I think there is a possibility to do it using content conversion.
Use set NameA.fieldFixedLengths for the unused data in the file.
use NameA.fieldContentFormatting - Enter trim to remove all the leading and subsequent blanks for a value found. This is the default.
If there is any field length restriction use NameA.fieldFixedLengths.
NameA.fieldSeparator & NameA.endSeparator shoulf be used.
NameA.additionalLastFields
If the inbound structure has more fields than specified in the configuration then the XML outbound structure is created as follows:
○ ignore
Outbound structure only contains the fields in the inbound structure
○ error
Conversion is terminated due to the incomplete inbound structure. An error message is displayed.
The default value is ignore. If you have defined the NameA.fieldFixedLengths parameter, the default value is error.
I hope this info will help you.
Refer the below link:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Regards,

File Content Conversion in JMS Adapter

Hello,
I am trying to use module parameters to convert File to XML in Sender JMS adapter. I have followed the instructions in the SAP document (3.1 Example of a Simple Conversion in a Sender Communication Channel)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50061bd9-e56e-2910-3495-c5faa652b710
The problem I am facing is instead of creating one xml message for all the lines in the file; it is creating one message per line. Not sure what I need to do get all the lines in to one xml message.
Please let me know if any of you have faced similar issue.
Thanks
AV

The Parameter xml.recordsetsPerMessage can only be used if it is a complex structure. I mean it needs a recordSet with Keys..etc and What I am trying to do is a simple FCC using
Transform.Class=com.sap.aii.messaging.adapter.Conversion
Transform.ContentType=text/xml;charset=utf-8
xml.conversionType=SimplePlain2XML
xml.documentName=PurchaseOrder_Root
xml.documentNamespace=http://namespace
xml.fieldFixedLengths =2,10,10,3,..
xml.fieldNames = DATA1,DATA2,DATA3....
xml.processFieldNames=fromConfiguration
xml.structureTitle=PurchaseOrder
<b>I am expecting</b>
<PurchaseOrder_Root>
<PurchaseOrder>
<DATA1> </DATA1>
<DATA2> </DATA2>
</PurchaseOrder>
<PurchaseOrder>
<DATA1> </DATA1>
<DATA2> </DATA2>
</PurchaseOrder>
</PurchaseOrder_Root>
<b>When I use the above Module Config it is giving me </b>
</PurchaseOrder_Root>
<PurchaseOrder>
<DATA1> </DATA1>
<DATA2> </DATA2>
</PurchaseOrder>
</PurchaseOrder_Root>
</PurchaseOrder_Root>
<PurchaseOrder>
<DATA1> </DATA1>
<DATA2> </DATA2>
</PurchaseOrder>
</PurchaseOrder_Root>

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

.csv file Vs .txt file Content conversion sender file channel

Hi Experts,
I have a file with filename say input.csv.I want to do content conversion for these .CSV file.Is it same like we have to do for .txt file say input.txt.
when i open my .csv file in notepad, i get multiple rows with each field separated by ';'.what are the content conversion parameters we have to define for .csv file and can we mention input.csv as the file name as a source file name.
Thanks
Deepak

Hi,
Use the following parameters for Sender file channel in case of reading .csv file
Recordset Structure.fieldSeparator -
Recordset Structure.endSeparator -
'nl'
Recordset Structure.fieldNames -
provide field names separated with ,
Regards
Seshagiri

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 issue for header record

Hi,
We have a very urgent question on an issue here with one of our XI objects.
This is an inbound interface from an external system into R/3 & BW. The inbound file has a header record (with about 8 fields) and detail records (about 900 fields per detail record). Data going into R/3 & BW don't have header records and everything goes in as detail records. One field from the header of this source file should be passed to the target structure at the detail level. Also, we are NOT using BPM.
Can someone help us how we could define the file content conversion parameters for File adapter.
Thanks in advance ......
Prashant

I'm so sorry, I wasn't subscribed to this thread and I didn't realize there were responses.
If you have a message type made up of a Header with 1 occurence and Detail with 1 to unbounded occurunces, you'd want to do the following in content conversion:
Document Name - your message type
Document Namespac - your message type namespace
Recordset Structure - Header,1,Detail,*
Recordset Structure - Ascending
Then you'll need to set some of the parameters, depending on the layout of your incoming file.
As for the problem of having hundreds of fields, I'm less sure about that.
Would it be possible to break your detail data type down into smaller data types. Each with fewer fields. You'd still have to maintain every field in content conversion, but at least they'd be in seperate parameters, instead of all 900 in one tiny box.
Here's a very rough example of what I mean:
If you have 900 fields, instead of making 1 data type of detail, you could make 9 data types, Detail1, Detail2, Detail3, Detail4, Detail5, Detail6, Detail7,Detail8, Detail 9, each with 100 fields in them (or more with even less fields).
Setting things up the file content conversion would be more complex in this scenario, so it might be a toss up if it's worth it to break it up this way or not if it meant configuring quite a few more parameters.
For example,
You'd have to declare your recordset structure like Header,1,Detail1,,Detail2,,Detail3,* etc, and you'd have to make sure to set the .endSeparator to '0' for all of the first 8 details, so it would recognize that they were all on one line.
I hope this helps a little bit.

Content Conversion for J2SE Adapter

Hi,
I have configured the J2SE Adapter properly,
Still content conversion is not taking place for my file and it is going unconverted to xi.
Following is the process.
I have the file as:
<b>0000665811     0111     500.00     20071217</b>
I Require the xml as
<b><ns0:Mt_Customer_Balance_Info xmlns:ns0="http://aoa.nestle.com/fi">
   <RECORDSET>
      <CUSC>0000665811</CUSC>
      <CRCA>0111</CRCA>
      <OBAL>500.00</OBAL>
      <DATE_REPORT>20071217</DATE_REPORT>
   </RECORDSET>
</ns0:Mt_Customer_Balance_Info></b>
I have configured as follows:
<b>mode=FILE2XMBWITHROWCONVERSION
xml.processFieldNames=fromConfiguration
xml.fieldSeparator='0x09'
xml.lastFieldsOptional=NO
xml.endSeparator=nl
xml.fieldNames=CUSC,CRCA,OBAL,DATE_REPORT
xml.structureTitle=RECORDSET
xml.documentName=FILE
xml.documentNamespace=http://aoa.nestle.com/fi</b>
Can you help me regarding this?

hi anupam,
u may refer this and see if u have done the configuration correctly.
http://help.sap.com/saphelp_nw04/helpdata/en/88/0f453cf1fcc85ee10000000a11402f/frameset.htm
regards,
latika.

File Content Conversion - Sender File Adapter - Record Delimeter ~

Similar Messages

Maybe you are looking for