Search Results rcv_correction_sv




Overview
Explore in AI Chat

Overview

APPS.RCV_CORRECTION_SV is a server-side PL/SQL package body within the Oracle E-Business Suite Receiving module. It supports the correction and querying of receiving transaction data, particularly for the Receiving Corrections and Receiving Transactions forms. The package encapsulates the business logic needed to populate and validate transaction attributes when a user queries or corrects a receipt, including resolution of unit of measure (UOM) codes, hazard classifications, UN numbers, license plate numbers, and related descriptive fields. It serves as a supporting service layer beneath the receiving forms rather than as a public API for external integration. Its classification is listed as OTHER in the ETRM metadata, indicating that it is an internal, form-driven utility package. The package body carries a header referencing RCVTXCOB.pls, confirming its association with the receiving transaction correction (RCV TX Correction) form functionality in Release 11i and carried forward into 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents two named subprograms, both of which are procedures:

  • POST_QUERY — The principal procedure in the package. It executes after a transaction has been queried in the receiving corrections interface, deriving and returning a broad set of display and validation values based on the transaction context. Inputs describe the transaction identity and source (transaction ID, receipt source code, organization, hazard class, UN number, shipment line, PO line location, RMA line, parent transaction type, source document code, destination type code, LPN identifiers, and PO type). Outputs include resolved hazard class and UN number descriptions, maximum positive, negative, tolerable, and supply quantities, packing slip information, parent transaction type and destination type display values, license plate numbers, and the ordered and secondary ordered units of measure. Two of the output parameters, x_ordered_uom and x_secondary_ordered_uom, are declared IN OUT NOCOPY, allowing the resolved UOM values to be both received and returned to the calling form.
  • NAME — Documented as a package member. In the ETRM classification it is listed among the documented procedures, though its primary role is as a standard package-level identifier entry rather than a heavyweight business routine. It does not carry the correction logic associated with POST_QUERY.

Internally, POST_QUERY relies on private cursors, including get_po_lookup_code, get_uom_class, and get_uom. The get_uom cursor — the object most closely associated with the user search term "get_uom" — selects the unit_of_measure from MTL_UNITS_OF_MEASURE based on a supplied uom_code, and is used to translate stored UOM codes into their display values for the queried transaction. A parallel cursor, get_uom_class, retrieves the UOM class for a given unit of measure. These cursors are declared privately within the package body and are not part of its public interface.

Tables Accessed

The package reads from the following tables through APPS synonyms:

  • MTL_UNITS_OF_MEASURE — Referenced by the get_uom and get_uom_class cursors to resolve UOM codes to their display names and classes.
  • PO_HAZARD_CLASSES — Used to derive hazard class descriptions for the queried transaction.
  • PO_UN_NUMBERS — Used to derive UN number descriptions.
  • RCV_SHIPMENT_LINES — Provides shipment line context for quantity and UOM resolution.
  • WMS_LICENSE_PLATE_NUMBERS — Supplies license plate (LPN) number details returned by POST_QUERY.

The package is documented as being referenced by zero other packages, confirming it is a leaf-level utility rather than a dependency of other PL/SQL units.

Usage Notes

RCV_CORRECTION_SV is typically invoked from the Oracle Receiving forms during the post-query phase of the receiving corrections and receiving transactions windows. When a user queries a receipt or correction record, the form calls POST_QUERY to populate non-database display fields, resolve UOM and hazard-related descriptions, compute allowable quantity tolerances, and populate license plate information. Because it is a form-support package, it is not intended for direct invocation by concurrent programs or external integrations. Customizations that extend the receiving corrections form should preserve the POST_QUERY contract, since changes to its output parameters affect the form's display and validation behavior. Note that in Oracle EBS 12.1.1 and 12.2.2, much of the receiving correction functionality has been supplemented by the RCV_* public APIs; however, RCV_CORRECTION_SV remains the internal service routine backing the correction form's query logic. The get_uom cursor is the specific code element that resolves a UOM code to its display unit of measure, which is why a search for "get_uom" surfaces this package.