Mapping hierarchy structure to flat one

Hi,
I have incoming hierarchical structure:
Node(0...3)
Field1
Field2
Outcoming flat structure:
Field1 from Node no.1
Field2 from Node no.1
Field1 from Node no.2
Field2 from Node no.2
Field1 from Node no.3
Field2 from Node no.3
Have any idea how to do this.
Thanks,
Regards,
Natalia.

Hello,
You can try using the copyValue function and then specify the position to be copied e.g
Field1 --> removeContext --> copyValue[0] --> Node no. 1
Field2 --> removeContext --> copyValue[0] --> Node no. 1
Field1 --> removeContext --> copyValue[2] --> Node no. 3
Field2 --> removeContext --> copyValue[2] --> Node no. 3
Hope this helps,
Mark

Similar Messages

Conversion of hierarchy structure to flat structure

Hi Gurus,
I am mapping a multi node XML structure to flat structure to create the JDBC statements to Oracle database. I think JDBC DML statement can have only flat structure.
Now how to convert the incoming multi node xml file to several flat structures?
Can I map the multi node XML structure to jdbc structure?
Please help me this is critical.
Thanks
Kalyan

Chilla,
Thanks for the post. My source structure is as below. I have to map this one to flat structure for JDBC. For each customer_num, drop_point there are many customer brands. Now with the customer number and drop point, we have to create the flat structure for each customer brand.
<?xml version="1.0" encoding="UTF-8" ?>
<record>
<CUSTOMER_NUM>00140084000</CUSTOMER_NUM>
<DROP_POINT>00140084000</DROP_POINT>
<CUSTOMER_BRANDS>
       <BRAND_CODE>23258</BRAND_CODE>
       <BRAND_EFF_DATE>20060617</BRAND_EFF_DATE>
       <BRAND_CAN_DATE>99991231</BRAND_CAN_DATE>
       <FREIGHT_CODE>2</FREIGHT_CODE>
       <BRAND_STATUS>00</BRAND_STATUS>
       <INVOICE_UOM />
       <CREATION_DATE />
      <TRANS_LOCATION_CD>272</TRANS_LOCATION_CD>
      <TRANS_FAC_TYPE_CD>058</TRANS_FAC_TYPE_CD>
</CUSTOMER_BRANDS>
<CUSTOMER_BRANDS>
<BRAND_CODE>23265</BRAND_CODE>
<BRAND_EFF_DATE>20060617</BRAND_EFF_DATE>
<BRAND_CAN_DATE>99991231</BRAND_CAN_DATE>
<FREIGHT_CODE>2</FREIGHT_CODE>
<BRAND_STATUS>00</BRAND_STATUS>
<INVOICE_UOM />
<CREATION_DATE />
<TRANS_LOCATION_CD>272</TRANS_LOCATION_CD>
<TRANS_FAC_TYPE_CD>058</TRANS_FAC_TYPE_CD>
</CUSTOMER_BRANDS>
<CUSTOMER_BRANDS>
<BRAND_CODE>23365</BRAND_CODE>
<BRAND_EFF_DATE>20010901</BRAND_EFF_DATE>
<BRAND_CAN_DATE>99991231</BRAND_CAN_DATE>
<FREIGHT_CODE>2</FREIGHT_CODE>
<BRAND_STATUS>00</BRAND_STATUS>
<INVOICE_UOM />
<CREATION_DATE />
<TRANS_LOCATION_CD>272</TRANS_LOCATION_CD>
<TRANS_FAC_TYPE_CD>058</TRANS_FAC_TYPE_CD>
</CUSTOMER_BRANDS>
<CUSTOMER_BRANDS>
<BRAND_CODE>23531</BRAND_CODE>
<BRAND_EFF_DATE>20050210</BRAND_EFF_DATE>
<BRAND_CAN_DATE>99991231</BRAND_CAN_DATE>
<FREIGHT_CODE>2</FREIGHT_CODE>
<BRAND_STATUS>00</BRAND_STATUS>
<INVOICE_UOM />
<CREATION_DATE />
<TRANS_LOCATION_CD>272</TRANS_LOCATION_CD>
<TRANS_FAC_TYPE_CD>058</TRANS_FAC_TYPE_CD>
</CUSTOMER_BRANDS>
<CUSTOMER_BRANDS>
<BRAND_CODE>97335</BRAND_CODE>
<BRAND_EFF_DATE>20070217</BRAND_EFF_DATE>
<BRAND_CAN_DATE>99991231</BRAND_CAN_DATE>
<FREIGHT_CODE>3</FREIGHT_CODE>
<BRAND_STATUS>00</BRAND_STATUS>
<INVOICE_UOM>01</INVOICE_UOM>
<CREATION_DATE />
<TRANS_LOCATION_CD>420</TRANS_LOCATION_CD>
<TRANS_FAC_TYPE_CD>New</TRANS_FAC_TYPE_CD>
</CUSTOMER_BRANDS>
<CUSTOMER_BRANDS>
<BRAND_CODE>99448</BRAND_CODE>
<BRAND_EFF_DATE>20070217</BRAND_EFF_DATE>
<BRAND_CAN_DATE>99991231</BRAND_CAN_DATE>
<FREIGHT_CODE>3</FREIGHT_CODE>
<BRAND_STATUS>00</BRAND_STATUS>
<INVOICE_UOM>01</INVOICE_UOM>
<CREATION_DATE />
<TRANS_LOCATION_CD>4</TRANS_LOCATION_CD>
<TRANS_FAC_TYPE_CD>New</TRANS_FAC_TYPE_CD>
</CUSTOMER_BRANDS>
<CUSTOMER_BRANDS>
<BRAND_CODE>97337</BRAND_CODE>
<BRAND_EFF_DATE>20070217</BRAND_EFF_DATE>
<BRAND_CAN_DATE>99991231</BRAND_CAN_DATE>
<FREIGHT_CODE>3</FREIGHT_CODE>
<BRAND_STATUS>00</BRAND_STATUS>
<INVOICE_UOM>01</INVOICE_UOM>
<CREATION_DATE />
<TRANS_LOCATION_CD>4</TRANS_LOCATION_CD>
<TRANS_FAC_TYPE_CD>New</TRANS_FAC_TYPE_CD>
</CUSTOMER_BRANDS>
<CUSTOMER_BRANDS>
<BRAND_CODE>99471</BRAND_CODE>
<BRAND_EFF_DATE>20070217</BRAND_EFF_DATE>
<BRAND_CAN_DATE>99991231</BRAND_CAN_DATE>
<FREIGHT_CODE>3</FREIGHT_CODE>
<BRAND_STATUS>00</BRAND_STATUS>
<INVOICE_UOM>01</INVOICE_UOM>
<CREATION_DATE />
<TRANS_LOCATION_CD>12</TRANS_LOCATION_CD>
<TRANS_FAC_TYPE_CD>New</TRANS_FAC_TYPE_CD>
</CUSTOMER_BRANDS>
<CUSTOMER_BRANDS>
<BRAND_CODE>97234</BRAND_CODE>
<BRAND_EFF_DATE>20070217</BRAND_EFF_DATE>
<BRAND_CAN_DATE>99991231</BRAND_CAN_DATE>
<FREIGHT_CODE>3</FREIGHT_CODE>
<BRAND_STATUS>00</BRAND_STATUS>
<INVOICE_UOM>01</INVOICE_UOM>
<CREATION_DATE />
<TRANS_LOCATION_CD>11</TRANS_LOCATION_CD>
<TRANS_FAC_TYPE_CD>New</TRANS_FAC_TYPE_CD>
</CUSTOMER_BRANDS>
<CUSTOMER_BRANDS>
<BRAND_CODE>94771</BRAND_CODE>
<BRAND_EFF_DATE>20070217</BRAND_EFF_DATE>
<BRAND_CAN_DATE>99991231</BRAND_CAN_DATE>
<FREIGHT_CODE>3</FREIGHT_CODE>
<BRAND_STATUS>00</BRAND_STATUS>
<INVOICE_UOM>01</INVOICE_UOM>
<CREATION_DATE />
<TRANS_LOCATION_CD>120</TRANS_LOCATION_CD>
<TRANS_FAC_TYPE_CD>New</TRANS_FAC_TYPE_CD>
</CUSTOMER_BRANDS>
<SALES_TERMS_CODE />
<ACTION />
<REC_STATUS />
</record>

Problem Mapping Deep Structure to Flat Structure

Hello,
I hope someone can help me. My scenario is idoc to file. I am collecting many idocs with a bpm and writing them out to one file. My bpm is working great, but my mapping program is not working properly. My source message is a deep structure and my target message is a flat structure.
See my example message formats below.
Source message:
zmessage (1..1)
+zidocmessage (0..unbounded)
++zidoc       (1..1)
+++zidocheader (1..1)
++++zidocitem (0..unbounded)
Target Message:
zmessage (1..1)
+zfilemessage   (1..1)
++zfilefirstrec (1..1)
++zfileheader (1..unbounded)
++zfileitem   (1..unbounded)
I need to map zidocheader to zfileheader and zidocitem to zfileitem.
The Source Data:
<zmessage>
<zidocmessage>
    <zidoc>
      <zidocheader>
         <hfield1>hf1</hfield1>
         <hfield2>hf2</hfield2>
         <zidocitem>
           <ifield1>if1</ifield1>
           <ifield2>if2</ifield2>
         </zidocitem>
         <zidocitem>
           <ifield1>if1</ifield1>
           <ifield2>if2</ifield2>
         </zidocitem>
      </zidocheader>
    </idoc>
<zidocmessage>
    <zidoc>
      <zidocheader>
         <hfield1>hf1</hfield1>
         <hfield2>hf2</hfield2>
         <zidocitem>
           <ifield1>if1</ifield1>
           <ifield2>if2</ifield2>
         </zidocitem>
         <zidocitem>
           <ifield1>if1</ifield1>
           <ifield2>if2</ifield2>
         </zidocitem>
      </zidocheader>
    </idoc>
</zmessage>
The Target Data:
<zmessage>
<zfilemessage>
    <zfilefirstrec>
      <firstrecfield1>ff1</firstrecfield1>
      <firstrecfield2>ff2</firstrecfield2>
    </zfilefirstrec>
    <zfileheader>
      <hfield1>hf1</hfield1>
      <hfield2>hf2</hfield2>
    </zfileheader>
    <zfileitem>
       <ifield1>if1</ifield1>
       <ifield2>if2</ifield2>
    </zfileitem>
    <zfileitem>
       <ifield1>if1</ifield1>
       <ifield2>if2</ifield2>
    </zfileitem>
    <zfileheader>
      <hfield1>hf1</hfield1>
      <hfield2>hf2</hfield2>
    </zfileheader>
    <zfileitem>
      <ifield1>if1</ifield1>
      <ifield2>if2</ifield2>
    </zfileitem>
    <zfileitem>
       <ifield1>if1</ifield1>
       <ifield2>if2</ifield2>
    </zfileitem>
<zfilemessage>
</zmessage>
Can someone advise me on how to map this correctly?
Thank you,
Rhonda

Hello,
Can someone please help me with this problem?
I am at the point where all of the records in my source message are being written out, however, all of the header records are together and all of the line item records are together. So, the target message is not in the proper sequence. It should contain the header record, then item records, header record, then item records, etc.
Is there anyone that can help me with this issue?
Thank you,
Rhonda

Numbering nodes when loading hierarchy from a flat file.

Hi All,
I want to load a hierarchy from a flat file. When we number the nodes, do they have to be in a sequence or can I give them any number I want? I want to make the GL account number as the node number since it makes it easy to generate the node number that way. The way I see it, the important thing is the parent node number; so this approach should be fine. Please correct me if I am wrong.
Thanks,
Uday

Hi Uday,
   You need to have a running sequence numbers for Node Id field in the flat file. The file structure is as
NODEID IOBJNM      NODENAME TLEVEL LINK PARENTID
00000001 0GLACC     GL233344             00000001
00000002 0GLACC     GL435556             00000001
00000003 0GLACC     GL545666             00000001
00000004 0costcenter cc433232            00000002
00000005 0costcenter cc433233            00000002
00000006 0costcenter CC555551            00000003
The Parentid will calculated by the system automatically.
when you prepare you file csv please ensure that you have 8 characters for the Node ID " 00000003" other wise you will get error.
And if you want to add GL Account number to your hierarchy then you need to add GL A/c Number as external characteristics in hierarchy and add it to your flat file .
Hope it helps.
Cheers,
Balaji

Org unit Hierarchy structure between two Key date s

Hello Friends,
We have an issue with displaying HR Org unit hierarchy structure between two calendar months.
The BI Report has a selection parameter to select Org unit hierarchy , Calendar month From and Calendar month To
The BI Report is to display the no.of sick absence days for employees in a chosen Org unit hier.
Employee A had a sick absence of 5 days in the month 04.2011 in the Org unit X . The same employee had a sick absence of 4 days in 05.2011.The Org unit X then delimit in 05.2011 , the Org unit X is no longer in Org structure from 05.2011.
When we run the report for 04.2011 to 04.2011 , the employee A is showing absence under Correct Org unit ie X with correct Org structure .
When we run the Report for 05.2011 to 05.2011 , the employee A is showing absence under hierarchy Org unit Not assigned which is OK .
But the issue is when we run the Report from 04.2011 to 05.2011 , The employee A absence days 9 (5 +4 ) showing under Not assigned Org unit hierarchy structure which is the latest Org unit .
When I deactivate the Org unit hierarchy and choose tech name of Org unit , It is showing correct Org unit key
But The user would like to see 5 days under org unit X and 4 days under Not assigned with Correct Org unit hier structure when we run the Report from 04.2011 to 05..2011 .
We have a user Exit variable for the Key date in the Bex Report which seems to be taking only one date at any time .
Is there any way to get the correct figures under Org unit hier structure where employee had absence in when we put range of calendar months on a selection screen ?
Any advice appreciated.
Thanks.

Hi
Yes, we can display the same by using time dependent hierachy's i.e. your org is converted to time dependent so that respective employee shows with respective of time.
Regards
Jagadeesh.M

Org unit Hierarchy structure at Key date

Hello Friends,
We have an issue with displaying HR Org unit hierarchy structure between two calendar months.
The BI Report has a selection parameter to select Org unit hierarchy , Calendar month From and Calendar month To
The BI Report is to display the no.of sick absence days for employees in a chosen Org unit hier.
Employee A had a sick absence of 5 days in the month 04.2011 in the Org unit X . The same employee had a sick absence of 4 days in 05.2011.The Org unit X then delimit in 05.2011 , the Org unit X is no longer in Org structure from 05.2011.
When we run the report for 04.2011 to 04.2011 , the employee A is showing absence   under Correct Org unit ie X with correct Org structure .
When we run the Report for 05.2011 to 05.2011 , the employee A is showing absence under hierarchy Org unit Not assigned which is OK .
But the issue is when we run the Report from 04.2011 to 05.2011 , The employee A absence days 9 (5 +4 ) showing under Not assigned Org unit hierarchy structure which is the latest Org unit .
When I deactivate the Org unit hierarchy and choose tech name of Org unit , It is showing correct Org unit key
But The user would like to see 5 days under org unit X and 4 days under Not assigned with Correct Org unit hier structure when we run the Report from 04.2011 to 05..2011 .
We have a user Exit variable for the Key date in the Bex Report which seems to be taking only one date at any time .
Is there any way to get the correct figures under Org unit hier structure where employee had absence in when we put range of calendar months on a selection screen ?
Any advice appreciated.
Thanks.

Hi,
You can try adding two more attributes to Org Unit as "Calender month from" and "Calender month to".
In these attributes maintain the validity period for the corresponding master data.
For example, in your case you can maintain the master data as:
Employee | Org Unit | Calender month from |Calender month to | sick absence
A | X | 4.2011| 4.2011 | 5 days
A |    | 5.2011 | 05.2011 | 4 days
And in report use variables for Calender month from" and "Calender month to".
Hence, when user executes the report with selection as:
Calender month from" = 04.2011
"Calender month to"    = 05.2011
The data will be read from master data based on these selections along with key date and report will show output as expected.
Employee | Org Unit | Calender month from |Calender month to | sick absence
A | X | 4.2011| 4.2011 | 5 days
A |    | 5.2011 | 05.2011 | 4 days
Hope this works for you.
Regards,
Geetanjali

How to use File Adapter with hierarchial Structure?

Hi,
How to use File Adapter with hierarchial Structure like..
Data:
--Header Details:
Line Item Details:
Data
Bcoz I am getting a Flatfile in a hierarchial way as shown below.
Header Details :1
Line Item a
Line Item b
Header Details :2
Line Item c
Line Item d
Kishore

Hey Kishore,
In order to create a structure you need to use the file with convertion mode on the sending communication channel of the file adapter.
check the link for the needed configuration paramters.
If the structure is more complexed you can use the Contetnt master(CM) from itemfield which allows to ceate XML file from complex flat files and more.
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm">File sender adapter</a>
If you have any question i'll be more than happy to assist.
Nimrod Gisis

Hierarchy format in Flat file

Hi gurus,
      please tellme the Hierarchy format in Flat file.
           ThanQ.
   Regards,
   Ramesh.

Hi
1.Defining the source system from which you want to load data:
Create For a flat file, choose: File System, Manual Metadata; Data via File Interface.
2.Defining the InfoSource for which you want to load data:
Create Application Component.
Create InfoSource , Direct Update
Choose an InfoObject from the proposal list, and specify a name and a description.
3.Assigning the source system to the InfoSource
Assign Source System. You are taken automatically to the transfer structure maintenance.
The system automatically generates DataSources for the three different data types to which you can load data.
Attributes, Texts,Hierarchies (if the InfoObject has access to hierarchies)
The system automatically generates the transfer structure, the transfer rules, and the communication structure (for attributes and texts).
4.      Maintaining the transfer structure / transfer rules
Choose the DataSource to be able to upload hierarchies.
Idoc transfer method: The system automatically generates a proposal for the DataSource and the transfer structure. This consists of an entry for the InfoObject, for which hierarchies are loaded. With this transfer method, during loading, the structure is converted to the structure of the PSA, which affects performance.
PSA transfer method: The transfer methods and the communication structure are also generated here.
5.      Maintaining the hierarchy:
Choose Hierarchy Maintenance, and specify a technical name and a description of the hierarchy.
PSA Transfer Method: You have the option here to set the Remove Leaf Value and Node InfoObjects indicator. As a result, characteristic values are not transferred into the hierarchy fields NODENAME, LEAFFROM and LEAFTO as is normally the case, but in their own transfer structure fields. This option allows you to load characteristic values having a length greater than 32 characters.
Characteristic values with a length > 32 can be loaded into the PSA, but they cannot be updated in characteristics that have a length >32.
The node names for pure text nodes remain restricted to 32 characters in the hierarchy (0HIER_NODE characteristic).
The system automatically generates a table with the following hierarchy format (for sorted hierarchies without removed leaf values and node InfoObjects):
The system transfers the settings for the intervals and for time-dependency from the InfoObject maintenance. Depending on which settings you have defined in the InfoObject maintenance, further table fields can be generated from the system.
The valid from and valid to field is filled if you select Total Hierarchy Time-dependent in the InfoObject maintenance. The time-dependent indicator is activated if you select the Hierarchy Nodes Time-dependent option in the InfoObject maintenance.
6.      Save your entries.
Depending on which settings you defined in the InfoObject maintenance, additional fields can be generated from the system. Also note the detailed description for Structure of a Flat Hierarchy File for Loading via an IDoc and for Structure of a Flat Hierarchy File for Loading via a PSA.
Further Steps:
Maintaining InfoPackages
Result
You have uploaded the hierarchy data for the corresponding characteristic.

Error in the hierarchy structure - Data Load Failure

Hi
We are having a regular Master data hierarchy Full load: 0WBS_ELMT. This data load is from the SAP R/3 source system. It was failed today with following message:
Error in the hierarchy structure
Node ID 00016749 does not exist.
Node ID 00005867 starts an endless loop
Node ID 00001367 has not been included in the hierarchy
Can any one help me out to solve this issue?
Best Regards,
Venkata.

hi,
refer to this thread.
No hierarchy displaying in the Maintain Hierarchies

Hierarchy structure changes

Hi All,
I have one requirement at clent site where hierarchy structure changes i.e. parent child relation switches or changes from one level to another level. For example WBS element hierarchy stucture for project 101014 is:
101014--root
101014-1>101014-1-01>101014-1-01-02-->101014-1-01-02-01
after above hierarchy load to bw there are chances that hierarchy nodes change their positions.
i.e.above hierarchy node 101014-1-01 can be removed from parent(101014-1) and assigned to 101014-2.
In Next load Hierarchy need to realign/restructure according to new hierarchy tree from ECC system. Right now we are BW 7.30. Thanks for you help and gurantee of points.
Regards,
Reddy

Hi Gaurav,
Thanks for quick response, we are running process chain on daily basis which will trigger full load from ECC to BW. I thought the same but when I look below error message I think we need to some how delete hierarchy data and reload with restructed or realigned data. Please find below error details and once again thanks for your help.
Node ID 00001564 has not been included as a sibling node or as a child node
Message no. RH207
Diagnosis
The node with the ID 00001564 and the node name 101014-1-02-03 is not used as a child node (field CHILDID) or a sibling node (field NEXTID) by any node in the hierarchy. The node is also not a root node because the ID of the parent node 00001565 (field PARENTID) is not equal to 0. The node is therefore not linked into the hierarchy. Therefore the node is not connected to the hierarchy.
Procedure
This message is displayed in addition to message RH 242. The node is the root node of a subtree that is not connected to the hierarchy. For further details, see the long text for message RH 242.
4 of a total of 13,846 nodes are not included in the hierarchy
Message no. RH242
Diagnosis
The root nodes are the starting point for moving through the hierarchy. The content of the fields NEXTID and CHILDID is used to move from the current node to its sibling and child nodes.
4 out of a total of 13,846 nodes cannot be reached by moving through the hierarchy in this way. These 4 nodes are not connected to the hierarchy.
System Response
The hierarchy is not consistent and therefore cannot be activated.
Procedure
The cause of the problem is usually incorrect links to sibling nodes (field NEXTID) or child nodes (field CHILDID). An incorrect value often means that an entire subtree (consisting of several nodes) is not included in the hierarchy.
To simplify the search for incorrect links, the system identifies the nodes (from all the not connected nodes) that are not used as sibling nodes or as child nodes. These nodes are usually root nodes of subtrees that are not connected to the hierarchy. You can find these nodes in the RH 207 messages that follow.
Try to localize the problem by using the RH207 messages for help. If the hierarchy is loaded from an SAP source system, you can check whether the extracted data is correct by executing transaction RSA3 in the source system. If necessary, check if the data is modified with a user exit. If the hierarchy is loaded from a file, check the contents of this file. The problem might also be due to an error in the transfer rules or in the transformation.
Thanks
Reddy

How to create the Hierarchy Structure in BeX

Hi,
We have a cost center IOBJ MD, and our source system does not have the feasibility to create hierarchy to load it. But the business gave a hiearchy structure in flat file, and want to get the cost center hierarchy in bex.
How do we do that ? Please suggest.
Thanks
RK

Hi,
A hierarchy can be created in the system by two ways:
By hand:
     I would recomend to create by hand if the hierarchy has a few nodes or if the hierarchy will stay without changes for long.
     RSA1 --> Look for your infoobject and "create hierarchy". Then, you can create the folders and nodes that you need and dont forget activate it
This option is the quickest and easier, if you could go for it.
Loaded by flat file.
     If the hierarchy has many many nodes or if it will change its values quite often, it will be a good idea to develop stractors, infopackage and so on for loading the information from file file.
There are plenty of information of the Internet about how to do it.
From my own experience, it would be easier to build the extractor in the old version (rsa1old).
I hope that it helps!

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

Hierarchy using a flat file for a master data load.

Can anyone please tell me the steps involved in creating a hierarchy in BI 7.0. and loading the data using a flat file into the created hierarchy? I have seen some posts and weblogs but they were not helpful and i have been getting some errors which i dont know how to resolve.
Can someone please give a clear steps and procedure for this?
Thanks a lot in advance.
Naveen

Hi,
The flat file is generated in application server by executing an ABAP program in SE38.
This ABAP program contains the logic to generate hierarchy.
In our case we used a DSO to store employee & supervisors.
This program generated a flat file in tmp folder in application server
In our case, To load this flat file we created an Infosource on our master data using direct update using RSA1old Tcode
after Infosource is created right click on the InfoSource and click on Assign DataSource.
Give the Source System name
When you open this Info source you can select data source as YHIEROBJ_HIER and then activate the InfoSource.
create an Info Package to load the Hierarchy. Right click on the PC Files (Source System) and click on u201CCreate InfoPackage".
Under Extraction tab give the flat file name which is generated by the ABAP program in AL11.
Select the hierarchy which you want to load. Also, you can rename the Hierarchy after loading it. The update method is selected as u201CFull Updateu201D.
Logic for Generation of flat file & ABAP Program:
Flat file structure:
Node ID     InfoObject     NodeName     Parent ID     Date To      Date From     Language
u2022     u201CNode IDu201D indicates the unique number which defines the Node.
u2022     u201CInfoObject u201Cgives the name of the InfoObject which is assigned to this Node ID.
u2022     u201CNodeNameu201D is the name you specify to that Node.
u2022     u201CParent IDu201D is the Node ID to which the Current Node ID reports to.
u2022     u201CDate Tou201D and u201CDate Fromu201D are taken for time references (You can set them constant).
u2022      u201CLanguageu201C is set to English (E).
The program Logic can be :
Declare the hierarchy structure
Get the data from DSO into internal table
Read all the EMP values into NodeName Field of the table
Build lookup table for Parent Node ID
Fill Parent Node ID field
Append this data to work area & then to another internal table
You need to declare the selection parameter as SSFILE1
& use following code to write back the file
OPEN DATASET SSFILE1 FOR OUTPUT IN TEXT MODE ENCODING DEFAULT
     MESSAGE MSG.
IF SY-SUBRC NE 0.
    MESSAGE E008(ZBW1) WITH MSG.
ENDIF
Populate the output from that internal table into final work area.
Transfer this final work area to the ssfile1 which is the desired output file.
and   CLOSE DATASET SSFILE1.
When this program is executed, selection screen asks for the name of file
Enter the desired file name & execute
flat file would be generated in the Application server now.
To view the File, Go to Transaction AL11. Search the directory /tmp. Double click on this directory.
This opens the list of flat files under this directory. Double click on the file name.
Hope this helps.
Thanks,
Rashmi.

Creating hierarchy structure in excel

Hi,
Could someone help me in how to create a hierarchy structure in excel like defining
InfoObject X as Node 1
InfoObject Y as Node 2 and etc.
I have the excel file where we can create a structure but i lost that. if someone can send me a template i would really appreciate ur help.
Thanks,
pandu

Hi
If u need to create the structure
Go to the IS datasource
1)click the Heirarchy structute
and u can see the structure that is the right structure u need to have in the Flat file
Check this link also
http://help.sap.com/saphelp_nw04/helpdata/en/fa/e92637c2cbf357e10000009b38f936/content.htm
Hope it helps
regards
AK

Service hierarchy structure

Hi all,
We are upgrading from SRM 5 to SRM 7.0 EHP1 with ECS.
When a service shopping cart is created in SRM 5,a hiererachy structure is created for each item i.e. PARENT and then ITEM .
We want to create service carts and PO's w/o the hierarchy structure.Is that possible in SRM 7?
Pls advise.

Hi Ranjan,
I'm talking about service PO's which are created using the link "ORDER" in SHOP ONE screen.
WHen service PO's are created using this link,each service item has 2 nodes:
1 parent and other with the actiual item details.
E.g. SC with 2 items in SRM will actually have 4 line item structure. will also have the same structure.when the PO for this cart replicates to ECC,in ECC thre will be only 2 item structure.
Is there a way to create service PO's in SRM 5 and SRM 7 w/o the hierarchy structure?

Mapping hierarchy structure to flat one

Similar Messages

Maybe you are looking for