Receiver - File Content Conversion(FCC)

Hi,
I am facing problem which creating file in destination FTP server with FCC.
Message Type - MT_GCPO
DATA Type - DT_GCPO
Substructures in data type -DT_GCPO are
FILE_HDR, -> 1
ORD_HDR, ->1
SHIP_TO_RCD, ->1
CARD_DETAIL_RCD -> 0 - unbounded
MSG_RCD, -> 0 - unbounded
ORDER_TRL_RCD, -> 1
FILE_TRL_RCD -> 1
In Receiver channel, metioned details as
Record Set Structure - FILE_HDR,ORD_HDR,SHIP_TO_RCD,CARD_DETAIL_RCD,MSG_RCD,ORDER_TRL_RCD,FILE_TRL_RCD
FILE_HDR.fieldFixedLengths     1,10,10,10,8,6,8,3
FILE_HDR.endSeparator     'nl'
ORD_HDR.fieldFixedLengths     1,15,10,8,6,1,3,11,3,2,8,25,7,3,8,80
ORD_HDR.endSeparator     'nl'
SHIP_TO_RCD.fieldFixedLengths     1,15,20,10,1,32,32,32,20,2,9,15,10
SHIP_TO_RCD.endSepartor     'nl'
CARD_DETAIL_RCD.fieldFixedLengths     1,15,2,10,1,10,11,6,8,5,8,2,19
CARD_DETAIL_RCD.endSeparator     'nl'
MSG_RCD.fieldFixedLengths     1,15,2,30,30,30,5,70
MSG_RCD.endSeparator     'nl'
ORDER_TRL_RCD.fieldFixedLengths     1,15,2,2,2,2
ORDER_TRL_RCD.endSeparator     'nl'
FILE_TRL_RCD.fieldFixedLengths     1,8
FILE_TRL_RCD.endSeparator     'nl'
Error message - "File Adapter Receiver Channel CC_GC_PO: Not initialized - cannot proceed: nullI checked Communication Channel and it is in active status.
Adapter Framework caught exception: Channel has not been correctly initialized and cannot process messages"
Not sure how to proceed further ? Please shred some light on this.
Appreciate your help.
Thanks,
Krishna

Hi,
I got an error message like this "Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error occurred while connecting to the FTP server "ftp.bostonapparel.com:21": java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Column value '25P' too long (>1 for 5. column) - must stop', probably configuration error in file adapter (XML parser error)"
I checked all parameters
FILE_HDR.fieldFixedLengths     1,10,10,10,8,6,8,3
FILE_HDR.endSeparator     'nl'
ORD_HDR.fieldFixedLengths     1,15,10,8,6,1,3,11,3,2,8,25,7,3,8,80
ORD_HDR.endSeparator     'nl'
SHIP_TO_RCD.fieldFixedLengths     1,15,20,10,1,32,32,32,20,2,9,15,10
SHIP_TO_RCD.endSepartor     'nl'
CARD_DETAIL_RCD.fieldFixedLengths     1,15,2,10,1,10,11,6,8,5,8,2,19
CARD_DETAIL_RCD.endSeparator     'nl'
MSG_RCD.fieldFixedLengths     1,15,2,30,30,30,5,70
MSG_RCD.endSeparator     'nl'
ORDER_TRL_RCD.fieldFixedLengths     1,15,2,2,2,2
ORDER_TRL_RCD.endSeparator     'nl'
FILE_TRL_RCD.fieldFixedLengths     1,8
FILE_TRL_RCD.endSeparator     'nl'

Similar Messages

Limitations of File Content Conversion (FCC)

Hi
I want to know the Limitations of File Content Conversion (FCC) while defining for a particular structure.
I was bit confused from the [SAP Help |http://help.sap.com/saphelp_nw2004s/helpdata/EN/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm]
It says "There can be a fixed or variable number of substructures in a recordset." but from sdn i found
[Content Conversion in File Adapter |Content Conversion in File Adapter]
It will support "A maximum of 3 hierarchy level will be supported in FCC"
Is <recordset> Mandatetory in for FCC, what if we dont have <recordset> in the structure.
Till what hierarchy level it supports
what is the limitation of FCC
Regards,
Varun
Edited by: Varun Reddy on Feb 26, 2009 4:52 PM

Varun,
Both statements are true:
Consider, for instance, a file containing orders. You could have:
HEADER;123;456;11112 (containing sender 123, receiver 456, order number 11112)
PARTNER;OR;234 (containing the ordering partner number 234)
PARTNER;DL;235 (containing the delivery address 235)
DATE;OR;20090226 (containing the order date 26/02/2009)
DATE;DL;20090228 (containing the delivery date 28/02/2009)
LINE;9998;12 (article number 9998, quantity 12)
LINE;9996;25 (article number 9996, quantity 25)
LINE;9991;3 (article number 9991, quantity 3)
HEADER;123;456;11113 (2nd order containing sender 123, receiver 456, order number 11113)
PARTNER;OR;234 (containing the ordering partner number 234)
PARTNER;DL;237 (containing the delivery address 237)
DATE;OR;20090226 (containing the order date 26/02/2009)
DATE;DL;20090301 (containing the delivery date 01/03/2009)
LINE;9998;4 (article number 9998, quantity 4)
Parsing such a file with FCC would be possible, provided there's an identifier that indicates the type of line (like 'HEADER', 'PARTNER', etc). This is an example of There can be a variable number of substructures in a recordset.
If the records do not contain an identifier from which you can see the line type, FCC can only parse this if the order of the various structure types is fixed, so that it can determine from the line number what type of record this is. This would be an example of There can be a fixed number of substructures in a recordset.
Now, about A maximum of 3 hierachy level will be supported in FCC. In the FCC, there are three levels: the recordset (one order in the above example), the record (a line in the file) and the field (the order number, for instance). The FCC does not support files with deeper nesting. For instance, if a line item in your flat file could also contain a delivery date, FCC does not support this.
Hope this helps,
Koen

Can External Definition be used or Receiver File content conversion (CSV)?

Hi Experts,
I'm a newbie to SAP PI and I started working on file to File(FCC) scenario in which I am provided with the receiver structure as an External definition. The structure is like
Name
Place
Designation
Salary
hike
Can I use the same structure (External Definition) for the receiver file content conversion or do I need to create another specific structure?
Can I convert the target CSV file to UTF-8 encoding?
Please help.
Regards,
Taro

Hi,
Can the above specified structure be used for receiver FCC? Does this work? Can this be converted to UTF-8?
If it can be used, how do we specify the parameters for FCC then as there's no root element?
Regards,
Taro

Receiver file Content Conversion with Header line

Hi,
Here I am doing receiver file content conversion with header line.
I am able to get the output file correct, when I open the file in notepad the header line and data appearing in the same line (not accepted).
But when I tried to open the name file in internet explorer I can see the header line and data in two different lines (accepted).
What should I do I want to see the same output in the notepad?
Please help me out.
Thanks in advance,
Srikanth.

You can use NameA.addHeaderLine.
Specify whether the text file will have a header line with column names. The following values are permitted:
0 u2013 No header line
1 u2013 Header line with column names from the XML document
2 u2013 As for 1, followed by a blank line
3 u2013 Header line is stored as NameA.headerLine in the configuration and is applied
4 u2013 As for 3, followed by a blank line
The below weblinks will help you to know the other paramters.
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
http://help.sap.com/saphelp_nwpi71/helpdata/en/44/686e687f2a6d12e10000000a1553f6/content.htm

Receiver File content conversion with nested structure

Hi Guys,
I have the below nested structure and have to convert it using receiver file content conversion.
<Header> [o, unbounded]
   <A>a</A>
   <B>b</B>
</Header>
<record>   [0, unbounded]
   <field1>
        <X1>x</X1>
        <Y1>y</Y1>
   </field1>
   <field2>
         <X2>x</X2>
         <Y2>y</Y2>
   </field2>
</record>
The file is a comma separated one. Please let me know how to configure the content conversion.
Thanks

Hi Mukesh,
Have a look at the Shabz's blog for the receiver File content conversion : File Adapter (Receiver) - Are we "really" sure about the concepts?
Thanks,
Pooja

File adapter: Receiver File Content Conversion problem.. XML to CSV..!!

Hi,
I am facing some problem in FCC for Receiver adapter. It has to convert from XML to CSV File.
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:PaymentFull_Target xmlns:ns0="http://sdn.com/Payment">
- <RECORDSET>
- <Header>
<LineItem>1</LineItem>
<SaleNumber>102</SaleNumber>
<TransNumber>105</TransNumber>
<Store>1326</Store>
<variant>Z6</variant>
<TransType>NEW</TransType>
<Adjustm_Type />
</Header>
- <Header>
<LineItem>2</LineItem>
<SaleNumber>102</SaleNumber>
<TransNumber>105</TransNumber>
<Store>1326</Store>
<variant>Z6</variant>
<TransType>NEW</TransType>
<Adjustm_Type />
</Header>
- <Header>
<LineItem>3</LineItem>
<SaleNumber>102</SaleNumber>
<TransNumber>105</TransNumber>
<Store>1326</Store>
<variant>Z6</variant>
<TransType>NEW</TransType>
<Adjustm_Type />
</Header>
</RECORDSET>
</ns0:PaymentFull_Target>
Output File is coming only with lineitem values , remaining fields are not coming.
*1,2,3*
FCC Used...
RecordSet Structure -- Header
Header.fieldNames -
LineItem,SaleNumber,TransNumber,Store,variant,TransType,Adjustm_Type
Header.fieldSeparator----- ,
Header.endSeparator----- 'nl'
Did I miss anything.. any idea whats going wrong?
Thanks
Deepthi

Hi Deepthi,
Mention the occurrence of header in Recordset
You specify like this:
Recordset: Header, *
Header.fieldSeparator : u2018Field Separatoru2019
-->For FCC on Receiver side you donu2019t have to mention the field names.
-->The u2018endSeparatoru2019 parameter needs to given for substructure only
Check this links:
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
/people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
Rgds,
Akhila

Receiver File content conversion for multi level hireachy

Receiver channel file content conversion..
this is SAP proxy to FIle Scenario, which will get invoice details from SAP along with multiple invoice texts for each invoice.
I would like to have below mentioned payload at Target side,
<MT_Invoice>
<File Header>    1...1
<f1> customer invoices </f1>
<f2> 12/02/2010 </f2>
</File Header>
<Invocie header>
<f1> Invoice number1 </f1>
<f2> customer number1 </f2>
</Invoice header>
<Invoice text>
<f1> Inovice no1-text1 </f1>
</Invoice text>
<Invoice text>
<f1> Inovice no1-text2 </f1>
</Invoice text>
<Invocie header>
<f1> Invoice number2 </f1>
<f2> customer number2 </f2>
</Invoice header>
<Invoice text>
<f1> Inovice no2-text1 </f1>
</Invoice text>
<Invoice text>
<f1> Inovice no2-text2 </f1>
</Invoice text>
<Invocie header>
<f1> Invoice number3 </f1>
<f2> customer number3 </f2>
</Invoice header>
<Invoice text>
<f1> Inovice no3-text1 </f1>
</Invoice text>
<Footer> 1..1
<f1> have a great day </f1>
</footer>
</MT_Invoice>
for the above payload file should come as mentioned below
customer invoices 12/02/2010
invocie number1 customer no 1
invoice no1-text1
invoice no1-text2
invocie number2 customer no 2
invoice no2-text1
invoice no2-text2
invoice no2-text3
invocie number3 customer no 3
invoice no3-text1
have a great day
For to get the above payloadI have create a message type like
MT_invoice
header   1...1
   f1         1
   f2         1
invoice details   0... unbound
   f1           1
   f2           1
invoice text     0.... unbound
   f1
footer       1...1
   f1          1
Please correct me if my message type declaration was wrong...
Please suggest how do i need to approach for message mapping and as well as FCC in File adapter...
Edited by: Vidyadhar Kurmala on Dec 2, 2010 10:28 AM

It is not possible to create alternating nodes in graphical mapping tool.
I recommend using the MessageTransformBean for FCC, as this supports a 2-level hierarchy.
Then you add a node record like this:
<MT_Invoice>
<Record>
<File Header> 1...1
<f1> customer invoices </f1>
<f2> 12/02/2010 </f2>
</File Header>
</Record>
<Record>
<Invocie header>
<f1> Invoice number1 </f1>
<f2> customer number1 </f2>
</Invoice header>
<Invoice text>
<f1> Inovice no1-text1 </f1>
</Invoice text>
<Invoice text>
<f1> Inovice no1-text2 </f1>
</Invoice text>
</Record>
<Record>
<Invocie header>
<f1> Invoice number2 </f1>
<f2> customer number2 </f2>
</Invoice header>
<Invoice text>
<f1> Inovice no2-text1 </f1>
</Invoice text>
<Invoice text>
<f1> Inovice no2-text2 </f1>
</Invoice text>
<Invocie header>
<f1> Invoice number3 </f1>
<f2> customer number3 </f2>
</Invoice header>
<Invoice text>
<f1> Inovice no3-text1 </f1>
</Invoice text>
</Record>
<Record>
<Footer> 1..1
<f1> have a great day </f1>
</footer>
</Record>
</MT_Invoice>

Doubt regarding Recever file adapter file content conversion (FCC)

Hi Expetrts, below is the my target structure.
<?xml version="1.0" encoding="TF-8"?>
<ns1:MT_StatusChange xmlns:ns1="urn:passhe.com/ChangeOfStatusISA26">
     <IV_ST_OBJID>65390091</IV_ST_OBJID>
     <IV_BEGDA>25082008</IV_BEGDA>
     <LT_STUDENT_STATUS>
           <item>
          <HS_CAMPUS>65</HS_CAMPUS>
          <STOBJID>65390091</STOBJID>
          <STUDENT12>michal</STUDENT12>
          <HS_STATUS>MISC</HS_STATUS>
           <item>
        <LT_STUDENT_STATUS>
</ns1:MT_StatusChange>
How to configure in File Content Conversion Recever File Adapter for above target structure. i have done as below, but i am getting error. please correct me where i did mistake.
Recordset Structure : IV_ST_OBJID,IV_BEGDA,LT_STUDENT_STATUS,item
IV_ST_OBJID.fieldNames : IV_ST_OBJID -> for this field there is no subfield
IV_ST_OBJID.fieldSeparator: , (comma)
IV_BEGDA.fieldNames : IV_BEGDA -> for this field there is no subfield
IV_BEGDA.fieldSeparator: , (comma)
LT_STUDENT_STATUS.fieldNames : HS_CAMPUS,STOBJID,STUDENT12,HS_STATUS
LT_STUDENT_STATUS.fieldSeparator: 'nl'
item.fieldNames : HS_CAMPUS,STOBJID,STUDENT12,HS_STATUS
item.fieldSeparator: , (comma)
I am getting below error:
'Conversion configuration error: Unknown structure 'ns1:MT_StatusChange' found in document', probably configuration error in file adapter (XML parser error)'
Thanks
Dhanush.

Hi Dhanush,
                    It is better always if u have a structure with Header and trailers if u have a subsrtuctures in it & always try make it in this format:
<?xml version="1.0" encoding="UTF-8"?>
<MT_ContentConversion_Test>
   <Header>
      <F1>HF1</F1>
      <F2>HF2</F2>
   </Header>
   <Item>
      <F1>IF1</F1>
      <F2>IF2</F2>
   <Item>
   <Trailer>
      <F1>TF1</F1>
      <F2>TF2</F2>
   </Trailer>
</ns0:MT_ContentConversion_Test>
Try to go through this blog it will be very helpful to u :
/people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts
Regards,
Vinod.

Receiver File content conversion - NO Output

Hi, yesterday i posted already to this topic but i chose to make a new thread.
I have an IDoc2File Scenario where i put the generated File to the filesystem of the XI-Server.
I try to do a file content conversion at the receiver side. I already read several blogs and also the official documentation (which is kind of bad - because the arne't posted all supported parameters which could be used on the recordset)
But anyway, the is a txt file written but without any details inside, no data is deliverd.
I do a message mapping and try to put only some data to the end-file.
here is my MT which i try to convert:
MT_Tafel
++TafelRecordset
+++TafelDetailsStructure
++++TAFIST
++++TAFSOLL
My parameters at the receiver communication channel are:
Recordset: TafelDetailsStructure
TafelDetailsStructure.endSeparator = 'nl'
TafelDetailsStructure.addHeader = 0
TafelDetailsStructure.fieldSeparator = ,
I have the right message protocol, i am trying to write a simple text file, i have no file-coding like ASCII, file is directly written into an empty one - and that's all.
The file is written but without data inside.
Do i have to announce the filednames i want to write? Like TafelDetailsStructure.fieldNames??
Do i have to add Parameters concerning the tags on the higher level, like TafelRecordset?
Is there a general overview about all parameters you can use on this file content conversion?
Can anybody help me with my scenario - i have no clue what i have done wrong. Communcation channel says everthing is fine, message succesfully transfered.
best regards, Jens

hi,
you need to mention the names of the field by
TafelDetailsStructure.fieldNames where u need to specify the filed names.
and also chk the similar thread
content conversion
plsz check the blog
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
check this like below,
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
hope this helps,
kvr
Message was edited by:
PrasadBabu Koribilli

Receiver File Content Conversion concerns

Dear SAP experts,
Need your advise regarding File Content Conversion.
I have here the XML,
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:CSV xmlns:ns0="http://pg.com/xi/tom/connect/edi">
<SLI_root> ---> this is the root node of 'CSVFileName' and 'SLI'
<CSVFileName>Globus_20080306</CSVFileName>
<SLI> ---> this is the root node of the below fields
<PERIO>20071222</PERIO>
<EAN>737052018164</EAN>
<ILN>4304452000004</ILN>
<SALES>16</SALES>
<TURNO>120</TURNO>
<PERFL>W</PERFL>
<SUBSFL>X</SUBSFL>
<SALUN>ST</SALUN>
<CURRENCY>EUR</CURRENCY>
<STOCK>000000000</STOCK>
<STOUN>ST</STOUN>
</SLI>
<SLI>
<PERIO>20071222</PERIO>
<EAN>737052018232</EAN>
<ILN>4304452000004</ILN>
<SALES>3</SALES>
<TURNO>38.699997</TURNO>
<PERFL>W</PERFL>
<SUBSFL>X</SUBSFL>
<SALUN>ST</SALUN>
<CURRENCY>EUR</CURRENCY>
<STOCK>000000000</STOCK>
<STOUN>ST</STOUN>
</SLI>
<SLI>
</SLI_root>
</ns0:CSV>
CSV --> The Message Type of the XML.
SLI_root is under CSV
CSVFileName and SLI are under SLI_root
PERIO, EAN, ILN.. etc. are under SLI
SLI_root is under CSV.
CSVFileName and SLI are under SLI_root.
PERIO, EAN, ILN,... fields are under SLI.
The parameters i've set in Content Conversion are:
Recordset Substructure: SLI_root,SLI
SLI_root.endSeparator: 'nl'
SLI_root.fieldSeparator: 'nl'
SLI.addHeaderLine: 3
SLI.headerLine: PERIO;EAN;ILN...
SLI.fieldSeparator: ;
My output should be,
PERIO;EAN;ILN;SALES;TURNO;PERFL;SUBSFL;SALUN;CURRENCY;STOCK;STOUN
20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;00000000;ST
20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;00000000;ST
20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;00000000;ST
The parameters i've set in Content Conversion are:
SLI_root.endSeparator: 'nl'
SLI_root.fieldSeparator: 'nl'
SLI.addHeaderLine: 3
SLI.headerLine: PERIO;EAN;ILN...
SLI.fieldSeparator: ;
SLI.endSeparator: 'nl'
When i've run my scenario, the output is this,
Globus_20080306;20071222;737052018164;4304452000004;16;120;W;X;ST;EUR;000000000;ST
20071222;737052018232;4304452000004;3;38.699997;W;X;ST;EUR;000000000;ST
20071222;737052018263;4304452000004;1;12.9;W;X;ST;EUR;000000000;ST
20071222;737052018294;4304452000004;1;10.45;W;X;ST;EUR;000000000;ST
The header lines are not present and the value of CSVFileName (Globus_20080306) was inserted in my values.
Kindly advise what is wrong on my parameters set.
Or is there something missing in my configs.
Or i will change my structure of XML ?
Thank you very much!
Fred

Hi Raj,
Im just 4months working in SAP XI, and i still consider myself as a beginner.
I've only used Receiver File Adapter in my scenario (NO Sender File Adapter)
These are the configurations i've made in the Receiver File Comm Channel.
For the Parameters TAB:
File Receiver
Transport Protocol: File System (NFS)
Message Protocol: File Content Conversion
Adapter Engine: Integration Server
File Access Parameters:
Target Directory: * specified directory
File Name Scheme: .csv
Processing Parameters:
File Construction Mode: Create
Write Mode: Directly
File Type: Text
Adapter-Specific Message Attributes
- Use Adapter-Specific Message Attributes
- File Name
Run Operating System Command After Message Processing
Command Line: chmod 664 %F
Content Conversion Parameters:
Recordset Structure: SLI
SLI.addHeaderLine: 3
SLI.headerLine: PERIO;EAN;ILN;....
SLI.field Separator: ;
SLI.endSeparator: 'nl'
Adapter Status: Active
For the Identifiers TAB: (i've had no configs on that)
For the Module TAB:
Processing Sequence:
Number: 1
Module Name: CallSapAdapter
Type: Local Enterprise Bean
Module Key: 0
That's all in my configs in Receiver File Adapter.
Is it ok if you check this?
I've read a SAP Blogs, https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/6400. [original link is broken] [original link is broken] [original link is broken]
I've read in it that there must be set-up in the Module TAB to get the Filename in the Dynamic Configuration.
Kindly advise.
Thank you very much for your usual support.
Fred

Receiver File Content Conversion - Multiple Hier. Levels, Several Files

you can create several files using single message execution.
one source message structure and target multiple messgae types(0..1) occurance
and same thing you can implement in your Interface mapping.
1 -> Multiple Inbound interfaces
your target final strcture would be with Header,lineitems.
your JDBC->XI Intermedicate.
XI Intermediate ->XI final (this final structure will create the your file)
that way you can design your scenario.
Regards,
Venu.

Hello Venu, thanks for answering,
When you talk about intermediate structure you are referring to the approach I mentioned in the link above or to something that can be done using the same scenario structure I have right now?
I am going I little bit deeper in my scenario just in case I havent been so clear in my first explanation:
Lets suppose I have 3 stores: 1001,1002,1003
For each store there are 2 items: 999,888
So XI retrieves the information from the DB thru a stored procedure. This is the output:
STORE--PLU
1001--999
1001--888
1002--999
1002--888
1003--999
1003--888
Please note the information is coming in a flat structure. In the beginning I tried to separate it into several outputs (selects) as shown below but I relaized that was not possible to be handled by XI:
STORE--PLU
query 1
1001--999
1001--888
query2
1002--999
1002--888
query
1003--999
1003--888
That would have been the best approach as I would have generated one single file for each message and thats it, but unfortunately, Xi does not work that way with MSSQL Queries. So I had to made something up based on the answers I got from the SDN experts (Link is below in first message). There was when I used context handling for generating the structures myself within one single message.
In the scenario shown above I would have just needed to generate the following structure for creating messages from the source:
Level1: Main Node
Level 2: Header
Level 2: Body
But now, As I am forced to generate my 3 structures within 1 single message, I had to insert one more node to wrap header and body in per iteration (as a file would do):
Level1: Main Node
Level2: File
Level3: Header
Level3: Body
And that is the problem I am asking help for, that allegedly, XI File Content conversion can just handle up to 2 levels.
Thanks again for answering Venu.
Regards.
Edited by: Anibal Granado on May 12, 2010 11:34 PM

Receiver File content conversion

Hello All
I am trying to convert the XML file into the text file, my XML file is of the following structure...
<root>
<data>
    <details>
    </details>
    <details>
    </details>
</data>
<data>
    <details>
    </details>
    <details>
    </details>
</data>
<trailer>
</trailer>
</root>
into the following flat structure
<data><details><details>---
<data><details><details>---
<trailer>
for this i have done the following content conversion settings
Recordset Structure: data,details,trailer
data.addHeaderLine           0
data.fieldFixedLengths       1,8,6,8,8,1,3
data.endSeparator            'nl'
details.addHeaderLine        0
details.fieldSeparator       ,
details.endSeparator         'nl'
trailer.addHeaderLine        0
trailer.fieldFixedLengths    1,3,6
trailer.endSeparator         'nl'
but actually i do not need the 'nl' for details.endSeparator, but i am not able to find out any other value which i could provide here, as default value is 'nl', i also do not want to "," for details.fieldseparatoe, but when i change this with fieldFixedLengths, i get the error
"Error: Message processing failed with java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value '015')', probably configuration error in file adapter (XML parser error)'"
kindly help me in finding out the mistake i am doing...
Regards
Dheeraj

hi Dheeraj,
I feel you handle this situation in mapping by creating the reciever structure similar to given below.
<root>
<data>
<field1/>
<detfield1/>
<detfield2/>
</data>
<trailer>
<count/>
</trailer>
<root>
<field1/> <detfield1/> <detfield2/> are at the same level children of <data>
Map the occurence of <data> element (target structure) per occurence of <data> element(sender XML structure)
By content conversion you will be able the desired output.
Now you have 2 record set structure
Data and trailer.
Hope it helps,
cheers,
Satish

File Content Conversion (FCC ) to IDoc Scenario

Hi All,
I have a Flat File to Idoc Scenario. Sample flat file looks as shown below.
A|20101001150207|SAPQMP|31|
B|5998|400858|2|N|20012010|MRGB0309S0030|
C|T0025|M0331||0.884||Inspection|1|No|Y||
C|T0001|M1556||Clear & bright ||QC|1|No|Y|Text|
C|T0050|M0341|6.0|6.5|7.0|QC|1|No|Y|Number|
C|T0010|M0360|0.279|0.341|QC|1|No|Y|Number|
C|T0062|M0360|0.112|0.137|QC|1|No|Y|Number|
C|T0056|M0373|7000|QC|1|No|Y|Number|
C|T0042|M0422|||-25|First Prod|1|No|N||
B|5998|400859|4|N|20012010|MRGB0309S0065|
C|T0025|M0331||0.896||Inspection|1|No|Y||
C|T0001|M1556||Clear & bright ||QC|1|No|Y|Text|
C|T0050|M0341|10.6|11.0|12.0|QC|1|No|Y|Number|
C|T0042|M0422|||-25|QC|1|No|Y||
C|T0010|M0360|0.279|0.341|QC|1|No|Y|Number|
B|5998|400859|4|N|20012010|MRGB0309S0065|
C|T0025|M0331||0.896||Inspection|1|No|Y||
C|T0001|M1556||Clear & bright ||QC|1|No|Y|Text|
C|T0050|M0341|10.6|11.0|12.0|QC|1|No|Y|Number|
Z|20101001150242|SAPQMP|31|
where Records A indicate File Header, Z indicates File Trailer
Recodrs B indicateds Material header and Would be repeating multiple times
No. of B Records = No. of Idocs generated with corresponding C records data which indicates Component Rows (multiple)
i.e as many B records file contains, that many Idoc will be created
For Mapping I require B and C Records. Field Separator is Pipe | symbol
I need to Ignore A B C Z
How to define the source structure and the respective FCC Parameters.
Regads,
Varun

Hi,
For Mapping I require B and C Records. Field Separator is Pipe | symbol
I need to Ignore A B C Z
two statements are ambiguous.
I assume u want only B and C records.
Since the structure is little complex, u can gat the whole record as a single element into Mapping and then u can take only those u want to access and map.
MT_Name
        Records
             Data(0..unbounded)
Now in Data u have all the records.
If you dont want at all these A and Z records to come to mapping(IE) then u need to go for a small adapter module.
Deploy it and use in the modules sequence...
Babu

Receiver File content conversion problem with newline separator

Hello Experts,
My scenario is IDOC To file..At output we are generating an csv file wherein we have got records in new line.
somethng like these..
ITEM1,ITEM2,ITEM3
ITEM1.ITEM2,ITEM3.
But when i open these csv file using notepad,we are getting records in same line.
i.e item1,item2,item3item1,item2,item3
Also we have specify in FCC,endseparator value as 'nl'
My target structure is somethng like these,
MT_PRODUCT_MASTER
   -Product master
      -item1
      -item2
Pleasee advise.

What is exactly parameter that you have set on channel?
endSeparator = 'nl'
NameA.endSeparator
If you enter a character string here, the system adds it to the last column as a closing character. You can also make this specification in addition to NameA.fieldFixedLengths. To include a line break following the closing character, you must explicitly define it by attaching ´nl´ (including the quotation marks) to the string.

Nested structur for receiver file content conversion

Hello all,
i have the following problem to set up a nested XML-structure to an flatfile.
XML-Structure:
LtcRecords (root)
   Header
   Deduction
   Trailer
Now i want to convert the Header,Deduction and Trailer values to an flatfile.
I tried it with a lot of possibilies. But without an result.
Recordset Structur: LtcRecords
LtcRecords.fieldNames: Header,Deduction,Trailer
Header.fieldFixedLengths: 1,10,5
Header.fieldNames:id,group_id,location_id
Deduction.fieldFixedLengths: 1,10,3
Deduction.fieldNames:id,group_id,product_code
Trailer.fieldFixedLengths: 1,10,5,3
Trailer.fieldNames:id,group_id,location_id,product_code
I hope somebody can help me with my wrong settings.
Many thanks
ilka
Attachments:
Source:
<?xml version="1.0" encoding="utf-8" ?>
<ns1:mt_Metlife0>
     <LtcRecords>
          <Header>
               <id>A</id>
                <group_id>0000700015</group_id>
               <location_id>00002</location_id>
          </Header>
          <Deduction>
               <id>D</id>
               <group_id>0000700015</group_id>
               <product_code>GPC</product_code>
          </Deduction>
          <Trailer>
               <id>Z</id>
               <group_id>0000700015</group_id>
               <location_id>00002</location_id>
               <product_code>GPC</product_code>
          </Trailer>
     </LtcRecords>
     <LtcRecords>
          <Header>
               <id>A</id>
               <group_id>0000700013</group_id>
               <location_id>00005</location_id>
          </Header>
          <Deduction>
               <id>D</id>
               <group_id>0000700013</group_id>
               <product_code>GPC</product_code>
          </Deduction>
          <Trailer>
               <id>Z</id>
               <group_id>0000700013</group_id>
               <location_id>00005</location_id>
               <product_code>GPC</product_code>
          </Trailer>
      </LtcRecords>
</ns1:mt_Metlife0>
Target:
A000070001500002
D0000700015GPC
Z000070001500002GPC
A000070001300005
D0000700013GPC
Z000070001300005GPC

Hi
I tried the same scenario successfully.
I had given the same input xml and got same output as u want.
The settings of my File Adapter is as follows:
Recordset Structure: LtcRecords,Header,Deduction,Trailer
Header.fieldFixedLengths: 1,10,5
Header.fieldNames:id,group_id,location_id
Deduction.fieldFixedLengths: 1,10,3
Deduction.fieldNames:id,group_id,product_code
Trailer.fieldFixedLengths: 1,10,5,3
Trailer.fieldNames:id,group_id,location_id,product_code
LtcRecord.fieldSeparator:'nl'
File Type: Text
File Encoding:UTF-8
Try with these settings u will definately get the output.
Regards
Arpit Seth

Receiver - File Content Conversion(FCC)

Similar Messages

Maybe you are looking for