Use this function to select and update dimensional accounting journals that require amendment.
Refer to documentation Implementation
The Dimensional modifications function displays an initial screen into which you enter your selection (or filtering) criteria and a screen into which you enter the required changes.
Criteria
| All companies (field TOUSOC) |
Enter the company code for which the processing has been started.
The company code:
Select this check box to include all sites. To run this process for a single site, leave clear.
Enter the site code for which the processing has been started.
It is mandatory to enter this field if the box "All sites" is not checked.
Select this check box to include all users. To run this process for a single user group, leave clear.
The current user will be used if the user/group code is blank.
If a user code is entered in this field, the process only includes accounting documents entered by the user. If left blank, only accounting documents for the current user are included.
If this box is checked, all types of ledgers linked to the selected company, and for which the "Analytical" accounting type is checked, will be impacted by the processing.
This field corresponds to the ledger type on which the processing is started.
It is mandatory to enter this field if the box "All ledger types" is not checked.
Select this check box to include all types. To run this process for a single type, leave clear.
When a journal type is entered, the processing is only started for the journals for which this type has been used.
If this box is checked, all journal types are taken into account for the operation.
Enter the journal type. It must be of the same type as the journal linked to the selected journal type.
It is mandatory to enter this field if the box "All journals" is not checked.
The journal type is used to group journals based on common characteristics mainly linked to the nature of the operations that will be recorded in it:
Some processings and controls depend on the journal type:
The setup of the cash journals is specified in the Definition of the journals, journal types and accounts on payments documentation.
Six journal types have been allocated to the miscellaneous operations:
If the box "All journals" is checked, all types of journals are taken into account for the operation.
Here, indicate the journal code comprised of one to five alphanumeric characters.
Upon creation, the journal is automatically open for all the specified periods.
The journal selected here must be of the same type as the journal linked to the journal type kept in the previous selection criteria.
It is mandatory to enter this field if the box 'All journals' is not checked.
Date from which the records are selected.
Date until which the records are selected. This date can only correspond to the end of a period.
This field is used to further specify the selection by defining an account range.
Specify here the first account to be selected.
This field is used to further specify the selection by defining an account range.
Specify here the last account to be selected.
If the box "All dimensions" is checked, the processing involves all the dimensions linked to the selected dimension view(s).
Enter the dimension view for which the dimension ra nges need to be entered.
This field is mandatory if the box "All dimensions" is not checked.
Enter a start range to limit the processing to some dimensions of the filtered dimension view.
Enter an end range to limit the processing to some dimensions of the filtered dimension view.
It is possible to further specify the selection to:
This field is activated if the option "No entry on the dimension view" has been selected.
Enter the dimension view onto which the condition should be applied.
Selection
| Quantity change (field MODQTE) |
|
Check this box if modifications need to be introduced to the quantities. |
| Log file (field TRACE) |
|
Select this check box to generate a log file. |
Grid Dimension type
| field NBRDIE |
| No. (field NUMLIG) |
|
It is the line number. |
| Dimension type (field DIE) |
|
Select the analytical dimension view(s) that need to be modified. |
| Modification (field MODAXE) |
|
Check the cell for the entered dimension views that need to be modified. |
Criteria
| Entry (field TYP) |
|
Journal type of the displayed recording. Each accounting journal entered is linked to a given type. The journal type corresponds to the nature of the entered posting: customer invoice, miscellaneous operations, cash receipt, etc. |
| Number (field NUM) |
|
Journal number of the recording. |
| Line (field LIN) |
|
It is the line number. This number is automatically generated. |
| Ledger (field LEDTYPNAM) |
|
This field corresponds to the ledger type on which the modification is performed. |
| Company (field CPY) |
|
Enter the company code for which the processing has been started. |
| field CPYNAM |
|
Company description. |
| Site (field FCYLIN) |
|
This field defines the site involved in the processing. |
| field FCYNAM |
|
Site description. |
| Accounting date (field ACCDAT) |
|
Date on which the transaction is posted. |
| Journal (field JOU) |
|
This field defines the journal of the displayed recording, impacted by the processing. |
| field JOUNAM |
|
Description of the displayed journal. |
| Control (field SAC) |
|
This field mentions the collective account code of the displayed account. |
| Account (field ACC) |
|
This field displays the account of the journal impacted by the processing. |
| BPs (field BPR) |
|
This field specifies the code of the BP in the record displayed for the processing. |
| Amount (field AMTCUR) |
|
Amount expressed in the transaction currency. |
| field CUR |
|
Transaction currency code. |
| field SNS |
|
Sense of the entry: Debit or credit. |
| Reference (field REF) |
|
This field contains the reference of the journal displayed for processing.. |
| Description (field DES) |
|
This field displays the content of the free entry field of the recording. |
Nonfinancial units
| Nonfinancial unit (field UOM) |
|
On analytical inquiry, this field determines the non-financial unit linked to the displayed account. |
| Quantity (field QTY) |
|
This field is used to display the quantity of non-financial units of the recording displayed for processing. |
| Distribution (field DSP) |
|
Use this field to apply a different analytical allocation key to the selected journals. Analytical allocation keys apportion the journal line across multiple analytical dimensions. |
Dimension types
| field CCE |
|
Use these fields to apply a different dimension type code to the selected journals. These fields can be modified if the following conditions are met:
|
|
Recall memo |
Click this action to enter a Memo code to load the settings associated with the code. |
|
Delete Memo |
Click this action to delete a Memo code. |
|
Criteria |
Click the Criteria action if you need to change the journal selection criteria. You are sent back to the journal selection screen. |
|
Entry |
Click the Entry action to display the entry details. |
Example (applicable to the two limitations mentioned above)
A company has three ledgers:
A journal line on my supplier account updates the legal and the group ledgers.
- The analytical allocation key can be updated.
- The CCT dimension type can be updated.
Reason:
- The analytical allocation key defined on the entry line in this example only distributes the amount onto a single analytical ledger (the grouped analytical ledger).
- The CCT dimension type affected by the entry line in this example is common to only a single analytical ledger – the group analytical ledger.
An entry line on the purchase account updates the legal, analytical and grouped ledgers.
- The analytical allocation key cannot be updated.
- The CCT dimension type cannot be updated.
Reason:
- In this example, the analytical allocation key defined on the entry line distributes the amount onto several analytical ledgers (the analytical and grouped ledgers).
- The CCT dimension type associated with the entry line is common to several analytical ledgers (the analytical and grouped ledgers).
The only error messages are the generic ones.
Refer to documentation Implementation