Search Results release_inv

Overview

PA_CLIENT_EXTN_PWP is an Oracle Applications (APPS) schema package that forms part of the Oracle Projects suite of client extensions supporting Pay When Paid (PWP) processing. In Oracle E-Business Suite 12.1.1 and 12.2.2, the CLIENT_EXTN naming convention identifies packages delivered as client extension hooks — pre-seeded integration points that Oracle Projects calls to allow customer-specific or standard business logic to participate in core transactions. The PWP designation refers to the Pay When Paid feature set, in which supplier and subcontractor costs are withheld from release until the corresponding customer invoice (receivable) has been collected or otherwise satisfied.

PA_CLIENT_EXTN_PWP is documented in the E-Business Suite Technical Reference Manual (ETRM) with the object type PACKAGE, owner APPS, and status VALID. Its API classification is listed as OTHER, and its primary role is to encapsulate the release logic associated with PWP invoice relationships. The package maintains a dependency relationship with the standard SYS.STANDARD package and is both referenced by and depends upon APPS.PA_CLIENT_EXTN_PWP itself, reflecting the standard package specification/body pairing. It interacts with the PWP invoice relationship package PA_PWP_INVOICE_REL, which is the module that controls the association between project invoices and the releases they authorize.

Key Procedures and Functions

The ETRM metadata documents exactly one procedure or function within this package:

• RELEASE_INV — The release invoice procedure. It implements the logic that evaluates whether a Pay When Paid hold may be lifted and, where the release conditions are satisfied, performs the release of the affected invoice transaction. This is the extension point invoked by the PWP framework when a release decision must be applied.

No parameter lists are published in the metadata, and the procedure should be treated as an internal extension routine rather than a publicly documented open API. Its invocation signature is dictated by the calling PWP components.

Tables Accessed

The package accesses the following tables through APPS synonyms, as documented in the ETRM:

• AP_INVOICES — The Oracle Payables invoice header table. It supplies the supplier-side invoice information required to determine which held invoice is being evaluated for release.
• PA_PWP_RELEASE_REPORT — The Pay When Paid release reporting table, holding the release status and detail records maintained by the PWP process for the organization in question.
• PA_PWP_RELEASE_REPORT_ALL — The "ALL" variant of the release report table, which spans all operating units or organizations. It supports cross-organization release reporting and is consulted when the release scope is not limited to a single organization.

Collectively these tables provide both the payable-side invoice identity and the PWP release state needed by RELEASE_INV to determine and record release outcomes.

Usage Notes

PA_CLIENT_EXTN_PWP is invoked indirectly through standard Oracle Projects and Payables PWP processing. It is referenced by the PWP invoice relationship package, PA_PWP_INVOICE_REL, which means that release logic flows from that component into this extension package rather than being called directly from a form. Typical triggering scenarios include the receipt of customer payment or the completion of project invoice collection that satisfies the Pay When Paid condition, at which point the held supplier invoice becomes eligible for release.

Because the package is not documented as an open interface, customizations should not call RELEASE_INV directly unless the calling context and parameter contract are fully understood from the package specification. The recommended practice in both 12.1.1 and 12.2.2 is to let the standard PWP concurrent and relational processes drive the release, and to extend behavior only through Oracle-supported extension mechanisms. When troubleshooting PWP release issues, DBAs and developers commonly query this package's source using the "show dependent code" facility referenced in the ETRM dependency listing.