Search Results pa_pwp_customer_summ




Overview
Explore in AI Chat

Overview

APPS.PA_PWP_SUMM_PKG is a PL/SQL package body supplied by Oracle Projects as part of the Subcontractor (Supplier) Workbench functionality within Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business purpose is to populate and maintain the summary table PA_PWP_CUSTOMER_SUMM, which is recorded in the embedded source comments as PA_PWP_CUSTOMER_SUMM_ALL. This table consolidates customer-facing billing and invoice information for a project so that the Supplier Workbench can present subcontractor-related transactions without repeatedly joining large transactional invoice tables at runtime.

The package is classified as OTHER in the ETRM 12.2.2 metadata and is owned by APPS. The header comment identifies the file as PAPWPSMB.pls at version 120.19, dated 2011/06/28. The source text explicitly notes that the data populated in the summary table is used in the subcontractor (supplier) workbench, confirming the package's role as the data-population engine behind that workbench. The primary driver is a project identifier, and the work is scoped per project.

Key Procedures and Functions

Three documented program units are exposed by this package. Parameter lists are deliberately not restated here; only purpose is described.

  • POPULATE_SUMMARY — The core routine. It first deletes existing rows from PA_PWP_CUSTOMER_SUMM for the project being processed, then inserts invoice-level attributes such as organization, project, draft invoice number, RA invoice number, credited draft invoice number, system reference, transfer status code, customer identifiers and name, invoice date, invoice status, invoice class, agreement number, bill-through date, project functional invoice transfer rate type and date, invoice currency, and audit columns. The embedded source also references a corrective cursor, added under bug 10061846, that derives multiplier factors for project functional and project bill amounts on draft invoices whose invoice amount sums to zero. This cursor joins PA_PWP_CUSTOMER_SUMM to PA_DRAFT_INVOICE_ITEMS and filters on transfer status code 'A' to reconcile lines with zero or mismatched amounts.
  • GET_RAINVOICE_NUM — Retrieves the RA (Receivables) invoice number associated with a given billing record, providing the linkage between Oracle Projects draft invoices and the corresponding Receivables invoice in the workbench display.
  • GET_LAST_INVOICE_DATE — Returns the most recent invoice date for the applicable billing context, supporting the workbench presentation of current billing status.

Note that the POPULATE_SUMMARY body also makes use of the PA_IMPLEMENTATIONS org identifier lookup, though a later bug (12534894) comments out the direct selection, reflecting ongoing maintenance of the logic.

Tables Accessed

The package reads and writes a small but focused set of tables, accessed through APPS synonyms. PA_PWP_CUSTOMER_SUMM is the target of the DELETE and INSERT statements and holds the summarized output. PA_DRAFT_INVOICE_ITEMS is joined in the corrective cursor to obtain draft invoice line amounts and line numbers. PA_DRAFT_INVOICES and PA_DRAFT_INVOICES_ALL supply invoice header details. PA_PROJECTS and PA_PROJECTS_ALL provide project attributes. PA_IMPLEMENTATIONS supplies operating unit context. PA_AGREEMENTS_ALL supplies agreement numbers for the inserted rows.

Additional tables documented against the package — AR_PAYMENT_SCHEDULES, AR_RECEIVABLE_APPLICATIONS_ALL, FND_TERRITORIES_TL, GL_PERIOD_STATUSES, HZ_CUST_ACCT_SITES, HZ_LOCATIONS, and HZ_PARTY_SITES — support customer, site, location, territory, period-status, and receivables application lookups used in building the customer summary and determining invoice and payment context.

Usage Notes

PA_PWP_SUMM_PKG is not documented as being referenced by any other package, indicating it is invoked directly by the application layer or by concurrent processing rather than as a shared library call. In practice, invocation occurs from the Subcontractor (Supplier) Workbench form flow, where a project's customer summary must be refreshed, and from concurrent programs that regenerate the summary table for one or more projects. Custom extensions should call POPULATE_SUMMARY with the target project identifier, recognizing that the procedure performs a destructive delete for that project before reinserting, and should avoid concurrent invocation for the same project. Because the routine depends on committed draft invoice lines with transfer status 'A', it should be run after invoice generation and transfer processing have completed. The GET_RAINVOICE_NUM and GET_LAST_INVOICE_DATE functions are suitable for read-only calls within custom reporting or form personalization, since they do not modify the summary table.