This function is used to perform a mass validation of a selection of accounting batches entered in the Batch entry function (GESLOT).
The validated batches are then posted (generation of accounting entries).
Although the Partner and Flow fields are not part of the Batch entry function (GESLOT), the rules for Partner initialization and Flow initialization follow the same rules used for generating journal entries. The same rules also apply to any controls for the partner and flow fields.
Read the documentation for Partner initialization and Flow initialization.
Refer to documentation Implementation
The status of postings in the launch screen must be "Definitive" when the "Actual" journal category is selected and when the company is:
Presentation
This process performs a "bulk" validation of accounting batches. Once the validation process has been started, a journal is generated for each of the operations recorded via batch entry.
This journal is used to transfer the documents entered for each batch to the document entry program.
The validation process in simulation mode (activated or not) makes it possible to modify and revalidate the journal batch. In that case, the entries last transferred cancel the previous ones.
In real mode, the journal batch can neither be modified not revalidated.
In that case, the possible choices are:
Close
Fields
The following fields are present on this tab :
Criteria
|
If this box is checked, the processing is launched for all the companies (otherwise, they have to be specified). |
|
This is the code of the assignment company of the entity. |
|
  |
|
If this box is checked, the processing is launched for all the companies (otherwise, they have to be specified). |
|
This title is associated with the previous code. |
|
When this box is checked, the data associated with all the users are involved by the process (if it is not checked, only the user whose code is given is involved (if no code given, the current user). |
|
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. |
Selection
|
No help linked to this field. |
|
  |
Generation
|
This field indicates the category of the documents to generate.
|
|
In the event of an actual generation, the status of the journal can be:
The entry status for entries must be Final when the requested generation type is Actual and the company meets one of the following criteria:
In temporary mode, most of the information displayed on the journal can be modified. The modification options can vary based on:
|
|
When checked, this box is used to delete the lot record in lot entry when it is posted. |
|
If checked, this box is used to summarize all the validated journals at the end of a processing. |
Close
This function can be run in batch mode. The standard task ACCLOT is provided for that purpose.
|
|
The management and generation of 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.
The KRU - Russian legislation activity code must be active to use the double-entry method for a company.
In addition to the generic error messages, the following messages can appear during the entry :
" Batch xxx line y unmatched journal "Batch xxx cannot be validated, line y has no offset.
If the processing is launched for a given company and this company has selected Conformity DGI no. 13L-1-06 (i.e. the value of setup FRADGI/chapter TC/group CPT is 'yes'), the documents generated by the processing will have the status 'Final'.
The processing is launched for all companies or a group of companies, and if at least one of the companies chose Conformity DGI no. 13L-1-06 (i.e. the value of setup FRADGI/chapter TC/group CPT is 'yes'), the documents generated by the processing will have the status 'Final'.