Skip to main content

EPMA Search Member Function Does Not Find Hierarchy Members Below Shared Parent


So this is a published bug in EPMA for Hyperion Financial Management Version
11.1.2.3.500 and later only, However, I have experienced this issue to be coming up in Planning applications.

SYMPTOMS

In Enterprise Performance Management Architect (EPMA) if you move or include an existing parent member as a shared member underneath a different or new parent then the children rolling up to the first parent will not be shown.If Parent member is shared in an hierarchy, all levels below that shared level can not be found while using "Find Members" through Smart View neither can be drilled down through Smart View.

Search member result is "No member found", although this member is part of the Hierarchy.

CAUSE

EPMA is behaving as expected.

SOLUTION

When we drill the Shared Member we are unable to see the level0 members in the template in generic. However, if we change one of the MEMBER OPTIONS of retrieval in our Smart View -> Options tab
Generic Setting for Zoom In Level is set to Bottom Level or All Members , change it to “FORMULAS”.
Retrieve now: You should be able to drill to level 0 members in Shared hierarchy.

I think for some reason Smart View treats the shared members level 0 as a formula to pull members from the actual hierarchy.

For more details on the published documentation by oracle refer : 



Hope you find this useful somewhere!!

Cheers!
Anvi.S

Popular posts from this blog

Essbase for Beginners: Data Block concepts Part A

An Essbase outline has a number of dimensions.  The number of dimensions can range in quantity and size, but each dimension is identified as a dense or sparse dimension.  As we understood the concept of Dense and Sparse in our last discussion, let’s begin with the cocept of data blocks now. To understand this, let’s carry forward our hierarchy of 5 dimensions in a test application in my previous post.. We have 3 dense and 2 sparse dimensions each with 3 stored members. So let’s begin: Number of Existing Blocks = (potential number of blocks) * estimated density= 9 Block Size = Dense Stored * Dense Stored * Dense Stored * 8 bytes = 3*3*3 *8 = 216 Potential number of blocks = Sparse Stored * Sparse Stored = 9 If all dimensions are assigned as Dense, Number of Existing Blocks = (potential number of blocks) * estimated density= 1 Block Size = Dense Stored * Dense Stored * Dense Stored * 8 bytes = 3*3*3*3*3 *8 = 1944 Potential number of bloc...
Home

Shared Connection and Private Connection

You connect to data sources through shared or private connections. Shared Connections •Shared connections are stored in a central location and are available to multiple users through the Smart View Panel. You cannot add, edit, or rename shared connections, but you can save them as private connections, which you can edit and rename. Private Connections •Private connections are those that you create by saving a shared connection to your local computer or by entering a URL to a provider that is not configured for shared connections. When you create a private connection, it becomes the active connection. Shared Connections : 1. From the Smart View ribbon, click  Panel . 2. From Smart View Home or from the menu displayed when you click the arrow next to Home button, do one of the following: • Click a connection name under  Recently U sed . You can click    to pin items to this list. • Select  Shared Connections  to open th...
Home

Essbase for Beginners: Data Block concepts Part B

Below concepts involve Data Blocks in some way or the other, so to understand how Data Blocks behave it’s good to understand these concepts: Let's Begin!! Compression Clean and Dirty Blocks Fragmentation Restructure Compression: When Essbase stores blocks to disk, it can compress the data blocks using one of the following compression methods, this is based on the type of data that is being loaded into the Essbase database. Essbase provides several options for data compression: 1. Bitmap compression : This is the default compression method. Essbase stores only non-missing values and uses a bitmapping scheme. A bitmap uses one bit for each cell in the data block, whether the cell value is missing or non-missing. When a data block is not compressed, Essbase uses 8 bytes to store every non-missing cell. 2. Run-length encoding (RLE): Essbase compresses repetitive, consecutive values --any value that repeats three or more times consecutively, including...
Home