The data associated with a shared member comes from a stored member with the same name as the shared member. The shared member creates a pointer to data contained in the stored member; thus the data is shared between the members and is stored only once.
Adding shared members in Outline Editor is a simple process; you assign the Shared data storage property to the member. But, the process of using a rules file to build shared members differs from the process of using a rules file to build stored members; you must choose the build method and format the data source carefully. You must also consider the generation and level numbers of the shared members and their related stored members, because generation and level affect the validity of build methods.
Copyright © 2007, Oracle. All rights reserved.
Creating Shared Members
Parent-child references
Generation references
Level references
Lesson 7 Creating Advanced Dimension Build Rules Files
Parent-Child Build Method
Parent-child references provide the most flexible method for loading and maintaining shared members. By default, a parent-child build automatically adds shared members, without the field designations that are required in level and generation builds. The principal requirements are that a matching stored member exists in the outline and that the matching member has a parent other than the parent of the shared member that Essbase is currently loading.
Creating and maintaining shared members with parent-child references solves a variety of sharing issues that are difficult to manage with the generation or level build methods.
The parent-child build method provides the following benefits:
• Creates shared members automatically without special setup requirements
Module 2 Building Rules Files
Lesson 7 Creating Advanced Dimension Build Rules Files
Hyperion Essbase Analytics 9.3.1 Bootcamp 7-5
• Enables sharing at any level or generation (In the example on the slide, the
Configuration Total shared members and the Line Total shared members are added in one build, despite being shared at different levels or generations.)
• Enables building complete secondary rollup hierarchies in one build (When using generation and level build methods, the duplicate generation or level parents must exist in the outline before the shared member is added; thus, a separate build is usually required. In the example on the slide, Essbase adds not only the shared members but also their ancestors.)
N O T E
Selecting Do Not Share in the Dimension Build Settings dialog box disables for the selected dimension all sharing in a parent-child build. The Do Not Share check box is not selectable for generation or level build methods.
Lesson 7 Creating Advanced Dimension Build Rules Files
Generation Build Method
Using the generation build method to add shared members is a two-step process:
1. Create the secondary hierarchy down to the level of the parents of the shared members, as in the original hierarchy example on the slide.
2. In a separate dimension build, add shared members to the bottom of the hierarchy, as in the resulting hierarchy example on the slide.
In addition to requiring multiple steps, this method also limits where you can add shared members to your hierarchies.
Module 2 Building Rules Files
Lesson 7 Creating Advanced Dimension Build Rules Files
Hyperion Essbase Analytics 9.3.1 Bootcamp 7-7
In the example on the slide, the shared member Lightbolt (a child of New Lines) is a generation 4 member of the Product hierarchy, as is its related stored member (a child of Performance). You can create members that are shared at the same generation by using the generation build method. In this example, Performance is the primary parent, and New Lines is considered a duplicate generation: a generation with shared members for children.
To create shared members by using the generation build method, you need both the primary parent and the parent of the shared member in your data source. List the primary parent first, and define the field type for the parent of the shared members as DUPGEN, using the GEN number of the primary parent.
Lesson 7 Creating Advanced Dimension Build Rules Files
Level Build Method
Sometimes you want shared members to roll up into parents of different generations.
Like the generation build method, the level build method is a two-step process:
1. Create the secondary hierarchy down to the level of the parents of the shared members, as in the original hierarchy example on the slide.
2. In a separate dimension build, add shared members to the bottom of the hierarchy, as in the resulting hierarchy example on the slide.
In the example on the slide, Lightbolt 365 A is a stored member under Lightbolt (generation 4) and a shared member under Config A (generation 3). Because the parents are at different generations, you cannot use the generation build method.
Module 2 Building Rules Files
Lesson 7 Creating Advanced Dimension Build Rules Files
Hyperion Essbase Analytics 9.3.1 Bootcamp 7-9
You can create members that are shared at the same level by using the level build method. In this example, Performance is the primary parent, and Config A is considered a duplicate level: a level with shared members for children.
To create shared members using the level build method, you need both the primary parent and the parent of the shared member in your data source. List the primary parent first, and define the field type for the parent of the shared members as DUPLEV, using the LEV number of the primary parent.
Lesson 7 Creating Advanced Dimension Build Rules Files