Search Results check_adjusted

Overview

APPS.CN_SCA_TRX_PROC_PVT is a private PL/SQL package within the Oracle E-Business Suite Incentive Compensation (formerly Sales Compensation) module. It forms the transactional processing core of the Sales Compensation Accelerator (SCA) batch framework, orchestrating the creation, adjustment, and negation of commission transactions that flow from interface staging tables into the production commission repository. The package is classified as a PVT (private) API, indicating that it is not intended as a public integration point and is invoked internally by other Incentive Compensation components rather than by external callers.

In the 12.1.1 and 12.2.2 releases, the SCA batch architecture is the modern scheduling and parallel-processing infrastructure that replaced legacy compensation run mechanics. CN_SCA_TRX_PROC_PVT provides the worker-level logic that the batch runner dispatches, ensuring that transaction rows are validated, adjusted, and persisted consistently. Because it is a private package, its procedures are shielded from direct customer invocation, though its behavior surfaces indirectly whenever a compensation batch is executed.

Key Procedures and Functions

The ETRM documentation records 13 procedures and functions within this package. Each serves a distinct role in the batch transaction lifecycle:

• SCA_BATCH_RUNNER — the primary entry point driving the batch execution loop, coordinating the remaining worker procedures.
• CONC_SUBMIT / CONC_DISPATCH — handle concurrent program submission and dispatching for parallel batch processing.
• ASSIGN — associates transactions with the appropriate processing context, such as batch or repository assignment.
• CREATE_TRX — creates new commission transaction records from staged interface data.
• NEGATE_TRX — produces reversing transaction entries, typically for credit or adjustment rollbacks.
• CHECK_ADJUSTED / CHECK_API_ADJUSTED — validation routines that determine whether transactions have been adjusted, including checks via the public API pathway.
• POPULATE_RESULTS / POPULATE_DATA — load output results and source data into their respective processing structures.
• CALL_POPULATE_DATA / CALL_POPULATE_RESULTS — wrapper procedures that invoke the population routines, likely serializing calls across the batch.
• DEBUGMSG — diagnostic message logging for troubleshooting batch runs.

Parameter lists are intentionally omitted; the documented metadata names procedures without exposing signatures, and inventing them is inadvisable.

Tables Accessed

The package reads and writes a well-defined set of Incentive Compensation tables through APPS synonyms:

• CN_SCA_HEADERS_INTERFACE / CN_SCA_LINES_INTERFACE / CN_SCA_LINES_OUTPUT — the SCA staging and output tables consumed and produced during batch runs.
• CN_COMMISSION_HEADERS, CN_COMM_LINES_API, CN_COMM_LINES_API_S — the core commission transaction store, written via CREATE_TRX and NEGATE_TRX.
• CN_SCA_PROCESS_BATCHES / _S, CN_SCA_LOGICAL_BATCHES_S — batch tracking and logical partitioning tables.
• CN_REPOSITORIES — repository metadata governing where transactions are stored.
• FND_USER — used for user context and audit attribution.

Utility program units DBMS_LOCK, DBMS_SQL, and PLITBLM are also referenced, supporting concurrency control and dynamic SQL.

Usage Notes

CN_SCA_TRX_PROC_PVT is invoked indirectly through the Incentive Compensation batch submission process, most commonly by CN_SCA_WF_PKG, which references this package to drive transaction processing. Administrators trigger it by submitting the associated SCA concurrent programs from the Compensation workbench. It should not be called directly from custom code, because the PVT classification and internal dependencies (notably DBMS_LOCK usage) mean private behavior may change across patches. Customizations should instead rely on the public Incentive Compensation APIs.