Results for “pa_mc_draft_revs_all”

50+ results




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

Overview

PA_MC_DRAFT_REVS_ALL is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the draft revenue records generated for a project in each reporting currency. The "MC" designation indicates the table participates in Oracle's multi-currency architecture, while the "_ALL" suffix confirms it is an intersection table that holds one row per operating unit context. Each record represents a draft revenue amount, expressed in the reporting currency defined by the set of books, before that revenue is reviewed, adjusted, and transferred to the general ledger.

Functionally, the table acts as the staging repository within the revenue generation lifecycle. Draft revenues are produced by the revenue generation program, then reviewed, modified, or rejected, and ultimately transferred. Columns such as TRANSFER_STATUS_CODE, TRANSFERRED_DATE, and TRANSFER_REJECTION_REASON capture the outcome of each draft, making this a transactional rather than purely master-level repository. Under a heuristic Data Vault classification, the documented foreign-key structure suggests modeling this object as a link, because it resolves the relationship between an accounting set of books, a project, and a specific draft revenue instance. Practitioners designing a warehouse layer may treat it as a link satellite if transfer-state attributes are versioned separately from the natural business key.

Key Information Stored

The table contains 22 documented columns. The primary key, PA_MC_DRAFT_REVS_ALL_PK, is composed of SET_OF_BOOKS_ID, PROJECT_ID, and DRAFT_REVENUE_NUM. The unique index PA_MC_DRAFT_REVENUES_ALL_U1 enforces the same three-column combination as the business-key candidate, meaning no duplicate draft revenue number can exist for a given project and set of books.

Common Use Cases and Queries

The principal reporting scenario is reconciling draft revenue that has not yet been transferred to GL. A typical query selects pending drafts by project and set of books:

SELECT project_id, draft_revenue_num, transfer_status_code, unbilled_receivable_dr, unearned_revenue_cr FROM pa_mc_draft_revs_all WHERE set_of_books_id = :p_sob AND project_id = :p_project AND transfer_status_code IS NULL;

Additional scenarios include analyzing transfer rejections via TRANSFER_REJECTION_REASON, auditing realized gains and losses by batch name, and monitoring concurrent request outcomes through REQUEST_ID. Because the table is keyed by reporting currency, it supports multi-currency revenue reporting without re-deriving translated amounts. Reports frequently join to PA_DRAFT_REVENUES_ALL to obtain the transactional draft detail and to GL_SETS_OF_BOOKS_11I for the currency and book name.

Related Objects

  • PA_DRAFT_REVENUES_ALL — referenced by PA_MC_DRAFT_REVS_ALL.PROJECT_ID and DRAFT_REVENUE_NUM, supplying transactional draft revenue detail.
  • PA_PROJECTS_ALL — referenced by PROJECT_ID, providing project master attributes.
  • GL_SETS_OF_BOOKS_11I — referenced by SET_OF_BOOKS_ID, resolving the reporting currency and ledger.
  • PA_MC_DRAFT_REVS_ALL_PK and PA_MC_DRAFT_REVENUES_ALL_U1 — the primary key and unique business-key index that guarantee one row per books, project, and draft number.
  • PA_DRAFT_REVENUE_APIs and the revenue generation concurrent program — the PL/SQL interfaces and programs that populate and transfer these rows. Standard EBS revenue transfer logic consumes TRANSFER_STATUS_CODE and writes unbilled and unearned amounts to GL.