Results for “op_comm_cds”

31 results




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

Overview

OP_COMM_CDS is a transactional detail table owned by the GML schema (Process Manufacturing Logistics) in Oracle EBS 12.1.1 and 12.2.2. It stores commission code detail records that link a specific commission code, a sales representative, and a commission event into a single meaningful combination. In practical terms, the table answers the question of how a given sales representative participates in (or is credited under) a given commission arrangement at a defined event point.

From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying OP_COMM_CDS as a link table. It primarily resolves many-to-many relationships among three business entities — commissions (OP_COMMISSION), sales representatives (OP_SLSR_MST), and commission events — rather than serving as a descriptive hub. This classification is a heuristic suggestion derived from the FK topology and should be validated against the broader GML commission model during design.

Key Information Stored

The table documents 13 physical columns and carries the unique index OP_COMM_CDS_PK, defined on the composite key (COMMISSION_CODE, SLSREP_CODE, COMMISSION_EVENT). Because the unique index is built on natural business columns rather than a single surrogate, this composite key is the business-key candidate for the row.

  • COMMISSION_CODE — Identifies the commission record; foreign key to OP_COMMISSION. Part of the business-key candidate.
  • SLSREP_CODE — Identifies the sales representative; foreign key to OP_SLSR_MST. Part of the business-key candidate.
  • COMMISSION_EVENT — The event at which the commission applies; part of the business-key candidate.
  • EVENT_ALLOC — Allocation value associated with the commission event for this representative combination.
  • COMMENTS — Free-form descriptive text for the detail line.
  • TEXT_CODE — Foreign key to OP_TEXT_HDR, linking standardized text maintained in the text header repository.
  • TRANS_CNT — Transaction counter used for concurrency/row versioning.
  • CREATION_DATE, CREATED_BY — Audit columns recording row creation.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit columns recording the most recent change.
  • DELETE_MARK — Soft-delete / logical deletion indicator (typically 0 or 1).

Common Use Cases and Queries

Typical reporting scenarios include listing all sales representatives associated with a commission code, auditing allocation across events, and driving commission calculation or reconciliation reports in Process Manufacturing Logistics.

  • Retrieve all detail rows for a commission code:
    SELECT * FROM gml.op_comm_cds WHERE commission_code = :p_code;
  • Join to the commission master to enrich descriptive data:
    SELECT a.commission_code, a.slsrep_code, a.commission_event, a.event_alloc FROM gml.op_comm_cds a JOIN gml.op_commission b ON a.commission_code = b.commission_code WHERE a.delete_mark = 0;
  • Resolve sales representative details:
    SELECT a.slsrep_code, c.slsrep_name FROM gml.op_comm_cds a JOIN gml.op_slsr_mst c ON a.slsrep_code = c.slsrep_code;
  • Report allocations by event for a given representative, aggregating EVENT_ALLOC across commission codes.

Queries should generally filter on DELETE_MARK = 0 where soft-deleted rows must be excluded, and use the composite key columns for indexed access.

Related Objects

The documented foreign keys define the principal relationships for OP_COMM_CDS:

  • OP_COMMISSION — joined on COMMISSION_CODE; the commission master referenced by each detail row.
  • OP_SLSR_MST — joined on SLSREP_CODE; the sales representative master.
  • OP_TEXT_HDR — joined on TEXT_CODE; standardized text header records.

Additional dependent objects within the GML commission model (such as commission calculation or allocation programs that read OP_COMM_CDS by commission code) typically reference this table through the COMMISSION_CODE relationship. When building custom reports or interfaces, these three master tables form the core join graph anchored on OP_COMM_CDS_PK.