Search Results get_transaction_details

Overview

RCV_GET_DELIVERED_QTY is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite Receiving. Its purpose is to calculate and return delivered, received, and in-transit quantities for a given item across a defined organization, supplier, or date range. The package is defined with AUTHID CURRENT_USER and, per the ETRM 12.2.2 metadata, is classified as OTHER rather than as a formal public API. It exists to centralize the aggregation logic that Oracle Receiving forms and dependent programs require when reporting on receipt and delivery activity without duplicating that logic across multiple callers. The header revision visible in the source listing (115.3) indicates the package has been stable since at least 2002, a reflection of its narrow and well-defined scope.

Key Procedures and Functions

• GET_TRANSACTION_DETAILS — Calculates delivered quantity for an item sourced from a specific vendor and vendor site, bounded by a start and end date. It returns the accumulated quantity through an OUT NOCOPY parameter. This is the procedure most commonly associated with the search term "get_transaction_details," since it is the package's primary supplier-facing aggregation entry point.
• GET_INTERNAL_DETAILS — Calculates delivered quantity for an item transferred between two inventory organizations (a from-org and a to-org), again constrained by a start and end date, and returns the result through an OUT NOCOPY parameter. It supports internal requisition and internal shipment reporting.
• GET_INTRANSIT_DETAILS — Returns the quantity that has been received but not yet delivered for a movement between two organizations. Unlike the other two procedures, it is not date-bounded, reflecting that in-transit balances are current-state measurements.

All three procedures use OUT NOCOPY parameters, which reduces copying overhead for numeric return values in PL/SQL.

Tables Accessed

• RCV_SHIPMENT_LINES — The core receiving table holding shipment and delivery line quantities used to derive delivered amounts.
• RCV_TRANSACTIONS — Receiving transaction history, used to identify what has actually been transacted within the requested date window.
• PO_HEADERS_ALL — Supplier-side context, used to correlate receipts with the correct purchasing document for the GET_TRANSACTION_DETAILS path.
• MTL_SUPPLY — Supply and demand records, consulted primarily to determine in-transit quantities for inter-org movements.

The package reads from these tables through APPS synonyms and does not maintain its own persistent state.

Usage Notes

RCV_GET_DELIVERED_QTY is invoked from Oracle Receiving forms and from other PL/SQL packages; the ETRM metadata records exactly one package reference. Because it is not a registered public API with a formal interface contract, custom code should call it defensively and validate that the caller's organization, item, and date parameters align with the seeded semantics of each procedure. The package must be called within an APPS initialization context (FND_GLOBAL.APPS_INITIALIZE) so that AUTHID CURRENT_USER resolves synonyms and organization security correctly. Typical use cases include supplier performance reporting, internal transfer reconciliation, in-transit quantity displays on receiving forms, and custom concurrent programs that summarize delivery activity for a period. Developers should treat the OUT NOCOPY parameter as the sole return channel and should not assume the procedures raise defined exceptions for invalid input.