EPMA Inserted Shared Member Order is not Maintained when Deployed to Planning Application (Doc ID 1313112.1)

Last updated on JULY 28, 2016

Applies to:

Hyperion Planning - Version 11.1.1.3.00 and later
Information in this document applies to any platform.

Symptoms

Member order is not Maintained for Shared members after Redployment
To reproduce the issue you will have to do the following in your existing
hierarchy:
- In EPMA, Right click on StoredStaff -> David, select create member as
sibling and create the member David1
- Right click on SharedStaff -> Catherine(Shared), Insert Shared Member
(David1) as sibling
So that you endup in EPMA with:
-StoredStaff
--Baschir
--David
--David1
--Careen
--Catherine
--Albert
-SharedStaff
--Albert(Shared)
--Baschir(Shared)
--Catherine(Shared)
--David1(Shared)
--Careen(Shared)
--Eddie
--Freddie
When you refresh, you will endup in Planning with the following (tested in
patch 11.1.1.3.05)
-StoredStaff
--Baschir
--David
--David1
--Careen
--Catherine
--Albert
-SharedStaff
--Albert(Shared)
--Baschir(Shared)
--Catherine(Shared)
--Careen(Shared)
--Eddie
--Freddie
--David1(Shared)

Changes

EPMA metadata has been updated requiring a Hyperion planning application deployment.

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