Search Results rate_disc_reason_code




Overview
Explore in AI Chat

Overview

PA_CUST_REV_DIST_LINES is a single-organization Oracle Projects view that exposes customer revenue distribution lines generated during the revenue and billing cycle in Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents the row-level detail of how revenue is distributed and recognized against a project's eligible transactions, and how those amounts subsequently flow to draft invoices. Its principal role in the application is to support reporting, reconciliation, and integration scenarios that require the intersection of revenue processing and invoicing processing within a single organization.

The view is classified as a Single-Org object, meaning the query is expected to be filtered by ORG_ID and oriented to one operating unit at a time. In the documented environment it is listed as not implemented in the database, so it should be treated as a metadata-defined object that may exist in some installations but not others.

Underlying Base Objects

According to the documented view text, PA_CUST_REV_DIST_LINES is defined exclusively over the base table PA_CUST_REV_DIST_LINES_A. All columns are passed through directly; there are no joins, unions, or computed expressions in the view definition. No additional referenced base objects are documented for ETRM 12.2.2, and the view's own owner is not recorded in the supplied metadata.

Because it is a thin projection of a single table, the view inherits the transactional characteristics of PA_CUST_REV_DIST_LINES_A directly. There is no aggregation layer, so each row of the view corresponds to exactly one distribution line, preserving attributes such as reversal flags, batch names, request identifiers, and the audit columns CREATED_BY, CREATION_DATE, and PROGRAM_UPDATE_DATE.

Key Columns

Common Use Cases and Queries

The view is typically used to reconcile revenue recognized to revenue invoiced, to verify that invoice-eligible revenue was transferred to draft invoices, and to feed downstream reporting in Oracle Business Intelligence or custom extracts. A representative query for one operating unit is:

  • SELECT PROJECT_ID, DRAFT_REVENUE_NUM, DRAFT_REVENUE_ITEM_LINE_NUM, AMOUNT, BILL_AMOUNT, CODE_COMBINATION_ID, INVOICE_ELIGIBLE_FLAG FROM PA_CUST_REV_DIST_LINES WHERE ORG_ID = :p_org_id AND PROJECT_ID = :p_project_id ORDER BY DRAFT_REVENUE_NUM, LINE_NUM;
  • To isolate unbilled or failed invoicing lines: SELECT * FROM PA_CUST_REV_DIST_LINES WHERE INV_GEN_REJECTION_CODE IS NOT NULL AND ORG_ID = :p_org_id;
  • To audit the concurrent process that generated the lines: SELECT REQUEST_ID, BATCH_NAME, FUNCTION_CODE, COUNT(*) FROM PA_CUST_REV_DIST_LINES WHERE ORG_ID = :p_org_id GROUP BY REQUEST_ID, BATCH_NAME, FUNCTION_CODE;

Because the view exposes many currency and rate attributes, it is well suited to foreign-currency revenue reporting and to validating exchange rate application across the billing, project functional, and funding contexts.