Procurement reports
The Procurement heading of the Report menu has one entry, the Procurement Status Report. It is a direct download, not a module print mode, and it is the only report of the group that survived the move to the registry.
How this page was verified
Written from master on 2026-09-06. The installed rows were read from the QA databases the same day.
The entry
| Label | Code | Opens | Rendered by | Reads |
|---|---|---|---|---|
| Procurement Status Report | procurement_status_report | page=member&direct_download_report=procurement_status_report&get_form_filter=1 | modules/member/direct_download_report/procurement_status_report.inc.php (4,617 lines, on $pdo) and procurement_status_report.php; an .xlsx through PhpSpreadsheet | ts_spb, ts_spb_item, ts_rfq, ts_rfq_bidder_invited, ts_purchase_order, ts_mrr |
The first request, with get_form_filter=1, shows the filter form. The second builds the workbook and exits; member.php includes the two files and stops before rendering the page, which is why the report opens as a download. One row per requisition item, followed through RFQ, bid, PO and MRR: the status of each step and the dates.
What is seeded but hidden
The registry carries older procurement reports with no modules_parent, so they never show: Material Expediting (All, Summary, Look Ahead), PO/WO outstanding, Packing List, Certificate of Origin, Shipping Mark, Tender and Milestone Overdue, Sales Order, Commission Report, Returned Items, Filing Report. Their targets are print modes of modules that are no longer in the menu (sales_order, packing_list, package_order, tender) or of Material Expediting. Installing one of them is a database change plus a check that the print handler still runs on $pdo; most do not.
Gotchas
- The download ignores the grid filters. It has its own form. A user filtering the Requisition grid and then opening the report gets the whole project.
- A requisition with no RFQ still appears, with the later columns empty. That is the intended "where is it stuck" view, not a bug.
Instance differences
Checked on 2026-09-06 in the QA databases.
| Instance | Difference |
|---|---|
| Master | The entry is installed in all three QA databases. |
| JOTRE | The Procurement modules are installed, but no Procurement report row is installed in its QA database. The code is there. |
| Jadestone, Medco, Timas, KTP | Not installed; no Procurement modules either. |