R12/CE: Bank Statement Loader Main Program Completes Before Spawned Programs Complete
(Doc ID 1930238.1)
Last updated on FEBRUARY 22, 2019
Applies to:Oracle Cash Management - Version 12.1.3 and later
Information in this document applies to any platform.
Customer has created a request set with two programs added:
Bank Statement Loader (standard) - with process option, 'Load'
Bank Statement Archive Program (custom) - to purge the bank statement file loaded in server
The Bank Statement Loader program internally spawns the below programs:
Run SQL*Loader- SWIFT940
Load Bank Statement Data
Load Bank Statement Data Execution Report.
The main program, Bank Statement Loader completes before the other programs are completed and irrespective of the status of the other programs the main program always completes normal.
As a result, Archive program is kicked off before child programs complete and bank statement file archived even before the child programs process the file.
Expect the bank statement loader program to be complete only when the child programs have completed.
This is stopping users from kicking off the Archiving program as the main program completion status cannot be used to kick off other requests in the request set. Some times even the file is not processed yet the archival program which is part of the request set gets kicked off and archives the bank statement. This is stopping business from processing bank statements correctly.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document