Results for “user_attribute14”

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

Overview

The EDW_MTL_UOM_CLS_CONV_F_IV view is an Oracle Inventory (INV) reporting object that belongs to the Enterprise Data Warehouse (EDW) family of interface views supplied within Oracle E-Business Suite. It exposes unit-of-measure (UOM) class conversion data in a flattened, denormalized form suitable for extraction, transformation, and loading into external reporting or data warehousing environments. The "F_IV" suffix convention identifies it as a fact-style interface view intended primarily for downstream analytical consumption rather than for transactional processing within the EBS application itself.

Because it surfaces UOM conversion rates alongside descriptive flexfield-style user attributes, the view supports cross-referential analysis between inventory item conversions and any custom metadata captured on the underlying conversion records. This is particularly relevant for organizations that leverage the fifteen user-defined attribute columns for business-specific classification, such as conversion reason codes, routing identifiers, or regulatory tags.

Underlying Base Objects

According to the ETRM metadata, no base objects are formally documented for this view, and the object is noted as "Not implemented in this database." The view definition itself is a straightforward SELECT with a ROWID-based surrogate key and no joins or aggregations, indicating it reads directly from a single underlying EDW table, referenced in the view text as EDW_MTL_UOM_CLS_CONV_F. That base table stores the class conversion facts from which the interface view projects its columns.

The view is best understood as a thin projection layer: it renames the physical ROWID to ROW_ID, exposes foreign key surrogate columns (FROM_BASE_UOM_FK_KEY, TO_BASE_UOM_FK_KEY, INSTANCE_FK_KEY, UOM_CLS_CONV_PK_KEY), and appends a constant OPERATION_CODE of a single space. This pattern is typical of EBS EDW interface views, which are designed to present a stable, extraction-friendly column list irrespective of changes to the physical fact table.

Key Columns

• ROW_ID — Surrogate identifier derived from the physical ROWID of the underlying fact row.
• UOM_CLS_CONV_PK — Primary key of the UOM class conversion entity being described.
• INVENTORY_ITEM_ID — Identifier of the inventory item to which the conversion applies.
• CONVERSION_RATE — The numeric factor expressing the relationship between the from- and to- base units of measure.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE15 — Fifteen descriptive flexfield-style columns carrying customer-defined metadata. USER_ATTRIBUTE14 is the fourteenth of these and is frequently used for organization-specific classification.
• USER_MEASURE1 through USER_MEASURE5 — Numeric user-defined measure columns.
• LAST_UPDATE_DATE / CREATION_DATE — Standard audit timestamps supporting incremental extraction.
• FROM_BASE_UOM_FK_KEY, TO_BASE_UOM_FK_KEY, INSTANCE_FK_KEY, UOM_CLS_CONV_PK_KEY — Foreign-key surrogate keys enabling joins to dimension views in the EDW model.
• OPERATION_CODE — A placeholder column returned as a single space, retained for interface consistency.

Common Use Cases and Queries

Typical usage involves extracting UOM class conversion facts for loading into a warehouse, reconciling conversion rates per item, or reporting on user-defined attribute values such as USER_ATTRIBUTE14. The following query illustrates retrieving item conversions where the fourteenth user attribute is populated:

SELECT INVENTORY_ITEM_ID, CONVERSION_RATE, USER_ATTRIBUTE14
FROM EDW_MTL_UOM_CLS_CONV_F_IV
WHERE USER_ATTRIBUTE14 IS NOT NULL;

A second common pattern joins the surrogate keys back to EDW dimension views to resolve the from and to units of measure, then filters on the audit dates for incremental refreshes:

SELECT c.INVENTORY_ITEM_ID, c.CONVERSION_RATE, c.USER_ATTRIBUTE14
FROM EDW_MTL_UOM_CLS_CONV_F_IV c
WHERE c.LAST_UPDATE_DATE >= :last_run_date;

Because the view is read-only and fact-oriented, it should be used for reporting and integration only. Direct DML against it is not supported, and any modifications to user attributes must be performed on the source conversion tables within the Inventory module, with the view reflecting those changes on the next warehouse refresh cycle.