H2R 606 · PRODUCTION SUPPORT
How do you support Hire to Retire when an employee lifecycle event goes wrong?
Restore a trustworthy employee state by tracing identity, employment, effective-dated change, approval, downstream execution, and evidence. The visible symptom may be in payroll, Finance, access, or an integrated system; the first unreliable record may be earlier in the lifecycle.
H2R EVENT CHAIN
Follow the employee event through every dependent result
People and employment are not the same object, and an approved event does not automatically prove downstream completion. Trace the change across the systems that use it.
- 01Workforce needNeed
- 02Person & employmentIdentity
- 03Effective-dated assignmentState
- 04Time & pay inputsInputs
- 05PayrollCalculation
- 06Finance, access & exitConsequences
SUPPORT OPERATING LOOP
Protect the employee record before correcting the symptom
Establish the people impact
Identify the person, employment, event, effective date, country, affected system, payroll period, access or privacy impact, and a reproducible example. Escalate sensitive access or payment risk immediately.
Find the first unreliable state
Follow source event → approval → effective-dated record → integration → target state → payroll, Finance, access, or exit evidence. Record where the intended result was last known to be correct.
Choose the cause family
Separate identity, employment or job data, effective dating, workflow, foundation object, integration, permission, time, payroll input, payroll calculation, and downstream posting.
Correct at the owning layer
Correct the authorized event, effective-dated record, owning object, integration, payroll input, or permission—not just the downstream display. Use a controlled payroll correction or rerun only when justified.
Verify as of the right date
Confirm person and employment status, organizational assignment, manager, cost center, target-system result, payroll, Finance, and access at the applicable effective date and period.
Make recurrence visible
Capture the symptom, cause, correction, validation, and control improvement. Turn repeat defects into data validation, monitoring, integration alerting, cut-off controls, role review, or regression tests.
FIRST H2R DECISION
Decide whether the issue is state, date, or hand-off
Do not treat a visible target-system value as the authoritative record. Establish the owner, effective date, and evidence that proves the intended successor was created and consumed.
A person identity can be correct while an employment, user, payroll, or local record is missing or wrong. Diagnose the object that owns the result.
An approved event is evidence of intent; the effective-dated successor record and its downstream result prove execution.
A correct source change can fail in selection, mapping, identity matching, timing, or target processing. Correct the first broken hand-off.
YOUR THREE-ROUTE TRIAGE
Start each downstream incident on its actual route
Use the H2R 202 landscape for the full data contract. In support, establish the source record, effective date, route status, and target evidence before choosing a correction.
EC → BTP → ERP HCM / PA30
Check: employee key, effective date, BTP flow or ECPAO/BIB status, and resulting PA master data. PA30 confirms the result; it is not the middleware correction point.
EC → IDM/GRC → target roles
Check: identity match, eligibility, governance or risk decision, provisioning status, and the roles actually present in the receiving system.
EC → Microsoft Entra → Outlook
Check: employee and manager scope, identity mapping, Entra manager relationship, and directory propagation. Correct EC or Entra—not Outlook directly.
SUPPORT OPERATING LOOP
Classify the symptom before changing the record
Use the smallest path that can locate the first unreliable state. Capture business impact and evidence, correct safely, prove the end-to-end result, then record the prevention action.
Data
Symptoms: missing required field, wrong worker detail, incorrect date, incomplete external-worker record.
Check: Person → Employment → Job Information → Position → effective-dated record.
Structure
Symptoms: wrong manager, reporting line, Position, organisation, or cost centre.
Check: Position → incumbent → manager → organisational assignment.
Authority
Symptoms: unavailable action, missing button, cannot see, maintain, or approve.
Check: RBP role → permission → target population.
Workflow
Symptoms: wrong approver, stuck request, missing approval, failed delegation.
Check: business event → workflow → approver determination → delegation → status.
Integration
Symptoms: correct in SuccessFactors, wrong in a downstream system; missing account, payroll data, or hierarchy.
Check: source → execution → mapping → authentication or connectivity → target processing.
H2R DIAGNOSTIC PLAYBOOKS
Follow the path that matches the employee-lifecycle symptom
Each case begins with the business event and the record that should prove its result. Investigate in Admin Center, Manage Data, Position Org Chart, RBP, workflow administration, scheduled jobs, or Integration Center according to the owning layer.
01 · New hire did not become active
Trace: Position or requisition → candidate → offer → person match → employment → hire and job information → user and payroll identity. Check that the hire is effective and all required creation steps completed.
02 · Employee data looks wrong
Trace: Displayed value → owning person, employment, job, compensation, or foundation object → effective date → event. Correct the owner, not the screen that merely consumes it.
03 · Transfer or promotion did not take effect
Trace: Event and reason → workflow → effective date → job information → position and organization → replication. Confirm the approved successor record exists on the intended date.
04 · Wrong manager, department, or cost center
Trace: Employee → job information → position or foundation object → effective date. Decide whether the employee assignment or its referenced organizational object is wrong.
05 · Correct HR change did not reach another system
Trace: Source record → effective date → integration selection → identifier and mapping → target processing. Separate a source-data issue from a failed or delayed hand-off.
06 · Employee cannot access a system
Trace: Employment status → platform user → activation → role assignment → target population → identity integration. Check timing and whether access is an intended eligibility control.
07 · The wrong employees can see HR data
Trace: User → role → permission → target population → field or object → effective date. Treat this as a sensitive access incident and contain exposure before broad changes.
08 · Time or absence did not reach payroll
Trace: Time record → approval → effective or pay period → valuation → wage or pay type → payroll input. Check cut-off, eligibility, and interface status.
09 · Payroll result is wrong
Trace: Employee master data → compensation, time, absence, and other inputs → payroll calculation → result. Separate wrong input from a correct calculation using the wrong rule.
10 · Payroll is correct but Finance posting is wrong
Trace: Payroll result → posting mapping → cost assignment → Finance document. Keep payroll correction separate from the downstream accounting determination.
11 · Terminated employee still has access
Trace: Termination event → effective date → employment and user status → identity integration → application access. Contain access first, then prove removal across targets.
12 · Final pay or obligations remain open
Trace: Termination → final time and leave → final payroll → benefits or deductions → payment → Finance, assets, and access. Closure is complete only when all obligations have evidence.
13 · Retroactive change produced an unexpected result
Trace: Historic event → effective date → earlier payroll result → retroactive calculation → difference → payment and Finance impact. Explain the period affected before correcting the historical record.
RECURRING SUCCESSFACTORS SYMPTOMS
Use an owning-object path for common live failures
Contractor extension fails
Trace: contractor data → required fields → administrator or manager authority → end date and work assignment → workflow → downstream access.
Workflow went to the wrong approver
Trace: business event → workflow rule → manager or Position → approver → delegation. Correct the determination source, not only the active request.
Onboarding task is missing
Trace: hire event → applicable onboarding process → task → responsible user → status.
Performance form is unavailable
Trace: employee population → form or cycle → route and status → permission → effective cycle dates.
Integration cannot connect
Trace: integration job → authentication → certificate → endpoint or network → target availability.
H2R SUPPORT MOMENT
A transfer is approved, but payroll charges the old cost center
Do not begin by changing the Finance posting. Confirm the event, approval, effective date, and job-information successor; then trace the payroll period, integration timing, cost assignment, and any retroactive result. Correct the first broken record or hand-off and prove the employee's assignment and posting across the affected periods.
- Preserve the source event, successor record, integration status, payroll result, and posting evidence before changing anything.
- Keep HR correction, payroll correction, and Finance correction distinct but connected.
- Verify both the effective date and the payroll period; they may not be the same.
Use 101 for lifecycle language, 202 for employee data and operations controls, 303 for cross-system execution, 404 for solution design, and 505 for implementation context.