Results for “um_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PMI_UOM_LOV_V is a database view owned by the APPS schema in Oracle E-Business Suite, classified under the Process Manufacturing Intelligence (PMI) product family. As its documented description states, it is a "Unit of Measure List Of Values View." The view exists to supply a lightweight, presentation-ready set of unit-of-measure (UOM) values that Oracle Forms, OAF pages, concurrent programs, and reporting tools can query when populating a list of values field or validating a UOM selection.

Because it projects only two columns — the UOM code and its description — the view abstracts the full structure of the underlying master table and exposes exactly the attributes needed to render an LOV. In Oracle EBS 12.1.1 and 12.2.2, the object is registered as VALID in the APPS schema, meaning the compiled definition is consistent with its dependencies and is available for normal runtime access. The view itself carries no business logic beyond projection and renaming; it is a pure read-only wrapper.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, PMI_UOM_LOV_V is defined over a single referenced base object: SY_UOMS_MST, accessed through a synonym. The documented view text is:

SELECT UM_CODE, UM_DESC FROM SY_UOMS_MST

SY_UOMS_MST is the unit-of-measure master table associated with the Process Manufacturing (OPM) schema stack. The synonym allows the APPS-owned view to resolve the table without hard-coding a schema prefix, which is consistent with EBS coding standards for cross-schema access. Because the view performs a simple projection with no joins, filters, or aggregation, it inherits the row cardinality and any enabled/disabled semantics present in the master table itself — the view does not independently filter inactive or obsolete units of measure unless the underlying table rows are removed.

Key Columns

• UM_CODE — The unit-of-measure code, the unique short identifier for a UOM (for example, the code a user types or selects in an LOV). This is the value normally stored in transactional and setup tables when a UOM is referenced. It corresponds directly to the user search term "um_code."
• UM_DESC — The descriptive name of the unit of measure, shown alongside the code in the list of values so that users can identify the correct selection without memorizing codes.

No additional columns, expressions, or aliases are documented. Any auditing, base-UOM conversion factor, or class information held in SY_UOMS_MST is intentionally excluded from this view.

Common Use Cases and Queries

Typical scenarios include populating an LOV on a custom OAF or Forms page, validating a UOM entered through an interface or conversion program, and driving the parameter list of a Process Manufacturing Intelligence report. The two-column shape makes it well suited to value-set style lookups and to lightweight reporting extracts.

• Retrieve all available UOMs: SELECT UM_CODE, UM_DESC FROM APPS.PMI_UOM_LOV_V ORDER BY UM_CODE;
• Resolve a description for a known code: SELECT UM_DESC FROM APPS.PMI_UOM_LOV_V WHERE UM_CODE = :p_um_code;
• Existence check during validation: SELECT COUNT(*) FROM APPS.PMI_UOM_LOV_V WHERE UM_CODE = :p_um_code;
• Case-insensitive LOV search: SELECT UM_CODE, UM_DESC FROM APPS.PMI_UOM_LOV_V WHERE UPPER(UM_DESC) LIKE UPPER('%'||:p_search||'%');

Because the view is a thin projection, performance is effectively that of the base table; grants on the view should follow the standard APPS synonym and responsibility-based access model. When the requirement extends to conversion factors or UOM classes, query SY_UOMS_MST directly rather than expanding this object.