Results for “pa_cust_event_rdl_all”

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

Overview

PA_CUST_EVENT_RDL_ALL is the Oracle Projects (PA) table that stores event revenue distribution lines for customer events processed through the Event Revenue Distribution and revenue recognition engine. Each row represents a distribution line generated when event revenue is apportioned across task, line, and code combination combinations, together with the full set of monetary amounts and exchange rate attributes required to report the transaction in the bill transaction, revenue processing, invoice processing, project, project functional, and funding currencies. In Oracle EBS 12.1.1 and 12.2.2 the object resides in the PA schema and is reported as VALID.

The table is an _ALL object, indicating it is partitioned by operating unit via the ORG_ID column and accessed through multiorg views. Its primary key, PA_CUST_EVENT_REV_DIST_LINE_PK, is defined on (PROJECT_ID, EVENT_NUM, TASK_ID, LINE_NUM), and a matching unique index, PA_CUST_EVENT_REV_DIST_LINE_U1, enforces the same business key. The documented physical schema contains 73 columns.

From a heuristic Data Vault modeling perspective, the metadata mined from the foreign key structure classifies this object as satellite-leaning. The composite natural key formed by PROJECT_ID, EVENT_NUM, TASK_ID, and LINE_NUM behaves like a hub/link key, while the numerous amount, currency, rate type, rate date, and tax attributes behave as descriptive satellite payload. This classification is a modeling suggestion only; in native EBS the table is a standard transactional child table.

Key Information Stored

The most significant columns are:

• PROJECT_ID, EVENT_NUM, TASK_ID, LINE_NUM — the composite primary key (PA_CUST_EVENT_REV_DIST_LINE_PK) and unique business key (PA_CUST_EVENT_REV_DIST_LINE_U1). Together they identify a single revenue distribution line for an event.
• AMOUNT — the distributed revenue amount on the line, held in the transaction currency.
• CODE_COMBINATION_ID — the GL accounting flexfield combination to which the distribution is posted; foreign key to GL_CODE_COMBINATIONS.
• DRAFT_REVENUE_NUM and DRAFT_REVENUE_ITEM_LINE_NUM — link the line to the draft revenue item generated from the event.
• DRAFT_INVOICE_NUM and DRAFT_INVOICE_ITEM_LINE_NUM — link the line to the corresponding draft invoice item when billing is generated.
• REVERSED_FLAG and LINE_NUM_REVERSED — indicate whether the line has been reversed and the original line reversed.
• ORG_ID — the operating unit, driving multiorg security on the _ALL table.
• Currency and rate attributes — BILL_TRANS_AMOUNT and BILL_TRANS_CURRENCY_CODE; REVPROC currency, rate type, rate date, and exchange rate; INVPROC equivalents; PROJECT_REVENUE_AMOUNT, PROJECT_BILL_AMOUNT and project rate attributes; PROJFUNC_REVENUE_AMOUNT, PROJFUNC_BILL_AMOUNT and project functional rate attributes; and FUNDING_REVENUE_AMOUNT, FUNDING_BILL_AMOUNT and funding rate attributes.
• Tax columns — OUTPUT_VAT_TAX_ID (foreign key to AR_VAT_TAX_ALL_B), OUTPUT_TAX_EXEMPT_FLAG, OUTPUT_TAX_CLASSIFICATION_CODE, and related exemption reason and number fields.
• Retention columns — RETAINED_AMOUNT and RETENTION_RULE_ID.
• Audit and concurrency columns — CREATED_BY, CREATION_DATE, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE.

There is no single surrogate sequence column; the primary key is the composite business key itself, and PA_CUST_EVENT_REV_DIST_LINE_U1 is the unique index that backs it.

Common Use Cases and Queries

Typical uses include reconciliation of event revenue to draft revenue and draft invoices, multi-currency amount validation, tax and retention reporting, and reversal tracking. A representative query returns the distribution lines for a specific event:

• SELECT project_id, event_num, task_id, line_num, amount, code_combination_id FROM pa_cust_event_rdl_all WHERE project_id = :project_id AND event_num = :event_num AND org_id = :org_id;
• Joining to GL_CODE_COMBINATIONS on CODE_COMBINATION_ID to resolve the accounting flexfield for a distribution line.
• Joining to AR_VAT_TAX_ALL_B on OUTPUT_VAT_TAX_ID to report output tax details for tax reporting.
• Filtering on REVERSED_FLAG and LINE_NUM_REVERSED to identify reversed and reversing lines.
• Aggregating PROJECT_REVENUE_AMOUNT, PROJECT_BILL_AMOUNT, and funding amounts by project and event to compare currency views.

Related Objects

The following are the most significant related objects, based on documented foreign key relationships:

• PA_DRAFT_REVENUE_ITEMS — referenced through PROJECT_ID; the draft revenue item generated from the event.
• PA_DRAFT_INVOICE_ITEMS — referenced through PROJECT_ID; the draft invoice item associated with the distribution line.
• PA_CUST_EVENT_RDL_ALL — self-referencing on PROJECT_ID; supports intra-table hierarchy and reversal relationships.
• PA_MC_CUST_EVENT_RDL_ALL — references this table on PROJECT_ID; the multiple-currency companion table.
• PA_TXN_ACCUM_DETAILS — references this table on PROJECT_ID; the transaction accumulator detail table.
• GL_CODE_COMBINATIONS — referenced through CODE_COMBINATION_ID for the accounting flexfield.
• FND_CURRENCIES — referenced by the currency code columns (bill transaction, revproc, invproc, project, project functional, and funding).
• GL_DAILY_CONVERSION_TYPES — referenced by the rate type columns for each currency view.
• AR_VAT_TAX_ALL_B — referenced through OUTPUT_VAT_TAX_ID for output tax reporting.