Search Results pa_commitment_txns_s

Overview

PA_TXN_ACCUMS is a PL/SQL package body in the APPS schema that supports the Project Accounting transaction accumulation engine in Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business function is to summarize, or accumulate, detailed project transaction data into period-based accumulator balances used for costing, revenue recognition, billing, and commitment reporting. Rather than recalculating balances from raw expenditure and revenue lines on each inquiry, Oracle Projects maintains consolidated accumulation records; PA_TXN_ACCUMS is the programmatic layer that creates, refreshes, updates, and purges those records.

The package operates against the PA_TXN_ACCUM, PA_TXN_ACCUM_S, PA_TXN_ACCUM_DETAILS, and PA_PROJECT_ACCUM_HEADERS tables, and it derives its inputs from three distinct transaction families: actual expenditures, revenue events and distributions, and commitments. The package is classified as API classification OTHER, indicating it is an internal implementation package rather than a public, supported interface for customer extensions. The metadata records 24 documented procedures and functions and states that the object is VALID and not referenced by any database object, though it is referenced by three other packages.

Key Procedures and Functions

The documented program units follow a consistent naming pattern organized by transaction class. Initialization and configuration routines include INITIALIZE, GET_ACCUM_CONFIGURATIONS, CMT_LINE_ID, and UPDATE_RESOURCE_FLAG, which establish processing context, resolve configuration options, generate commitment line identifiers, and maintain resource-level flags used to determine which accumulators require rebuilding.

Actual cost accumulation is handled by REFRESH_ACT_TXN_ACCUM, UPDATE_ACT_TXN_ACCUM, DELETE_ACT_TXN_ACCUM_DETAILS, and ACCUM_ACT_TXN. Revenue accumulation is handled by REFRESH_REV_TXN_ACCUM, DELETE_REV_TXN_ACCUM_DETAILS, and ACCUM_REV_TXN. Commitment accumulation is handled by REFRESH_CMT_TXN_ACCUM, DELETE_CMT_TXN_ACCUM_DETAILS, CREATE_CMT_TXNS, DELETE_CMT_TXNS, and ACCUM_CMT_TXN. These routines accept or identify a project or transaction set, recalculate the corresponding accumulator values, and remove the detail rows associated with the prior calculation.

Generic accumulation infrastructure is provided by REFRESH_TXN_ACCUM, CREATE_TXN_ACCUM, CREATE_TXN_ACCUM_DETAILS, and the global ACCUM_CDLS routine, which processes cost distribution lines. The presence of separate refresh and delete routines indicates an incremental rebuild strategy: stale detail rows are deleted before the accumulator totals are recomputed.

Tables Accessed

The package references expenditure data through PA_EXPENDITURES_ALL, PA_EXPENDITURE_ITEMS_ALL, PA_EXPENDITURE_TYPES, and PA_COST_DISTRIBUTION_LINES_ALL, which supply the raw cost transactions being summarized. Revenue accumulation draws on PA_DRAFT_REVENUES, PA_CUST_REV_DIST_LINES, PA_CUST_EVENT_REV_DIST_LINES, PA_EVENTS, and PA_EVENT_TYPES. Commitment processing accesses PA_COMMITMENT_TXNS, PA_COMMITMENT_TXNS_S, PA_COMMITMENT_TXNS_TMP, and PA_COMMITMENT_TXNS_V; the sequence PA_COMMITMENT_TXNS_S is frequently associated with commitment transaction identifiers and is a common search target for site-specific inquiries.

Project and period context is obtained from PA_PROJECTS, PA_PROJECTS_ALL, PA_PERIODS, PA_PERIODS_ALL, PA_IMPLEMENTATIONS, GL_SETS_OF_BOOKS, and GL_DATE_PERIOD_MAP. Output is written to the accumulator tables PA_TXN_ACCUM, PA_TXN_ACCUMS, PA_TXN_ACCUM_DETAILS, PA_TXN_ACCUM_S, and PA_PROJECT_ACCUM_HEADERS. Utility and diagnostic dependencies include FND_APPLICATION, FND_GLOBAL, FND_PROFILE, PA_ACCUM_UTILS, PA_UTILS, PA_DEBUG, GMS_PA_API3, and PA_GMS_API.

Usage Notes

PA_TXN_ACCUMS is an internal engine package. It is most commonly executed indirectly through Oracle Projects concurrent programs such as the accumulator regeneration processes, through the Project Accounting forms when transaction amounts are displayed or recalculated, and through the costing and revenue generation flows that update project accumulators. Because PA_TXN_ACCUMS is not a published API and is referenced by only three other packages, direct invocation from custom code is not recommended. Extensions requiring accumulator data should read the PA_TXN_ACCUM inquiry views or call the supported Oracle Projects public APIs, since the internal procedure signatures and rebuild strategy may change between releases.