Results for “pa_status_task_ev_base_v”

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

Overview

PA_STATUS_TASK_EV_BASE_V is an Oracle Applications (APPS) view belonging to the Projects (PA) product family. Its ETRM metadata describes it as "10SC Only", indicating it exists specifically to support the ten-stream reporting model associated with contract and event revenue processing rather than being a general-purpose Projects view. The view presents a consolidated projection of transaction accumulation data joined to customer event revenue distribution lines, exposing project, task, period, event, and revenue amount information for a single current transaction context.

Its role in Oracle EBS 12.1.1 and 12.2.2 is primarily internal and reporting-oriented. Rather than being a standalone transactional object, it serves as a convenient, pre-joined read surface over the event-based revenue tables, allowing concurrent programs, forms, or diagnostic queries to retrieve event revenue amounts aligned with accumulated transaction details without re-encoding the multi-table join logic each time.

Underlying Base Objects

The view text is defined over four documented base objects:

• PA_TXN_ACCUM (SYNONYM) — the transaction accumulation header providing PROJECT_ID, TASK_ID, TXN_ACCUM_ID, and PA_PERIOD.
• PA_TXN_ACCUM_DETAILS (SYNONYM) — the accumulation detail lines supplying EVENT_NUM and LINE_NUM, filtered to LINE_TYPE = 'E' (event lines).
• PA_CUST_EVENT_RDL_ALL (SYNONYM) — the customer event revenue distribution lines that supply the revenue AMOUNT.
• PA_STATUS (PACKAGE) — a PL/SQL package whose GETPROJID and GETTASKID functions are invoked in the WHERE clause to constrain the result to the currently selected project and task.

Joins are made on TXN_ACCUM_ID between the accumulation header and details, and on PROJECT_ID, TASK_ID (with NVL to zero), EVENT_NUM, and LINE_NUM between the detail lines and the event distribution lines. The NVL(ERDL.AMOUNT, 0) expression guarantees a numeric revenue amount even where no matching event line exists.

Key Columns

• PROJECT_ID — identifier of the project to which the accumulation belongs.
• TASK_ID — identifier of the task within the project.
• RESOURCE_LIST_MEMBER_ID — exposed as the literal 0, reflecting that this view is not resource-list-specific.
• TXN_ACCUM_ID — key to the transaction accumulation header record.
• PA_PERIOD — the accounting period of the accumulated transaction.
• EVENT_NUM — the customer event number driving the revenue line.
• REVENUE_AMOUNT — the distributed revenue amount, defaulting to zero when absent.

Common Use Cases and Queries

The view is typically queried in a context where the PA_STATUS package context has been initialized for a project and task, since its predicates depend on PA_STATUS.GETPROJID and PA_STATUS.GETTASKID. A representative query follows:

• SELECT project_id, task_id, pa_period, event_num, revenue_amount FROM apps.pa_status_task_ev_base_v;
• Diagnostic verification of event revenue amounts per accumulation: SELECT txn_accum_id, event_num, revenue_amount FROM apps.pa_status_task_ev_base_v WHERE pa_period = :period;

Because the view text references global package state, ad hoc queries executed outside that initialized context may return no rows. In both 12.1.1 and 12.2.2 the object remains a read-only projection; it must not be treated as an update target, and its output should be interpreted only within the ten-stream, event-based revenue reporting flow for which it was designed.