Part requisitions
Request approved catalogue parts, independently approve demand, reserve exact stock into a material kit and link existing governed shortage actions.
Screen orientation
requisitions:read exposes scoped demand; requisitions:create, requisitions:approve and requisitions:fulfill govern creation, independent decision and fulfilment. The requester and submitter cannot decide their own demand. Stock allocation is checked against site, clearance and the requisition's exact item revision.
New requisition opens a multi-line draft form above approval, shortage and issued metrics. Each requisition card shows demand and fulfilment separately; Plan fulfilment opens exact allocations and shortage-reference linking in a dialog.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Required site | Select | Required. | Choose the assigned site where the material is needed. | Scopes availability, allocation and downstream destinations. |
| Requesting work centre | Text | Required; at least two characters. | Name the team or cell that needs the parts. | Identifies the demand owner and eventual kit work centre. |
| Required date / Priority | Date and select | Date required; priority defaults to Routine. | Choose Routine, Urgent or Aircraft on ground according to the operational need. | Records scheduling context without bypassing approval. |
| Project / programme / Contract reference | Text | Optional. | Supply the project and contract references where applicable. | Retains business context on the demand. |
| Operational purpose | Text | Required; at least three characters. | Explain the build, maintenance or repair need. | Provides the basis for independent demand approval. |
| Item / Quantity / Line notes | Repeated select, decimal and text | 1–100 item lines; positive quantity required; notes optional. | Select approved catalogue items, one line per item. Add or remove lines before creating the draft. | Pins each requested item revision and quantity without reserving stock. |
| Reason for rejection | Browser text prompt | Required when rejecting; at least three characters. | Explain why the pending demand cannot be approved. | Retains the independent rejection rationale. |
| Exact stock identity | Per-line select | Required for each allocation being reserved. | Review the offered balance, including exact revision, location, pool and batch/serial/container. Choose Do not reserve now to leave a line unallocated. | Selects the precise unrestricted stock identity to reserve. |
| Reserve quantity | Decimal | Positive and within both available stock and remaining demand; serial allocation exactly one. | Check the suggested quantity before committing. Serial quantity is disabled; open-container content must remain reconciled. | Sets the quantity moved from UNRESTRICTED to RESERVED in a linked kit. |
| Requisition line / Downstream type | Selects | Required to link a shortage action. | Select the demand line and an existing Replenishment proposal, Receipt authority or Stock transfer. | Chooses the type of independently governed fulfilment reference. |
| Verified reference / Routed quantity | Text and decimal | Reference required; positive routed quantity within uncommitted demand. | Create the downstream record in its normal module first, then enter its exact reference and quantity. The server verifies matching item and target site and rejects quantities exceeding demand after existing commitments. | Records a link; it neither creates nor approves the downstream record. |
| Available / Reserved / Issued / Short | Read-only line badges | Derived from current stock and fulfilment records. | Distinguish physical availability, kit reservation, completed issue and shortage; a routed shortage is not received stock. | Shows progress without changing the approved demand. |
Actions and effects
When to use: When the requester has complete multi-line demand.
What it does: Creates a zero-stock draft; removing a form line only changes the unsaved draft.
When to use: Submit a draft as its requester or eligible administrator; decide pending demand independently.
What it does: Changes demand status only. Submission and approval use standard screen notes; rejection prompts for a reason.
When to use: For an approved requisition with fulfilment authority.
What it does: Opens proposed exact-stock allocations and shortage links without yet reserving stock.
When to use: After reviewing at least one eligible allocation.
What it does: Atomically creates a material kit and moves selected UNRESTRICTED stock to RESERVED. The requisition number becomes the kit's work-order reference; a different issuer completes the handoff.
When to use: After a downstream reference exists and matches the demand item and destination site.
What it does: Retains the routed quantity and reference, not a procurement or stock transaction.
When to use: When the next owning workflow is needed.
What it does: Navigates to the separate authority screen without executing its action.
Lists and states
- Requisition cards: number, demand status, fulfilment status, priority, classification, work centre, site, required date, project, purpose and creator/decider retain approval context.
- Requested-part rows: pinned revision, requested quantity, available/reserved/issued/short quantities and linked references show fulfilment without treating a proposal as stock.
Authority boundary
Drafting, submission, approval and shortage linking create no stock movement. Reserve selected material is an explicit inventory action that creates a linked kit and moves UNRESTRICTED to RESERVED; it does not issue the material or approve a purchase.