Search Results ar_inv_reciept_amount




Overview

APPS.PA_PWP_CUSTOMER_INVOICE_V is a reporting view in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2) that consolidates Project Billing and Accounts Receivable (AR) information for a project's customer invoices. The name derives from the "PA PWP" family — Project Accounting (PA) "Project, Workplan, and Progress" billing summary objects — and the view presents draft and finalized invoice attributes alongside receipt, adjustment, outstanding, line, and tax amounts at three currency levels: invoice currency, project functional currency, and project currency.

The view functions primarily as a denormalized reporting layer. It joins the summary customer invoice data stored in PA_PWP_CUSTOMER_SUMM to the link status derived from PA_PWP_LINK_STATUS_V, exposing one row per invoice with computed aggregations. Most numeric amount columns are wrapped in NVL(..., 0) to prevent null propagation in financial reporting, and a ratio column (PFC_RATE) is computed via DECODE to avoid division by zero. This makes the view well suited for dashboards, reconciliation extracts, and downstream integration into data warehouses or custom OAF/BI Publisher reports.

Underlying Base Objects

The documented referenced base objects are:

Because the view references another view, the effective base at query time is PA_PWP_CUSTOMER_SUMM joined to whatever tables PA_PWP_LINK_STATUS_V resolves to. The PWP objects are populated by Project Billing between draft invoice generation and transfer to Oracle Receivables, so the view reflects the billing workbench state rather than the final AR transactional record.

Key Columns

  • DRAFT_INVOICE_NUM / RA_INVOICE_NUMBER — the draft billing number and the transferred AR invoice number, respectively.
  • CREDIT_OF — aliased from DRAFT_INVOICE_NUM_CREDITED. This column identifies the original draft invoice number that a credit memo reverses or adjusts, which is the column most relevant to a search term such as "credit_of". It allows a report to link credit transactions to their source invoices.
  • INVOICE_STATUS_M — aliased from INVOICE_STATUS, indicating the billing state (e.g., draft, approved, transferred).
  • Currency columnsINV_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE, and PROJECT_CURRENCY_CODE, each pairing with their respective amount families.
  • Amount families — parallel sets of bill, receipt, outstanding, adjustment, line, and tax amounts prefixed by INV_ (invoice currency), PFC_ (project functional currency), and PC_ (project currency). Examples include INVOICE_INV_AMOUNT, AR_PFC_RECIEPT_AMOUNT, and AR_PC_OUTSTANDING_AMOUNT.
  • PFC_RATE — the functional-to-invoice currency rate, computed as PFC_BILL_AMOUNT / INV_BILL_AMOUNT, defaulting to zero when the denominator is zero.
  • Invoice count and link amounts — invoice_count, PFC_LINK_AP_AMOUNT, and PC_LINK_AP_AMOUNT, sourced from the PLC aggregate.
  • Date columns — BILL_THROUGH_DATE, INVOICE_DATE, GL_DATE, and APPROVED_DATE for period and cutoff analysis.

Common Use Cases and Queries

Typical uses include credit memo tracing, AR aging reconciliation, project currency reporting, and billing workbench extracts. The CREDIT_OF column supports the recurring requirement to reconcile credit memos against the invoices they offset.

To list credit invoices and their referenced originals:

  • SELECT CREDIT_OF, DRAFT_INVOICE_NUM, RA_INVOICE_NUMBER, CUSTOMER_NAME, INVOICE_DATE, AR_INV_OUTSTANDING_AMOUNT FROM APPS.PA_PWP_CUSTOMER_INVOICE_V WHERE CREDIT_OF IS NOT NULL;

To summarize outstanding balances by customer in project functional currency:

  • SELECT CUSTOMER_NUMBER, CUSTOMER_NAME, SUM(AR_PFC_OUTSTANDING_AMOUNT) OUTSTANDING FROM APPS.PA_PWP_CUSTOMER_INVOICE_V GROUP BY CUSTOMER_NUMBER, CUSTOMER_NAME;

To identify invoices transferred to AR within a period:

  • SELECT RA_INVOICE_NUMBER, INVOICE_DATE, GL_DATE, INVOICE_STATUS_M FROM APPS.PA_PWP_CUSTOMER_INVOICE_V WHERE GL_DATE BETWEEN :p_start AND :p_end;

Because the view aggregates linked amounts and applies NVL defaults, consumers should confirm whether the PLC join introduces row multiplication for invoices with multiple link records before using the view for row-level transactional processing.