Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
monapiao
Associate
Associate

Introduction:


 

As part of the SAP Cloud Integration Strategy, SAP provides the SAP One Domain Model (ODM), a unified domain model for business objects distributed throughout different SAP applications. SAP One Domain Model focuses on the end-to-end Intelligent Enterprise business processes.

SAP One Domain Model helps establish out-of-the-box master data integration for SAP Intelligent Suite applications and lower the integration efforts for customers and partners.

 

SAP Master Data Integration (MDI) uses SAP One Data Model for out-of-the-box SAP integration and synchronize business objects across SAP Intelligent Suite. SAP Master Data Integration is a multi-tenant cloud service used to do master data distribution among SAP/Non-SAP product/services.


SAP Master Data Integration


 

SAP Master Data Integration provides a central data model for consumption of a set of Workforce data across SAP systems. Workforce data is maintained in SAP SuccessFactors Employee Central and uploaded to SAP Master Data Integration, from which SAP S/4HANA or other applications can retrieve it for their own purposes.

 

The SAP One Domain Model is released on the SAP API Business Hub and structured by domains. The following picture shows the graphical view of Workforce entity. In this view we can see all relations between Workforce entity to other entities and other domain types.


SAP One Domain Model


 

This blog post provides the steps required to integrate Workforce data from SAP SuccessFactors to SAP Master Data Integration.

 

Process:


 

Step1: Create SAP Master Data Integration service instance:

Login to Business Technology Platform (BTP) subaccount. Then navigate to Services > Service Marketplace and select Master Data Integration.

Select Create in the top-right corner.


Create MDI Instance


 

Enter basic info for your instance.

Service: SAP Master Data Integration

Plan: sap-integration

Runtime Environment: Cloud Foundry

Space: <Any option from the dropdown list. The chosen space is not relevant for MDI service>

Instance Name: <User-definable>

Click on Next.


MDI Instance Basic Info


 

Configure instance parameters for your instance.

application: sfsf

businessSystemId: <User-definable. An identifier for the client>

writePermissions:
[
{
"entityType": "sap.odm.workforce.WorkforcePerson"
}
]

Click on Create.


MDI Instance Parameter


 

Step2: Create a Service Key for service instance

Navigate to Services > Instances and Subscriptions and click Actions icon of the newly created service instance. Then click on Create Service Key.


Create Service Key


 

Provide a Service key name.

Service Key Name: <User-definable. It is recommended to indicate the date of creation in the service key name>


Service Key Name


 

Write down the uaa.clientid, uaa.clientsecret, uaa.url and the uri of service key which will be used later.


Service Key Details



Service Key Details


 

Step3: Configuration steps for integrating Workforce data from SF EC to SAP MDI

Login to SAP SuccessFactors Employee Central and go to the Security Center page.


SF Security Center


 

Maintain the OAuth configuration based on the Service key info of Master Data Integration service instance.

Configuration Name: <User-definable>

OAuth Type: OAuth 2.0

Grant Type: Client_Credentials

Client ID: <uaa.clientid of service key>

Client Secret: <uaa.clientsecret of service key>

Token URL: <uaa.url + /oauth/token>

Token Method: POST

Content-type: application/x-www-form-urlencoded


SF OAuth Configurations


 

Navigate to the Business Scenarios page. Find the scenario “Workforce Replication from EC to SAP Master Data Integration” and activate the scenario.


SF Business Scenarios



Confirmation Info


 

Click the pen icon on the right to start configuring the settings.

Integration Name: <User-definable>

Description: <User-definable>

Destination Page Size: <By default, the value of the Destination Page Size is set to 100>


Workforce Replication from EC to SAP Master Data Integration - Options


 

Configure filters and sorting. For initial load, no filters and sorting needed.


Workforce Replication from EC to SAP Master Data Integration - Filter and Sort


 

Configure destination settings.

Connection Name: <User-definable>

REST API URL: <uri value of service key>

Authentication Type: OAuth

OAuth Configuration: <Create in Security Center above>

HTTP Method: POST

Source Page Size: <400 by default>

Enable Server Side Pagination: <Make sure it’s not selected>

Enable diagnostics for Run Now: <Select if only for trouble-shooting purpose>


Workforce Replication from EC to SAP Master Data Integration - Destination Settings


 

Remain the setting by default.


Workforce Replication from EC to SAP Master Data Integration - Scheduling


 

Save and choose Run Now to start the integration. Refresh the latest runtime on the Refresh icon and click on it. Then you can access the integration center to monitor the integration.


Workforce Replication from EC to SAP Master Data Integration - Review and Run


 

With this we have completed the Workforce Integration from SAP SuccessFactors to SAP Master Data Integration service. Please feel free to leave the comments with your feedback and thoughts.

 
10 Comments
0 Kudos
Hi Mona,

Great overview of all the steps involved to get workforce data from SF EC to MDI on BTP.

If this helps establish out-of-the-box master data integration for SAP Intelligent Suite applications and lower the integration efforts for customers and partners, why is this entire setup not available automatically for every single SAP SF / HXM customer?  Why is this Workforce integration requiring this long list of steps if it's supposed to be out-of-the-box?

Should partners in the future connect to the MDI workforce model on BTP or directly to the existing OData APIs as done today?  What is the recommendation for partners going forward?

Best regards
SJ1111
Advisor
Advisor
0 Kudos
Hello,

I am no expert in MDI integration but I would like to mention the Cloud Integration Automation Service offers various predefined scenario workflows for the integration with MDI:


  • Intelligent Enterprise - Lead to Cash - Master Data



    • MDI Business Partner Integration with S/4HANA Cloud (MDI BP)



    • MDI Business Partner Integration with SAP Cloud for Customer(MDI C4C)





  • Intelligent Enterprise - Recruit to Retire - Hire to Retire



    • Integrating master data between EC and MDI




These are task based step-by-step configuration procedures that should make the integration for the available scenarios easier.

Please find more information here: help.sap.com/cias

Or here:

Best Regards

Stefan Jakobi

Product Management @ CLM
monapiao
Associate
Associate
0 Kudos
Hi Jason,

Sorry for the late reply.

Workforce data is maintained in Employee Central and uploaded (upstream integration) to SAP Master Data Integration, from which SAP S/4HANA or other applications can retrieve it for their own purposes (downstream integration).

The integrations are run with either an initial load or a delta load. Above steps are initial load. After successful completion of an initial load, we can schedule periodic Integration Center jobs (for example every 15 min) to replicate the data timely.

And as mentioned in blog, SAP Master Data Integration is a multi-tenant cloud service for master data integration, it provides a consistent view on master data across multiple systems. Master Data Integration use One Domain Model concept in SAP. It means multiple systems can edit the same data.

You can check the details in SAP Master Data Integration.

Thanks,

Mona
MartinW
Explorer
0 Kudos
Hi Mino,

thanks for sharing this integration scenario between SF and MDI. Actually I am wondering, how this workforce data on MDI can be consumed by other processes/systems.

E.g. it would be really helpful to have a standard integration scenario available in order create Business Users on S/4HANA. Do you know if this is already there? Or can you share any plans when this might be available.

Kind regards

Martin
monapiao
Associate
Associate
0 Kudos
Hi Martin,

Sorry for the late reply.

I have published a new blog which provides steps required to integrate Workforce data from SAP Master Data Integration to SAP S/4HANA Cloud as below. You can check it.

https://blogs.sap.com/2022/12/21/workforce-integration-from-master-data-integration-service-to-sap-s...

Thanks,

Mona
MartinW
Explorer
0 Kudos
Dear Mona,

I have just read part to of you blog. Thanks for providing this step-by-step description. What is still not clear to me: Which object is created on the S/4HANA side by this integration? Is it a Business Partner? Or is it an HR record? Or something else?

Kind regards

Martin
monapiao
Associate
Associate
Hi Martin,

It's workforce person data. You can also check below help portal for the workforce replication between MDI and S/4HANA Cloud.

https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/d9e300b90f024162b8f26737...

Thanks,

Mona
saanvid
Discoverer
0 Kudos
Hi Mona,

From S4 to SF replication , on consumer side other than configuring the instance parameters for the instance do we need to do any set up for newly connecting system in BTP cockpit?

 

 
0 Kudos
Hi mona1221

Thanks for such a detailed blog, could you please suggest it it possible to send some of the employee master data from S4 system to EC in success factor through MDI?

Source is S4

Target is EC in success factor

via: SAP MDI

Thanks,

Nalla B.
Romina
Explorer
0 Kudos

Hi mona1221,

 

thank's for you blogpost.

 

Unfortunatly we are getting different error messages during the implementation process.

 

We do not have a solution for this one, do you have any idea?

 

{"error":{"code":"InvalidRequest","message":"Invalid Request","details":[{"code":"InvalidRequest","message":"request entity too large"}]}}

 

Thank's in advance!

Romina