Search Results pa_cust_event_rev_dist_line_pk

Overview

The PA_CUST_EVENT_RDL_ALL table is a core transactional table within the Oracle E-Business Suite Projects module (PA). It serves as the central repository for storing detailed revenue distribution lines for customer events. In the context of Oracle Projects, an event typically represents a billable milestone or transaction. This table is critical for the revenue recognition and billing processes, as it holds the granular financial data that determines how revenue from a project event is distributed across different accounting dimensions, such as tasks, revenue categories, and accounts. Its ALL suffix indicates it is a multi-organization access enabled (MOAC) table, storing data for all operating units accessible to a user, which is a standard architecture in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary key, PA_CUST_EVENT_REV_DIST_LINE_PK, is a composite key consisting of PROJECT_ID, EVENT_NUM, TASK_ID, and LINE_NUM. This structure uniquely identifies each revenue distribution line for a specific event on a project task. Beyond these identifiers, the table's extensive foreign key relationships reveal its primary data domains. It stores multiple currency codes (e.g., BILL_TRANS_CURRENCY_CODE, PROJECT_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE) and their corresponding conversion rate types (e.g., REVPROC_RATE_TYPE, PROJECT_REV_RATE_TYPE) from the GL_DAILY_CONVERSION_TYPES table, which is essential for multi-currency transactions and reporting. The link to AR_VAT_TAX_ALL_B via the OUTPUT_VAT_TAX_ID column integrates the distribution with tax calculations for invoicing. The table fundamentally stores the quantified revenue amounts, associated dates, and accounting flexfield segment assignments for each distribution line.

Common Use Cases and Queries

This table is primarily accessed for revenue analysis, audit reconciliation, and troubleshooting billing issues. A common reporting requirement is to trace the revenue distribution for a specific project event. The following query pattern is typical:

• SELECT project_id, event_num, task_id, line_num, revenue_amount, accounted_revenue, gl_date FROM pa_cust_event_rdl_all WHERE project_id = :p_project_id AND event_num = :p_event_num ORDER BY task_id, line_num;

Financial analysts use joins with PA_PROJECTS_ALL, PA_TASKS, and GL_CODE_COMBINATIONS to produce reports that show revenue distributed by project, task, and natural account. During period-end close, queries against this table help verify that all event revenue has been properly transferred to the General Ledger. Support and implementation consultants often query this table to diagnose discrepancies between projected revenue in PA and invoiced amounts in AR, examining the currency conversion rates and amounts stored in the distribution lines.

Related Objects

PA_CUST_EVENT_RDL_ALL has integral relationships with numerous foundational EBS objects. Its primary parent is the PA_CUST_EVENTS table, which defines the header-level event information. For financial processing, it is closely tied to the General Ledger (GL) through the GL_DAILY_CONVERSION_TYPES table for rates and the eventual creation of journal entries. For tax and invoicing, it references AR_VAT_TAX_ALL_B. The table is also a key source for the Projects Accounting currency translation processes. Common views that may simplify access to this data include PA_CUST_REV_DIST_LINES_V and other project revenue distribution reports. Data is typically populated and maintained via the Oracle Projects' revenue accrual and billing workflows, not via direct SQL manipulation.