The following points provide information on the projection data:
1. Baseline run also populates projected date data.
2. This application requires projected data at two levels - Quarterly and Annual.
3. The DIM_CONSOLIDATION table is used to identify the projections. It contains the codes for projected quarters and years as required by the templates.
4. In the Fact tables, projection data is referred to with the respective Consolidation codes (scenario code for FCT_MGMT_REPORTING). BHC must populate the data accordingly.
5. In the following example, FQ1 means Financial Quarter 1, FY1 means Financial Year 1 and so on.
Table 14: Projection Data Example 1
Consolidation Code |
Consolidation Description |
Reporting Line |
Scenario |
EOP Balance |
100 |
Actual |
100 |
BSL |
426,367 |
400 |
FQ1 |
100 |
BSL |
608,618 |
401 |
FQ2 |
100 |
BSL |
870,502 |
402 |
FQ3 |
100 |
BSL |
567,736 |
403 |
FQ4 |
100 |
BSL |
846,196 |
404 |
FQ5 |
100 |
BSL |
775,027 |
410 |
FY1 |
100 |
BSL |
470,092 |
411 |
FY2 |
100 |
BSL |
473,880 |
412 |
FY3 |
100 |
BSL |
942,034 |
413 |
FY4 |
100 |
BSL |
497,889 |
414 |
FY5 |
100 |
BSL |
807,813 |
NOTE:
For Movement Measures Data is not carried from one reporting period to another. For example, Profit or Loss. Where General Ledger Balances such as loan outstanding are carried forward from one year to another, profit and loss are period specific.
Therefore, unlike End of Period (EoP) Balance, movement values for quarter actuals must be derived for reporting. For Historical Data, net sales for quarter 3 is the difference between the sales figure as of the end of quarters 2 and 3. You need not provide this difference as a download. Movement Data for actual is identified through different runs and respective values are summed up.
Only those records, whose corresponding runs fall between the Fiscal Month Start Date and End Date of the reporting quarter are selected for summation. Each Run has an associated date, and runs can be performed daily. Assuming that runs are performed daily in a given quarter (90 days), REG REP sums up data points across all 90 days to arrive at a quarter-end movement figure.
Table 15: Projection Data Example 2
Code |
Projected Period |
Reporting Line |
Scenario |
Run ID |
Date |
Projected Amount |
Movement |
100 |
Actual |
100 |
BSL |
RUNID001 |
10-Oct-13 |
300,000 |
900,000 |
100 |
Actual |
100 |
BSL |
RUNID002 |
15-Nov-13 |
100,000 |
|
100 |
Actual |
100 |
BSL |
RUNID003 |
20-Nov-13 |
300,000 |
|
100 |
Actual |
100 |
BSL |
RUNID004 |
30-Dec-13 |
200,000 |
|
400 |
FQ1 |
100 |
BSL |
-- |
-- |
-- |
608,618 |
401 |
FQ2 |
100 |
BSL |
-- |
-- |
-- |
870,503 |
402 |
FQ3 |
100 |
BSL |
-- |
-- |
-- |
567,736 |
410 |
FY1 |
100 |
BSL |
-- |
-- |
-- |
470,093 |
411 |
FY2 |
100 |
BSL |
-- |
-- |
-- |
473,881 |
412 |
FY3 |
100 |
BSL |
-- |
-- |
-- |
942,035 |
However, when the projection of net sales for quarter 2 next year is to be performed, no derivation is required. Projections data for the said quarter can be directly downloaded in the respective Fact table(s) for reporting.