You use the Dimensions screen to configure dimensions and security properties for dimensions. You can add or delete Custom dimensions, and specify a Custom Dimension name and Alias.
In the Dimensions table, the first two Custom dimensions for the application are automatically displayed. These Custom dimensions are used for currency rate and consolidation method information, and the size for these dimensions must be Large. The first dimension is used for “From Currency” and consolidation method information, and the second dimension is used for “To Currency” information. You can specify the dimension name (short label) and dimension alias (long label) for the Custom dimension for these two entries. You cannot change the size, and you cannot delete these dimensions.
In addition to the default dimensions, you can create additional Custom dimensions with these guidelines:
You must enter a unique Custom dimension name and dimension alias for the application. Both the name and alias must be unique. For example, if you have a dimension name of PROD, the dimension alias cannot be PROD. The Custom dimension name also cannot be the same as a Currency name.
The dimension name can be a maximum of 10 characters.
The dimension alias can be a maximum of 20 characters.
The dimension name and alias cannot contain spaces, and cannot be blank.
You must select a size for the Custom dimension: Small, Medium, or Large.
The maximum number of Custom dimensions depends on the database type and the size of each Custom dimension.
The Large Custom dimension supports 2 billion members, and requires 4 bytes of space in a database column for storage.
Medium supports 32,000 members and requires 2 bytes.
Small supports up to 128 and requires 1 byte.
The calculation method of the maximum number of Custom dimensions is the same regardless of the database type, but the database type determines the amount of total space available.
The total number of physical Custom columns dictates the total number of bytes available for Custom dimension storage in Oracle, Microsoft SQL Server, or IBM DB2 databases.
Oracle supports up to 21 physical Custom columns; 21 x 8 = 168 bytes total available space.
SQL Server supports 5 physical Custom columns; 5 x 8 bytes = 40 bytes total available space
IBM DB2 supports primary keys up to 900 bytes, = 800 bytes total available space
At least two Custom dimensions are required. Below are the formulae for calculating more than two Custom dimensions:
Migrating applications: 4xLD + 2xMD + SD <= MAXBYTES - 8 New applications: 4xLD + 2xMD + SD <= MAXBYTES
LD = number of large dimensions, MD = number of medium dimensions, and SD = number of small dimensions.
MAXBYTES = 40 for Microsoft SQL Server, 168 for Oracle, 800 for IBM DB2
Oracle recommends that you use Medium for Custom dimensions for all practical purposes.
The Small size for Custom dimensions is not recommended if you anticipate having more than 128 members over the lifetime of the application.
Oracle recommends that you use the Large size for Custom dimensions only if you plan to have more than 32,536 members in that dimension over the lifetime of the application.
The following example shows sample Custom dimensions.
| Custom Dimension Name | Custom Dimension Alias | Custom Dimension Size | Use for Currency |
|---|---|---|---|
Prod | Products | Large | From Currency |
Mkt | Markets | Large | To Currency |
Flows | BSFlows | Small | N/A |
Cust | Customers | Large | N/A |
To create Custom dimensions:
From the Dimensions table, click the (+) Create Custom Dimension button, or select Actions, and then Create Custom Dimension.
For Dimension Size, select an option: Small, Medium, or Large.
Optional: If you have completed all the steps to create an application, click Create Application.
When the application is successfully created, a confirmation message displays that the application has been created and that the metadata has been loaded successfully. From the confirmation message, click OK.