Hi guys,
need your help, please:
I was actually wondering i fit is possible to achieve the following scenario using a BPC 10.0 ‘Load Hierarchy’ Data Manager Package.
In fact, I would need you input in respect to the referenced transformation file.
Scenario:
A dimension got members that are structured through a PARENNTH1 hierarchy.
In order to allow planning and postings against parents, we run a Load Attribute Package, creating Base Members for all members where the condition property ‘CALC = Y’ applies.
The ID of these ‘new BAS is created based on the rule Concatenate ‘BM_’ & ID. That allows the derivation of the referenced Parent from the BM_ Base Member ID.
So far so good:
What we got after having created those BM_ Base Members is the following:
(Example)
Member | CALC | PARENTH1 |
TOP_NODE | Y |
|
A | Y | TOP_NODE |
A1 | Y | A |
A1.1 | N | A1 |
A1.2 | N | A1 |
A2 | Y | A |
A2.1 | N | A2 |
A2.2 | N | A2 |
BM_TOPNODE | N |
|
BM_A | N |
|
BM_A1 | N |
|
BM_A2 | N |
|
Now:
What I’d like to achieve is a somehow automated process, preferably featured by a BPC DMP,
publishing the referenced Parents as PARENTH1 in order for the BM_ Base Members to be integrated in the PARENTH1 hierarchy.
At the end, the hierarchy should structure / display as follows:
Member | CALC | PARENTH1 |
TOP_NODE | Y |
|
BM_TOPNODE | N | TOPNODE |
A | Y | TOP_NODE |
BM_A | N | A |
A1 | Y | A |
BM_A1 | N | A1 |
A1.1 | N | A1 |
A1.2 | N | A1 |
A2 | Y | A |
BM_A2 | N | A2 |
A2.1 | N | A2 |
A2.2 | N | A2 |
Of course I am aware of the option to publish these PARENTH1 entries manually via the Member Sheet Maintenance in the WebAmin.
However, due to customer’s requirements this would not be the preferred option.
Should anyone have come across this challenge himself or might have an inspiring idea of how to achieve the goal via an automated process,
your input would be highly appreciated!
Thanks heaps!
Claus