Search Results msc_uom_class_conversions_u2

Overview

MSC.MSC_UOM_CLASS_CONVERSIONS is a transactional data table in the MSC (Advanced Supply Chain Planning) schema that stores inter-class unit of measure conversion definitions at the item level. In Oracle EBS 12.1.1 and 12.2.2, each item belongs to a base unit of measure class, and that class has a single base unit of measure. Where an item must be planned, transacted, or reported in the base unit of a different class, the conversion factor between the two class base units is captured here. The table therefore supplies the planning engine with the arithmetic bridge between an item's native class base unit and the base unit of any other class in which that item is expressed.

The heuristic Data Vault classification mined from the foreign key structure is link. This is a sensible modeling suggestion: the row resolves a many-to-many style association between an item and the unit-of-measure definitions it converts between, with the descriptive CONVERSION_RATE and DISABLE_DATE attributes acting as link-level qualifiers rather than as independent satellite content. The primary key, MSC_UOM_CLASS_CONVERSIONS_PK, is composed of INVENTORY_ITEM_ID, FROM_UNIT_OF_MEASURE, and TO_UNIT_OF_MEASURE, confirming the link interpretation.

The table resides in the APPS_TS_TX_DATA tablespace, with its two unique indexes in APPS_TS_TX_IDX. Its status is VALID and it is registered as FND Design Data under MSC.MSC_UOM_CLASS_CONVERSIONS.

Key Information Stored

The columns of greatest operational importance are the following.

• INVENTORY_ITEM_ID — the inventory item for which the inter-class conversion is defined. Mandatory, and the leading column of both unique indexes and the primary key.
• FROM_UNIT_OF_MEASURE — the base unit of measure of the item's base class; the source side of the conversion.
• FROM_UOM_CODE — the short name of that base unit.
• FROM_UOM_CLASS — the class of the item's base unit.
• TO_UNIT_OF_MEASURE — the base unit of the class to which the conversion is defined; the target side.
• TO_UOM_CODE — the short name of the target base unit.
• TO_UOM_CLASS — the class to which the conversion is defined.
• CONVERSION_RATE — the numeric factor that converts the item's class base unit into the "to" class base unit.
• DISABLE_DATE — the date after which the defined inter-class conversion may no longer be used, giving the row a time-bounded validity.
• SR_INSTANCE_ID and REFRESH_NUMBER — source application instance identifier and refresh number, used to track the origin and collection cycle of the row in the planning data repository.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, together with the concurrent Who columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Two business-key candidates are documented. The unique index MSC_UOM_CLASS_CONVERSIONS_U1 covers INVENTORY_ITEM_ID, FROM_UNIT_OF_MEASURE, and TO_UNIT_OF_MEASURE, and is the user's likely search target. The unique index MSC_UOM_CLASS_CONVERSIONS_U2 covers INVENTORY_ITEM_ID and TO_UOM_CODE. The 36-column physical schema also includes ATTRIBUTE_CATEGORY and fifteen descriptive ATTRIBUTE columns reserved for extensibility.

Common Use Cases and Queries

The most frequent requirement is to retrieve the conversion factor for a given item between two class base units, typically for on-hand aggregation or planning output reconciliation.

• Point lookup of a conversion rate: SELECT conversion_rate FROM msc.msc_uom_class_conversions WHERE inventory_item_id = :item AND from_unit_of_measure = :from AND to_unit_of_measure = :to
• Validation of duplicate or conflicting definitions per item, using the U1 index columns as the grouping key.
• Expiry reporting: filter on disable_date IS NULL OR disable_date > SYSDATE to isolate currently effective conversions.
• Source-tracking diagnostics: group by SR_INSTANCE_ID and REFRESH_NUMBER to confirm which collection instance supplied a conversion, useful when planning results disagree with transactional data.
• Class-level reporting: join FROM_UOM_CLASS to TO_UOM_CLASS to produce a matrix of supported inter-class conversions per item.

Related Objects

The foreign keys documented for this table reference MSC.MSC_UNITS_OF_MEASURE on both FROM_UNIT_OF_MEASURE and TO_UNIT_OF_MEASURE, so any query resolving unit descriptions joins MSC_UNITS_OF_MEASURE twice against the same table.

• MSC.MSC_UNITS_OF_MEASURE — joined on from_unit_of_measure and, with an alias, on to_unit_of_measure.
• INV.MTL_SYSTEM_ITEMS_B — the item master supplying the descriptive context for INVENTORY_ITEM_ID.
• MSC.MSC_SYSTEM_ITEMS — the MSC-side item repository used by the planning engine alongside this table.
• INV.MTL_UOM_CONVERSIONS — the source-side conversion definitions from which planning data is collected, useful for comparing EBS and planning values.

Because conversion rows are collected into the planning schema, the originating inventory conversion table and the MSC item and unit-of-measure tables constitute the core dependency set for impact analysis.