Problem with File Content Conversion at Receiver end (nested structure)

[Former Member]

Hi All,

I have the below nested XML structure which I want to convert into a flat file(fixed length).

<ns1:MT_MaterialSales_File>(1:1)

<HEADER>..fields..</HEADER> (1:1)

<INVOICE_GROUPS> (1:unbounded)

<INVOICE_HEADER>..fields..</INVOICE_HEADER> (1:1)

<INVOICE_DETAILS>..fields..</INVOICE_DETAILS> (1:unbounded)

</INVOICE_GROUPS>

<FOOTER>..fields..</FOOTER> (1:1)

</ns1:MT_MaterialSales_File>

The desired output will be like this:

-

---

HEADER.......<fields of fixed length>

INVOICE_HEADER..INVOICE_DETAILS..

FOOTER...<fields of fixed length>

-

---

i.e all INVOICE_GROUPS are in a single line one after the other.

Can someone help me what parameters to use to get this done using FCC?

Thanks a lot

Rajeev

[Former Member · Accepted solution]

hi

how far i understand your stucture i think you cant go for FCC in receiver communication channel because FCC support upto 2level hierarchy. as you are having nested structure you can do your CC using conversion agent tool.

regards

Kasturika

[turmoll]

Hi,

Take a look at this document: [How To Handle Unstructured Source Content for Adapters|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/482aae19-0301-0010-3485-8efd618818d0] to read about the limitations and workarounds for file adapter.

Regards,

Jakub

[Former Member]

Hi,

It will not be possible to use FCC conversion for this. There are limitations of hirarchical structure upto max 2 levels for FCC conversion with File adapter.

refer

Converting File Content in the Receiver Adapter

http://help.sap.com/saphelp_nw70/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm

May be below links will help you on this

File Content Conversion for Unequal Number of Columns

/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns - FCC

Content Conversion (Pattern/Random content in input file)

/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file - FCC

/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario - FCC - MDM

Thanks

Swarup

[Former Member]

Hi Rajeev,

You can use the following content conversion parameters:

HEADER.endSeparator = 'nl';

INVOICE_GROUPS.fieldSeparator = '';

INVOICE_GROUPS.endSeparator = 'nl';

INVOICE_HEADER.endSeparator ='';

INVOICE_DETAILS.fieldSeparator ='';

INVOICE_DETAILS.endSeparator='';

FOOTER.endSeparator = 'nl';

Thanks,

Varun

[Former Member]

Hi Varun,

Thanks for your reply.

But i got the following error in the adapter:

Message processing failed. Cause: com.sap.aii.af.modules.conversion.xml2plain.ConversionException: The element nesting level for the structure INVOICE_GROUPS is too deep (reference: 3 levels, found: 4 levels) at XML element MT_MaterialSales_File,INVOICE_GROUPS,INVOICE_HEADER,RecTyp

Regards,

Rajeev

[Former Member]

Hi,

I am having a similar issue with nested structure. How did you work around this ???

[stefan_grube]

> I am having a similar issue with nested structure. How did you work around this ???

You find in online help a sample structure.

Adjust your message structure to this.