Sharing members allows alternate rollup structures within Planning applications. A base member must exist before you can create a shared member. You can create multiple shared members for the base member. A base member must display before its shared members in position from top to bottom.
Shared members are allowed for Account, Entity, Scenario, Version, Period, and custom dimensions. Shared members share some property definitions with base members, such as member name, alias name, base currency, and plan types for which members are valid. The Data Storage property for shared members must be Shared or ShareData. Custom properties, custom property values, and member formulas are not allowed for shared members.
Shared members cannot be moved to other parent members. You must delete shared members and re-create them under different parent members. Shared members must be at the lowest level (level zero) in the hierarchy, and cannot have children. (The base member need not be level zero.) You can enter data in shared members; values are stored with base members. With shared members:
A base member cannot be the parent of the shared member. The shared member can be anywhere else in the dimension hierarchy.
A shared member and its base member must have the same name.
You must set data storage for shared members to ShareData in Performance Management Architect. Otherwise, shared members are not added when the application is deployed to Planning.
In dimension hierarchies for member selection in Oracle Hyperion Business Rules and Oracle Smart View for Office, shared members are displayed similarly to base members. For Oracle Hyperion Business Rules, there is no labeling distinction, so you might not be able to select shared members for actions such as Copy Data.