In Fusion Apps, the concept of Business Event & subscription is still in place, however it has become easy to raise business events in Fusion Apps, with lesser programming. In addition to this, the listener of the business events is implemented in SOA. In case of 11i and R12, we have a Workflow Event listener that runs within the R12 tech stack itself.
In case of 11i and R12, we used to raise the business events using
1. WF_EVENT.RAISE API from PL/SQL Layer
OR
2.oracle.apps.fnd.wf.BusinessEvent.raise from Java/OAF Layer.
In Fusion Apps, we can raise business events from the BC4J layer as well, for example Entity Objects in ADF model layer. To do something similar in R12 you will have to write a piece of java code as shown in appendix of this article. However Fusion Apps provides a configurable solution for raising the event.
These business events can be picked up by the SOA Layer. Of course you will need a SOA project in place, with a SOA component named mediator that can listen to your business events. The mediator needs to be configured to listen to the specific business events of interest. After the event is identified, mediator can route the flow for further downstream processing in SOA, typically using a BPEL process component.
Alongside the name of the Business Event and the conditions, you can raise payload for the business event that will be available as parameter to the SOA Layer.
The image below shows Entity Object, which has a tab for Business Events.![]()
![]()
In case of 11i and R12, we used to raise the business events using
1. WF_EVENT.RAISE API from PL/SQL Layer
OR
2.oracle.apps.fnd.wf.BusinessEvent.raise from Java/OAF Layer.
In Fusion Apps, we can raise business events from the BC4J layer as well, for example Entity Objects in ADF model layer. To do something similar in R12 you will have to write a piece of java code as shown in appendix of this article. However Fusion Apps provides a configurable solution for raising the event.
These business events can be picked up by the SOA Layer. Of course you will need a SOA project in place, with a SOA component named mediator that can listen to your business events. The mediator needs to be configured to listen to the specific business events of interest. After the event is identified, mediator can route the flow for further downstream processing in SOA, typically using a BPEL process component.
Alongside the name of the Business Event and the conditions, you can raise payload for the business event that will be available as parameter to the SOA Layer.
The image below shows Entity Object, which has a tab for Business Events.
