Problem using file content conversion

I want to generate a input message with no recordset and root element
It just contains one element like below:
<line>AI0 AXXX-001 20089830 120</line>
<line>AI0 AXXX-002 20089830 120</line>
What properties I need to setup in file content conversion to get this format message?
The data inside <line> comes from a txt flat file.
Please help
Thanks
Gopal

Hi,
Root element can be ignore by using FCC property Recordset Name i.e ignoreRecordsetName: true
If you set the parameter to true, the <Recordset> element is not inserted.
Recordset Name defines the root node under which rest of the XML will be created. If not required ignore.
As Recordset Structure is a mandatory parameters, So I'm not sure how you ignore it.
Abid!

Similar Messages

Trailing spaces problem during file content conversion

I have developed a proxy to file scenario.And am using file content conversion for creating the file. The file is to be a fixed length file.
File Structure
<Header>
<Item>
<Item Trailer>
<File Trailer>
Each tab in the file has the last character mapped to spaces.
Eg: Header00000001 2006011700000000020060<blank space>
Item00000001 2006011700000000020060<blank space>
The problem is that during file content conversion. XI does not preserve trailing spaces at the end of the line i.e.if a particular line in the file ends with space. It terminates the line at the last non-space character (in this case at 060).
However we are required to maintain these trailing spaces at the end of each line.
I have tried preserve white space in data type that does not work.
I know that xslt mapping may solve the problem but I am looking for a workaround with my current graphical mapping.
Looking for suggestions !!
Thanks,
Rashida

Hi,
I have the problem quite opposite to this where we are getting the trailing spaces at end of each record which should not come.
File structure is
<Record>
- <Data>
<Content>11/09/2007@210@ZACSL007@GBB-56436@PS01@29@1044@19@646@0</Content>
</Data>
</Record>
............. n records
<Header>
<File_Name>UK01</File_Name>
</Header>
Record structure in communication channel used is
Header, Data
Data.fieldFixedLengths 1024
Data.addHeaderLine 0
Header.addHeaderLine 0
Header.fieldFixedLengths 0
Header.fixedLengthTooShortHandling Cut
Data.fixedLengthTooShortHandling Cut
Header.endSeparator '0'
Actually if the length of record is less than 1024, rest of the length is being filled with spaces which should not occur.
Many advanced thanks.
Jitender

Problems in File Content Conversion

Hello,
 I am trying to convert a text file to an XML using File Content Conversion in XI 3.0.
 The incoming text file gets picked up but no message is sent and hence no message is received in the monitor.I get the following log-
Success Channel FILE_SENDER_XML_1: Entire file content converted to XML format
Warning Channel FILE_SENDER_XML_1: Empty document found. Proceed without sending message
Success File "C:\xi_public\i033066\dme_in.txt" deleted after processing
Can somebody help me on this
Thanks
Sandeep

Hello,
 I am not sure of why the empty Payload is created.
I have the following TXT file -
LINE 1 01 22 Sandeep ASKDJKLASD HDFC Bank 12342 asdasd 123569
LINE 2 02 22 Sagar 23123 ICICI 4234 ASDASD 254636 12304 ASDAsdqwe
LIME 3 03 22 1 12304
Ignore 'Lines' above.They are not part of the file.
I have given the following parameters -
Document Name - SampleMessageType
Document Namespace - http://sandeep/xi/bpm_example
Recordset Name - Header,Item,Trailer
Recordset Namespace - http://sandeep/xi/bpm_example
Record Structure - Header,,Item,,Trailer,*
Recordset Sequence - Ascending
Key Field Name - Record Type
Key Field Type - String(Case Sensitive)
Header.fieldFixedLengths 3,4,15,20,15,15,20,10
Header.fieldNames RecordType,RecordLength,CompanyName,CompanyAddress,BankName,BankCode,BankAddress,AccountNumber
Header.processFieldNames fromConfiguration
Header.keyFieldValue 01
Header.lastFieldsOptional YES
Item.fieldFixedLengths 3,4,15,20,15,15,15,10,6,10
Item.fieldNames RecordType,RecordLength,BeneficiaryName,BeneficiaryAddress,BankName,BankCode,BankAddress,AccountNumber,Amount,NoteToPayee
Item.processFieldNames fromConfiguration
Item.keyFieldValue 02
Item.lastFieldsOptional YES
Trailer.fieldFixedLengths 3,4,6,6
Trailer.fieldNames RecordType,RecordLength,TotalRecords,TotalAmount
Trailer.processFieldNames fromConfiguration
Trailer.keyFieldValue 03
Trailer.lastFieldsOptional YES
If I don't give these parameters then channel will give me errors.I don't know what other parameter to give to create a file.
I had tried the same thing with the following and it worked
Document Name - SampleMessageType
Document Namespace - http://sandeep/xi/bpm_example
Record Structure - Substr,*
Recordset Sequence - Ascending
Key Field Name - Record Type
Key Field Type - String(Case Sensitive)
Substr.fieldFixedLengths 3,4,15,20,15,15,20,10,3,4,15,20,15,15,15,10,6,10,3,4,6,6
Substr.fieldNames RecordType,RecordLength,CompanyName,CompanyAddress,BankName,BankCode,BankAddress,AccountNumber,RecordType,RecordLength,BeneficiaryName,BeneficiaryAddress,BankName,BankCode,BankAddress,AccountNumber,Amount,NoteToPayee,RecordType,RecordLength,TotalRecords,TotalAmount
Substr.processFieldNames fromConfiguration
Substr.keyFieldValue 01
Substr.lastFieldsOptional YES
But the problem here is my mapping has the Header,Item and Trailer as the structure names but he XML created here will be like
<?xml version="1.0" encoding="utf-8" ?>
- <ns:SampleMessageType xmlns:ns="http://sandeep/xi/bpm_example">
- <Recordset>
- <Substr>
<RecordType>21</RecordType>
<RecordLength>22</RecordLength>
<CompanyName>Sandeep</CompanyName>
<CompanyAddress>ASKDJKLASD</CompanyAddress>
<BankName>HDFC Bank</BankName>
<BankCode>12342</BankCode>
<BankAddress>asdasd</BankAddress>
<AccountNumber>123569</AccountNumber>
</Substr>
- <Substr>
<RecordType>02</RecordType>
<RecordLength>22</RecordLength>
<CompanyName>Sagar</CompanyName>
<CompanyAddress>23123</CompanyAddress>
<BankName>ICICI</BankName>
<BankCode>4234</BankCode>
<BankAddress>ASDASD 25463</BankAddress>
<AccountNumber>6 12304</AccountNumber>
<RecordType>AS</RecordType>
<RecordLength>DAsd</RecordLength>
</Substr>
- <Substr>
<RecordType>03</RecordType>
<RecordLength>22 1</RecordLength>
</Substr>
</Recordset>
</ns:SampleMessageType>
In this case my mapping fails
Thanks,
Sandeep

XML to flat file conversion using file content conversion in reciever CC

Hi,
Iam working on Idoc to File scenario.
Iam having a problem in the communication channel of reciever.
Iam using File content conversion in Reciever Adapter.
My xml format is asfollows:--
- <Header>
<FILLER1>KTP</FILLER1>
<YEAR_IDOC>YEAR 2006</YEAR_IDOC>
<FILLER2>FIRSTWEEKNUMBER</FILLER2>
<WEEK_IDOC>51</WEEK_IDOC>
<FILLER3>NUMBER WEEKS 26</FILLER3>
<PLANT_CODE>FACTORYM019</PLANT_CODE>
</Header>
- <Record>
<First_material>731000</First_material>
<First_quantity>0000.0</First_quantity>
<First_quantity>0001.9</First_quantity>
<First_quantity>0000.0</First_quantity>
<First_quantity>0000.0</First_quantity>
<First_quantity>0020.0</First_quantity>
<First_quantity>0000.0</First_quantity>
<First_quantity>0000.0</First_quantity>
<First_quantity>0000.0</First_quantity>
<First_quantity>0018.0</First_quantity>
<First_quantity>0000.0</First_quantity>
<Second_material />
<Seond_quantity>000000</Seond_quantity>
<Second_quantity>0011.0</Second_quantity>
<Seond_quantity>000000</Seond_quantity>
<Seond_quantity>000000</Seond_quantity>
<Seond_quantity>000000</Seond_quantity>
<Seond_quantity>000000</Seond_quantity>
<Second_quantity>0049.0</Second_quantity>
<Seond_quantity>000000</Seond_quantity>
<Seond_quantity>000000</Seond_quantity>
<Second_quantity>0067.0</Second_quantity>
<Third_material />
<Third_quantity>000000</Third_quantity>
<Third_quantity>000000</Third_quantity>
<Third_quantity>000000</Third_quantity>
<Third_quantity>0008.0</Third_quantity>
<Third_quantity>000000</Third_quantity>
<Third_quantity>000000</Third_quantity>
</Record>
The file format should be as follows:--
KTP YEAR 2006 FIRSTWEEKNUMBER 51 NUMBER WEEKS 26 FACTORYM019
731000 0000.0 0001.9 0000.0 0000.0 0020.0 0000.0 0000.0 0000.0 0018.0 0000.0
 0000.0 0011.0 0000.0 0000.0 0000.0 0000.0 0049.0 0000.0 0000.0 0067.0
 0000.0 0000.0 0000.0 0008.0 0000.0 0000.0
Could some one help me in resolving this issue.
Regards
Praveen

Hi Praven,
couldn't you simply modify your target DATA type so it will be easier to handle?
For example something like:
<Header>
</Header>
<Record>
<Material>
<Number>..</Number>
<quantity>..</quantity>
<quantity>..</quantity>
</Material>
In this way file content conversion will be easier (easy)!
Regards,
Sergio

Receiver adopter using File Content Conversion

Guys,
I am using File Content Conversion at receiver end.
maintained record structure: Table1,Table2,Table4,Table5,Table6,Table7,Table8,Table9
and maintained parameters below menction for each table.
fieldFixedLengths
fieldNames
fixedLengthTooShortHandling
I want to create target file fixed length and the order which maintained in source file.(EXPECTED FORMAT).
But receiver File Content Conversion creating file in below menction format(FILE COMING FORMAT) which i don't want. Can any one help me what are the parameters do I need to maintain, to create the file same order which is like source file.
SOURCE FILE
100ABCDEF 0430000960603201321
2 000000000040008000802
400100160200002000015E59332 000000000010424400
50000000640672060320ABCDEF 043000096
600100100220887000311003510300958527437215 BAMBERGER POLYMERS
400100160100002000015E59347 000000000000008250
700100206430530603200010022088700
80010030643053060320000100220887009
400100160100002000015E59347 000000000000008260
9000010
<?xml version="1.0" encoding="utf-8"?>
<ns:CSAA_Bankdet_src xmlns:ns="urn:cs.www.abcdefinc.com/CSAA_ODSFTP_ECC_Bank_Details">
 <Table1>
 <RecordType>1</RecordType>
 <PriorityCode>00</PriorityCode>
 <Destination>abcdef</Destination>
 <BankOrginNo>043000096</BankOrginNo>
 <CreationDate>060320</CreationDate>
 <CretionTime>1321</CretionTime>
 <Spaces></Spaces>
 </Table1>
 <Table2>
 <RecordType>2</RecordType>
 <Destination>00000000</Destination>
 <BankOrginNo>0040008000</BankOrginNo>
 </Table2>
 <Table4>
 <RecordType>4</RecordType>
 <BatchNumber>001</BatchNumber>
 <ItemNumber>001</ItemNumber>
 <RecordOverflow>6</RecordOverflow>
 <SequenceNumber>020</SequenceNumber>
 <OverflowCode>0</OverflowCode>
 <CustomerNumber>002000015E</CustomerNumber>
 <InvoiceNumber>59332 0</InvoiceNumber>
 <DiscountAmount>00000000</DiscountAmount>
 <GrossAmount>010424400</GrossAmount>
 </Table4>
 <Table5>
 <RecordType>5</RecordType>
 <BatchNumber>000</BatchNumber>
 <ItemNumber>000</ItemNumber>
 <LockboxNumber>0640672</LockboxNumber>
 <DepositDate>060320</DepositDate>
 <Destination>abcdef</Destination>
 <BankOrigin>043000096</BankOrigin>
 <Spaces></Spaces>
 </Table5>
 <Table6>
 <RecordType>6</RecordType>
 <BatchNumber>001</BatchNumber>
 <ItemNumber>001</ItemNumber>
 <RemittanceAmount>0022088700</RemittanceAmount>
 <MICRTransitRouting>031100351</MICRTransitRouting>
 <MICRAccountNumber>03009585274372</MICRAccountNumber>
 <MICRCheckSerialNumber>15 BAMB</MICRCheckSerialNumber>
 <CustomerName>ERGER POLYMERS</CustomerName>
 </Table6>
 <Table4>
 <RecordType>4</RecordType>
 <BatchNumber>001</BatchNumber>
 <ItemNumber>001</ItemNumber>
 <RecordOverflow>6</RecordOverflow>
 <SequenceNumber>010</SequenceNumber>
 <OverflowCode>0</OverflowCode>
 <CustomerNumber>002000015E</CustomerNumber>
 <InvoiceNumber>59347 0</InvoiceNumber>
 <DiscountAmount>00000000</DiscountAmount>
 <GrossAmount>000008250</GrossAmount>
 </Table4>
 <Table7>
 <RecordType>7</RecordType>
 <BatchNumber>001</BatchNumber>
 <ItemNumber>002</ItemNumber>
 <LockboxNumber>0643053</LockboxNumber>
 <DepositDate>060320</DepositDate>
 <NoofDetailRecords>001</NoofDetailRecords>
 <BatchDollarAmount>0022088700</BatchDollarAmount>
 <Spaces></Spaces>
 </Table7>
 <Table8>
 <RecordType>8</RecordType>
 <BatchNumber>001</BatchNumber>
 <ItemNumber>003</ItemNumber>
 <LockboxNumber>0643053</LockboxNumber>
 <DepositDate>060320</DepositDate>
 <NoofDetailRecords>0001</NoofDetailRecords>
 <RemittanceDollarAmount>0022088700</RemittanceDollarAmount>
 <LastRecordIndicator>9</LastRecordIndicator>
 <Spaces></Spaces>
 </Table8>
 <Table4>
 <RecordType>4</RecordType>
 <BatchNumber>001</BatchNumber>
 <ItemNumber>001</ItemNumber>
 <RecordOverflow>6</RecordOverflow>
 <SequenceNumber>010</SequenceNumber>
 <OverflowCode>0</OverflowCode>
 <CustomerNumber>002000015E</CustomerNumber>
 <InvoiceNumber>59347 0</InvoiceNumber>
 <DiscountAmount>00000000</DiscountAmount>
 <GrossAmount>000008260</GrossAmount>
 </Table4>
 <Table9>
 <RecordType>9</RecordType>
 <TotalRecords>000010</TotalRecords>
 <Spaces></Spaces>
 </Table9>
</ns:CSAA_Bankdet_src>
FILE COMING FORMAT
100ABCDEF 043000096 0603201321
200000000
40010016020059332 0 00000000 010424400
40010016010059347 0 00000000 000008250
40010016010059347 0 00000000 000008260
50000000640672060320ABCDEF 043000096
600100100220887000311003510300958527437215 BAMBERGER POLYMERS
700100206430530603200010022088700
80010030643053060320000100220887009
9000010
EXPECTED FORMAT
100ABCDEF 043000096 0603201321
200000000
40010016020059332 0 00000000 010424400
50000000640672060320ABCDEF 043000096
600100100220887000311003510300958527437215 BAMBERGER POLYMERS
40010016010059347 0 00000000 000008250
700100206430530603200010022088700
80010030643053060320000100220887009
40010016010059347 0 00000000 000008260
9000010
Thanks
M

Hi,
Try to handle this with the context in the mapping.
I think your mapped xml will look like this-
100ABCDEF 043000096 0603201321
200000000
40010016020059332 0 00000000 010424400
40010016010059347 0 00000000 000008250
40010016010059347 0 00000000 000008260
50000000640672060320ABCDEF 043000096
600100100220887000311003510300958527437215 BAMBERGER POLYMERS
700100206430530603200010022088700
80010030643053060320000100220887009
9000010
SO this is because of context problem. All similar nodes are grouped in the Message Mapping.
1) For this you can try with Context Handling - i.e using RemoveContext,SPlity value functions etc in the message mapping.
2) Another way use XSLT mapping here. In this case it will be easier, because you just need to read the input xml as it is and produce the same.
3) One more thing, your input xml looks as if is the output xml. Is it required to have mapping here? If there is no transformation required, then you can do without any mapping, and you will get the required output as it is ..
Regards,
Moorthy
Message was edited by: Krishna Moorthy P

Problem in file content conversion from XML to CSV

Hi Experts,
I am finding problem in file content conversion. I need to convert the following XML file into CSV file:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_CROSS_REF xmlns:ns0="urn:dabur:idoc2file:pos">
 <Update_type>2</Update_type>
 <PLU>00000000</PLU>
 <Cross_ref_PLU>7777777</Cross_ref_PLU>
 <Capture_PLU />
 <Package_size />
 <Package_desc />
</ns0:MT_CROSS_REF>
The output file data has to be like:
2,00000000,7777777,,,,
The problem I am facing is while specifying the content conversion parameters in communication channel i dont know what recordset structure i should mention as all the records are directly under root. If I mention recordset structure as "ns0:MT_CROSS_REF" and parameters as
ns0:MT_CROSS_REF.fieldSeparator ,
ns0:MT_CROSS_REF.endSeparator 'nl'
i get error in communication channel monitoring and no file is posted.
Please help me as to what correct parameter i should mention in my case.
Thanks,
Regards,
Yash

Hi Chirag,
I cannot change the xml file as it comes after mapping idoc to a message type. How can I add ROOT in the xml? My message type is like MT_CROSS_REF and it has those 6 fields as in the XML (Update_type, PLU etc.). I do the mapping of these fields from a IDOC and get the XML.
I hope you got my point.
Thanks,
Yash

Problem with File Content Conversion

Hi All
I am facing a problem with file content conversion.
This is my sample file structure:
Header_Record (Occurance - 1)
Field1 in Header
Field2 in Header
Item(Occ-1 to n)
Field3 in Item
Field4 in Item
<<ItemType>> (Structure in Item) (Occ - 0 to n)
<<Field5>> in ItemType
<<Field6>> in ItemType
<<ItemTypeCategory>> (Structure in ItemType)(Occ - 0 to n)
<<<<Field7>>>> in ItemTypeCategory
<<<<Field8>>>> in ItemTypeCategory
Footer_Record (Occurance-1)
Field9
Field10
There is a key field 'Type' in all the above records with unique value in each record.
Now, I defined Field content conversion as follows:
Recordset Structure: Header_Record,1,Item, * , ItemType, * ,ItemTypeCategory, * ,Footer_Record,1
Recordset Sequence: Ascending
KeyField Name: Type
Following are parameters defiled:
Header_Record.Keyfieldvalue: 00
Header_Record.fieldseperator: ,
Header_Record.fieldnames: Field1,Field2
Header_Record.endseperator: 'nl'
Item.keyfieldvalue: 05
item.fieldseperator: ,
item.fieldfieldnames: field3,field4
item.endseperator: 'nl'
ItemType.keyfieldvalue: 10
itemType.fieldseperator: ,
itemType.fieldfieldnames: field5,field6
itemType.endseperator: 'nl'
ItemTypecategory.keyfieldvalue: 15
itemTypecategory.fieldseperator: ,
itemTypecategory.fieldfieldnames: field7,field8
itemTypecategory.endseperator: 'nl'
Footer.keyfieldvalue: 20
Footer.fieldseperator: ,
Footer.fieldfieldnames: field5,field6
Footer.endseperator: 'nl'
Now, i pass the following file:
00,111
05,222
10,333
15,444
20,555
What i expect out of my FCC is this (Sample output to show the hierarchy of field values):
00,111
05,222
<<10,333>>
<<<<15,444>>>>
20,555
But, I am getting this output (Hierarchy is missing. All the structures are in the same order without hierarchy):
00,111
05,222
10,333
15,444
20,555
Field values are being identified according to field content conversion, but, the hierarchy of the fields is missing.
Can you please tell me how should i change my FCC config?
Sorry for this long question.
Many Thanks
Chandra
Edited by: Chandra Sekhar H on Jan 30, 2009 7:10 PM
Edited by: Chandra Sekhar H on Jan 30, 2009 7:16 PM
Edited by: Chandra Sekhar H on Jan 30, 2009 7:17 PM

You will always get a flat structure from FCC. If you want hierarchichal strucuture, you have to create a target and map. You will get only like -
Root
--Recordset
Group1
Fields
Grop2
Fields
Group3
Fields
VJ

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

IDOC to flat File----Problem in File Content Conversion at receiver

hi experts,
I am doing a IDOC to flat file secnario.
My requirment is IDOCXI-Flat file
Format of flat file is like:--
Every segment in the IDOC will be converted into a single line of file(without any delimiter). So number of lines in flat file will be equal to number of segments in IDOC.
I am facing problem in File Content conversion.
Please help me out..
Thanks
Jaideep

Check this doc...
[How To...Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0 |https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a]

Using File Content Conversion converting XML format to text format

Hi All,
 I am able to convert to Text format using file content conversion, But the requirement is to convert the same for the structure with additional subnodes as in the example (also complex nested structures)
<ns0:SendXSDEmployeeDetails xmlns:ns0="http://ehro.eds.com/FRAMEWORK/FileToFile/FileCConverion">
 <Employee>
 <Employee_ID>2</Employee_ID>
 <Employee_Name>KannanKumar</Employee_Name>
 <Address>
 <Street>13th Cross Reddy</Street>
 <City>Bangalore</City>
 <Pincode>641026</Pincode>
 <Phone_No>
 <t1>9901934934</t1>
 <t2>9901934934</t2>
 </Phone_No>
</Address>
 </Employee>
</ns0:SendXSDEmployeeDetails>
can any one help on this please
I have already seen the blogs :
/people/krishnakumar.ramamoorthy3/blog/2007/01/27/generic-mapping-to-convert-nested-xml-to-flat--receiver-file-adatper
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
Can any one help to do this in simple way 

Hi,
Like correctly pointed by JaiShankar, the Sender File Adapter currently does not supoort such stracutures.
the strcuture supported is described in this link,
http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
Regards
Bhavesh

Problem with file content conversion for multiple substrcture. Please help!

Hi Experts,
 I am using file content conversion in file sender communication channel. The input file is a flat file with data like this:
 A01 AA8I0NBVDA 20090704 84900
 A02 AA8I0NBVDA 20090704 84900
 A03 AA8I0NBVDA 20090704 84900
 I want the data in sender side after content conversion to be like this:
<ns:Receive_Schedules xmlns:ns="http://mynamespace">
 <ScheduleData>
 <line>A01 AA8I0NBVDA 20090704 84900</line>
 <line>A02 AA8I0NBVDA 20090704 84900</line>
 <line>A03 AA8I0NBVDA 20090704 84900</line>
 </ScheduleData>
</ns:Receive_Schedules>
I have tried many options in file content conversion but getting the data like this:
<ns:Receive_Schedules xmlns:ns="http://mynamespace">
 <ScheduleData>
 <line>A01 AA8I0NBVDA 20090704 84900</line>
 </ScheduleData>
 <ScheduleData>
 <line>A02 AA8I0NBVDA 20090704 84900</line>
 </ScheduleData>
 <ScheduleData>
 <line>A03 AA8I0NBVDA 20090704 84900</line>
 </ScheduleData>
</ns:Receive_Schedules>
Following are the settings/properties have configured in content conversion:
Document Name Receive_Schedules
Document namespace http://mynamespace
Document Offset <no value>
Recordset Name <no value>
Recordset namespace <no value>
Recordset structure ScheduleData,*
Recordset sequence Ascending
Recordsets per message 1
Key field Name <no value>
Key Field Type String
ignoreRecordsetName true
ScheduleData.endSeparator 'nl'
ScheduleData.fieldNames line
ScheduleData.fieldSeparator 'nl'
How to get the desired message? What changes I need to do in content conversion settings? Please help!
thanks
Gopal
Edited by: GOPAL BALIGA on Jul 1, 2009 12:11 PM

Hi Ranjan,
My structure is like what you ahve defined.
scheduledata...1.1
...line....0...Unbound
I also tried the parameters you gave but still getting the same.
<ns:Receive_Schedules xmlns:ns="http://mynamespace">
<ScheduleData>
<line>A01 AA8I0NBVDA 20090704 84900</line>
</ScheduleData>
<ScheduleData>
<line>A02 AA8I0NBVDA 20090704 84900</line>
</ScheduleData>
<ScheduleData>
<line>A03 AA8I0NBVDA 20090704 84900</line>
</ScheduleData>
</ns:Receive_Schedules>
Following are the settings/properties have configured in content conversion:
Recordset structure ScheduleData,* -
> Is the value correct?
Recordset sequence Ascending -
> Is the value correct?
Recordsets per message 1 -
> Is the value correct?
ignoreRecordsetName true
ScheduleData.fieldSeparator nl
ScheduleData.fieldNames line
ScheduleData.endSeparator nl
Edited by: GOPAL BALIGA on Jul 2, 2009 5:28 AM

ERR: EXCEPTION_DURING_EXECUTE while using FILE CONTENT CONVERSION

Hi,
I'm trying a file to file scenario with File Content Conversion for Sender communication channel. But am getting the following error in SXMB_MONI
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code> 
<SAP:P1>com/sap/xi/tf/_MM_ContentBased_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/sap/xi/tf/_MM_ContentBased_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I tried the same message mapping for normal file to file scenario without using File Content Conversion. It went through fine.
Our file structure follows
 <Header>
 <Sysnum>01</Sysnum>
 </Header>
 <Body>
 <Name>ABCDE</Name>
 <Age>25</Age>
 <Stream>XYZ</Stream>
 </Body>
The Sender Communication Channel Parameters follows:

Recordset Str: Header,1,Body,1
Header.fieldFixedLengths : 2
Header.fieldNames : Sysnum
Body.fieldFixedLengths : 5,2,3
Body.fieldNames : Name,Age,Stream
ignoreRecordsetName : true
Looking for a solution
Thanks,
Ajay.

Hi Ajay,
your message mapping failed.
Copy the XML message from monitoring and exectute the mapping in Integration Builder with maximal trace to get the reason.
Regards,
Udo

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

Problem in file content conversion, file 2 xml scenario

Hi,
Could some one help me in finding out the error in my file to xml scenario, please do consider the following things what I did for this scenario.
1.My sender file structure is flat file with , seperated 4 fields. On receiver end expecting xml file.
2.Did file content conversion at sender file adapter and given parameters as follows.
     Document name             : MT_FileInput
     DocumentnameSpace     : http://file/praveenworkshop
     Recordset Name             : DT_Record
     Recordset Structure        : DT_Row,*
     KeyfieldType                   : String( default)
    DT_Row.fieldnames          : FirstName,LastName,City,PostCode
    DT_Row.fieldSeparator      : ,
    DT_Row.processConfiguration: FromConfiguration
    Dt_Row.endSeparator       : 'nl'
3. I did check in Adapter Monitor that Both Sender and receiver adapter are showing green and It was showing 'Adapter is up and running: But no messages processed'
4. I did check the SXMB_MONI which was showing " Scheduled for Outbound processing"
5. In SXMB_MONI outbound processing payload was picking up the file and also inbound processing showing the same.
6. my source folder and destination folder are very simple c:/praveenfiles/input and c:/praveenfiles/output
    files are source file praveen.txt and destination file praveenOP.xml
Please help me in finding out the error to see the output file in my output folder.

Hi Praveen,
Hope these bloga are useful to you..
File content conversion sites
/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/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
/people/shabarish.vijayakumar/blog/2005/08/17/nab-the-tab-file-adapter
/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/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/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Thanks,
Satya

Encoding problem after File Content Conversion

Hi SAP gurus!
we're about exporting debitor data via PI into CSV files. Therefore we use a mapping to an intermediate structure. In the receiver file adapter a file content conversion is done into the target CSV format.
We have a lot of data with eastern europe characters. Right after the mapping, everything is fine. All characters are processed correctly. After the file content conversion, the files written on the target system contain "?" instead of the special characters.
Does anybody have any hint to fix this problem? We already tried to change the "file.encoding" parameter, but hasn't helped.
Thanks in advance for your support!
Cheers,
Matthias

Hello Satish,
thanks for your reply.
First, I have to explain, that the sender side isn't done by file adapter but IDoc adapter. So I cannot change the encoding on sender side.
Both on IDoc and file side, the data is ok. Only when inserting the file content converion, the files become corrupted.
Without using the FCC, tjhe target files are stored as UTF-8. When using FCC the files are stored as ANSI. (I tested this by opening the files in notepad and performing "Save As")
Do you have further ideas?
Cheers,
Matthias

Problem using file content conversion

Similar Messages

Maybe you are looking for