Search Results get_uom2_code

Overview

INV_LABEL_PVT1 is a private PL/SQL package in the APPS schema that supports Oracle E-Business Suite's inventory labeling infrastructure. It operates as a helper package beneath the public INV_LABEL package, which is responsible for rendering and printing barcode and material labels used throughout warehouse and receiving operations. Rather than exposing a user-facing API, INV_LABEL_PVT1 supplies the lower-level logic that assembles label content by resolving item identifiers, units of measure, and transactional context into the data elements printed on physical labels. It also serves receiving flows, as evidenced by its use by INV_RCV_COMMON_APIS. The package is classified as VALID and is documented as an OTHER-type API, meaning it is not part of a formally published interface but is invoked internally by other inventory components.

Key Procedures and Functions

The ETRM metadata documents six procedures and functions within this package. Their names indicate the following purposes:

• CHECK_RTI_ID — Validates an RTI (receiving transaction interface or related label identifier) value, ensuring a requested identifier corresponds to a legitimate record before label data is assembled.
• GET_VARIABLE_DATA — Retrieves variable label data, likely resolving runtime label fields whose values differ per transaction or item.
• GET_UOM_CODE — Returns the primary unit of measure code associated with an item, used to display the correct stocking UOM on the label.
• GET_UOM2_CODE — Returns the secondary unit of measure code, supporting dual-UOM items where a second UOM must appear on the label.
• GET_ORIGINATION_TYPE — Determines the origination type of a transaction or label, identifying the source context (for example, receipt, move order, or cycle count) so the correct label format is applied.

These routines function as accessors and validators that feed label generation rather than performing business commits themselves.

Tables Accessed

INV_LABEL_PVT1 references a broad set of inventory and source tables through APPS synonyms. Items and their attributes are resolved from MTL_SYSTEM_ITEMS, MTL_PARAMETERS, and MTL_LOT_NUMBERS. Transactional context comes from MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_ONHAND_QUANTITIES_DETAIL, and MTL_RESERVATIONS. Cycle counting data is drawn from MTL_CYCLE_COUNT_HEADERS and MTL_CYCLE_COUNT_ENTRIES. Resource and routing information is sourced from BOM_DEPARTMENTS, BOM_DEPARTMENT_RESOURCES, and BOM_RESOURCES, while CST_COST_GROUPS supplies cost group classifications. User and location details are obtained from FND_USER and HR_LOCATIONS_ALL. The package thus reads across inventory, bills of material, costing, and human resources data to build a complete label record.

Usage Notes

INV_LABEL_PVT1 is not typically called directly by end users or custom code. It is invoked by the INV_LABEL package during label printing, and by INV_RCV_COMMON_APIS during receiving label generation. In Oracle EBS 12.1.1 and 12.2.2 the naming convention _PVT1 designates a private package body reserved for internal use, so the supported entry point for extensions remains the parent INV_LABEL public API. Developers troubleshooting label formatting, missing UOM values, or incorrect origination types should inspect this package's logic, but customizations should avoid direct dependency on it to prevent breakage during patching or upgrades. Two other packages reference it, confirming its role as a shared internal utility. Because the metadata provides only subobject names and dependency lists, exact parameter signatures are not documented here and should be confirmed against the deployed package specification in the target environment.