Reference & Data Model
Procurement request (good_procurement_request)
A procurement request (BAUF) requests a quantity of a good variant, either from stock or via purchase.
Purpose
Section titled “Purpose”The procurement request is the project’s demand notification to warehouse and purchasing. It carries good, quantity, delivery address and dates and has a status. Planned material costs and stock movements arise from it. (Transactional data)
Where in the app
Section titled “Where in the app”Project › tab „Beschaffung“ (Procurement) › table „Beschaffungsaufforderungen“ (columns „Typ“, „Gut-Variante“, „Menge“, „Fällig am“, „Frühstens am“, „Status“ — type, good variant, quantity, due on, earliest on, status), with filter and sorting (Guides › Procurement). „Neue Beschaffungsaufforderung“ (New procurement request) creates a manual request. In the tab „Engineering“ per component: cards „Beschaffungsaufforderungen“ with „Neue Beschaffungsaufforderung“ (Guides › From engineering to order). Status and dates can also be changed on the goods card in „Ressourceneinsatz“.
Fields
Section titled “Fields”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Type | type |
Selection | yes | „Lageraufforderung“ (stock request, stock) or „Einkaufsaufforderung“ (purchase request, purchase) |
From the component: proposal „Einkauf“ when the stock does not cover the remaining quantity |
| Status | state |
Selection | yes | „Offen“, „Erledigt“, „Fehlgeschlagen“ (open, done, failed) | Default „Offen“; badge blue/green/red |
| Good variant | good_variant_id |
Reference | yes | Requested good (name, SKU, good type) | Manual: search across all variants; component: fixed |
| Quantity | quantity |
Number | yes | Quantity in base units; the table shows quantity × base quantity | Component: proposal = bill-of-materials quantity |
| Address | address |
Address | yes | Delivery address | – |
| Due on | due_date |
Date | no | Latest date | |
| Earliest on | earliest_date |
Date | no | Earliest date | |
| Component | technical_structure_good_id |
Reference | no | Origin from engineering | Manually created: empty |
| Project | project_id |
Reference | no (always set) | Project of the request |
Not displayed: currency (set, not shown), optimization_run_id (system; marks Optimizer requests).
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
| Project | belongs to | no | kept | deleted along |
| Component | belongs to | no | — | reference cleared |
| Good variant | belongs to | yes | — | blocked (a variant with requests cannot be deleted) |
| Good usage | has many | — | — | kept (reference on the usage is kept) |
States
Section titled “States”| Value | Label | Meaning | Set by |
|---|---|---|---|
open |
Offen | Demand reported, not yet fulfilled | Creation; warehouse (movement „ausstehend“, pending) |
done |
Erledigt | Material withdrawn or procured | User; warehouse (movement „erfüllt“, fulfilled) |
failed |
Fehlgeschlagen | Cannot be fulfilled | User; warehouse (movement „storniert“, cancelled) |
┌──────────────────┐Creation ─► OPEN „Offen“ ├──► DONE „Erledigt“ └────────┬─────────┘ └──────────────► FAILED „Fehlgeschlagen“Transitions are free via the status selection field; the stock movement follows the request, with no copy-back.Origin
Section titled “Origin”| Origin | Marker | Behavior |
|---|---|---|
| Manual (tab „Beschaffung“) | without component | Free choice of the good variant |
| Component (engineering) | technical_structure_good_id set |
Quantity and type prefilled; appears on the component and on the good usage |
| Optimizer | optimization_run_id set (system) |
When a run is applied, one open purchase request is created per proposed order; on the next apply, still-open Optimizer requests are replaced, user requests never |
Rules & automation
Section titled “Rules & automation”- Purchase request: planned material cost item (net price × quantity, date = due on, otherwise earliest on, otherwise creation) which ends once a linked purchase is ordered or delivered. Actual costs and goods receipt are booked by the purchase.
- Stock request: goods issue; while „Offen“ planned costs, on „Erledigt“ one-time actual costs „Materialkosten aus Lagerentnahme“ (material costs from stock withdrawal).
- The status of the stock movement follows the request (Offen → pending, Erledigt → fulfilled, Fehlgeschlagen → cancelled); there is no copy-back from stock onto the request.
- Without a project no cost booking, but a stock movement.
- Details: Procurement, Material costs.
Number of procurement requests, purchase volume, open purchases – see Procurement.