Search Results book_order

Overview

APPS.OE_BOOK_WF is a workflow-enabled PL/SQL package body in Oracle Order Management (OE) that implements the booking activity within the Order Management order flow. Booking is the business event that validates an order, applies booking holds and business logic, and transitions the order from entered status to booked status so that it can proceed to fulfillment and shipping. The package exposes a single workflow-callable entry point, BOOK_ORDER, which is designed to be invoked as a function activity by the Oracle Workflow engine. Its header revision (OEXWBOKB.pls 120.0, dated 2005/06/01) reflects a long-stable interface carried forward through EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

• BOOK_ORDER — The package's sole documented procedure. It follows the Oracle Workflow standard activity signature, accepting an item type, item key, activity identifier, function mode, and an IN OUT result string. In RUN mode, the item key is interpreted as the order header identifier. Two principal operations are performed: a booking-hold validation via OE_ORDER_BOOK_UTIL.Check_Booking_Holds, and the return of a workflow result that drives the subsequent branch of the order flow. Where holds are detected, the procedure returns a COMPLETE:ON_HOLD result so that Workflow routes the order to a hold/completion path. An unexpected API error raises an application exception, which causes Workflow to place the activity in error status for administrative review. Debug messages are emitted through OE_DEBUG_PUB and message context is managed through OE_STANDARD_WF to preserve user-facing messages on the workflow item.

The procedure contains a dedicated short-circuit for bulk order import: when the global header index in OE_BULK_WF_UTIL is populated, it reads the BOOKED_FLAG from the bulk order PVT record and returns COMPLETE:COMPLETE immediately if the order is already booked. This is necessary because bulk import performs booking validations and business logic during import itself, which may occur before the Workflow booking activity would otherwise execute.

Tables Accessed

ETRM metadata lists no directly referenced tables via APPS synonyms for this package. This is consistent with its design: OE_BOOK_WF is an orchestration layer that delegates all data access to the Order Management public APIs and utilities it calls. Booking hold evaluation and order state transitions are performed inside OE_ORDER_BOOK_UTIL and the bulk order PVT layer, which in turn operate against the OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL base tables and their associated holds and workflow-status columns. The package therefore reads order booking state indirectly through OE_BULK_ORDER_PVT.G_HEADER_REC.BOOKED_FLAG during bulk import, and otherwise relies on the invoked APIs to read and update order data.

Usage Notes

OE_BOOK_WF is not intended for direct invocation from forms or concurrent programs. It is registered as a function activity in the Order Management workflow definition (order header item type) and is executed by the Workflow background engine as the order flow progresses to the booking node. Custom workflows that extend or copy the standard order flow may reference the activity, but developers should not call BOOK_ORDER directly; order booking should be initiated through the Order Management booking APIs or the Booking concurrent program, which in turn drive the standard workflow. The package is documented as referenced by zero other packages and references no tables directly, confirming its role as a thin workflow adapter. Customizations should avoid modifying this package, since changes to the seeded workflow activity signature or result codes would break the standard order flow and could compromise upgrade safety between 12.1.1 and 12.2.2.