In business rules you can create a sub routine to copy your base data from one scenario to another. The rule will copy all base entity data in Entity Currency and Entity Currency Adjust from one scenario to another and keep the data in Entity Currency and Entity Currency Adjust.
In the below example, ACTUAL scenario data (actual data at current close rates) is copied to the ACT_LY scenario (actual data at last year rates). This allows the business user to view actual data at last year rates. Once the data is consolidated for ACT_LY, the business user can run HFM reports to analyze the exchange impact between actual rates and last year rates.
Another beneficial rule that can be used with the above is a rule that will change the consolidation status from OK to Impacted in the ACT_LY scenario. As the monthly close process takes place and the data in the ACTUAL scenario continues to change, the data will also change in ACT_LY. The business user will need to know when the data in ACT_LY has changed, and the best way to see this is if the consolidation status automatically changes to Impacted. This will indicate to the business user that the ACTUAL data has changed and ACT_LY needs to be consolidated prior to running the report.
Business rules can also be used to pull or copy exchange rates from one scenario to another. In the below example, ACTUAL exchange rates are pulled to scenario ACT_LY (actual data at last year rates). This can be used to view the exchange impact between current year actual rates and the same data at last year rates. As is displayed in the report example.
In your business rules start by clearing your destination scenario, and then use the copy command to populate ACT_LY, as seen in the following example:
'Copy ACTUAL data into the ACT_CP, ACT_NP, ACT_LY scenario:
'Loop through each base level accounts
For Each Acc In .Account.List("", "[Base]")
If pov_scenario = "ACT_LY" _
'Clear the destination
HS.Clear "A#" & Acc
'Copy the data
HS.Exp "A#" & Acc & "=A#" & Acc & ".S#ACTUAL"
'Business rule to Impact last year scenario:
Sub ImpactNextYear()
If .Scenario.Member = "ACTUAL" Then
HS.ImpactStatus "P#Cur.S#ACT_LY"
End If '.Scenario.Member
End Sub 'ImpactNextYear
'To move pull exchange rates between scenario:
'RATES - This only runs on the currencies at the [None] entity.
'Effectively this is using the global rates
'If this is the [None] entity
If StrComp(pov_entity, "[None]", vbTextCompare) = 0 Then
'If the scenario is ACT_LY then pull the rates from the Prior Year in the ACTUAL scenario
If StrComp(pov_scenario, "ACT_LY", vbTextCompare) = 0 Then
'Copy the rates
HS.Exp "A#ALL = S#ACTUAL.Y#Prior"
Using the above business rules can save time for your HFM administrator, increase accuracy of your application and provide additional reporting capabilities. This rules example can also be expanded to include scenarios at multiple other rates, including current year plan or next year plan rates, depending on your individual needs.
In the report example the same data is in both the ACTUAL and ACT_LY scenarios, as was accomplished by the copy business rule, the difference is the ACTUAL scenario contains current actual close rates and ACT_LY contains close rates from last year.