Library · Travel & housing – master data in detail

DAT-090 · Process master data change during production

Brings changes to personal data during ongoing production into the system in a controlled way and triggers the check whether bookings already made…

Travel & housing · master data

Overview

Who it's for

Coordination, assistance, office

Trigger

Change notification via self-service, production office, or department head; field change to a record with at least one confirmed booking.

You get

Brings changes to personal data during ongoing production into the system in a controlled way and triggers the check whether bookings already made need to be adjusted as a result.

Status: Concept – not built yet

Brings changes to personal data during ongoing production into the system in a controlled way and triggers the check whether bookings already made need to be adjusted as a result.

Trigger: Change notification via self-service, production office, or department head; field change to a record with at least one confirmed booking.

1Receive thechange andclassify thefield type2Determine bookingrelevance againstthe field catalog3Ifbooking-relevant,trigger impactanalysis CHG-0204Log old and newvalue withtimestamp andauthor5If D4 or D5changes, recheckthe consentstatusTHK6Decide onimplementing orrejecting thechange if costsPL7Regeneratedownstreamartifacts(HSG-100,

Rule (automatable) Judgment (human decides)

Decision rules

  • R1 IF the changed field is not marked as booking-relevant THEN only log it, do not trigger a follow-up chain.
  • R2 IF the changed field is booking-relevant (starting location, name as per ID, contract period, employment type, special needs) THEN CHG-020 must be triggered.
  • R3 IF the change results in cancellation or rebooking costs AND these exceed {{FREIGABE_LIMIT_F1_EUR}} THEN obtain approval F2 before implementing it.
  • R4 IF the change arrives after the free cancellation period has expired THEN state the cost impact and inform the person that the change incurs costs before a decision is made.
  • R5 IF the employment type is changed THEN reset the billing path and mandatorily inform PBH, because per diem items already booked become invalid (ACC-120).
  • R6 IF a change is reported by a third person (not by the affected person themselves) THEN obtain confirmation from the affected person before it takes effect.

Common pitfalls

1. Change is communicated verbally at the work site and only corrected in the rooming list → ticket, transfer, and billing continue to run on the old data. 2. Name change after marriage is updated in the system, but the ticket already issued shows the old name → ticket unusable at the gate. 3. Starting location changes because the person moves privately, and nobody recalculates the distance → mileage allowance and overnight entitlement remain incorrect until the end of the project. 4. Change is implemented without stating the cost impact → cancellation costs hit the budget without approval and without allocation.

Impact H × Effort S → Do-first · HITL · RACI **R** THK · **A** PL · **C** PBH for billing relevance, DSB for D4/D5 · **I** GWL, 1RA · Manual effort: Estimate: 5 min per non-booking-relevant change, 20–60 min per booking-relevant change with rebooking

Request this workflow

Request this workflow See all workflows