Results for “commission_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OP_COMMISSION is a commission code header table owned by the GML schema (Process Manufacturing Logistics) within Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the master list of commission codes used throughout the Oracle Process Manufacturing (OPM) order-to-cash flow. Each row represents a distinct commission code that can be attached to customers, sales representatives, orders, order lines, proposals, and proposal lines. The table functions as a foundational reference object: transactional and master-data tables across the OPM sales cycle carry a COMMISSION_CODE foreign key column that resolves back to this header.

Under the heuristic Data Vault classification mined from the foreign key structure, OP_COMMISSION is classified as hub-leaning. In dimensional or Data Vault modeling terms, this suggests treatment as a hub entity — a relatively narrow, stable set of business keys (commission codes) around which links and satellites describing assignments, rates, and history would be modeled. The table itself is a low-volatility reference list rather than a transactional fact or a high-churn detail table.

Key Information Stored

The documented physical schema for OP_COMMISSION in ETRM 12.2.2 contains six columns. The most significant are:

• COMMISSION_CODE — The business identifier for the commission code header. This column is both the primary key column of OP_COMMISSION_PK and the sole unique index candidate, making it the single business-key candidate for the table.
• CREATED_BY, CREATION_DATE — Standard Oracle EBS WHO columns recording the user and timestamp of initial row insertion.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing the most recent modification user, date, and login session.

Note that in this documented schema the primary key OP_COMMISSION_PK is defined over COMMISSION_CODE, so the surrogate and business key coincide; no separate numeric surrogate identifier is documented. The table carries no additional descriptive attributes in the ETRM metadata beyond the WHO audit columns, meaning descriptive detail about a commission code is likely held in related tables such as OP_COMM_CDS.

Common Use Cases and Queries

The primary practical use of OP_COMMISSION is as the validation and lookup source for commission code values. Typical scenarios include resolving the commission code attached to a sales order, verifying that a code referenced by a customer or sales representative is valid, and populating LOVs and reports.

• Validating a code: SELECT COMMISSION_CODE FROM GML.OP_COMMISSION WHERE COMMISSION_CODE = :code;
• Resolving an order's commission context by joining OP_ORDR_HDR to OP_COMMISSION on COMMISSION_CODE.
• Auditing recent maintenance via LAST_UPDATED_BY / LAST_UPDATE_DATE to identify who introduced or changed commission codes.
• Reporting all sales representatives associated with a given commission code through OP_SLSR_MST.

Because the table is small and static in nature, queries are generally inexpensive lookups or joins rather than large scans.

Related Objects

Eight tables reference OP_COMMISSION through the COMMISSION_CODE foreign key, all pointing to the OP_COMMISSION.COMMISSION_CODE column:

• OP_COMM_CDS — likely holds the descriptive detail lines for each commission code.
• OP_CUST_MST and OP_CUST_MST_OPM — customer master tables assigning a default commission code to customers.
• OP_ORDR_HDR and OP_ORDR_DTL — sales order header and detail lines carrying the applicable commission code.
• OP_PRSL_HDR and OP_PRSL_DTL — proposal header and detail lines referencing commission codes.
• OP_SLSR_MST — sales representative master linking representatives to commission codes.

These relationships confirm OP_COMMISSION's role as a hub shared by master-data and transactional objects across the OPM order-to-cash and proposal cycles.