Search Results uom_depth




Overview
Explore in AI Chat

Overview

The APPS.EGO_GTIN_UCCNET_HIER_ATTRS_V view is a reporting and integration object delivered within the Oracle E-Business Suite Advanced Product Catalog (EGO) module. Its documented purpose is to expose Global Trade Item Numbers (GTINs) alongside the complete set of GDSN (Global Data Synchronization Network) attributes associated with each item. The view is defined to return a single row per GTIN, which makes it suitable for outbound message construction where a flattened, one-record-per-trade-item shape is required.

The view is used specifically to send CIN (Catalog Item Notification) messages through the UCCnet/GDSN data pool integration. Because it aggregates item master data, unit-of-measure conversions, cross-reference GTINs, and extended GTIN attribute values into a single projection, it serves as the primary extraction source for party, trade item, and measurement segments of the outbound CIN document. It is valid in both 12.1.1 and 12.2.2, with the documented metadata referencing 12.2.2 base objects.

Underlying Base Objects

The view is defined over a combination of item master, category, cross-reference, lookup, and GTIN attribute objects. Documented referenced base objects include:

Dimension and weight columns are sourced from MTL_SYSTEM_ITEMS_KFV, while GTIN-specific attributes such as brand owner and temperature ranges are drawn from the EGO GTIN attribute tables.

Key Columns

The most relevant column for users researching uom_height is UOM_HEIGHT, which is populated from MSI.DIMENSION_UOM_CODE. The view exposes the height value in UNIT_HEIGHT and the associated unit of measure in UOM_HEIGHT, so that the trade item measurement is unambiguously qualified. Parallel columns exist for UOM_DEPTH and UOM_WIDTH, all mapped to the same DIMENSION_UOM_CODE, plus UNIT_WEIGHT and WEIGHT_UOM_CODE.

Other notable columns include ORGANIZATION_ID and INVENTORY_ITEM_ID (item key), GLOBAL_TRADE_ITEM_NUMBER, CONCATENATED_SEGMENTS, BRAND_OWNER_GLN, BRAND_OWNER_NAME, STORAGE_HANDLING_TEMP_MAX/MIN with their corresponding UOM columns, DIAMETER and UOM_DIAMETER (derived via INV_CONVERT.INV_UM_CONVERT), and several DECODE-based indicator columns for consumer unit, base unit, variable unit, orderable, shippable, and invoice-enabled flags.

Common Use Cases and Queries

Typical use cases include CIN message generation, GTIN data audits, and verification of trade item measurements such as height, width, depth, and weight. A representative query to inspect height UOM data follows:

  • SELECT organization_id, inventory_item_id, global_trade_item_number, unit_height, uom_height, unit_width, uom_width FROM apps.ego_gtin_uccnet_hier_attrs_v WHERE organization_id = :org_id;
  • SELECT global_trade_item_number, unit_height, uom_height FROM apps.ego_gtin_uccnet_hier_attrs_v WHERE global_trade_item_number = :gtin;
  • SELECT inventory_item_id, concatenated_segments, unit_height, uom_height, unit_weight, weight_uom_code FROM apps.ego_gtin_uccnet_hier_attrs_v ORDER BY inventory_item_id;

Because UOM_HEIGHT derives from DIMENSION_UOM_CODE rather than a dedicated height UOM field, users should confirm that the item's dimension UOM reflects the intended measurement standard before publishing GTIN data.