Results for “uom_class_name”

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

Overview

INVFV_UOM_CLASSES is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined over the base table MTL_UOM_CLASSES. It resides in the INV (Inventory) product module and is classified as a retrofitted object, meaning its definition was adapted during an upgrade or migration to preserve interface compatibility while the underlying data model evolved. The view presents unit-of-measure (UOM) class definitions used throughout Inventory and related modules such as Order Management, Purchasing, and Manufacturing.

In the Oracle EBS 12.1.1 and 12.2.2 architecture, UOM classes provide the grouping construct for units of measure — for example, temporal, length, weight, or volume classes — that subsequently determine which UOMs may be assigned to a given item or transaction. The view's reporting role is to expose the class name, description, and effective/disabling dates in a stable, name-mapped form, allowing reports and integrations to query UOM class metadata without depending directly on the base table's column names. This insulation is significant when custom extensions or third-party systems reference INVFV_UOM_CLASSES rather than MTL_UOM_CLASSES.

Underlying Base Objects

The view is defined with the READ ONLY clause over MTL_UOM_CLASSES, accessed through a synonym in the APPS schema. The view text selects from MTL_UOM_CLASSES using the alias UO, mapping the base columns UOM_CLASS, DISABLE_DATE, DESCRIPTION, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY. A literal value — '_DF:INV:MTL_UOM_CLASSES:UO' — is injected as an additional projected column. This "described-by" (DF) literal embeds descriptive-flexfield context, pointing to the INV:MTL_UOM_CLASSES:UO descriptive flexfield. Because the view is read only, no DML can be performed against it; all maintenance of UOM class records occurs directly on MTL_UOM_CLASSES through the standard Inventory setup forms.

The single-source definition means the view carries no join overhead. It does not aggregate or filter rows, so its cardinality matches MTL_UOM_CLASSES exactly, including any records that have been disabled by way of DISABLE_DATE.

Key Columns

• UOM_CLASS_NAME — the exposed name of the UOM class, aliasing the base column UOM_CLASS. This is the primary identifier presented to consumers.
• END_EFFECTIVE_DATE — the date on which the UOM class ceases to be effective, aliasing the base DISABLE_DATE. A null value indicates the class remains active.
• DESCRIPTION — the free-text description of the class, unchanged from the base table.
• _DF — the literal column carrying the descriptive flexfield reference string identifier.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — audit columns recording the most recent change to the record and the user responsible.
• CREATION_DATE / CREATED_BY — audit columns recording the original insertion timestamp and user.

The audit and effective-date columns support both historical reporting and change-tracking. The re-mapping of UOM_CLASS and DISABLE_DATE into UOM_CLASS_NAME and END_EFFECTIVE_DATE is the principal value the view adds over the base table.

Common Use Cases and Queries

Typical scenarios include validating that an item's assigned UOM belongs to an active class, extracting UOM class reference data for interfaces and conversions, and generating setup audit reports. The following query retrieves all currently effective UOM classes:

SELECT uom_class_name, description, creation_date
FROM apps.invfv_uom_classes
WHERE end_effective_date IS NULL
ORDER BY uom_class_name;

To audit recently maintained class definitions:

SELECT uom_class_name, last_updated_by, last_update_date
FROM apps.invfv_uom_classes
WHERE last_update_date > SYSDATE - 30;

Because the view is read only and unfiltered, it is well suited to data extraction into conversion or reporting schemas, and to lookup queries that must remain insulated from future column changes in MTL_UOM_CLASSES.