Search Results ref_um

Overview

SY_UOMS_MST_V is a read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the GMA product family, Process Manufacturing Systems, and presents a consolidated master list of units of measure used across process manufacturing and inventory operations. Rather than maintaining a dedicated storage table, the view derives its result set from Oracle Inventory's unit-of-measure and conversion tables, applying decoding logic at query time to normalize the unit-of-measure code exposed to callers.

The view exists to give GMA applications and their integrations a stable, denormalized access point to unit-of-measure definitions, including description, class, and conversion factor. Because it resolves conversion data for non-item conversions, it supports reporting and validation logic where a calling program needs a class-level unit of measure rather than an item-specific one. The object is documented as VALID, indicating that it compiles successfully and that its dependencies on the underlying Inventory synonyms resolve without error.

Underlying Base Objects

The view is defined over two documented base objects, both exposed through synonyms:

• MTL_UNITS_OF_MEASURE — the Inventory master table holding each unit of measure, its code, description, class, conversion rate, and audit columns.
• MTL_UOM_CONVERSIONS — the Inventory conversion table that maps units of measure to conversion rates and, optionally, to specific inventory items.

The join is driven by UNIT_OF_MEASURE equality between the two tables, restricted by the predicate UOMC.INVENTORY_ITEM_ID = 0. This restriction selects the class-level, non-item-specific conversion row, so each unit of measure is returned with its standard master conversion rate rather than an item override.

Key Columns

• UM_CODE — the user-facing unit-of-measure code. It is derived with a DECODE that returns UNIT_OF_MEASURE unchanged when its byte length is between one and four characters, and falls back to UOM_CODE otherwise.
• UM_DESC — the first 40 characters of the source description, returned as a SUBSTR of MTL_UNITS_OF_MEASURE.DESCRIPTION.
• UM_TYPE — sourced from UOM_CLASS, identifying the unit-of-measure class.
• STD_FACTOR — the conversion rate from the class-level conversion row.
• UNIT_OF_MEASURE / UOM_CODE — the raw underlying identifiers carried through for traceability.
• DELETE_MARK — a derived flag computed as DECODE(SIGN(SYSDATE-DISABLE_DATE), 1, 1, 0), indicating whether the unit of measure has passed its disable date.
• Audit columns — LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY.

Additional columns listed in the metadata, such as DELETE_MARK, TEXT_CODE, RND_FACTOR, REF_UM, and TRANS_CNT, are exposed for compatibility with consumers expecting the full master shape; only the columns selected in the documented view text carry values from the two base tables.

Common Use Cases and Queries

Because the user searched on "um_code", the most frequent access pattern is retrieval of a unit-of-measure by its code. A representative query is:

• SELECT um_code, um_desc, um_type, std_factor FROM apps.sy_uoms_mst_v WHERE um_code = 'KG';
• SELECT um_code, um_desc, std_factor FROM apps.sy_uoms_mst_v WHERE um_type = 'MASS' ORDER BY um_code;
• SELECT um_code, um_desc FROM apps.sy_uoms_mst_v WHERE delete_mark = 0;

Typical scenarios include populating unit-of-measure lists in process manufacturing forms and concurrent programs, validating a unit of measure supplied by an external interface, and driving conversion calculations in batch reporting where the class-level standard factor is sufficient. Integrations often join SY_UOMS_MST_V to item or transaction data on um_code to resolve descriptive text for output files. As with any APPS-owned view, consumers should treat it as read-only and avoid DML.