Results for “pa_draft_revenues_mrc_v”

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

Overview

PA_DRAFT_REVENUES_MRC_V is a Projects (PA) module reporting view that exposes draft revenue records in a single-organization, single-currency, single-set-of-books context. It is the "MRC" (Multi-Reporting Currency) companion to the base PA_DRAFT_REVENUES table, designed to flatten the multi-org/multi-currency structure into a form that can be queried under a specific operating unit and ledger. The view is not implemented in the database as a stored object in every instance; the ETRM metadata indicates "Not implemented in this database," meaning availability depends on whether the MRC feature set has been deployed.

Its primary role is to present draft revenue rows — the interim stage of revenue recognition before final revenue is generated — along with their associated accounting attributes (unbilled receivable, unearned revenue, realized gains/losses, GL and PA period names, and transfer status) scoped to the current organization context. This makes it suitable for reporting and integration scenarios where a single-org view of draft revenue is required without the caller needing to manually join the MRC shadow table and filter by set of books.

Underlying Base Objects

The view is defined over two documented base objects:

• PA_DRAFT_REVENUES PA — the base Projects table holding the core draft revenue records, including accounting flags, dates, code combinations, and the REVTRANS_* surrogate columns.
• PA_MC_DRAFT_REVS_ALL MC — the MRC (multi-reporting-currency) shadow table holding the set-of-books-specific amounts and batch names for each draft revenue row.

The join predicate links the two on PROJECT_ID and DRAFT_REVENUE_NUM, and filters the MRC side by SET_OF_BOOKS_ID derived from the session's CLIENT_INFO (specifically SUBSTRB positions 45–10, defaulting to -99 when absent). This is the standard EBS MRC mechanism for resolving the active ledger/org from the client context rather than requiring an explicit bind.

Key Columns

• PROJECT_ID / DRAFT_REVENUE_NUM — the natural key linking a draft revenue to its project.
• TRANSFER_STATUS_CODE / TRANSFERRED_DATE / TRANSFER_REJECTION_REASON — status of the transfer of revenue to GL.
• UNBILLED_RECEIVABLE_DR / UNEARNED_REVENUE_CR — amounts posted to the unbilled receivable debit and unearned revenue credit accounts. The view exposes NVL(PA.REVTRANS_UBR_DR, PA.UNBILLED_RECEIVABLE_DR) and NVL(PA.REVTRANS_UER_CR, PA.UNEARNED_REVENUE_CR), meaning the REVTRANS_* value is preferred when populated — this is the "revtrans_ubr_dr" the user searched for.
• UNBILLED_CODE_COMBINATION_ID / UNEARNED_CODE_COMBINATION_ID — the account code combinations used for the corresponding postings.
• REALIZED_GAINS_AMOUNT / REALIZED_LOSSES_AMOUNT / REALIZED_GAINS_CCID / REALIZED_LOSSES_CCID — realized foreign-exchange gain/loss amounts and their code combinations.
• GL_PERIOD_NAME / PA_PERIOD_NAME / GL_DATE / PA_DATE — accounting period and date context.
• ORG_ID — the operating unit, enabling single-org filtering.
• REVTRANS_CURRENCY_CODE — exposed via NVL(PA.REVTRANS_CURRENCY_CODE, PA_CURRENCY.GET_CURRENCY_CODE), giving the transaction currency.

Common Use Cases and Queries

Typical uses include reconciling draft revenue transfers, validating UBR/UER balances before revenue generation, and extracting draft revenue data for downstream reporting or integration. A sample query scoped to the current org and ledger:

SELECT d.project_id,
       d.draft_revenue_num,
       d.gl_period_name,
       d.org_id,
       d.unbilled_receivable_dr,
       d.uneared_revenue_cr,
       d.event_id
  FROM pa_draft_revenues_mrc_v d
 WHERE d.org_id = :p_org_id
   AND d.gl_period_name = :p_period
   AND d.transfer_status_code = 'U'
 ORDER BY d.project_id, d.draft_revenue_num;

Because the set-of-books filter is resolved from USERENV('CLIENT_INFO'), callers typically set the client info (via FND_GLOBAL or similar) before querying, ensuring the MRC amounts returned correspond to the correct reporting ledger. The view is particularly useful when debugging the REVTRANS_UBR_DR / REVTRANS_UER_CR values, since it surfaces both the remeasured and the base amounts with the NVL precedence applied.