Search Results global_location_number

Overview

The view EGO_GTIN_TP_ATTRS_V belongs to the Advanced Product Catalog (EGO) module of Oracle E-Business Suite and is owned by the APPS schema. It exposes trading-partner-specific Global Trade Item Number (GTIN) attributes, combining item-level master data with partner/party-site-level overrides. The view is central to scenarios where a single inventory item is published to a trading partner (a customer or a supplier identified by a Global Location Number, or GLN), and the physical, ordering, and commercial attributes of that item must be resolved in the context of that specific partner.

The user search term "global_location_number" maps directly to the view's GLOBAL_LOCATION_NUMBER column (sourced from the TP_GLN column of EGO_UCCNET_EVENTS). This column identifies the trading partner location to which a GTIN publication applies. The view therefore serves as a reporting and integration surface for GS1/UCCnet-style item publications in Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS synonyms:

• EGO_UCCNET_EVENTS — the driving table. It supplies the inventory item, organization, GTIN, trading partner GLN, party site, and event type. The view filters on EVENT_TYPE = 'PUBLICATION', restricting output to published item records.
• MTL_SYSTEM_ITEMS_B — the item master. It provides default flags and attributes that apply when no partner-specific override exists.
• EGO_ITEM_GTN_ATTRS_B — global (non-partner-specific) GTN attributes for the item, such as order quantity minimums/maximums and availability dates.
• EGO_ITEM_CUST_ATTRS_B — customer (trading-partner) specific GTN attributes, which take precedence over the global values via outer joins.

Joins are performed on INVENTORY_ITEM_ID and ORGANIZATION_ID across all tables, with the customer attributes table additionally joined on MASTER_ORGANIZATION_ID and PARTY_SITE_ID using outer joins. This design lets the view fall back to item-master or global values when no partner-specific record exists.

Key Columns

• INVENTORY_ITEM_ID / ORGANIZATION_ID — the item and inventory organization identifiers.
• GLOBAL_TRADE_ITEM_NUMBER — the GTIN (from UE.GTIN) assigned to the item.
• GLOBAL_LOCATION_NUMBER — the trading partner GLN, identifying the partner location for the publication.
• IS_TRADE_ITEM_AN_ORD_UNIT — derived from CUSTOMER_ORDER_ENABLED_FLAG; indicates whether the item is an orderable trade unit.
• IS_TRADE_ITEM_A_DESPATCH_UNIT — derived from the customer attribute or, failing that, SHIPPABLE_ITEM_FLAG.
• IS_TRADE_ITEM_AN_INVOICE_UNIT — derived from the customer attribute or INVOICE_ENABLED_FLAG.
• START_AVAILABILITY_DATE_TIME / END_AVAILABILITY_DATE_TIME — partner-specific or global availability windows.
• MIN_TRADE_ITEM_LIFE_ARR, ORDER_QUANTITY_MIN, ORDER_QUANTITY_MAX — commercial and shelf-life attributes resolved via NVL precedence.
• PUBLICATION_DATE — set to SYSDATE in the view text.
• BATCH_ID / SUBBATCH_ID — publication batch identifiers from the UCCnet events table.

Common Use Cases and Queries

Typical uses include auditing published GTINs per trading partner location, verifying which item attributes are being transmitted to a partner, and troubleshooting data-synchronization discrepancies between item master and partner-specific values.

SELECT INVENTORY_ITEM_ID,
       ORGANIZATION_ID,
       GLOBAL_TRADE_ITEM_NUMBER,
       GLOBAL_LOCATION_NUMBER,
       IS_TRADE_ITEM_AN_ORD_UNIT,
       ORDER_QUANTITY_MIN,
       ORDER_QUANTITY_MAX
FROM   APPS.EGO_GTIN_TP_ATTRS_V
WHERE  GLOBAL_LOCATION_NUMBER = :p_gln
AND    INVENTORY_ITEM_ID = :p_item_id;

The view is read-only reference metadata; it is not maintained directly and should be queried with the same care applied to any multi-table join, particularly when filtering on the trading partner GLN or a specific inventory organization.