๐๏ธ Requisition Structure
Each purchase requisition includes:
PR Number
Auto-generated unique identifier (Format: PR-00000001, PR-00000002...)
Requested By
User or department initiating the request
Reason (optional)
Purpose or justification for the requisition
Urgency
Priority level (e.g., Low, Medium, High, Critical)
Status
Current state of the requisition (e.g., Pending, Approved, Rejected, Draft)
๐ฆ Requested Items
Each requisition can contain one or more product lines:
Product โ selected from the product/service catalog
Quantity โ required units
Unit Price โ estimated or predefined price
Total โ calculated automatically (Quantity ร Unit Price)
โ
Creating a Purchase Requisition
Go to Purchase Management โ Purchase Requisitions
Click Create Purchase Requisition
What happens automatically:
PR number is generated (e.g., PR-00000002)
Requested By is auto-filled based on the logged-in user
Status (e.g., Pending or Draft)
Step 2: Fill Out Basic Details
Enter or select:
Step 3: Add Items
For each required product:
Select Product from the dropdown
Add more lines using Add More
Remove lines using the trash (๐๏ธ) icon
Step 4: Save the Requisition
Click Create
If all validations pass, the requisition is saved and listed in the table.
๐๏ธ Deleting a Requisition
You can delete a requisition if:
It has not progressed to an irreversible stage (e.g., converted to PO or RFQ)
You have the correct permissions
Open the requisition list
Click the Delete ๐๏ธ action
Deletion will:
Remove the record permanently
Remove all associated product lines
๐๏ธ Purchase Requisition Detail View
After creation, you can click on the PR number to view full details.
What Youโll See:
๐งพ Header Section
Status Badge (e.g., Approved, Pending)
๐ Product Table
Columns include:
๐ Receipt Summary
Displays:
โ
Estimated Cost (auto sum of all product totals)
No separate edit form here โ editing happens inline or via the list view.
โ
Key Features & Rules
โ Automatic Numbering
Sequential format: PR-00000001, PR-00000002โฆ
Cannot be changed manually
โ Required Fields
Requested By (auto-filled)
At least one product item
Unit price is required (can be zero if allowed)
โ Validation Rules
Duplicate PR numbers not possible
Status must match your workflow
Empty item rows are not allowed
๐ Permissions & Access
Only authorized users can create requisitions
Edit/delete rights may depend on status or role
Audit logging tracks who created and modified requests
๐ผ Common Use Cases
Internal purchase requests for office supplies
Department-level procurement planning
Pre-approval before raising purchase orders
๐จ Error Handling
โ Missing Fields
The system highlights:
Required fields left empty
Missing product selection
โ No Items Added
A purchase requisition cannot be created without at least one valid item.
๐ฎ Best Practices
Always add a reason for clarity
Set the correct urgency to help with prioritization
Review costs before submitting
Use consistent product naming
Last updated