Search Results pa_pwp_ap_inv_hdr




Overview
Explore in AI Chat

Overview

PA_PWP_AP_INV_HDR is a temporary (staging) table in the Oracle Projects (PA) schema that stores processed supplier invoice data at the invoice header level. It belongs to the Pay When Paid (PWP) and Delinquent Vendor/Lien (DLV) processing framework within Oracle Projects, which supports withholding, release, and payment-hold decisions on supplier invoices associated with project-related commitments. Rather than serving as a permanent transactional store, the table acts as an interim workspace populated during PWP/DLV batch processing, where supplier invoice records are assembled, validated, evaluated against hold rules, and later consumed to drive hold application or release logic before final processing against Oracle Payables.

Under a heuristic Data Vault classification mined from its foreign key structure, PA_PWP_AP_INV_HDR is hub-leaning. It carries a single-column primary key (PA_PWP_AP_HDR_ID) and is referenced by the detail table PA_PWP_AP_INV_DTL through that same key column, which is the classic pattern of a hub whose descriptive attributes and subordinate line-level records hang off it. In a Data Vault model this table would typically be treated as a hub for the invoice-header business entity, with a satellite capturing the descriptive attributes and a link connecting it to project, vendor, and invoice identifiers.

Key Information Stored

The table's 29 documented columns capture the invoice header context needed for PWP/DLV evaluation. The most significant columns include:

Common Use Cases and Queries

Typical use cases center on diagnosing why an invoice was held, released, or rejected under PWP/DLV rules, and on reconciling processed invoices back to Payables and Projects. A frequent query joins the header to its detail rows to trace hold decisions:

  • SELECT h.INVOICE_NUM, h.SUPPLIER_NAME, h.PWP_HOLD_FLAG, h.DLV_HOLD_FLAG, h.HOLD_REASON, h.PAYMENT_STATUS FROM PA.PA_PWP_AP_INV_HDR h WHERE h.PWP_HOLD_FLAG = 'Y';
  • Joining to the detail table to examine line-level hold logic: SELECT h.INVOICE_NUM, d.* FROM PA.PA_PWP_AP_INV_HDR h, PA.PA_PWP_AP_INV_DTL d WHERE h.PA_PWP_AP_HDR_ID = d.PA_PWP_AP_HDR_ID;
  • Reporting on held amounts by project or supplier for cash-flow and dispute analysis, filtering on INVOICE_DATE and grouping by PROJECT_ID or VENDOR_ID.

Because the table is temporary in nature, queries are most meaningful immediately after a PWP/DLV processing run, before the workspace is repopulated. It should not be treated as a persistent audit repository; permanent hold history belongs in the transactional Payables and Projects tables.

Related Objects

The most significant related objects, drawn from the documented foreign key structure, are:

  • PA_PWP_AP_INV_DTL – the detail table that references the header via PA_PWP_AP_INV_DTL.PA_PWP_AP_HDR_ID = PA_PWP_AP_INV_HDR.PA_PWP_AP_HDR_ID; this is the direct child of the header.
  • AP_INVOICES_ALL – the underlying Oracle Payables invoice entity, referenced by INVOICE_ID.
  • AP_SUPPLIERS / PO_VENDORS – supplier master data referenced by VENDOR_ID.
  • PA_PROJECTS_ALL – project master referenced by PROJECT_ID.
  • AP_INVOICE_PAYMENTS_ALL and Payables payment tables – relevant to PAYMENT_STATUS reconciliation.
  • PO_HEADERS_ALL – purchase order context referenced by PO_NUMBER.

These relationships position PA_PWP_AP_INV_HDR as the header hub connecting invoice, supplier, project, and purchase-order context within the Pay When Paid processing workspace.