Best Practices in SAP Rollout
Here is what you need to get right!
When large enterprises use tier 1 ERP for financials and other core common processes at the corporate level and tier 2 ERP for subsidiaries and smaller locations this is what SAP calls two-tier ERP. SAP’s Two-Tier model allows you to use the robust, comprehensive ERP system at the corporate level (tier one) while keeping the more flexible, agile, cost-effective and easier to implement solution called SAP Business ByDesign at the subsidiary level (tier two).
At Seidor we offer SAP Two Tier Strategy under the following models:
- Assistance in building a 2-Tier Decision tree: Choosing a software is a complicated task at the best of times, and considerations such as tiers likely only complicate the situation and make the decision of what to go with and where to start harder. At Seidor, we can help you to define parameters about when to implement Tier 1-level solution and Tier 2 to ensure that this task starts and stays on the right path. Most of these decisions are driven by time, money and functionality.
- Definition of the Tier-2 Template: If you are considering an ERP for your subsidiaries, then let’s define the standard parameters based on your subsidiaries needs to be able to make faster implementations.
- Rollout of the template to 2-Tier Subsidiaries: as your business expand you don’t need to reinvent the wheel every time you acquire more assets around the world. At Seidor we can help you with several deployments worldwide in quick succession through our 26 offices and United VARs with coverage in 80 countries.
Sharing 3 Top Tips to ensure a successful global SAP Rollouts using a global template based on Cantel's experience
Companies that are expanding their business globally and are already using SAP solutions eventually want to ensure that their subsidiaries also run their operations with SAP. David Leon, COO at Seidor USA shares his experience on the Two-Tier Strategy and the 3 top tips to ensure a successful rollout when using a global template:
1. Create Definitions
If you don’t create definitions before the project starts, this can cause delays when implementation is underway. However, you might already have your definitions in SAP, or another first-tier solution, in which case it is a good idea to use those in your global template.
When implementing SAP ByDesign into one of Cantel’s subsidiaries, we incorporated into the global template a lot of the definitions from S/4 HANA, which Cantel runs in its main office.
2. Be flexible
A common expectation from customers at the start of a global implementation is to think the new system will work perfectly out of the box. But even if the HQ is running SAP too, there will be fields in the second-tier system that are named differently, or fields you want to keep from your old system that aren’t in the new system.
So, a key to a successful global template approach is to realise some changes will be needed. Being open to suggestions from your systems integrator will be an important factor in having a project run more smoothly and to get all the results you want.
3. Document your Standard Operation Procedures (SOPs)
The testing and training phases can involve a lot of duplicate work and be very time-consuming. It’s important to be very clear on what you are expecting and make sure everybody's following the same processes.
I recommend documenting your Standard Operation Procedures (SOPs) preparing a well-documented step by step guide including screenshots and clear instructions which should be used everywhere where ByD is being used.
Creating SOPs saves a lot of time in the long run. In the future, if anyone has a question regarding a process, you already have it documented. They can just check the SOP manual or watch the relevant training video. This eliminates so much back-and-forth between people that I would say this is an essential key to a successful project.