Search Results pa_draft_revenue_items_mrc_v

Overview

The view PA_DRAFT_REVENUE_ITEMS_MRC_V belongs to the Oracle Projects (PA) module and is documented as a "Single currency MRC view." It is a reporting and integration construct layered over the draft revenue interface tables, exposing draft revenue line data in the reporting currency selected at runtime through the Multi-Report Currency (MRC) framework. The view is defined as a projection over a single base object, PA_DRAFT_REVENUE_ITEMS, and derives several additional columns rather than storing them physically. In the supplied ETRM metadata the view is noted as "Not implemented in this database," meaning the definition is documented but no corresponding object was created in the referenced environment.

The view's principal purpose is to present revenue amounts and associated exchange-rate attributes in a single currency context. It references PA_MC_CURRENCY_PKG and GL_MC_CURRENCY_PKG to compute currency conversions and currency codes, using the session-level USERENV('CLIENT_INFO') value to determine the active reporting currency. The term "MRC" (Multi-Report Currency) and "single currency" indicate that the view is intended for consumers that require one consistent currency representation of draft revenue data, rather than the multiple-currency set held in the base table.

Underlying Base Objects

Per the documented metadata, the view is defined over the base object PA_DRAFT_REVENUE_ITEMS, aliased as DRI. No other base tables are documented as referenced objects, although the view text calls two PL/SQL packages during execution:

• PA_MC_CURRENCY_PKG.SUM_MC_CUST_RDL_ERDL — used to derive converted revenue amounts for the draft revenue line.
• GL_MC_CURRENCY_PKG.GET_CURRENCY_CODE — used to resolve the reporting currency code from the client information setting, with a default of -99 when the value cannot be parsed.

The view therefore does not introduce new stored data; it re-projects the columns of PA_DRAFT_REVENUE_ITEMS and replaces or supplements multi-currency columns with derived single-currency equivalents. Because it is defined over a single base object with a straightforward column projection and function-based derivations, it behaves as an inline view suitable for joining to project, task, and revenue category reference data.

Key Columns

The view exposes the standard key and audit columns of the draft revenue line along with currency-specific attributes:

• PROJECT_ID, TASK_ID, DRAFT_REVENUE_NUM, LINE_NUM — the identifying keys of the draft revenue line.
• AMOUNT — the derived amount, returned as NVL(DRI.REVTRANS_AMOUNT, DRI.AMOUNT), expressing the transaction amount.
• REVENUE_SOURCE — the source indicator for the revenue line, carried directly from the base table. This is the column most relevant to the revenue_source search term.
• REVENUE_CATEGORY_CODE — the revenue category classification for the line.
• Currency code and amount column sets: PROJFUNC_CURRENCY_CODE, PROJFUNC_REVENUE_AMOUNT, PROJECT_CURRENCY_CODE, PROJECT_REVENUE_AMOUNT, FUNDING_CURRENCY_CODE, FUNDING_REVENUE_AMOUNT, REVPROC_CURRENCY_CODE, and the transaction set REVTRANS_AMOUNT / REVTRANS_CURRENCY_CODE.
• Rate attributes: FUNDING_RATE_TYPE, FUNDING_RATE_DATE, FUNDING_EXCHANGE_RATE, and the corresponding REVPROC_REVTRANS_RATE_TYPE, REVPROC_REVTRANS_RATE_DATE, REVPROC_REVTRANS_EX_RATE.
• Audit and concurrent request columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage involves reconciling or reporting draft revenue lines by source and category, or feeding downstream processes that require a single-currency revenue amount. A representative query filters by project and revenue source:

SELECT project_id,
       draft_revenue_num,
       line_num,
       task_id,
       revenue_source,
       revenue_category_code,
       projfunc_currency_code,
       projfunc_revenue_amount,
       project_currency_code,
       project_revenue_amount,
       revtrans_amount,
       revtrans_currency_code
  FROM pa_draft_revenue_items_mrc_v
 WHERE project_id = :p_project_id
   AND revenue_source = :p_revenue_source
   AND draft_revenue_num = :p_draft_revenue_num;

Aggregation by source is common when analyzing how revenue was generated across a project:

SELECT revenue_source,
       revenue_category_code,
       COUNT(*) line_count,
       SUM(projfunc_revenue_amount) total_projfunc_amount
  FROM pa_draft_revenue_items_mrc_v
 WHERE project_id = :p_project_id
 GROUP BY revenue_source, revenue_category_code;

Because the reporting currency is resolved at runtime through GL_MC_CURRENCY_PKG.GET_CURRENCY_CODE based on CLIENT_INFO, the returned PROJFUNC_CURRENCY_CODE values will reflect the session or profile context of the executing user. Queries should therefore be run within a consistent MRC session context to ensure currency comparability. When the object is not implemented in a given database, callers must rely on the base PA_DRAFT_REVENUE_ITEMS table and apply equivalent conversion logic.