ARLCPW - 'Create Late Charge Documents per Worker and Batch' Child Program is Always Spawned with 4 Workers, Even When Changing Number of Workers in the Program Definition (Doc ID 2967892.1)

Last updated on NOVEMBER 06, 2023

Applies to:

Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

The Late Charges process is having locking issues when executed for all customers in a single run, and selecting 'Final' mode from the Batches Maintenance form.
Generally, the process for late charges is run in two steps:
- First, submit Late Charges Generate program in 'Draft' mode to generate the batch.
- Then, query the batch and submit the process in 'Final' mode with status 'Transferred'.
When there is a large number of customers, the Late Charges process may fail due to locking issues, and the log file may show the error message listed below:

The above error may also be captured in the FND Debug log.
The complete steps are listed below:

Responsibility: Receivables Responsibility
Navigation: Late Charges > Generate Late Charges

1. Submit Late Charges Generate program in Draft mode.
2. Once the above program completes, navigate to Late Charges > Batch Maintenance
3. Query the batch created in step 1, and change the Mode to ‘Final’ and Status to ‘Transferred’.
4. Click on the ‘Generate’ button
5. This submits the program ARLCSM-'Create Late Charge Documents per Batch', which has the number of 4 workers hard-coded for the child program ARLCPW- 'Create Late Charge Documents per worker and batch'

Locking issues on the workers mentioned above may occur when processing data for large number of customers. In this case, the ORA-00054 error is raised.
Trying to run the child program with only one worker to avoid the locking is not possible, even when changing the number of workers in the definition of the program ARLCSM via System Administrator > Concurrent > Program > Define
Still 4 workers are spawned for the child program as the number of workers is hard-coded in the code. Normally, there is no issues with the workers, but in certain case scenarios locking issues have been reported.