Results for “mtl_uom_classes”

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

Overview

INVBV_UOM_CLASSES is a read-only Oracle EBS view owned by the APPS schema and registered under the INV (Inventory) product module. The "BV" naming convention indicates a backward-compatibility or business view layer, and the ETRM metadata explicitly labels this object as "Retrofitted," indicating it was introduced or re-created to preserve compatibility with an earlier interface, report, or custom extension. Its status is VALID in the documented 12.1.1 / 12.2.2 environment.

The view exposes unit-of-measure (UOM) class definitions maintained in Oracle Inventory. UOM classes are the categorization mechanism used by Inventory to group related units of measure — for example, Quantity, Weight, Volume, or Time — and to determine which base UOM and conversion rules apply to a given class. INVBV_UOM_CLASSES provides a stable, denormalized access point to this class-level metadata for reporting, integration, and custom code that must not query the underlying table directly.

Because it is defined with the WITH READ ONLY clause, the view is strictly a query surface. It cannot be used for DML, which reinforces its role as a controlled reporting and integration interface rather than a transactional object.

Underlying Base Objects

The view is defined over a single documented base object: MTL_UOM_CLASSES, accessed through a synonym in the APPS schema. The view text selects from this table using the alias UO and projects the class identifier, effective-dating and descriptive attributes, and the standard EBS audit columns.

MTL_UOM_CLASSES is the Inventory master table for UOM class definitions. Each row represents one UOM class, and the class is subsequently referenced by the units of measure themselves (MTL_UNITS_OF_MEASURE) and by conversion definitions at the class and item level. INVBV_UOM_CLASSES therefore sits one level above individual UOMs in the Inventory hierarchy: it abstracts the class header record without exposing the child UOM records, which remain accessible through their own views and tables.

Because the relationship is one table to one view, INVBV_UOM_CLASSES preserves the cardinality of MTL_UOM_CLASSES. No joins, unions, or aggregations are applied, so row counts and primary key uniqueness on the class identifier are maintained. The WITH READ ONLY restriction is inherited by all consumers, including concurrent programs and BI Publisher data sets that reference the view.

Key Columns

• UOM_CLASS_NAME — The logical class identifier exposed by the view. In the base table this originates from the UOM_CLASS column and corresponds to the user-defined class code that identifies the class throughout Inventory.
• END_EFFECTIVE_DATE — The class disable/end date, mapped from DISABLE_DATE on MTL_UOM_CLASSES. A null value indicates the class is active; a populated value indicates the date from which the class is no longer available for new assignments.
• DESCRIPTION — The descriptive text for the UOM class, used in reports and lookup screens.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard EBS audit columns recording when and by which user the class record was most recently modified.
• CREATION_DATE, CREATED_BY — Standard EBS audit columns recording the original insertion of the class record.

The audit columns are significant for reconciliation and data-governance reporting, since they allow changes to class definitions to be tracked without querying the base table.

Common Use Cases and Queries

Typical uses include validating that a class is active before assigning items, listing classes for a setup report, and feeding downstream integrations that require class-level metadata. A basic listing of active classes:

• SELECT uom_class_name, description FROM apps.invbv_uom_classes WHERE end_effective_date IS NULL ORDER BY uom_class_name;
• SELECT uom_class_name, end_effective_date, last_update_date, last_updated_by FROM apps.invbv_uom_classes WHERE last_update_date >= :p_since_date; — for change-audit reporting.
• SELECT uom_class_name FROM apps.invbv_uom_classes WHERE end_effective_date IS NULL OR end_effective_date > SYSDATE; — to identify classes valid as of the current date.

Because the view is read only, all access is limited to SELECT statements. Organizations migrating custom code forward should treat INVBV_UOM_CLASSES as the preferred interface for class-level queries, insulating reports from future changes to MTL_UOM_CLASSES.