Receiver adopter using File Content Conversion

Question

Guys,
I am using File Content Conversion at receiver end.
<b>maintained record structure:</b> 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.
<b>SOURCE FILE</b>
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>
<b>FILE COMING FORMAT</b>
100ABCDEF    043000096 0603201321                                              
200000000
40010016020059332  0        00000000  010424400
40010016010059347  0        00000000  000008250
40010016010059347  0        00000000  000008260
50000000640672060320ABCDEF    043000096                                        
600100100220887000311003510300958527437215    BAMBERGER POLYMERS                    
700100206430530603200010022088700                                              
80010030643053060320000100220887009          
9000010
<b>EXPECTED FORMAT</b>
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

Answer 1

Hi,
Try to handle this with the context in the mapping.
I think your mapped xml will look like this-
<i>100ABCDEF 043000096 0603201321
200000000
40010016020059332 0 00000000 010424400
40010016010059347 0 00000000 000008250
40010016010059347 0 00000000 000008260
50000000640672060320ABCDEF 043000096
600100100220887000311003510300958527437215 BAMBERGER POLYMERS
700100206430530603200010022088700
80010030643053060320000100220887009
9000010</i>
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