Results for “uom_desc”

2 results




Overview
Explore in AI Chat

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

Overview

PMIFV_UOM_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PMI (Process Manufacturing Intelligence) product family. Its documented purpose is to present Process Manufacturing units of measure alongside their associated conversion factors. The "FV" naming convention identifies it as a foundation view within the Process Manufacturing Intelligence schema, a set of database objects that expose Process Manufacturing master and transactional data in a flattened, reporting-friendly form.

Functionally, the view serves as a denormalized lookup over the units-of-measure definitions and unit-of-measure type classifications used by Oracle Process Manufacturing. Because it joins the UOM master to its type definition and filters out logically deleted rows, consumers obtain a clean, current list of valid units with their standard conversion factors, rounding factors, reference (base) units, and the standard UOM implied by each unit's type. In EBS 12.1.1 and 12.2.2, this makes PMIFV_UOM_V a convenient integration and reporting surface for any process-manufacturing extract, interface, or Operational Data Store load that must translate or validate units of measure, particularly where a search for the term standard_uom is involved, since that attribute is exposed directly as the STANDARD_UOM column. ETRM classifies the object with status VALID.

Underlying Base Objects

The view text is a straightforward equijoin of two objects, both accessed through synonyms in the APPS schema:

The join condition is UOMMASTER.UM_TYPE = UOMTYPE.UM_TYPE. Both sides are constrained with DELETE_MARK = 0, implementing the standard Oracle logical-delete pattern and ensuring that only active units and active unit types are returned. The view is declared WITH READ ONLY, so no DML may be issued against it. Because the relationship between master rows and type rows is a simple foreign-key lookup on UM_TYPE, each returned row represents one unit of measure enriched by exactly one type definition.

Key Columns

  • UOM_CODE — the unit of measure code (UM_CODE); the primary business key for a unit.
  • UOM_DESC — the descriptive name of the unit of measure.
  • STANDARD_FACTOR — the standard conversion factor (STD_FACTOR) used to convert the UOM to its reference unit.
  • ROUNDING_FACTOR — the rounding precision or factor (RND_FACTOR) applied when converting quantities into this unit.
  • REFERENCE_UOM — the reference (target) unit against which the standard factor is expressed (REF_UM).
  • UOM_TYPE — the code of the unit-of-measure class to which the unit belongs.
  • TYPE_DESCRIPTION — the descriptive text for that class, resolved from SY_UOMS_TYP.
  • STANDARD_UOM — the standard or base UOM defined for the unit's type (STD_UM), resolved through the join.
  • CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY — the WHO audit columns from the master row.

Common Use Cases and Queries

Typical consumers use the view to populate UOM dimension tables in a data warehouse, to drive LOV-style lookups in custom Process Manufacturing forms, or to validate conversion inputs in integrations. Auditing the WHO columns supports impact analysis of UOM definition changes.

Standard conversion-factor lookup for a specific unit:

  • SELECT uom_code, uom_desc, standard_factor, rounding_factor, reference_uom FROM apps.pmifv_uom_v WHERE uom_code = :p_uom_code;

Listing all units belonging to a given UOM type, with the type's standard UOM:

  • SELECT uom_code, uom_desc, standard_uom FROM apps.pmifv_uom_v WHERE uom_type = :p_uom_type ORDER BY uom_code;

Searching by description when the exact code is unknown, for example resolving a "standard_uom" reference:

  • SELECT uom_code, uom_desc, standard_factor, standard_uom FROM apps.pmifv_uom_v WHERE UPPER(uom_desc) LIKE UPPER('%' || :p_search || '%');

Because the view is read-only and pre-filtered on DELETE_MARK, it can be queried directly without additional validity predicates, and it may be safely joined to other PMI foundation or transactional views on UOM_CODE.