Page tree
Skip to end of metadata
Go to start of metadata

The BPC consolidation engine has a limitation: If there are two rule items, one item has the 'Periodic Calc' setting selected and the other one does not but both rule items have the exact same destination data region (i.e. destination account + destination flow), the result of both rule items will affect each other. This has been documented in SAP Knowledge Base Article 2217212. This article gives a simple example which causes a consolidation data issue. Note that some customers’ configuration is much more complicated than a simple example so it may be difficult for customers to identify if they are having the same issue.

This article proivdes a more complicated example and explains how it could affect the consolidation calculation result.

The "Eliminations and Adjustments Rule" detail table is configured below:

Notice that some rule items have the 'Periodic Calc' setting selected but the others do not. This satisfies the prerequisites of the issue so we should be careful about the destination data region.

Now look at the destination data region: All the destination group accounts are 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 of ‘ELIMACC’ of the source accounts. Refer to SAP KBA 2217652.

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

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’ set to be empty, which causes 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 and 1,110,000 for respective months. The snap shot for the same is provided below.

Snap shot for Feb-15 before Consolidation.

    Snap shot for Mar-15 before Consolidation

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 0 (zero).

Snap shot for Feb-15 After Consolidation.

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.

This is because of the limitation explained in 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.
  • No labels