Skip to Content
Product Information

Streamlining the Hire-to-Retire Process with SAP One Domain Model

Welcome to this blog post which explains the streamlining the Hire-to-Retire process with SAP One Domain Model.

SAP is introducing a new aligned domain model – The SAP One Domain Model which will be delivered to all customers.

Before diving into the details, let us first understand the background of the Hire-to-Retire Process and what were its challenges in the existing data model.

What is Recruit-to-Retire?

Recruit-to-Retire is the overarching process which was previously known as the Total Workforce Management capturing the entire end to end processes of an employee or a contingent worker. 

Recruit-to-Retire spans across several phases enabling the end to end experience of planning , staffing and managing employees.
Recruit-to-Retire is divided into three sub-processes:
  1. Hire-to-Retire
  2. Travel to Reimburse
  3. External Workforce

For this blog, we shall focus on the Hire-to-Retire process on the context of Recruit-to-Retire.

What is Hire-to-retire (H2R)?

H2R is the SAP SuccessFactors Employee Central Integration to the SAP S/4HANA Cloud which offers you predefined content for data integration to enable end-to-end business processes across your core Cloud HR – SAP SuccessFactors Employee Central – and SAP S/4HANA Cloud.

The integration between SAP S/4HANA Cloud and SAP SuccessFactors Employee Central supports transfer of employee data (including contingent workers) and financial master data (cost centers). It includes basic data, such as employee name and ID, and contact details, such as e-mail, and telephone information.

The most important thing in H2R is the maintenance of the Master Data. In the traditional process we are replicating the Master data between SAP S/4HANA Cloud and SAP SuccessFactors Employee Central but the data models were not aligned between them. 

In order to overcome this, we have come up with the new approach – One Aligned, common, people data model.

H2R and master data integration with SAP One Domain Model

All SAP LOBs have aligned on one data model for people and cost center data across all SAP business applications, enabling consistent and semantically understood data. This ensures easy maintenance as continuous remapping is not required.

Benefits of the new SAP One Domain Model based workforce data structure :

  • Prepare switch to new business partner model which enables concurrent employment / global assignments / international transfer.
  • Prepare enhanced employment-based processed like improved payment information handling/bank transfer, private address.
  • TCO reduction for customers due to minimal configuration.
  • The new workforce data structure simplifies the migration to the target architecture.

This target architecture introduces additionally the SAP Master Data Integration, the new product to distribute the master data across cloud suite.

The master data owner is the SAP SuccessFactors Employee Central in most cases and there are multiple consumers like SAP S/4HANA Cloud, SAP Concur, SAP Fieldglass and also the 3rd party applications.

This simplifies the integration effort substantially.

One central master data integration service enables 1:n integration which is:

  • Fast – efficient, centralized distribution.
  • Efficient – standardized, out-of-the-box, reusable.
  • Compliant – consistent, scalable, purpose-driven master data replication.

What Does it mean for our Customers?

All existing SAP S/4HANA Cloud customers are migrated to the workforce object based on SAP One Domain Model.
Throughout our 40+ years of serving customers, we have been propelled forward to solve complex business challenges by asking the question, “Is there a better way?”
SAP is introducing a new aligned domain model – SAP One Domain Modelwhich will be delivered to all customers. As part of this transformation, SAP will deliver an improved employee data model with SAP One Domain Model.
For customers using the “Import Employees” app, the employee master is currently based on a legacy domain model.As part of the journey to becoming an Intelligent Enterprise and using our Innovation Roadmap, SAP S/4HANA Cloud customers will be migrated to the new workforce domain model for employees during H1/ 2021.
SAP will schedule the migration to take place over two scheduled migration windows. Typically, test or quality instances will be migrated during the first migration window, with production instances migrated over the following two weeks. Any additional provisioned instances, such as customer sandbox or partner sales demo type, will be migrated separately. This should not result in any disruptive impact to the quality or production environment.
The migration for your system is currently scheduled to be performed between the months of April and July 2021.

The migration activity itself is completely automated; however, SAP does recommend performing basic testing after the migration to the new data model.For further details, please refer to SAP Note 2990013: Rollout of the Steps Involved in Worker Migration.

What changes can our SAP S/4HANA Cloud customers expect?

Please see the detailed demo with voice over explanation about the new search models after Migration in Enterprise Search :

What are the next steps for our SAP S/4HANA Cloud customers?

After the migration is complete, the end users need to use the Employment-Workforce Search model instead of the Employees Search Model that was used prior to the migration.

Post migration, the old ‘Employees’ search model will not yield any search results, There will be a notification issued to the authorized user informing about this change, for more information please refer to the video in the KBA 3046025 – HCM Carveout/Hire-to-Retire: Employee search does not return any values – SAP ONE Support Launchpad.

Further read

Please refer to the following blogs and SAP note for more details:

  • HR business process of Hire to Retire in SAP’s Integrated Intelligent Enterprise just got a triple shot of espresso! (Link)
  • SAP Reimagines HR Business Process of Recruit to Retire for its Intelligent Enterprise Suite (Link)
  • SAP Note Rollout of the steps involved in Worker Migration 2990013 (Link)
  • SAP Integration Strategy paper (Link)

 

Do you still have Questions?

Please contact your assigned Customer Engagement Executive, Customer Success Manager or your SAP contact for any queries and also write to us via an incident in your BCP system under CA-WFD-INT.

/
3 Comments
You must be Logged on to comment or reply to a post.
  • Hello,

    Thanks for the blog. Somehow the demo link/video didn't work for me and it may have already answered my questions but in case it doesn't, can you please provide your inputs:

    1. What is the migration roadmap for S/4HANA on-premise based customers?
    2. One Domain model make sense from an overall vision perspective but the customers are still setting up CPI between SuccessFactors and S/4, Point to Point between SF EC and ECP etc. What would be the business case and motivation for such customers to move away from these current setups?

    Thanks,

    Prateek

    • Hello Prateek,

       

      thanks a lot for your interest in Hire-to-Retire and these very important questions.

      1. For the foreseeable future S4HANA on-premise will still utilize an underlying HCM. Hence customers are free to choose between the already well known integrations of PA_SE_IN addon, ALE inbound or the new integration via SAP Master Data Integration.
      2. As long as we collectively worry about integrations between two applications the benefit of these developments is indeed not very convincing yet. The real benefit comes by looking at an entire suite of applications, consisting of multiple providers and consumers.
        If we take the example of workforce data a customer could have Employee Central for internal employees and Fieldglass for externals, while the number of consuming applications rises constantly. Currently it is SAP S4HANA Cloud. But we are building Consumption by Identity Services, Concur and several applications that are getting build natively on BTP. Having the data already in MDI simplifies the integration of these services substantially as it is the same interface for all services.

       

      Best regards,

      Samir

  • This is an excellent and well-written description of the challenges the One Domain Model is supposed to solve, the advantages of the new approach, and what to expect and when. I really enjoyed reading it.