Search Results mtl_system_items_v

Overview

The APPS.INV_UI_RCV_LOVS package body provides the server-side list of values (LOV) queries used by the Oracle E-Business Suite receiving user interface. Its primary responsibility is to populate the selection lists that appear on the Receiving, Receipt, Delivery, and Inspection forms, dynamically constructing the underlying SQL based on the current operating unit, inventory organization, and mobile form context. The package is classified under the OTHER API category in ETRM and is owned by the APPS schema. It is a UI-support utility rather than a transactional API; it does not post receipts or update inventory, but instead retrieves the reference data that a user must select before a receipt transaction can be recorded.

The header comment ($Header: INVRCVLB.pls 120.31.12010000.6) confirms the package is an Oracle-shipped file delivered with the Receiving product. It exposes 33 documented procedures, each dedicated to a specific LOV.

Key Procedures and Functions

The documented procedures are grouped by the reference data they resolve:

• Purchase order and sourcing: GET_PO_LOV returns PO numbers for a given organization, honoring manual PO number type (numeric or alphanumeric) and varying its SQL for the receipt versus delivery mobile form. GET_PO_LINE_NUM_LOV, GET_PO_LINE_ITEM_NUM_LOV, and GET_PO_RELEASE_LOV resolve line numbers, item numbers, and releases against a header.
• Receipt and shipment references: GET_SHIPMENT_NUM_LOV, GET_PACK_SLIP_NUM_LOV, GET_RECEIPT_NUMBER_LOV, and GET_RECEIPT_NUMBER_INSPECT_LOV return existing receipt and packing-slip identifiers, the latter scoped for inspection activities.
• Requisitions, RMA, and jobs: GET_REQ_NUM_LOV, GET_RMA_LOV, and GET_JOB_LOV list internal requisitions, return material authorizations, and work-in-process jobs eligible for receipt.
• Locations and parties: GET_LOCATION_LOV, GET_LOCATIONCODE_LOV, and GET_DIRECTSHIP_LOCATION_LOV supply ship-to and delivery locations, including direct-ship scenarios.
• Carriers, reasons, and quality: GET_FREIGHT_CARRIER_LOV, GET_CARRIER, GET_REASON_CODES_LOV, and GET_QUALITY_CODES_LOV provide freight carriers, return/transaction reason codes, and quality inspection codes.
• Units of measure and documents: GET_UOM_LOV_EXPENSE and GET_DOC_LOV resolve expense UOMs and document references.

Tables Accessed

The LOV SQL reads from a broad set of APPS synonyms:

• Inventory masters: MTL_SYSTEM_ITEMS_KFV, MTL_PARAMETERS, MTL_INTERORG_PARAMETERS, MTL_UNITS_OF_MEASURE, MTL_CROSS_REFERENCES, and MTL_RELATED_ITEMS supply item, organization, and UOM reference data.
• Receiving and supply: MTL_SUPPLY and MTL_TXN_REQUEST_LINES provide open supply and requisition line data, while MTL_TRANSACTION_REASONS and MTL_TRANS_REASON_SECURITY back reason-code LOVs.
• Parties and locations: HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_LOCATIONS, and HR_ALL_ORGANIZATION_UNITS_TL resolve customers, sites, and organization names.
• Order and vendor context: OE_ORDER_HEADERS_ALL supports RMA and internal order searches.

Usage Notes

This package is invoked at runtime by the Receiving forms (including the mobile receipt and delivery forms, referenced by the p_mobile_form parameter) whenever a user opens an LOV field. Because it is a pure retrieval utility, it is well suited for reuse in custom Forms personalizations and OAF pages that require the same validated lists. Developers should note that the SQL reflects Multi-Org Access Control through calls such as MO_GLOBAL.get_ou_name, so results are filtered by the caller's operating unit; organization context is passed explicitly through parameters such as p_organization_id. The package is referenced by one other APPS package and should be treated as an internal Receiving component rather than a general-purpose integration API.