H2R 202 · DETERMINE
What determines an employee change in SAP SuccessFactors?
A visible employee change is the result of several independent controls. The action, effective date, event and event reason, business rules, workflow, permissions, object associations, synchronization, and integration must agree before the intended successor appears.
DETERMINATION STACK
Read from business event to downstream evidence
Each layer answers a different question. Skipping directly to a rule or field often hides an earlier eligibility or ownership problem.
What is changing, and when?
Hire, transfer, promotion, pay change, leave, return, termination, rehire, or data correction establishes intent and effective date.
Which event and reason apply?
Event and Event Reason classify the change, support reporting, influence status, and can participate in workflow or derivation.
Which rules, workflow, and permissions apply?
Business-rule scenario and trigger derive or validate values; workflow establishes approval; RBP controls action, field, history, and target population.
Which successor must update?
Position sync, HRIS Sync, Intelligent Services, API or payroll replication carry approved state to their governed consumers.
ONE RECORD TRAIL
Follow one transfer into its successor evidence
These records are connected, but they do not share one owner, date model, permission boundary, or completion status.
- 01AUTHORIZEApproved transfer request
Business purpose, owner, budget, country, timing and approval establish why work may exist.
- 02STRUCTUREEvent, Event Reason and effective date
Position, parent position, job, legal entity, department, location and cost centre establish where work belongs.
- 03ACTIVATEJob Information and workflow
The approved structure becomes employee assignment or recruiting demand with an effective date.
- 04PROVEHRIS Sync, integration and payroll evidence
History, approval, position-to-job result, requisition or incumbent record explain the outcome.
CONTROL ORDER
Inspect the layer that owns the result
- 01
Confirm the transaction and owning entity
Identify whether the user is changing Job Information, Compensation Information, Employment Details, Position, an MDF object, time data, or another entity.
Evidence Action, base object, record key, current history, effective date and requested operation: create, insert, correct, delete or view.
- 02
Confirm event classification and date logic
Check the event, Event Reason, employee status consequence, sequence, same-day change behavior, and whether the action belongs in history or correction.
Evidence Event Reason configuration, effective-dated record and source transaction.
- 03
Trace business-rule execution
Check the correct rule scenario, base object, trigger, condition, execution order, derived values, validation message, and rule log where available.
Evidence Rule assignment, version, context, input values and result.
- 04
Trace workflow and permission decisions
Determine who initiated the change, which workflow was derived, who may approve, and whether RBP permits the action and target population.
Evidence Workflow request, participants, status, permission role, group and target criteria.
- 05
Trace propagation and consumers
Check Position-to-Job synchronization, HRIS Sync timing, platform-user result, domain event, integration message, payroll cut-off and target-system key.
Evidence Admin Alert, job or sync log, replication status and target record.
DIAGNOSIS
Similar symptoms can come from different layers
Was it entered, derived, synchronized, or mapped?
Compare source value, rule result, Position propagation, effective date, field visibility, and target mapping.
Was the workflow eligible and derivable?
Check transaction type, rule condition, approver resolution, dynamic role, permission, and whether the save actually created a pending request.
Did approved state reach the consumer?
Check approval completion, HRIS Sync, event publication, integration job, replication monitor, payroll cut-off, error and retry ownership.
WORKED SCENARIO
A transfer saves but payroll retains the old cost centre
The Job Information transfer is approved for 1 July. First confirm the event and effective date, then the new department and cost centre on the dated record. Check workflow completion, HRIS Sync or replication timing, target payroll identity, payroll cut-off, and replication status. Do not change the Finance posting rule to compensate for a source or replication error.
- Owning entity and effective date are known
- Event Reason and workflow are explainable
- Rule and permission outcomes are traceable
- Target replication has an accountable status
Apply the determination stack across recruiting, employment, payroll, Finance, and exit hand-offs.