Account-based Calculation Rule different behaviour on BPC 10.1

[former_member690707]

Hello gurus,

we recently upgraded BPC from 10.0 to 10.1 sp20 and noticed a strange behaviour when using account-based calculation.

Application help for BPC 10.1 on this topic says "Account-based calculations read and aggregate the values posted to specific combinations of accounts, flow types, and audit members in order to post the aggregated amount under an alternate destination account, flow and audit member combination."

This was true for BPC 10.0: if we had a non existing (in the model) combination of source account-flow-audit, the rule simply did nothing to the destination. We assume that this was beacuse no posted values could be found.

Instead in BPC 10.1, if we use a non existing (in the model) combination of source account-flow-audit, the rule sets destination's value to 0, even if there are no posted values for that source.

Is this behaviour correct or is it a bug?

Is there any way to have these rules work again like in 10.0?

Thanks

[former_member186338]

Not sure about old behavior and unable to check it (don't have BPC 10).

You can try to recreate the old behavior using script logic addition...

[former_member186338]

Let's assume:

You have 2 accounts: ACC1 and ACC2

And the rule will aggregate both accounts to ACC3

If there is some value in ACC3 and ACC1 and ACC2 is empty to my mind it's correct to have the value in ACC3 to be replaced by zero.

[former_member690707]

Hi Vadim, thanks for the answer.

I also think that this may be correct. In our situation the problem is that before the upgrade, if ACC1 and ACC2 were empty (no records at all in the model) ACC3 was left untouched. Since we have some rules that rely on this behaviour, we wanted to investigate the matter before changing them.