Meta Model POC

STARK MDM Config Builder

A clean restart of the MDM concept: model configuration first, generated user view second.

1Workspaces
11Entity types
58Attributes
8Relations

Demo Access

Greta Group Admin

GROUP_ADMIN | GROUP | Can configure group standard and approved BU overlays.

Config Workspace

Meta Model POC

A clean MDM proof of concept for building entity models, relations, views, and list layouts through configuration.

Reference system

Golden Record Roots

1 configured Location (Location)

Config Focus

Branch 4 attributes | 0 child relations

Model Overview

Build the model in focused steps

1 Golden Record roots across configured domains
4 Entity types configured
33 Attributes across the model
3 Relationships between entities
Design entities Design relationships Preview runtime
Open target state runtime model

Target Principle

Records are assembled by queries, not stored as JSON documents

Runtime records are stored as entity instances, attribute values, relation instances, and generated views in separate tables. The runtime UI then behaves like inriver-style composition: read the model, read the record graph, join values by attribute definitions, and render the configured view.

Record Assembly

How a user page is built

  1. Find the Golden Record root entity for the selected master data domain.
  2. Load the configured view sections, tabs, dialogs, fields, and relation blocks for that entity.
  3. Load the root record instance by global_id, entity_type_id, and tenant/BU context.
  4. Load attribute values from the generic value table using the attribute definitions.
  5. Load child records through relation instances and repeat the same value lookup recursively.
  6. Apply active BU overlays as additive attribute definitions without changing the group model.

Configuration layer

mdm_model_workspace, mdm_entity_type, mdm_attribute_definition, mdm_relation_definition, mdm_view_definition, mdm_view_section, and mdm_view_field define what can exist and how it should be shown.

Runtime data layer

mdm_record, mdm_record_value, and mdm_record_relation store the actual master data graph. A Supplier, Location, Facility, Address, or future entity is just an instance of an entity type with values attached by attribute definition.

Tenant and overlay layer

mdm_tenant, mdm_model_overlay, and mdm_overlay_attribute_definition allow approved BU-specific attribute additions while preserving the group model.

Governance and versioning layer

mdm_record_version, mdm_workflow_task, mdm_validation_result, and mdm_audit_event preserve draft/approved lifecycle, validation outcomes, approvals, and traceability.

-- Target-state runtime core, simplified
mdm_entity_type (
  id, workspace_id, entity_key, label,
  classification, master_data_domain_key, is_golden_record_root
)

mdm_attribute_definition (
  id, entity_type_id, attribute_key, label,
  data_type, reference_domain_key, required,
  unique_value, read_only, main_id, display_order
)

mdm_relation_definition (
  id, parent_entity_type_id, child_entity_type_id,
  relation_key, label, cardinality, display_mode_default, required
)

mdm_record (
  id, global_id, workspace_id, entity_type_id,
  tenant_id, status, lifecycle_state, created_at, updated_at
)

mdm_record_value (
  id, record_id, attribute_definition_id,
  value_text, value_number, value_boolean, value_date, value_reference_code,
  valid_from, valid_to
)

mdm_record_relation (
  id, relation_definition_id,
  parent_record_id, child_record_id,
  display_order, status
)

mdm_view_definition / mdm_view_section / mdm_view_field (
  define generated list pages, object pages, tabs, inline blocks, and dialogs
)

Model

Attributes and relations

Attribute Module

Fields owned by each entity

Select focus from the entity cards below. New attributes are created for the focused entity. Add attribute
Location 11 fields
Set focus
LocationID text | main ID | required | unique | read-only Edit
LocationSource text Edit
Location Name text Edit
Location Domain Type select | required Edit
Creation Date date | required Edit
Last Update Date date | required Edit
Latitude text Edit
Longitude text Edit
GLN number Edit
Country text | required Edit
Region text Edit
Facility 13 fields
Set focus
FacilityID text | main ID | required | unique | read-only Edit
Facility Source text | required Edit
Creation Date date | required Edit
Country select Edit
Facility Manager text Edit
Phone Number text Edit
Operational Hours text Edit
Operational Status select Edit
Facility Type select Edit
Capabilities multiselect Edit
BU Ownership text Edit
Firma Code text Edit
Pricing Region select Edit
Address 5 fields
Set focus
Address Line 1 text Edit
Address Line 2 text Edit
Postal Code text Edit
City text Edit
Country select Edit
Branch 4 fields
Focused
Branch Name text Edit
Branch Type select Edit
Branch Source text Edit
Operartional Status select Edit

Relation Module

Connections between entity types

Create/edit/delete relations and control how they render in generated views.
Add relation Connect parent and child entities in the model.
Location -> Facility 1..n | tab
Edit relation
Facility -> Address 1..n | inline
Edit relation
Facility -> Branch 1..n | inline
Edit relation

Governance

BU change requests and Group Admin overlays

Group standard is immutable BU needs never update the group model directly. They create requests and Group Admin creates centrally governed overlays.
BU owns the need, not the model Requests capture local business needs. Effective model changes only happen after Group Admin approval.
Only active overlays are available Governance only exposes overlay behavior that is applied in runtime: extend, disable, override, and specialize for attributes.
Submitted requests 0 requests

No BU model change requests yet.

Existing overlays 2 overlays
Add overlay
Davids Field STARK_SE | override | attribute | Base attribute: Location / GLN Created by Greta Group Admin
Edit overlay
Active behavior

Overrides Location / GLN for STARK_SE.

GLN
DK Facility name STARK_DK | extend | attribute | Base entity: Facility Created by Greta Group Admin Runtime placement: visible for STARK_DK on Facility under Location -> Facility (tab).
Edit overlay
BU extension attributes
DK Facility name dk_facility_name | text
Add BU attribute

Runtime Preview

Location object page

Location

Runtime source: Location attributes and direct child relations.