Financial Management Blogs by SAP
Get financial management insights from blog posts by SAP experts. Find and share tips on how to increase efficiency, reduce risk, and optimize working capital.
cancel
Showing results for 
Search instead for 
Did you mean: 

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 lower consolidation group need to reflected (consolidated) in the higher level group.


Following is an example:


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

TIME      GROUP     RPTCURRENCY    ENTITY  INONE CATEGORY  ACCOUNT AUDITID   SIGNDATA

2015.02  Group1        USD                       E100      I_NONE Acutal          A1000       Journal_M   1000

2015.02  Group2        USD                       E100      I_NONE Acutal          A2000       Journal_M   100

2015.02  Group3        USD                       E100     I_NONE Acutal           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  INONE CATEGORY   ACCOUNT    AUDITID     SIGNDATA


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


The question here is : When executing BPC consolidation business rule, 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 his functionality, there are some subsequent fixes in later SPs,refer to note 2073249,2098172 and KB 2163803.

Enjoy.

2 Comments