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

Similar Messages

File Content Conversion - Key Field Value

Hi Experts,
I am using File to Idoc scenario for my mapping. In the receiver Communication channel, I am using File Content Conversion. My scenario is as follows :
I have a recordset with Header and Line items with Key Field Indicator as 'H' and 'L'. In some cases, the value for this Key Field is coming in as something other than 'H' and 'L'. I need to throw an exception when this Key Field is not 'H' or 'L'.
In the 'Content Conversion' tab, my attributes are as:
Header_Structure.keyFieldValue = 'H' and Line_Structure.keyFieldValue = 'L'. Is there any more attributes that I need to add ?
Please advise. Thanks a lot.
Regards,
Freddy.

>>multiple key field values in FCC configuration i.e Line_Structure.keyFieldValue = H or L
AFAIK it is not possible but lets wait for other experts to comment on this...
>>Can keyFieldInStructure (add, ignore) parameter help me in this case ?
No. this parameter is only used when you want to include key filed in ur XML structure(add) or not (ignore)...
Chk this:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm

File Content Conversion ( avoid fields in conversion)

Hi all
 An IDoc to File scenario , I am doing file content conversion in receiver File adapter.
my message type for file 2 HEADER each having its own substructure
Like 1header
 fieldA
 2header
 fieldC
 fieldD
I want the "1header and its 1 subelement not be converted in file content conversion" 
because its used for dynamic file name configuration, so i do'nt want it to be written on file.
Regards
Ashutosh.r

Rawat,
Yes I know you will get that error. That is the reason why I have told you to add another parameter fixedLengthTooShortHandling as Cut. So add one more parameter in your file receiver communicaion channel: Also I hope ASFD0101 is your strcuture not the field in the strcuture.
ASFD0101.fixedLengthTooShortHandling : Cut
Then I think it should work like a boom.
---Satish

File Content Conversion ignore fields

HI ,
I need to ignore some rows in the middle of the data in File content conversion for exaple
H1,Field1,Field2,Field3
A,GB07,MICHEL,1000
H2,Field3,Field4,Field5
B,GB08,andrew,2000
The above is the sample text file from the source , I need to parse in the below
RECORDset1
<Field1>A</Field1>
<Field2>MICHEL</Field2>
<Field3>100</Field4>
RecrodSet2
<Field4>A</Field4>
<Field5>andrew</Field5>
<Field6>200</Field6>
I need to omit or ignore the H1 and H2 rows from the File Content conversion.,
Please guide me how to achive this using File Content conversion

Hi Krishna,
In case if H1 and H2 is your record type or line type then to ignore line for this type... just do not handle "keyFieldValue" in the content conversion for H1 and H2 record type.
Thanks,
Binod

Flat file content conversion repeating fields

Hello,
   I have a flat file where the first three fields are fixed; the rest of the file line is made up of 1 .. n analysis characteristic results. The name of the field (Result) is always the same, but I never know how many results I will have on one line. Could anyone tell me how I might define this in content conversion ? Thanks in advance.
Peter DOUGHERTY.

Sorry,
   Of course ... here it is
10059514     22/09/08 8:29:02     20,2     0     0     0     0,30     0     133     0     0     0     0     0     0     0     0     0     0     0
The first field is the Id of the sample
Second field Date
Third field Time
The 4th ... 21st fields a (varying) number of results (here there are 18, but there could be any number from 1 upwards)
Hope it is clearer
Thanks
Peter

File Content Conversion some fields are missing

Hello Friends,
I am trying to convert a fixed length flat file to XML.
Here are my parameters
CompanyCodeRecord.fieldNames = field1,field2,....field50
CompanyCodeRecord.fieldFixedLengths = 1,4,15,20...,50 (for all 50 fields)
CompanyCodeRecord.processFieldNames = fromConfiguration
CompanyCodeRecord.lastFieldsOptional = YES
CompanyCodeRecord.endSeparator = nl
If I do not use lastFieldsOptional=YES then the adapter is throwing an exception Error: Conversion of complete file content to XML format failed around position 0 with java.lang.Exception: ERROR converting document line no. 1 according to structure 'CompanyCodeRecord':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this
last retry interval started 19:31:08 2005-07-11
If I use lastFieldsOptional=YES then the message does not contain last 8 columns (That means each record is containing only 42 columns).
Please help.
Thanks
SKM

Hi SKM
Go through this blog on sending fixed length flat file
/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
and
>>lastFieldsOptional=YES then the message does not contain last 8 columns
lastFieldOptioanl parameter specifies whether the last fields can be omitted (YES) or not (NO) in a CSV structure. If you do not make a specification, the default value is NO.
So i think u should use NO in this parameter.
Hope it helps.
Regards
Arpit Seth

File Content Conversion(SenderFileadapter) fields parameters

Hi all
 I am doing aFile to File scenario,
Using content Conversion at SENDER FILE adapter
my source message type is as :
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Cnet_Source xmlns:ns0="http://abc.com/Cnet">
 <HeaderPayment>
 <First_Payt_Doc/>
 <Beneficiary_email_id/>
 </HeaderPayment>
 <AdviceFormat>
 <Client_Code/>
 <Payment_Document_No/>
 <Document_Date/>
 </AdviceFormat>
 <LineItem>
 <Title1/>
 <Title3/>
 </LineItem>
 <FILENAME>
 <FNAME/>
 </FILENAME>
</ns0:MT_Cnet_Source>
it has 3 structures :HeaderPayment(0,1),AdviceFormat(0,1),LineItem(0,unbounded)
in Recordsetstructure i gave= HeaderPayment,1,AdviceFormat,1,LineItem,1
in FCC parameters i used
HeaderPayment.fieldname... =First_Payt_Doc,Beneficiary_email_id
HeaderPayment.fieldseperator ='nl'
HeaderPayment.endseperator ='nl'
ignorerecordset = true
similarly for rest 2 structure also
my source text file is type :
we0023
[email protected]
xyc
acd
21/05/2007
10034
acccd
payment
i tried alot of options,refering sdn..still on reading the file value are not coming in the designated fields...
Thanks &Regards,
ajay

You are Right i correct it but i sxmb_moni
i get as <HeaderPayment>
<First_Payt_Doc/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
</AdviceFormat>
<LineItem>
<Title1/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
<HeaderPayment>
<First_Payt_Doc/>
<Beneficiary_email_id/>
</HeaderPayment>
<AdviceFormat>
<Client_Code/>
<Payment_Document_No/>
<Document_Date/>
</AdviceFormat>
<LineItem>
<Title1/>
<Title3/>
</LineItem>
<FILENAME>
<FNAME/>
</FILENAME>
the header payment should not repeat....
Regards
Ajay

File content conversion: Target Field is optional

I am using FCC in receiver file adapter.
My file is getting generated.
In target structure one field is optional and hence target xml element doesnt have value. hence that field is not there in txt file. with this what happens next subsequent field gets shifted to my optional field place and then i get error field length is not correct.
I want to put 2 spaces if that optional field length is 2 char and then there should be field separator(space) and the subsequent column.
I am already giving fixedfieldlegnth of all the fields.
Pl can anyone suggest how to do this.
thanks,
sharada

Hi Sharada,
Do your normal mapping to the target field that is optional.
Use a If function before mapping the field.
Check if the node is created in usual mapping, else map a constant with 2 spaces.
DO something like this:
Mapping ---------------->
                           equalsS ----> if
constant(empty Value)--->
                  constant(2 spaces)--> then -> tgtField
                   Mapping -----------> else
regards,
P.Venkat

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

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,

Skip field in file content conversion (file adapter)

hy guys,
I have a log file and want to convert it into xml. that works fine.
the problem is: can I skip some fields that I do not need in the xml with file content conversion
the fields I want to skip are the same in every record of the log file.
thanks.

Ralf,
You can only ignore lines in the begiining of the file using Document Offset option.
If you have the unwanted field in the end of the record and you are in SPS12 (PI 7.0), you can use the option additionalLasstFields in FCC parameters. have a look into the blog /people/sukumar.natarajan/blog/2007/06/12/content-conversion-in-sender-file-adapter--2-new-useful-parameters
Easier, is to ignore those fields in mapping.
Also, you can try to remove those fields using a shell script which can be called from the File adapter.
Regards,
Jai Shankar

File Content Conversion - Error in keyfield Value

Hello experts,
I am doing file content conversion for a file to file scenario. The input file is a csv file which is converted to xml using the file content conversion. The key field of input file is used for implementing conversion.
While testing the FCC, I noticed that if the keyfield value is wrong for a record in the file, the record is ignored altogether without throwing any errors or warnings. Is there any way to notify if any records have been ignored as a result of incorrect keyfield value??
Thanks in advance!
RR

There seems to be NO way to handle it in FCC.
File Content Conversion - Key Field Value
u can think of work arounds by handling it in mapping....
-santosh.

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

Duplicate field names in File content conversion

Hi,
I need some details for csv to xml file conversion.I have configured the file content conversion adapter for these conversions.In source CSV file we will receive below details in single line.
0020000001000 0020000002000 0020000003000 0020000004000
Now i can successfully generate
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_GLMast_out xmlns:ns="http://sap.com/PI/GLMast">
- <GLMasterData>
- <GLMAST>
<Customer1>0020000201000</Customer1>
<Customer2>0020000200000</Customer2>
<Customer3>0020000199000</Customer3>
<Customer4>0020000198000</Customer4>
</GLMAST>
</GLMasterData>
</ns:MT_GLMast_out>
with following parameters
GLMAST.fieldSeparator ,
GLMAST.fieldNames Customer1,Customer2,Customer3,Customer4
GLMAST.endSeparator 'nl'
Now the issue is customer wants to send 3000 customer number in single file.How to maintain the parameter to duplicate filednames just customer instead of customer1,customer2,customer3 etc...
<Customer>0020000201000</Customer>
<Customer>0020000200000</Customer>
<Customer>0020000199000</Customer>
<Customer>0020000198000</Customer>
This can be done if customer sends file like one customer number in one line.please help me how to process multiple customer number in single file separated with comma.
Thanks,
Vijay

For this what you can do is, create the source and target data types as shown below
Source Data Type
<DTO_Customer>
<Records> 0..unbounded
 <Customers> </Customers>0..1
</Records>
</DTO_Customer>
Target Data Type
<DTI_Customer>
<Records> 0..1
 <Customer> </Customer> 0..unbounded
</Records>
</DTI_Customer>
Now since your data will come in a single string therefore do the FCC in sender channel as shown below
Records.fieldNames = Customers
Records.fieldSeparator = 'nl'
ignoreRecordsetName = true
So by doing this you will get the data into XI mapping in as single string. Now you need to write an UDF which will split this string into individual customers based on your delimiter in the string.
Now map the output of this UDF to <Customer> field.
You may need to do some other small fixes accordingly.
I hope this will solve your problem.

File Content Conversion in EDI to File without Seeburger

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 

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 without field separator

Similar Messages

Maybe you are looking for