Reference & Data Model
System-generated record (system_derived_record)
The system posts planned costs and cost events from other data types and logs the source for each; such rows are marked and not editable.
Purpose
Section titled “Purpose”system_derived_record is the server’s provenance register: it links a rule, the source row and the record generated from it. Exactly one record per (rule, source, key). The table is never transferred to the client; in the user interface it appears as the marker „Systemgeneriert“ (system-generated) and as provenance text on planned costs and cost events.
Where in the app
Section titled “Where in the app”Detail view of the cost item › section „Kosten“ (Costs), both lists:
- Badge „Systemgeneriert“ (grey) instead of „Manuell“ (blue) in the column „Bezeichnung“ and in the field „Erstellungsart“ (creation kind) of the dialogs.
- Instead of the description, the source is shown in two lines: kind (e.g. „Einkauf“, „Zeiterfassung“, „Ressourcenplanung“, „Risiko-Prävention“, „Erwartete Risikokosten“, „Lagerentnahme“, „Einkaufsaufforderung“) and detail (e.g. „3 × SKU-… (Titel)“, „Max Muster vom 12.03.2026“, „8 h Max Muster — Aufgabe“). Clicking the detail opens the source: purchase dialog, risk or opportunity dialog, otherwise an info view.
- System rows have no context menu, only a link icon. Their dialogs are read-only; for cost events, „Korrigieren“ (Correct) remains available because it only creates new rows.
Fields
Section titled “Fields”All columns are server-internal: rule_key (rule), source_id (source row), derived_key (key within the source), target_table (cost_occurrence, planned_cost, cost_item or stock movement), target_id (generated row). Only the information derived from them is visible on the record: creation kind, rule (rule_key) and source (source_id).
Rules that generate records
Section titled “Rules that generate records”Rule (rule_key) |
Source | Generates | Kind | Description of the record | Chapter 12 |
|---|---|---|---|---|---|
project.default_cost_items |
Project created | 7 cost items + budgets | once | – | Default cost items |
employee_usage.personal_cost |
Employee usage | Planned cost | synced | Geplante Personalkosten aus Ressourcenplanung | Planned personnel costs |
time_log.personal_cost |
Time log approved | Cost event | once | Personalkosten aus Zeiterfassung | Actual personnel costs |
good_purchase.material_cost |
Purchase in base class „Bestellt“ or „Geliefert“ | Cost event | synced | Materialkosten aus Einkauf | Material costs |
good_procurement_request.purchase |
Purchase request | Planned cost | synced | Geplante Materialkosten aus Einkaufsaufforderung | Procurement |
good_procurement_request.stock |
Stock request „offen“ | Planned cost (+ goods issue) | synced | Materialkosten aus Lagerentnahme | Procurement |
good_procurement_request.stock_withdrawal |
Stock request „erledigt“ | Cost event | once | Materialkosten aus Lagerentnahme | Procurement |
risk.expected_opex |
Active risk | Planned cost | synced | Erwartete Risikokosten | Risk costs |
risk.occurred_opex |
Risk occurred | Cost event | once | Risiko eingetreten | Risk costs |
risk_action.opex |
Measure of an occurred risk | Cost event | synced | Risiko-Präventions-/Reaktionsmaßnahme (System) | Risk costs |
chance_action.opex |
Measure of an occurred opportunity | Cost event | synced | Chancen-Präventions-/Reaktionsmaßnahme (System) | Risk costs |
Once (create-only): the record is created when the condition is met for the first time and is afterwards neither recalculated nor removed. Synced: on every relevant change of the source, the amount is recalculated; if the condition no longer holds (source deleted, risk inactive, measure discarded, request „fehlgeschlagen“ (failed)), the record is removed.
Rules & automation
Section titled “Rules & automation”- The rules run on the server via database change events (CDC) with a small delay; see Engine.
- Prerequisite of every cost rule: the project has a cost item of the target category (Materialkosten, Personalkosten, Sonst. betr. Aufw). If it is missing, the record is skipped and a warning is logged. For personnel costs an hourly rate is additionally required: „Stundensatz“ (hourly rate) of the project member, otherwise „Stundenkosten“ (hourly cost) of the employee.
- The server rejects every client change to system rows, as well as users setting the creation kind to „Systemgeneriert“.
- If the source can no longer be loaded (e.g. deleted), the list shows the stored description with the badge „Systemgeneriert“ instead of the provenance.