Search Results icpurch_class

Overview

The IC_PRCH_CLS table is a master data table within the Oracle Process Manufacturing (OPM) Inventory module (GMI) of Oracle E-Business Suite (EBS). It serves as the central repository for defining and storing purchase class codes, which are critical classification attributes used to categorize and manage purchased items throughout the OPM system. These classifications enable standardized procurement processes, reporting, and inventory control for process manufacturing items. While the table is a core component of the GMI data model, its metadata indicates it is "Not implemented in this database," a status that may reflect a specific instance configuration or a legacy note. Its primary key is enforced by the IC_PRCH_CLS_PK constraint on the ICPURCH_CLASS column.

Key Information Stored

The primary data element stored in this table is the purchase class code itself. Based on standard OPM table design and the provided foreign key relationships, the table likely contains descriptive and control columns typical of a setup table. The definitive column is ICPURCH_CLASS, which is the unique identifier for a purchase class. While the full column list is not provided in the excerpt, such tables commonly include fields for a description (e.g., PURCH_CLASS_DESC), an enabled flag, who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY), and potentially a TEXT_CODE column linking to the IC_TEXT_HDR table for storing extensive descriptive text, as indicated by the foreign key relationship.

Common Use Cases and Queries

The primary use case for the IC_PRCH_CLS table is to provide a validated list of purchase classes for assignment to items and procurement documents. A fundamental query retrieves all active purchase classes for use in a list of values (LOV) during item or purchase order setup. For example:

SELECT icpurch_class, purch_class_desc
FROM ic_prch_cls
WHERE disable_flag = 'N'
ORDER BY 1;

Another common reporting scenario involves joining the table to item master or purchase order data to analyze procurement by class. For instance, to list all items associated with a specific purchase class, one would query:

SELECT i.item_no, i.item_desc, p.purch_class_desc
FROM ic_item_mst i, ic_prch_cls p
WHERE i.purch_class = p.icpurch_class
AND p.icpurch_class = '&PURCH_CLASS_CODE';

Related Objects

The IC_PRCH_CLS table has integral relationships with several key transactional and master tables across OPM and Purchasing, as documented by its foreign keys. The PO_BPOS_HDR and PO_BPOS_DTL tables (Blanket Purchase Agreements), along with PO_ORDR_HDR and PO_ORDR_DTL (Standard Purchase Orders), reference this table to classify procurement documents. The IC_ITEM_MST (Item Master) table references it to classify purchased items at the master data level. Furthermore, the relationship with IC_TEXT_HDR allows for the storage of extended descriptive text for each purchase class code. These relationships underscore the table's role as a shared reference point for procurement classification in an integrated OPM environment.