Results for “rcv_express_sv”

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

Overview

APPS.RCV_EXPRESS_SV is a server-side PL/SQL package within the Oracle E-Business Suite Receiving module. Its name reflects its role in the "Express" receiving flow — a streamlined approach that allows high-volume receipt processing while deferring full validation to a background or on-demand step. The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking user rather than the definer, which is consistent with the Receiving schema's practice of letting calling sessions determine data access scope.

The package provides a single, focused entry point for validating a batch of express transactions that have already been staged by the receiving forms. Rather than validating each receipt interactively, the receiving process groups transactions and hands the group off for bulk validation, which improves throughput in environments where receiving clerks process many lines quickly. The package is owned by APPS and is classified under the "OTHER" API category in ETRM, indicating it is an internal support package rather than a public integration API.

Key Procedures and Functions

• val_express_transactions — The sole documented procedure. It accepts a group identifier (X_group_id) that selects the set of staged express transactions to be processed, and returns two out parameters: X_rows_succeeded and X_rows_failed, which report how many rows passed and how many failed validation respectively. The NOCOPY hint on the out parameters avoids copying large PL/SQL values, a minor but deliberate performance choice. The procedure header comment identifies "VALIDATE EXPRESS TRANSACTIONS" as its responsibility, but the underlying validation logic is not enumerated in the source excerpt. Do not assume additional procedures or overloads exist; ETRM documents exactly one procedure for this package.

Tables Accessed

Although the package exposes only one procedure, it touches a broad set of receiving, purchasing, and inventory tables via APPS synonyms during validation:

• RCV_PARAMETERS — Receiving system options that govern validation rules (e.g., over-receipt tolerance, receipt routing).
• FINANCIALS_SYSTEM_PARAMETERS and HR_ORGANIZATION_INFORMATION — Operating unit and organization context used to resolve the correct validation environment.
• PO_LINES, PO_LINE_LOCATIONS, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS, PO_REQ_DISTRIBUTIONS — Purchasing documents against which received quantities are validated.
• MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_REVISIONS, MTL_UNITS_OF_MEASURE, MTL_PARAMETERS — Item, revision, UOM, and inventory organization attributes needed to confirm the received item is valid.
• PO_INTERFACE_ERRORS and FND_NEW_MESSAGES — Error recording and user-facing message lookup when validation fails.

These references indicate the package performs end-to-end consistency checks across the purchasing-to-receiving chain before transactions are committed.

Usage Notes

RCV_EXPRESS_SV is invoked indirectly rather than as a public API. It is referenced by one other package (per ETRM metadata), and is typical of internal receiving validation plumbing called from the Receiving forms, Receiving Transaction Processor, or related concurrent programs that process staged express transactions. Custom code should not call this package directly; the supported integration surface for receiving is the RCV_* transaction APIs. Because it runs with AUTHID CURRENT_USER, database grants and MO security must be configured at the calling user's level. The header indicates the file was last updated in 2007 (RCS revision 120.0), so the package has remained stable across 12.1.1 and 12.2.2.