org by period analysis

7/25/2019 Org by Period Analysis

http://slidepdf.com/reader/full/org-by-period-analysis 1/9

HFM Organization by Period White Paper

Prepared by: Danny Tijerina

Advanced Technology group (OrgByPeriodApplication)

When choosing to set up an HFM application with organization by period there are a few factors toconsider that will have various effects on the way data is consolidated. The Default Frequency and

Default View do not effect consolidation, however, they do affect rules. Zero View for NonAdjust andZero View for Adjust as well as Consolidate YTD do have an effect.

Default View affects rules to the extent that numbers in flow type accounts (Income, Expense and Flow)default to the scenario view. For example: In a Periodic scenario you would need to specify W#YTD on

the right side of the expression to retrieve YTD numbers in a Sub Calculate routine, the inverse would betrue for a YTD scenario.

The following will explain the various effects of the different combinations of Scenario settings:

The first two examples Scenario OBP1 and OBP2 have the following settings:

OBP1 OBP2 Default Frequency – MTD Default Frequency – MTDDefault View – Periodic Default View – YTD

ZeroView for Non Adjust – Periodic ZeroView for Non Adjust – YTDZeroView for Adjust – Periodic ZeroView for Adjust – YTD

Consolidate YTD – No Consolidate YTD – No



POV: View – Periodic, Value [Contribution].

I these examples the following changes were made:- EastSales was moved from EastRegion to NEastSales in March

- EastAdmin was moved from EastRegion to NEastSales in February

The RED cells are invalid or inactive in relationship to the current parent.

The numbers in both scenarios consolidate exactly the same way for the first three months. The difference

is the ZeroView for April. OBP2 shows the YTD reversal of the data to get to a YTD zero balance.



POV: View – YTD, Value [Contribution].

The numbers in both scenarios consolidate exactly the same way for the first three months. The differencehere is OBP1 numbers flow to April on a YTD basis. The odd thing with OBP2 is the YTD numbers

don’t completely zero out because of the YTD values produced by the change is structure. See the nextsnap shot for a better explanation.



In this grid both Periodic and YTD views are included for March and April to demonstrate why the YTDnumbers in OBP2 do not completely zero out.

Notice March YTD numbers compared to the YTD reversal in the Periodic column for April in OBP2.The reversal includes all members for all periods, whereas the YTD numbers only reflect active members.



The next two examples Scenario OBP3 and OBP4 have the following settings:

OBP3 OBP4 Default Frequency – MTD Default Frequency – MTD

Default View – Periodic Default View – YTD

ZeroView for Non Adjust – Periodic ZeroView for Non Adjust – YTDZeroView for Adjust – Periodic ZeroView for Adjust – YTD

Consolidate YTD – Yes Consolidate YTD – Yes



POV: View – Periodic, Value [Contribution].

I these examples the following changes were made:- EastSales was moved from EastRegion to NEastSales in March

- EastAdmin was moved from EastRegion to NEastSales in February


Notice in this example, even though the zero view in OBP3 is Periodic the YTD value goes to zero forinactive Memebers. The numbers in March reflect the YTD numbers in the active Member and zero in the

inactive members.



POV: View – YTD, Value [Contribution].


In this example the two scenarios consolidated exactly the same on a YTD basis. Notice the difference in

YTD numbers between scenarios OBP4 and OBP2. OBP4 completely zeros out due to the YTDconsolidation.



In this grid both Periodic and YTD views are included to demonstrate why the YTD numbers in OBP4completely zero out.

Notice March YTD numbers compared to the YTD reversal in the Periodic column for April in OBP4.



Summary:

In summary if you are going to create an application with Organization By Period you need to be aware of

how the scenario attributes affect consolidation. The recommended settings for an OBP application are

reflected in scenario OBP1.

The settings in OPB1 allow for the proper consolidation of numbers on both a periodic and YTD basis based on the active and inactive members. Although the settings in OPB2 allow for proper consolidated

numbers the YTD zero view could be very confusing to a client. Also, the YTD zero view does not bodewell for trended monthly reports because of the reversal in the first month without data.

The Consolidate YTD setting does not reflect the proper numbers on a YTD basis. The purpose of OBP isto include numbers for the current parent in the active months only. Consolidate YTD overrides this

theory by inc luding YTD numbers for the active member only and zeros out the inactive member on aYTD basis.

org by period analysis

Documents