Item Requirement
A request for items from the store: what, how much, for which site and warehouse, and by when. It moves no stock. The store picks it and issues against it.
What it is for
It records internal demand in one place, so the store can pick it and the Item Requirement Tracking lists can show what is still open. An issue against it cannot be dated before the requirement.
The one rule people get wrong: a requirement cannot be deleted once issues or plans have been raised against it.
Every field in plain words
| Field | What it means | What to put |
|---|---|---|
| Transaction Date | The requirement's date | Required |
| Transaction Journal, Movement | The kind of need | |
| Origin Number, Name | The job or document it is for | |
| Site, Warehouse | The store asked | Site required. Every line takes them |
| Required Date, Required Time | When needed | Default for the lines |
| Responsible, Responsibility Central | Who asks | |
| Notes | Free text | |
| Item No, Item Variant, Name | The item | |
| Required Unit, Enter Quantity, Required Quantity | How much | More than zero |
| Required Date, Required Time | When needed, per line | |
| Picked, Handling Status, Picked Quantity, Picked Date | The pick, as recorded | |
| Line Text | Free text |
What it is connected to
- Picking List and Item Issue To Picking List - pick and issue it.
- Purchase Requisition - a purchase requisition can refer to it.
- Lists and reports - Item Requirement, Lines, Tracking and My Item Requirement Tracking.
If something looks wrong
- "Line ID: ... - Required Quantity cannot be zero" / "... Inventory Quantity cannot be zero" / "... Inventory Unit cannot be empty"
- "Item Requirement ... cannot be deleted. Following plans have been raised against it: ..." / "... Following Item Issue Transactions have been raised against it: ..."