Search Results pa_accum_api




Overview
Explore in AI Chat

Overview

PA_ACCUM_API is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite. It is classified in the ETRM repository as an API, indicating that its procedures are intended for programmatic invocation rather than exclusively internal use. The package serves the Project Accounting (PA) module, whose core responsibility is to capture, accumulate, and report project cost and revenue transactions across the project lifecycle.

In Oracle Project Accounting, accumulation refers to the process of summarizing raw expenditure and revenue items—captured through subsystems such as Purchasing, Payables, and Time and Labor—into the project transaction and resource accumulators used for costing, burdening, budgeting, and reporting. PA_ACCUM_API exposes this accumulation logic through a controlled interface, allowing callers to retrieve accumulated transaction and resource totals for a given project without having to query the underlying accumulator tables directly. This encapsulation is significant because the PA accumulator tables are dense, denormalized structures that join transaction detail to project, task, and period definitions; the API shields callers from that complexity and provides a stable contract across releases.

Key Procedures and Functions

The documented package interface comprises four procedures and functions:

  • GET_PROJ_TXN_ACCUM — Retrieves accumulated transaction-level amounts for a project. This is the entry point used when a caller requires the raw accumulated totals associated with project transactions, as opposed to resource-summarized figures.
  • GET_PROJ_RES_ACCUM — Retrieves accumulated amounts at the resource level. Because PA accumulates cost by resource and resource list membership, this procedure supports reporting and analysis segmented by the resource dimension.
  • GET_PROJ_ACCUM_ACTUALS — Returns accumulated actual amounts for a project. Actuals represent costs and revenues already incurred, and are the basis for project cost reporting, revenue recognition, and profitability analysis.
  • GET_PROJ_ACCUM_BUDGETS — Returns accumulated budget amounts for a project, supporting budget-versus-actual comparison and funds checking scenarios.

The ETRM metadata deliberately does not publish parameter lists for these units; consumers should inspect the live package specification in the target instance before invoking them from custom code.

Tables Accessed

The package references the following tables through APPS synonyms:

  • PA_TXN_ACCUM and PA_TXN_ACCUM_DETAILS — the core project transaction accumulators that hold summarized transaction amounts by project, task, and period.
  • PA_RESOURCE_ACCUM_DETAILS — resource-level accumulated amounts, used by GET_PROJ_RES_ACCUM.
  • PA_RESOURCE_LIST_MEMBERS — defines resource list membership, establishing the resource grouping used in accumulation.
  • PA_TASKS — task definitions that partition project work and to which accumulated amounts are attributed.
  • PA_PERIODS and GL_PERIOD_STATUSES — period definitions and open/closed status, used to determine which periods are valid for accumulation and reporting.
  • PA_IMPLEMENTATIONS — implementation-level configuration controlling Project Accounting behavior.

Usage Notes

PA_ACCUM_API is referenced by two other documented packages, PA_PAXMGPSD_XMLP_PKG and PA_PAXMGTSD_XMLP_PKG, which are XML Publisher report packages. This confirms that the API is consumed by seeded concurrent programs in the Project Accounting reporting family, where report logic must obtain accumulated project amounts programmatically. Because it is classified as an API rather than a private helper, it is also a legitimate dependency for custom PL/SQL, Oracle Forms personalizations, and extensions that require project accumulator values.

Typical invocation occurs during concurrent report execution or within integration code that needs consolidated project totals without duplicating accumulation logic. Callers should respect period status when interpreting results, since accumulation is period-aware and closed periods may be excluded. As with all PA APIs, custom code should call the packaged interface rather than querying the accumulator tables directly, ensuring compatibility across EBS 12.1.1 and 12.2.2.