Reference & Data Model
Procurement request: planned costs and stock movement (good_procurement_request.*)
Depending on its type, a procurement request creates a continuously reconciled planned item, a stock movement and – for a completed stock withdrawal – an actual booking.
Trigger
Section titled “Trigger”A procurement request (good_procurement_request) changes type, status, quantity, due date, project or good. For type purchase additionally: a linked purchase changes its status or link.
Condition
Section titled “Condition”Request not deleted. For cost rows: project present, cost item „Materialkosten“ present, good has a „Stückpreis (Netto)“ (net unit price). Without a project only the stock movement is created.
What is created
Section titled “What is created”Type purchase (purchase, rule good_procurement_request.purchase):
- Planned item „Geplante Materialkosten aus Einkaufsaufforderung“ = net unit price of the good × quantity; date = „Fällig am“, otherwise „Frühstens am“, otherwise creation date. Source: „Einkaufsaufforderung ·
× “. - Only while the request is „Offen“ and no linked purchase has reached base class „Bestellt“ or „Geliefert“. Linking a purchase to the request ends the planning; the actual booking and the goods receipt then come from the purchase.
- This rule creates no goods receipt.
- „Erledigt“ (done) exists for stock requests only. „Fehlgeschlagen“ (
failed) counts nothing: the planned item is dropped.
Type stock (stock, rules .stock and .stock_withdrawal):
- Always a stock movement goods issue (
outbound) for the rounded-up quantity, date = creation date. - While „Offen“: planned item „Materialkosten aus Lagerentnahme“ = unit price × quantity.
- On „Erledigt“ (
done): a reconciled actual booking „Materialkosten aus Lagerentnahme“; the planned item is removed. Moving back to „Offen“ is not allowed. - On „Fehlgeschlagen“ (
failed): nothing — movement, planned item and actual booking are dropped.
Status mirroring request → stock movement: „Offen“ → pending, „Erledigt“ → fulfilled. The movement is system-generated and cannot be edited in the warehouse; there is no feedback from the warehouse to the request.
On change or rollback
Section titled “On change or rollback”Planned items and movements are continuously reconciled (quantity, price, date, status); deleting the request or „Fehlgeschlagen“ removes them, as well as the actual booking of the stock withdrawal. Open requests created by the optimizer are deleted when the optimization is rolled back; their planned items then disappear too (Apply optimizer).
Where visible
Section titled “Where visible”Projektansicht › Beschaffung › Beschaffungsaufforderungen (Guides › Procurement); cost item „Materialkosten“, section „Kosten“ (sources „Einkaufsaufforderung“ or „Lagerentnahme“).
Known limitations
Section titled “Known limitations”- Stock movements are not documented as a data type of their own in the interface (the warehouse is not part of this handbook); the optimizer counts only fulfilled (
fulfilled) movements as stock. - If the good has no net price, no cost row is created; existing planned items remain unchanged until the next change.
- Fractional quantities are rounded up for the movement and computed exactly for the costs.
See Procurement request · Material · Planned item.