Working with Shared Members
Sharing members allow alternate rollup structures within an application. The shared member values can be ignored to avoid double-counting values when you roll up the outline.
You can create multiple shared members for the primary member.
Note:
Primary members must exist before shared members ("above" the shared member in the hierarchy) for the following dimensions: Scenario, Account, Intercompany, Movement, Data Source, Multi-GAAP (if it exists), and user-created Custom dimensions.
The Period dimension does not support alternate hierarchies.
Shared members share some property definitions with primary members, such as member name, alias name, base currency, and application types for which members are valid. Shared members must have unique parent members and different rollup aggregation settings. Custom attributes, custom attribute values, and member formulas are not allowed for shared members. Renaming primary members renames all shared members.
Shared members cannot be moved to another parent member. You must delete shared members and recreate them under different parent members.
You cannot share a parent member in Custom dimensions.
Shared members must be at the lowest level (level zero) in the hierarchy and cannot have children. The primary member need not be level zero. You can enter data in shared members, and values are stored with primary members.
Shared members are displayed similarly to primary members in the dimension hierarchy for member selection in Oracle Smart View for Office.