Purchase Requisition
Every request line from the Purchase Requisition form: what was asked for, its status, how much has been turned into a PO, and what remains. The working report of the purchasing desk.
Questions It Answers
- Which requests are approved but not yet turned into a PO?
- What quantity is still to be ordered for a given product?
- Who approved this requisition, and what is its estimated value?
Filters
| Filter | What it does |
|---|---|
| Transaction Date | Date range of the requisitions. Empty means the whole history - slow on years of data, so always fill it. |
| Division | Pre-filled from the user role's default division. A role locked to one division cannot change it. |
| Supplier | The supplier named on the request line (can differ per line). |
| Product | One product only. |
| Status | Draft, Pending Approval, Approved, Processed, or Cancelled. |
How To Read It
One row per requested product, so a requisition with five products shows five rows.
| Column | Meaning |
|---|---|
| Invoice, Transaction Date, Division, Department | Requisition number, date, and who the goods are for. |
| Status | Draft, Pending Approval, Approved, Processed, or Cancelled. The status belongs to the requisition, not the line. |
| Quantity | Quantity requested. |
| Processed | Quantity already placed on Purchase Orders. |
| Remaining Qty | Quantity - Processed: what still has to be ordered. |
| Purchase Price, Estimated Value | Estimated unit price when the requisition was made, and quantity x price. Not the invoice price. |
Why The Numbers May Differ
- Processed grows when a PO is created from the requisition - not when goods are received or invoiced.
- Cancelled requisitions still show with their status; use the Status filter to see active ones only.
- This report reads the requisition's own status, not the transaction approval workflow.
Purchase Price Permission
Columns derived from COGS or purchase prices - COGS, inventory value, purchase prices and totals, and profit - appear only for roles that have the Show Purchase Price History permission in User Roles. For other roles those columns are absent from the screen, prints, and exports, and the server does not send the figures at all - they are not merely hidden by the layout.
- A missing column does not mean the data is empty. If the user should see it, turn the permission on for their role and ask them to log in again so the report layout follows.
- Custom-built reports are not protected automatically; a copy made with Duplicate in Report Designer keeps the settings of the original.
Menu Location
- Procurement / Purchase Reports / Purchase Requisition
/report/purchaserequisition