Search Results get_intransit_details

Overview

RCV_GET_DELIVERED_QTY is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified as a utility ("OTHER") API rather than a formal public interface. Its business function is to derive received and in-transit quantity information for a given item, vendor, and vendor site over a specified date range, so that downstream receiving, purchasing, and reconciliation logic can quantify what has been delivered versus what remains in the supply pipeline. The package isolates the quantity-aggregation logic that would otherwise be duplicated across receiving inquiry screens, supplier performance reports, and custom extensions.

Although the search term that surfaced this object was "get_intransit_details," the package is broader than that single routine. The excerpted source header (RCVDELQB.pls, version 115.6) indicates the body has been maintained since the early 11i era and carried forward into 12.1.1 and 12.2.2, with a notable correction applied under Bug# 2449044 that restructured the vendor join into an EXISTS subquery against PO_HEADERS_ALL.

Key Procedures and Functions

• GET_TRANSACTION_DETAILS — Computes delivered quantity for a specified item, vendor, vendor site, and date window. It drives a cursor over RCV_TRANSACTIONS and RCV_SHIPMENT_LINES filtered on source_document_code = 'PO' and transaction_type = 'DELIVER', with vendor attribution resolved through PO_HEADERS_ALL. It also declares a child_details_c cursor to walk RCV_TRANSACTIONS rows linked by parent_transaction_id, which supports drill-down from a delivery transaction to its dependent child transactions.
• GET_INTERNAL_DETAILS — Retrieves quantity details for internal (non-PO) receiving movements, providing the counterpart view for transfers and internal sourcing rather than supplier shipments.
• GET_INTRANSIT_DETAILS — Returns in-transit quantity details, the quantity shipped but not yet delivered, leveraging MTL_SUPPLY to determine what is still on the way. This is the routine most often referenced by custom inventory and supplier-portal reporting.

All three procedures expose output quantities to the caller rather than persisting results; none are documented as returning a value through a function signature.

Tables Accessed

• RCV_TRANSACTIONS — The core transaction ledger; supplies transaction_type, transaction_id, parent_transaction_id, primary_quantity, and transaction_date for delivered and in-transit computations.
• RCV_SHIPMENT_LINES — Links transactions to shipment lines and carries item_id and po_header_id, enabling item- and vendor-scoped filtering.
• PO_HEADERS_ALL — Resolves vendor_id and vendor_site_id for the purchase-order source, now referenced through an EXISTS subquery per Bug# 2449044.
• MTL_SUPPLY — Supplies in-transit and on-hand supply information used by GET_INTRANSIT_DETAILS.

Usage Notes

The package is typically invoked from receiving inquiry forms, supplier performance and in-transit reporting, and custom PL/SQL that needs a consolidated delivered or in-transit quantity without reimplementing the RCV query logic. One other package references it, suggesting it functions as a shared utility rather than a top-level entry point. Because the procedures are read-only and output-parameter based, they are safe to call from concurrent programs, OAF pages, and ad hoc scripts. Developers extending receiving analytics in 12.1.1 or 12.2.2 should treat the routine names as stable but validate the date-range and vendor-site semantics, since the NVL(vendor_site_id,-99) pattern means a null site argument matches headers with null site values.