Results for “um_code”

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

Overview

PMI_UOM_V is a database view owned by the APPS schema in Oracle E-Business Suite. It is documented under the PMI – Process Manufacturing Intelligence product, which is flagged as obsolete in the ETRM metadata for both 12.1.1 and 12.2.2. The view carries a VALID status and serves as a Unit of Measure List of Values (LOV) view, providing a simplified, read-only projection of the unit of measure master data used across Process Manufacturing components. Rather than exposing the full column set of the underlying master table, PMI_UOM_V presents only the two attributes required by LOV-driven user interfaces and lookup queries: the unit of measure code and its descriptive text.

Because it is a view and not a table, PMI_UOM_V stores no data of its own. It is resolved at runtime against its base object, returning a filtered, presentation-oriented result set appropriate for value list population, reporting joins, and lightweight integrations. Its role in Oracle EBS reporting and integration is that of a convenience access point: developers and report authors can query a single, stable object to retrieve unit of measure codes and descriptions without navigating the broader structure of the underlying master table.

Underlying Base Objects

The documented view text is a direct two-column projection over a single base object:

• SY_UOMS_MST — the unit of measure master table, referenced in ETRM as a SYNONYM within the APPS schema.

The view definition is expressed as SELECT UM_CODE, UM_DESC FROM SY_UOMS_MST. There are no joins, filters, or aggregation in the documented definition, meaning the view is a straightforward column-subset projection. All rows present in the base master object are exposed through the view, subject only to whatever row-level security or synonym-level configuration applies at the database layer. Because the base object is referenced as a synonym, the view depends on that synonym remaining valid and on the underlying physical table being accessible in the APPS execution context.

Key Columns

The view exposes exactly two columns, as documented:

• UM_CODE — the unit of measure code. This is the unique identifier for a unit of measure (for example, a code representing each, kilogram, or liter) and is the value typically stored in transactional and setup tables that reference a unit of measure. It is the column most commonly used in joins and lookup conditions.
• UM_DESC — the unit of measure description. This is the human-readable text associated with the code, used for display in list of values windows, reports, and user-facing output.

The user search term "um_code" maps directly to the UM_CODE column, confirming that the primary retrieval pattern for this view is keyed on the unit of measure code.

Common Use Cases and Queries

Typical scenarios include populating LOV fields on concurrent program parameters, enriching transactional extracts with readable unit of measure text, and validating unit of measure codes during data conversion or interface loads. A basic retrieval of all units of measure is:

• SELECT UM_CODE, UM_DESC FROM APPS.PMI_UOM_V ORDER BY UM_CODE;
• SELECT UM_CODE, UM_DESC FROM APPS.PMI_UOM_V WHERE UM_CODE = :um_code; — used to resolve the description for a specific code.
• SELECT t.transaction_id, t.um_code, v.um_desc FROM some_transaction_table t, APPS.PMI_UOM_V v WHERE t.um_code = v.um_code; — a join pattern enriching transaction data with the description.

Because the PMI product is documented as obsolete, implementations should treat this view as legacy. Where a replacement object exists in the current Process Manufacturing schema, new development should prefer it; existing queries against PMI_UOM_V should be reviewed before upgrades, since obsolete objects may be desupported in later releases.