Keeping up with EPM Cloud

When building Reports in Oracle Cloud EPM Planning or FCC, member functions are an incredibly useful way to make reports as user-friendly as possible. Including functions can also help to make reports more dynamic and reduce any required report maintenance going forward. Functions are accessed via the dropdown at the bottom of the Member Selector : Here are my top 5 member functions to use when creating EPM reports: 1. CurrentPOV Purpose: References the current point of view selection for a dimension Example: Allow the selected Scenario to be visible both in the POV and on the report columns Syntax: CurrentPOV Benefits: Allows the user to change the selection at run-time, making the report more dynamic CurrentPOV can be referenced in other functions to reduce required selections POV choices can be restricted to only valid selections 2. Bottom Purpose: Retrieve the level 0 relatives of a selected member Example: To see all bottom level account codes only Syntax

We’ve all come across this question before as part of the Planning requirements and design – we have some additional information for a base dimension member, but which is the best way to represent this in our EPM Planning system?? All of the options are great, which makes it more difficult sometimes… so this blog will go through a few different example scenarios, which will hopefully help when deciding whether a UDA, attribute dimension or alternate hierarchy fits best. Firstly, let’s make sure we’re clear on the definitions of each option: UDA (User Defined Attribute) – an attribute which is tagged as a member property, which can then be referenced in other areas of the system. Attribute Dimension – a special type of dimension, which is tagged onto a base dimension, to provide additional information about each bottom level member for cross-reporting. Alternate Hierarchy – an alternate hierarchy sits within the main dimension, consisting of subtotals for each attribute which then