Search Results cn_process_tae_trx_pub




Overview
Explore in AI Chat

Overview

CN_PROCESS_TAE_TRX_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Trade Management (formerly Oracle Contracts) module, where the prefix CN designates objects in the Channel/Contracts schema family and the suffix PUB identifies the package as a public API intended for external invocation. The package provides the transactional processing engine for Trade Management Analytics Engine (TAE) records. The TAE framework evaluates trade promotion, deal, and accrual transactions against defined rule sets to determine eligibility, qualification, and settlement outcomes. CN_PROCESS_TAE_TRX_PUB serves as the orchestration point that accepts incoming transaction records, validates them through the FND_API error-handling convention, and persists the resulting analytics outcomes to the Trade Management data model. Its status is documented as VALID in the ETRM repository, confirming it is a supported, compiled object in the reference environment.

Key Procedures and Functions

The package exposes a single documented program unit:

  • PROCESS_TRX_RECORDS — The principal entry point for TAE transaction processing. It accepts a body of transaction records and drives them through the analytics engine, applying the applicable TAE rules and writing the evaluated results. The procedure follows the standard Oracle public API contract: callers pass an initialization flag and receive status, message, and reference cursors upon completion, allowing the calling program to interrogate success or failure without raising unhandled exceptions. The PUB classification indicates the procedure is designed for reuse by other Application modules and by customer extensions.

No additional procedures or functions are documented for this package in the ETRM metadata.

Tables Accessed

The documented table references, resolved through APPS synonyms, fall into three functional groups:

  • CN_COMM_LINES_API and CN_COMM_LINES_API_S — The Trade Management compensation and accrual line API entities and their sequence. These hold the transaction line records being evaluated by the analytics engine, and constitute the primary read/write target of PROCESS_TRX_RECORDS.
  • JTF_TAE_1001_SC_WINNERS — A TAE scoring and winner-determination table. It stores the outcomes of rule evaluation, identifying which competing rule, promotion, or scenario prevailed for a given transaction. This table is characteristic of the Trade Management Analytics Engine model and is central to determining qualification results.
  • FND_USER — The Oracle Applications user repository, referenced to resolve the identity and context of the user under whose authority the transaction is processed, supporting audit and security attribution.
  • PLITBLM — The PL/SQL integer table type used as a bind array for bulk operations, enabling the procedure to process record sets efficiently rather than row-by-row.

Usage Notes

CN_PROCESS_TAE_TRX_PUB is an internal integration API rather than an end-user-facing component. It is invoked indirectly through Trade Management transaction flows — for example, when collection or accrual processing submits transaction records for analytics evaluation — and directly by other public packages. The ETRM dependency report confirms that CN_POST_COLLECTION_TAE_PUB references this package, indicating that post-collection TAE processing calls PROCESS_TRX_RECORDS to evaluate and persist qualifying transactions. A self-referencing dependency is also recorded, consistent with recursive or multi-pass processing of transaction batches.

Customizations and extensions should treat the package strictly as a documented public API. Because the internal parameter list is not published in the metadata, integrators should obtain the formal signature from the Oracle Integration Repository or by describing the package in the target instance. Callers must supply the API initialization and check the returned status and message before committing, in line with Oracle's standard API error-handling pattern. Direct DML against the underlying TAE winner and line tables is not recommended, as it bypasses the validation and scoring logic encapsulated in this package.