Quantcast
Channel: SCN : Document List - SAP Planning and Consolidation, version for SAP NetWeaver
Viewing all articles
Browse latest Browse all 192

A BPC consolidation limitation

$
0
0

BPC consolidation has a limitation: If there are two rule items, one item has 'periodic calc' selected and the other one doesn't and both rule items have the same destination data region (destination account+ destination flow), the result of both rule items will affect each other. This has been documented in SAP KBA 2217212.On this KBA,it gives a simple example which causes problem. But some customers’ configuration is much more complicated than the simple example so it causes difficulty to customers to identify if the problem they have is exact the same problem.

 

This article gives a more complicated example and explains how it affects calculation result.

 

In The elimination and adjustment rule ,detail table is configured as below:

1.png

We can see that some rule items have  'periodic calc' selected but the others don’t -this satisfys the prerequisite of the problem so we should be careful about the destination data region.

Let’s take a look at the destination data region: all the destination group account is set to be ‘PROP (ELIMACC)’ and the destination flow is empty. Therefore, when executing consolidation, BPC will search for those accounts which are maintained as the value of the property ‘ELIMACC’ of the source accounts. Refer to SAP KBA 2217652.

It will cause problem if account dimension is configured as below:

2.png

3.png

For account 2000004, it’s ‘TYPEELIM’ is set to ‘ELIM05’ and it’s ‘ELIMACC’ is set to be 99000050.

For account 22030001, it’s ‘TYPEELIM’ is set to ‘ELIM10’ and it’s ‘ELIMACC’ is set to be 99000050.

So the account 2000004 is found as the one of the source accounts of the rule item’ ELIM05’ and the account 22030001 is found as one of the source accounts of the rule item ‘ELIM10’.

For both source accounts, the account 99000050 is found as the destination group account. Since both rule items has the field ‘destination flow’ se to be empty, which cause the fact that the destination data region of both rule items duplicated.

This will cause a problem as below:

Account 22030001 data has been inputted for Audit ID INP002, for Feb-15 and Mar-15 with values 1,108,680 & 1,110,000 for respective months. The snap Shot for the same is provided below.

 

Snap shot for Feb-15 before Consolidation.

4.png

  Snap shot for Mar-15 before Consolidation.

5.png

After Consolidation, for the period Feb-15, the Clearing account 99000050 offsets the data for Account 22030001 in the AUDITID “ICO010” . The Below snap shot shows the value of ICO010 Audit adding to Zero.

 

Snap shot for Feb-15 after Consolidation.

6.png

After Consolidation, for the period Mar-15, the Clearing account 99000050 offsets the data for Account 22030001 in the AUDITID “ICO010”. But the Clearing Account is also showing the value that was cleared for the period Feb-15 for the account 99000050 for the value 1,108,680 which is incorrect. This value is actually being pulled from the previous month value for the Account 99000050.

 

Snap shot for Mar-15 After Consolidation.

7.png

This is because of the limitation explained this article.

 

To solve the issue, we have the options below:

1, Uncheck the ‘periodic calc’ option for both rules

2, Change the destination data region to be different.


Viewing all articles
Browse latest Browse all 192

Trending Articles