See the documentation on dimensional allocation structures for further information.Use this function to calculate the dimensional allocation structures. When you run this function, the dimensional allocation journal entries are generated immediately.
See the documentation on dimensional allocation structures for further information.
Because the final allocation criteria of expenses or revenues is not known at the time of the transaction, these expenses and revenues are assigned at a later point.
This is the case, for example, with dimensions for indirect expenses such as advertising expenses. First, these expenses are allocated to a dimension (a department, for example) on entry. They can subsequently be allocated to the other departments of a company in proportion to the sales achieved by each of these services.
This generates the corresponding dimensional entries that can be viewed and modified using dimensional miscellaneous operations entry screens.
It groups the allocation lines in the same entry, except for:
Read the documentation for Partner initialization and Flow initialization.
Refer to documentation Implementation
Header
| Company group (field GRPSOC) | ||||||||||||||||||||||||||||||
|
Enter or select a company or a group of companies to limit the generation of journals in the balance sheet or the result of a given company or group of companies. |
||||||||||||||||||||||||||||||
| Ledger type (field LEDTYP) | ||||||||||||||||||||||||||||||
|
Use this field to define the ledger type concerned by the journal balance. In this function, only Manual ledgers can be accessed. You can read the balance on the selected ledger and balance the account for that ledger type. The propagation then initializes the accounts for the non automatic and non prohibited ledger types. This initialization process is based on the entry type setup and account setup. The propagated amount is the one calculated on the main general ledger in transaction currency. This amount is then converted into the currency of the propagated ledgers. When generating the journal balance, the propagation depends on the selected entry type. The entry type used during the journal generation and the entry type used during the balance generation (actual mode) must be consistent.If the two entry types are not consistent, the balance process must be launched on each non-propagated manual ledger where the account needs to be balanced. Examples
Selected ledger type = Social, Generation type = Actual In this case, when generating the balance, the propagation is global.
Selected ledger type = Legal; Generation type = Actual Here, the propagation is incomplete. The IAS ledger is not propagated. If you want to balance the account on the IAS ledger, relaunch the balance process for this ledger type using an entry type that only authorizes IAS ledgers. For an automatic ledger type, the amounts in transaction currency are not calculated from the balance. They are the same as the currency amounts calculated for the original manual ledger. The ledger amounts for the automatic ledger are calculated by converting its currency amounts according to the journal entry rates. |
||||||||||||||||||||||||||||||
Grid Details
For an automatic ledger type, the amounts in transaction currency are not calculated from the balance.
The amounts are the same as the currency amounts calculated for the original manual ledger. The ledger amounts for the automatic ledger are calculated by converting its currency amounts according to the journal entry rates.
| Company (CPY) |
|
Enter the company code or use the Look up tool to search for and select the code. |
| Allocation (DIA) |
|
Enter the name of an allocation setting that was defined in Dimension structures. |
| Site (SITE) |
|
This code is used to identify the site concerned. It is unique for each site. |
| All users (ALLUSR) |
|
Select this checkbox to include all users. To run this process for a single user group, leave clear. The current user is used if the user or group code is blank. |
| User (USR) |
|
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. |
| Starting allocation period (STRDAT) |
|
The period to be distributed is the period considered to calculate the amounts to be distributed. On a dimension defined as the dimension to be distributed in the distribution structure, the program sums up all the postings completed over the period defined by this field. This total represents the amount to be distributed for this dimension. When these dates correspond to the exact fiscal year period start and end dates, the generated journal entries are identical whether Processing based on balances is selected or not. See the limitations when the allocation has multiple lines. By default, the range for this period corresponds to the current financial year. |
| Ending calculation period (ENDDAT) |
| Starting calculation period (STRDAT2) |
|
This field is only used for the allocation structures that use the following distribution types: Calculated amount or Calculated Quantity. It corresponds to the reference period used in the calculation of the distribution coefficients. The purpose of these distribution types is to distribute the balance (in amount) or the quantity (in non-financial units) of each selected dimension into all the other dimensions in proportion to the postings of the selected dimensions on a distribution nature. The purpose of the Calculation period is to:
Example:
The aim is to distribute these expenses into the other departments in proportion to their sales (distribution nature: "Sales") recorded for the period ranging from 01/01/07 to 31/12/07. The allocation period ranges from 01/01/07 to 31/01/07. The coefficient calculation period range from 01/01/07 to 31/12/07. The advertising expenses posted to the "Administration" dimension are distributed into the Departments 1 and 2 in proportion to the sales achieved by these two departments over a period which ranges from 01/01/07 to 31/12/07. The distribution coefficients are calculated over this period. The range of the coefficient calculation period matches the definition of accounting periods. It is possible to define a coefficient calculation period over multiple accounting periods of the same fiscal year. In that case, the range of these periods must be respectively the start date of the first accounting period and the end date of the last accounting period. By default, the range for this period corresponds to the current fiscal year.
|
| Ending calculation period (ENDDAT2) |
| Generation type (GENCAT) |
|
Select the generation type:
|
| Entry status (GENSIM) |
|
When the generation type is Actual, you also need to select:
|
| Transaction (DACDIA) |
|
The entry transaction must be selected before starting the journal entry. The action Transaction, accessible from the Display/Choose the transaction menu, opens a selection window with all the entry transactions. After selecting a transaction, only the documents entered through this transaction are displayed in the selection list, provided that the transaction setup authorizes it. The selected transaction allows you to create, modify, or view a journal.
"Tab" transaction types do not allow for the creation or modification of journals. The Transaction field is initialized according to the selected entry transaction. Four standard transactions are delivered:
A journal can only be viewed:
A default entry transaction can be added to the user favorites. |
| Entry type (GENTYP) |
|
The type of analytical journal to be generated. See the documentation on Document types for further details.
|
| Journal (GENJOU) |
|
This is the posting journal of the generated document. It must be consistent with the document type. Any recalculation of the same allocation structure, for the same period or a period different from the initial calculation, cancels the active simulation documents created during the first calculation. It generates either new active simulation documents or actual documents, depending on the chosen generation type. The postings generated by the calculation of the structures are recorded in the entered analytical journal. Journal codes can apply to a specific company, a specific site, or a specific group. This information is defined when the journal code is created but the selection window for this field (using the selection tool) does not consider it.
The controls apply when you select or confirm the journal code. You can amend the journal code if it is not valid. |
| Entry date (GENDAT) |
|
The posting date of the generated entries. |
| Entry description (GENLIB) |
|
Enables the header description for the journal postings when a value is entered. |
| Log file (TRC) |
|
Generates a log file if the checkbox is selected. |
This function can be run in batch mode. The standard task "dimensional allocations" (CPTDSPANA) is provided for that purpose.
| Memo | Select this action to save the current settings to reuse later using a unique memo code. The memo code is linked to your user profile, not to the function or the screen. |
| Recall | Enter or select the unique memo code you created to apply the settings saved with that code. |
| Delete memo | This action deletes a saved memo code and cannot be undone. |
| Memo code (CODE) |
|
This field is used to save the criteria applied to an entry screen. It shows if a memo code has already been saved for the current screen values. The following buttons can be used to manage memos: Recall: Recall a previously defined and saved memo. Memo: Save the current values of the screen in a memo file with a code to be specified. Del. Memo: Delete a previously saved memo. If a STD (standard) memo is associated with the screen, it loads when opening the function. |
|
Memo |
This action saves the current settings to a Memo code that can be reused later. The memo is linked to your user profile. The STD memo code is linked to the screen and is loaded immediately when you open the function. Refer to the documentation on the General ergonomics of SAFE X3 software for more information on the advanced use of the Memo action.
|
|
Recall |
This action loads the settings linked to the code when entering a Memo code. |
|
Delete Memo |
This action can be used to delete a Memo code. |
The function does not use automatic journal process. As a result, the double-entry method is not available for managing and generating accounting documents.
When an allocation setup is defined with several lines and allocation rules, and when Processing based on balances is not selected, the lines are independent from one another:
If the Processing based on balances checkbox is selected when the reallocation journal entries are created, the analytical balance updates automatically, and the original amounts from the reallocated amount from previous lines can no longer be identified.
Whether the Processing based on balances checkbox is selected or not, the following cases are not managed:
The reallocation process then generates journal entries where the sign of the ledger amounts is incorrect on the automatic ledger.
The journal entry line is not generated by the dimensional allocation process when the line amount is less than 0.01 in the currency transaction for the selected ledger type.
This can occur when the selected ledger type is not linked to an automatic ledger type, for any ledger currency amount of the line.
When an account and dimension combination is not balanced in the transaction or ledger currency, the journal entry is not generated. The log file that displays after the process shows the line or lines of the dimensional allocation structure (GESDAD) that are affected.
In addition to the generic error messages, the following message can appear on entry:
Document type XXXXX is not of single ledger type YYY"XXXXX" corresponds to the entry type for this allocation.
"YYY" corresponds to the ledger type related to analytical balance on which the allocation entries are calculated and generated.
This message is displayed to signal that one of the chosen entry types is not consistent with the ledger type entered on the screen.