Search Results cn_comm_lines_api_s




Overview
Explore in AI Chat

Overview

CN_PROCESS_TAE_TRX_PUB is an Oracle EBS Application Object Library (APPS) public package body within the Channel Revenue Management (CN) module. Its primary business function is to process transaction records originating from Territory Assignment Engine (TAE) scoring results and apply the appropriate channel commission or revenue line adjustments to the relevant transaction records. The package acts as a processing bridge between the TAE winner determination process and the commission lines API, ensuring that territory-based sales representative assignments and associated credit allocations are correctly reflected on commission transaction lines.

The object is classified as a public (PUB) API, indicating it is intended for external invocation by forms, concurrent programs, or custom extensions rather than being restricted to internal-only use. Its dependency footprint confirms tight integration with the Channel Revenue Management commission lines API and the TAE schema, as well as with standard Oracle EBS utility packages such as FND_API, FND_MSG_PUB, FND_GLOBAL, and FND_PROFILE.

Key Procedures and Functions

  • PROCESS_TRX_RECORDS — The single documented procedure in this package. It drives the end-to-end processing of transaction records that have been scored or flagged by the Territory Assignment Engine. Conceptually, the procedure reads qualifying records from the TAE winner table (JTF_TAE_1001_SC_WINNERS), resolves the associated sales representatives and their role assignments, and orchestrates the corresponding updates to commission lines through the CN_COMM_LINES_API. It also handles standard API error and message handling conventions through FND_API and FND_MSG_PUB, and retrieves session context via FND_GLOBAL and FND_PROFILE.

No parameter lists are documented in the ETRM metadata; the procedure should be treated as an encapsulated processing entry point rather than a granular, per-record API.

Tables Accessed

  • CN_COMM_LINES_API — The commission lines API package that performs the actual creation, update, or computation of commission transaction line records. This is the principal write path for the package.
  • CN_COMM_LINES_API_S — The corresponding API specification package, referenced for signature resolution and standard API structuring.
  • JTF_TAE_1001_SC_WINNERS — The TAE scoring winners table, which stores the output of Territory Assignment Engine evaluations. This is the primary source of records to be processed.
  • FND_USER — Used for resolving user identity associated with the processing session, typically for audit or created-by attribution.
  • PLITBLM — A PL/SQL table type helper package used for in-memory collections, commonly for arrays of record identifiers or API message lists.

Additional dependencies include CN_SALESREPS, JTF_RS_ROLES_VL, and the FND_API/FND_MSG_PUB utility stack, indicating that sales representative and resource role lookups are performed as part of the processing logic.

Usage Notes

CN_PROCESS_TAE_TRX_PUB is typically invoked as part of the commission transaction processing flow in Channel Revenue Management, most often from concurrent programs that execute after TAE territory assignments have been staged. The package is not referenced by any other database object per the documented metadata, meaning it is a top-level entry point rather than a helper called by sibling packages.

Because it is a public API, custom code and extensions may call PROCESS_TRX_RECORDS directly, but the standard Oracle-provided concurrent program that manages TAE transaction processing is the recommended invocation path. Developers should be aware that the procedure relies on FND_GLOBAL initialization for the correct application and user context, and that error conditions are surfaced through the standard FND_MSG_PUB message stack rather than raised as unhandled exceptions. When troubleshooting, checking the FND message stack and the JTF_TAE_1001_SC_WINNERS staging rows provides the clearest diagnostic path. The behavior is consistent across Oracle EBS 12.1.1 and 12.2.2, though 12.2.2 online patching may regenerate the package body invalid during patching cycles; status should be verified through the ETRM dependency report in either release.