Search Results revtrans_amount




Overview
Explore in AI Chat

Overview

PA_DRAFT_REVENUE_ITEMS is a transaction table within the Oracle Projects (PA) module of Oracle E-Business Suite, holding the individual revenue lines that make up a draft revenue record. It exists in both release 12.1.1 and 12.2.2 under the PA schema and is classified as VALID in the ETRM repository. A draft revenue run creates header records in PA_DRAFT_REVENUES_ALL and detail lines in PA_DRAFT_REVENUE_ITEMS; the items table therefore represents the granular, line-level revenue distribution used before revenue is finalized and transferred to the general ledger.

From a dimensional modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table is keyed dependently on a parent revenue document and carries the descriptive and financial attributes of each line, rather than standing alone as a hub or acting purely as an associative link.

Key Information Stored

The table contains 25 documented columns. The composite primary key, enforced by PA_DRAFT_REVENUE_ITEMS_PK, consists of PROJECT_ID, DRAFT_REVENUE_NUM, and LINE_NUM, with the unique index PA_DRAFT_REVENUE_ITEMS_U1 mirroring the same three-column business key. The most significant columns include:

Common Use Cases and Queries

Typical uses center on revenue reconciliation, validation before finalization, currency variance review, and reporting on revenue composition by task and category. A common pattern joins detail lines to the parent revenue header:

  • Retrieving all lines for a project's draft revenue: SELECT LINE_NUM, TASK_ID, AMOUNT, REVENUE_CATEGORY_CODE FROM PA.PA_DRAFT_REVENUE_ITEMS WHERE PROJECT_ID = :project_id AND DRAFT_REVENUE_NUM = :draft_revenue_num ORDER BY LINE_NUM;
  • Reconciling project-functional revenue against the entered amount: SELECT PROJECT_ID, DRAFT_REVENUE_NUM, LINE_NUM, AMOUNT, PROJFUNC_REVENUE_AMOUNT FROM PA.PA_DRAFT_REVENUE_ITEMS WHERE AMOUNT <> PROJFUNC_REVENUE_AMOUNT;
  • Aggregating draft revenue by category: SELECT REVENUE_CATEGORY_CODE, SUM(PROJFUNC_REVENUE_AMOUNT) FROM PA.PA_DRAFT_REVENUE_ITEMS GROUP BY REVENUE_CATEGORY_CODE;
  • Tracing audit lineage by request: SELECT * FROM PA.PA_DRAFT_REVENUE_ITEMS WHERE REQUEST_ID = :request_id;

Because revenue runs regenerate draft lines, queries should be scoped to the current draft revenue number and not relied upon as historical fact until the revenue is finalized and interfaced.

Related Objects

The table sits between the draft revenue header and downstream customer event and distribution objects:

  • PA_DRAFT_REVENUES_ALL – the parent header, joined on PROJECT_ID and DRAFT_REVENUE_NUM; items are meaningless without it.
  • PA_TASKS – referenced through TASK_ID to resolve task detail.
  • FND_CURRENCIES – referenced four times for the currency codes on each line.
  • PA_CUST_EVENT_RDL_ALL – customer revenue distribution lines linked back via PROJECT_ID, DRAFT_REVENUE_NUM, and DRAFT_REVENUE_ITEM_LINE_NUM.
  • PA_CUST_REV_DIST_LINES_ALL – revenue distribution lines keyed to the draft revenue item.
  • PA_MC_CUST_EVENT_RDL_ALL and PA_MC_CUST_RDL_ALL – multi-currency counterparts carrying the same join columns.

Together these relationships make PA_DRAFT_REVENUE_ITEMS the detail anchor from which Oracle Projects derives customer event and revenue distribution records prior to final revenue recognition.