Defining and Maintaining Dimensions
This topic provides an overview of dimensions and discusses how to:
Define dimensions.
Define dimension details for an Operational Warehouse - Enriched (OWE) warehouse table.
Define dimension details for a Multidimensional Warehouse (MDW) table.
Pages Used to Set Up Dimensions
Page Name |
Definition Name |
Navigation |
Usage |
---|---|---|---|
Dimension |
PF_DIM_DEFN |
|
Define dimension metadata. |
OWE Detail for Dimension |
PF_DIM_OWE_DETL |
|
Define dimension metadata details for an OWE dimension and apply security parameters. |
MDW Detail for Dimension |
PF_DIM_MDW_DETL |
|
Define dimension metadata details for an MDW dimension and apply security parameters. |
Understanding Dimensions
Dimension metadata is associated with specific record metadata and its fields. For example, you can define the dimension DEPARTMENT that references the record DEPARTMENT_TBL and the DEPT_ID column in that record. Dimension metadata captures additional column, key, and security information that is not included with a standard datamap, such as alternate key fields and dimension security. A single dimension can be defined for both an OWE and MDW tables, enabling you to use the same dimension name for both table types.
Dimension metadata is used by the EPM Warehouses, applications, security, and KPI manager.
Dimension Security
Because EPM is delivered with no security restrictions, dimensions are also delivered unsecured. Before you can grant a user access to a dimension you must first indicate to the system that a particular dimension requires securing. Dimensions that are not secured are classified as public, or unsecured. All EPM users can view these objects.
You specify dimensions that require securing using the Dimension page. After you specify a dimension to secure you must associate that dimension with a security join table to complete dimension security. Security join tables are EPM database tables that store the security profiles for users along with the corresponding dimension values for which they have access. During security processing, a security join table acts as a lookup. For example, when a user is trying to access a row of data, the SQL that processes this request uses the security join table to identify the user and her access to the particular row of data.
A security join table must be created for every dimension that you plan to secure. Each security join table should match the key structure of the dimension table for which it is defined. Each row in a security join table identifies a user or security role and his access to a specific dimension value. A user who is granted access to multiple values in a single dimension table has several rows in the security join table. In the event that a user has access to an entire dimension, you can insert a single row designated all and prevent the table from ballooning in size with several rows of data. A user that is granted access to multiple dimensions appears in several security join tables.
Image: Account security join table
The following is an example of a security join table.
The security join table model is better than a single security output table for two main reasons: Processing smaller tables is more efficient when you are inserting or deleting data, or querying the table to determine access privileges, and modeling individual security tables enable you to be in sync with the anticipated migration to data objects in future releases.
Dimensions Page
Use the Dimension page (PF_DIM_DEFN) to define dimension metadata.
Image: Dimension page
This example illustrates the fields and controls on the Dimension page. You can find definitions for the fields and controls later on this page.
OWE Detail for Dimension Page
Use the OWE Detail for Dimension page (PF_DIM_OWE_DETL) to define dimension metadata details for an OWE dimension and apply security parameters.
Image: OWE Detail for Dimension page
This example illustrates the fields and controls on the OWE Detail for Dimension page. You can find definitions for the fields and controls later on this page.
Record Information
Security
MDW Detail for Dimension Page
Use the MDW Detail for Dimension page (PF_DIM_MDW_DETL) to define dimension metadata details for an MDW dimension and apply security parameters.
The MDW Detail for Dimension page contains the same fields as the OWE Detail for Dimension page with the addition of the following three fields.