How to maintain Hierarchy for non logical number ids in BPC

[Former Member]

Hello, i have  a dimension named 0ORGUNIT. The master data for that orgunit has been maintained in sequential order with many parent nodes in between. The list is big, and any time new number/ID can be added to any parent. The other part of this dimension is every parent has got data to be stored. As BPC cannot store parent data, all the members are taken as base level members

For Reporting purpose i need to show the same with parent and child relationships. How to handle this scenario?

Please find the sample hierarchy structure below.

ID	Description	PARENT
5000000	MD's office
5000001	CEO's office	5000000
5000221	Internal Audit	5000001
5000002	COO	5000000
5000222	Operations	5000002
5000223	Contact Center	5000222
5000224	Customer Service	5000222
5000225	Branch Operations	5000222

Regards

Praveen

[Former Member]

Praveen,

For the parent members on which you have to save the data concatenate them with _I or _D and make these base members whereas the ID with nos as parents. So in report you can show it with parent and child relation as well...

As in your case 500000_I - MD office inputable etc.

Regards,

JP

[Former Member]

Hi JP,

This seems fine with fixed set of parent members. But how can i identify (How to automize) the member 501000 which would come as parent tomorrow and create a dummy member for the same? The parent and child relation is created based on reporting designations. The parent and child relationships changes frequently.

regards

praveen

[Former Member]

The parent and child relation is created based on reporting designations

How?? How are they currently being maintained? In BW or in Excel? Are you loading the master data from BW?

If the parent and child relationship changes frequently....and you may also need to use Time dependent hierarchies!

Regards,

JP

[Former Member]

Hello JP,

They are being maintained in BW in 0ORGUNIT dimension.

Regards

Praveen

[Former Member]

So load the parent twice maybe....First load as it is with ID=ID and NODENAME=NODENAME. Load the normal heirarchy and for the dummy parent nodes....create a transformation file with only  NODENAME=NODENAME+STR(_I) and load. I haven't tested this......but try this way. If your gonna include this dummy member under the parent, you will have to do it manually.

Best way would be to include this on the BW side so that it is seamless. BW transformations are flexible. Also you have any option of Start or End Routine BADI in transformation file.

Regards,

JP

[Former Member]

Hi Praveen,

Probably the easiest way to implement this is END ROUTINE BADI. In that BADI you can read data from 0ORGUNIT and find out if a member is a node. Then add an _I member underneath.

The only concern I can see with your approach is that if you want to make a base member a node in the next load. You won't be able to do this if that base member has some transaction data.

Regards,

Gersh