Using override threading on the Calculate Payments action

Administrators must enable the Override Threading On Calculate Payments feature on the Feature Toggle page.

See the Infor HR Talent Feature Toggle Administration Guide.

Use override threading on the Calculate Payments action to process a high volume of employee payments. For example, if you have 10,000 or more employees. You can set the threading to two or three times the current queue size for payroll cycle actions.

Threaded actions divide the work to be processed during the Calculate Payments action. The smaller units of work are processed faster in a balanced manner. With this setting, jobs are queued for processing instead of being allocated to the maximum actions in the queue.

  1. Select Payroll Administrator > Setup > Payroll Configuration.
  2. Open a country configuration.
  3. Click the Payroll tab.
  4. Select the Enable Threading On Override Payments check box.
  5. Click Save.
  6. Select Administrator > Utilities > Action Configuration.
  7. Select the item with a PaymentSchedule class and a CalculatePayment action.
  8. Click Change Number of Threads.
  9. In the Number Of Threads field, specify 1x, 2x, or 3x for 1x, 2x, or 3x the size of the queue.
  10. Click Submit.

    If the value is set to 2x or 3x, a confirmation message is displayed. The message indicates that the number of threads exceeds the maximum active actions for the assigned async queue. Click OK.

    If the value is set to a value that is not 1x, 2x, or 3x, a confirmation message is displayed. The message indicates that the number of threads should be 1x, 2x, or 3x the queue size. Click OK, but we recommend that values of 1x, 2x, or 3x to avoid performance issues.

    When the feature is enabled, a blue alert is displayed on the field with a CalculatePayments action.

    When the Number Of Threads value is changed to a value other than the defined thread for payroll cycle actions, a blue alert is displayed.

    When the Calculate Payments action is performed, the job is threaded according to size that is defined. Threads are in a queue waiting to run upon completion of other active threads. Because the new threads are smaller than previous threads, the new threads are completed faster.