Search Results op_slsr_mst




Overview
Explore in AI Chat

Overview

The OP_SLSR_MST table is the central master data repository for sales representatives within the Oracle E-Business Suite (EBS) Process Manufacturing Logistics (GML) module. It functions as a core reference table, establishing and maintaining the unique identity and attributes of each salesperson or agent in the system. Its primary role is to provide a consistent, validated source of sales representative information that is linked to critical transactional and master data across the order management, customer management, and commission calculation processes. The table's integrity is enforced by its primary key and numerous foreign key relationships, ensuring data consistency throughout the logistics and sales operations.

Key Information Stored

While the full column list is not detailed in the provided metadata, the foreign key relationships and primary key indicate the core data elements stored. The central column is SLSREP_CODE, which serves as the unique identifier (primary key) for each sales representative record. Other significant fields, inferred from the foreign keys, include COMMISSION_CODE (linking to the OP_COMMISSION table for compensation rules), SLSREP_CLASS (for categorization via OP_SLSR_CLS), TEXT_CODE (for descriptive notes via OP_TEXT_HDR), and ADDR_ID (for address information in SY_ADDR_MST). The CO_CODE (company code) column links the representative to organizational structures in SY_ORGN_MST, anchoring them within the enterprise hierarchy.

Common Use Cases and Queries

This table is essential for operational reporting, transaction processing, and master data maintenance. Common use cases include populating sales representative lists on sales orders (OP_ORDR_HDR/DTL), proposals (OP_PRSL_HDR/DTL), and customer accounts (OP_CUST_MST). It is also critical for calculating commissions via the OP_COMM_CDS table. A typical query might retrieve active representatives for a specific company code or associate representative details with their sales transactions. For example:

  • SELECT slsrep_code, [name_column], co_code FROM gml.op_slsr_mst WHERE co_code = :p_co_code;
  • Joining with order headers to analyze sales performance: SELECT o.slsrep_code, s.[name_column], SUM(o.order_total) FROM op_ordr_hdr o, op_slsr_mst s WHERE o.slsrep_code = s.slsrep_code GROUP BY o.slsrep_code, s.[name_column];

Related Objects

As evidenced by the extensive foreign key metadata, OP_SLSR_MST is a foundational table with wide-ranging dependencies. Key related objects include transactional tables like OP_ORDR_HDR, OP_ORDR_DTL, OP_PRSL_HDR, and OP_PRSL_DTL, which store the sales representative assigned to each document. Master data tables OP_CUST_MST and OP_CUST_MST_OPM reference it to define the primary representative for a customer. Commission-related objects OP_COMMISSION and OP_COMM_CDS depend on it. It also integrates with shared EBS entities for address (SY_ADDR_MST), organization (SY_ORGN_MST), and descriptive text (OP_TEXT_HDR).