Allocation Processing
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:
- Entries with currencies different from those of the main general ledger
- Allocation of several dimensions to a single receiving dimension and generates as many entries as there are dimensions
Read the documentation for Partner initialization and Flow initialization.
Prerequisites
Refer to documentation Implementation
Screen management
Entry screen
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
Company (field CPY) |
Enter the company code or use the Look up tool to search for and select the code. |
Criteria
Allocation (field DIA) |
Enter the name of an allocation setup that was defined in Dimension structures. |
Site (field SITE) |
This code is used to identify the site concerned. It is unique for each site. |
All users (field ALLUSR) |
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. |
User (field 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. |
Generation
Starting allocation period (field STRDAT) |
The period to be distributed is the period taken into account 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 is that of the current financial year. |
Ending allocation period (field ENDDAT) |
Starting calculation period (field STRDAT2) |
This field is only used for the allocation structures that use the following distribution types: Calculated amount or Calculated Quantity.
For example:
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. |
Ending calculation period (field ENDDAT2) |
Generation type (field GENCAT) |
Select the generation type:
|
Entry status (field GENSIM) |
When the generation type is Actual, you also need to select:
|
Transaction (field DACDIA) |
The entry transaction must be selected before starting the journal entry . According to the selected transaction, you have the option 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 entry transaction selected. Four standard transactions are delivered:
A journal can only be viewed by means of:
A default entry transaction can be added to the user favorites. |
Entry type (field GENTYP) |
Enter the type of analytical journal to be generated. |
Journal (field GENJOU) |
This is the posting journal of the generated document. It must be consistent with the document type. 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 take this into account. These controls are applied when you select or confirm the journal code. You can amend the journal code if an error message warns that it is invalid. |
Entry date (field GENDAT) |
Posting date of the generated entries. |
Entry description (field GENLIB) |
Entering a value to enable the header description for the journal postings. |
Log file (field TRC) |
Select this check box to generate a log file. |
Batch task
This function can be run in batch mode. The standard task CPTDSPANA is provided for that purpose.
Specific Actions
Memo code (field CODE) |
You use a memo code to save the criteria applied to an entry screen. Use this field to find out if a memo code has already been saved for the current screen values. Use the following buttons 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 memo named STD (standard) is associated with the screen, it is loaded when opening the function. |
Recall |
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. |
Limitations
Managing and generating accounting documents using the double-entry method is not available for this function because it does not use an automatic journal process. Only functions that use an automatic journal process can use the double-entry method for a company.
Multiple allocation lines
When an allocation setup is defined with several lines and allocation rules, these lines are independent from one another when Processing based on balances is not selected:
- The reallocation journal entries generated by the upper lines are not taken into account by the subsequent allocation lines when amounts to reallocate are calculated.
- The Dimensional allocations (CPTDSPANA) process excludes all the journal entries that have been generated by the allocation code in process from amounts to reallocate.
If the Processing based on balances check box is selected, when the reallocation journal entries are created, the analytical balance is automatically updated and it is no longer possible to identify the original amounts from the reallocated amount from previous lines.
Distribution allocation is run on a manual ledger type linked to an automatic ledger type
Whether the Processing based on balances check box is selected or not, the following case is not managed:
- The amount to allocate, in the document transaction currency, is different from zero.
- In the manual reallocated ledger type, the amounts in document currency and ledger currency have a given sign.
- In the automatic ledger, the sign of the ledger amount is the reverse of the one in the linked reallocated ledger type.
The reallocation process then generates journal entries where the sign of the ledger amounts is wrong on the automatic ledger.
The KRU - Russian legislation activity code must be active to use the double-entry method for a company.
Error messages
In addition to the generic error messages, the following messages can appear during the 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 entry types chosen is not consistent with the ledger type entered on the screen.