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

Lesson 2 of 6

Packaged scenarios and Cloud Integration

10 min

Listen to this lesson

0:00 / 6:51

SAP delivers packaged integrations between Employee Central and SAP S/4HANA (on premise and private cloud) or SAP ERP HCM. They run on SAP Cloud Integration in SAP Integration Suite, using SAP's prebuilt integration flows; SAP Press notes they are only available on Cloud Integration, not on third-party middleware. On the S/4HANA side, the integration is configured in the Business Integration Builder (BIB) under the IMG path Personnel Management > Integration with SuccessFactors Employee Central > Business Integration Builder.

ScenarioDirectionTrigger and technologyLands in
Employee master data and org assignmentsEC → S/4HANAQuery program ECPAO_EE_ORG_REPL_QUERY in S/4HANA; middleware reads EC's Compound Employee API; inbound web servicePA infotypes; org assignments via a staging area to OM
Organizational objectsEC → S/4HANAQuery program RH_SFIOM_ORG_OBJ_REPL_QUERY; middleware reads EC OData APIOM infotypes (org units, positions, relationships)
Cost centersS/4HANA → ECReport ODTF_REPL_CC with IDocs (often with RBDMIDOC) or ODTF_REPL_CC_CSV for filesEC cost center foundation objects
Employee as business partnerWithin S/4HANASynchronization report /SHCM/RH_SYNC_BUPA_FROM_EMPLBusiness partner with Employee role (and supplier role where used)

The packaged flows and their triggers, following SAP Press and SAP documentation.

How a replication run works

  1. The query program in S/4HANA reads the BIB settings and sends a query through Cloud Integration; the query is logged in query tables (for example SFIOM_QRY_ADM holds query status per object type).
  2. Cloud Integration calls Employee Central: the Compound Employee API for employee data, the OData API for org objects, using the configured filters and the last successful run time for deltas.
  3. Cloud Integration transforms the data and calls the S/4HANA inbound web service.
  4. S/4HANA processes the data through BIB mappings: employee data into PA infotypes, org assignments into a staging area and then OM infotypes.
  5. S/4HANA sends a confirmation back through Cloud Integration to EC's Data Replication Monitor, where HR sees success or errors per employee.
One employee replication run: pulled from EC by a scheduled query in S/4HANA, confirmed back to the Data Replication Monitor.
The Sign-Off Table · thesignofftable.com/academy/sap-int-303

The Cloud Integration side

Theo's team deploys SAP's integration package for Employee Central integration with SAP ERP or SAP S/4HANA from the SAP Business Accelerator Hub into Contoso's Integration Suite tenants (CMC_DEV, CMC_TEST, CMC_PROD), and configures the externalized parameters: EC API endpoint and credentials, S/4HANA endpoints through the Cloud Connector, and filters. The flows are SAP standard content; Contoso changes configuration, not the flows themselves, so SAP updates can be applied. Each tenant pairs with one EC instance and one S/4HANA system: the EC test instance with CMQ client 100, EC production with CMP.

Employee Central instanceTest instance or production instance; APIs and Data Replication Monitor
Integration Suite tenantCMC_TEST or CMC_PROD with SAP's packaged flows, configured, not modified
Cloud ConnectorSecure tunnel from BTP to the S/4HANA system
S/4HANA systemCMQ client 100 or CMP; BIB, query jobs, inbound services, logs
Each environment is a full stack; test and production stacks must never cross.
The Sign-Off Table · thesignofftable.com/academy/sap-int-303
Private cloud / on premise (Contoso)S/4HANA Cloud Public Edition
Employee recordPA infotypes via BIB, then business partner syncWorkforce replication to a workforce person; check SAP's setup guide
ConfigurationBIB in the IMGCommunication arrangements and SAP-delivered settings
Org structureOM infotypes via org object replicationAs delivered for the cloud edition
Edition differences: this course follows Contoso's private cloud setup.
The Sign-Off Table · thesignofftable.com/academy/sap-int-303

Full loads and deltas

Replication normally runs in delta mode: each query asks EC for changes since the last successful run. The first load, and any reload after a change to the first full transmission start date (FTSD) moved into the past, needs a full load; SAP's learning material describes running the query programs with "Initiate Full Load" for that case. Full loads touch every employee in scope and are the moment many mapping gaps first appear, so Contoso ran its first full load in CMQ two weeks before the first test cycle and cleared all errors before testers started.

Full load versus delta: the stored last run time decides what the next delta picks up, which is why a failed run must be visible.
The Sign-Off Table · thesignofftable.com/academy/sap-int-303

What would you do?

After a refresh of CMQ from production, testers find that new hires entered in the EC test instance never arrive in CMQ. The Data Replication Monitor shows nothing. What is the most likely cause?

Key points
  • Packaged EC–S/4HANA integrations run on SAP Cloud Integration with SAP's standard flows.
  • S/4HANA pulls: query programs start replication; EC APIs provide the data.
  • Org assignments pass through a staging area into OM infotypes.
  • Monitor the query jobs themselves; silence is not success.

Check your understanding · not graded

Lesson check

  1. 1. Which program starts employee and org assignment replication in S/4HANA?

  2. 2. Which EC API supplies employee data for replication?

  3. 3. Which report replicates cost centers to EC through IDocs?

  4. 4. Where does HR see the result of each employee replication?