Search Results validate_locator




Overview
Explore in AI Chat

Overview

APPS.RCV_TRANSACTIONS_INTERFACE_SV1 is a server-side validation package within the Oracle E-Business Suite Receiving module. Its core role is to validate the contents of records held in RCV_TRANSACTIONS_INTERFACE before those records are processed by the receiving transaction processor and migrated into the perpetual inventory and receiving tables. The package operates under AUTHID CURRENT_USER, meaning that it executes with the privileges of the invoking session and resolves all unqualified object references against the caller's schema. This is significant because the package references a large set of APPS synonyms, which are resolved at runtime.

The package header carries the revision marker $Header: RCVTIS2S.pls 120.1.12020000.2 2012/11/18, reflecting a maintenance lineage that includes the INVCONV (ROI convergence) changes. It declares global constants for standardized return statuses — g_ret_sts_success ('S'), g_ret_sts_error ('E'), and g_ret_sts_unexp_error ('U') — together with the exceptions g_exc_error and g_exc_unexpected_error. These conventions allow callers to interpret results uniformly across the receiving validation APIs.

Key Procedures and Functions

The ETRM metadata documents 23 procedures and functions in total. The excerpt exposes a record type and two representative procedures:

  • validate_quantity_shipped — Accepts a quantity_shipped_record_type parameter declared from rcv_shipment_line_sv. It validates the quantity shipped value on a receiving interface record, checking quantity consistency against the associated shipment line.
  • validate_secondary_parameters — Validates secondary quantity and secondary unit of measure attributes carried on the interface record, ensuring the secondary UOM code and conversion data are coherent before processing.
  • attributes_record_type — A record type aggregating inventory_item_id, transaction_quantity, transaction_unit_of_measure, secondary_quantity, secondary_unit_of_measure, secondary_uom_code, and to_organization_id, plus an error_record element drawn from RCV_SHIPMENT_OBJECT_SV.ErrorRecType. This structure bundles the key validation inputs and the resulting error payload passed between the package's validation routines.

Although the searched term validate_locator is not listed verbatim among the documented procedure names in this excerpt, locator validation is intrinsic to this package's responsibilities: locator checks draw upon MTL_SECONDARY_LOCATORS and MTL_ITEM_SUB_INVENTORIES, which appear in the referenced-table list below. In the receiving flow, locator validity is confirmed as part of the subinventory/locator attribute validation performed by the package's validation procedures before the record is accepted.

Tables Accessed

The package reads and, where appropriate, writes through APPS synonyms to the following documented tables:

Usage Notes

RCV_TRANSACTIONS_INTERFACE_SV1 is typically invoked indirectly through the Receiving Open Interface (ROI) and the Receiving Transactions Interface concurrent programs, which load and validate staged records in RCV_TRANSACTIONS_INTERFACE. It is also referenced by three other packages, indicating reuse across the receiving validation stack. Custom integrations that populate the interface table and then call the standard processor will benefit from the validation performed here — particularly around locator, subinventory, quantity, and secondary UOM attributes — before records are committed. Because the package is AUTHID CURRENT_USER, custom callers must ensure the necessary APPS synonyms and privileges are visible in their session schema.