Search Results op_cust_mst




Overview
Explore in AI Chat

Overview

The OP_CUST_MST table serves as the central customer master data repository within the Process Manufacturing Logistics (GML) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It is a foundational table designed to store comprehensive business entity information for customers, enabling core order management, shipping, invoicing, and accounts receivable processes. The table's structure facilitates the management of critical attributes such as financial terms, pricing rules, tax calculations, and shipping defaults, making it integral to the logistics and financial operations of a process manufacturing organization. As indicated by the metadata, it is defined within the GML product family, though its data is heavily referenced by other EBS modules.

Key Information Stored

The table's primary identifier is the system-generated CUST_ID. However, a unique composite key on CO_CODE (Company Code) and CUST_NO (Customer Number) enforces business-level uniqueness. Key columns, as inferred from the extensive foreign key relationships, store pointers to related master data. These include ADDR_ID and MAILADDR_ID for physical and mailing addresses, TAXCALC_CODE and TAXLOC_CODE for tax determination, and TERMS_CODE for payment terms. The table also links to pricing (CUSTPRICE_CLASS), customer classification (CUST_CLASS, CUSTTRADE_CLASS), sales representatives (SLSREP_CODE), freight methods (FRTBILL_MTHD), and currency (CUST_CURRENCY). Columns like FROM_WHSE and TO_WHSE suggest default shipping warehouse logic.

Common Use Cases and Queries

Primary use cases revolve around customer data maintenance, order processing validation, and integrated reporting. Common SQL queries include retrieving a customer's complete profile for order entry screens or validating tax and pricing rules during sales order creation. For instance, a query to fetch active customer details for a specific company might be: SELECT cust_no, cust_name, addr_id, terms_code, slsrep_code FROM op_cust_mst WHERE co_code = :p_co_code AND inactive_date IS NULL;. Reporting use cases often involve joining OP_CUST_MST with transactional tables like OP_ORD_HDR to analyze sales performance by customer class, territory, or sales representative, leveraging the foreign key links to classification tables.

Related Objects

OP_CUST_MST has a wide network of dependencies, as shown in the metadata. It is a parent table to numerous transactional and setup entities. Key child tables include OP_CUST_ASC (Customer Associations), OP_CUST_CON (Customer Contacts), OP_CUST_ITM (Customer Items), and OP_CHRG_ITM (Charge Items). It is referenced by allocation parameters (OP_ALOT_PRM) and form effectivity rules (FM_FORM_EFF). Crucially, it draws its descriptive codes from a suite of reference tables: SY_ADDR_MST for addresses, OP_TERM_MST for terms, TX_CALC_MST for tax, OP_SLSR_MST for sales reps, and OP_CUST_CLS for customer classification. This extensive relational model underscores its role as a hub for customer-centric data.