Cost Center Replication from SAP S4/Hana Public Cloud to SF EC using Master Data Integration

[Kirthan_Kumar]

Introduction:

This post is a continuation of my previous article, "Workforce replication from SuccessFactors to S4/Hana Public Cloud using Master Data Integration". In this post, we will explore the process of Cost Center Replication from SAP S/4HANA Public Cloud to SuccessFactors Employee Central (SF EC) using Master Data Integration (MDI).

Similar to the previous integration, we will leverage the pre-delivered business scenarios provided by SAP in SuccessFactors for this integration as well.

Background:

Initially we didn't have the cost center integration in scope, the idea was to maintain cost center manually in EC for this phase of the project. But during the testing of Workforce replication from SuccessFactors to S4/Hana Public Cloud using Master Data Integration we found that cost center associated with employee in EC is not replicating to S4Hana Public Cloud.

Reason: 

1. A GUID will be created in Master Data Integration (MDI) for each cost center, and this GUID will serve as a reference during workforce replication. If a cost center is created manually in Employee Central (EC), it will not have an associated GUID. For example, consider the records below: the first record represents a cost center created manually in EC, while the second record shows a cost center created using MDI in EC.
2. If you choose to create cost centers manually in SuccessFactors Employee Central (SF EC), you will need to implement the BADI WFD_CHANGE_WFP_MDI, as outlined in this document.

Since we want to adhere to the standard approach without any customization, we have decided to replicate the cost centers from SAP S/4HANA Public Cloud to SuccessFactors Employee Central (SF EC) using Master Data Integration (MDI).

High-level Architecture:

In this integration setup, SAP S/4HANA Public Cloud serves as the source for cost center creation. Cost centers will be replicated to Master Data Integration (MDI) using the Push distribution model of Master Data Orchestration (MDO). SuccessFactors will then retrieve the data from MDI using the Pull distribution model of MDO.

High Level Architecture of Cost center replication using Master data Integration/MDI

Configuration:

1. The step BTP 1.1 and S4/Hana Public Cloud mentioned in here (Workforce replication from SuccessFactors to S4/Hana Public Cloud using Master Data Integratio... will be generic for both workforce and cost center integration. By this time we will have 2 instance of MDI, one for S4/Hana Public Cloud and one for SF EC.
2. SuccessFactors: Enable and configure the "Cost Center Replication from SAP Master Data Integration to EC" business scenario.
   1. Search for "Business scenario" in SuccessFactors search bar.
   2. Filter for the scenario "Cost Center Replication from SAP Master Data Integration to EC" and activate it using the active toggle button and click on edit using pencil icon.
   3. Create OAuth connection in SF EC, using the service key of the SF MDI instance of the BTP.
   4. Scenario could be scheduled based on the requirement.
   5. Run the scenario using "Run now" option. 
3. SAP BTP: Create the destination for SAP SuccessFactors in SAP BTP. It can be done in 2 ways. Below are the additional properties need to be added in the destination.  

   Property Name	Value
   MDIInstanceId	Id of the MDI instance created for SuccessFactors
   MDOBusinessSystem	SF Company ID or businessSystemId mentioned in while creating the instance.
   MDOConsumer	true
   MDOProvider	true
   url.header.successfactors-companyid	SF Company ID

     
   1. Create the destination manually - Login to BTP -> Open the subaccount -> Connectivity -> Destination --> Create  

      

   2. Subscribe of the SAP SuccessFactors Extensibility, it will create the destination in BTP.
4. MDO/Master Data Integration - Create the distribution model in MDO/Master Data Orchestration. Below are the distribution models that needs to be configured.

   Mode	Provider	Consumer
   Push	S4/Hana Cloud Destination from BTP	MDI/Master data integration
   Pull	MDI/Master Data Integration	SF EC destination from BTP

     
   1. Push distribution model from MDO.   

      Provider	S4/Hana Cloud Destination from BTP
      Consumer	MDI/Master data integration
      Business Object Type	sap.odm.finance.costobject.CostCenter
      API	MDI_CHANGE_COST_CENTER
      Version	3.1.0
      Mode	Push
      Continuous Distribution	Yes

           
   2. Pull distribution model from MDO.   

      Provider	MDI/Master data integration
      Consumer	SF EC destination from BTP
      Business Object Type	sap.odm.finance.costobject.CostCenter
      API	MDI_LOG_COST_CENTER
      Version	3.1.0
      Mode	Pull
      Recurrence Pattern	Minutes

        

Replication and Monitoring:

1. Replicate all cost centers from S4/Hana Public Cloud to MDI using push distribution model.
   1. Login to MDO -> Manage Distribution Model -> Click on push distribution model that was created earlier -> Replicate -> Replication Mode = Initial Replication -> Click on Replicate. 
   2. 
2. Replicate the cost centers from MDI to SF EC
   1. Go the business scenario in SuccessFactors -> Go to Run and Review --> Click on Run now

   1. Click on the hyperlink on the "Last Run Time" to see the job status.

      

   2. You could see the replicated cost center by navigating to "Manage Data" -> Choose Cost Center from Search drop-down -> Filter with cost center code.

      

Conclusion:

By leveraging Master Data Integration (MDI), organizations can ensure that accurate and timely data flows effortlessly between systems, enhancing operational efficiency and decision-making capabilities. These out-of-the-box integrations using MDI not only simplify the management of essential data resources such as cost centers and workforce data but also ensure consistency and reliability across the enterprise.

In conclusion, adopting MDI for integrating SAP S/4HANA Public Cloud with SuccessFactors Employee Central—and vice versa—empowers businesses to maintain a unified data ecosystem. This seamless integration fosters a more streamlined and strategic approach to managing enterprise data, enabling companies to better adapt to dynamic business environments.

Thanks for taking the time to read this!

Regards,

Kirthan