Contet Conversion for multilevel hierarchy structure

Hi,
I wanted to create csv file as a output for the structure
GROUP1                     1-1
      ITEM1
      ITEM2
GROUP2                      1 - unbounded
     ITEM3
     ITEM4
     GROUP3                 1-10
          ITEM5
          ITEM6
but i see only one level content conversion is possible. Does anyone worked such kind of scenario ?
Laks

Hi Lakshmi,
Few questions on the structure..Is it like thsi
GROUP1 1-1
-ITEM1
-ITEM2
--GROUP2 1 - unbounded
---ITEM3
---ITEM4
---GROUP3 1-10
-----ITEM5
-----ITEM6
means group3 is withing group2 and so item5 and item6 becomes 4th level in hierarchy
FCC is possible till 3 levels and hence in your case the normal FCC will not work.. I will suggest you to look into this link and do some workaround like that mentioned in the blog
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3414700%29ID1981012450DB01072979760660502867End?blog=/pub/wlg/7154
Also You want Group1, Group2 etc to be written in th output file? Then you need to have them in a field of target structure (so possible need to put one more node at each level viz Group1, 2 and 3 which will have the name of the group).
Regards
Suraj

Similar Messages

Content conversion for multilevel varying structure File to Idoc

Hi All,
I have following file structure.
VO
C1
S1 1 to unbounded
     H1 1 to unbounded
          D1 0 to unbounded
          D2 0 to unbounded
          U2 0 to unbounded
          UC 0 to unbounded
My Idoc structure.
ISU_EL34
     IDOC 0 to unbounded
          E1ISU34 1 to unbounded
               ZSEGMENT 0 to 1
I have applied the content conversion for the length specific file as follows.
Recordset structure: VO,1,C1,1,S1,1,H1,1,D1,,D2,,U2,,UC,
Do I need to do any changes over here to satisfy the above file structure.
V0 and C1 occurs only once in a file.
for S1 I should have H1 compulsory and others are optional, but i need to create Idoc when D1 data is available only.
I'm able to read the total file with the above content conversion.
MY requirements:
1) I need to create the Idoc based on the occurance of D1 node. I'm using H1 data also in the idoc not S1.
2) My doubt is whether the content conversion I have provide is applicable to the structure I have prepared.
3) When I'm trying useOneAsMany function for the above ie H1 data should repeat in Idoc as and when D1 repeats.I'm failing the error is both queues are not contain same number of data..
Could anyone suggest how I should approach for the above scenario.

Hi Sravya,
It is really helpfull answer , Thanks for sharing my problem .
It worked for this purpose, but I'm facing following problems
MY scenario
The file contains records V0,C1,S1,H1,D1,D2,U2 and Uc
In which Im using the data of H1,D1,D2,U2 and UC for creating target Idoc.
Every H1 contains at least 1 D1 record, If D1 exists D2 ,U2 and UC may or may not exist.If exists those are in a sequence and should consider the data of them to create Idoc.
Idoc should be created for every D1.
Problem facing:
Do we have any mechanism to group the D1 records to the relevant header.since Im unable do this with content conversion.
I think bcz of above problem; some records (D2 & U2 & UC) data is populating in Idoc even there is no D2,U2 and Ucs.
Thanks,
venu.

Unable to configure file adapter using FCC for Multilevel hierarchy

Hi Experts,
Can anyone help me in configuring the Receiver file adapter with FCC for the structure given below
<Root>
<Level1>
     <Ele1>
     <Ele2>
     <Level2>
            <Ele2_1>
            <Ele2_2>
            <Level2a>
                    <Ele2a_1>
                    <Ele2a_2>
            </Level2a>
     </Level2>
</Level1>

Hi dineshmale,
I have do this Multilevel hierarchy before. FCC can directly configure this scenario. But I don't know you output format. What my format shown below(here i use '#' instead of space):
Level1_Field1##Level1_Field2##Level1_Field3##Level2_Field1##Level2_Field2##Level3_Field1##Level1_Field2
#################################################################Level3_Field1##Level1_Field2
#######################################Level2_Field1##Level2_Field2##Level3_Field1##Level1_Field2
#################################################################Level3_Field1##Level1_Field2
Level1_Field1##Level1_Field2##Level1_Field3##Level2_Field1##Level2_Field2##Level3_Field1##Level1_Field2
#################################################################Level3_Field1##Level1_Field2
#######################################Level2_Field1##Level2_Field2##Level3_Field1##Level1_Field2
#################################################################Level3_Field1##Level1_Field2
#################################################################Level3_Field1##Level1_Field2
FCC Parameter:
Recordset Structure: Level1,Level2,Level3
Level1.fieldSeparator = (2 spaces)
Level2.beginSeparator = (some spaces according to the length of the fields in Level1)
Level2.fieldSeparator = (2 spaces)
Level3.beginSeparator = (some spaces according to the length of the fields in Level1and Level2)
Level3.fieldSeparator = (2 spaces)
Level3.endSeparator = \n
There are some points:
1. the endSeparator for Level1 and Level2 doesn't work.
2. the first begin separator in Level2 and Level3 doesn't work.
3. The last field of super node and the first field of child node is separated by the (child).fieldSeparator.
4. ....
What's more, I have write a blog of FCC For Hierarchical Structure in Receiver Channel just now. So it need two days for Approval. Let me know for any issues.
Edited by: guKidd on Dec 14, 2010 7:52 AM
Edited by: guKidd on Dec 14, 2010 7:54 AM

FCC Configuration for Multilevel Hierarchy

Hello Everyone,
I have a problem with FCC in sender side.
I have a multilevel nested structure shown below:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_XX__OB xmlns:ns0="http://xx.com">
   <Record1>
      <X/>
      <Record2>
         <A/>
         <B/>
         <C/>
         <D/>
         <E/>
      </Record2>
   </Record1>
</ns0:MT_XX_OB>
However I couldn't implement Record2 with FCC.Because,Lower subelement Record2 and Its elemnts weren't determined with FCC(with .fixedLenght).Furthermore,Data doesn't include keyfields.So,I couldn't use .keyfield.Can you help me please about this problem?
Thnx..

Hello Hareen,
Thanks your reply.
But,I need a solution in fcc side when retrieving data from text for multivel structure.Is it possible or not?I need fcc parameters for creating multilevel structure.
RECORD1
     -->PARTNR
     -->RECORD2
          --->matnr
          --->idnrk
          --->menge

File Content Conversion for Multi Hierarchical Structure for Sender Adapter

Hi Gurus,
My text file is coming as
Header,filed1,field2(Occurrence=1)
Content,field3,field4(Occurrence =1-Unbounded)
Detail,field4,field5(Occurrence = 1-unbounded)
Trailer,fieldN(Occurrence=1)
My requirement is to write a file content conversion, so that, in the resultant XML Structure the Detail will come under Content.
I have defined the Record Set Structure as
Header,1,Content,*,Detail,*,Trailer,1
But after FCC, the Detailed record is coming in the same level as the Content Record. But the business requires that, the Detailed Record should come under Content Record, so that they can correlate.
Could any one advise?
Regards,
SS
Edited by: Subhendu Sahu on Jun 17, 2011 4:43 PM

Hi,
Please use the below parameters -
○       NameA.keyFieldValue
Specify the value of the key field for the structure.
This entry is mandatory if the key field name is set. Otherwise, the entry is ignored.
NameA.keyFieldInStructure
■       If the key field of the substructure is to be added to the XML document, enter add. This is the default.
■       If the key field is to be ignored, enter ignore.
http://help.sap.com/saphelp_nwpi711/helpdata/en/44/6713ec3f914ddee10000000a1553f7/frameset.htm
cheers,
Sunil

File content conversion for receiver file structure(fixed length)

Hi Experts,
I am tryinng reciver file FCC for the following strcuture. it seems I have done some wrong configuration,and failing at conversion level. so experts please help me to get the correct content conversion parameters.
note : ( * Nothing can be altered at repository side * ) and the fields are fixed in length so the file needs to be fixed lentgh format.
Tree--Occ--
TYPE
SBLSALDATA--1..1--
SBLSALDATA
SALDATA----
1..1
Headrec----
1..1
XXX----
1..1
XXX----
1..1
XXX----
1..1
TotalDatarec----
1..Unbounded
YYY----
1..1
YYY----
1..1
YYY----
1..1
YYY----
1..1
LASTREC----
1..1
ZZZ----
1..1
ZZZ----
1..1
Thanks in advance.

I have done in the same procedure as in above link. its not working either.
My receiver structure looks like below.
<?xml version="1.0" encoding="UTF-8"?>
<ns1:TaxData xmlns:ns1="urn:XXXXXXXX">
<EmpTaxDat>
<Header>
   <A/>
   <B/>
   <c/>
</Header>
<Detail>
   <D/>
   <e/>
   <f/>
</Detail>
<Trail>
   <g/>
   <h/>
   <i/>
</Trail>
</EmpTaxDat>
</ns1:TaxData>
Edited by: Harish.k on Jan 2, 2010 2:15 PM

Hierarchy on file content conversion for receiver?

Y'all,
I'm stuck in this problem and I haven't find a solution to solved it... so, all your clues and reply's are really appreciate...
The basic problem is a File content conversion for a receiver C.C. that is not working and it's raising some errors in the RWB, I have gone thru some blogs but I still having a lot of doubts...
I want to produce a flat TXT file that will have a line for every node or subnode, it doesn't matter if it's not represented as hierarchical structure like this one... but the records must be produced or written in the same order...
Man_Del_Header as main node with Man_Header, Delete_Detail and Trailer as subnodes...
<?xml version="1.0" encoding="UTF-8"?>
<ns1:MT_DISTRIBUTOR_DELETE xmlns:ns1="http://xxx.com/xi/POSout">
   <Man_Del_Header>
      <MD_Header>|HM|1|</MD_Header>
      <MD_StoreNumber>051</MD_StoreNumber>
      <MD_filler1>|2|0000|3|</MD_filler1>
      <MD_EffDate>09/17/07</MD_EffDate>
      <MD_filler2>|4|005|5|dsdvnd|7|</MD_filler2>
      <MD_BatchNumber>500</MD_BatchNumber>
      <MD_fiiller3>|8|</MD_fiiller3>
      <MD_BatchDescr>DELETE PREV CST BTCH</MD_BatchDescr>
      <MD_filler4>|10|D|</MD_filler4>
      <MD_linef>1</MD_linef>
      <Man_Header>
         <Man_Header>|HM|1|</Man_Header>
         <Man_StoreNumber>051</Man_StoreNumber>
         <Man_filler1>|2|0000|3|</Man_filler1>
         <Man_EffDate>09/17/07</Man_EffDate>
         <Man_filler2>|4|005|5|dsdvnd|7|</Man_filler2>
         <Man_BatchNumber>500</Man_BatchNumber>
         <Man_filler3>|8|</Man_filler3>
         <Man_BatchDescription>Delete Distributor</Man_BatchDescription>
         <Man_filler4>|</Man_filler4>
         <Man_linef>Constant</Man_linef>
      </Man_Header>
      <Delete_Detail>
         <Delete_Detail>|D|901|170|</Delete_Detail>
         <Delete_DistribNumber>0000005010</Delete_DistribNumber>
         <filler9>|</filler9>
         <delete_linef>1</delete_linef>
      </Delete_Detail>
      <Delete_Detail>
         <Delete_Detail>|D|901|170|</Delete_Detail>
         <Delete_DistribNumber>0000005011</Delete_DistribNumber>
         <filler9>|</filler9>
         <delete_linef>1</delete_linef>
      </Delete_Detail>
      <Trailer>
         <Trailer>|T|1|</Trailer>
         <TotalRecCnt>00005</TotalRecCnt>
         <filler1>|2|</filler1>
         <NoOfHeaders>00002</NoOfHeaders>
         <filler2>|3|</filler2>
         <NoOfAdds>00000</NoOfAdds>
         <filler3>|4|</filler3>
         <NoOfChanges>00000</NoOfChanges>
         <filler4>|5|</filler4>
         <NoOfDeletes>00002</NoOfDeletes>
         <filler5>|13|</filler5>
         <NoOfSubstitution>00000</NoOfSubstitution>
         <filler6>|</filler6>
         <linef>1</linef>
      </Trailer>
   </Man_Del_Header>
   <Man_Del_Header>
      <MD_Header>|HM|1|</MD_Header>
      <MD_StoreNumber>061</MD_StoreNumber>
      <MD_filler1>|2|0000|3|</MD_filler1>
      <MD_EffDate>09/17/07</MD_EffDate>
      <MD_filler2>|4|005|5|dsdvnd|7|</MD_filler2>
      <MD_BatchNumber>500</MD_BatchNumber>
      <MD_fiiller3>|8|</MD_fiiller3>
      <MD_BatchDescr>DELETE PREV CST BTCH</MD_BatchDescr>
      <MD_filler4>|10|D|</MD_filler4>
      <MD_linef>1</MD_linef>
      <Man_Header>
         <Man_Header>|HM|1|</Man_Header>
         <Man_StoreNumber>061</Man_StoreNumber>
         <Man_filler1>|2|0000|3|</Man_filler1>
         <Man_EffDate>09/17/07</Man_EffDate>
         <Man_filler2>|4|005|5|dsdvnd|7|</Man_filler2>
         <Man_BatchNumber>500</Man_BatchNumber>
         <Man_filler3>|8|</Man_filler3>
         <Man_BatchDescription>Delete Distributor</Man_BatchDescription>
         <Man_filler4>|</Man_filler4>
         <Man_linef>Constant</Man_linef>
      </Man_Header>
      <Delete_Detail>
         <Delete_Detail>|D|901|170|</Delete_Detail>
         <Delete_DistribNumber>0000005012</Delete_DistribNumber>
         <filler9>|</filler9>
         <delete_linef>1</delete_linef>
      </Delete_Detail>
      <Delete_Detail>
         <Delete_Detail>|D|901|170|</Delete_Detail>
         <Delete_DistribNumber>0000005013</Delete_DistribNumber>
         <filler9>|</filler9>
         <delete_linef>1</delete_linef>
      </Delete_Detail>
      <Delete_Detail>
         <Delete_Detail>|D|901|170|</Delete_Detail>
         <Delete_DistribNumber>0000005014</Delete_DistribNumber>
         <filler9>|</filler9>
         <delete_linef>1</delete_linef>
      </Delete_Detail>
      <Trailer>
         <Trailer>|T|1|</Trailer>
         <TotalRecCnt>00006</TotalRecCnt>
         <filler1>|2|</filler1>
         <NoOfHeaders>00002</NoOfHeaders>
         <filler2>|3|</filler2>
         <NoOfAdds>00000</NoOfAdds>
         <filler3>|4|</filler3>
         <NoOfChanges>00000</NoOfChanges>
         <filler4>|5|</filler4>
         <NoOfDeletes>00003</NoOfDeletes>
         <filler5>|13|</filler5>
         <NoOfSubstitution>00000</NoOfSubstitution>
         <filler6>|</filler6>
         <linef>1</linef>
      </Trailer>
   </Man_Del_Header>
</ns1:MT_DISTRIBUTOR_DELETE>
|HM|1|051|2|0000|3|09/17/07|4|005|5|dsdvnd|7|500|8|DELETE PREV CST BTCH|10|D|1
|HM|1|051|2|0000|3|09/17/07|4|005|5|dsdvnd|7|500|8|Delete Distributor|Constant
|D|901|170|0000005010|1
|D|901|170|0000005011|1
|T|1|00005|2|00002|3|00000|4|00000|5|00002|13|00000|1
|HM|1|061|2|0000|3|09/17/07|4|005|5|dsdvnd|7|500|8|DELETE PREV CST BTCH|10|D|1
|HM|1|061|2|0000|3|09/17/07|4|005|5|dsdvnd|7|500|8|Delete Distributor|Constant
|D|901|170|0000005012|1
|D|901|170|0000005013|1
|D|901|170|0000005014|1
|T|1|00006|2|00002|3|00000|4|00000|5|00003|13|00000|1
So as you can see, i wanna produce a flat file that will have line or record for each node, it doesn't matter that it has a hierarchy or a deeper level, it should be a simple flat file...
The thing is that i have been trying to setup the receiver comm. channel and it's raising some errors like Could not process due to error:
<i>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 'XXXX')', probably configuration error in file adapter (XML parser error)'</i>
I have checked this blog:
/people/karthiknarayan.kesavan2/blog/2007/08/22/file-content-conversion-for-multi-hierarchical-structure
Unfortunately i don't know if there's another way to achieve this...

Jerry,
it easy if you go with multi mapping concept and without BPM if you are above >XI3.0 SP14.and use Append mode in the receiver file adapter.
just create the target structure like root under that Man_Del_Header,Man_Header,Detail,Trailer at the same level but got be careful with occurences.
<b>Source:</b>
I think from your structure you have
Man_Del_Header (1-unb)
Man_Header   (1-1)
detail   (0-unb ) may be (1-unb)
trailer (1-1)
create <b>target DT</b> like:
ROOT
..Man_Del_Header (1-1)
..Man_Header   (1-1)
..detail   (0-unb ) may be (1-unb)
..trailer (1-1)
all are at same level under ROOT.
create MT,MI,MM,IM.
in MM just map correspoding fields and if you have any unbounded onces map the nodes too. and map Man_Del_Header in the source to MT_XYZ (important)
and in the MM go to MESSAGES tab and change the occurences of the target Message to 0-unbounded same way in the interface mapping 0-unbounded.
here it create anothe extra node in the mapping something like Message1,this is ok.
and in ID just create all other objects like as usual except creating Interface determination ,in that select the extended radio button.
in reciever File CC use FCC ,would be very simple in the recordsetstrcture give
your four nodes Man_Del_Header,Man_Header,Detail,Trailer.
and use either fixed or field seperator.use append mode in recv File CC otherwise it will generate files as many occurences your source "Man_Del_Header" has ,cos we are mapping it to the MT--xyz .
thats it you are ready to go...
if any error post back here again.
you can make use of this thread
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible (here there are two target DT ,but you just create one DT,remaining are similar)
good luck.
Babu

Query on Content conversion for Receiver SFTP Adapter

Hi Experts,
We have the receiver structre as follows:
<DT_Receiever>
<Header>
<field1>abc<\field1>
<field2>1234<\field2>
<\Header>
<Detail>
<field3>nhj<\field3>
<field4>bshsrt<\field4>
<\Detail>
<\DT_Receiever>
We should do content conversion for the above structure using SFTP adapter at the receiver end.
Kindly provide us some tips in achieving the same.
Thanks
Suganya.

Hi Suganya,
You can use message tranform bean for ur case.
U have to use "StructXML2Plain"
Please follow below link for ur reference If you face any problem please let me know....
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
Thanks,
Enivass

How to use content conversion for Complex structure

Hi All,
I want to know how to use content conversion for the following complex structure:
Data
...Details            1 to Unbound
.....Header           1 to 1
.......HF1
.......HF2
.......HF3
.......ITEM           1 to unbound
.........ITF1
.........ITF2
all are of type string.
Thanks & Regards,
Viswanath
Message was edited by: Viswanath Mente

Hi,
In the content conversion,
give ur
1.document name as message type
2.give ur recordstructure as Details,,Header,1,ITEM,
3.mention ur keyfield.
conversion parameter
Header.fieldFixedLength - give the field lengths
Header.fieldNames=mention all the field name
Header.keyField=enter the value of keyfield
Header.endSeparator='nl'
repeat the same for Item
regards
jithesh

Can we use content conversion for this structure

Hi,
could any one help me on this
MT_Type
   Segment(0-unbounded)
        field1
        field2
        field3
        Segment 2(0-unbounded)
             field1
             field2
        Segment 3(0-unbounded)
             field1
             field2
thanks in advance

Hi Avinash,
is this possible by using the Message Transformation Bean for the folowing structure
MT_Type
     Segment 1
          Segment2
               field 1
               field2
               Segment3
                      field1
                      field2
Is there possibilty to do it by FCC. If not which ll suit better
thanks for your response

Report designer error for hierarchial structure on Columns

Hello,
I have a query with a structure in rows and another one in columns. I also have a 0COMPANY hierarchy Dimension within the Columns.
When I insert the data provider into a report designer report, I receive the following error:
"Query contains a hierarchial structure on Column(s)..."
Has any one encountered this issue before? Is there a note or workaround available?
Thank you.
Sri Yalla

Hi,
the report designer need to have a fixed number of columns. If you have a Hierarchical Structure in the Columns, the number of columns can change. Therefore Report designer does not allow to use this DP in this drill down. You should place the Row structure to the columns and the hier-structure to the rows. then it should work.
best regards,
kai

RFC with Multilevel Hierarchy call from Server Proxy

Dear Experts,
We would like to call BAPI inside a server proxy.
PI has created an interface structure exactly identical as the BAPI structure, but while generating ABAP proxy, system has added additional controller structure for each hierarchy.
Now our ABAP team is facing the difficulty to map Proxy structure with BAPI Structure as now the structures are not identical any more due to control structure .
Also since the BAPI has multilevel hierarchy and to fill the bapi structure from proxy structure (which is having the same structure as bapi but with control records) there are lots of loops required.
Please share your thoughts on how to get rid of looping on proxy structure when both the structure are identical but only control structure has been added to proxy structure.
Also would like to know if we can restrict the control structure generation during proxy generation process.
- Shri

Yes, you have to read and map the abap proxy structure to bapi structure.
Take a look here:
http://help.sap.com/saphelp_nw04/helpdata/en/ab/585f3c482a7331e10000000a114084/content.htm

What are the special conversions for time in update rules?

What are the special conversions for time in update rules?

Hello,
Special conversions for time in update rules are automatically conversion rules.
Example: If the cube contains calendar month and your transfer structure contains date, the date to month is converted automatically.
Assign points if this helps,
Regards,
Jorge Diogo

RFC 2 FLAT "Conversion configuration error: Unknown structure" MessageTrans

Hello all,
I want to use MessageTransformBean to map an RFC Call to a FlatFile in Receiver Adapter. As it is not FTP I can't use FCC.
Everytime I start the processing I get the error:
com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Z_FUNCTION' found in document', probably configuration error in file adapter (XML parser error)''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:Z_FUNCTION' found in document', probably configuration error in file adapter (XML parser error)'
I implemented everything according to [this|http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm] guide (complex conversion for receiver cc).
I also tried to map the RFC to another XML structure, but the error was the same?
Any ideas?
Best regards,
David

You can probably find answers in these threads:
Error in Receiver FCC: Unknown structure ... found in document
Unknown structure 'ns0:MT_dbglgtr_FileName' found in document'
Error in reciever file content conversion
Regards,
Ravi

'Conversion configuration error: Unknown structure

Hi, my scenario is very simple, Proxy->PI->File and there is no mapping.
There is a report that sends all the data to PI with the proxy and that works OK, but when the file adapter must generate the file I get the following error:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'n:WU_MT_BP' found in document', probably configuration error in file adapter (XML parser error)'
The XML can't be wrong because the MT of the proxy service interface is the same that the MT of the file interface.
In the file content conversion I specified all the structures, with fieldFixedLenghts parameter and endSeparator = 'nl'... I checked those parameters too and they look OK too...

>>Unknown structure 'n:WU_MT_BP
This looks clearly like a content conversion issue.
In file content conversion for recordset structure,have you specified WU_MT_BP?
Is this tag required or it shouldn't be coming in payload in first place.
It is possible that the occurrence of this tag is optional and you may be specified/not-specified content conversion parameters for it.
Thanks
Aamir

Contet Conversion for multilevel hierarchy structure

Similar Messages

Maybe you are looking for