cancel
Showing results for 
Search instead for 
Did you mean: 

BPC allocations automatically

Former Member
0 Kudos

Hi,

I have a requirement where figures need to be allocated automatically from account group/year to account/month. Also it should be possibble to user change figures in the account/month level manually and those changes should be reflected also to account group/year level.

I know that I can create script which would allocate values to account/month and other script which would sum up values from the account/month level to account group/year. Thing is that customer wants this to happen without the need to run packages. So basically this should all be done in default script. Problem is that if I make automatic allocation to account/month then it will overwrite the values which user has inputted to accounts. So I would need a way to tell default logic that in the case somebody has changed values in the account level, it won't run the allocation and instead it would run script which would sum up figures to account group level. I tried to utilize Audit ID's, but then input schedules would be quite problematic.

Any ideas?

Tommi

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member186338
Active Contributor
0 Kudos

Hi Tommi,

There is a problem with the logic in this scenario...

Let's check a simple case:

ACC_TOT (parent for ACC1..3)

     ACC1

     ACC2

     ACC3

ACC_TOT_BASE (base member to input total)

What logic you want to implement?

Example:

1. Enter 90 to ACC_TOT_BASE

2. Allocation to ACC1..3 each by 30 (OK, standard disaggregation)

3. ACC2 manually changed to 40

4. ACC_TOT_BASE to be adjusted to 100 ? (90 + 10)

5. ACC_TOT_BASE manually changed to 120

6. What do you want to have in ACC1..3???

Vadim

P.S. In most cases the assumption is simple - if ACC_TOT_BASE is manually changed then allocation has to be performed equally to ACC1..3

Former Member
0 Kudos

Hi,

ACC_TOT_BASE should be 100 after input 40 to ACC2.

First input 90 to ACC_TOT_BASE

Allocation to ACC1, ACC2 and ACC3

Result:

ACC_TOT_BASE = 90

ACC1 = 30

ACC2 = 30

ACC3 =30

User changes ACC2 to 40 -> system should automatically update ACC_TOT_BASE to 100

Result:

ACC_TOT_BASE = 100

ACC1 = 30

ACC2 = 40

ACC3 =30

Also I would like to know if there is a way to tell default logic that it should not run every time. Example there is allocation in default logic, which would allocate values to ACC1, ACC2 and ACC3. I want this to happen only once sence there is a possibility that user has modified data straight in the accounts. If allocation is done again, then it would overwrite user input.

Tommi

former_member186338
Active Contributor
0 Kudos

Hi Tommi,

You come only to step 4!

What happen if user perform step 5?

"Also I would like to know if there is a way to tell default logic that it should not run every time." - what do you mean by "not every time" How the system will differentiate the first run???? You will need to have some flag for each ACC_TOT_BASE intersection...

And if the user enter incorrect value into ACC_TOT_BASE - how to correct it?

Sorry, but you are trying to implement something logically contradictory...

Vadim

P.S.

In the real life it's better to segregate 2 processes:

1. Planning on the node level - with allocation launched by DM package (only once )

2. Planning on the base member level - just saving values, no script.