Previous	Next		Contents	Index	Glossary

The products listed below leverage the Oracle Workflow Business Event System for business process integration. A full description of each feature is documented in its respective product's User's Guide or Configuration Guide, if one is available.

See Also

Oracle XML Gateway

Oracle XML Gateway leverages the Oracle Workflow Business Event System to publish and subscribe to application business events of interest in order to automatically trigger message creation or consumption. Seeded Workflow functions are provided for use in Workflow processes to interact directly with the XML Gateway Execution Engine to generate outbound or to consume inbound messages. The outbound messages generated by the Execution Engine are made available to the downstream Workflow activity for processing. The Execution Engine consumes the inbound messages passed to it by a Workflow process.

Two item types are delivered with the XML Gateway: the XML Gateway Standard Item Type and the XML Gateway Error Processing Item Type.

XML Gateway Standard Item Type - The XML Gateway Standard Item Type includes the Raise Document Delivery Event, which is used to raise a business event from an existing Workflow process. This allows you to seamlessly integrate your existing Workflow process with Oracle XML Gateway to create an outbound XML message. The functions included with the XML Gateway Standard Item Type are Consume XML Document, Generate XML Document, Generate Trading Partner XML Document, Send Document, Transform XML, and Transaction Delivery Required.

Configure the seeded events and event subscriptions delivered by the Oracle E-Business Suite for pre-built XML messages in support of Business-to-Business or Application-to-Application integration.

XML Gateway Error Processing Item Type - The XML Gateway Error Processing Item Type contains error handling processes to manage errors detected by the Oracle Workflow Business Event System or Oracle XML Gateway. The error processes are: Default Error Process, ECX Engine Notification Process, ECX Main Error Process, ECX Main Inbound Error Process, ECX Main Outbound Error Process, Error Handling for Inbound Messages, and Error Handling for Outbound Messages.

The XML Gateway Error Processing Item Type supports two event activities: Receive Error and Receive Send Notification Event. The Receive Error event is used by the XML Gateway to indicate that the XML Gateway execution engine has detected an error. The Receive Send Notification Event is used to indicate that the execution engine has identified a need to send a notification for errors related to an inbound process.

Oracle Workflow error handling provides active error notification to the XML Gateway System Administrator or Trading Partner with support for the Workflow retry and reprocess features. The functions provided by the XML Gateway Error Processing Item Type are: ECX Reprocess Inbound, ECX Resend Outbound Message, Get ECX In Error Details, Get ECX Out Error Details, Get System Administrator Role, and Get Trading Partner Role.

For more information, see: Oracle XML Gateway User's Guide.

Oracle Payables

- When you confirm a payment batch or create a Quick payment, the Business Event System initiates this program which automatically sends an e-mail to each supplier that has a remittance advice e-mail address defined.

Send XML Payment - This business event is raised when a user formats a payment or a payment batch that uses the OAG XML payment program. This event starts the Process Payment Message workflow, which sends an XML Payment message to your FSP (bank).

XML Payment Confirmation - This business event is raised when the FSP (bank) sends a Confirm BOD XML message to the ERP. This event continues and completes the Process Payment Message workflow.

XML Payment Errors - This business event is raised when the FSP (bank) sends a Payment Errors XML message to the ERP. This event starts the Process Payment Errors Message workflow.

XML Payment Advice - This business event is raised when the FSP (bank) sends a Payment Advice XML message to the ERP. This event starts the Process Payment Advice Message workflow.

Oracle Receivables

In Oracle Receivables, when the AR Credit Management Application Process Workflow completes a credit review, the workflow raises the oracle.apps.ar.cmgt.CreditRequestRecommendation.implement business event. If you want to implement a custom credit decision, then use the Business Event System to create a subscription to this event.

Oracle Process Manufacturing (OPM)

Operation Approval - The Change Status window in Product Development starts the signature capturing process whenever an operation status change is requested. When the status of an operation is changed, the E-Signatures can be captured at multiple points in the process. Required signatures are captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them that their E-Signature must be entered before the status of the operation is changed to the requested status.

Routing Approval - When the status of a routing is changed, the E-Signatures can be captured at multiple points in the process. When the status change is requested, required signatures can be captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them that their E-Signature must be entered before the status of the routing is changed to the requested status.

Formula Approval - When the status of a formula is changed, the E-Signatures can be captured at multiple points in the process. When the status change is requested, required signatures can be captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them that their E-Signature must be entered before the status of the formula is changed to the requested status.

Recipe Approval - When the status of a recipe is changed, the E-Signatures can be captured at multiple points in the process. When the status change is requested, required signatures can be captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them that their E-Signature must be entered before the status of the recipe is changed to the requested status.

Validity Rule Approval - When the status of a validity rule is changed, the E-Signatures can be captured at multiple points in the process. When the status change is requested, required signatures can be captured online, while the event is happening in the window. Any users responsible for additional required signatures receive workflow notifications informing them that their E-Signature must be entered before the status of the validity rule is changed to the requested status.

OPM Process Execution E-Signature Events

Release Batch - Release batch is an event that signals that a batch has begun production, and that the automatic release ingredients have been consumed. The batch has an actual start date and the automatic release ingredients have actual quantities (if allocation was successful), supported by completed transactions.

Close Batch - Close Batch is an event that signals that a batch is completed and no further changes are made to the batch data. Close Batch assigns a date to the actual close date and changes the status of the batch to closed. Once the batch is closed, you can no longer make any adjustments, insertions, or deletions to the batch.

OPM Inventory Events

Item Events - When an existing item is modified, any E-Signatures required are captured online so that transactions requiring use of the item can function without interruption.

Lot Status Events - Approval of an OPM Lot Master and update of a Lot Master are performed online. When you are creating or updating a lot or sublot using the Lot Master window, the E-Signature event is raised when you save the data. This displays the E-Signature window. The new or updated data is not committed to the database unless all of the required signatures are obtained online, while the E-Signature window is open.

Quantities Events - Process Inventory transactions are configurable to capture E-Signatures and E-Records upon any of the following Inventory Quanitities transactions: Adjust Immediate, Create Immediate, Grade Immediate, Status Immediate, and Move Immediate transactions.

OPM Quality Events

Approval of Quality Specification - The approval of a Quality Specification consists of two separate events: the approval of a specification, and the approval of the specification validity rule. Both events require the capture of E-Signatures and E-Records. A specification is controlled by a status or through a workflow. Therefore, signatures for both creation and updates of specifications are deferred.

Results - Quality Results also require E-Signature and E-Record support. After all results are entered during a session, upon saving the results, the E-Signature event is raised by the window and the appropriate signoffs take place online. If all the necessary signatures cannot be fulfilled at this time, then the results cannot be committed to the database. Results for all listed tests do not have to be entered in order for the E-Signature event to be raised; if one or more test results are entered and saved, then E-Signature is required. If more results are entered in subsequent sessions, then E-Signature is required at that time.

Sample Disposition - The Sample Disposition event represents the final review and approval or rejection of all of the results logged against a sample. After the sample disposition is accepted, accepted with variance, or rejected, the lot status is changed to reflect this disposition. The Certificate of Analysis report and Specification Matching feature both depend on a sample disposition being accepted. If a sample is not accepted, then these features will not recognize the sample.

Lot Status Change - The Lot Status Change event represents automatically changing a lot status based on results being in or out of specification.

Grade Change - The Grade Change event represents automatically changing a grade based on results being in or out of specification. This affects the whole warehouse under consideration.

Copyright © 2003 Oracle Corporation.
All rights reserved.