Results for “base_uom_flag”

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

Overview

PO_UNITS_OF_MEASURE_VAL_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. It is delivered as a validation view, exposing a restricted set of columns from the master unit of measure definition so that purchasing forms, lookups, and validation logic can resolve only those units of measure that are currently active. The view carries a status of VALID and is documented as "Retrofitted," indicating that it was reimplemented or re-registered during an upgrade cycle (notably the transition to Release 12) while preserving its original interface contract for dependent objects.

Its principal functional role is temporal filtering. Rather than presenting every row in the units of measure table, the view excludes records whose DISABLE_DATE has already passed, returning only units of measure that are effective as of the current system date. This makes it suitable for validation against a list of acceptable values, for LOV (list of values) definitions, and for integration or reporting queries that must not offer retired units of measure to end users or downstream processes.

Underlying Base Objects

The view is defined over a single referenced base object: MTL_UNITS_OF_MEASURE, accessed through its public synonym. MTL_UNITS_OF_MEASURE is the inventory-owned master table that stores all unit of measure definitions across the enterprise, including their class assignments, base-unit designation, descriptive text, and enable/disable dates.

Because PO_UNITS_OF_MEASURE_VAL_V is a simple, non-joined projection over that table, it introduces no aggregation, no outer joins, and no additional business logic beyond the date predicate. Consequently, it inherits the security, performance, and data characteristics of the underlying table, and any row inserted into, updated in, or deleted from MTL_UNITS_OF_MEASURE is immediately reflected in the view.

Key Columns

• UNIT_OF_MEASURE — The descriptive name or label of the unit of measure (for example, Each, Dozen, Kilogram). This is the value typically presented to users in a list of values.
• UOM_CODE — The short, unique code that identifies the unit of measure internally. It is the primary key of the underlying table and the value most commonly stored on transactional records.
• UOM_CLASS — The class to which the unit of measure belongs (such as Quantity, Weight, Volume, or Time). The class governs conversion rules, since conversions are only valid within the same class.
• BASE_UOM_FLAG — A flag indicating whether the unit of measure is the base unit for its class. The base unit serves as the anchor against which all other units in the same class are converted. This column is frequently the target of user searches, since the base unit determines the conversion denominator for the entire class.
• DESCRIPTION — Free-form descriptive text associated with the unit of measure, used for clarification and reporting.

Common Use Cases and Queries

Typical uses include populating validation lists in purchasing setup, filtering units of measure in reports, and identifying the base unit for each class.

• Retrieving active units of measure by class:

SELECT uom_code, unit_of_measure, description FROM apps.po_units_of_measure_val_v WHERE uom_class = 'QUANTITY' ORDER BY unit_of_measure;

• Identifying base units of measure across all classes:

SELECT uom_code, unit_of_measure, uom_class FROM apps.po_units_of_measure_val_v WHERE base_uom_flag = 'Y';

• Locating a specific unit of measure by code for validation:

SELECT unit_of_measure, uom_class, base_uom_flag FROM apps.po_units_of_measure_val_v WHERE uom_code = :uom_code;

Because the view already restricts output to currently enabled units of measure, queries against it should not apply additional disable-date logic. Reports requiring historical units of measure must instead query MTL_UNITS_OF_MEASURE directly, as the view deliberately omits disabled records.