Hyperion Financial Management (HFM) (MOSC)

MOSC Banner

NOINPUT Rules to block large portion of Entity Dimension members in HFM

in Hyperion Financial Management (HFM) (MOSC) 2 commentsAnswered

Folks,

There are about 600+ Base Entities and overall 1000 Entities ( Parent + Base) in one hierarchy, Entity Dimension constitute of 3 such hierarchies for reporting using changes in Entity structure and Base members are shared across these 3 hierarchies. We might not require 50% of these base entities due to structural changes and want them to be blocked for future usage - using HS.NOINPUT treads for all the future periods e.g from 2026 to 2036 ( next 10 years).

What are the risk considerations and list of test cases to be consider for making large portion of Entity members blocked via NOINPUT rules in Oracle HFM application ?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center