Periodic Scheduled Concurrent Program Submitted With Incorrect Operating Unit After First Run
Last updated on DECEMBER 19, 2017
Applies to:Oracle Alert - Version 12.2.6 to 12.2.6 [Release 12.2]
Oracle Application Object Library - Version 12.2.6 to 12.2.6 [Release 12.2]
Oracle Concurrent Processing - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
The first time a periodic scheduled concurrent program is submitted, where the Operating Unit passed as NULL, it submits fine with ORG_ID as NULL and inserts ORG_ID value as NULL in the fnd_concurrent_requests table.
For the second and consecutive runs for the scheduled program, the scheduler process inserts ORG_ID value as zero in the fnd_concurrent_requests table.
The issue occurs for any concurrent programs that are scheduled and have no specific Operating Unit parameter.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms