H2R 202 · INTEGRATION LANDSCAPE
Where do employee changes go after EC?
Employee Central is the source of people and job-change intent. In this organisation, selected employee changes then reach ERP HCM, access governance, and Microsoft 365 through three distinct routes. Each route has its own identity key, timing, owner, and proof of completion.
ONE SOURCE, THREE OUTCOMES
Do not treat “sync completed” as one result
A transfer can be visible in EC while the PA master record, role assignment, or Outlook hierarchy is still old. The target result and its confirmation are part of the business change.
People, employment, and effective-dated job-change intent
BTP Integration Suite→ERP HCM / PA
Employee and organisational-assignment replicationIDM / GRC→Target-system roles
Identity lifecycle, governance, and provisioningMicrosoft Entra→Outlook hierarchy
Directory identity and manager relationshipTHE ORGANISATION'S THREE ROUTES
Know what each route is supposed to produce
These are the local integration routes, not a claim that every H2R landscape uses the same products or direction.
01 · EC → BTP → ERP HCM
Purpose: replicate employee and organisational assignment data for the ERP HCM personnel master. SAP Integration Suite carries the exchange; ECPAO/BIB processing creates or updates PA master data, which users inspect in PA30.
Prove: employee identifier and effective date match, replication status is successful, and the expected PA infotype data is present.
02 · EC → IDM/GRC → target-system roles
Purpose: use employment and assignment data to drive identity lifecycle, access eligibility, governance, and role provisioning. GRC governs the access decision; the provisioning path applies access in the receiving systems.
Prove: identity matched, request or rule outcome is approved, risk decision is recorded, and the intended roles are present only in the intended targets.
03 · EC → Microsoft Entra → Outlook hierarchy
Purpose: provision or update directory identity and reporting relationships used by Microsoft 365. The manager relationship in Entra is the evidence Outlook consumes for the organisation view.
Prove: worker is in scope, manager identity resolves, the Entra manager relationship is correct, and the hierarchy is visible after directory propagation.
DESIGN DISCIPLINE
Every route needs the same six answers
Different middleware and targets do not remove the need for a simple, owned data contract.
Identify whether person, employment, job information, position, manager, cost center, or termination status is the source for this route.
Document the source identifier, target key, matching rule, effective date, and payroll or access cut-off that determines when the result is valid.
Record who monitors the route, where success and error evidence lives, and who owns correction in EC, middleware, target, or access governance.
CHANGE-SCENARIO CHECKS
Test a complete lifecycle, not one successful hire
Create the identity
Prove a new employee reaches PA data, access eligibility, and the directory without duplicate identities or premature access.
Move assignment and manager
Prove the effective-dated organisation, cost center, manager, target roles, and Entra hierarchy change together at the intended time.
Remove access safely
Prove termination reaches the employment record, access deprovisioning, and directory state while preserving required payroll and Finance processing.
Explain a historical correction
Prove the impact of a backdated change on PA data, access, hierarchy, payroll, and any corrective Finance result before releasing it.
INTEGRATION DECISION
A manager transfer is correct in EC but still wrong in Outlook
Check the EC job-information successor and effective date first. Then prove that the employee and new manager are in the Entra provisioning scope, that identity matching succeeds, and that the Entra manager relationship changed. Do not change Outlook directly; it consumes the directory relationship.
- Keep the source event, effective-dated successor, route log, target record, and expected result together as one support case.
- Use a known employee and manager pair to test mapping and timing safely.
- Escalate access or privacy exposure ahead of ordinary data-display defects.
Use H2R 303 for lifecycle hand-offs, operating ownership, payroll controls, Finance evidence, and exception triage.