Reference & Data Model
Material: Material category › Product › Article (good_type › good › good_variant)
The material catalog describes goods on three levels: the material category defines attributes, the product groups articles, the article is the orderable unit with price and stock.
Purpose
Section titled “Purpose”Engineering, procurement and warehouse work with the same articles (master data). The material category carries the specifications, the product the unit of measure, the article the price, stock parameters and specification values.
Where in the app
Section titled “Where in the app”Stammdaten › Material-Katalog (Master data › Material catalog) with the dialogs „Neue Materialkategorie“ (New material category), „Neues Produkt“ (New product), „Neuer Artikel“ (New article) and „Updaten“ (Update); detail views per level. See Guides › Material catalog and Guides › Build the material catalog.
Material category (good_type) e.g. „Kabel“└── Sub-material category (good_type) e.g. „Energiekabel“ ← inherits specifications └── Product (good) e.g. „NYM-J“ └── Article (good_variant) e.g. SKU „NYM-J 3×1,5 mm² 100 m“Fields
Section titled “Fields”Material category (good_type)
Section titled “Material category (good_type)”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Name („Materialkategorie-Name“) | name |
Text | yes | Designation | |
| Parent material category („Besitzt übergeordnete Kategorie“) | parent_id |
Reference | no | Parent category | from the tree on create |
| Description | description |
Text | no | Free text |
System: „Wirksame Spezifikationen“ (effective specifications), „Produkte“ (products), „Unter-Materialkategorien“ (sub-material categories), „Spezifikationsabdeckung“ (specification coverage).
Product (good)
Section titled “Product (good)”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Product name | name |
Text | yes | Designation | |
| Key | user_key |
Text | yes (DB) | Your own key | dialog does not enforce input |
| Material category | good_type_id |
Reference | no | Associated category | from the tree |
| Purchase required | purchase_required |
Yes/No | yes | Badge „Bestellpflichtig“ (order required) | purely informational |
| Active | active |
Yes/No | yes | Selectable in projects | |
| Unit quantity | base_amount |
Number | no | Base quantity per packaging/stock unit | displayed as „1“ when empty |
| Unit | base_unit |
Text | yes | Unit of the base quantity, e.g. pcs | |
| Description | description |
Text | no | Free text | |
| Tags | tags |
Text | – | Only shown in „Info“ | not editable |
System: „Gesamtbestand“ (total stock), „Artikel unter Minimum“ (articles below minimum), „Offene Bestellungen“ (open orders) with badges „bestellt“ (ordered) and „Bedarfsanfrage“ (demand request).
Article (good_variant)
Section titled “Article (good_variant)”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| SKU | sku |
Text | yes | Article number | search-weighted |
| Product | good_id |
Reference | yes | Parent product | from the tree |
| Status | active |
Selection | yes | „Aktiv“/„Inaktiv“ (Active/Inactive) | inactive articles are locked in selection lists |
| Stockable | stockable |
Yes/No | yes | Article can be kept in stock | |
| Stock tracking on („Bestandsverfolgung“) | stock_tracking_on |
Yes/No | yes | Stock management active | only such articles are planned as material by the Optimizer |
| Minimum / maximum / desired stock quantity | min_stock_quantity / max_stock_quantity / desired_stock_quantity |
Number | no | Min / max / target | bar and badge „Bestand kritisch“ (stock critical) |
| Procurement lead time (working days) | procurement_lead_time_days |
Number | no | Working days from order to goods receipt | empty = available immediately |
| Unit price (net) | net_unit_price |
Amount | no | Net price per unit | |
| Currency | currency |
Selection | no | Currency of the price | |
| Description | description |
Text | no | Free text |
System: „Aktuelle Lagermenge“ (current stock quantity: article receipts − article issues), „Gepflegte Spezifikationen“ (maintained specifications), „Offene Bestellungen“ (open orders), „Technische Daten“ (technical data).
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
| Material category → parent category | belongs to | no | – | reference cleared |
| Material category → specification category, technical specification | has many | – | – | deleted along |
| Material category → product | has many | – | – | reference cleared |
Material category ← component requirement (technical_structure_requirement) |
has many | – | – | reference cleared |
| Product → material category | belongs to | no | – | reference cleared |
| Product → article | has many | – | – | deleted along |
| Article → product | belongs to | yes | – | deleted along |
Article → specification value, stock (spec_value, stock) |
has many | – | – | deleted along |
| Article ← technical component, procurement request, purchase, stock movement | has many | – | – | blocked |
None of the three levels can be archived.
Rules & automation
Section titled “Rules & automation”- Delete lock: An article that is used in a technical structure, a procurement request, a purchase or a stock movement cannot be deleted. A product deletes its articles along with it, so it fails on the same lock.
- Price → costs: A procurement request creates a planned material cost value of unit price × quantity; a price change re-prices open planned values. An ordered or delivered purchase books actual material costs and keeps them current; later price changes update the booking (Material costs, Procurement).
- Stock tracking and procurement lead time → Optimizer: Only articles with „Lager-Tracking an“ (stock tracking on) take part in material planning: demand from tasks, stock from completed stock movements, open procurement requests and order proposals at origin + procurement lead time in working days (empty = 0). Articles without stock tracking are reported by the run as a notice and not planned (Optimizer commit).
- Purchase required is only shown as a badge; no rule reads the field.
- Master data character: Price, unit, stock parameters and specification values apply immediately in all projects, technical structures and procurements that reference the article. Moving a material category changes the inherited specifications of all articles below it.
Quantity (procurement request) = quantity × unit quantity; purchase volume and amount (net) from the unit price; material costs. See ch. 13 › Procurement.
See also
Section titled “See also”Specification · Technical component · Component requirement · Procurement request · Purchase