Hyperion Planning Default Member Alias Does Not Update Through EPMA Import Using Interface Tables (Doc ID 1079683.1)

Last updated on MAY 01, 2017

Applies to:

Hyperion Planning - Version 11.1.1.0.00 to 11.1.1.3.00 [Release 11.1]
Information in this document applies to any platform.
June 1,2015

Symptoms


The default member alias does not get updated in EPMA import using Interface Tables.

The data was loaded via ODI to Interface Tables. When making a change to the default alias member, it does not update in EPMA after a re-deploy.

Steps to reproduce:
----------------------
1. Make a change to the alias dimensions in the Accounts table
(i.e. HS_Account_Hierarchy) in the Interface Tables and commit.
2. Create a new profile in EPMA.
3. Load from the interface tables in the Shared Library.
4. Remove all other dimensions using just the Account dimension, merge no Share.
5. Re-deploy the EPMA application.
6. It will deploy successfully.
7. Go back to the Dimension Library and the alias will not be updated.

This works in 11.1.1.2


Added an additional field "ALIAS=DEFAULT" to the hierarchy tables. Below are the create script for tables and views for the account dimension. The view name is what referenced in the im_dimension table.

CREATE OR REPLACE FORCE VIEW epma_int01.vint_account_hierarchy (heir,
loadid,
PARENT,
CHILD,
capexaggregation,
datastorage,
membervalidforcapex,
membervalidforplan1,
membervalidforplan2,
membervalidforplan3,
membervalidforworkforce,
plan1aggregation,
plan2aggregation,
plan3aggregation,
exchangeratetype,
sourceplantype,
workforceaggregation,
"ALIAS=DEFAULT"
)
AS
SELECT LPAD (' ', 2 * (LEVEL - 1)) || TO_CHAR (CHILD) heir,
hs_account_hierarchy."LOADID", hs_account_hierarchy."PARENT",
hs_account_hierarchy."CHILD",
hs_account_hierarchy."CAPEXAGGREGATION",
hs_account_hierarchy."DATASTORAGE",
hs_account_hierarchy."MEMBERVALIDFORCAPEX",
hs_account_hierarchy."MEMBERVALIDFORPLAN1",
hs_account_hierarchy."MEMBERVALIDFORPLAN2",
hs_account_hierarchy."MEMBERVALIDFORPLAN3",
hs_account_hierarchy."MEMBERVALIDFORWORKFORCE",
hs_account_hierarchy."PLAN1AGGREGATION",
hs_account_hierarchy."PLAN2AGGREGATION",
hs_account_hierarchy."PLAN3AGGREGATION",
hs_account_hierarchy."EXCHANGERATETYPE",
hs_account_hierarchy."SOURCEPLANTYPE",
hs_account_hierarchy."WORKFORCEAGGREGATION",
hs_account_hierarchy."ALIAS=DEFAULT"
FROM hs_account_hierarchy
START WITH PARENT = '#root'
CONNECT BY PRIOR CHILD = PARENT
ORDER BY LEVEL ASC,
hs_account_hierarchy.PARENT ASC,
hs_account_hierarchy.CHILD ASC;

CREATE TABLE EPMA_INT01.HS_ACCOUNT_HIERARCHY
(
LOADID NUMBER(38),
PARENT NVARCHAR2(255) NOT NULL,
CHILD NVARCHAR2(255) NOT NULL,
CAPEXAGGREGATION NVARCHAR2(50),
DATASTORAGE NVARCHAR2(50),
MEMBERVALIDFORCAPEX NUMBER(1),
MEMBERVALIDFORPLAN1 NUMBER(1),
MEMBERVALIDFORPLAN2 NUMBER(1),
MEMBERVALIDFORPLAN3 NUMBER(1),
MEMBERVALIDFORWORKFORCE NUMBER(1),
PLAN1AGGREGATION NVARCHAR2(50),
PLAN2AGGREGATION NVARCHAR2(50),
PLAN3AGGREGATION NVARCHAR2(50),
EXCHANGERATETYPE NVARCHAR2(50),
SOURCEPLANTYPE NVARCHAR2(50),
WORKFORCEAGGREGATION NVARCHAR2(50),
"ALIAS=DEFAULT" NVARCHAR2(255)
)


Changes

In the view, change the Alias column from ALIAS=DEFAULT to ALIAS=Default

Notice the case. Since 'Default' is a member name, it is case sensitive.

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