Search Results pfc_bill_amount
Overview
PA_PWP_CUSTOMER_SUMM_ALL is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores summarized customer invoice information used by the Subcontractor Workbench (PWP). It functions as a denormalized convenience table that consolidates draft invoice header context and counterparty billing attributes so the Workbench and related inquiry pages can present customer invoicing data without repeatedly querying the base Oracle Receivables (AR) transaction tables. Although it is a physical table under the PA schema, its contents are typically derived from the RA interface and project billing flows that populate draft invoices before they are transferred to Receivables.
The table is multi-organization aware, as evidenced by the ORG_ID column and its participation in the composite primary key. The documented primary key constraint, PA_PWP_CUSTOMER_SUMM_PK, is defined over (ORG_ID, PROJECT_ID, DRAFT_INVOICE_NUM), giving each row a natural composite business key rather than a synthetic surrogate identifier. Based on the heuristic Data Vault classification derived from the foreign key structure, this object is best modeled as a standalone table; in Data Vault terms it would most naturally be treated as a satellite-like or reference structure linked to project and invoice hubs, since no explicit parent-child FK relationships are documented in the ETRM metadata.
Because the table carries 58 documented columns and is oriented around monetary rollups in three parallel currencies, it supports reconciliation between project currency, project functional currency, and invoice currency views of billing and receipt activity.
Key Information Stored
The composite primary key columns ORG_ID, PROJECT_ID, and DRAFT_INVOICE_NUM uniquely identify each summarized draft invoice record within an operating unit. Notable business and descriptive columns include:
- RA_INVOICE_NUMBER and DRAFT_INVOICE_NUM_CREDITED – link the summary to the transferred Receivables invoice and any credited draft.
- CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER – identify the billed customer.
- BILL_TO_CUST_NUMBER, BILL_TO_CUST_NAME, SHIP_TO_CUST_NUMBER, SHIP_TO_CUST_NAME, BILL_TO_ADDRESS, SHIP_TO_ADDRESS – capture bill-to and ship-to parties and addresses.
- INVOICE_DATE, GL_DATE, APPROVED_DATE, RELEASED_DATE, BILL_THROUGH_DATE – key billing lifecycle dates.
- INVOICE_STATUS, INVOICE_CLASS, TRANSFER_STATUS_CODE, SYSTEM_REFERENCE, AGREEMENT_NUM and LAST_RA_INVOICE_NUMBER – control and reference context for the draft.
- PROJFUNC_INVTRANS_RATE_TYPE, PROJFUNC_INVTRANS_RATE_DATE, PROJFUNC_CURRENCY_CODE, PROJECT_CURRENCY_CODE, INV_CURRENCY_CODE – currency and conversion metadata.
- Amount groups PFC_* (project functional currency), PC_* (project currency), and INV_* (invoice currency), each containing BILL_AMOUNT, CP_BILL_AMOUNT, RECIEPT_AMOUNT, CP_RECIEPT_AMOUNT, OUTSTANDING_AMOUNT, ADJUSTMENT_AMOUNT, TAX_AMOUNT, and LINE_AMOUNT.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – standard audit columns.
Common Use Cases and Queries
Typical usage centers on reporting and reconciliation. A representative query retrieves outstanding balances for a project by invoice currency:
SELECT project_id, draft_invoice_num, inv_invoice_number,
inv_outstanding_amount
FROM pa_pwp_customer_summ_all
WHERE org_id = :p_org_id
AND project_id = :p_project_id
AND transfer_status_code = :p_status;
Other common scenarios include aging analysis using BILL_THROUGH_DATE and GL_DATE, cross-currency comparison of the PFC, PC, and INV amount columns, and reconciliation of TRANSFER_STATUS_CODE against successfully transferred RA invoices. Reporting tools such as Oracle BI Publisher, Discoverer, and custom OAF pages frequently query this table for Subcontractor Workbench display, since it pre-aggregates customer invoice data and minimizes joins to Receivables.
Related Objects
The following objects are most significant in relation to this table:
- PA_PROJECTS_ALL – joined on PROJECT_ID for project context.
- RA_CUSTOMER_TRX_ALL – matched via RA_INVOICE_NUMBER and CUSTOMER_ID to locate the transferred invoice.
- RA_CUSTOMER_TRX_LINES_ALL – line-level detail underlying the summarized amounts.
- HZ_CUST_ACCOUNTS / HZ_PARTIES – resolved through CUSTOMER_ID for customer and party details.
- PA_DRAFT_INVOICES_ALL – source of the draft invoice numbers summarized here.
- AR_INTERFACE tables – used during the transfer process referenced by TRANSFER_STATUS_CODE.
- PA_PWP_* Workbench views – UI-facing queries that consume this summary table.
-
Table: PA_PWP_CUSTOMER_SUMM_ALL
12.2.2
owner:PA, object_type:TABLE, fnd_design_data:PA.PA_PWP_CUSTOMER_SUMM_ALL, object_name:PA_PWP_CUSTOMER_SUMM_ALL, status:VALID, product: PA - Projects , description: This stores customer invoice information to be used in subcontractor workbench , implementation_dba_data: PA.PA_PWP_CUSTOMER_SUMM_ALL ,
-
View: PA_PWP_CUSTOMER_SUMMARY_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PA.PA_PWP_CUSTOMER_SUMMARY_V, object_name:PA_PWP_CUSTOMER_SUMMARY_V, status:VALID, product: PA - Projects , description: Subcontractor workbench customer summary view , implementation_dba_data: APPS.PA_PWP_CUSTOMER_SUMMARY_V ,