Hierarchy structure changes

[Former Member]

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

[Former Member]

Hi Vaishu,

I am in a very similar situation.Need your help with this.

I load R/3 hierarchy in BW. I need to change its structure to rearrange nodes in BW. You had similar kind of requirement. Would you please tell me how you handled this situation.

Thx,

-Su

[Former Member]

Hi,

Created OSS message and SAP team has created custom program to fix this issue.

[Former Member]

Can you please share the program on b.s.ramgarhiya@gmail.com? I shall be very thankful to you.

Thanks,

[Former Member]

Hi Kiran

Thanks for response. Source system is ECC and datasource is 0DPR_PROJECT_HIER. I have created 7.0 dataflow where infopackage loads data till PSA and used DTP to load Infoobject. And its daily load using process chain and both Infopackage & DTP are full loads. Infopackage works fine but when DTP gets triggered system throws above error message. And also one more strange thing RSA3 records doesnt match with PSA records. Even after full load. There are no routines between Datasource and Infoobject.

If there is no other option could you please let me know how to delete and reload data. As its hierarchy I am not clear on how to delete and load data.

Your help is greatly appreciated and thanks for all your valuable responses.

Regards,

Reddy

[former_member188080]

Hi,

There are few points

1. which source system this change has happened..so if it is possible to load the data through datasource ,loading should resolve your problem

every change at node level or assignment will reflect the changes in the hierarchy structure within BW side

2. Also you can make the changes by manually carrying out deletion

3. You can also carry out flat file data loads to make the correction..

Thanks and regards

Kiran

[Former Member]

Hi Naveen,

Thanks for your response. Can you please explain in detail about the settings at infopackage level. I think that if DSO/table key changes/deleted in source than we need to delete entire data and reload with new key else there will be duplicates. Similarly I guess there should be some option to delete entire hierarchy data and relaod with new structure. Please corect me if i am wrong.

Gurantee of points for valuable answers. Thanks for all your help.

Regards,

Reddy

[Former Member]

Hi,

Full update method i mentioned earlier will overwrite your old structure and replace with the newer hierarchy structure.

Pls read below txt from SAP about update options available in the InfoPackage:

Store Hierarchy as Subtree

There are three options for storing loaded hierarchies in the Business

Information Warehouse:

o Full Update:

The hierarchy is stored under the selected technical name. If a

hierarchy exists already in the BW it is overwritten.

o Subtree Insert:

The hierarchy is inserted as a subtree without deleting the nodes in

the original hierarchy. This means, among other things, that if you

insert a hierarchy as a subtree more than once, it appears in

duplicate in the target hierarchy (see below for details).

o Subtree Update:

The hierarchy is inserted as a subtree and all the nodes under the

interface node in the target hierarchy are deleted. Unlike a subtree

insert, the old subtree is replaced each time a new upload takes

place.

Hope this helps !

Thanks,

Naveen Rao Kattela

[Former Member]

Hi,

In the Infopackage you will find a setting for Hierarchy load behavior:

Choose full update for update method.

Also select auto activation flag for this hierarchy.

This way you will overwrite hierarchy in BW from R/3 system.

Hope this helps !

Thanks

Naveen Rao Kattela

[Former Member]

Hi All,

Any inputs on this. Because of this dependent loads also fail in production. Your help is greatly appreciated.

Thanks,

Reddy

[Former Member]

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

[former_member199691]

Load will take care of it automatically. You do not need to do anything specific.

Regards,

Gaurav