Global Organizations are always challenged with diverse business processes in different plants, companies, and organizations across the globe. This puts a lot of pressure on uniform reporting, quick reporting, and analysis, decision making, etc.
If you ask every CEO of such global organizations, the ideal scenarios for them would be:
- To have standardized processes across the globe with country-specific localizations.
- To have worldwide standard core procedures and policies in different functions.
- To have a worldwide unified system and one set of processes.
Using this backdrop, from a system point of view, it is of utmost importance to develop one global SAP template and roll it out in different locations across multiple countries in a simplified and fast approach.
How to create a Global Template?
Let’s see how to create a Global Template with SAP S/4HANA. To get a good head start, organizations can look at the following SAP model companies:
- Industry-specific model company.
- Different lines of business (LoB) model companies.
- Multinational Corporation model company (for global organizations).
These model companies have best business practices that are pre-configured, which can give a good baseline from which Organizations can customize their unique processes that differentiate them from their competition.
It is important to take into account the unique requirements of each country and business divisions across the globe to make sure the global template meets close to 70% of the global requirements. The key input to creating SAP Global template is the approved Core procedures/policies of the global organization.
How to roll out Global Template to multiple locations effectively?
After successfully creating a global template with the template management approach, the next set of challenges involves rolling out this template across multiple locations effectively.
The biggest challenge is in the first rollout of this template in each country. It takes the longest time and could be challenging due to country-specific localizations.
It is important to focus on these points when the first roll out in each country happens:
- Get the best key users from each location, preferably 100% committed.
- Have the key users understand the template ahead of the start of the roll-out.
- Have the key users ready with country-specific challenges and possible ways of changing the processes where applicable.
- Get the key users to understand the roles and responsibilities.
- Make the key users understand that their role is not just important for the first roll out but other plants /locations within that country.
- Get the project implementation team fluent in the local language.
- And most importantly, have the individual country-specific sponsors ready and committed.
Once the first roll out in each country is completed, the remaining rollouts should fall into a ‘cookie-cutter’ approach. The key points are:
- Get the same key users in each rollout.
- Get the same project team in each rollout.
- Use the ‘fit workshop’ methodology than fit-gap or traditional blueprint.
- Each location that wants to deviate from the template should have a strong business case as to why they want to do it.
- Changes to the process should be allowed only if it is customer mandated or any legal requirements.
- Change Management team should be part of each roll out to make this process smooth.
Two other important areas to focus during global rollouts are:
1) Data Migration
- Make sure the data migration methodology is standardized and well-tested.
- Standard mappings, documentations, procedures, etc. should be in place before starting the rollout.
- Business users should start with Data Cleansing process well ahead of the roll-out of the template in each location.
2) End-User Training
- Training documents have to be standardized, elaborated, and distributed accordingly. These documents need to be clear in order to be understood by the team that will handle the system on a regular basis.
- Training documents will have to be in the country-specific language and preferably created by the individual key users.
- Local key users have to impart end-user training, with support from the project team.
The switch to S/4HANA will take your business to the next level, so don’t delay!