Search Results pa_draft_revenues_all




Overview
Explore in AI Chat

Overview

The PA_DRAFT_REVENUES_ALL table is a core transactional table within the Oracle E-Business Suite Projects module (PA). It serves as the primary repository for draft revenue records generated for projects. In the context of Oracle EBS 12.1.1 and 12.2.2, this table plays a critical role in the revenue management lifecycle, acting as a staging area for revenue calculations before they are finalized, approved, and transferred to the General Ledger. Its multi-org structure, denoted by the "_ALL" suffix, indicates it stores data for all operating units, making it essential for multi-organization implementations. The table's integrity is maintained through a primary key and a network of foreign key relationships with other fundamental project and financial tables.

Key Information Stored

The table stores header-level information for each draft revenue transaction. Key columns, as indicated by its primary and foreign keys, include PROJECT_ID and DRAFT_REVENUE_NUM, which uniquely identify each draft revenue record. The table links to critical financial and project control data through foreign keys. These include AGREEMENT_ID, which ties the revenue to a specific customer agreement, and code combination IDs such as UNBILLED_CODE_COMBINATION_ID and UNEARNED_CODE_COMBINATION_ID, which define the accounting flexfields for unbilled receivables and deferred (unearned) revenue. The self-referencing foreign key on DRAFT_REVENUE_NUM_CREDITED is particularly significant, as it enables the table to track credit memos or adjustments that directly offset an original draft revenue invoice, maintaining a clear audit trail for revenue corrections.

Common Use Cases and Queries

This table is central to processes involving the generation, review, and adjustment of project revenue. Common use cases include auditing draft revenue before final approval, tracing the lineage of credit memos back to their original invoices, and reconciling project revenue data before interfacing to GL. A typical analytical query might join this table to project and agreement details to summarize draft revenue by project or customer. For instance, to list all draft revenue for a specific project with its associated agreement, one might use a query pattern such as:

  • SELECT pdr.draft_revenue_num, pdr.revenue_amount, paa.agreement_num
  • FROM pa_draft_revenues_all pdr, pa_agreements_all paa
  • WHERE pdr.project_id = :p_project_id
  • AND pdr.agreement_id = paa.agreement_id;

Technical consultants often query this table to troubleshoot revenue interface issues or to validate data integrity by checking for orphaned records or mismatched code combinations.

Related Objects

As documented in the ETRM, PA_DRAFT_REVENUES_ALL has extensive relationships within the Projects schema. It is a parent table to several key transactional entities, including PA_DRAFT_REVENUE_ITEMS (which holds the detailed line items) and PA_DISTRIBUTION_WARNINGS. Its primary parent tables are PA_PROJECTS_ALL and PA_AGREEMENTS_ALL, establishing its foundation in project and contract management. The foreign keys to GL_CODE_COMBINATIONS underscore its integration with the financials stack. For multi-currency functionality, the PA_MC_DRAFT_REVS_ALL table stores the currency-converted amounts for each draft revenue record. When draft revenues are finalized, they are processed through the revenue interface to create accounting events, ultimately impacting the GL via the PA_PROJECT_ASSOCIATIONS and XLA tables.