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

According to some customer’s business requirement, manual adjustments to automatic consolidation result is required. So they configure a ‘M’ type data source (audit ID) particularly for this and post journal entries by this data source to adjust the consolidation result.

In this scenario, there is a common requirement that manual entries posted at a lower consolidation group needs to be reflected (consolidated) in the higher level group.

Below is an example:

Group1 is the parent of Group2 and Group3.The manual adjustment in 2015,FEB is :

TIME       GROUP     RPTCURRENCY    ENTITY   IntCo CATEGORY   ACCOUNT    AUDITID      SIGNDATA

2015.02  Group1        USD                       E100      I_NONE Actual          A1000       Journal_M   1000

2015.02  Group2        USD                       E100      I_NONE Actual           A2000       Journal_M   100

2015.02  Group3        USD                       E100      I_NONE Actual           A3000       Journal_M   100

The customer expects the data of group2 and group3 to be consolidated to the group1 as below:

TIME          GROUP     RPTCURRENCY    ENTITY   IntCo CATEGORY   ACCOUNT AUDITID     SIGNDATA

2015.02  Group1        USD                       E100      I_NONE Actual          A1000       Journal_M          1000+100+100

The question here is : When executing the BPC consolidation business rules (Automatic Adjustments), it only takes care of the data source (Audit ID) whose type is set to be ‘A’.

How can this be achieved?

It is not well known that we can use the property ‘DATASRC_STAGE’ of the AUDITID (datasource) dimension to achieve this

Regarding how to make the configuration for this is not documented on SAP help. But this is introduced on SAP Note 2049932. This functionality is available since BPC 10 NW SP15.

Please note:for this functionality, there are some subsequent fixes in later service packs, please refer to SAP Notes 2073249, 2098172 and 2163803.

 

 

  • No labels