All accounting journals processed automatically (invoice validation, depreciation charges, stock interface, payment validation, etc.) are written to a temporary table within the database, and a batch process run by this function processes them for accounting. All matching operations are run in the same way.

Only journals processed directly can be entered in accounting and imported. All other journals are subject to a batch task: This batch task must be set up to find journals in accounting or the journals are on hold until the batch task is launched.

The accounting task can be inactive even when the launch query has already been saved. There could be several reasons:

  • The number of simultaneously active tasks set up for the batch server has been exceeded: The accounting batch task only starts once a sufficient number of tasks in progress have finished.
  • The batch task is going to be launched, but the waiting time defined in the batch server parameters means that the task has not been launched yet.
  • The task has been canceled or stopped during the process.

For further problems, view the queries in progress or processes in progress to identify the origin of the problem.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

The following information displays for each task:

  • Recurring task and Query statuses
  • The number of queries running for an active task or the number of queries that were launched for an inactive task. A status flag is linked to this query number to determine if the batch task is on Standby or if it has been stopped during the process.
  • The corresponding process number (depending on the operating system).
  • The number records waiting to be run.
  • The number of balance updates waiting to be run. This column displays if the UPDBALBTC - Balance update desynchronization parameter is set to Yes. (CPT chapter, ACC group).
  • The next execution date and time.

Grid List

Task (field COD)

This fields displays the accounting batch task code.
Recurring task (field CODABT)

This field displays the Recurring task code.
Recurring task status (field STA)

Status of the batch task which can have the values:

Inactive

The batch task is not launched. A growing number of entries await validation.

Active

The batch task is active.

Shutting down

Launching an order for shutting down the batch task. The batch task is shutting down.

Restart in progress

Launching an order for activating the batch task. The batch task is about to start.
Journals on hold (field NBRPCE)

Number of journals pending posting.

Matching (field NBRMTC)

Number of matching groups pending validation

Balance update (field NBRBAL)

Number of balance updates waiting to run.

This column displays if the UPDBALBTC - Balance update parameter (CPT chapter, ACC group) is set to Yes. The number of balance updates is included in the total number of records for each task.
Query (field RQT)

This field displays the number of queries running for an active task or the number of queries that were launched for an inactive task.
Query status (field FLAG)

This field displays the query status as Standby, In Progress, or Finished.
Next execution (field NEXTEXE)

This field displays the next execution day and time based on the Periodicity and Time range settings in Recurring tasks (GESABA).
Log

Select this option to view a log file for the task on the line.
Recurring task

Select this option to view the Recurring task on the line.

Specific Buttons

Activate

This turns on recurring task/s and selects the Active check box in the Recurring task function (GESABA).

Depending on the batch server settings, the task might not immediately start. Click Update to refresh the status.

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to Yes, clicking Activate generates the Recurring tasks for new tasks defined in Accounting tasks (GESBTC).

The task/s run according to the Periodicity and Time range (based on server time) settings in the Recurring task function (GESABA), not immediately upon clicking Activate.

You can only Activate or Deactivate tasks here. Never in the function (GESABA).

Deactivate

This turns off recurring task/s and selects the Active check box in the Recurring task function (GESABA).

You might need to Update the task to view the status change. Depending on settings, the status could go from Active, to Shutting down, to Inactive.

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to Yes, you can modify the Periodicity and Time range in Recurring tasks (GESABA) while a task is not active.

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to No, you cannot modify the Periodicity and Time range in Recurring tasks (GESABA). You can only enter the No. of records while the task is not active.

You can only Activate or Deactivate tasks here. Never in the function (GESABA).

Update

Setup

Error messages

In addition to the generic error messages, the following messages can appear during the entry :

The server is not active

This message is sent if the accounting task is launched but the batch server is not active. In this case, the launch request is recorded in the batch server but the task can only be launched if the batch server is running.

Tables used

SEEREFERTTO Refer to documentation Implementation