FCC: Substructure inside Substructure

[Former Member]

Hi all,

I am working on a POC which uses FCC. The expected XML file Structure at the Receiver side is:

<root>

. <substructureA>

<field1/>

<substructure1>

<field1/>

<field2/>

<\substructure1>

<substructure2>

<field1/>

<field2/>

<\substructure2>

<\substructureA>

<substructureB>

<substructure1>

<field1/>

<field2/>

<\substructure1>

<substructure2>

<field1/>

<field2/>

<\substructure2>

<\substructureB>

<\root>

Is it possible to perform the conversion by FCC? If Yes, how to specify the substructure inside a substructure in configuration?

Thanks

Chilanka

[Former Member · Accepted solution]

HI,

Please check your structure is it correct,

we can have the substructure in side another substructure ,

In general these type of file content conversion , we can specify like below

Record Structure : root,sunstructure1,occurences,substructure2,occurrences,substructure3,occur....

processing parameters ;

root.endseparator : 'nl'

structure1.fieldSeparator:,

structure1.fieldnames:give field names....

repeat the above for all substrucuters...

ingorerecordset : true

try

also see the below links

/people/shabarish.vijayakumar/blog/2006/04/03/xi-in-the-role-of-a-ftp

Regards

Chilla

[Former Member · Accepted solution]

Hi Chilla

I am expecting the output in the following structure. Is it possible to perform the conversion using FCC?

ROOT

substructure1

sub_substructure

FIELD

substructure2

sub_substructure

FIELD

Thanks

Chilanka

[former_member184619 · Accepted solution]

Hi

Just check this link...for

Content Conversion (Pattern/Random content in input file)

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

Reagrds

Sachin

[Former Member · Accepted solution]

Chilanka,

This nested conversion is currently not supported by Sender File adapter.

Regards,

Jai Shankar

[Former Member · Accepted solution]

Hi,

Jai Shankar,

I think the above requirement is for Receiver side , am i correct or not? For sender is different , you nend use another...

Now , in receiver side

Record structure :

ROOT,substructure1,sub_substructure,FIELD,*,substructure2,sub_substructure

<b>Here you have to use the above sustructure name,occurrences</b> if any fields are under that structure and the respective parent will more no of occurrences

In processing parameters

Root.endSaparator : 'nl'

substructure1.fieldNames : (give field names if available if not available then you no need to give these type parameters for that specified substructure)

See my above answer...

Regards

Chilla

[Former Member · Accepted solution]

Chilla,

Yep. It was at the receiver side. I dint get the requirement correctly.

But again, if you see the structure posted, it is of many level hierarchy and this has no proper sequence. Also, I beleive this is just a sample and at run time the hierarchy may be still complex and different from the structure shown here. So I dont think Content conversion will work here.

Regards,

Jai Shankar

[prabhu_s2]

u may also take a luk into this thread:

[prabhu_s2]

check this link for the req structure:

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