202
MODULE TOPICBusiness decisions, SAP model, and operating evidence

H2R 202 · ACTIVATE

Onboarding turns an accepted offer into a ready worker and complete employment record.

Personal, job, bank, tax, benefit, equipment, and policy data are collected with appropriate access. Tasks coordinate HR, manager, IT, payroll, and the new hire.

HR MANAGER LENS

What must the business decide?

This capability becomes useful only when policy, ownership, employee experience, controls, measures, and exceptions are explicit.

Journey scope

Decide which pre-day-one, day-one, crossboarding, rehire, and offboarding activities belong in the coordinated journey.

Data minimisation

Collect only data required for employment, payroll, access, benefits, compliance, and employee service.

Readiness ownership

Assign HR, manager, IT, payroll, facilities, and new-hire tasks with clear due dates and escalation.

Employment hand-off

Define when the new hire becomes an Employee Central record and what evidence proves payroll and access readiness.

ACCOUNTABILITY

Who owns what?

New hire

Provides authorised personal and statutory data and completes acknowledgements.

Manager / responsible groups

Prepare role, team, equipment, access, schedule, and local welcome activities.

HR / payroll / IT

Validate employment data, payroll inputs, identity, permissions, and completion exceptions.

ONE RECORD TRAIL

Follow one decision into its successor evidence

These records are connected, but they do not share one owner, date model, permission boundary, or completion status.

  1. 01
    INITIATEAccepted candidate and process trigger

    Source identity, offer, start date and hiring context initiate the correct process.

  2. 02
    COLLECTOnboarding process, forms and tasks

    The new hire and responsible groups complete authorised data, documents and readiness work.

  3. 03
    VALIDATEPending hire and person match

    HR reviews mandatory entities, duplicate risk, effective dates and mapped values.

  4. 04
    ACTIVATEPerson, Employment, Job Information and user

    The employee record, payroll inputs, identity and access tasks become accountable outcomes.

CONSULTANT LENS

How SAP represents the capability

Recruiting or an external ATS initiates an Onboarding process. Data mapping connects requisition, application, offer, new-hire data collection and mandatory Employee Central entities. Rules, responsible groups, document templates, workflows, permissions, and integrations coordinate completion.

DIAGNOSTIC EVIDENCE

Diagnose using the owning record and hand-off

Separate an undesired business result from missing setup, failed execution, wrong effective date, insufficient permission, or broken integration.

SOURCE

Candidate, accepted offer, start date, legal entity, job or position, hiring manager and initiation status.

PROCESS

Onboarding process, participant, task owners, forms, signatures, documents, data-collection status and overdue work.

EMPLOYMENT

Pending-hire validation, person match, employee ID, Job Information, payroll data, user/access task and first-day readiness.

OPERATING VIEW

Exceptions and measures that deserve ownership

Common exceptions

  • Candidate data does not map to the intended EC field or picklist
  • A rehire is created as a duplicate person
  • Responsible group or manager cannot see the task
  • Employee exists but payroll, identity, equipment, or access is not ready

Useful measures

  • Day-one readiness by accountable workstream
  • Overdue and reassigned onboarding tasks
  • Data-mapping and pending-hire corrections
  • First-pay and access-ready success for new hires

WORKED SCENARIO

One decision carried into system evidence

An accepted candidate enters Onboarding with approved offer data. HR validates the person match and employment fields; payroll verifies required pay data; IT provisions role-based access; the manager completes workspace tasks. Readiness is measured by accountable outcomes, not task count alone.

  • What must be complete before day one and before first payroll?
  • Which data is collected once and which system owns it?
  • How are rehired, internal, contingent, and cross-country workers handled?
  • Who owns each failed mapping or overdue task?
Official SAP referencesSAP Help — Recruiting systems with Onboarding
CONTINUE THE PATHContinue to H2R 303

Connect this capability to lifecycle hand-offs, integration ownership, payroll, Finance, and exception triage.

Open practitioner map