Master Data Administration — business view

1. Business Summary

Maintains the dictionaries the rest of the system depends on — currencies, taxes, languages, subject matters, brands, offices, departments, calendar templates with holidays, statuses for every transactional entity, payment methods, role definitions, and many more.

2. Business Value

Standardises operational vocabulary, drives validation, enables consistent reporting, and supports multi-brand and multi-currency operations.

3. Users / Stakeholders

Administrators, finance, operations leads.

4. Workflows

• Administrators create or update reference values via standardised admin screens.
• Calendar templates (per country) define working days, holidays, and shift times that drive resource availability and deadline calculations.
• Tax rules can be overridden per brand × job-type combination.
• Custom fields can be added and bound to specific entities.

5. Sub-Features

• Brands, Offices, Departments, Roles, Job Titles.
• Currencies, Taxes, Brand-Job-Tax overrides, over-production rules.
• Languages, Source/Target languages, Language Groups, Language Regions, Subject Matters.
• Calendar templates, days, holidays, times.
• Custom fields and entity bindings.
• Engineering / DTP / Graphics / Programming application catalogues.
• Checklists and checklist groups.
• Resource and Employee types, Vendor types.
• Many enumerations (statuses for every entity).

6. Business Rules

• Most transactional records reference master data, so deletion is unsafe and typically blocked by relationships.
• Brand-specific tax overrides enable correct multi-jurisdiction billing.
• Calendar templates control resource availability calculations.

7. Data Entities

~200 reference tables across the admin module.

8. Entry Points

• Standardised admin CRUD screens.

9. Inputs & Outputs

• Inputs: admin form data.
• Outputs: dropdowns, validation lookups, reporting dimensions.

10. Integrations

• SAP synchronizes selected master entities (taxes, currencies, branches).

11. Calculations / Logic

• Brand-Job-Tax drives tax group selection in invoice generation.
• Calendars feed resource availability and deadline computation.

12. Status Lifecycle

• Reference data; many enumerations within define states for transactional records.

13. Permissions

• Restricted to administrative roles.

14. Reports & KPIs

• Counts, integrity reports, orphan-record checks.

15. Risks & Observations

• Standardised CRUD provides minimal validation — broad change radius.
• Soft delete is rare; cascading deletes can orphan transactional records.
• Multi-brand parameters spread across many tables — coordinated maintenance required.

16. Source Code Evidence

• app/Plugin/admin/Controller/*, app/Plugin/admin/Model/* (≈200 controllers/models).