Value Driver Tree - Link driver node with hierarchy parent

[flacko]

Hello All,

After several tries, I post the issue I have faced while creating a Value Driver Tree in SAC.

I have a planning model with different accounts and hierarchy set for these accounts. I first created a driver tree, I changed Personnel Costs node to a YoY node and then added a new data source node (Personnel Costs Growth) which will be used as a driver for simulation. However, when setting the output from design panel,I am not able to link the created node to the parent node (Personnel Costs) but only to its children (Salaries, Wages, Bonus,..).

P.S: screenshots below to illustrate the example.

Could you please advise if there is any solution/workaround to link driver directly to Personnel Costs node instead of its children (Salaries, Wages,..)?

[sgodfree]

Hi Faicel,

In this case you would have to use the child as a proxy to represent the aggregated value, however I understand this is not exactly what you're looking for.

I'd suggest that you create an Influence item for this request, however any future enhancement support would not come to the classic VDT, but rather the story based VDT. We are expecting to have the ability to create YoY calculations within the modeler (which will emulate those currently using the original VDT) in the near future, afterwhich you maybe able to accomplish your specific scenario using the story based VDT.

Thanks,
Scott

[flacko]

Hi Scott,

Thanks for the feedback. Well noted on my side.

Best Regards

Faicel

[sgodfree]

Hi Faicel,

You will have to link the growth projection (YoY) to a leaf account (i.e. the target will have to a be a leaf). However if you do this, assuming the parent node (of the target specified in the YoY) is defined in the VDT, the nodes should link themselves in the calculation view.

Thanks,

Scott

[flacko]

Hi Scott,

Thanks for your helpful answer.

As per the requirement, users want to do simulation at the parent node level (Personnel Costs) as they have a large number of sub-accounts which complicates the task to simulate at this bottom level. In this case, is there any workaround to this?

Regards

Faicel