Search Results publication_status




Overview
Explore in AI Chat

Overview

APPS.EGO_ITEM_GTIN_V is a Business Intelligence System (BIS) view in the Oracle E-Business Suite APPS schema, registered under FND Design Data as EGO.EGO_ITEM_GTIN_V and carrying a VALID status. Its purpose is to expose Global Trade Item Number (GTIN) assignments for inventory items in a flattened, organization-aware form suitable for reporting and integration. A GTIN is the standardized identifier used to represent a trade item in barcode and catalog exchange contexts, and in EBS it is maintained against inventory items as part of item cross-reference data.

Because the view is defined as a BIS view, it is intended primarily for read-only consumption by reporting tools, discoverer workbooks, data extraction routines, and external integration layers that require item-to-GTIN relationships without having to resolve the multi-table structure maintained by the item master and cross-reference entities. It resolves organization context through MTL_PARAMETERS, allowing a single query to return GTIN records with the relevant item number, master organization, unit of measure, and publication status.

Underlying Base Objects

The view is defined over the following documented objects:

  • EGO_ITEM_GTN_ATTRS_VL (VIEW) — supplies the GTIN attribute information, including the GTIN value, description, trade item descriptor, unit of measure, and publication status.
  • MTL_CROSS_REFERENCES (SYNONYM) — provides the item cross-reference relationship that ties an item to its GTIN, since GTINs are stored as cross-reference types in the item master.
  • MTL_PARAMETERS (SYNONYM) — supplies organization-level parameters, including the master organization context used to resolve organization identifiers.
  • MTL_SYSTEM_ITEMS_KFV (SYNONYM) — the key-flexfield item view supplying INVENTORY_ITEM_ID, ORGANIZATION_ID, ITEM_NUMBER, and master organization relationships.
  • MTL_UNITS_OF_MEASURE (SYNONYM) — provides the unit of measure code and descriptive unit of measure text.

The view is not referenced by any other database object, confirming that it functions purely as a terminal reporting layer rather than as a building block for further views or program logic.

Key Columns

  • INVENTORY_ITEM_ID — Inventory item identifier; foreign key to MTL_SYSTEM_ITEMS_B.
  • ORGANIZATION_ID — Organization identifier; foreign key to MTL_SYSTEM_ITEMS_B.
  • ITEM_NUMBER — The user-visible item number (VARCHAR2, length 40).
  • MASTER_ORGANIZATION_ID — Foreign key to MTL_SYSTEM_ITEMS_B, identifying the item's master organization.
  • GTIN — The Global Trade Item Number value (VARCHAR2, length 255).
  • DESCRIPTION — Descriptive text for the GTIN record (VARCHAR2, length 240).
  • ORG_INDEPENDENT_FLAG — Indicates whether the GTIN assignment is independent of organization.
  • UOM_CODE — The unit of measure code associated with the GTIN.
  • UNIT_OF_MEASURE — The descriptive unit of measure (VARCHAR2, length 25).
  • TRADE_ITEM_DESCRIPTOR — Trade item unit descriptor, e.g., each, case, pallet (VARCHAR2, length 35).
  • PUBLICATION_STATUS — Numeric publication status (NUMBER, length 15), indicating whether the GTIN record has been published in the applicable data pool or catalog context.

Common Use Cases and Queries

Typical usage centers on item data governance, barcode and catalog publication tracking, and integration feeds to external trading partner systems. Reporting teams frequently filter on PUBLICATION_STATUS to identify GTIN assignments that have not yet been published or that require review before syndication. A representative query returning all GTIN data for an item is:

SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, ITEM_NUMBER, MASTER_ORGANIZATION_ID, GTIN, DESCRIPTION, ORG_INDEPENDENT_FLAG, UOM_CODE, UNIT_OF_MEASURE, TRADE_ITEM_DESCRIPTOR, PUBLICATION_STATUS FROM APPS.EGO_ITEM_GTIN_V;

To isolate unpublished GTINs for a specific organization, the view supports predicates such as WHERE ORGANIZATION_ID = :org_id AND PUBLICATION_STATUS <> 1. Because the view already joins the cross-reference and item master structures, it eliminates the need for consumers to reconstruct those joins independently, making it well suited to concurrent program extracts and BI reporting layers within EBS 12.1.1 and 12.2.2.