Search Results rcv_transactions_sv




Overview
Explore in AI Chat

Overview

RCV_TRANSACTIONS_SV is a server-side PL/SQL package owned by the APPS schema in Oracle E-Business Suite. In the 12.1.1 and 12.2.2 releases it carries the object status VALID and is classified under the ETRM as an API of type OTHER, indicating that it is an internal application programming interface rather than a formally published open interface.

Functionally, RCV_TRANSACTIONS_SV encapsulates the validation and derivation logic applied to receiving transactions recorded in the Receiving module. A receiving transaction represents a movement or change of state for a shipment or supply — a receipt, delivery, return, correction, or adjustment. Before such a transaction is persisted by the receiving transaction processor, its attributes must be validated against purchasing, inventory, work-in-process, and order-management data. RCV_TRANSACTIONS_SV centralizes these checks and the corresponding column derivations, so that the various receiving entry points (forms, APIs, and self-service flows) apply a consistent rule set rather than replicating logic independently.

The package is heavily reused. ETRM records that it references the SYS.STANDARD package and that it is referenced by nine other APPS packages, including GML_RCV_DIR_RCPT_APIS, INV_RCV_DIR_RCPT_APIS, INV_RCV_STD_DELIVER_APIS, PO_ITEMS_SV2, RCV_DISTRIBUTIONS_S, RCV_EXPRESS_SV, RCV_RECEIPTS_QUERY_SV, and recursively by RCV_TRANSACTIONS_SV itself. This dependency footprint confirms its role as a shared validation layer beneath the direct receipt and delivery APIs.

Key Procedures and Functions

ETRM documents eight procedures and functions within RCV_TRANSACTIONS_SV, though the metadata excerpt does not enumerate individual routine names or parameter lists. Based on the package's documented classification and dependency profile, its members correspond to the validation and defaulting operations required by the receiving transaction lifecycle: validating transaction type and action combinations against PO_LINE_TYPES; validating source document references such as purchase orders, releases, and internal requisitions; resolving the owning organization, department, and location for the transaction; deriving supply and shipment-line attributes from RCV_SHIPMENT_LINES and RCV_SUPPLY; validating destination and deliver-to information; and applying work-in-process context when a transaction is associated with a discrete job or WIP entity. Parameter lists are not reproduced here because the ETRM metadata does not expose them, and they should be confirmed against the live package specification in the target environment.

Tables Accessed

The documented table references, resolved through APPS synonyms, reflect the breadth of the validation performed:

Usage Notes

RCV_TRANSACTIONS_SV is not intended for direct invocation by end users or external integrations. It is invoked indirectly by Receiving forms and by the higher-level receiving APIs — notably the direct receipt and standard delivery APIs listed in its dependency metadata — and by concurrent programs that process receiving transactions. Because the package is referenced by other server-side packages, customers extending receiving functionality should call the published Receiving APIs rather than this internal validation package. Any direct reference in custom code creates a dependency on Oracle's internal implementation, which may change between 12.1.1 and 12.2.2 or in subsequent patches. Developers diagnosing validation failures during receipt processing should treat RCV_TRANSACTIONS_SV as the likely origin of the error and trace backward from the calling API or form.