Results for “pmt_amount_adj”

40 results




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

Overview

CN_PAYMENT_WORKSHEETS_ALL is a core transactional table in the Oracle EBS Incentive Compensation (CN) module. It stores the calculated payment worksheet records that determine how much compensation each sales representative is owed for a given pay run. Each row represents the earnings, adjustments, recoveries, and net payment amounts for one salesperson within a single payment run, spanning commission, bonus, draw, and guarantee components. The table is the primary staging ground between compensation calculation and the subledger posting process, meaning it carries the amounts that ultimately flow into Oracle Payables or the general ledger.

From a Data Vault modeling perspective, the FK structure suggests this table behaves as a link entity, joining a pay run (CN_PAYRUNS_ALL) to a sales representative and to credit types, quotas, and conversion factors. This classification is a heuristic suggestion rather than a documented architectural decision. The table is owned by the CN schema, is VALID in both 12.1.1 and 12.2.2, and exposes 66 documented columns. It supports multi-organization and multi-currency deployments through ORG_ID and the credit conversion columns.

Key Information Stored

The surrogate primary key, CN_PAYMENT_WORKSHEETS_PK, is composed of PAYRUN_ID and SALESREP_ID, so the natural business key is effectively the combination of pay run and salesperson. The most operationally significant columns include:

Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER support concurrency and traceability. SECURITY_GROUP_ID governs row-level access.

Common Use Cases and Queries

Typical scenarios include payment reconciliation, commission variance analysis, draw balance tracking, and pre-posting validation. A payroll analyst might reconcile calculated versus paid amounts for a pay run:

  • SELECT PAYRUN_ID, SALESREP_ID, PMT_AMOUNT_CALC, PMT_AMOUNT_ADJ, HELD_AMOUNT FROM CN_PAYMENT_WORKSHEETS_ALL WHERE PAYRUN_ID = :p_run_id;
  • Identifying worksheets pending posting: SELECT * FROM CN_PAYMENT_WORKSHEETS_ALL WHERE POSTING_STATUS <> 'POSTED';
  • Analyzing recoverable draws by salesperson: SELECT SALESREP_ID, DRAW_RECOVERABLE_BEGIN, DRAW_PAID, RECOVERY_METHOD FROM CN_PAYMENT_WORKSHEETS_ALL WHERE DRAW_RECOVERABLE_BEGIN > 0;
  • Commission trend reporting across pay runs joined to CN_PAYRUNS_ALL for period context.

Because the table is joined frequently to pay runs and credit types, standard reporting patterns filter by ORG_ID and PAYRUN_ID to keep result sets manageable.

Related Objects

The most significant related objects, based on documented foreign keys, include:

These relationships confirm the table's role as a central link between pay runs, salespeople, and compensation configuration, and they should be used for joins when building custom reports or extensions.