Some customers do not know that when the BPC consolidation package is executed, an automatic ‘copy opening’ will be done. Some customers might have known about this but they are not sure about the detailed process.
Because of this, many customers have doubt about the data after they executed the consolidation data package, especially when ‘copying opening’ is taken into consideration.
This article explains the detailed process .
An automatic ‘copy opening’ for data in AuditID (Datasource type) of type ‘A’ will be executed during consolidation run (either through a BPC data manager package or through the consolidation monitor).
In fact it is not a simple copy process.
Let’s take an example to explain.
In 2010.DEC, a customer has a record below under entity
E14003,group C14001, currecny GBP.The data source is ‘DS11140’,
which is ‘I’ type data source.
1) 2010.DEC /10505111 / F_999 / DS11140 / 3,250,000/
After consolidation run for 2010.DEC, System generates a
record below to reverse the record 1) above, under audit ID DS12100:
2) 2010.DEC /10505111 / F_999 / DS12100 / -3,250,000/
To execute consolidation for 2011.AUG, the first step is to run the balance carry-forward business rule, which is to do ‘copy opening’ (carry forward) for ‘I’ and ‘M’ type data source.
After that, we can see a record under the same account, flow
F_100, in 2011.AUG,as below:
3) 2011.AUG /10505111 / F_100 / DS11140 / 3,250,000
That's the only record on account 10505111 and flow F_100 in 2011.AUG.
And the audit ID is DS11140.
The second step to execute consolidation for 2011.AUG is to execute the consolidation data package for 2011.AUG .At this time, the process of copy opening for data in audit ID of type 'A' will occur.
It is not a simple copy process.
a) First, system looks for data that has been carried forward into flow F_100. That's the record 3).
b) Consolidation engine tries to calculate result for record
3)according to business rules. Normally system will generate the following record,
just like it does when generating record 2):
4) 2011.AUG /10505111 / F_100 / DS12100 / -3,250,000
You may have already noticed that the step b) is in fact doing the carry-forward. And that's how the system is designed.
You may ask why the system is designed in this way just in order to copy the balance in audit ID of type 'A'. Well, let's imagine
that ownership on the entity E14003 is decreased in 2011.AUG. Although the opening balance record 3) is not changed, final result should be
calculated according to the latest ownership.
4-1) 2011.AUG /10505111 / F_100 / DS12100 / -3,000,000
The record 4-1) is the result according to the latest ownership.
Compare it with 4), the difference is 250,000. Instead of generating the record 4-1), system will come up with the records below:
5) 2011.AUG /
10505111 / F_100 / DS12100 / -3,250,000
6) 2011.AUG /
10505111 / F_VAR / DS12100 / 250,000
5) tells the end-user that this record is copied from
2010.DEC.
6) tells the end-user that the percentage is changed and the
difference is 250,000.
The summary of 5) and 6) is the actual result of 2011.AUG.
Next, I will share a bad configuration that results in the copying opening does not work.
A customer has configured a rule ICELIM and there is a detailed line whose SOURCE FLOW has been set to 'F_999' (closing flow).
That prevents the system from doing step b) above because ‘opening flow’ is not included’.
This will result in the fact that the balance is not carried-forwarded.