Refer to documentation Implementation
Fields
The following fields are present on this tab :
Grid List
| This field displays the accounting task code. |
| 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. |
|   |
| 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. |
| 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. |
| 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. |
| 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. |
| This field indicates whether the task on the line is active or not according to the Journal status monitor setting (VALPCE). |
Block number 2
Block number 3
Close
Action icon
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.
Close
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. |