Regarding content conversion parameters at receiver side

Hi
In the recevier side I have 3 nodes.
like HEADER,BODY,TRAILER.
file receiver communication channel I mentioned
RecordsetStructure* HEADER,BODY,TRAILER
parmeters I mentioned
HEADER.fieldFixedLengths
HEADER.endSeparator
BODY.fieldFixedLengths
BODY.endSeparator
TRAILER.fieldFixedLenghths
TRAILER.endSeparator.
In runtime workbench it is showing "Channel has not been correctly initialized and cannot process messages"
Please tell me is there any other parameters I have to mention.
regards
venkat.

Venkat,
Pls refrer the below:
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Sameer!

Similar Messages

Regarding content conversion parameters

Hi,
Can anyone send me a blog that completely explains in detail about each and every content conversion parameters?Need complete info about ALL those parameters
Thanks in Advance

Hi Rambabu,
Try to implement scenarios in these weblogs...it cover almost all type of scenarios
/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/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
Also go through this :
Converting File Content in the Sender Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/frameset.htm
Converting File Content in the Receiver Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Thanks,
Maheshwari.

File Adapter - Content conversion parameters at Receiver

Hi all,
I'm trying to translate a XML message to a text line file.
My XML message is this:
<?xml version="1.0" encoding="UTF-8"?>
<ns1:Proveedor_100011 xmlns:ns1="http://sap.com/xi/webservices/buyordint">
<config>
<directory>c:/tmp</directory>
<filename>dynamicFile3.txt</filename>
</config>
<root><string>Header;423423</string>
<lines>
<value>LINE;</value>
</lines>
</root>
</ns1:Proveedor_100011>
I only want to write to text file the "root" TAG content.
I try different "Content conversion parameters" in the integration builder (configuration)
For example:
RecordSet Structure: root
root.addHeaderLine 0
root.fieldSeparator ;
root.endSeparator ;
but the better result is all XML content.
Can someone tell me how to skip "Config" TAG and only write the "ROOT" one?
I'll apreciate any help.
Thanks in advance,
Diego.

Hi Sravya,
I've tried again without better luck.
I change the root element of my message from
Proveedor_100011 to Proveedor100011. (removed underscore)
I created the next message as in your weblog:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/webservices/buyordint" targetNamespace="http://sap.com/xi/webservices/buyordint">
<xsd:element name="Proveedor100011" type="Proveedor100011" />
<xsd:complexType name="Proveedor100011">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
54650790d48f11dab96c001438eb3b44
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="root">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
45f01f20d48e11dab854d06ec0a8004a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="head" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
45f01f21d48e11da8f1dd06ec0a8004a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="rows" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
45f01f22d48e11da894ad06ec0a8004a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
45f01f23d48e11dab889d06ec0a8004a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="filenode">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
45f01f24d48e11daab91d06ec0a8004a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="filename" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
45f01f25d48e11da8becd06ec0a8004a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="filepath" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
45f01f26d48e11dac56cd06ec0a8004a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<Proveedor100011>
<root>
<rows>
<value></value>
</rows>
</root>
<filenode>
<filename></filename>
<filepath></filepath>
</filenode>
</Proveedor100011>
I've tried to set "Recordset Structure" in file adapter configuration to "root,filenode" and to "Proveedor110001, filenode" but no output is writed
We are using XI version: SAPKB64015, which version did you use in your weblog?
Thanks and regards,
Diego.

File Content Conversion at the receiver side

Hello All,
I have a field which has to be truncated at 50th character. What content conversion parameters do I need to add ...?!?!?
Thanks,
Smita

Hi Smita,
As understood by your question you want a target field to be of 50 character,
either you can apply substring function in your mapping to that target node.
It would be much more clear if you mention hows your source file structure is it fixed length or delimiter separated, if it fixedlength file you can apply this parameter in Content conversion fixedLengthTooShortHandling with value Cut nad mention your required length.
Rewards point if it is helpful,
Thanks
Anu Singhal

File Content Conversion on the Receiving side

Is there a way in which if I want a Pipe Delimited File as a result, after the last field also I get a pipe with next record starting in the next line.

Hi,
For | (Pipe), use corresponding hex code as fieldSeparator i.e. 0x7C as fieldSeparator.
For FCC on receiver side refer -
[Simple FCC|http://www.riyaz.net/blog/index.php/2008/02/19/xipi-file-content-conversion-for-simple-structure/], [Complex FCC|http://www.riyaz.net/blog/index.php/2008/02/20/xipi-file-content-conversion-for-complex-structures/]
For separotor at the end of line you can try using a dummy field or use combination of pipe and newline i.e. '0x7C' and '0x0D' (stands for carriage return) or 'nl' as endSeparator
Edit: You might consider using 'nl' as beginSeparator parameter and 0x7C as endSeparator. This will do the trick. However, this would add a blank line in the beginning of the file.
Hope this helps.
Regards,
Riyaz
Edited by: Riyaz Sayyad on Aug 21, 2008 3:00 PM

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

Problem with end seperator in file content conversion parameters

Hi All
I have a proxy to file scenario, and i am writing the file using file content conversion.
In my message type, there can be multiple object records in a single data record, as shown here:
<Data_Record>
<Field1>111</Field1>
<Field2>222</Field2>
<Object_Record>
<Field3>333</Field3>
<Field4>444</Field4>
</Object_Record>
</Data_Record>
Recordset Structure: Data_Record, Object_Record
Content conversion parameters:
Data_Record.fieldseperator: ,
Data_Record.end_seperator: 'nl'
Object_Record.fieldseperator: ,
Object_Record.end_seperator: 'nl'
My requirement is, every data record should be followed by new line character and every object record should be followed by new line character:
111,222(new line character)
333,444(new line character)
But, my current output is:
111,222,333,444(new line character)
The problem is, as the data record ends only after object record, i am getting new line character only after object record. (technically, the end tag of data record occurs only after the end tag of object record).
Now, how can i get a new line character after data record and after object record?
Thanks
Chandra

Hi Sekhar,
We know the input which you are trying to use(in XML ).
Can you please tell us the output which you are expecting here after using ContentConversion at receiver side.
Regards,
Prakash.

Content Conversion in File Receiver Adapter

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

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

Give me list of content conversion parameters in sap xi

Hello experts,
give me the list of file content conversion parameters (like <node>.fieldSeparator)
with their explination.
Thanks inadvance.
Arjun

Hi,
Did you checked help.sap....
Sender Side:
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Receiver Side:
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
also check these blogs
File Receiver with Content Conversion By Jeya Kumar
The specified item was not found. By Shabarish Vijayakumar
NAB the TAB (File Adapter) By Sukumarar
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1) By Venkat Donela
Content conversion in Sender file adapter-- 2 new useful parameters By Sukumar Natrajan
Thanks
SaNv...

Content Conversion Parameters in Communication Channel

Hi,
I have a requiremnet to develop:
Scenario is SAP to Legacy System
Based on Mapping Sheet, I have defined Data types for both SAP and Legacy system. The Data structure is
There is a root node IS with occurance 1-n. In this node there is another node MS with occurance 1-n. This MS contains another node MI with occurance 1-n. MI contains MA node with occurence 1-n.Similarly MA contains MT node with occurance 1-n.
IS -> MS -> MI -> MA -> MT all with occurance 1-n.
Can anyone please help me in defining Content Conversion Parameters and Variable Substitution in Receiver Communication Channel.
Regards,
Deepak Raj

IS -> MS -> MI -> MA -> MT all with occurance 1-n
Your requirement seems to match with that mentioned in this blog:
/people/karthiknarayan.kesavan2/blog/2007/08/22/file-content-conversion-for-multi-hierarchical-structure
The blog does not mention the use of FCC...instead uses functionalities in mapping to get flat file....
Regards,
Abhishek.

What are the content conversion parameters for this structure

Hi All,
The below file is the text file. what are the content conversion parameters are required and what is the structure to create in the IR to convert into xml.
Schedule D - District/Port List (by District Code) [Produced13APR11]
District |    Port      |    Name
Code     |    Code      |
01       |              |    PORTLAND, ME
         |    0101      |    PORTLAND, ME
         |    0102      |    BANGOR, ME
         |    0103      |    EASTPORT, ME
         |    0104      |    JACKMAN, ME
         |    0105      |    VANCEBORO, ME
         |    0106      |    HOULTON, ME
         |    0107      |    FORT FAIRFIELD, ME
         |    0108      |    VAN BUREN, ME
         |    0109      |    MADAWASKA, ME
         |    0110      |    FORT KENT, ME
         |    0111      |    BATH, ME
         |    0112      |    BAR HARBOR, ME
         |    0115      |    CALAIS, ME
         |    0118      |    LIMESTONE, ME
         |    0121      |    ROCKLAND, ME
         |    0122      |    JONESPORT, ME
         |    0127      |    BRIDGEWATER, ME
         |    0131      |    PORTSMOUTH, NH
         |    0132      |    BELFAST, ME
         |    0152      |    SEARSPORT, ME
         |    0181      |    LEBANON AIRPORT
         |    0182      |    MANCHESTER USER FEE AIRPORT, NH
02       |              |    ST. ALBANS, VT
         |    0201      |    ST. ALBANS, VT
         |    0203      |    RICHFORD, VT
         |    0206      |    BEECHER FALLS, VT
         |    0207      |    BURLINGTON, VT
         |    0209      |    DERBY LINE, VT
         |    0211      |    NORTON, VT
         |    0212      |    HIGHGATE SPRINGS/ALBURG

since in this case you dont seem to have a key value to figure out what your header is, it is better to go for a two level mapping. i.e first read all the data - each line as an xml tag. and in the first mapping group it as required and then use it for your original mapping.
Regards,
Ninu

Content conversion parameters for fixed length file

Hi,
Hey i have a small doubt.My input is like this
99443 123213 232234 12312 127544 23423
Here i have four recorsetnames namely HEADER1,HEADER2,HEADER3,HEADER4,HEADER5,HEADER6 all the recordsets are of same size but the lengths of the fields in it vary so i specified the following parameters
HEADER1.fieldFixedLengths=1,3,1
HEADER1.fieldNames=value1,value2,value3
HEADER1.endseperator=" "
HEADER2.fieldFixedLengths=1,3,2
HEADER2.fieldNames=value1,value2,value3
HEADER2.endseperator=" "
MY OUPUT XML STRUCTURE SHOULD BE like this
<header1>
<value1>9<\value1>
<value2>944<\value2>
<value3>3<\value3>
<\header1>
<header2>
<value1>1<\value1>
<value2>232<\value2>
<value3>13<\value3>
<\header2>
Is the content conversion parameters i specified enough for that. I wanted to know how would it know the begin of the next recordset(ie the seperation between the two recordsets) .Please help me its vey urgent
Thanks in advance
Sriandh

Are header 1 fields always going to occur first , then header 2 and so on?
By default file adapters do not support Nested Strcutures and so if the sequence is going to be the same and all of these have an occurence of 1..1 then things will work.
But if there is going to be an occurnece of * then you will need to use KeyFields.
Regards
Bhavesh

Sender content conversion parameters

what wld be the sender content conversion parameters for the following structure?
MessageType        1-1
    Records            1-1
       File                1-unbounded
thanks

Hi,
If you have not come across:
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
would be of help.
Regards,
Manjusha.

CONTENT CONVERSION PARAMETERS IN XI

Hello guyz,
im following a certain procedure in XI ,it said that i need to enter the content conversion parameters as follows:
document name :
document namespace and others
and the name:                           value
contact.record.fieldseparator      ;
contact.record.endseparator      nl
contact.record.fieldnames         firstname,lastname
this is under integration directory, in business system in communication channel.
But i dont know where can I find it in that module.
Please help.
Thanks in advance
aVaDuDz

Hi,
file content conversion parameters change based on ur file data.
if its Fixed length then u have to use certain parameters and if its separated by some chatactor then u have u use certain parameters.
refer the below links to understand;
Converting File Content in a Sender Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
Converting File Content in the Receiver Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
Sender -
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Key value:
How to send a flat file with various field lengths and variable substructures to XI 3.0
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter) -
File Content Conversion for Unequal Number of Columns
Content Conversion ( The Key Field Problem )
The specified item was not found.
NAB the TAB (File Adapter)
NAB the TAB (File Adapter)
Receiver FCC no need of Endseparator
File Adapter (Receiver) - Are we "really" sure about the concepts?
Receiver-
File Receiver with Content Conversion
chirag

Content conversion parameters necessary for fixed length file

Hi,
I new to xi.The scenario is that i have to handle a fixed length file where the records repeat after every 80 characters.Can anyone help me as to how thw identify the start of every record based on length
thanks and regards ,
srinadh

Hi,
Hey i have a small doubt.My input is like this
99443 123213 232234 12312 127544 23423
Here i have four recorsetnames namely HEADER1,HEADER2,HEADER3,HEADER4,HEADER5,HEADER6 all the recordsets are of same size but the lengths of the fields in it vary so i specified the following parameters
HEADER1.fieldFixedLengths=1,3,1
HEADER1.fieldNames=value1,value2,value3
HEADER1.endseperator=" "
HEADER2.fieldFixedLengths=1,3,2
HEADER2.fieldNames=value1,value2,value3
HEADER2.endseperator=" "
MY OUPUT XML STRUCTURE SHOULD BE like this
<header1>
<value1>9<\value1>
<value2>944<\value2>
<value3>3<\value3>
<\header1>
<header2>
<value1>1<\value1>
<value2>232<\value2>
<value3>13<\value3>
<\header2>
Is the content conversion parameters i specified enough for that. I wanted to know how would it know the begin of the next recordset(ie the seperation between the two recordsets) .Please help me its vey urgent
Thanks in advance
Sriandh

Regarding content conversion parameters at receiver side

Similar Messages

Maybe you are looking for