Search Results get_pmt_tran_id

Overview

CN_PMT_TRANS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM API taxonomy as "OTHER." It belongs to the Oracle Incentive Compensation (OIC) module and governs the manipulation of payment transaction records stored in the CN_PAYMENT_TRANSACTIONS table and its related intersection tables. The package declares AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the definer.

The central artifact of the package specification is the pmt_trans_rec_type record type, a PL/SQL RECORD whose fields mirror the columns of CN_PAYMENT_TRANSACTIONS: payment_transaction_id, posting_batch_id, credited_salesrep_id, payee_salesrep_id, quota_id, pay_period_id, incentive_type_code, credit_type_id, payrun_id, amount, payment_amount, hold_flag, paid_flag, waive_flag, recoverable_flag, commission_header_id, commission_line_id, pay_element_type_id, srp_plan_assign_id, processed_date, processed_period_id, and quota_rule_id. Each field carries a default sentinel drawn from the CN_API and FND_API packages (for example, cn_api.g_miss_id, cn_api.g_miss_num, fnd_api.g_miss_char, and fnd_api.g_miss_date). This record type allows callers to pass a complete payment transaction row as a single parameter and to distinguish explicitly supplied values from unspecified ones via the sentinel defaults.

Key Procedures and Functions

The ETRM documentation for release 12.2.2 records three procedures and functions in the public interface of CN_PMT_TRANS_PKG:

• GET_PMT_TRAN_ID — Returns the identifier of a payment transaction. This is the routine most frequently referenced in support and customization searches, since it provides the lookup mechanism needed to resolve a payment transaction's primary key before downstream processing.
• INSERT_RECORD — Inserts a new payment transaction row into CN_PAYMENT_TRANSACTIONS using the pmt_trans_rec_type structure, applying appropriate defaults for fields left at sentinel value.
• DELETE_RECORD — Removes a payment transaction record and manages the associated dependent rows in the supporting tables.

These three routines form a minimal CRUD surface for the payment transaction entity. The metadata lists four documented program units total, of which three are named; the fourth is most likely a private or helper routine not exposed in the specification.

Tables Accessed

The package operates against a defined set of Incentive Compensation tables, accessed through APPS synonyms:

• CN_PAYMENT_TRANSACTIONS and CN_PAYMENT_TRANSACTIONS_S — the base and sequence tables holding payment transactions, the primary target of all DML in this package.
• CN_COMMISSION_LINES — links each payment transaction back to the commission line that generated it.
• CN_PAYRUNS_ALL — provides the payrun context in which transactions are grouped for payment.
• CN_QUOTAS_ALL and CN_QUOTA_PAY_ELEMENTS/CN_QUOTA_PAY_ELEMENTS_ALL — supply quota and pay element definitions referenced by the quota_id and pay_element_type_id columns.
• CN_SRP_PAYEE_ASSIGNS_ALL and CN_SRP_PERIODS — resolve the payee sales representative and the period in which the sale is recognized.
• CN_REPOSITORIES and CN_REPOSITORIES_ALL — repository metadata used to validate transaction content.
• DUAL — used for sequence and scalar lookups.

Usage Notes

CN_PMT_TRANS_PKG is an internal Incentive Compensation package rather than a public, documented open interface. It is referenced by five other packages, indicating that it sits in the middle of the OIC processing chain rather than at its edge. Typical invocation paths include the Incentive Compensation concurrent programs that populate payment transactions during a payrun, and Oracle Forms or OAF pages in the Incentive Compensation Administrator responsibility that display and maintain payment details. GET_PMT_TRAN_ID is commonly called from custom SQL and PL/SQL extensions that need to derive a payment transaction key for reconciliation, reporting, or integration with Oracle Payables and Oracle Payroll.

Because the package is not a published API, its signature may change between 12.1.1 and 12.2.2. Customizations that call these routines should be regression-tested after any OIC patch application, and callers must handle the g_miss sentinel convention correctly: passing a sentinel value signals "not supplied," while passing NULL carries explicit semantic meaning.