Results for “accum_period”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_PRJ_ACCUM_PERIODS_V is a read-only Oracle EBS view owned by the APPS schema within the Projects (PA) module. It exposes the set of accumulation periods defined for a project at the project level, deliberately filtering out task-level, resource-level, and resource-list-level rows held in the underlying accumulation header table. The view is defined with the WITH READ ONLY clause, so it cannot be used as the target of DML and is intended purely for querying, reporting, and integration consumption.

Because accumulation headers in Oracle Projects can be stored at several levels of granularity — project, task, resource, resource list, and resource list assignment — consumers frequently need only the top-level, project-wide accumulation periods. PA_PRJ_ACCUM_PERIODS_V provides exactly this slice, presenting a simple two-column projection (PROJECT_ID and ACCUM_PERIOD) that answers the question: "For this project, which accumulation periods exist at the project level?" This makes it a convenient, low-cost access path for reporting and for integration programs that must resolve a project's accumulation period set without navigating the full header table or applying their own filtering logic.

Underlying Base Objects

The view is defined over a single base object, PA_PROJECT_ACCUM_HEADERS, referenced through its APPS synonym. PA_PROJECT_ACCUM_HEADERS is the primary table storing accumulation header records in Oracle Projects, keyed in part by project, task, resource, and resource list dimensions.

The view text applies a fixed predicate on the header table, retaining only rows where TASK_ID, RESOURCE_ID, RESOURCE_LIST_MEMBER_ID, RESOURCE_LIST_ID, and RESOURCE_LIST_ASSIGNMENT_ID are all zero. In Oracle Projects, a zero value in these dimension columns denotes "not applicable" or the all-levels context, so the filter isolates project-level accumulation headers. No joins, aggregations, or outer queries are involved; the view is a straight, filtered projection of two columns from PA_PROJECT_ACCUM_HEADERS. Because it is defined WITH READ ONLY, it inherits the read-only semantics and cannot be updated through the view. The documented ETRM metadata for 12.2.2 confirms the owner (APPS) and the single referenced base object (PA_PROJECT_ACCUM_HEADERS), consistent with the 12.1.1 definition.

Key Columns

• PROJECT_ID — The unique identifier of the project (foreign key to PA_PROJECTS). Identifies the project to which each project-level accumulation period belongs.
• ACCUM_PERIOD — The accumulation period associated with the project-level header. This is the period for which accumulation is performed or tracked at the project level.

The view intentionally exposes only these two columns; all other header attributes (task, resource, resource list, and assignment dimensions) are suppressed because they are fixed at zero by the view's filter.

Common Use Cases and Queries

Typical scenarios include determining the accumulation periods defined for a given project, driving period-based reporting, and validating project setup before running accumulation or summarization processes. Because the view is small and indexed through the base table, it is well suited to lookups within PL/SQL and Oracle Reports.

List all project-level accumulation periods for one project:

• SELECT project_id, accum_period FROM pa_prj_accum_periods_v WHERE project_id = :p_project_id;

Join to the project table for descriptive reporting:

• SELECT v.project_id, p.project_number, p.name, v.accum_period FROM pa_prj_accum_periods_v v, pa_projects_all p WHERE v.project_id = p.project_id ORDER BY p.project_number, v.accum_period;

Confirm whether a specific period is set up at project level:

• SELECT COUNT(*) FROM pa_prj_accum_periods_v WHERE project_id = :p_project_id AND accum_period = :p_period;

As the view is read-only, it should only be referenced in SELECT statements; any maintenance of accumulation headers must target the base table through supported Oracle Projects APIs or concurrent programs.