Qualified Name Display in Alternate Hierarchies

Cloud data source types: Planning, Planning Modules, Financial Consolidation and Close

About Qualified Member Name Display in Alternate Hierarchies

When connected to Planning, Planning Modules, or Financial Consolidation and Close, alternate hierarchies are supported in the Entity dimension. One entity can have multiple parents, and contribute differently to each parent. These members are referred to as partially shared entities, where only a part of input data is shared across all instances of the entities.

In Oracle Smart View for Office, displaying partially shared members requires that member names and aliases are qualified, so that users can uniquely reference the specific instance of a member and can then enter appropriate values based on this context. Qualified names include the member name and the names of its ancestors to the level that uniquely defines the member. The most common example is the Percentage Contribution (PCON) metric used for weighted consolidations in Financial Consolidation and Close.

The qualified name behavior for alternate hierarchies is explained in these topics:

Expected Runtime Behavior on Forms

Expected Runtime Behavior for Aliases on Forms

Expected Runtime Behavior on Ad Hoc Grids

Expected Runtime Behavior for Aliases on Ad Hoc Grids

Expected Member Selector Behavior on Ad Hoc Grids

Expected Member Selector Behavior on Forms

Expected Runtime Behavior on Forms

Starting in 17.01, Planning, Planning Modules support the option to qualify member names as part of form design. This option, Show Qualified Names, is only exposed when you have a dimension enabled for Partial Share. This option has three possible values:

Never
As Needed
Always

By default, to maintain backwards compatibility the "Never" option is selected. "Never" is also used when this option is not exposed. Note that this is a runtime option and does not impact design time member selectors. Here is the expected behavior on forms for each option:

Never
- PBCS, EPBCS: All member names are not qualified.
- FCCS: All member names are not qualified.
As Needed
- PBCS, EPBCS: Base members are NOT qualified. Shared members are qualified.
- FCCS: Both base members WITH SHARES and shared members are qualified. Base member without shares are not qualified.
Always
- PBCS: All members are qualified.
- FCCS: All members are qualified.

Expected Runtime Behavior for Aliases on Forms

Alias behavior should behave the same as for member names with these exceptions:

When showing qualified aliases both components (parent and child) must have aliases otherwise, the member name or qualified member name is returned as per selected option.
Duplicate aliases are also qualified when "As Needed" or "Always" option is selected.

Expected Runtime Behavior on Ad Hoc Grids

Member names are qualified or not based on the Smart View Member Name Display option setting. There are two values to support the partial share feature: Distinct Member Name Only and Member Name Only. Here is the expected behavior for each option:

Member Name Only
- PBCS, EPBCS: All members are not qualified.
- FCCS: All members are not qualified.
Distinct Member Name Only
- PBCS, EPBCS: Behaves the same as the "As Needed" option for forms above.
- FCCS: Behaves the same as the "As Needed" option for forms above.

Expected Runtime Behavior for Aliases on Ad Hoc Grids

Alias behavior should be the same as in Expected Runtime Behavior on Forms, but also subject to the Smart View ad hoc alias options.

If the "None" alias table option is selected, then you should see same behavior for members in ad hoc grids as in Expected Runtime Behavior on Forms.
If an alias table is selected, then the aliases from that table should be used and ad hoc options for members apply. Note that alias behavior for aliases on forms applies as well based on Smart View ad hoc settings.

Expected Member Selector Behavior on Ad Hoc Grids

The Member Selector will work based on the setting in the Smart View "Member Name Display" option.

The Member Selector will display the qualified names for shared members by default.

Expected Member Selector Behavior on Forms

The Member Selector will work based on form settings for aliases and behave like the "As Needed" setting on forms.