Results for “event_num”

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

Overview

PA_STATUS_EV_BASE_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered under the Projects (PA) product family. The ETRM metadata documents its status as VALID in both 12.1.1 and 12.2.2, with the description "10SC Only." This designation indicates the view exists to support a specific, restricted functional scope — typically associated with a specialized revenue/event status processing path — rather than the general-purpose project status reporting exposed by the mainstream PA_STATUS views.

Functionally, the view aggregates revenue amounts at the intersection of project, task, resource list member, transaction accumulator, project accounting period, and event number. It serves as a consolidated, pre-summarized source for event-based revenue data, presenting the rolled-up results of two sibling views so that downstream reporting, reconciliation, and integration logic can query one object instead of two. Because it is a base view (suffixed _BASE_V), it is intended for internal consumption by other views, program units, and the PA_STATUS package rather than for direct end-user reporting, though it is queryable by any schema with the appropriate grants.

Underlying Base Objects

The documented referenced base objects are:

• PA_STATUS (PACKAGE) — the PA package that orchestrates status and revenue processing; the view sits within its processing footprint.
• PA_STATUS_TASK_EV_BASE_V (VIEW) — supplies task-level event revenue rows.
• PA_STATUS_RSRC_EV_BASE_V (VIEW) — supplies resource-level event revenue rows.

The view text is a UNION of two aggregate SELECT statements. The first selects PROJECT_ID, TASK_ID, RESOURCE_LIST_MEMBER_ID, TXN_ACCUM_ID, PA_PERIOD, EVENT_NUM and SUM(REVENUE_AMOUNT) from PA_STATUS_TASK_EV_BASE_V grouped by those six non-measure columns. The second performs the identical aggregation against PA_STATUS_RSRC_EV_BASE_V. The UNION therefore materializes a single distinct set of event-level revenue summaries, merging the task-oriented and resource-oriented perspectives. Note that UNION (not UNION ALL) is used, so duplicate combinations of the six key columns across the two branches collapse into one row, with revenue amounts not added together across branches. This is a deliberate deduplication semantic that must be understood before the view is consumed in arithmetic.

Key Columns

• PROJECT_ID — identifier of the project to which the event revenue pertains.
• TASK_ID — identifier of the task within the project; the task-level grain inherited from PA_STATUS_TASK_EV_BASE_V.
• RESOURCE_LIST_MEMBER_ID — the resource list member associated with the transaction, enabling resource-based revenue analysis.
• TXN_ACCUM_ID — the transaction accumulator identifier, the key grouping structure used in PA revenue and billing accumulation.
• PA_PERIOD — the project accounting period (PA period name or identifier) in which the event falls.
• EVENT_NUM — the event number, directly corresponding to the user's search term. It distinguishes individual revenue events, allowing multiple events within the same period and accumulator to be tracked separately.
• REVENUE_AMOUNT — the summed revenue amount for the grouped combination. Because it is produced by SUM, it is a derived measure and is not a stored base-table column.

Common Use Cases and Queries

Typical uses include reconciling event-level revenue against PA_STATUS outputs, validating event numbering continuity, and feeding summarized revenue into custom reporting or interfaces. A representative query lists summarized revenue by project and event number:

SELECT project_id, task_id, pa_period, event_num, SUM(revenue_amount) revenue
FROM apps.pa_status_ev_base_v
WHERE project_id = :p_project_id
GROUP BY project_id, task_id, pa_period, event_num;

To inspect all events for a given accumulator and period:

SELECT event_num, resource_list_member_id, revenue_amount
FROM apps.pa_status_ev_base_v
WHERE txn_accum_id = :p_accum_id AND pa_period = :p_period
ORDER BY event_num;

Because the view already performs aggregation, joins to PA_PERIODS or PA_PROJECTS on the respective identifier columns are common to resolve names. Analysts should remember that the UNION deduplication means the view is suitable for distinct event-level lookup; when an additive total across task and resource dimensions is required, the underlying PA_STATUS_TASK_EV_BASE_V and PA_STATUS_RSRC_EV_BASE_V views should be queried directly. As a 10SC-only base view, its column set and semantics should be treated as internal and subject to change across patches.