How
to Integrate Business Events in Concurrent Processing?
This
functionality has been introduced in Oracle Application Release 12.1.
Concurrent programs can
be integrated with the Business Event System in Oracle Workflow. Business
events can be raised at key points of the life cycle of a request to run a
concurrent program. Users can subscribe to the business events and create their
own business processes interacting with the concurrent programs.
Navigation
System Administrator
Responsibility > Concurrent > Program > Define
Here you specify the points at which business events are enabled. The possible points are:
- Request Submitted
- Request On Hold
- Request Resumed
- Request Running
- Program Completed
- Post Processing Started
- Post Processing Ended
- Request Completed
Possible parameters for
each event are:
- REQUEST_ID
- REQUESTED_BY
- PROGRAM_APPLICATION_ID
- CONCURRENT_PROGRAM_ID
- STATUS
- COMPLETION_TEXT
- TIME_STAMP
Change profile
There is a new profile
"Concurrent: Business Intelligence Integration Enable". This has to
be set to "Yes" to enable Business Events from Concurrent Processing
System
Workflow - Create Event
& Subscription to link Events
You need to create Event
Subscription from Workflow Administrator. An event subscription is a
registration indicating that a particular event is significant to a particular
system. An event subscription specifies the processing to perform when the
triggering event occurs.
For
EXAMPLE - Refer this Note
How To Use Business
Events To Send Notifications when a Spawned Report Completes (Note
1506980.1 )
How to Send Email Notification from one report that is a part of a
Payment Process that creates multiple spawned reports?
Usually
the method of Sending Email Notifications with a report is allowed as a
Delivery Option in the Concurrent Request Submission form, but it is only
applicable to a single report. In the case when the concurrent program is
similar to a request that spawns multiple reports there is no option to choose
an individual report from the parent report.
Note
1161254.1 - "EBS 12.1
How to Integrate Business Events in Concurrent Processing?" describes how
a Business Event can be used with a Concurrent Program. In addition to
the steps in Note
1161254.1, the ability to "Send Notification" through a Business
Event is documented below.
FIX
In Release 12.1 and up, there is a the ability to create a
Business Event Subscription that is triggered when a Concurrent Program is run.
The Business Event feature offers customer's the option of Notifying through
email by selecting the "Action Type = Send Notification".
NOTE: These steps should be used in conjunction with Note: 1161254.1 EBS 12.1 How to Integrate Business Events in Concurrent Processing?
NOTE: These steps should be used in conjunction with Note: 1161254.1 EBS 12.1 How to Integrate Business Events in Concurrent Processing?
1. Login to E-Business Suite as SYSADMIN.
-
Enable profile option: Concurrent:
Business Intelligence Integration setting
Enable=Y at the Site Level > and SAVE.
2. In step 1 of Note 1161254.1, one is telling the concurrent program that once it completes it should raise the event indicating that the request has reached any of those status in the squared area (submitted, resumed, completed, etc).
Select "Program Completed"
Ex:
2. In step 1 of Note 1161254.1, one is telling the concurrent program that once it completes it should raise the event indicating that the request has reached any of those status in the squared area (submitted, resumed, completed, etc).
Select "Program Completed"
Ex:
a) Concurrent > Program > Define
b) Choose Concurrent Request: "Format Payment Instruction
with Text Output" IBY_FD_PAYMENT_FORMAT_TEXT > Check the
"Program Completed" > SAVE
3. Check that the proper System Name is associated with the "Business Event Local System":
a) Login to E-Business Suite as SYSADMIN.
b) Select "Workflow Administrator Web Applications" Responsibility.
c) Select "Administrator Workflow" > then "Administration".
d) Select the proper system name under Business Event Local System > Apply.
b) Select "Workflow Administrator Web Applications" Responsibility.
c) Select "Administrator Workflow" > then "Administration".
d) Select the proper system name under Business Event Local System > Apply.
4. Check that the Business Event oracle.apps.fnd.concurrent.program.completed is enabled:
a) Business Event Tab > Query the
Name"oracle.apps.fnd.concurrent.program.completed" > Go.
b) Change the status from Disabled to Enabled.
c) Click on Apply button.
b) Change the status from Disabled to Enabled.
c) Click on Apply button.
5. Create the Subscription for the Business Event "oracle.apps.fnd.concurrent.program.completed":
a) Click on the "Subscription" Icon >
Create Subscription.
b) Give the specifics for the Subscription:
b) Give the specifics for the Subscription:
*** This is an Example of Required Fields when
creating the Subscription
*** This is where to specify the "Action Type =
Send Notification"
Create Subscription
--------------------------
Subscriber
* System = VIS.US.ORACLE.COM
Triggering Event
------------------
* Source Type = Local
* Event Filter = oracle.apps.fnd.concurrent.program.completed
* Source Agent =
Execution Condition
-----------------------
* Phase = 100
* Status = Enabled
* Rule Data = Message
Action Type
-----------------
Action Description
-------- ------------
* Action Type = Send Notification Send a notification using standard or your own message templates
* On Error = Stop and Rollback
Action
* Message Type = CSM_MSGS (this an example)
* Message Name = FYI_MESSAGE
* Recipient = USER_A
* Priority = Normal
Documentation
---------------
* Owner Name = FND
* Owner Tag = FND
> APPLY
Create Subscription
--------------------------
Subscriber
* System = VIS.US.ORACLE.COM
Triggering Event
------------------
* Source Type = Local
* Event Filter = oracle.apps.fnd.concurrent.program.completed
* Source Agent =
Execution Condition
-----------------------
* Phase = 100
* Status = Enabled
* Rule Data = Message
Action Type
-----------------
Action Description
-------- ------------
* Action Type = Send Notification Send a notification using standard or your own message templates
* On Error = Stop and Rollback
Action
* Message Type = CSM_MSGS (this an example)
* Message Name = FYI_MESSAGE
* Recipient = USER_A
* Priority = Normal
Documentation
---------------
* Owner Name = FND
* Owner Tag = FND
> APPLY
6. Check to make sure the Subscription is added to the Business Event:
a) Business Event > Query -
oracle.apps.fnd.concurrent.program.completed > Drill down on
"Subscriptions"
7. Check whether raising the business event is now working, by select "Run":
Business Events > Query >
oracle.apps.fnd.concurrent.program.completed
Click Test (over in the right side)
Notice: Business Event has been raised - message.
Click Test (over in the right side)
Notice: Business Event has been raised - message.
8. Check the WF_NOTIFICATIONS table to see if a new record is created:
In sqlplus apps/
SQL> select * from
wf_notifications order by 1 desc
NOTIFICATION_ID
4682893 4682893 WFERROR DEFAULT_EVENT_ERROR SYSADMIN OPEN 203626643180155389996808706742823752864 SENT
4682892 4682892 WFSTD WFSTD_DEFAULT_VOTE USER_A OPEN 127521793540816397462516875018174582244 SENT
Note: that the subscription has generated a Notification and was Sent by the Workflow Mailer.
4682893 4682893 WFERROR DEFAULT_EVENT_ERROR SYSADMIN OPEN 203626643180155389996808706742823752864 SENT
4682892 4682892 WFSTD WFSTD_DEFAULT_VOTE USER_A OPEN 127521793540816397462516875018174582244 SENT
Note: that the subscription has generated a Notification and was Sent by the Workflow Mailer.
9. Now test running the Concurrent Program that should trigger the oracle.apps.fnd.concurrent.program.completed Business Event.
