Search Results gl_per




Overview
Explore in AI Chat

Overview

PA_ACCUM_VIEW is a Projects (PA) module database view documented within Oracle E-Business Suite reference material for releases 12.1.1 and 12.2.2. The ETRM metadata identifies it as "10SC Only," indicating that the object is associated with a specific 10SC (ten-something) localized or legacy deployment rather than the standard global product. The documentation further records "Not implemented in this database," meaning the view was not instantiated in the captured environment; the definition is preserved for reference only.

Functionally, PA_ACCUM_VIEW consolidates accumulated project transaction data into a single reporting structure. It merges two distinct streams of project accounting information — expenditure item accumulations and project event accumulations — into one UNION-based result set. This design supports cross-period and cross-ledger reporting of revenue, raw cost, burdened cost, and quantity data, allowing reporting tools to retrieve expenditure and revenue activity by project, task, PA period, and GL period without joining the accumulation tables directly.

Underlying Base Objects

The view text references the following base objects:

The UNION combines the expenditure branch (labeled 'EXPENDITURE ITEMS') with the event branch (labeled 'EVENTS'), unifying both into a common column layout.

Key Columns

Common Use Cases and Queries

Typical usage involves period-by-period project performance reporting, reconciliation of project accumulations to the GL, and revenue-versus-cost analysis across expenditure and event streams.

Example query retrieving accumulated cost and revenue for a project across periods:

  • SELECT project_id, task_id, pa_period, gl_period, expenditure_type, expenditure_category, total_raw_cost, total_burden_cost, total_revenue, total_quantity FROM pa_accum_view WHERE project_id = :project_id AND pa_period BETWEEN :from_period AND :to_period ORDER BY pa_period, task_id;

Because the metadata records "Not implemented in this database," confirmation of object existence and column availability should be performed against the target instance before relying on the view in production reporting or integration. Where the view is absent, equivalent reporting is generally achieved by querying PA_PROJECT_EXP_ITEM_ACCUM and PA_PROJECT_EVENT_ACCUM directly with the same joins to PA_PERIODS and GL_PERIOD_STATUSES.