Search Results is_billed




Overview
Explore in AI Chat

Overview

PA_PWP_INVOICE_REL is a PL/SQL package in the APPS schema that supports Oracle EBS Project Billing and Pay When Paid (PWP) processing. Pay When Paid is a contractual arrangement in which a project's customer invoice is released to Accounts Receivable only after the related supplier invoice has been paid. The package acts as the controlling engine for that relationship: it holds customer invoices generated from PWP-enabled project agreements, evaluates whether the prerequisite supplier invoice and payment conditions have been satisfied, and then releases the held invoice so that normal revenue and receivables processing can proceed.

Within the Oracle EBS 12.1.1 and 12.2.2 releases, the object is classified as OTHER rather than as a published open interface. It is intended for internal use by the Project Billing application, and its interface is not formally committed for customer extensions. The package is stored in the APPS schema and carries a VALID status in the documented environment.

Key Procedures and Functions

The documented API surface contains six callable units. No parameter lists are published, so only their functional roles are described here.

  • RELEASE_INVOICE — Performs the core release action, permitting a previously held PWP customer invoice to move forward into the receivables cycle once the payment conditions have been met.
  • PAAP_RELEASE_HOLD — Removes or releases the hold applied to the draft invoice, complementing RELEASE_INVOICE in the hold-clearing path.
  • WRITE_LOG — Writes diagnostic and processing information to the PWP log, supporting troubleshooting of hold evaluations and release attempts.
  • IS_PROCESSED — Returns an indicator of whether a given invoice has already been processed by the PWP logic, guarding against duplicate release activity.
  • IS_ELIGIBLE — Evaluates whether an invoice qualifies for PWP handling, based on the invoice's project, agreement, and associated supplier invoice linkage.
  • IS_BILLED — Determines whether the related invoice has been billed, providing a further condition check before release is attempted.

Tables Accessed

The package reads and writes across the Project Billing, Payables, and Receivables schemas through APPS synonyms. The PWP linkage itself is maintained in PA_PWP_LINKED_INVOICES, which associates the supplier invoice with the customer invoice that is being held. Draft invoice data is held in PA_DRAFT_INVOICES and PA_DRAFT_INVOICE_ITEMS, with distribution and event information in PA_CUST_REV_DIST_LINES, PA_EVENTS, and PA_EVENT_TYPES. Project and expenditure context comes from PA_PROJECTS, PA_PROJECTS_ALL, PA_EXPENDITURE_ITEMS, and PA_EXPENDITURE_ITEMS_ALL. Supplier-side payment status is confirmed through AP_INVOICES_ALL and AP_HOLDS_ALL, while the receivables position is derived from AR_PAYMENT_SCHEDULES_ALL and AR_RECEIVABLE_APPLICATIONS_ALL. PA_IMPLEMENTATIONS provides installation-level setup and operating unit context. In the ETRM dependency listing the only object explicitly named as referenced is AP_INVOICES_ALL; the remaining tables are documented through the 12.2.2 package metadata.

Usage Notes

PA_PWP_INVOICE_REL is invoked indirectly by Oracle Project Billing rather than through a user-facing form. It is driven by the invoice generation and invoice review flows, where PWP-eligible customer invoices are identified, held, and subsequently released once the matching supplier invoice has settled. Concurrent processing, including billing generation and hold-release programs, calls into the package on behalf of the application. Because the API is classified as OTHER, custom code should not depend on its signature; integrators requiring PWP behavior should use supported Oracle APIs or the standard billing windows. When troubleshooting, WRITE_LOG output should be reviewed first, followed by the IS_ELIGIBLE, IS_BILLED, and IS_PROCESSED results to determine why an invoice has not been released. The package is not documented as being referenced by any other package, confirming its position as a leaf-level utility within the Project Billing stack.