Search Results op_cust_itm




Overview
Explore in AI Chat

Overview

The OP_CUST_ITM table is a core data object within the Oracle E-Business Suite, specifically in the Process Manufacturing Logistics (GML) product family. It serves as the central repository for customer-specific item information, establishing a critical link between a customer, an item, and a specific warehouse. This table is essential for managing complex supply chain and order fulfillment scenarios where item characteristics, packaging, or handling instructions may vary by customer or by the distribution location. Its role is to define and maintain these unique customer-item relationships, enabling precise inventory control, accurate order processing, and tailored logistics execution within the EBS environment.

Key Information Stored

The table's structure is defined by its primary and unique keys, which reveal the core data entities it connects. The primary key, CUSTITEM_ID, provides a unique system identifier for each customer-item relationship record. A significant unique key constraint (OP_CUST_ITM_U1) enforces business logic by ensuring that the combination of CUST_ID (customer), ITEM_ID (item), WHSE_CODE (warehouse), and SALESPKG_ID (sales package) is unique. This prevents duplicate configurations. The key columns, therefore, are CUST_ID, ITEM_ID, WHSE_CODE, and SALESPKG_ID. While the provided metadata does not list descriptive or attribute columns, the table's foreign key relationships confirm it stores the identifiers necessary to join to master data for customers (OP_CUST_MST), items (IC_ITEM_MST and IC_ITEM_MST_B), warehouses (IC_WHSE_MST), and sales packages (OP_PKGD_ITM).

Common Use Cases and Queries

This table is pivotal in scenarios requiring customer-specific inventory or shipping data. A common use case is validating an order line: before booking a sales order, the system can query OP_CUST_ITM to confirm if the ordered item is valid for the specific customer and ship-from warehouse. Another key use is in pick slip and shipping document generation, where the associated SALESPKG_ID can determine correct packaging instructions. A typical reporting query would join this table to its referenced master tables to produce a list of all items configured for a particular customer.

SELECT c.customer_name, i.item_number, w.whse_code, p.pkg_description
FROM gml.op_cust_itm ci,
     op_cust_mst c,
     ic_item_mst_b i,
     ic_whse_mst w,
     op_pkgd_itm p
WHERE ci.cust_id = c.cust_id
  AND ci.item_id = i.item_id
  AND ci.whse_code = w.whse_code
  AND ci.salespkg_id = p.salespkg_id(+)
  AND c.cust_id = :p_customer_id;

Related Objects

OP_CUST_ITM is highly integrated within the GML and Inventory modules through documented foreign key relationships. It references the following key master and transactional tables:

  • OP_CUST_MST via CUST_ID: Joins to the customer master table.
  • IC_ITEM_MST_B and IC_ITEM_MST via ITEM_ID: Joins to the item master tables for item definitions.
  • IC_WHSE_MST via WHSE_CODE: Joins to the warehouse master table.
  • OP_PKGD_ITM via SALESPKG_ID: Joins to the sales package items table for packaging specifications.

These relationships ensure data integrity and enable comprehensive queries that combine customer-item rules with master data attributes.