It is not Possible to Enter Data for Entity Which is not Part of Planning Unit Hierarchy
Last updated on AUGUST 08, 2016
Applies to:Hyperion Planning - Version 184.108.40.206.00 and later
Information in this document applies to any platform.
In Hyperion Planning application entities, which are not part of the Planning Unit Hierarchy (PUH), are becoming Read Only when the Parent of that Entity is promoted in Planning Unit.
Consider the below hierarchy of Entity:
-- Entity 1.1
-------- Entity 1.1.1
-------- Entity 1.1.2
-------- Entity 1.1.3
Enable Entity 1.1 and Entity 1.1.1 in the PUH. The Entity 1.1 has been promoted and locked.
Since Entity 1.1.2 and Entity 1.1.3 are not part of PUH, users will not able to enter data. This is because the parent Entity 1.1 is locked and we cannot enter data for any of its children, as it might change the value of the Entity1.1 which is locked.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms