Results for “pa_cust_event_rev_dist_lines”

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

Overview

PA_CUST_EVENT_REV_DIST_LINES is an Oracle Projects (PA) view that exposes customer event revenue distribution lines in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified in the ETRM reference as a Single-Org view, meaning it is designed to return data for a single operating unit context rather than aggregating across multiple organizations in a single query result set. The view presents the detailed revenue distribution records generated when customer events are processed for revenue recognition and invoicing.

In the Oracle Projects revenue lifecycle, customer events drive the recognition of revenue against contract and project funding. Each event produces one or more distribution lines that identify how much revenue is recognized, which draft invoice or draft revenue document it is associated with, and the accounting code combination used to record the transaction. This view surfaces those lines in a denormalized, currency- and tax-enriched form, making it suitable for reporting, reconciliation, and integration. The ETRM entry notes the view is not implemented in the documented database, meaning its definition is supplied for reference and the object may not be instantiated until the relevant Revenue Management functionality is enabled.

Underlying Base Objects

The ETRM documentation identifies no separately documented base objects for this view, but the view text reveals it is drawn from the PA_CUSTOMER_EVENTS revenue distribution tables within the PA schema. The view combines the distribution line attributes with draft revenue, draft invoice, and accounting flexfield references, and applies the PA_MULTI_CURRENCY.GET_USER_CONVERSION_TYPE function to translate stored rate types into user-facing conversion type labels.

Because the view is Single-Org, it is expected to be queried with an ORG_ID constraint (or within a single operating unit session) so that rows returned belong to one organization. The view includes ORG_ID as a projected column, allowing callers to filter explicitly. Rate and amount values are stored in multiple currencies, and the view carries separate rate type, rate date, exchange rate, and converted amount columns for each currency basis, reflecting Oracle Projects multi-currency revenue processing.

Key Columns

• Identification: TASK_ID, EVENT_NUM, LINE_NUM, PROJECT_ID, ORG_ID identify the task, customer event, distribution line, project, and operating unit.
• Amounts: AMOUNT is the distribution amount. Parallel converted amounts are exposed for billing transaction, revenue processing, invoice processing, project, project functional, and funding currency bases (BILL_TRANS_AMOUNT, PROJECT_REVENUE_AMOUNT, PROJFUNC_REVENUE_AMOUNT, FUNDING_REVENUE_AMOUNT, and related BILL columns).
• Currency and rates: Columns such as REVPROC_CURRENCY_CODE, REVPROC_RATE_TYPE, REVPROC_RATE_DATE, and REVPROC_EXCHANGE_RATE (and INVPROC, PROJECT, PROJFUNC, FUNDING equivalents) capture the currency basis and conversion used.
• Accounting: CODE_COMBINATION_ID references the accounting flexfield combination used to record the distribution.
• Draft documents: DRAFT_REVENUE_NUM, DRAFT_REVENUE_ITEM_LINE_NUM, DRAFT_INVOICE_NUM, and DRAFT_INVOICE_ITEM_LINE_NUM link the line to its generated draft revenue and draft invoice documents.
• Reversal handling: LINE_NUM_REVERSED and REVERSED_FLAG indicate reversal relationships, while INV_GEN_REJECTION_CODE records invoice generation rejections.
• Tax: OUTPUT_VAT_TAX_ID, OUTPUT_TAX_EXEMPT_FLAG, OUTPUT_TAX_EXEMPT_REASON_CODE, and OUTPUT_TAX_EXEMPT_NUMBER expose output tax and exemption details.
• Retention: RETENTION_RULE_ID, RETN_DRAFT_INVOICE_NUM, RETN_DRAFT_INVOICE_LINE_NUM, and RETAINED_AMOUNT support retention processing.
• Audit/concurrency: CREATION_DATE, CREATED_BY, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE identify the originating request and program.
• Other: BATCH_NAME, PRC_GENERATED_FLAG, and the trailing NULL and TO_NUMBER/TO_DATE placeholders used for column alignment.

Common Use Cases and Queries

Typical uses include reconciling customer event revenue to draft revenue and draft invoices, validating currency conversion, and reporting output tax and retention on event-based revenue. A representative query follows.

• Revenue by project and event: SELECT project_id, event_num, line_num, amount, project_revenue_amount FROM pa_cust_event_rev_dist_lines WHERE org_id = :org_id ORDER BY project_id, event_num, line_num;
• Reconciliation to draft revenue: SELECT draft_revenue_num, draft_revenue_item_line_num, event_num, amount FROM pa_cust_event_rev_dist_lines WHERE org_id = :org_id AND draft_revenue_num IS NOT NULL;
• Tax and exemption review: SELECT event_num, line_num, output_vat_tax_id, output_tax_exempt_flag, output_tax_exempt_reason_code FROM pa_cust_event_rev_dist_lines WHERE org_id = :org_id AND output_tax_exempt_flag = 'Y';
• Reversal identification: SELECT event_num, line_num, line_num_reversed, reversed_flag, amount FROM pa_cust_event_rev_dist_lines WHERE org_id = :org_id AND reversed_flag = 'Y';

Because the view is documented as not implemented in the reference database, deployments should confirm availability before depending on it, and applications should always constrain by ORG_ID to respect its Single-Org design.