Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 6

Why HR-to-ERP integration breaks finance

9 min

Listen to this lesson

0:00 / 5:43

When a company runs SAP SuccessFactors Employee Central (EC) as its HR system and SAP S/4HANA as its ERP, employee data has to travel. Finance and logistics processes in S/4HANA need to know who works where: which cost center an employee belongs to, who their manager is, whether they are still employed, and how to reimburse their expenses. None of these processes are HR processes, so HR changes that arrive late, wrong or not at all show up as finance defects, often weeks later.

S/4HANA processEmployee data it relies onWhat goes wrong if replication fails
Travel and expense reimbursementEmployee as business partner with a supplier role, bank details, cost centerExpenses post to the old cost center; terminated employees still get paid
Time recording on orders and projectsPersonnel number, cost center, activity typeLabor costs land on the wrong cost center
Approvals (flexible workflow)Manager relationships from organizational dataA PO over 25,000 USD routes to someone who left
Maintenance and productionPersons responsible on work centers and ordersOrders assigned to people who changed jobs
Payroll posting (where payroll results post to S/4HANA)Cost center and org assignment per periodWages post to the wrong cost center or profit center

Where employee data from EC drives finance and logistics in S/4HANA.

Contoso's setup

Contoso runs SAP SuccessFactors Employee Central as the HR system of record for about 1,400 US employees (illustrative course data). Payroll is run by an external payroll service, and its results are posted to S/4HANA as journal entries by cost center. S/4HANA (CMP) needs an employee record for each person who records time on production and maintenance orders, submits travel expenses, approves purchasing documents, or is responsible for work centers. Kofi, Contoso's HRIS lead, owns EC; Theo's team owns the integration; Dan owns the finance outcome; Nadia reviews access to personal data.

The three packaged flows: employees and org objects from EC into S/4HANA, cost centers from S/4HANA back into EC, all through SAP Cloud Integration.
The Sign-Off Table · thesignofftable.com/academy/sap-int-303

Why the direction of cost centers matters

Cost centers are mastered in S/4HANA controlling (controlling area A000 at Contoso) and replicated to EC, where HR assigns employees to them in job information. The employee's cost center then travels back to S/4HANA with the employee record. So a cost center has a round trip: created by controlling in S/4HANA, sent to EC, chosen by HR, returned with the employee. A break anywhere in the loop puts costs in the wrong place.

The cost center round trip: created in S/4HANA, used in EC, returned with the employee. Illustrative new cost center for the example.
The Sign-Off Table · thesignofftable.com/academy/sap-int-303

Which employees S/4HANA needs

Not every employee needs a record in S/4HANA, and replicating everyone multiplies personal data in a second system. Contoso's scope (illustrative course data) covers employees who confirm time on production or maintenance orders at Detroit and Chicago, everyone who can submit travel expenses, approvers in purchasing workflows, and persons responsible on work centers such as WIND-10, ASSY-10 and TEST-10. In practice that is most of the workforce, but the filter is explicit and documented, and testers include one employee who should not replicate.

  1. Does the person confirm time on orders in S/4HANA?Yes → replicate · No → next question
  2. Can the person submit travel expenses or be reimbursed?Yes → replicate with a supplier role · No → next question
  3. Does the person approve documents in S/4HANA workflows?Yes → replicate with org relationships · No → do not replicate
The scope rule Contoso applies per employee group; each branch has a test employee.
The Sign-Off Table · thesignofftable.com/academy/sap-int-303

What would you do?

Dan reports that travel expenses for a Chicago engineer still post to Detroit Assembly (17101101) two weeks after the engineer moved to Chicago Assembly (17201101). EC shows the new cost center. Where should Priya start?

Key points
  • EC is the HR system of record; S/4HANA needs employee data for travel, time, approvals and postings.
  • Packaged flows: employees and org objects to S/4HANA, cost centers back to EC.
  • Cost centers make a round trip: S/4HANA to EC and back with the employee.
  • Most defects come from changes and corrections, not from new hires.

Check your understanding · not graded

Lesson check

  1. 1. Which system masters cost centers in Contoso's design?

  2. 2. Why can a PO over 25,000 USD route to the wrong approver?

  3. 3. What did Contoso's first reconciliation after go-live find?

  4. 4. Who owns the finance outcome of HR replication at Contoso?