Search Results update_pmt_transactions

Overview

APPS.CN_PMT_TRANS_PVT is the private application programming interface for payment transactions within the Oracle Incentive Compensation (formerly Oracle TeleSales / Compensation) module of Oracle E-Business Suite. The package encapsulates the core business logic governing how commission and bonus payment transactions are created, modified, deleted, held, released, and processed during a pay run. It exists as the transaction-level engine beneath the public compensation APIs, insulating calling code from the physical schema of CN_PAYMENT_TRANSACTIONS while enforcing validation rules, hold semantics, and revenue-class filtering.

The package header declares a constant identifying the package as CN_Pmt_Trans_PVT and a default credit type identifier of -1000. A prominent internal cursor, get_transactions_details, drives the read path, accepting a pay run identifier, sales representative, quota, revenue class, invoice number, order number, customer name, hold flag, and a bulk action verb. The cursor joins payment transactions to commission headers and to the customer/party model, restricting rows to incentive types of COMMISSION and BONUS and applying conditional predicates so that quota, revenue class, invoice, and order filters are only enforced when a value is supplied.

Key Procedures and Functions

• UPDATE_PMT_TRANSACTIONS — Modifies existing payment transaction rows, honoring the filter criteria and hold/release action semantics. This is the routine most commonly reached when a user searches for update_pmt_transactions, typically in the context of correcting amounts, quotas, or credited sales representatives on an existing pay run.
• CREATE_PMT_TRANSACTIONS — Inserts new payment transaction records, generating the identifiers and defaulting attributes required before a pay run processes the rows.
• DELETE_PMT_TRANSACTIONS — Removes payment transaction rows that are no longer required for a pay run.
• RELEASE_WKSHT_HOLD — Clears worksheet-level holds, allowing held transactions to proceed through commission calculation.
• PROCESS_PMT_TRANSACTIONS — Performs the processing flow over the selected transactions, applying the hold logic and revenue-class filters established by the cursor.
• HOLD_MULTIPLE_TRANS_CONC — A concurrent-program entry point that holds or releases multiple transactions in bulk.

The cursor enforces hold semantics using a DECODE on the supplied action: HOLD_ALL selects only unheld rows, RELEASE_ALL selects only held rows, and any other value leaves the hold flag unconstrained. Invoice and order comparisons use NVL-based predicates to treat nulls and wildcards consistently.

Tables Accessed

• CN_PAYMENT_TRANSACTIONS — The primary table read and written; holds transaction identifiers, amount, payment amount, quota, credited sales representative, incentive type, hold, waive, and recoverable flags.
• CN_COMMISSION_HEADERS — Supplies invoice number, order number, customer, and revenue class used for filtering and joining.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — Resolve customer name for search and display criteria.
• CN_PAYRUNS, CN_QUOTAS, CN_REVENUE_CLASSES — Provide pay run, quota, and revenue-class context.
• CN_PAYMENT_WORKSHEETS — Supports worksheet hold release.
• CN_POSTING_BATCHES, CN_REPOSITORIES, PAY_ELEMENT_TYPES_F — Support downstream posting and payroll element mapping.

Usage Notes

This is a PVT-classified package and is not intended for direct customer invocation; it is called by Oracle's own compensation forms and concurrent programs, and it is referenced by two other documented packages. Customizations should invoke the supported public compensation APIs rather than calling CN_PMT_TRANS_PVT procedures directly, since the private interface may change between releases. When troubleshooting a search for update_pmt_transactions, examine the calling form or concurrent request and confirm the action verb and filter values, as incorrect hold-action codes will silently reduce the affected row set.