Search Results op_commission




Overview
Explore in AI Chat

Overview

The OP_COMMISSION table is a core master data table within the Oracle E-Business Suite (EBS) Process Manufacturing Logistics (GML) module. It functions as the header table for defining and storing commission codes. These codes are essential for configuring and managing commission structures, which are critical for calculating and tracking salesperson or agent compensation based on transactional activity. As a foundational reference table, OP_COMMISSION ensures data integrity and consistency by centralizing commission definitions that are subsequently referenced across numerous transactional and master tables in the order management and sales processing cycles.

Key Information Stored

While the provided ETRM excerpt does not list specific columns, the table's role as a header and its primary key definition indicate its core structure. The central column is COMMISSION_CODE, which serves as the table's primary key (OP_COMMISSION_PK). This unique identifier is the critical piece of data stored. The table would logically contain additional descriptive and control columns to fully define a commission code, such as a name, description, effective dates (start and end), status, and potentially links to calculation formulas or rate tables. The integrity of the COMMISSION_CODE is enforced by its use as a primary key and is propagated as a foreign key into dependent tables.

Common Use Cases and Queries

The primary use case for the OP_COMMISSION table is to serve as a validated source for commission code assignment during sales order entry, quotation creation, and customer or salesperson setup. Common operational and reporting queries involve joining this table to its numerous child tables to generate commission-related analyses. For instance, to list all active sales orders with their associated commission code descriptions, one would join OP_ORDR_HDR to OP_COMMISSION. A typical SQL pattern for validating or reporting on commission code usage is:

  • SELECT c.COMMISSION_CODE, c.DESCRIPTION, COUNT(o.ORDER_NUMBER) AS ORDER_COUNT FROM GML.OP_COMMISSION c, GML.OP_ORDR_HDR o WHERE c.COMMISSION_CODE = o.COMMISSION_CODE GROUP BY c.COMMISSION_CODE, c.DESCRIPTION;

Data maintenance tasks, such as querying for codes not referenced in transactions before inactivation, also rely heavily on this table.

Related Objects

As evidenced by the foreign key relationships, OP_COMMISSION is a pivotal reference table with extensive dependencies. Key related transactional tables include OP_ORDR_HDR (sales order headers) and OP_PRSL_HDR (proposal/quote headers), along with their detail lines (OP_ORDR_DTL, OP_PRSL_DTL). Master data tables that reference commission codes include OP_CUST_MST and OP_CUST_MST_OPM (customer masters), OP_SLSR_MST (salesperson master), and OP_COMM_CDS, which is likely a child table containing further details or schedules for the commission code header. These relationships underscore that OP_COMMISSION is a central node in the GML data model for sales compensation.