Approved Planning Units Writable In Data Forms Where Scenario Shared Members are used

(Doc ID 1369223.1)

Last updated on JULY 28, 2016

Applies to:

Hyperion Planning - Version 9.3.1.0.00 to 11.1.2.1.101 [Release 9.3 to 11.1]
Information in this document applies to any platform.

Symptoms

Scenario Dimension hierarchy:
Scen1
Scen2
Scen3
ScenShared
  Scen1 (Shared)
  Scen2 (Shared)
Version Dimension Hierarchy
Ver1
Ver2
VerShared
  Ver1 (Shared)
  Ver2 (Shared)

Normal Behaviour:

Setup a planning Unit that is based on the combination Version, Scenario and Entities using the based members (ie. Sen1, Ver1, Entiy members).
Create a webform that enables data entry to the above combination.
Go through process management cycle till approval at which point data entry should no longer be possible
as cycle is closed.
Issue:
Create another webform based on the combination Scen1 (Shared), ver1, Entiy member (as above).
Users are able to enter data in the shared member Scen1 (Shared) which is in fact a pointer to the base member Scen1. So using Scenario shared members users are able to enter data in a closed cycle which defeats the purpose of the process management cycle.

Cause

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