Search Results unit_of_measure_tl




Overview
Explore in AI Chat

Overview

CST_XLA_INV_UOM_REF_V is a lightweight reference view owned by the APPS schema in Oracle E-Business Suite. It is part of the Subledger Accounting (XLA) and Cost Management (CST) infrastructure that supports the generation of accounting entries for inventory transactions. Its purpose is to expose a minimal, denormalized projection of the units-of-measure definitions used when inventory quantities are converted and reported in the accounting engine.

The view is named with the CST_XLA prefix, indicating that it is consumed by the XLA (Subledger Accounting) engine during inventory valuation and cost processing. Rather than presenting the entire unit-of-measure configuration, it surfaces only three attributes required for accounting line construction and reporting: the unit-of-measure code, the base-unit indicator, and the descriptive unit-of-measure name. Because it is a view and not a table, it introduces no independent storage and is always consistent with the current state of its underlying source.

The view is available in both EBS 12.1.1 and 12.2.2. The metadata documented under ETRM 12.2.2 lists a single referenced base object, MTL_UNITS_OF_MEASURE, accessed through a synonym.

Underlying Base Objects

The view is defined over one base object:

  • MTL_UNITS_OF_MEASURE — the master units-of-measure definition table in the Oracle Inventory (INV) module. In the APPS schema this is referenced via a synonym.

The documented view text is a direct three-column projection from that table, with no joins, filters, or aggregations:

Because there are no join conditions, each row of the view corresponds one-to-one with a row in MTL_UNITS_OF_MEASURE. The view behaves as a simple column-restricted synonym, providing a stable, narrowly scoped interface for concurrent programs and XLA extraction logic that would otherwise query the full inventory table.

Key Columns

  • UOM_CODE — the unique alphanumeric code identifying a unit of measure (for example, Ea, KG, CTN). This is the primary key of the underlying table and the value stored on inventory and accounting transaction lines.
  • BASE_UOM_FLAG — indicates whether the unit of measure is the base unit within its class. This is relevant when the accounting engine performs conversions or distinguishes the primary unit from secondary units.
  • UNIT_OF_MEASURE_TL — the translatable description or name of the unit of measure. The "_TL" suffix denotes that the underlying table stores language-specific translations, so the returned value reflects the session language. This column is the one most commonly referenced in ad hoc searches for "unit_of_measure_tl."

Common Use Cases and Queries

Typical use cases include confirming which unit-of-measure descriptions are available to the Subledger Accounting engine, validating the base-unit flag when investigating inventory valuation discrepancies, and joining the view to XLA or inventory transaction tables to obtain readable UOM text in custom reports.

A basic retrieval of all units of measure:

  • SELECT uom_code, base_uom_flag, unit_of_measure_tl FROM apps.cst_xla_inv_uom_ref_v ORDER BY uom_code;

Filtering to the base unit of measure:

  • SELECT uom_code, unit_of_measure_tl FROM apps.cst_xla_inv_uom_ref_v WHERE base_uom_flag = 'Y';

Joining to inventory transactions to attach descriptive UOM text:

  • SELECT t.transaction_id, t.inventory_item_id, t.transaction_quantity, u.unit_of_measure_tl FROM mtl_material_transactions t, apps.cst_xla_inv_uom_ref_v u WHERE t.transaction_uom = u.uom_code;

Because the view exposes only three columns, queries should join it to the primary transaction tables rather than treating it as a general-purpose inventory source.