Appendix: Technical details

This section covers information intended for a technical audience with advanced knowledge.

Upgrading

If you are upgrading from a previous version, you need to consider the following information.

During an upgrade, the following standard tasks from the previous version or release are deleted in the Task management function (GESABT):

  • ACCSTOP
  • ACCBATCH

Recurring tasks related to ACCSTOP and ACCBATCH are also deleted.

Processes linked to the accounting task

Certain processes require the accounting task to be active or inactive.

Some processes need the accounting task to be started or stopped to be executed. For example, the Dimensional allocations function (CPTDSPANA) needs the accounting task to be activated.

These processes are compliant with the new accounting task management.

Recurring task default activation

These rules do not apply to the recurring task templates, which are always inactive.

New accounting task installation

Result

Action

Recurring task created by a folder validation VALDOS
(1st installation: folder creation)

The recurring task is created as Inactive regardless of the MULBATCH parameter value.

You must activate them via the Accounting task function (VALPCE).

Recurring task created via migration (CPTMAJ90)

The recurring task is created as inactive regardless of the MULBATCH parameter value.

You must activate them via the Accounting task function (VALPCE).

Recurring task created by easy grade

If MULBATCH = No:

The recurring task linked to ACCENTRY is created and activated.

Recurring tasks linked to ACCENTRYxx are created and remain inactive.

None

Recurring task created by easy upgrade

If MULBATCH = Yes:

The recurring task linked to ACCENTRY is created and remains inactive.

Recurring tasks linked to ACCENTRYxx are created and activated.

None

 

Existing folders with new accounting task already installed

Result

Action

VALDOS performed on an existing folder with the new accounting task

 

If the recurring task code (CODABT) in the BATCH table is empty or incorrect, the recurring task (CODABT) is reinitialized in the BATCH table and created as inactive, regardless of the MULBATCH parameter value.

You must activate them via the Accounting task function (VALPCE).

If the recurring task code (CODABT) in the table BATCH is correct, the recurring task is deactivated, regardless of the MULBATCH parameter value.

You must activate them via the Accounting task function (VALPCE).

Recurring task created manually from the Accounting tasks function (GESBTC)

The recurring task is created as inactive when MULBATCH = Yes. When MULBATCH = No, the Accounting tasks function (GESBTC) grid cannot be modified.

You must activate them via the Accounting task function (VALPCE).

Recurring task creation

  • If the recurring task code (CODABT) in the BATCH table is empty, the recurring task is created according to the logic explained in the grid above.
  • If the recurring task code (CODABT) in the BATCH table is incorrect (for instance recurring task code associated to a folder different from the current one) the recurring task code (CODABT) in the BATCH table is reinitialized and created according to the logic explained in the grid above.
  • If the recurring task code (CODABT) in the BATCH table is defined and correct, when the processes described in the grid above are executed, the existing recurring task are not modified.

Exceptions for Accounting task (VALPCE)

Normally, the recurring task is always generated correctly and associated with the correct accounting task when the recurring task has been generated by the following processes:

  • Via VALDOS
  • Via migration
  • After the upgrading from version 2018.R7 to 2018.R8
  • Manually via Accounting tasks (GESBTC)

However, if something went wrong, another control is performed in the Accounting task function (VALPCE) to recalculate the recurring task and to assign it to the correct accounting task.

  • If in the Accounting task function (VALPCE), the recurring task is incorrect, there is no recurring task associated with the accounting task lines (meaning CODABT is empty in the BATCH table).
  • When you click Activate, the recurring task(s) is created as active and is also updated in the Accounting tasks function (GESBTC) according to the MULBATCH parameter setting.

Example: MULBATCH = Yes

In Accounting tasks (GESBTC): Two lines are defined for ACCENTRY01, ACCENTRY02, but none of them have a recurring task defined.

In Accounting task (VALPCE): Two lines are visible for ACCENTRY01 and ACCENTRY02, but no recurring task is defined.

If you activate the accounting tasks:

  • Two recurring tasks are created in the Recurring tasks function (GESABA) for ACCENTRY01 and ACCENTRY02 and are set to active.
  • Accounting tasks (GESBTC) records are updated for the accounting tasks ACCENTRY01 and ACCENTRY02.
  • The Accounting tasks (GESBTC) record linked to the ACCENTRY accounting task is not modified.