My Oracle Support Banner

After Publishing ESSBASE Member names changing (Doc ID 2263077.1)

Last updated on OCTOBER 16, 2019

Applies to:

Oracle Fusion General Ledger Cloud Service - Version 11.1.11.1.0 and later
Information in this document applies to any platform.

Goal

Qn1:On : 11.1.11.1.0 version, Financial Reporting and Analysis

After publishing hierarchies member names changed

Initially the segment values appearing in Application Hierarchies UI are published as is to ESSBASE
After Adding new node and published, values are changed to {All Product Values}{011} , initial value for this are 011
Because of name change Allocation Rules and FR reports ending in to error and customer need to re select new member names to fix this.


Steps to reproduce
1. Updated  segment  hierarchy.
2. Published Hierarchies
3. When  open FRS reports, few of the segment member names are not being recognized Because After Publishing ESSBASE Member unique names changing
4. Every time Customer fix the error in FRS and Allocations by re selecting the member(change in name ) again.
 

Reason For member names change after  adding new node :-

Essbase dynamically generates member unique names for members based on the number of occurrences of a member(value) on Essbase cube at various levels.

For example, Unique names include @ and pipe(|) characters when the number of occurrences of same member name is more than once in the cube.
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.