Search Results pay_payrun_conc




Overview

The APPS.CN_PMTSUB_PUB package is a public PL/SQL API belonging to the Oracle E-Business Suite Incentive Compensation (CN) module. Its name reflects its role in payment submission — the process by which calculated sales compensation is transmitted to Oracle Payables for disbursement. In Oracle Incentive Compensation, once transactions have been collected, credited, and calculated into payable earnings, those earnings must be forwarded to Payables so that payment can be issued to the participant. CN_PMTSUB_PUB encapsulates the logic that packages this payment information and drives the submission process, either interactively or through concurrent processing. It is classified as a PUB (public) API, indicating it is intended for supported, external invocation by other Oracle applications and by customer-written code. In both EBS 12.1.1 and 12.2.2 the package resides in the APPS schema, is reported with a VALID status, and depends on the core Incentive Compensation API package CN_API together with the standard SYS.STANDARD library.

Key Procedures and Functions

The ETRM metadata documents three callable program units within the package:

  • PAY — The primary procedure that initiates the payment submission activity. It performs the substantive work of preparing payable earnings and handing them off for payment processing, operating against the pay run context supplied by the caller.
  • PAY_PAYRUN_CONC — A concurrent-program entry point variant of the payment logic. Its name indicates it is designed to be launched as a background concurrent request rather than run interactively, allowing large payment submission workloads to execute in batch.
  • SUBMIT_REQUEST — A utility procedure that submits the payment submission as an Oracle concurrent request. It allows the calling process to schedule the payment job programmatically without requiring the user to navigate to the standard Submit Request form.

Consistent with the documented metadata, no parameter signatures are asserted here; the procedures should be invoked according to the published Oracle Incentive Compensation API documentation for the applicable EBS release.

Tables Accessed

The package references a single documented table through its APPS synonym:

  • CN_PAYRUNS — The pay run table that holds the header records for each incentive compensation payment run. CN_PMTSUB_PUB reads and updates pay run rows to track the submission of earnings to Payables, recording the state of the run as it progresses through the payment cycle. This table is the natural anchor for a payment submission API, since a pay run defines the set of calculated earnings being disbursed.

The metadata also records a dependency on the CN_API package. CN_API is the central Incentive Compensation API package and supplies much of the underlying business logic — such as payment and earnings processing routines — that CN_PMTSUB_PUB orchestrates when submitting payments.

Usage Notes

CN_PMTSUB_PUB is typically invoked in three ways. First, it is called from the Oracle Incentive Compensation payment submission forms, where the user selects a pay run and triggers payment submission interactively. Second, it is invoked by the PAY_PAYRUN_CONC entry point as a concurrent program, enabling scheduled or high-volume batch submissions. Third, custom code and other Oracle modules may call the public PAY and SUBMIT_REQUEST procedures directly, since the package is classified as a public API and is intended for supported extension. The ETRM documentation notes that CN_PMTSUB_PUB is not referenced by any other package, confirming that it sits at the top of the call stack as an entry-point API rather than as a shared utility. Because it writes to CN_PAYRUNS, callers should ensure the pay run has completed calculation before submission and should commit only after the procedure returns successfully.