Search Results oe_ship_confirmation_pub




Overview
Explore in AI Chat

Overview

OE_SHIP_CONFIRMATION_PUB is a public PL/SQL API in the APPS schema that supports the shipping confirmation flow within Oracle Order Management. Shipping confirmation is the point in the order-to-cash lifecycle at which warehouse personnel confirm that goods have physically left the shipping dock. This confirmation triggers downstream activities including inventory relief, order line status advancement, delivery detail updates, and notification of interested parties through the Oracle Workflow notification framework.

The package is classified as a PUB (public) API, indicating that it is intended for external invocation by other Oracle EBS modules and customer extensions rather than restricted to internal use. It depends on FND_API for the standard API return-status conventions, on OE_ORDER_PUB for order-level processing, and on OE_WSH_BULK_GRP for bulk shipping group operations. A range of Oracle Shipping Execution components, including OE_DS_PVT, WSH_DCP_PVT, WSH_FC_INTERFACE_PKG, and WSH_SHIP_CONFIRM_ACTIONS, reference this package, confirming its role as a supporting service in the shipping confirmation integration path.

Key Procedures and Functions

The documented package exposes four entry points:

  • SHIP_CONFIRM — The primary shipping confirmation routine. It executes the core confirmation logic for a given shipment or delivery, driving order line status changes and related inventory and delivery updates.
  • SHIP_CONFIRM_NEW — A variation of the confirmation routine, presumably providing an extended or alternative signature used for newer confirmation scenarios or revised processing paths.
  • CALL_NOTIFICATION_FRAMEWORK — Invokes the Oracle Workflow notification framework, raising events or notifications tied to shipping confirmation activity so that configured subscribers and business events can respond.
  • SHIP_ZERO — Handles the zero-quantity or zero-shipment confirmation case, ensuring the confirmation transaction completes cleanly when no physical quantity is being shipped.

Specific parameter lists are not documented in the available metadata and are therefore not reproduced here.

Tables Accessed

Through APPS synonyms the package reads and writes a defined set of base tables:

  • OE_ORDER_LINES and OE_ORDER_LINES_ALL — The order line interface and base tables, updated to reflect shipped quantities and line status progression.
  • OE_PRICE_ADJUSTMENTS and OE_PRICE_ADJUSTMENTS_S — Price adjustment records, consulted or updated when shipping confirmation affects priced adjustments.
  • OE_SETS — The order set control table, used for set processing context.
  • WSH_DELIVERY_DETAILS — The Shipping Execution delivery detail table, where confirmed shipment quantities and statuses are recorded.
  • WF_ITEM_ACTIVITY_STATUSES and WF_PROCESS_ACTIVITIES — Workflow runtime tables supporting notification and process activity state.
  • DUAL, PLITBLM, and V$TIMER — Utility objects used for single-row queries, PL/SQL table handling, and timing or event scheduling logic.

Usage Notes

OE_SHIP_CONFIRMATION_PUB is normally invoked indirectly. Oracle Shipping Execution calls it during delivery confirmation processing through packages such as WSH_DCP_PVT and WSH_SHIP_CONFIRM_ACTIONS, and the Order Management direct-ship path reaches it through OE_DS_PVT. The WSH_FC_INTERFACE_PKG also references it as part of forecast or interface processing.

Because the package is a PUB API, custom code should call it rather than writing directly to OE_ORDER_LINES or WSH_DELIVERY_DETAILS, ensuring that the standard validation, workflow notification, and status-derivation logic executes. Extensions should respect the FND_API return-status convention and check the returned status before assuming success. Direct invocation requires a fully resolved shipping context, including the delivery or order line identifiers expected by the selected procedure.