Search Results inv_mo_backorder_pvt




Overview
Explore in AI Chat

Overview

INV_MO_BACKORDER_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It belongs to the Inventory (INV) module and supports the material movement and transaction processing infrastructure, specifically the handling of backordered move order lines. The package operates within the ETRM classification "PVT," designating it as a private implementation package rather than a public API. As such, it is not intended for direct invocation by external custom code, though it underpins several warehouse management and inventory processes.

The core business purpose of this package is to manage the backorder condition that arises when a move order or warehouse task cannot be fulfilled due to insufficient on-hand quantity, a discrepancy in the requested item, or a change in demand. The package provides the internal logic required to either place demand lines on backorder status or to purge the associated detail records. Its presence in the dependency chain of the Oracle Warehouse Management (WMS) public and private packages indicates a tightly integrated role in task dispatch, wave planning, device confirmation, and transaction reasoning.

Key Procedures and Functions

The ETRM metadata documents exactly two program units within this package:

  • BACKORDER — This procedure implements the primary business logic for placing a material movement or move order line into a backordered state. It is invoked when a requested transaction cannot be satisfied, adjusting the status of the affected transaction and supporting the rescheduling or reallocation of demand. It forms the functional entry point for the package's namesake operation.
  • DELETE_DETAILS — This procedure removes the detail records associated with a backordered transaction. It performs the cleanup of temporary or staging rows that are no longer required once the backorder decision has been finalized, ensuring that residual data does not interfere with subsequent moves or warehouse task execution.

These units are exposed only within the package scope and are consumed by the dependent WMS and INV routines listed in the metadata. No parameter lists are documented in the source metadata, and none should be assumed.

Tables Accessed

The package interacts with the following tables through APPS synonyms:

  • MTL_MATERIAL_TRANSACTIONS_TEMP — The staging table for pending material transactions. The package updates or removes rows here to reflect the backorder outcome and the deletion of detail records.
  • MTL_SYSTEM_ITEMS — The item master, consulted to verify item attributes and validate the item involved in the transaction.
  • MTL_TXN_REQUEST_HEADERS — Stores move order header information, used to locate and update the parent move order when its lines are backordered.
  • MTL_TXN_REQUEST_LINES — Stores moving order line detail, the primary target for backorder status changes and line-level adjustments.
  • WMS_DISPATCHED_TASKS — Warehouse management tasks that have been dispatched; these are examined and potentially modified when a task cannot be completed and must be backordered.
  • DUAL — The standard Oracle dummy table, used for simple value selection and procedural control.

Usage Notes

INV_MO_BACKORDER_PVT is an internal, private package and is not documented as a public API. It is referenced by five other packages: WMS_DEVICE_CONFIRMATION_PUB, WMS_TASK_DISPATCH_GEN, WMS_TXNRSN_ACTIONS_PUB, WMS_UT_PKG, and WMS_WAVE_PLANNING_PVT. This dependency pattern demonstrates its invocation through warehouse task dispatch, transaction reasoning, wave planning, and device confirmation flows. The BACKORDER procedure is typically reached when a warehouse operator confirms a task or when the system evaluates a move order that cannot be satisfied; DELETE_DETAILS is subsequently called to clear the associated staging rows. Because the package is private, custom development should not call it directly; instead, developers should invoke the documented public WMS or INV APIs that internally drive this package. It also depends on the SYS.STANDARD package for basic PL/SQL functionality.