Search Results inc_items_freeze_required

Overview

OE_SHIPPING_WF is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports workflow-driven shipping execution within the Order Management (ONT) and Shipping Execution (WSH) modules. Its role is to determine whether order lines are eligible to proceed through the shipping workflow and to start the shipping workflow itself when conditions permit. The package acts as a bridge between the Order Management transactional data model and the Oracle Workflow engine, allowing shipping-related processing such as pick release, delivery creation, and line-level fulfilment to be orchestrated through standard workflow events rather than purely procedural logic.

The package is classified as OTHER in the ETRM documentation, indicating it is not a formally published public API. It is an internal component invoked by other EBS modules and is not intended for direct customer invocation. Its dependents, OE_DELAYED_REQUESTS_PVT and OE_SHIPPING_WF itself, confirm that it operates within the broader order and shipping processing chain, particularly where delayed or deferred requests must be evaluated before shipping activity proceeds. The package is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes two documented procedures or functions:

• INC_ITEMS_FREEZE_REQUIRED — Determines whether an increment of items in a shipping or order context requires a freeze. This logic supports the evaluation of item availability and fulfillment constraints, ensuring that workflow decisions regarding line progression account for conditions under which items should not be released or advanced.
• START_SHIPPING — Initiates shipping workflow processing. This procedure triggers the workflow actions necessary to begin shipping execution for eligible order lines, coordinating with the workflow engine and logging skip or exception conditions where applicable.

The ETRM metadata does not publish parameter lists for these units, and callers should not assume any particular signature. Custom code should never invoke these procedures directly.

Tables Accessed

Through APPS synonyms, OE_SHIPPING_WF accesses the following tables:

• OE_ORDER_LINES and OE_ORDER_LINES_ALL — The primary order line tables. The package reads line attributes to determine shipping eligibility and to evaluate whether a freeze is required before shipping proceeds.
• WSH_DELIVERY_DETAILS — Shipping execution detail records. Used to associate order lines with delivery-level shipping activity and to confirm the state of delivery detail rows.
• ONT_WF_SKIP_LOG — A workflow skip log. Records instances where workflow processing was intentionally bypassed, providing a diagnostic audit trail for shipping workflow decisions.
• FND_USER — Used to resolve user context, typically to attribute workflow actions or log entries to the responsible user.

In addition, the package depends on FND_PROFILE, indicating it reads profile option values that govern shipping workflow behaviour, and on the SYS.STANDARD package for standard PL/SQL functionality.

Usage Notes

OE_SHIPPING_WF is an internal package invoked by Oracle Order Management and Shipping Execution processing rather than by end users. It is referenced by OE_DELAYED_REQUESTS_PVT, which handles deferred order requests, and by OE_SHIPPING_WF itself, indicating recursive or self-referential workflow handling. Typical invocations occur during order line shipping progression, including deferred request processing, pick release and delivery workflows, and any process that must determine whether an item freeze should block shipping before the workflow is started. Because it is classified as OTHER and is not a documented public API, customization should be limited to understanding its behaviour for troubleshooting workflow logs, diagnosing skip log entries, or tracing why shipping did not start for a given line. Direct calls from custom code are not supported and should be avoided; instead, use supported Order Management and Shipping Execution APIs and workflow configuration.