Content Conversion without a fieldSeparator

Good day, I would like to know is there a way to use file content conversion in the receiver adapter but not specifying a delimiter? I have to convert an idoc to a flatfile. The flatfile should have no delimiters in. Everything works fine but only if I have a parameter .fieldSeparator and the value as space of somthing. Is there some way to bypass this?

Hi,
Just check out the below thread for this :-
File Receiver with Content Conversion
For more on FCC please refer these:-
http://help.sap.com/saphelp_nw2004s/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
The specified item was not found. - FCC
File Content Conversion for Unequal Number of Columns - FCC
Content Conversion (Pattern/Random content in input file) - FCC
XI in the role of a FTP - FCC

Similar Messages

File content conversion without field separator

Hi experts,
in my scenario I'm sending a txt file to an external receiver.
Each field of the file must be separated from the others with differents field separators according with the requirement of the receiver, for example:
field1;field2:field3, field4; ecc....
For this reason I've created in the source message many "FieldSeparator" fields. These fields will be populated by ABAP program.
I thought that it was possible to omit parameter fieldSeparator in content conversion, but testing the interface I receive an error because fieldSeparator is missing.
Is possible to omit fieldSeparator or to specify a fieldSeparator null?
The fields in the target file must be of variable lenght, so I cannot use FieldFixedLenght.
The only solution I found is to create in the target message structure a single string with each field concatenated, is the only possible solution?
Thanks
Fabio Boni
Edited by: Fabio Boni on Oct 21, 2010 5:47 PM

Sorry...posting error earlier..
The seperator can be concatenated at the end of each field in mapping.So seperator will be part of field value.
But with receiver FCC, you need to either mentione fieldfixedlenght or fieldseperator.Please check if space is going to to work for you as separator.
Edited by: nagarjuna _s on Oct 21, 2010 6:36 PM

Content conversion - endSeparator and fieldSeparator with unusual separators

Hi Experts.
I have a problem with the content conversion of a file due to delimiters.
The problem is that the field separators and end line separators are:
fieldSeparator ¿ (ASCII hexadecimal code BF).
endSeparator ¨ (ASCII hexadecimal code A8).
It seems like if the channel is not recognizing these characters.
1. If I use the character directly in content conversion:
    I get all the file data in the first field of my message:
    <Field1>xxxxxx¿sssssss¨xxxxxx¿sssssss¨<Field1>
2. If use ASCII Hexadecimal code in content conversion
    '0xBF'
    '0xA8'
     I get this error in communication channel:
    Conversion initialization failed: java.lang.Exception: java.lang.NumberFormatException: Value out of range. Value: "BF" Radix: 16
Any idea about how to solve this? Is that even possible to handle this kind of files with this unusual separators?
Thanks a lot in advance.
Christian.

Hi Jens.
Thank you so much for the information.
The thing is that I'm not working with module SimplePlain2XML and I'm doing the conversion directly from content conversion. Do you think that could be the same problem as using SimplePlain2XML module?
Btw, I'm working in 7.31.11.0 environment.
Many thanks.
Christian.

Content Conversion without key field value

Hi all,
I want to do a content conversion which includes a record structure Header,1,Detail,*
I dont have any key field value in the header nor in the detail. Can this be achived using FCC or should i go for Java.
Rgds
Aditya

Hi Aditya,
I think if u having multiple records then one shud hav key fields,
pls check 4th point in this guide
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/troubleshooting%2bthe%2bfile%2badapter
Also check this discussion::File Content Conversion(SenderFileadapter) fields parameters
Thanks,

Content conversion without delimiter and key fields

I am pretty new to XI, so it has been very challenging till now... (and someway I want to keep it that way) But this problem has kept me awake a couple of nights, so I will unleash it to the XI experts at SDN!
I have to read a legacy file (customers are ordering stuff) with the following content into XI. I finally found out you can use file content conversion to do the job, but I have only seen scenarios where people can use delimiters or key fields so far. I suppose XI can do this job as good as the others, but the question is how it has to be done! :-s
Do I have to use key fields? Or can I simply state there will be 1 header line, X order lines, 1 EOF line?
Sample content:
100207.310551
0107299700001
0108658400001
0109575600001
1200276500001
0109745600001
9999999999999
Header line containing the customer (100207) and the ticket number (300551) separated by a dot.
In this case 5 order lines containing material (8 digits, ex 01072997) and quantity (5 digits, ex 00001)
Line containing only 9's to indicate the end of the file has been reached.
Thanks in advance!
Sven

Hi Sven,
This FCC might help u..If your structure like ...
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:bestin xmlns:ns0="http://test.com">
<recordset>
<header>
<client>100207</client>
<ticket>310551</ticket>
</header>
<item>
<material>01072997</material>
<quantity>00001</quantity>
</item>
<item>
<material>01086584</material>
<quantity>00001</quantity>
</item>
<item>
<material>01095756</material>
<quantity>00001</quantity>
</item>
<item>
<material>12002765</material>
<quantity>00001</quantity>
</item>
<item>
<material>01097456</material>
<quantity>00001</quantity>
</item>
</recordset>
</ns0:bestin>
then
RecordStructure----header,item
otherwise
RecordStructure----client,ticket,item
client.fieldFixedLengths----give length of client
ticket.fieldFixedLengths----
item.fieldFixedLengths----
client.fixedLengthTooShortHandling--Cut
ticket........same
item.....
client.addHeaderLine--0
ticket........same
item.....
recordsetStructureOrder---var
Cheers!
Samarjit
Message was edited by:
Samarjit Dey

File content conversion without key field

Hi,
i have a input file with the following format:
posvalue1;posvalue2;posvalue3;posvalue4
posvalue1;posvalue2;posvalue3;posvalue4
posvalue1;posvalue2;posvalue3;posvalue4
posvalue1;posvalue2;posvalue3;posvalue4
posvalue1;posvalue2;posvalue3;posvalue4
footervalue1;footervalue2;footervalue3
footervalue1;footervalue2;footervalue3
i just need the information from pos lines and the footer is not needed. the only indicators are:
the empty line between
the number of fields
maybe i could use the keyfieldvalue:
in posvalue2 i have only numbers (diffrent) in footervalue2 i have only chars (diffrent)
has anyone an idee?
regards
J.

Hi
yes you have to use the key field value as the posvalue1.
if you do not want the footer informatuion in the target side then inthe grahical mapping do not map footer fields with the target structure.
to convert the text file into XML file you can use the following parameters
RECORD.fieldSeparator :;
RECORD.fieldNames :KEY,FNAME,LNAME,AGE
RECORD.keyFieldValue :1
DETAIL.fieldSeparatr :;
DETAIL.fieldNames :KEY,SALARY,EMPID
DETAIL.fieldNames :2
Note:these parameters are accoding to the structure given below.
suppose you have a structure like as below
data (0..unbounded)
record (0..unbounded)
key (1..1)
fname (1..1)
lname (1..1)
age (1..1)
detail (0..unbounded)
key (1..1)
salary (1..1)
empid (1..1)
and the input file will look like as below
1,aaa,bbb,23
2,12000,10838
1,ccc,ddd,23
2,13000,10830
if you still face the problem please reply me back
Thanks
Rinku

Problem with Sender Adapter File Content Conversion

Hi all!
I have a question about file content conversion in sender file adapter.
I have file like:
{field1
field2
field3
field4
$
{field5
field6
field7
field8
And i need to get file like:
<dealings>
<deal>
<field1>{field1</field1>
<field2>field2</field2>
<field3>field3</field3>
<field4>field4</field4>
<field5>-}*</field5>
</deal>
<deal>
<field1>{field5</field1>
<field2>field6</field2>
<field3>field7</field3>
<field4>field8</field4>
<field5>-}*</field5>
</deal>
</dealings>
I put content conversion parameters:
deal.fieldSeparator = $
deal.fieldNames = field1,field2,field3,field4,field5
And i get a file like:
<ns:mt_swift_file>
<dealings>
<deal>
<field1>{field1</field1>
</deal>
<deal>
<field1>field2</field1>
</deal>
<deal>
<field1>field3</field1>
</deal>
<deal>
<field1>field4</field1>
</deal>
<deal>
<field1>-}*</field1>
</deal>
<deal>
<field1/>
</deal>
<deal>
<field1>{field5</field1>
</deal>
<deal>
<field1>field6</field1>
</deal>
<deal>
<field1>field7</field1>
</deal>
<deal>
<field1>field8</field1>
</deal>
<deal>
<field1>-}*</field1>
</deal>
</dealings>
</ns:mt_swift_file>
What i do wrong?
As i understand, XI put string to a separate tag after symbol 'nl', but how can i get structure without unnecessary tags?

Hi,
Check some links for FCC
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
File Receiver with Content Conversion
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
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.
File Receiver with Content Conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani

Complex content conversion File sender

RecordSet
    >Header   1..1
         hfield1 1..1
         hfield2 1..1
    >/Header
    >Detail      1..n
         Dfield1 1..1
         Dfield2 1..1
         > SubDetail 1..1
                 SDfield3 1..n
         > /SubDetail
     >/Detail
/RecordSet
My CSV File would be like.
1hfield1,hfield2
2Dfield1,Dfield2
3SDfield3
3SDfield3
2Dfield1,Dfield2
3SDfield3
3SDfield3
2Dfield1,Dfield2
3SDfield3
3SDfield3
I have Used following Conversion Parameter. Please check.
Recordset Structure :         Header,1,Detail,,SubDetail,
Keyfieldname :    key
Keyfieldtype: string
Header.fieldSeparator   ,
Header.endSeparator   u2018nlu2019
Header.fieldNames hfield1,hfield2
Header.keyFieldValue 1
Header.keyFieldInStructure ignore
Detail.fieldSeparator   ,
Detail.endSeparator   u2018nlu2019
Detail.fieldNames Dfield1,Dfield2,SubDetail
Detail.keyFieldValue 2
Detail.keyFieldInStructure ignore
SubDetail.fieldSeparator   ,
SubDetail.endSeparator   u2018nlu2019
SubDetail.fieldNames SDfield3
SubDetail.keyFieldValue 3
SubDetail.keyFieldInStructure ignore
Suggest , where I am wrong. And what is missing ?????????????????
So . I am not able to convert this SubDetail by using content conversion.
Upto Level Header and Detail , it is coming in xml file . but not for SUBDETAIL and SDfield3.
Please check above config and suggest.
Is there any way to perform such content conversion without using KEVALUE 1, 2, 3 in CC parameters,

Thanks Hareenkumar for reply ..
The Blog which you have Given , in that all the substructure is in same hierarchy , But in my case subDetail in Under Detail .
What Can i do for such structure ???.
And Thank You for pointing me on using key under fieldNames .But It was my mistake . I was forgot to write "key" under fieldNames , as i am already using Using it.

Problem with file content conversion in receiver file adapter

Hi All
I have a problem with file content conversion in receiver file adapter.
This is my recordset structure: Header_Record,1,Claim_Record,*,Check_Rec,1
These are the content conversion parameters:
Header_Record.fieldSeparator = ,
Header_Record.endSeparator = 'nl'
Claim_Record.fieldSeparator = ,
Claim_Record.endSeparator = 'nl'
Check_Rec.fieldSeparator = ,
Check_Rec.endSeparator = 'nl'
In SXMB_MONI, i can see that the data is correctly extracted from proxy, and correctly mapped to receiver message, and i see a checkered flag (success).
But, Adapter status is RED with the following error message:
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
In communication channel monitoring, i get the following error message:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages
What is going wrong here? Can anyone please tell me?
Thanks
Chandra

Posted in Incorrect forum.
Posted again in Process Integration forum

Content conversion problem

Hi gurus
I sem to have a really silly problem
I'm only getting the FIRST field on file content conversion and no new line
here's a part of the XML file from the payload manifest
<?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>100853</CUSTOMERID>
<COMPANY>Bram Van Tuyl Coldstore</COMPANY>
<SHORT_NAME>VAN TUYL</SHORT_NAME>
<SALES_REGION>EUROP</SALES_REGION>
</item>
</IP_CUSTOMER_HEADER>
</rfc:Z_XI_005_RFC>
I've defined the following parameters in the content conversion
Recordset sructure   item
content conversion parameters
item.fieldSeparator       ;   (a semi colon)
item.endSeparator      'nl'
if I look in my file all i get is
100853
where's the rest of the data ????
When I don't use content conversion   xml file is generated correctly.
Any ideas
I am at 100% loss to see what's wrong here as this should be an EASY automatic conversion.
(the input structure is all character)..
Max pts to anyone who solves this
Cheers
jimbo

the file is identical
payload from inbound message
for example
<rfc:Z_XI_005_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <IP_CUSTOMER_HEADER>
- <item>
<CUSTOMERID>1000001</CUSTOMERID>
<COMPANY>One-time ship-to</COMPANY>
<SHORT_NAME>ONE-TIME</SHORT_NAME>
<STREET />
<STREET2 /> .......
Paylioad under Receiver Grouping
<rfc:Z_XI_005_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <IP_CUSTOMER_HEADER>
- <item>
<CUSTOMERID>1000001</CUSTOMERID>
<COMPANY>One-time ship-to</COMPANY>
<SHORT_NAME>ONE-TIME</SHORT_NAME>
<STREET />
<STREET2 />
etc
text file 100001;1000001........ etc
There's no Payload that I can see under the response (checkered flag) where it says processed successfully.
cheers
jimbo

'nl' Not Working for fieldSeparator in File Content Conversion

I have a receiver communication channel where I want to create a file with each field being a new line. The xml (Message Protocol: File) output looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:complus_receiver_messageType xmlns:ns0="http://graybar.com/test/complus_rec
eiver"><cp><myrequest>AAFADFASFADFADSFDASFADFAAA</myrequest><myheader>DELADV</myheader></cp></ns0:complus_receiver_messageType>
When I turn on Message Protocol of File Content Conversion, and follow the SAP documentation on the parameters, the 'nl' is getting sent literally.
- I have Recordset Structure of: cp
- I have content conversion parameters of:
cp.fieldSeparator 'nl'
cp.fieldNames myrequest,myheader
cp.addHeaderLine 0
My file output looks like this:
AAFADFASFADFADSFDASFADFAAA'nl'DELADV0001
Note that the 'nl' is not processing as a new line. Ideas?

Hi,
Receiver FileContent conversion params dosen't have <b>fieldNames</b>
cp.fieldNames myrequest,myheader
so why don't u remove this and try once again...
Recordset Structure of: cp
cp.addHeaderLine 0
cp.fieldSeparator 'nl'
Hope this weblog helps you...
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
Cheers,
Siva Maranani.

Issue in content conversion .fieldSeparator

Hello !!
I am trying to post a file with * delimiter and for that I am using the below content conversion :
record.fieldNames -
f1,f2,f3,f4,f5
record.fieldSeparator -
all the fields under record are optional. When the sending system is sending the data as
<record>
<f1> 111</f1>
<f5> 555 </f5>
</record>
The file is created as follows :
111*555
I want that file should be created as
111*****555
"***" for the missing f2,f3,f4 fields , so that the receiving system wouldnt take 555 as f2 field value.
Thanks
Peeru

Hi Peeru,
Not sure how are you converting this data but to get this, you need to have empty tags.
<record>
<f1> 111</f1>
</f2>
</f3>
</f4>
<f5> 555 </f5>
</record>
If you are using any XSD or WSDL to do this mapping, that should take care of this
Thanks
-Kulwant
Also in mapping you can specify to create EMPTY element if no input is found. That way this is easy
Edited by: Kulwant Bhatia on Nov 6, 2008 5:20 PM

Queue to queue without content conversion

Hi All,
I have message in MQ queue and want send as it is to some target MQ.
I don't have any mapping requirements.
Its a text message in this case do i need to do content conversion ? or can i pass directly as a string?
we have solution for this if it is a file and placed in ftp, but i want to know how MQ behaves?
Thanks,
srini.

Hi,
As you do not need any mapping, you need not perfrom content conversion etc., infact you do not need even IR content
Just follow this bog , even though this is for file to file,it holds for other adapters as well,
/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
Regards
Bhavesh

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

File content conversion in File-to-RFC without BPM

Hi,
I am using FCC for file to RFc scenario.
My input record is in the following format:
Header record
data rec1
data rec2
Trailer record..
The parameters are used in File content conversion:
Recordset Name : Header,item
Recordset Structure: Header,1,item,*
key field name : data1
and in additional parameters:
Header.fieldNames            HI,GenDate,Ftype,Fname,Fdate
Header.keyFieldValue       Fname
Header.fieldFixedLengths 1,8,1,50,8
Header.endSeparator        nl
item.endSeparator             nl
item.fieldNames                  DATA1,DATA2,DATA3,DATA4
item.keyFieldValue             item
item.fieldFixedLengths       231,240,241,120
item.lastFieldsOptional       YES
Can anyone check whether any parameters are left, b'cos the file is not being read with this settings. and in the C.C its just showing file processing successfully but not able to see the actual file.

Hi,
I assume you have header, item and trailer structure in source file.
Source Data Type will be as follows.
RecordSet
--> Header
      --> KeyField(Value OH)
      --> H1
      --> H2
--> Item
      --> KeyField (Value OL)
      --> I1
      --> I2
-->Trailer
      --> KeyField (Value OT)
      --> T1
      --> T2
Where Item Strucutre can come multiple times.
Please use following settings.
Recordset name: RecordSet
RecordSet Structure: Header,1,Item,*,Trailer,1
Key Field Name: KeyField
Header.fieldNames: KeyField,H1,H2
Header.fieldFixedLengths: 2,3,4
Header.processFieldNames: fromConfiguration
Header.keyFieldValue: OH
Header.LastFieldsOptional: YES
Item.fieldNames: KeyField,I1,I2
Item.fieldFixedLengths: 2,5,6
Item.processFieldNames: fromConfiguration
Item.keyFieldValue: OL
Item.LastFieldsOptional: YES
Trailer.fieldNames: KeyField,T1,T2
Trailer.fieldFixedLengths: 2,8,9
Trailer.processFieldNames: fromConfiguration
Trailer.keyFieldValue: OT
Trailer.LastFieldsOptional: YES
Regards,
Gouri

Content Conversion without a fieldSeparator

Similar Messages

Maybe you are looking for