Results for “pa_status_rsrc_ev_base_v”

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

Overview

PA_STATUS_RSRC_EV_BASE_V is an Oracle EBS Projects (PA) schema view owned by APPS. It is marked Status: VALID in the ETRM repository, and its documentation is explicitly tagged "10SC Only." This is a critical constraint: the view is a specialized construct historically associated with a limited set of deployments, and Oracle does not document it as a general-purpose reporting or integration interface. It should therefore be treated as an internal, deployment-specific object rather than a supported external API surface.

Functionally, the view bridges three conceptual areas of Project accounting data: resource accumulation detail (cost/quantity accumulation by resource), transaction accumulation by PA period, and customer event revenue distribution lines. Its overall role is to expose, for a given project, task, and resource list member, the revenue amount associated with a specific event number. The name prefix "STATUS" and the reliance on a SQL package for filtering indicate it is intended to feed a status-style report or a "current context" query where the caller sets the active project/task/resource context before querying.

Underlying Base Objects

Per the documented metadata, the view is defined over the following referenced objects, all accessed through synonyms in the APPS schema:

• PA_RESOURCE_ACCUM_DETAILS — resource-level accumulation detail, supplying PROJECT_ID, TASK_ID and RESOURCE_LIST_MEMBER_ID.
• PA_TXN_ACCUM — transaction accumulation header, supplying PA_PERIOD.
• PA_TXN_ACCUM_DETAILS — transaction accumulation lines; filtered to LINE_TYPE = 'E', and supplying EVENT_NUM, LINE_NUM and project/task keys.
• PA_CUST_EVENT_RDL_ALL — customer event revenue distribution lines, supplying AMOUNT.
• PA_STATUS — a PL/SQL package (not a table) invoked in the WHERE clause via PA_STATUS.GETPROJID, PA_STATUS.GETTASKID and PA_STATUS.GETRSRCMEMBERID.

The joins are keyed on TXN_ACCUM_ID between the resource accumulation detail, transaction accumulation header, and transaction accumulation detail. The event revenue line is then matched on PROJECT_ID, TASK_ID (with NVL(ERDL.TASK_ID, 0) handling null tasks), EVENT_NUM and LINE_NUM. The row restriction is supplied at runtime by the PA_STATUS session context rather than by bind parameters in the SQL itself.

Key Columns

• PROJECT_ID — the project identifier for the accumulation and event records.
• TASK_ID — the task identifier; task 0 represents the project-level (no-task) context.
• RESOURCE_LIST_MEMBER_ID — the specific resource list member whose accumulation is being reported.
• TXN_ACCUM_ID — the transaction accumulation identifier linking resource details to period and event details.
• PA_PERIOD — the PA accounting period of the accumulation.
• EVENT_NUM — the customer event/billing event number associated with the transaction line.
• REVENUE_AMOUNT — the revenue amount from PA_CUST_EVENT_RDL_ALL.AMOUNT, wrapped in NVL(..., 0) so that unmatched events return zero rather than null.

Common Use Cases and Queries

Because the view depends on the PA_STATUS package functions for row filtering, it cannot be queried standalone without a properly initialized PA status context (typically established by the Projects status/inquiry form). Any query must therefore rely on the session state set by that caller. In practice the view supports:

• Verifying, for the currently selected project/task/resource, which customer events carry revenue and at what amount.
• Reconciling resource accumulation detail against customer event revenue distribution lines for a given period.
• Diagnostic scripts executed from within the Projects application context, where PA_STATUS has already been populated.

A representative query follows. It returns only the rows matching the active context:

SELECT project_id,
       task_id,
       resource_list_member_id,
       txn_accum_id,
       pa_period,
       event_num,
       revenue_amount
  FROM apps.pa_status_rsrc_ev_base_v;

Where a broader slice is required, filtering must still respect that PA_STATUS drives the returned set; adding WHERE pa_period = :period or ordering by event_num narrows the output. Given the "10SC Only" designation, usage for custom reporting or interfaces should be avoided in favour of documented PA public views and APIs, since Oracle does not guarantee the presence or behaviour of this view across 12.1.1 and 12.2.2 environments.