Search Results get_quality_codes_lov

Overview

INV_UI_RCV_LOVS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supplies the SQL behind list-of-values (LOV) windows used throughout the Receiving and receiving-adjacent user interfaces. The package name follows the EBS convention for "UI receiving LOVs," indicating that its purpose is to encapsulate the reference cursor queries that populate LOV selections rather than to execute transactional receiving logic. Each procedure returns a weakly typed REF CURSOR (t_genref), allowing the calling form or page to fetch and display candidate rows dynamically.

The package is declared AUTHID CURRENT_USER, so its statements execute under the privileges of the invoking session rather than the definer. Under Release 12 multi-org access control (MOAC), the "$Header" and inline comments confirm that the earlier parameter p_manual_po_num_type was removed from several procedures (GET_PO_LOV, GET_RECEIPT_NUMBER_LOV, GET_RECEIPT_NUMBER_INSPECT_LOV, GET_DOC_LOV), and organization restriction is now driven by p_organization_id, reflecting the shift to operating-unit and inventory-organization context in 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes 33 documented procedures and functions. The prominent members include:

• GET_PO_LOV — returns purchase order numbers restricted to the current inventory organization and, optionally, by a partial user-entered PO number and shipment header.
• GET_PO_LINE_NUM_LOV — returns PO line numbers scoped to a specific PO header.
• GET_PO_RELEASE_LOV — returns release numbers associated with a given PO.
• GET_PO_LINE_ITEM_NUM_LOV — returns item numbers tied to PO lines.
• GET_LOCATION_LOV, GET_LOCATIONCODE_LOV, GET_DIRECTSHIP_LOCATION_LOV — supply location and location-code selections, including the direct-shipment variant used when goods ship straight from supplier to customer.
• GET_FREIGHT_CARRIER_LOV, GET_CARRIER — return freight carrier selections for receipt and shipment entry.
• GET_SHIPMENT_NUM_LOV, GET_PACK_SLIP_NUM_LOV, GET_RECEIPT_NUMBER_LOV, GET_RECEIPT_NUMBER_INSPECT_LOV — return receipt, packing slip, and inspection receipt identifiers.
• GET_REQ_NUM_LOV, GET_JOB_LOV, GET_RMA_LOV, GET_DOC_LOV — return requisition numbers, job references, RMA numbers, and document selections.
• GET_QUALITY_CODES_LOV, GET_REASON_CODES_LOV — return quality and transaction reason codes, honoring reason security.
• GET_UOM_LOV_EXPENSE — returns units of measure applicable to expense destinations.

The search term GET_LOCATIONCODE_LOV resolves to one of these location-oriented procedures, returning location code values for the receiving UI rather than full address detail.

Tables Accessed

The package reads (and in limited cases writes) through APPS synonyms covering master and reference data:

• MTL_PARAMETERS and MTL_INTERORG_PARAMETERS — provide organization and inter-org context for MOAC filtering.
• MTL_SYSTEM_ITEMS_KFV, MTL_CROSS_REFERENCES, MTL_RELATED_ITEMS, MTL_SUPPLY — supply item key-flex and cross-reference lookups and supply information.
• MTL_UNITS_OF_MEASURE — backs GET_UOM_LOV_EXPENSE.
• MTL_TRANSACTION_REASONS and MTL_TRANS_REASON_SECURITY — back the reason and quality code LOVs and enforce reason security.
• MTL_TXN_REQUEST_LINES — supports move-order and requisition-related LOVs.
• HR_ALL_ORGANIZATION_UNITS_TL — supplies organization names.
• HZ_CUST_ACCOUNTS, HZ_LOCATIONS, HZ_PARTIES — provide trading partner, customer, and location/address data for location and RMA LOVs.
• OE_ORDER_HEADERS_ALL — supports order-related lookups such as RMA and direct-ship references.

Usage Notes

INV_UI_RCV_LOVS is invoked exclusively by the Receiving user interface — the core Receiving form, mobile receiving pages (the p_mobile_form parameter distinguishes RECEIPT from DELIVER), and inspection surfaces. It is referenced by one other documented package, indicating layered reuse rather than direct end-user invocation. Customizations normally call these procedures to populate their own LOV records when building extensions that require PO, location, carrier, receipt, or reason-code selection consistent with standard receiving behavior. Because procedures return REF CURSORs, callers must declare a cursor variable of t_genref and fetch rows themselves. All organization-sensitive queries require the caller to pass the correct organization context so that MOAC and org-level security remain intact.