: Big things that happened at Game Developer Conference!
Introduction:
Hello Everyone..!
Recently I came across the S4Hana Public Cloud Implementation and SuccessFactors was part of this implementation as well. So we had an integration where we need to bring the employee data from SuccessFactors to S4Hana Public Cloud.
My initial thought process is to leverage the Integration Suite where we have the standard package with the name “SAP SuccessFactors Employee Central Integration with SAP S/4HANA Cloud: Employee Data“.
Then I came across the SAP Best Practice for S4Hana Cloud Public Edition article where its stated that “The standard way of integrating SAP S/4HANA Cloud Public Edition and SAP SuccessFactors Employee Central is via SAP Master Data Integration”.
So in this blog, I will illustrate all the steps involved in S4Hana Public Cloud, BTP, Master Data Orchestration/MDO and SuccessFactors. Let’s get started..!
Before we touch base on the configuration, Lets understand what is MDI and MDO.
In the simple words, MDI is a cloud based service in BTP designed to facilitate the data replication based on the SAP One Domain Model/ODM and Master data orchestration/MDO will be used to define the configuration to distribute the data among the involved systems.
A high-level overview of possible data flows using MDI
Configurations:
Lets look the configuration involved in system by system.
1. BTP 1.1:
Create the instance and service key for Master Data Integration.Login to BTP –> Open the Subaccount –> Services –> Service Marketplace –> Search for “Master Data Integration” in the search bar. –> Create.Service is “Master Data Integration”.Plan is “sap-integration”.Runtime is “Cloud Foundry”Space – Choose the cloud foundry space from dropdown.Instance name – Give the name for your instance then click on “Next”.Give the following parameters.application – sfsfbusinessSystemId – If its SF then give company ID. If its S4C, then give system ID.entityType under write permission – sap.odm.workforce.WorkforcePerson, then hit on create. Navigate to newly created instance and create the service key for it, the save it.Following parameters will be created.Create another key for S4C application with application “s4“Subscribe for Master Data Integration (Orchestration)Goto Service Marketplace –> search for “Master Data Integration (Orchestration)” –> Create.An app will be added under subscription.
2. SuccessFactors:
Set the “SAP Master Data Integration Configuration parameters” in SuccessFactors.Login to SuccessFactors –> Search for “Manage data” –> Search for “SAP Master Data Integration Configuration” under “Create new” section and add below parameter.Integration Object – Workforce PersonParametersSync IDs of Purged Workforce – If you want to replicate purged record to MDI then choose “yes”, if not “no”.Replicate Photo – If you want to replicate photo MDI then “yes”, if not “no”.Cutoff Date – This date will pull the records created or modified after this date are considered eligible for synchronization.
Enable the “Workforce Replication from EC to SAP Master Data Integration” scenario in SuccessFactors.Search for “Business scenario” in SuccessFactors search bar.Filter for the scenario “Workforce Replication from EC to SAP Master Data Integration” and activate is using the active toggle button and click on edit using pencil symbol.
Add the the uri you received from the 1st step of the BTP after creating the service key for sfsf business system.
Create the OAuth config for MDI in SuccessFactors under “Security center” with same service key details.Integration can be scheduled using belowRun the integration using “Run Now” option.
Once above job is completed, all the employee records will be replicated to MDI.
3. S4/Hana Public Cloud:
Prerequisite – Scope Item 4AF should be activated.
Create inbound communication system, create the communication user for inbound communication and assign the communication arrangement SAP_COM_0594 for the communication system.Login to S4 Hana Public Cloud system –> search for “Communication systems” –> Select the “Communication systems” app –> create new –> give the name as “ZSAP_COM_0594″(name could be anything, but we are following this naming convention for better understanding).Under “Technical Data” section choose “inbound only” radio button.
Create a new communication user if you don’t have already one, using “+” button in the “users for inbound communication section”. Then hit on save.
Search and open the “Communication Arrangement” S4 Hana Public Cloud –> new -> Search for communication arrangement “SAP_COM_0594” –> click on itChoose the communication system created early from the dropdown. Notdown the communication user credential and “Distribution administration” URL, This is required while creating destination in BTP. Then hit on save.Create outbound communication system, maintain the s4 service key details for authentication and assign the communication system to the communication arrangement SAP_COM_0659.Login to S4 Hana Public Cloud system –> search for “Communication systems” –> Select the “Communication systems” app –> create new –> give the name as “ZSAP_COM_0659″(name could be anything, but we are following this naming convention for better understanding).Under technical data add below informationhost – uri from s4 service key of BTP.port – 443Business system – MDIUnder “OAuth 2.0 Settings” section add below info from s4 service keyAuthorization Endpoint – uaa.url +/authorizeToken Endpoint – uaa.url +/oauth/token Under “Users for Outbound Communication” section, add below info.
Authentication Method – OAuth 2.0Client Authentication – BasicOAuth 2.0 Client ID – Value from clientid in the s4 service keyClient Secret – Value from client secret in the s4 service key, then hit on Save
Search and open the “Communication Arrangement” S4 Hana Public Cloud –> new -> Search for communication arrangement “SAP_COM_0659” –> click on itChoose the communication system created early from the dropdown i,e ZSAP_COM_0659. Add “/” in path and hit on save.
4. BTP1.2:
Create the destination for S4 Hana Public Cloud in BTP.Login to BTP –> Open the subaccount –> Connectivity –> Destination –> Create Destination. Give the below parameter and ping the destination. It should return 200OK response.Name: S4C System ID(Anything can be given here)Type: HTTPURL: Provide the service URL from the MDO Distribution Administration from communication arrangement SAP_COM_0594.Proxy Type: InternetAuthentication: Basic AuthenticationUser and Password: Use the communication user and password created during ZSAP_COM_0594 communication systemAdditional PropertiesMDOProvider: trueMDOConsumer: trueMDIInstanceId: The value of this should be the systemId from the S4 service key.MDOBusinessSystem: Give the businessSystemId from the MDI instance.
5. MDO/Masterdata Orchestration:
Create pull distribution model in MDO with MDI as provider and S4/Hana Public Cloud as consumer.Login to the Master Data Integration (Orchestration) app which we subscribed in the 2nd step of BTP1.1 –> Click on “Manage Distribution Model” Click on create –> add the meaning full name to model and description.Provider – MDI SAP Master Data IntegrationConsumer – Choose the BTP destination of S4/Hana Public Cloud that we created in BTP.Application Category – SAP S/4HANA Cloud (S/4)Business Object Type – Workforce Person (sap.odm.workforce.WorkforcePerson)API – MDI_LOG_WORKFORCE_PERSONMode – PullSave and activate the distribution model.
After running the business scenario in SuccessFactors, You can use be Initial Replication to replicate all employees from MDI to S4C and Delta replication only for the changes since the last run of the integration.
Monitoring in S4 Hana Public Cloud:
You could see the replicated records in S4C using the “Message Dashboard” app under the /WFS namespace.
And you could see the replicated worker/employee details under “Manage Workforce” app.
NOTE: As per the new BP Model in S4/Hana Public Cloud, for one employee/worker 2 BPs will be created. One for employee and another one for employment.
Key things to consider:
One subaccount could have only one MDI instance, So make the instance strategy accordingly.You can delete the MDI instance only if the field enableTenantDeletion set to true.Before deleting the MDI instance, make sure you deactivated all the distribution model in MDO.By standard all employees should have unique email in SuccessFactors, If not it will throw error in S4C while replication.
Conclusion:
The integration of SuccessFactors with S4HANA Public Cloud through Master Data Integration provides a seamless and robust point to point solution for workforce replication, enabling organizations to streamline their HR processes while ensuring data consistency and accuracy across platforms.
Whats next:
In this blog we have seen all the steps involved in BTP, SuccessFactors, MDO and S4/Hana Public Cloud. In the next blog I will try to explain how the CB user will get created automatically and how SuccessFactors users could access the S4/Hana Public Cloud.
And in the subsequent blog we will discuss about the “Cost Center Replication from SAP Master Data Integration to EC“.
Thanks for taking time to read this..!
Introduction:Hello Everyone..!Recently I came across the S4Hana Public Cloud Implementation and SuccessFactors was part of this implementation as well. So we had an integration where we need to bring the employee data from SuccessFactors to S4Hana Public Cloud.My initial thought process is to leverage the Integration Suite where we have the standard package with the name “SAP SuccessFactors Employee Central Integration with SAP S/4HANA Cloud: Employee Data”.Then I came across the SAP Best Practice for S4Hana Cloud Public Edition article where its stated that “The standard way of integrating SAP S/4HANA Cloud Public Edition and SAP SuccessFactors Employee Central is via SAP Master Data Integration”.So in this blog, I will illustrate all the steps involved in S4Hana Public Cloud, BTP, Master Data Orchestration/MDO and SuccessFactors. Let’s get started..!Before we touch base on the configuration, Lets understand what is MDI and MDO.In the simple words, MDI is a cloud based service in BTP designed to facilitate the data replication based on the SAP One Domain Model/ODM and Master data orchestration/MDO will be used to define the configuration to distribute the data among the involved systems.A high-level overview of possible data flows using MDIConfigurations:Lets look the configuration involved in system by system.1. BTP 1.1:Create the instance and service key for Master Data Integration.Login to BTP –> Open the Subaccount –> Services –> Service Marketplace –> Search for “Master Data Integration” in the search bar. –> Create.Service is “Master Data Integration”.Plan is “sap-integration”.Runtime is “Cloud Foundry”Space – Choose the cloud foundry space from dropdown.Instance name – Give the name for your instance then click on “Next”.Give the following parameters.application – sfsfbusinessSystemId – If its SF then give company ID. If its S4C, then give system ID.entityType under write permission – sap.odm.workforce.WorkforcePerson, then hit on create. Navigate to newly created instance and create the service key for it, the save it.Following parameters will be created.Create another key for S4C application with application “s4″Subscribe for Master Data Integration (Orchestration)Goto Service Marketplace –> search for “Master Data Integration (Orchestration)” –> Create.An app will be added under subscription.2. SuccessFactors:Set the “SAP Master Data Integration Configuration parameters” in SuccessFactors.Login to SuccessFactors –> Search for “Manage data” –> Search for “SAP Master Data Integration Configuration” under “Create new” section and add below parameter.Integration Object – Workforce PersonParametersSync IDs of Purged Workforce – If you want to replicate purged record to MDI then choose “yes”, if not “no”.Replicate Photo – If you want to replicate photo MDI then “yes”, if not “no”.Cutoff Date – This date will pull the records created or modified after this date are considered eligible for synchronization. Enable the “Workforce Replication from EC to SAP Master Data Integration” scenario in SuccessFactors.Search for “Business scenario” in SuccessFactors search bar.Filter for the scenario “Workforce Replication from EC to SAP Master Data Integration” and activate is using the active toggle button and click on edit using pencil symbol.Add the the uri you received from the 1st step of the BTP after creating the service key for sfsf business system.Create the OAuth config for MDI in SuccessFactors under “Security center” with same service key details.Integration can be scheduled using belowRun the integration using “Run Now” option. Once above job is completed, all the employee records will be replicated to MDI.3. S4/Hana Public Cloud:Prerequisite – Scope Item 4AF should be activated.Create inbound communication system, create the communication user for inbound communication and assign the communication arrangement SAP_COM_0594 for the communication system.Login to S4 Hana Public Cloud system –> search for “Communication systems” –> Select the “Communication systems” app –> create new –> give the name as “ZSAP_COM_0594″(name could be anything, but we are following this naming convention for better understanding).Under “Technical Data” section choose “inbound only” radio button. Create a new communication user if you don’t have already one, using “+” button in the “users for inbound communication section”. Then hit on save. Search and open the “Communication Arrangement” S4 Hana Public Cloud –> new -> Search for communication arrangement “SAP_COM_0594” –> click on itChoose the communication system created early from the dropdown. Notdown the communication user credential and “Distribution administration” URL, This is required while creating destination in BTP. Then hit on save.Create outbound communication system, maintain the s4 service key details for authentication and assign the communication system to the communication arrangement SAP_COM_0659.Login to S4 Hana Public Cloud system –> search for “Communication systems” –> Select the “Communication systems” app –> create new –> give the name as “ZSAP_COM_0659″(name could be anything, but we are following this naming convention for better understanding).Under technical data add below informationhost – uri from s4 service key of BTP.port – 443Business system – MDIUnder “OAuth 2.0 Settings” section add below info from s4 service keyAuthorization Endpoint – uaa.url +/authorizeToken Endpoint – uaa.url +/oauth/token Under “Users for Outbound Communication” section, add below info.Authentication Method – OAuth 2.0Client Authentication – BasicOAuth 2.0 Client ID – Value from clientid in the s4 service keyClient Secret – Value from client secret in the s4 service key, then hit on Save Search and open the “Communication Arrangement” S4 Hana Public Cloud –> new -> Search for communication arrangement “SAP_COM_0659” –> click on itChoose the communication system created early from the dropdown i,e ZSAP_COM_0659. Add “/” in path and hit on save.4. BTP1.2:Create the destination for S4 Hana Public Cloud in BTP.Login to BTP –> Open the subaccount –> Connectivity –> Destination –> Create Destination. Give the below parameter and ping the destination. It should return 200OK response.Name: S4C System ID(Anything can be given here)Type: HTTPURL: Provide the service URL from the MDO Distribution Administration from communication arrangement SAP_COM_0594.Proxy Type: InternetAuthentication: Basic AuthenticationUser and Password: Use the communication user and password created during ZSAP_COM_0594 communication systemAdditional PropertiesMDOProvider: trueMDOConsumer: trueMDIInstanceId: The value of this should be the systemId from the S4 service key.MDOBusinessSystem: Give the businessSystemId from the MDI instance. 5. MDO/Masterdata Orchestration:Create pull distribution model in MDO with MDI as provider and S4/Hana Public Cloud as consumer.Login to the Master Data Integration (Orchestration) app which we subscribed in the 2nd step of BTP1.1 –> Click on “Manage Distribution Model” Click on create –> add the meaning full name to model and description.Provider – MDI SAP Master Data IntegrationConsumer – Choose the BTP destination of S4/Hana Public Cloud that we created in BTP.Application Category – SAP S/4HANA Cloud (S/4)Business Object Type – Workforce Person (sap.odm.workforce.WorkforcePerson)API – MDI_LOG_WORKFORCE_PERSONMode – PullSave and activate the distribution model. After running the business scenario in SuccessFactors, You can use be Initial Replication to replicate all employees from MDI to S4C and Delta replication only for the changes since the last run of the integration.Monitoring in S4 Hana Public Cloud:You could see the replicated records in S4C using the “Message Dashboard” app under the /WFS namespace.And you could see the replicated worker/employee details under “Manage Workforce” app. NOTE: As per the new BP Model in S4/Hana Public Cloud, for one employee/worker 2 BPs will be created. One for employee and another one for employment.Key things to consider:One subaccount could have only one MDI instance, So make the instance strategy accordingly.You can delete the MDI instance only if the field enableTenantDeletion set to true.Before deleting the MDI instance, make sure you deactivated all the distribution model in MDO.By standard all employees should have unique email in SuccessFactors, If not it will throw error in S4C while replication.Conclusion:The integration of SuccessFactors with S4HANA Public Cloud through Master Data Integration provides a seamless and robust point to point solution for workforce replication, enabling organizations to streamline their HR processes while ensuring data consistency and accuracy across platforms.Whats next:In this blog we have seen all the steps involved in BTP, SuccessFactors, MDO and S4/Hana Public Cloud. In the next blog I will try to explain how the CB user will get created automatically and how SuccessFactors users could access the S4/Hana Public Cloud. And in the subsequent blog we will discuss about the “Cost Center Replication from SAP Master Data Integration to EC”.Thanks for taking time to read this..! Read More Technology Blogs by Members articles
#SAP
#SAPTechnologyblog
