Results for “pa_status_proj_accum_headers_v”

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

Overview

The view PA_STATUS_PROJ_ACCUM_HEADERS_V is an Oracle EBS Projects (PA) application schema object owned by the APPS schema. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 environment, this view is classified under the Projects product module and is documented in the ETRM (E-Business Suite Technical Reference Manual) with the description "10SC Only." This designation indicates that the view is associated with a specific feature or configuration context, most likely a legacy or specialized accumulation-header presentation path rather than a general-purpose reporting view. Its role is to expose a filtered, status-driven projection of project resource accumulation header rows, scoped to the currently active project, task, and resource list identifiers retrieved through the PA_STATUS package. Because the view is driven by package-level session state rather than by bind parameters or a WHERE clause supplied by the caller, it is intended for internal application use—supporting concurrent programs, status views, or integration routines that require a status-contextualized list of accumulation header assignment rows.

Underlying Base Objects

The view is defined over three referenced base objects: the synonym PA_PROJECT_ACCUM_HEADERS, the synonym PA_RESOURCE_LIST_MEMBERS, and the package PA_STATUS. The core table PA_PROJECT_ACCUM_HEADERS (aliased PAH) supplies the primary row set. The view's selection criteria are driven entirely by three functions in the PA_STATUS package—GETPROJID, GETTASKID, and GETRSRCLISTID—which return the session's current project, task, and resource list identifiers. The definition is a UNION of two branches. The first branch selects accumulation header rows matching the current status identifiers directly. The second branch joins PA_PROJECT_ACCUM_HEADERS to PA_RESOURCE_LIST_MEMBERS (RLM) on RESOURCE_LIST_MEMBER_ID, restricting to rows where the parent member identifier is not null, and returns RLM.PARENT_MEMBER_ID in place of the original member identifier. This second branch is aggregated with a GROUP BY to collapse duplicates arising from the parent-member expansion, ensuring the union returns a distinct set of resource list assignment rows.

Key Columns

• PROJECT_ID — Identifier of the project to which the accumulation header row belongs, aligned with the value returned by PA_STATUS.GETPROJID.
• TASK_ID — Identifier of the task within the project, aligned with PA_STATUS.GETTASKID.
• RESOURCE_LIST_MEMBER_ID — Resource list member identifier. In the first branch this is the member identifier from the accumulation header; in the second branch it is the parent member identifier derived from PA_RESOURCE_LIST_MEMBERS.
• RESOURCE_LIST_ID — Identifier of the resource list associated with the accumulation header, aligned with PA_STATUS.GETRSRCLISTID.
• RESOURCE_LIST_ASSIGNMENT_ID — Identifier of the specific resource list assignment tied to the accumulation header row, carried through both branches of the union.

Common Use Cases and Queries

Because the view filters against session state held in PA_STATUS, its practical use assumes that GETPROJID, GETTASKID, and GETRSRCLISTID have been set by the calling application context. Typical scenarios include displaying accumulation header assignments for the currently selected project/task/resource list within Projects forms or status inquiries, and feeding parent-member-expanded assignment rows into downstream accumulation processing. A representative query is:

SELECT project_id, task_id, resource_list_member_id, resource_list_id, resource_list_assignment_id FROM apps.pa_status_proj_accum_headers_v;

Because no WHERE clause is permitted to override the internal status filter, callers that require different scoping must set the PA_STATUS context first or query the underlying PA_PROJECT_ACCUM_HEADERS table directly. Given the "10SC Only" classification, usage should be validated against the target release and configuration before relying on the view in custom reporting or integration code.