Results for “experimental_ind”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The GMI.GMI_ITEMS_XML_INTERFACE table is a staging and integration interface object within the Oracle E-Business Suite Process Manufacturing (OPM) Inventory module. Its documented purpose is to hold XML Gateway API requests used to add an Item to Oracle Process Manufacturing. In the EBS 12.1.1 and 12.2.2 architectures, this table functions as the inbound persistence layer for the XML Gateway listener: external systems publish item master payloads, the XML Gateway parses and inserts records into this table, and the OPM item import concurrent program subsequently validates, defaults, and promotes each row into the production item master tables.

The table is classified as VALID and resides in the GMI schema, which is the core schema for Process Manufacturing Inventory and Costing. With 99 documented columns, the structure closely mirrors the OPM IC_ITEM_MST item definition, plus audit columns and interface control columns. From a heuristic Data Vault modeling perspective, the mined FK structure suggests this object is best treated as a satellite — a standalone, descriptive, and transient staging table — rather than a hub or link. No dependent child tables were identified, reinforcing the standalone classification.

Key Information Stored

The surrogate primary key is ITEM_INTERFACE_ID, enforced by the unique index GMI_ITEMS_XML_INTERFACE_PK. Beyond the surrogate key, the most business-significant columns include:

• EXT_ITEM_ID — external item identifier supplied by the source system, used for cross-reference matching.
• ITEM_NUMBER and ITEM_DESC1/ITEM_DESC2 — the item code and descriptive text that become the OPM item identifiers.
• ITEM_UOM, ITEM_UOM2, and DUALUM_IND — primary/secondary units of measure and the dual-UOM indicator.
• LEVEL_CODE, LOT_CTL, SUBLOT_CTL, LOCT_CTL — inventory control attributes governing lot, sublot, and location tracking.
• INV_TYPE, GL_CLASS, INV_CLASS, COST_MTHD_CODE — item classification and costing method used for accounting and inventory valuation.
• PKG_ID — foreign key to IC_PKGS_MST, linking the item to its packaging definition.
• PROCESSED_IND and ERROR_TEXT — control columns that flag whether the interface row was successfully imported and capture any validation errors.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• USER_NAME and ATTRIBUTE_CATEGORY plus ATTRIBUTE1–ATTRIBUTE30 — the DFF/descriptive flexfield extension region.

Common Use Cases and Queries

Typical usages center on interface monitoring and troubleshooting. A common pattern is identifying unprocessed or failed item requests:

• Query rows stalled in the interface: SELECT ITEM_INTERFACE_ID, ITEM_NUMBER, EXT_ITEM_ID, ERROR_TEXT FROM GMI.GMI_ITEMS_XML_INTERFACE WHERE PROCESSED_IND = 'N';
• Reconciliation against the production master using EXT_ITEM_ID or ITEM_NUMBER to confirm the item was created.
• Error trending and root-cause analysis by grouping on ERROR_TEXT to surface recurring XML payload defects.
• Audit reporting on who submitted items and when, using CREATED_BY, CREATION_DATE, and USER_NAME.
• Purge/archival routines based on PROCESSED_IND = 'Y' and aging by CREATION_DATE.

Related Objects

The documented foreign key relationships and integration dependencies include:

• GMI.IC_PKGS_MST — referenced via GMI_ITEMS_XML_INTERFACE.PKG_ID.
• GMI.IC_ITEM_MST — the production OPM item master targeted by the import program.
• GMI.IC_ITEM_XREF — item cross-references, matched on EXT_ITEM_ID.
• GMI.IC_LOCT_MST — location master, referenced by location control attributes.
• XML Gateway runtime tables (ECX_*) that feed this interface during inbound processing.
• The OPM Item Import concurrent program and its associated PL/SQL validation packages, which read and update PROCESSED_IND and ERROR_TEXT.