Search Results op_gnrc_itm




Overview
Explore in AI Chat

Overview

The OP_GNRC_ITM table is a core data object within the Process Manufacturing Logistics (GML) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as a central repository for managing alternate names and identifiers for inventory items. Its primary function is to facilitate business processes where an item is known by different names or codes to different trading partners. Specifically, it maps a standard internal item (ITEM_ID) to a customer-specific name (CUST_ID, GENERIC_ITEM) or a vendor-specific name (VENDOR_ID, GENERIC_ITEM). This mapping is critical for accurate order processing, procurement, and logistics, ensuring that external partner references are correctly linked to the internal item master, thereby reducing errors in purchase orders, sales orders, and quotations.

Key Information Stored

The table's structure is designed to support its role in cross-referencing item identifiers. Its primary key (OP_GNRC_ITMI1) is a composite of four columns, highlighting the unique combination required for each record: GENERIC_ITEM (the alternate name/code), CUST_ID (the customer), VENDOR_ID (the vendor), and ITEM_ID (the internal item). A separate unique primary key constraint (OP_GNRC_ITM_PK) is also defined on the GENERIC_ID column, which is the system-generated unique identifier for each mapping record. Key data columns include ITEM_ID, which foreign keys to IC_ITEM_MST_B (the item master), and CUST_ID and VENDOR_ID, which foreign key to OP_CUST_MST and PO_VEND_MST respectively. The TEXT_CODE column links to OP_TEXT_HDR for storing descriptive notes.

Common Use Cases and Queries

A primary use case is translating a customer's provided item code into the internal item identifier during sales order entry. For example, when entering an order line, the system can query OP_GNRC_ITM using the customer's ID and the code they supplied to find the correct ITEM_ID. Conversely, when generating a purchase order for a vendor, the system can retrieve the vendor-specific item code to print on the PO document. Common reporting needs include generating a cross-reference list for a specific trading partner. A sample query to find all customer-specific names for an internal item '12345' would be:
SELECT generic_item, cust_id FROM gml.op_gnrc_itm WHERE item_id = 12345 AND cust_id IS NOT NULL;
Another critical pattern is validating order lines by joining to this table to ensure the generic ID on a sales order detail (OP_ORDR_DTL.GENERIC_ID) matches a valid record.

Related Objects

OP_GNRC_ITM has extensive relationships with transactional and master tables across EBS. It is a parent table to key detail lines in Order Management and Purchasing, as evidenced by foreign key references from OP_ORDR_DTL (sales orders), OP_PRSL_DTL (quotations), PO_ORDR_DTL (purchase orders), and PO_BPOS_DTL (blanket agreements). These dependencies underscore its operational importance. For master data, it references IC_ITEM_MST_B for the internal item definition, OP_CUST_MST for the customer, and PO_VEND_MST for the supplier. The relationship with OP_TEXT_HDR allows for attaching additional descriptive text to a specific item cross-reference.