AP invoices currently on hold
Review AP hold records with no release code, alongside invoice and supplier details.
Tables used
ap_holds_all ap_invoices_all poz_suppliers_v
Bind parameters
No bind parameters. Add approved filters to narrow the scope.
How to run it
Paste it into a BI Publisher data model as a SQL data set, or into QueryWell's Query Studio and run it against your pod with a reporting account. Results come back to a grid you can profile, chart and export with a SHA-256 hash.
SELECT
i.invoice_id,
i.invoice_num,
i.invoice_date,
i.invoice_amount,
i.invoice_currency_code,
s.vendor_name AS supplier_name,
h.hold_reason,
h.hold_lookup_code,
h.release_lookup_code,
h.created_by,
h.creation_date AS hold_created
FROM ap_holds_all h
JOIN ap_invoices_all i ON i.invoice_id = h.invoice_id
JOIN poz_suppliers_v s ON s.vendor_id = i.vendor_id
WHERE h.release_lookup_code IS NULL
ORDER BY h.creation_date DESCHow to read the hold rows
An invoice can appear more than once because it has multiple holds, repeating its full invoice amount. Do not treat row count as invoice count or sum those amounts as an outstanding balance.
The filter is h.release_lookup_code IS NULL. There is no date, business-unit or unpaid-status filter; newest-first sorting does not restrict the reporting period. Invoice and supplier details must match the query's joins. Validate the scope and result against an approved reference before relying on it.
A single read-only SELECT against Oracle Fusion Cloud's supported reporting surface. Column names and views can differ by release and by the roles your reporting account holds, so validate the result against a report you already trust before relying on it.
apinvoicesholds
More Accounts Payable queries
Top 25 suppliers by spend (last 12 months)
Highest-volume vendors over the trailing 12 months — supports vendor concentration analysis.
Potential duplicate invoices (supplier + amount + number)
Same supplier with identical invoice_num and amount but different invoice_id — strong duplicate-payment indicator.
Manual (quick) payments — last 90 days
Payments created as Manual or Quick (payment_type_flag M/Q) on ap_checks_all, outside the normal payment process — review for governance.
Plan your AP holds reporting task
Discuss the scope and expected reference before a live evaluation. No credentials or customer data are needed for that conversation.
A live QueryWell run needs an approved reporting username/password with Basic authentication over HTTPS permitted, BI Publisher permissions for the task, and installation approval on macOS or Windows. Worksheet SQL creates temporary data models and reports; SSO-only access cannot currently execute it. Review the access requirements.