Skip to content

Reference & Data Model

Good usage (good_usage)

A good usage assigns a component or a node of the technical structure to a task and optionally the procurement request that delivers the material.

The good usage answers: Which material does this task consume, in what quantity, and where does it come from? It connects the work plan and engineering. (Transactional data)

Task › „Ressourceneinsatz“ (Resource usage) › goods cards (component with good, SKU, good type, quantity and base unit; or node with expandable requirements, sub-nodes and components). „Keine Güter eingesetzt“ (No goods used) when the list is empty. Create via the assignment „Neue Zuweisung für …“ (New assignment for …) from engineering (Guides › Engineering) or from the task. Selection field „Beschaffungsaufforderung zuordnen“ (Assign procurement request) with „Keine Beschaffungsaufforderung“ (No procurement request) or the component’s requests (kind · quantity · status · due date); once assigned, the request’s status, „Fällig am“ (due on) and „Frühstens am“ (earliest on) appear directly on the card.

Field Technical Type Required Meaning Notes
Quantity quantity Number yes Consumed quantity in the base unit of the good Default 1; prefilled on create from the component’s bill-of-materials quantity
Task task_id Reference yes Task of the usage
Component technical_structure_good_id Reference no Component of the technical structure Either component or node
Node technical_structure_node_id Reference no Node of the technical structure Link „Engineering“
Procurement request good_procurement_request_id Reference no Request that delivers this material Set automatically when the component has exactly one request
Related to Kind Required On archive On delete
Task belongs to yes archived along deleted along
Component belongs to no — reference cleared
Node belongs to no — reference cleared
Procurement request belongs to no — kept

Technical structure · Procurement request