Results for “uom_code”

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

Overview

PMIBV_UOM_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered as VALID and delivered as part of the PMI — Process Manufacturing Intelligence — product family. The view exposes Process Manufacturing units of measure together with their associated conversion factors, providing a denormalized, reporting-friendly projection of the master unit-of-measure definition. Its purpose is to present UOM metadata in a stable, queryable form without requiring consumers to understand the underlying Process Manufacturing table structure directly. Because the object is defined as a view rather than a table, it carries no storage of its own and always reflects the current committed state of its base data. The view is implemented with a WITH READ ONLY clause, so any attempt to insert, update, or delete through it will fail; it is intended strictly for query and extraction workloads. In EBS 12.1.1 and 12.2.2 the object remains documented within ETRM with the same column list, making it a dependable reference point for both on-premise reporting and integration extracts.

Underlying Base Objects

The view is defined over a single documented base object, SY_UOMS_MST, referenced through the alias UOMMASTER. In the ETRM metadata SY_UOMS_MST is recorded as a SYNONYM, which resolves to the Process Manufacturing UOM master table in the APPS environment. The view text selects directly from this object with no joins, unions, or aggregations, and applies one predicate: WHERE UOMMASTER.DELETE_MARK = 0. This filter suppresses logically deleted unit-of-measure records, so consumers see only active definitions. The column list is a direct projection of base columns — UM_CODE, UM_DESC, STD_FACTOR, RND_FACTOR, REF_UM, UM_TYPE, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATED_BY — re-exposed under the view's own column names. The COMMENTS in the view text group these into "REGULAR ATTRIBUTES", "ID", and "WHO" categories, mirroring the standard EBS WHO-column convention. Relationship-wise, the view is one-to-one with the filtered base table: every surviving row in SY_UOMS_MST produces exactly one row in PMIBV_UOM_V. Consequently, PMIBV_UOM_V is in effect the single authoritative reporting surface for Process Manufacturing UOM master data.

Key Columns

• UOM_CODE (base UM_CODE) — the unique short code identifying the unit of measure.
• UOM_DESC (base UM_DESC) — the descriptive name of the unit of measure; this is the column users typically target when searching for "uom_desc".
• STANDARD_FACTOR (base STD_FACTOR) — the standard conversion factor relating the unit to its reference unit.
• ROUNDING_FACTOR (base RND_FACTOR) — the precision/rounding value applied when converting quantities expressed in this unit.
• REFERENCE_UOM (base REF_UM) — the unit of measure against which the standard factor is defined.
• UOM_TYPE (base UM_TYPE) — classifies the unit (for example, by measurement category), governing how it may be used in conversions.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard EBS WHO columns supporting audit and change tracking.

Note the distinction between the view's exposed names and the underlying base column names; queries against the view must use UOM_CODE and UOM_DESC, not UM_CODE and UM_DESC.

Common Use Cases and Queries

Typical scenarios include validating conversion factors during Process Manufacturing data migration, populating UOM drop-downs in custom forms and OAF/ADF pages, performing dependency analysis prior to changing a rounding rule, and extracting a UOM reference set for a downstream warehouse. Because the view already excludes deleted rows, consumers avoid re-implementing the DELETE_MARK filter. A simple lookup by description:

SELECT uom_code, uom_desc, uom_type
FROM   apps.pmibv_uom_v
WHERE  UPPER(uom_desc) LIKE '%KILOGRAM%';

Listing conversion relationships for a reference unit:

SELECT uom_code, uom_desc, standard_factor, rounding_factor
FROM   apps.pmibv_uom_v
WHERE  reference_uom = 'KG'
ORDER  BY uom_code;

Auditing recently maintained definitions:

SELECT uom_code, uom_desc, last_updated_by, last_update_date
FROM   apps.pmibv_uom_v
WHERE  last_update_date >= SYSDATE - 30
ORDER  BY last_update_date DESC;

Joining to transaction or formula data is straightforward since UOM_CODE follows the standard Process Manufacturing code convention. All queries should be run with the APPS schema in the FROM clause or via a synonym, and remain strictly read-only.