Results for “op_gnrc_itm”

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

Overview

OP_GNRC_ITM is a table in the GML (Process Manufacturing Logistics) schema of Oracle E-Business Suite, holding customer and generic (alternate) names for items. In process manufacturing environments, the same physical or formulated product is frequently sold or referenced under different names by different customers, vendors, or internal groups. OP_GNRC_ITM centralizes these aliases, allowing a single master item to be represented under multiple generic identifiers so that order entry, pricing, and procurement processes can resolve the correct item without duplicating the item master record itself.

From a Data Vault modeling perspective, the FK structure suggests this object behaves as a satellite-leaning entity. It is neither a pure hub nor a pure link: it carries descriptive attributes (names, descriptions, text references, flags) while also anchoring foreign keys to several master and transaction tables. Its unique key (GENERIC_ID) suggests the generic name record acts as a natural business entity, while the composite primary key ties each variant to a specific item, customer, and vendor combination.

Key Information Stored

OP_GNRC_ITM contains 17 documented columns. The most significant are:

• GENERIC_ID — the surrogate primary key and sole unique business-key candidate (index OP_GNRC_ITM_PK). This is the value referenced by downstream transaction tables.
• GENERIC_ITEM — the alternate or customer-facing item name; forms part of the composite primary key OP_GNRC_ITMI1.
• GENERIC_DESC — descriptive text for the generic name.
• ITEM_ID — foreign key to IC_ITEM_MST / IC_ITEM_MST_B, the true master item identity.
• CUST_ID — customer for whom the alternate name applies (FK to OP_CUST_MST).
• VENDOR_ID — vendor associated with the alternate name (FK to PO_VEND_MST).
• TEXT_CODE — link to OP_TEXT_HDR for long description or note storage.
• USE_ONORDER — flag controlling whether the generic name is available during order entry.
• DELETE_MARK — soft-delete indicator maintained by the OPM data model.
• TRANS_CNT — transaction counter used for concurrency control in Process Manufacturing.
• OPM_CUST_ID and CO_CODE — legacy/company identifiers carried for compatibility.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

The table is typically queried when resolving an item entered by a customer or vendor into its master item identity. A typical lookup joins the generic record to IC_ITEM_MST:

SELECT g.generic_item, g.generic_desc, i.segment1
FROM   gml.op_gnrc_itm g,
       gml.ic_item_mst  i
WHERE  g.item_id = i.item_id
AND    g.cust_id = :cust_id
AND    NVL(g.delete_mark,0) = 0;

Reporting uses include listing all alternate names available for a given customer, identifying items with multiple active generic names for data-cleansing initiatives, and validating that every order line's generic_id resolves to an active, non-deleted generic record. The transaction tables OP_ORDR_DTL and PO_ORDR_DTL reference GENERIC_ID, so reconciliation queries frequently join those sources to OP_GNRC_ITM to explain how a customer-entered name became a firm order.

Related Objects

• IC_ITEM_MST / IC_ITEM_MST_B — master item definitions; joined via ITEM_ID.
• OP_CUST_MST — customer master; joined via CUST_ID.
• PO_VEND_MST — vendor master; joined via VENDOR_ID.
• OP_TEXT_HDR — text/notes header; joined via TEXT_CODE.
• OP_ORDR_DTL — order lines; references GENERIC_ID.
• OP_PRSL_DTL — proposal/price list lines; references GENERIC_ID.
• PO_ORDR_DTL — purchase order lines; references GENERIC_ID.
• PO_BPOS_DTL — blanket purchase agreement lines; references GENERIC_ID.