The business dimensions in the model contain members that store information that is specifically related to the requirements of your business or organization, such as product types, sales regions, manufacturing processes, general ledger, payroll, departments, and so on.
At least one Business Dimension type must be defined by the user for the application. Business dimensions are created to describe elements within the model, such as business-specific departments, general ledger accounts, activities, locations, customers, and products. This dimension type does not apply to aggregate storage outlines.
The business dimensions are created in Performance Management Architect. When creating a business dimension, the following requirements apply:
The following properties for the Gen1 member of the dimension must be set to LABEL_ONLY:
DataStorage(BSO)
DataStorage(ASO)
The primary hierarchy is hosted under the first Gen2 child. The primary Gen2 hierarchy is the only hierarchy used in allocation modeling, and this hierarchy cannot contain any shared members.
If the business dimension needs to host an alternate hierarchy, set the dimension hierarchy type to Enabled.
Business dimensions can host alternate hierarchies that may be used in reporting, but these hierarchies are not used for constructing models. If the dimension is going to have shared members in the alternate hierarchies (under the second or further Gen2 members), set the HierarchyType to Dynamic for these members. These members will still be available for viewing in Essbase. See the Oracle Hyperion Profitability and Cost Management Administrator's Guide for detailed information.
Additional Gen2 members are initially displayed in the modeling screens. If you do not want these members to be visible in Profitability and Cost Management modeling screens, set the HierarchyType to Dynamic for these members. These members will still be available for viewing in Essbase. See the Oracle Hyperion Profitability and Cost Management Administrator's Guide for detailed information.
A NoMember member is required. The last Gen2 child in the hierarchy must always be NoMember, with consolidation set to IGNORE (~).
In the Calculation database, the consolidation symbol for NoMember is set to IGNORE (~).
In the Reporting database, because the user dimensions are Stored dimensions, the consolidation for NoMember can be set to IGNORE (~) only if the dimension root member is set to LABEL ONLY. If the dimension root member is set to LABEL ONLY, it does not store any data, and when being used in reporting, it takes the data value of its first child.
Note: | A NoMember member does not have to be created for .ads files because it is added automatically by Performance Management Architect. Do not delete this member. |
When the Essbase outlines are deployed, the business dimensions are created in the Profitability and Cost Management application as basic or generic dimensions, with no type. This feature enables Profitability and Cost Management to re-use the dimension member and hierarchies that were defined for other applications, such as Oracle Hyperion Planning, Fusion Edition.