Use this function to define recurring tasks that are launched regularly by the batch server. These recurring tasks are run based on a defined schedule. This includes batch tasks or linked batch tasks. You can define all or part of the settings linked to the task execution rules such the current period and frequency.

For Accounting batch tasks

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to Yes, you can create one accounting task per line in the Accounting task function (GESBTC). Each task is linked to a unique recurring task linked to the correct folder.

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to No, there is only one accounting task.

WarningYou cannot change the Active status of an accounting recurring task in this function. This can only be done in the Journal status monitor function (VALPCE). You can find more information about the VALPCE function here.

Prerequisites

See also Refer to documentation Implementation

Screen management

Entry screen

Here are entered both the launch conditions (identification of the folder and the user under whose identification the recurring task is launched) and the concerned times.

Specific Buttons

Parameters

This action opens the parameters for the task. When a group of tasks is launched, an intermediate window opens where you can choose the task and its settings.
 
Since 2025 R1/V12.0.37, the display of the intermediate window can differ depending if a Group code has been defined for the task. If the Group code has been defined , the intermediate window displays the sequence (related to the task), group code and sequence (related to the group code). If the Group Code has not been defined for the task, the intermediate window displayed is the classic representation.
 
Note: This action is not configured to handle a group of tasks containing a subgroup that contains subtasks.

Error messages

The only error messages are the generic ones.

Tables used

See also Refer to documentation Implementation

Technical operation of the recurring tasks

When starting the batch server (or after midnight, when the batch server operates continuously), all the recurring tasks in a day are created in the form of task execution requests that can be seen in batch task management.

For recurring tasks with a defined frequency, a single execution request is created; when the task is executed, a new execution request is created.

This means once the first execution for a recurring task with a defined frequency is launched:

  • In the request management, any interruption (if it is in progress), or deletion (if it is pending) of the next execution stops the process, which will be launched again the following day.
  • By default, any modification to the frequency will not be taken into account until the following day.