Search Results op_cust_mst_opm_uc1




Overview
Explore in AI Chat

Overview

The OP_CUST_MST_OPM table is the central customer master data repository within the Process Manufacturing Logistics (GML) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the foundational table for storing and managing all customer-specific information required for order processing, shipping, invoicing, and financial transactions in a process manufacturing environment. Its design supports complex operational needs, including multi-organization structures, trade classifications, and financial terms, which are critical for industries like chemicals, food and beverage, and pharmaceuticals. The table's integrity is maintained through a network of foreign key relationships with other master data tables, ensuring consistent and validated data across the logistics and financial streams.

Key Information Stored

The table's structure is defined by its primary and unique keys, which enforce critical business rules. The primary key is the system-generated CUST_ID, while a unique constraint (OP_CUST_MST_OPM_UC1) ensures that the combination of Company Code (CO_CODE) and Customer Number (CUST_NO) is unique within an enterprise. Key columns and their purposes include identifiers like CUST_NO and ADDR_ID for physical and mailing addresses; financial controls such as CUST_CURRENCY, TERMS_CODE, and TAXCALC_CODE; and operational parameters like FROM_WHSE and TO_WHSE for default shipping logistics. Classification columns (CUST_CLASS, CUSTTRADE_CLASS, CUSTPRICE_CLASS) enable segment-specific business policies, and fields for sales representatives (SLSREP_CODE), freight methods (FRTBILL_MTHD), and FOB codes (FOB_CODE) complete the comprehensive customer profile.

Common Use Cases and Queries

This table is integral to daily operations and reporting. Common use cases include the creation and maintenance of customer records through the GML application interface, the automatic population of customer data on sales orders and invoices, and the generation of customer master lists for compliance and analysis. Typical reporting queries involve joining with related tables to produce enriched customer lists. A fundamental SQL pattern retrieves active customers with their key attributes:

  • SELECT cust_no, cust_name, addr_id, terms_code, slsrep_code FROM gml.op_cust_mst_opm WHERE co_code = :p_org AND delete_mark = 0;

Another common query joins with the address (SY_ADDR_MST) and currency (GL_CURR_MST) tables to create a detailed customer master report for financial or sales analysis, often filtered by customer class or sales territory.

Related Objects

As indicated by its extensive foreign key constraints, OP_CUST_MST_OPM is a hub table with dependencies across multiple EBS modules. Key related objects include:

  • SY_ORGN_MST_B: Validates the Company Code (CO_CODE).
  • SY_ADDR_MST: Provides physical (ADDR_ID) and mailing (MAILADDR_ID) address details.
  • IC_WHSE_MST: Validates default shipping and receiving warehouses (FROM_WHSE, TO_WHSE).
  • Financial & Terms Tables: GL_CURR_MST (currency), OP_TERM_MST (payment terms), OP_COMMISSION, and OP_LKBX_MST (lockbox).
  • Classification Tables: OP_CUST_CLS, OP_CTRD_CLS, OP_CPRC_CLS, and OP_CGLD_CLS for customer categorization.
  • Transaction Tables: While not listed in the provided metadata, this master table is the source for customer information in GML transaction tables like sales orders and shipments.