Human Capital Management Blogs by SAP
Get insider info on SAP SuccessFactors HCM suite for core HR and payroll, time and attendance, talent management, employee experience management, and more in this SAP blog.
cancel
Showing results for 
Search instead for 
Did you mean: 
paramitamukherj
Product and Topic Expert
Product and Topic Expert
Context: 

In response to the dynamic nature of modern business environments, the evolving requirements for integrating Employee Central instances with ERP clients now emphasize a heightened level of flexibility. Originally centered around connecting a single Employee Central instance to a corresponding ERP client for downstream processes, the paradigm has shifted to cater specifically to customers such as conglomerates and service providers. 

In the context of Public Sector service providers delivering diverse services, such as Payroll through SAP HCM and other HR functions via SuccessFactors Employee Central, the requirement arises for different Employee Central entities which have specific business processes based on different legal entities. However, there is a need for a unified Payroll system, as the payroll processes remain consistent across all entities within a specific government. 

For conglomerates (as one of the examples) with different legal entities, each harboring unique business processes, the current approach requires the use of separate Employee Central instances. This facilitates a tailored management of employee and organizational data, aligning with the specific needs of individual legal entities. Despite this segmentation, a cohesive strategy is required to connect these instances to the same ERP client, ensuring the seamless execution of shared processes such as benefits, tax, and payroll. 

Another notable application of this flexible model arises during pivotal corporate events, such as mergers or splits. In such scenarios, the preference is to maintain separate Employee Central instances for an interim period. This strategy affords customers the operational dexterity to navigate transitional phases with minimal manual intervention. It provides a valuable buffer, allowing the organization to adapt gradually until all internal processes are streamlined. 

This approach not only acknowledges the diversity of business operations within different organizations but also underscores the significance of minimizing disruptions during periods of change. The operational autonomy granted to each legal entity through separate instances reflects a strategic understanding of the unique requirements and compliance considerations associated with each entity. 

In essence, this evolving integration strategy not only accommodates the complex landscape of conglomerate structures but also strategically positions the organization to manage change with agility, ensuring a smooth transition and continuity in critical HR and ERP functions. 

How It looks currently: 


 

How it will look with this feature: 

 


 

Conclusion: 

If you find the described feature intriguing and believe it aligns with your organization's needs, we would like to invite you to share your insights with us. Your feedback will help us in refining and tailoring this setup to meet the diverse scenarios and requirements of our customers. By reaching out to us, you contribute to the ongoing improvement and optimization of our services. 

Please consider sharing details on the specific scenarios you are planning to use with this feature. Your input will assist us in gaining a deeper understanding of your use cases, allowing us to enhance the feature to better suit your organization's unique needs. 

Feel free to contact us through the comment section, and we look forward to hearing more about your requirements and expectations. Thank you for your collaboration and for being an essential part of our ongoing development process. 
7 Comments
Mohan1
Explorer
0 Kudos
Hi Paramita,

This architecture looks to be good but i have basic query, i hope we need to deploy seperate artifacts for each EC Instance, if so then how to we configure the Webservices in SOAMANAGER? We only have one Webservice (Example: CO_ECPAOX_EE_MD_ORGAS_BNDL_QRY) having configured multiple iflows (Artifacts) depending on the number of EC Instances used we get different end point URL's to configure in SOAMANAGER. How do we handle this?

 

Regards,

Mohan
paramitamukherj
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hello Mohan,

Thank you for your question.

In our current design we are considering the possibility that you can, additionally to the settings in  SOAMANAGER , assign depending on the EC Instance different URLs reflecting the IFlow URL.

Regards,

Paramita
Mohan1
Explorer
0 Kudos
Hello Paramita,

 

Thank you so much for the swift reply. Let us know once this is achieved. We will keep in touch.

 

Regards,

Mohan
paramitamukherj
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hello Mohan,

 

Sure, we will communicate the same again through SAP Blog. Meanwhile if your company has the similar requirement, you can also get in touch with me and we can work together to validate the requirements.

 

Regards,

Paramita
SankarsanDey
Active Contributor
0 Kudos
Yes, this is one of the common requirement which we are looking for from past.

Please let me know how and when it will be feasible .
paramitamukherj
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hello Sankarsan,

Thanks for your interest in this topic. We are currently in the implementation phase and I'll roll out soon regarding the availability. May I know, what is the requirement in your company w.r.t this feature? We can align to get a better picture of the same and incorporate more features to this.

Regards,

Paramita
Umesh1
Participant
0 Kudos

Hi,

Thanks for working on this option, as many large customers which has multiple different subsidiaries are requesting for this kind of options.

Scenario 1: A global company wants to provide freedom to regional/country entities to implement their own customizations in separate instances of SuccessFactors, however for the finance reporting they want to have a global S4 system.

Scenario 2: Some organizations are also looking at this option from data centre location/data privacy requirements perspective, such as one dedicated instance of SuccessFactors for EU regions, and for USA, China, APAC separate instances in their respective regions.

Hope this helps.

Looking forward for the solution

 

Regards,

Umesh