Process description

This section explains how accounting batch tasks operate.

Accounting task (VALPCE)

For each accounting task on the line, you can access the Accounting task function to view details such as Status, Journals on hold, and Next Execution.

You can only activate or deactivate an accounting task from this function.
  • When the accounting task is activated, if the server time is within the time range defined on the recurring task, the ACCBATCH1 task is submitted to the batch server.
  • The Query field shows the ACCBATCH1 task’s query number currently executed or to be executed.
  • The Next Execution field shows when the next ACCBATCH1 task will be executed.

When you activate a task in the Accounting task function (VALPCE), if the server time is within the time range defined for the recurring task, the task is submitted to the batch server.

Query management (AREQUETE)

In Query management, you can check the previous ACCBATCH1 task executed and the one currently being executed. In the image below, task number 2467 has finished and task number 2468 is on standby.

If you set up multiple accounting tasks, the batch server executes as many ACCBATCH1 tasks as there are accounting tasks.

Examples

These examples show how records are processed for each iteration of the batch task depending on certain conditions.

Conditions: MULBATCH = No, only one task, ACCBATCH1 is running

  • ACCBATCH1 number 2468 is going to be executed.
  • ACCBATCH1 number 2467 is the task previously executed.
  • When task number 2468 is finished, task number 2467 is purged.
  • A new task number 2469 is put on standby. ACCBATCH1 number 2468 becomes the accounting task previously executed.

Conditions: MULBATCH = No, UPDBALBTC = No, No. of records = 100

  1. Initial state: Activate the accounting task with 130 records on hold (80 Journals on hold + 50 Matching).

  1. When the recurring task is in progress, the recurring task processes the records on hold up to 100 records out of 130; 30 records are not processed during the first iteration.

  1. If all the records on hold are processed or the maximum number of records is reached,  the recurring task pauses for one minute.

  1. After one minute, the recurring task restarts and processes the remaining records, up to 100; 30 records processed during the second iteration.

  1. If all the records on hold are processed or the maximum number of records is reached, the recurring task pauses for one minute.

If the No. of records had been set to 130 or more, all the journal entries and all the matching on hold would have been processed in one iteration (80 Journals on hold + 50 Matching = 130 records).

Because the UPDBALBTC - Balance update parameter was No, the balance is updated directly and not included in the batch task operation. And, the Balance Update column does not display.

Conditions: MULBATCH = No, UPDBALBTC = Yes and Balance update = Yes (in the Accounting tasks function), No. of records = 100

  1. Initial state: Activate the accounting task with 130 records on hold (80 Journals on hold + 50 Matching).

  1. When the recurring task is in progress, the recurring task processes the remaining records, up to 100 out of 130; 30 records are not processed.

  1. If all the records on hold are processed or the maximum number of records is reached, the recurring task pauses for one minute. There are now 80 records for Balance Update that need to be processed.

  1. After one minute, the recurring task restarts and processes the remaining records, up to 100 out of 110 (80 Balance Update + 30 Matching); 10 records are not processed.

  1. If all the records on hold are processed or the maximum number of records is reached, the recurring task pauses for one minute.

  1. After one minute, the recurring task starts again and processes the remaining 10 records.

  1. If all the records on hold are processed or the maximum number of records is reached, the recurring task pauses for one minute.

If the No. of records had been set to 210 or more, all records on hold would have been processed in one iteration (80 Journals on hold + 50 Matching + 80 Balance Update).

Because the UPDBALBTC parameter and the Update Balance field are set to Yes, the number of balances to update is included in the number of possible records the accounting task can process during one execution.