Search Results pa_txn_accums




Overview
Explore in AI Chat

Overview

PA_TXN_ACCUMS is the Oracle Projects transaction accumulation engine responsible for building and maintaining the summarized transaction records that drive project cost, revenue, and commitment reporting within Oracle EBS 12.1.1 and 12.2.2. Transaction accumulation collapses detailed expenditure, revenue, and commitment activity into period-based accumulations stored for reporting and downstream processing. The package determines, for each project, which accumulation categories are enabled — raw cost, burdened cost, quantity, labor hours, billable variants of each, revenue, and commitment (CMT) indicators — and then populates or refreshes the corresponding accumulation rows. Its central role is to keep accumulated transaction data synchronized with the underlying distributions whenever transactions are entered, adjusted, or reprocessed. The header reference (PATXNACS.pls 120.2) indicates a mature, stable code line, and the inclusion of commitment-specific variables and procedures confirms that commitment accumulation is an integral part of the design. The package is classified as OTHER in the ETRM metadata, meaning it is an internal engine rather than a formally published public API, though it is invoked by three other packages.

Key Procedures and Functions

The package exposes twenty-four documented program units. Two utility functions, INITIALIZE and CMT_LINE_ID, perform setup and commitment line identifier derivation respectively. GET_ACCUM_CONFIGURATIONS reads the accumulation configuration applicable to a given project and populates the package-level flags that govern subsequent processing. UPDATE_RESOURCE_FLAG maintains resource-level accumulation indicators over a project and date range.

The primary entry point for transaction accumulation is REFRESH_TXN_ACCUM, which accepts a project range, a PA date range, an optional transaction type, and an optional system linkage function. It coordinates the refresh of cost, revenue, and commitment accumulations. REFRESH_ACT_TXN_ACCUM, REFRESH_REV_TXN_ACCUM, and REFRESH_CMT_TXN_ACCUM perform the category-specific refresh of actual cost, revenue, and commitment accumulations. Each has a matching deletion counterpart — DELETE_ACT_TXN_ACCUM_DETAILS, DELETE_REV_TXN_ACCUM_DETAILS, and DELETE_CMT_TXN_ACCUM_DETAILS — used to clear stale detail before rebuilding.

The creation and accumulation layer includes CREATE_TXN_ACCUM, CREATE_TXN_ACCUM_DETAILS, CREATE_CMT_TXNS, and DELETE_CMT_TXNS for commitment records, together with ACCUM_ACT_TXN, ACCUM_REV_TXN, ACCUM_CMT_TXN, and ACCUM_CDLS, which perform the actual aggregation of cost distribution lines and revenue or commitment lines into accumulated form. UPDATE_ACT_TXN_ACCUM handles subsequent updates to existing actual accumulations.

Tables Accessed

The package reads and writes the core Projects transaction and setup tables through APPS synonyms. Expenditure data flows from PA_EXPENDITURES_ALL, PA_EXPENDITURE_ITEMS_ALL, PA_EXPENDITURE_TYPES, and PA_COST_DISTRIBUTION_LINES_ALL. Revenue accumulation draws on PA_CUST_REV_DIST_LINES, PA_CUST_EVENT_REV_DIST_LINES, PA_DRAFT_REVENUES, and PA_EVENTS together with PA_EVENT_TYPES. Commitments are sourced from PA_COMMITMENT_TXNS and its _S and _TMP counterparts, which is consistent with the commitment-oriented procedures and flags in the specification. PA_IMPLEMENTATIONS supplies implementation-level configuration, GL_DATE_PERIOD_MAP maps accounting dates to periods, and FND_APPLICATION provides application identification for standard WHO and diagnostic purposes.

Usage Notes

PA_TXN_ACCUMS is not normally invoked directly by end users. It is called from Oracle Projects concurrent programs and internal processing flows that refresh transaction accumulations, and from the three packages documented as referencing it. The presence of x_request_id, x_program_application_id, and x_program_id in the standard WHO variables confirms that it executes both in concurrent manager and in online transaction contexts. The error parameters x_err_stage and x_err_code follow the standard Oracle Projects error-handling convention and must be inspected by any custom caller. The NOCOPY hint on these parameters reflects Oracle 10g-era PL/SQL conventions carried into 12.1.1 and 12.2.2. The REFRESH_TXN_ACCUM entry point, with its project, date, transaction type, and system linkage function arguments, is the appropriate interface for targeted refresh operations in custom extensions, and the accompanying delete procedures should be used to remove obsolete details before re-running accumulation to avoid duplication.