Part requests
A request separates the need for a part from its physical delivery. It can be created from Inventory, from a report, or while suspending work for a reason that requires a part.
Availability: operational staff; approving, delivering, or rejecting requires Manage inventory. Level: Basic.
Purpose
It lets a user request a specific quantity from a warehouse, add a note and, when relevant, link it to a report, asset, position, or component. Requesters and managers can follow the decision and delivery.
Requirements
- An active warehouse and item accessible to the requester.
- A quantity greater than zero.
- To link a report, the user must be allowed to request parts for that work.
- A request targeted at an asset or component requires an active report or access to that asset, and its quantity is always one.
Step by step
- Choose Request in Inventory or use the report's Parts card.
- Select warehouse, item, and quantity; add a report and note when they provide useful context.
- For a targeted request, select the full asset, a template position, or the component that will be replaced.
- Submit it. The request becomes Pending and inventory managers are notified.
- A manager can Approve, Deliver, or Reject it. Delivery can be performed directly from Pending; prior approval is not required.
- The requester or a manager can cancel it while Pending or Approved.
Statuses, rules, and effects
- Pending: no decision has been made. It can be approved, delivered directly, rejected, or canceled.
- Approved: authorized but not deducted from stock. It can be delivered or canceled.
- Delivered: stock is reduced and the person who delivered it is recorded. This is final.
- Rejected: requires a reason and is final.
- Canceled: closes an open request without delivery.
- Approval never reserves or deducts stock; availability is checked again at delivery time.
- A linked delivery is recorded in the report conversation. If the work was suspended, the notification says that it can now be resumed, but does not resume it automatically.
- For serialized items, Inventory must select the exact physical units at delivery. A quantity item using hybrid tracking may also include exact units when applicable.
Required and optional information
Required: warehouse, item, and quantity; a reason for rejection; exact selection of all units for a serialized item. Optional: report, note, prior approval, and technical target. An approval note is also optional.
Practical example
A report is suspended because an SSD is missing. The technician requests one from the report. Since the part is available and urgent, the manager selects Deliver without approving it first. Stock decreases, the request ends as Delivered, and the technician is notified that work can resume.
Current limits
- Partial delivery is not available: the full quantity is delivered or none is.
- Approval does not guarantee later availability.
- A delivered request cannot be canceled or reopened.
- Delivering a part is not the same as installing it in an asset; installation is recorded separately.
This guide describes the features currently available to organization users.