This function enables you to set up the dimensions used to run consolidations.
The application set used for consolidations has been created and its parameters set up.
You set up consolidation dimensions by:
Setting up dimension library dimensions
Updating dimension properties
Updating dimension members and property values
You must ensure that all the dimensions are available in the Dimension Library of the new application set. (The names need not be exactly the same, but the types of the dimensions are mandatory for corresponding applications.)
For information on creating dimensions, see Dimension Management.
For a legal consolidation application, the following dimension types are required:
C_Acct (A)
C_Category (C)
C_Datasrc (D)
Flow (S)
Groups (R)
Entity (E)
IntCo (I)
Time (T)
For a rate application that contains exchange rates, the following dimension types are required:
R_Acct (A)
C_Category (C)
R_Entity (E)
InputCurrency(R)
Time (T)
For an ownership application that stores ownership details, the following dimension types are required:
O_Acct (A)
C_Category (C)
Entity (E)
Time (T)
IntCo (I)
Groups (R)
When you create a dimension, all the required properties (attributes) are created automatically. Typically, however, a consolidation process (such as currency conversion, simulation, automatic adjustment, and so on) needs additional properties for the filtering, flagging, and calculation of the target data. Therefore, it is necessary to ensure that these properties are correctly maintained with the expected value to be used in the consolidation process, according to business requirements.
The following dimension properties are required for a consolidation. The dimension properties listed here are only intended to help with checking the completeness of the master data setting for a basic consolidation process; the required properties that are automatically generated by the system are not included in this list. For those dimensions, only the requested properties are needed.
For more information about properties, see Member Behavior using Dimension Properties.
C_Category
Property |
Length |
Category_For_OPE |
20 |
FX_DIFFERENCE_ONLY |
2 |
FX_SOURCE_CATEGORY |
20 |
OPENING_PERIOD |
10 |
OPENING_YEAR |
10 |
RATE_CATEGORY |
20 |
RATE_PERIOD |
10 |
RATE_YEAR |
10 |
YEAR |
10 |
C_Acct
Property |
Length |
DIMLIST |
20 |
ELIMACC |
20 |
IC_MATCH |
20 |
VARIATION |
20 |
O_Acct
Property |
Length |
IS_Input |
2 |
Entity
Property |
Length |
Elim |
10 |
FX_Type |
20 |
IntCo |
20 |
Owner |
255 |
C_DataSrc
Property |
Length |
COPYOPENING |
2 |
DATASRC_TYPE |
2 |
IS_CONSOL |
2 |
IS_CONVERTED |
2 |
OPENING_DATASRC |
20 |
Groups
Property |
Length |
CURRENCY_TYPE |
2 |
DATASRC_LEVEL |
10 |
ENTITY |
20 |
GROUP_CURRENCY |
20 |
PARENT_GROUP |
20 |
STORE_ENTITY |
20 |
STORE_GROUP_CURR |
10 |
Flow
Property |
Length |
DIMLIST |
20 |
FLOW_TYPE |
10 |
IS_INPUT |
2 |
Time
Property |
Length |
MonthNum |
3 |
Update the dimension members and property values to meet your business needs. To maintain the dimension members, see Maintenance of Dimension Members.
Note
If the dimension is created as a time-dependant dimension, you cannot delete a hierarchy assigned dimension member out of the timestamp after it has been created.**
In the NetWeaver version of the system, the dimension member values are case sensitive. This means that if two members have the same name but one is in upper case and one in lower case, they are recognized as two different members. For example, the R_ACCT dimensions AVG and Avg could be two different members to store the AVG exchange rate. However, for a rate or ownership application, we strongly recommend that you do not define members this way. It could cause confusion in the script logic or consolidation engine, as well as for users.