Results for “rollup_flag”

50+ results




Overview
Explore in AI Chat

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

Overview

PA.PA_PROJECT_EVENT_ACCUM is a Projects (PA) module table that stores accumulated totals of event revenue for projects and tasks. Per Oracle's ETRM documentation, the table is populated and used only when the Projects application is running in Dual Accumulation Mode, a configuration that maintains parallel accumulation logic for event-based revenue alongside the standard revenue accumulation. The object is classified as VALID in the PA schema and contains 19 documented columns in the 12.2.2 physical schema.

From a data-modeling perspective, the mined foreign-key structure suggests a link classification in Data Vault terms. The table does not represent a standalone business entity; instead, it resolves relationships between projects, tasks, event types, and accounting periods, carrying accumulated measures (event revenue) as descriptive context. Analysts designing a warehouse around this source should treat it as a transactional link table rather than a hub or satellite.

Key Information Stored

The surrogate primary key, PA_PROJECT_EVENT_ACCUM_PK, is composed of PROJECT_ID, PA_PERIOD, GL_PERIOD, EVENT_TYPE, and TASK_ID. A separate unique index, PA_PROJECT_EVENT_ACCUM_U1, adds ORGANIZATION_ID to the same grain, making it the stronger business-key candidate for multi-organization implementations.

  • PROJECT_ID — the project to which accumulated event revenue belongs; foreign key to PA_PROJECTS_ALL.
  • TASK_ID — the task within the project; foreign key to PA_TASKS.
  • EVENT_TYPE — the category of revenue-generating event; foreign key to PA_EVENT_TYPES.
  • PA_PERIOD — the Projects accounting period for which totals are accumulated.
  • GL_PERIOD — the corresponding General Ledger period, enabling reconciliation between PA and GL.
  • TOTAL_REVENUE — the accumulated event revenue amount for the project/task/event/period combination.
  • INC_TOTAL_REVENUE — the incremental portion of total revenue, supporting the dual accumulation comparison.
  • ROLLUP_FLAG — indicates whether the row represents a rolled-up summary value.
  • ORGANIZATION_ID — the operating unit or organization context, part of the unique index grain.
  • REVENUE_CATEGORY_CODE — classification of the revenue for reporting and GL derivation.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the process that populated the row.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Because this table exists only under Dual Accumulation Mode, its principal use is validating that event revenue accumulates consistently across the parallel accumulation paths. Typical scenarios include reconciling PA event revenue to GL balances by period, reporting revenue by event type and task, and troubleshooting discrepancies between the standard and dual accumulation results.

  • Period revenue reconciliation: aggregate TOTAL_REVENUE by PA_PERIOD and GL_PERIOD and compare against GL balances for the same accounting periods.
  • Project/task revenue detail: join to PA_TASKS and PA_PROJECTS_ALL to present accumulated event revenue at the task level for a given project.
  • Event-type analysis: group by EVENT_TYPE joined to PA_EVENT_TYPES to summarize revenue contribution by event category.
  • Population auditing: filter on REQUEST_ID or PROGRAM_ID to identify rows written by a specific concurrent program run.

A representative query pattern filters on the period and joins the three foreign-key parents:

  • SELECT a.PROJECT_ID, a.TASK_ID, a.EVENT_TYPE, a.TOTAL_REVENUE FROM PA.PA_PROJECT_EVENT_ACCUM a WHERE a.PA_PERIOD = :period AND a.ORGANIZATION_ID = :org_id;

Related Objects

The documented foreign-key relationships identify the primary parent objects, while index structure supplies additional join paths.

  • PA.PA_PROJECTS_ALL — joined on PROJECT_ID; supplies project number, name, and organization context.
  • PA.PA_TASKS — joined on TASK_ID; supplies task number and task-level attributes.
  • PA.PA_EVENT_TYPES — joined on EVENT_TYPE; supplies event type name and configuration.
  • PA.PA_PERIODS — implied by PA_PERIOD; maps the PA period to its start and end dates.
  • GL.GL_PERIODS — implied by GL_PERIOD; maps the GL period for financial reconciliation.
  • PA.PA_EVENT_ACCOUNTS / event revenue accounting tables — typically referenced when tracing the accounting generated from event revenue.
  • Projects Revenue Accounting and event revenue concurrent programs — depend on this table when Dual Accumulation Mode is enabled.