Event "oracle.apps.fnd.concurrent.program.completed" subscription fails with 3203: Attribute 'TIME_STAMP' does not exist for notification
(Doc ID 2787542.1)
Last updated on OCTOBER 10, 2021
Applies to:
Oracle Workflow - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.9 version, Workflow Events
oracle.apps.fnd.concurrent.program.completed is completing but resulting into error.
The event "oracle.apps.fnd.concurrent.program.completed" is firing in all scenario, but resulting into Workflow Event Error.
Local Event ERROR : oracle.apps.fnd.concurrent.program.completed / 39601823:20210521085942:05
Local Event ERROR : oracle.apps.fnd.concurrent.program.completed / 39601799:20210521085417:05
ERROR
-----------------------
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run the Concurrent Program that should trigger the oracle.apps.fnd.concurrent.program.completed Business Event.
2. The event "oracle.apps.fnd.concurrent.program.completed" fails
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot Use Business Events To Send Notifications When A Spawned Report Completes
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |