Results for “inv_mo_backorder_pvt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

INV_MO_BACKORDER_PVT is a private PL/SQL package in the Oracle E-Business Suite Inventory module (APPS schema) that manages the backorder processing logic for move orders. In Oracle EBS 12.1.1 and 12.2.2, move orders represent internal inventory replenishment, transfer, and subinventory replenishment requests. When a move order line cannot be fully satisfied — for example, when the requested quantity exceeds availability at the source, or when picking generates a shortfall — the remainder must either be backordered (retained for later fulfillment) or cancelled. This package encapsulates the server-side rules that determine quantities eligible for backorder, evaluate source and delivery detail relationships, and perform the resulting cleanup of transactional detail rows.

The package is classified as PVT, meaning it is an internal implementation package rather than a public API. It is referenced by five other packages, indicating it acts as a shared utility layer consumed by move order processing flows rather than being called directly by external integrators.

Key Procedures and Functions

• BACKORDER — Evaluates a move order line and determines the residual quantity that should be carried forward as a backorder. The logic accounts for already-delivered quantities, ignores overpicking scenarios by clamping negative residuals to zero, and inspects shipping-related attributes (released status, delivery detail identifiers, and associated order header/line identifiers from the WSH delivery views) to decide whether a backorder is valid for the given move order type. It returns standard API status, message count, and message data outputs.
• DELETE_DETAILS — Removes the detail records associated with a move order line whose quantity has been fully satisfied through delivery or whose remainder has been resolved. This procedure supports the cleanup phase so that stale delivery and transaction details do not persist after backorder or cancellation decisions are applied.

The package also exposes a private DEBUG helper that writes trace messages through INV_LOG_UTIL and prints the package header version once per session, which is useful for diagnosing backorder behavior during support investigations.

Tables Accessed

• MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES — the core move order header and line tables that define the request being processed.
• MTL_MATERIAL_TRANSACTIONS_TEMP — staging of pending inventory transactions generated or evaluated during backorder processing.
• MTL_SYSTEM_ITEMS — item attribute validation, including ATO and reservation-related behavior governed by the WSH_RETAIN_ATO_RESERVATIONS profile.
• WMS_DISPATCHED_TASKS — warehouse execution task information used to determine whether work has already been dispatched against the line.
• DUAL — used for scalar evaluations and profile lookups.

Usage Notes

Because INV_MO_BACKORDER_PVT is a PVT package, it is not intended for direct invocation by customer extensions. It is invoked indirectly through move order processing — typically from the Inventory Move Orders form or the move order concurrent/manager processes that orchestrate pick, ship, and delivery-confirm flows. Custom code that needs to backorder or delete move order details should call the supported public APIs (such as INV_MOVE_ORDER_PUB) and allow this package to execute as part of the standard processing chain. The presence of the WSH_RETAIN_ATO_RESERVATIONS profile check indicates that behavior differs for ATO (assemble-to-order) configurations, and customers using ATO models should validate profile settings before expecting reservations to be retained across backorders.