Results for “pa_cust_event_rdl_ar”

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

Overview

PA_CUST_EVENT_RDL_AR is an archive and purge table owned by the PA (Projects) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name, purpose, and column layout mirror the operational table PA_CUST_EVENT_RDL, which stores customer event revenue distribution lines associated with the Revenue Distribution process in Oracle Projects. The "_AR" suffix denotes "Archive/Relational," signaling that this table is populated during archive and purge operations rather than during normal transactional processing. The ETRM description explicitly states that it is a table for Archive/Purge and directs readers to the column comments on the main operational table for semantic detail.

Within the Oracle Projects Revenue Distribution architecture, records flow through staging, processing, and final distribution tables. When a purge batch is executed against customer event data, qualifying rows are moved or copied into PA_CUST_EVENT_RDL_AR, preserving the distribution detail for audit, reconciliation, or historical reporting before the live rows are deleted. Because the table is described as standalone from a data vault perspective—its only documented foreign key is PURGE_BATCH_ID referencing PA_PURGE_BATCHES_ALL—it is best modeled as a standalone satellite (or, heuristically, a purge-managed archive satellite) rather than a hub or link. This classification reflects that all business context is supplied by column values inherited from the source table, with the single FK tying each archived row back to its governing purge batch.

Key Information Stored

The table contains 71 documented columns that closely track the parent customer event revenue distribution records. The most significant columns include:

• PURGE_BATCH_ID — Foreign key to PA_PURGE_BATCHES_ALL; identifies the purge run that archived the row.
• PURGE_RELEASE and PURGE_PROJECT_ID — Purge/archive management attributes identifying the release and project scope of the archived data.
• EVENT_NUM and LINE_NUM — The business identifiers of the original customer event and distribution line, forming the natural business key inherited from the source.
• PROJECT_ID and TASK_ID — Project and task to which the customer event distribution belongs.
• AMOUNT — The distributed amount for the line.
• DRAFT_REVENUE_NUM, DRAFT_REVENUE_ITEM_LINE_NUM, DRAFT_INVOICE_NUM, and DRAFT_INVOICE_ITEM_LINE_NUM — Links between the event distribution and downstream draft revenue and draft invoice items.
• CODE_COMBINATION_ID — General Ledger account combination for the distribution.
• REVERSED_FLAG and LINE_NUM_REVERSED — Indicate whether the distribution line was reversed and the originating line number.
• ORG_ID — Operating unit identifier, enabling multi-org reporting.
• REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID — Concurrent request and concurrent program context that created the record.
• Currency and exchange rate groups — BILL_TRANS_*, REVPROC_*, INVPROC_*, PROJECT_*, PROJFUNC_*, and FUNDING_* column families store multi-currency amounts and rates at billing, revenue processing, invoice processing, project, project functional, and funding levels.
• RETAINED_AMOUNT and RETENTION_RULE_ID — Retention amounts and the retention rule applied to the line.
• OUTPUT_VAT_TAX_ID and OUTPUT_TAX_CLASSIFICATION_CODE — Tax configuration associated with the distribution.

The table is documented with a purge-managed structure rather than a declared single-column surrogate primary key. The effective business-key candidates are EVENT_NUM, LINE_NUM, PROJECT_ID, and ORG_ID, together with PURGE_BATCH_ID for archive uniqueness.

Common Use Cases and Queries

Typical usage centers on audit, reconciliation, and post-purge analysis of customer event revenue distributions. A common query retrieves all archived lines for a given purge batch:

• SELECT * FROM PA.PA_CUST_EVENT_RDL_AR WHERE PURGE_BATCH_ID = :batch_id;
• Join to the purge batch table to identify when and why the rows were archived: SELECT a.*, b.* FROM PA.PA_CUST_EVENT_RDL_AR a, PA.PA_PURGE_BATCHES_ALL b WHERE a.PURGE_BATCH_ID = b.PURGE_BATCH_ID;
• Compare live versus archived distribution counts for a project by querying PA_CUST_EVENT_RDL and PA_CUST_EVENT_RDL_AR for the same PROJECT_ID and EVENT_NUM.
• Reconcile retained amounts and multi-currency totals by aggregating RETAINED_AMOUNT, PROJECT_REVENUE_AMOUNT, and FUNDING_REVENUE_AMOUNT grouped by PROJECT_ID, TASK_ID, and CODE_COMBINATION_ID.
• Trace draft revenue and draft invoice linkage using DRAFT_REVENUE_NUM, DRAFT_REVENUE_ITEM_LINE_NUM, DRAFT_INVOICE_NUM, and DRAFT_INVOICE_ITEM_LINE_NUM for historical documentation of revenue and billing flows.

Reporting typically excludes this table from operational dashboards and includes it only in historical or compliance reports, since its contents represent purged data.

Related Objects

The most significant related objects are the purge infrastructure and the source distribution tables:

• PA_PURGE_BATCHES_ALL — Referenced by the foreign key PA_CUST_EVENT_RDL_AR.PURGE_BATCH_ID; defines each archive/purge run.
• PA_CUST_EVENT_RDL — The primary operational source table whose rows are archived into this table.
• PA_CUST_EVENTS — Parent customer event header, linked through PROJECT_ID and EVENT_NUM.
• PA_PROJECTS_ALL and PA_TASKS — Project and task definitions referenced by PROJECT_ID and TASK_ID.
• PA_DRAFT_REVENUES and PA_DRAFT_INVOICES_ALL — Downstream revenue and invoice documents linked via DRAFT_REVENUE_NUM and DRAFT_INVOICE_NUM.
• GL_CODE_COMBINATIONS — Account validation for CODE_COMBINATION_ID.
• HR_OPERATING_UNITS — Operating unit context for ORG_ID.
• FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS — Execution context for REQUEST_ID and PROGRAM_ID.

Together these objects support end-to-end reconstruction of revenue distribution history after purge processing completes.