Results for “uom_code”

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

Overview

CST_XLA_INV_UOM_REF_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified under the BOM (Bills of Material) product family and is registered as a valid, deployed object within the ETRM metadata repository. Functionally, the view presents a simplified, denormalized projection of the units-of-measure reference data used by Cost Management and Subledger Accounting (XLA) inventory valuation logic. Its most probable purpose is to supply inbound or query-only UOM reference values to XLA distribution and accounting generation processes, which require a stable, low-column surrogate for the full Units of Measure definition.

The view carries the CST_ prefix associated with Cost Management and the XLA_ token associated with Subledger Accounting, indicating that it exists to bridge inventory UOM data into XLA data extraction rather than to serve as an end-user inquiry screen. Because it is defined over the core UOM table, it exposes only the three attributes required for UOM lookup and reference verification (code, base flag, and translated descriptive name), avoiding the wider set of translation and control attributes present on the base table.

Underlying Base Objects

Per the documented view metadata, CST_XLA_INV_UOM_REF_V is defined over a single referenced base object: MTL_UNITS_OF_MEASURE, accessed through a synonym. The view text is:

• SELECT UOM_CODE, BASE_UOM_FLAG, UNIT_OF_MEASURE_TL FROM MTL_UNITS_OF_MEASURE

This relationship is a straight projection: no joins, unions, or aggregations are present. The view therefore inherits its performance, indexing, and security characteristics directly from MTL_UNITS_OF_MEASURE. Note the third column name, UNIT_OF_MEASURE_TL, which follows Oracle's _TL translated-column convention; the underlying source column may be exposed under a translated naming convention even though all three projected fields originate from the single base table. Because only one base object is referenced, the view is inexpensive to maintain and carries no join cardinality risk.

Key Columns

• UOM_CODE — The unique alphanumeric unit-of-measure code (for example, EA, DOZ, CS) that identifies the unit being referenced. This is the primary lookup key consumed by inventory, costing, and XLA routines.
• BASE_UOM_FLAG — A flag indicating whether the referenced UOM is the base unit of measure for the applicable context. It supports determination of base-versus-transaction UOM relationships required for conversion during valuation.
• UNIT_OF_MEASURE_TL — The translated descriptive name supplied for the unit of measure, presented under the _TL naming convention. It distinguishes the human-readable UOM description from the machine-readable code.

Common Use Cases and Queries

The view is typically used by XLA inventory accounting extraction queries, UOM reference validation routines, and reconciliation reports that need a compact UOM lookup. A representative listing query is:

• SELECT UOM_CODE, BASE_UOM_FLAG, UNIT_OF_MEASURE_TL FROM APPS.CST_XLA_INV_UOM_REF_V ORDER BY UOM_CODE;
• SELECT UOM_CODE, UNIT_OF_MEASURE_TL FROM APPS.CST_XLA_INV_UOM_REF_V WHERE BASE_UOM_FLAG = 'Y';
• SELECT UOM_CODE FROM APPS.CST_XLA_INV_UOM_REF_V WHERE UOM_CODE = 'EA';

Practitioners should treat the view as a convenience reference over MTL_UNITS_OF_MEASURE and should not expect filtering or security predicates beyond those on the base table. Because it is delivered by Oracle and marked valid, it is safe to reference in custom reports, but direct dependency on the underlying table remains an option where additional UOM attributes are required.