Analytics Software

Hello,

I want to start discussion on one of the crucial design decision for HFM application/scenario, whether to use “MissingData0ViewForNonAdj” for Scenario as YTD or Periodic. So I publish this too long post...

If you also have any remarks, your experiences in using "MissingData0ViewForNonAdj" as YTD in your applications, workarounds for drawbacks etc., I would be grateful if you share it.

Some background for discussion
--------------------------------------------------
Simplifying we have to tell HFM how to treat missing data – as zero periodic or YTD. Usual decision are:
- if you load/input your data YTD (as Actual data) – use “MissingData0ViewForNonAdj”=YTD
- if you load/input your data periodic (as Budget data) – use “MissingData0ViewForNonAdj”=periodic

Good, but only “technical” explanation of this issue is here "Understanding the Scenario Settings ZeroViewForNonAdj and ZeroViewForAdj and the Impact on HFM Data [ID 1112863.1]":
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=REFERENCE&id=1112863.1

I focus on “business” implications of choosing setting "MissingData0ViewForNonAdj" as YTD for Actual scenario.

Advantages "MissingData0ViewForNonAdj" as YTD:
- if loading YTD P&L data you don’t need to care what was reported in previous months – system reset accounts to 0 YTD if there was no data in current month

Drawbacks "MissingData0ViewForNonAdj" as YTD:
- looking on P&L data for 12 months Periodic you see that last loaded month is reversed next month (to keep 0 YTD),
- cannot use [Year] element to see what YTD data are in current year, makes life harder in reporting and some calculations
- if entity is deconsolidated from Group (set to not active) during financial year net result from P&L till the day of deconsolidation from Group is not shown in consolidated Group result – it is 0 YTD in the next months till the end of financial year

Using “MissingData0ViewForNonAdj”=periodic is more “business” user friendly, data behave in more expected way with YTD reports or deconsolidation. But you must load/input data periodic, or at least use standard webforms only when inputting YTD data (to see what YTD is calculated from previous months).

Best regards,
Emil

p.s. I already start offline discussion with David, other Oracle EPM forum-mate. Here is his contribution:
“Changing these settings [“MissingData0ViewForNonAdj” for Scenario] can be rather difficult [when application is already working some time]. (These are not on-the-fly setting - meaning - just changing the settings will not automatically change the data in the database.) If you decide to flip the setting. You'll need to recreate a new application, reload all historical data in the new format, re-consolidated & re-translated. And understand what, if any, impact it could have on rules, reports, grids, forms, etc...”