Use this function to define accounting tasks. Accounting tasks are based on automatic journals and update accounting information including:

  • Operations performed in other modules, (i.e., invoice validation, stock movement posting, payment validation, depreciation charges)
  • Particular operations performed in the Financials module, (i.e., conversion variance, fiscal year end, matching)

Accounting tasks can take up system resources and impact performance. You can define multiple accounting tasks to improve resource allocation.

A task is associated with the following elements:

  • A criteria defining the task scope: The task is active for one or multiple companies.
  • One or several operation types:
    • Posting: create accounting entries.
    • Matching: complete matching operations.
    • Balance update: Update balances (general, dimension, etc.) distinct from creating accounting entries. Balance updates are included if the UPDBALBTC - Balance update desynchronization parameter (CPT chapter, ACC group) is set to Yes. Otherwise, the balance update is performed when creating accounting entries.

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to Yes:

You can create one accounting task per line. For each task, a unique recurring task linked to the correct folder is automatically created when the tasks are activated.

You can only Activate or Deactivate a task in the Journal status monitor function (VALPCE).

For each task, you can define the Periodicity and Time range in Recurring tasks (GESABA) while the task is Inactive.

You can delete an Inactive task. This also deletes the related recurring task.

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to No:

There is only one accounting task.

You cannot modify the Periodicity and Time range in Recurring tasks (GESABA).

You can only enter the No. of records while the task is Inactive.

You can only Activate or Deactivate a task in the Journal status monitor function (VALPCE).

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Grid List

Task (field COD)

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

This field displays the unique recurring task code, which is automatically generated for each accounting task when the task is Activated in the Journal status monitor function (VALPCE).

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to Yes, there is a unique recurring task for each accounting task on the line.
Criteria (field CRI)
Posting (field ACC)

Select Yes to post accounting entries.

This option is only available if the MULBATCH - Multi-instance batch task parameter is set to Yes and if the current accounting task is not active.

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to No, you cannot modify this field.
Matching (field MTC)

Select Yes to complete the matching operation. This option is only available if the MULBATCH - Multi-instance batch task parameter is set to Yes and if the current accounting task is not active.

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to No, you cannot modify this field.
Balance update (field BAL)

Select Yes to include balance updates in the account task process. The number of balances is included in the No. of records to process for each task.

This option is only available if the UPDBALBTC – Update balance parameter is set to Yes (CPT chapter, ACC group).

This option is only available if the MULBATCH - Multi-instance batch task parameter is set to Yes and if the current accounting task is not active.

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to No, you cannot modify this field.
No. of records (field NBRREC)

Enter the maximum number of records to be processed for each task. If you include Balance updates, the number of balances is included in the total number of records to be processed.

For example, with No. of records set to 100:

1) If there are 100 or fewer total records to process, including balance updates, the task only needs to run one iteration to completely process all records.

2) If there are 150 records to process not including balance updates, the task runs an initial iteration on the first 100 records. After the Frequency in minutes defined in Recurring tasks (GESABA), the task runs a second iteration on the remaining 50 records.

3) If you include balance updates, 100 for example, the total number of records that needs to be processed is now 250. The task runs an initial iteration on the first 100, a second iteration on the next 100, and a third iteration on the last 50 records. There is a (n) minute pause between each iteration based on the frequency setting.

This option is only available if the current accounting task is not active.
Active (field ACT)

This field indicates whether the task on the line is active or not according to the Journal status monitor setting (VALPCE).

Block number 2

Recurring task

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

If the MULBATCH – Multi-instance batch task parameter (CPT chapter, ACC group) is set to Yes, there is a unique recurring task for each accounting task on the line.

Specific actions

Accounting task

Click this action to open the Journal status monitor (VALPCE). This window displays the details for each accounting task such as Status, Journals on hold, and Next execution.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation