Dimension Groups

• Pyramid (field VPYM)

It is a title field.

• Analytical dimension type (field VDIE)

This field indicates the analytical dimension type concerned.

This field is used to enter or select any dimension view set up in the database.

• Group (field VGRU)

This field is used to indicate the code assigned to the group of analytical dimensions.
A group can be composed of sub-groups and/or analytical dimensions.
It belongs to an analytical pyramid.

• field VDESTRA

It is a title field.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for thefolder.

• Short description (field VSHOTRA)

It is a title field.

The short description replaces the standard description when display or print constraints require it.

• Parent group (field VPERE)

This field reuses the code assigned to the parent group from which comes the group of analytical dimensions selected.

• field VPDES

It is a title field of the parent group.

• Definition level (field VLEV)

This level MUST be less than 99, level 99 being reserved by convention to the analytical dimensions.
If the group is included in another group for the pyramid, the level MUST be greater than that of the group in which it is included.
If the group contains sub-groups, the level must be strictly less than that of the sub-groups.

• Print row (field VPRNROW)

The printing rank is used to sort the groups belonging to the same level.

The printing rank makes it possible to sort out the dimension groups in reports in an order different from the default alphabetical order.
Unlike the regrouping level, the printing rank cannot be identical for two dimension groups.

• Budget tracking (field VBUDTRK)

If this box is checked, the group of accounts can be used in the different existing budgets.

• Subgroup (field VSBBGRU)

Account sub-group included in the account group.
The sub-group must belong to the same pyramid as the group, must be of a definition level strictly greater than that of the group, and cannot be integrated in another group of the pyramid.

• Description (field VDESGRU)

This field assigns the sub-group title.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for thefolder.

• Dimension (field VCCE)

This field is used to enter the analytical dimension code.

The setup length of the code is used to define the maximum length of a dimension and dimension type code by dimension type.
It is possible to use the * and ? wildcards to include several dimensions into a template.
The dimension must not be included in another group in the same dimension pyramid.
Similarly, the same group name can only be used once, in a pyramid and a dimension type.

• Description (field VDESCCE)

This field assigns the title of the dimension codes displayed.

• Pyramid code (field PYM)

Code of the pyramid to be generated. It has probably already been created.
This code will be used at a later time in all records.

• Chart of accounts (field COA)

This field recalls the chart of accounts on which the account or the pyramid (general, analytical, both) will be created or to which they will be attached.

• Pyramid level (field NIVEAU)

The numerical value entered in the various available fields makes it possible to establish a hierarchy of groups present in the pyramid.

• Account length (field LENLEV)

The numerical value entered in the various available fields is used to indicate the number of character(s) for each level of the pyramid.
For instance, if the number entered is 4 for the level 40, the length of the groups is of four characters.

• Use wild-cards (field JOK)

When checked, this box is used to include any new account or dimension to the defined group.
This link is made by entering:

• a screen,
• a direct account number.

Example:
Let us consider a pyramid to be created for the SOC chart, grouping accounts 101 001, 101 002 and 101 003 :
1. box checked: the system uses wildcards and includes automatically any account of type 1010* (according to the screen entered). An account of type 101 004, corresponding to the screen, is thus included in the group.
2. box not checked: the system does not use wildcards. It includes only the existing accounts 101 001, 101 002 and 101 003. An account of type 101 004 is not automatically linked to the group.

• Homogeneous levels (field HOM)

When checked, this box is used to plan the insertion of groups on a same level when they have different length so that each branch of the generated pyramid has the same number of levels.