Search Results mtl_units_of_measure_tl




Overview
Explore in AI Chat

Overview

EGO_GTIN_ATTRS_V is an APPS-owned database view in the Oracle E-Business Suite Advanced Product Catalog (EGO) module. It presents Global Trade Item Numbers (GTINs) together with the associated Global Data Synchronization Network (GDSN) attributes for an inventory item, resolved at the organization level. Per the ETRM documentation, the view is defined as single-row only, meaning it returns exactly one consolidated record per item/organization/GTIN combination rather than a repeating attribute-per-row layout. Its stated purpose is to supply the payload required by the GDSN for Regulatory Content and Item Registration (RCIR) messages, making it an integration-facing object rather than a purely reporting artifact.

The view is exposed in both Oracle EBS 12.1.1 and 12.2.2 with the same owner and definition; the documented 12.2.2 metadata confirms its referenced base objects and VALID status in the APPS schema. Because it flattens both item master attributes and GTIN-specific GDSN attributes into a single row, it is well suited to data synchronization interfaces and downstream XML generation for trade item publication.

Underlying Base Objects

The view draws from a mix of item master, cross-reference, category, GTIN attribute, and lookup sources. The documented referenced objects are:

Key Columns

Common Use Cases and Queries

Typical usage centers on GDSN/RCIR message generation and GTIN attribute verification. A representative query retrieves the consolidated GDSN attributes for a specific item:

  • SELECT organization_id, inventory_item_id, global_trade_item_number, brand_owner_gln, brand_owner_name, is_trade_item_a_base_unit, net_weight, uom_weight FROM ego_gtin_attrs_v WHERE organization_id = :org_id AND inventory_item_id = :item_id;
  • Reporting all published GTINs for an organization: SELECT global_trade_item_number, brand_owner_name, target_market_country_code FROM ego_gtin_attrs_v WHERE organization_id = :org_id;
  • Validating physical dimensions and unit flags prior to synchronization: SELECT inventory_item_id, depth, uom_depth, height, uom_height, width, uom_width, is_trade_item_a_consumer_unit FROM ego_gtin_attrs_v WHERE inventory_item_id = :item_id;

Because the view is single-row only, no DISTINCT or aggregation is required for item-level extraction. Note that the diameter expression depends on MTL_UNITS_OF_MEASURE_TL and INV_CONVERT, so queries should ensure the item has a valid base UOM and diameter attribute to avoid NULL results.