Results for “to_uom_code”

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

Overview

The APPS.PMITS_ITEM_LOT_UOM_CONV_V view is a reporting and integration object belonging to the Process Manufacturing Intelligence (PMI) product family, which is documented as obsolete in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose unit-of-measure (UOM) conversion factors at the item-lot level, a granularity that is not available from the standard item-level conversion views shipped with Oracle Process Manufacturing (OPM). The view is owned by the APPS schema and holds a VALID status, meaning it remains compiled and queryable even though its parent product is no longer actively marketed.

Because conversion factors can vary by lot in process manufacturing—where a specific lot may exhibit a different density, potency, or concentration than the item default—this view provides the join path between item master data, lot master data, and the UOM type definitions required to translate a quantity expressed in one UOM type into another. It is most commonly consumed by custom reports, BI Publisher data templates, and outbound integration extracts that need lot-specific conversion logic.

Underlying Base Objects

The view definition draws on five documented base objects registered in ETRM as synonyms or views:

• IC_ITEM_CNV (synonym) — the OPM item conversion table, supplying UM_TYPE, TYPE_FACTOR, TYPE_FACTORREV, and audit columns.
• IC_ITEM_MST (synonym) — the OPM item master, providing ITEM_ID, ITEM_NO, and the base ITEM_UM.
• IC_LOTS_MST (synonym) — the OPM lot master, supplying LOT_ID, LOT_NO, and SUBLOT_NO.
• SY_UOMS_TYP_V (view) — the UOM type view, aliased twice: once as FROM_UOM_TYP driven by the item's base UOM and once as TO_UOM_TYP driven by the conversion's UM_TYPE.
• SY_UOMS_MST_V (view) — the UOM master view, aliased as FROM_ITEM_UOM, used to resolve the item's UOM code to its UOM type.

The joins link the conversion row to both the item and the lot on the shared ITEM_ID and LOT_ID keys, ensuring only conversions scoped to a specific lot are returned.

Key Columns

• LOT_ID, LOT_NO, SUBLOT_NO — the lot and sublot identifiers at which the conversion applies.
• ITEM_ID, ITEM_NO, ITEM_UM — the item identity and its base stocking UOM.
• UM_TYPE — the target UOM type of the conversion, resolved through TO_UOM_TYP.
• FROM_UOM_TYPE, FROM_UOM_CODE — the source UOM type and code derived from the item's base UOM.
• TO_UOM_CODE — the target standard UOM code (STD_UM) for the conversion's UOM type.
• TYPE_FACTOR and TYPE_FACTORREV — the forward and reverse conversion factors between the two UOM types.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus DELETE_MARK and TEXT_CODE for OPM soft-delete and descriptive flexfield traceability.

Common Use Cases and Queries

Typical scenarios include deriving lot-specific conversion factors for inventory transactions, validating conversion setup before lot release, and producing reconciliation reports between OPM and downstream systems. A representative query retrieves the conversion factors for a given item across all its lots:

SELECT ITEM_NO, LOT_NO, SUBLOT_NO,
       FROM_UOM_CODE, TO_UOM_CODE,
       TYPE_FACTOR, TYPE_FACTORREV
FROM   APPS.PMITS_ITEM_LOT_UOM_CONV_V
WHERE  ITEM_NO = :p_item
AND    NVL(DELETE_MARK, 0) = 0;

Because DELETE_MARK is exposed, consumers should always filter marked-deleted rows to avoid returning stale conversion definitions. Note that the view is flagged obsolete; new development should evaluate supported alternatives in OPM or Inventory UOM APIs, while existing customizations referencing this object can continue to rely on it in 12.1.1 and 12.2.2 environments.