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

Similar Messages

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

How to convert XML message in text format by using HTTPS-Receiver adapter

Is it possible to convert XML message in text format when we use HTTPS as the receiver adapter?
If yes, how?
Thanks!
Mrudula

Hi Mrudula,
As far as i know there are no content conversion methodology for HTTPS as the recevier adapter.
Also you can read through these links to confirm the same:
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/content.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst30.htm
SAP NetWeaver - XML Communication Interface (CA-XML) [original link is broken]
Regards,
abhy
note: reward the helpful.

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

File Adapter - File Content Conversion to XML last element missing

I'm using the SAP File Adapter with File Content Conversion to convert | (pipe) delimited records into XML.
When the last field is blank, I would expect that an empty node gets created, however, the node doesn't get created at all.
For example given these settings...
Record.fieldSeparator = |
Record.endSeparator = 'nl'
Record.fieldNames = FIELD1,FIELD2,FIELD3
Using this three record file as my data...
|123|XYZ
ABC||XYZ
ABC|123|
When converted to XML, this is what the recordset XML structure looks like...
<Recordset>
<Record>
<FIELD1 />
<FIELD2>123</FIELD2>
<FIELD3>XYZ</FIELD3>
</Record>
<Record>
<FIELD1>ABC</FIELD1>
<FIELD2 />
<FIELD3>XYZ</FIELD3>
</Record>
<Record>
<FIELD1>ABC</FIELD1>
<FIELD2>123</FIELD2>
</Record>
</Recordset>
Notice that the last record is missing the "FIELD3" element.
Edited by: William Krick on Jun 17, 2011 4:49 PM

Giuseppe Agnello wrote:
> Sorry, there was a typo in the parameter name.
> Word fields should start with capital F.
> Try with Record.missingLastFields, with value "add"
>
> http://help.sap.com/saphelp_nw70/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
>
> Similar issue was resolved with same parameter in this thread:
> Sender file adapter with FCC not creating last field
That did the trick. It was a typo. Thanks Giuseppe.
I'm willing to bet that this parameter was added to fix the parsing bug without breaking existing users that had already worked around the original bug. You shouldn't really have to special case the last field.

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!

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

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

Idoc to File Scenarion Using File Content Conversion for Sales order data.

Hi Frineds,
WOuld like to know in what strucuture should i design my output strucutre to get data from idoc coming from SAP system.
How to enbble file contenct conversion to get txt file.
Need a detial view of this scenario.
Please help.

Hi,
Get the target file structure format from the system or applicaiton which wants to use this data...
Based on this create message type in ESR and then configure the FCC parameters in the file adapter ..
if the structure is available and based on that want to know FCC ..then post the same some one here can help..
based on your requirement structure needs to be implemented and mapping as well
HTH
Rajesh

Error in File to JDBC Scenario using File Content Conversion.

Hi ,
I am sending a text file in CSV format, with all the configurations done in the sender and receiver channels.
But the adapter monitoring says this:
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter 'EmployeeDetails.fieldFixedLengths' or 'EmployeeDetails.fieldSeparator' is missing
Consistency check: no. of arguments in 'EmployeeDetails.fieldFixedLength' does not match 'EmployeeDetails.fieldNames' (0 <> 6)
One thing to note here is that
1. EmployeeDetails.fieldSeparator is given as ','
2. I haven't used any fieldFixedLengths.
Pointers in this regard would be higly appreciated.
Regards,
Younus

cross check if you have specified EmployeeDetails.fieldFixedLengths and EmployeeDetails.fieldSeparator. only one must be used.
in case you have already specified,
EmployeeDetails.fieldSeparator as ',' , then delete that line and reenter the details again, activate and run the scenario.

Using File Content Conversion

Hi
My source is like -,-,-,-,a,b,c like this.
and here -,-,-,- means white spaces.
If i do one to one mapping..should i get the same target as same with spaces
Regards,
YRaj.

Yes that is correct if you do one to one mapping then as long as the elements come in the source structure you will have the nodes in the target structure.
To ensure this you could also use a mapwithdefault funstion and simply put a space in there
let me know if this helps

J2SE XML to Flat File Content Conversion

Hi
I've currently got a scenario which sends a flat file to the integration server, it gets mapped and sent to a receiver adapter on a deployed j2se engine.
I'm now trying to convert the xi-xml structured file to a flat file again on the j2se side (the same flat file format it originally had).
My original flat file looks like this -
477
477=AA1
My xml file looks like this -
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ResultMessage xmlns:ns0="urn:xxxx-com:a_test_j2se_filetofile">
<Item>
 <field1>477</field1>
</Item>
<Item>
 <field1>477</field1>
 <field2>AA1</field2>
</Item>
</ns0:ResultMessage>
I am using these content conversion parameters:
xml.addHeaderLine=0
xml.fieldSeparator==
xml.endSeparator='nl'
I get this error on the integration engine (sxmb_moni):
Error while sending by HTTP (error code: 500, error text: Internal Server Error:java.lang.NullPointerException) (See attachment HTMLError for details)
and the j2se adpater log says this:
17:16:32 (4120): Message "13b9d644-54c9-4ffb-0c40-db4c14458d77" of type "application/xml", kind "B" received
17:16:32 (4124): Parsing XML message
17:16:32 (4131): ERROR: Message processing failed with "java.lang.NullPointerException"
What am i missing?

So, now... I did a test configuration in XI and sent your test-payload...it worked.
The J2SE adapter configuration:
File adapter java class
classname=com.sap.aii.messaging.adapter.ModuleXMB2File
version=30
mode=XMB2FILEWITHCONVERSION
#Adress for XMB endpoint -
XI.httpPort=8111
XI.httpService=/file/receiver
#File Adapter specific parameters -
file.createDir=1
file.targetDir=c:/transfer/inbound
file.targetFilename=xmboutput.txt
#file.writeMode=append
#file.writeMode=overwrite
file.writeMode=addCounter
file.counterMode=immediately
#file.counterMode=afterFirst
file.counterSeparator=_
file.counterFormat=00000
file.counterStep=1
#File Content Conversion specific parameters -
xml.addHeaderLine=0
xml.fieldSeparator==
xml.endSeparator='nl'
And here the configuration of the receiver communication channel in the integration directory:
Adapter Type: XI
Receiver
Transport-Protocol: HTTP 1.0
Message-Protocol: XI 3.0
Adapter-Engine: Integration Server
Adressing-Type: URL Address
Target Host: <yourJ2SEip>
Service Number: 8111
Path Prefix:http://<yourJ2SEip>:8111/file/receiver
Authentication Data
Logon data for non-SAP systems
User
Password
That's it... sent your payload and got the wished result:
477
477=AA1
Regards,
Heinrich

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

Hi Question about Sender File Content Conversion

Hi All,
I have a flat file i need convert that flat file to the below XML format using File content Conversion, can anybody help me on this with example File content Convertion parameters
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_FileSend xmlns:ns0="http://test">
 <Recordset>
 <Contact>
 <Name>ABC</Name>
 <Number>123</Number>
 <Address>
 <HouseNumber>246789</HouseNumber>
 <StreetNumber>100</StreetNumber>
 <Phone>
 <Mobile>90000000</Mobile>
 <LandLine>12345678</LandLine>
 </Phone>
 </Address>
 <Email>
 <Office></Office>
 <Personal></Personal>
 </Email>
 </Contact>
 </Recordset>
</ns0:MT_FileSend>

Hi Sudheer reddy,
 Good question.
File content conversion parameters are:
1) Doccument Name: Doccument name is nothing but message type name for file side: MT_FileSend
2) Doccument Namespace: mention the name space for the message type.
3) Doccument Offset: for which row and which coloumn doccument has to be write.
4) recordset name: mention the record set name: Recordset
5) Recordset Namespace: if the namespace is different for message type name space mention name space or otherwise it is blank.
6) Recordset Structure: Mention the structure name
7) Recordset Sequence: mention the sequence of the recordset Ascending or Decending
8) Recordset permessage: Would define no of record sets per message.
9) Key-field name: to query to the doccument
10) Key field type: string(Case-senstive)
fieldValues
fieldSeparator
endSeparator
Note: pls check in SDN about file content conversions it so many blogs are available, u can easily understand.
Regards,
Sateesh

Using File Content Conversion converting XML format to text format

Similar Messages

Maybe you are looking for