SAP Global Template Rollout Plan Template (PPT Outline)
A global template rollout plan answers four questions on one page: what is standard everywhere, what a site may change, in what order sites go live, and who decides. This tool gives you that structure with realistic example content that you overwrite.
Fill in
SAP Global Template Rollout Plan Template
Slide 1: Program and objectives
Program: Global ERP Harmonisation Program Company: Acme Industrial Group Global template: ACME Core Template v1.0 on SAP S/4HANA 2023, private cloud edition Executive sponsor: Group COO Template lead: Head of Business Process Excellence
Objectives: Run one global design for procure to pay, plan to produce, order to cash and record to report. Retire site specific custom code. Reduce time to onboard a new plant from 18 months to under 9 months.
Slide 2: Template scope (what is global)
| Process area | Global standard | Local extension allowed | Owner |
|---|---|---|---|
| Procure to pay (MM, FI-AP) | One purchasing org structure, release strategies, 3-way match | Local tax codes, e-invoicing | Global process owner P2P |
| Plan to produce (PP, QM) | MRP settings, routings, inspection plans | Plant specific work centers | Global process owner PTP |
| Order to cash (SD, FI-AR) | Order types, pricing procedure, billing | Country pricing conditions, statutory documents | Global process owner O2C |
| Record to report (FI, CO) | Chart of accounts, cost center hierarchy, close calendar | Local statutory ledger, local GAAP | Global process owner R2R |
| Master data | Material, vendor and customer data model and naming rules | Country specific tax fields | Data governance council |
Slide 3: Local deviation policy
Policy: Statutory deviations only.
Every request for a local deviation is logged with business case, legal driver (if any), process affected, build effort, and run cost. The design authority classifies it as: statutory (accepted), global improvement (move into template), or local preference (rejected unless the steering committee approves). Approved deviations are built as clearly separated enhancements, documented in the template repository, and reviewed at each wave.
Slide 4: Wave plan
| Wave | Sites and go-live | Focus | Exit gate |
|---|---|---|---|
| Wave 1 (pilot) | Plants DE01 and PL01, go-live 2027-04-01 | Prove the core template, validate cutover approach | Hypercare closed, KPIs stable for 2 closes |
| Wave 2 | Plants US01, US02 and MX01, go-live 2027-10-01 | Add country localisation, first reuse of template | Deviation count within agreed limit |
| Wave 3 | Plants IN01 and CN01, go-live 2028-04-01 | Complex statutory regions, remaining plants | All sites on one release and one support model |
Slide 5: Governance
| Body | Cadence | Decides |
|---|---|---|
| Steering committee | Monthly | Scope, budget, wave dates, deviation escalations |
| Design authority | Weekly | Template changes, deviation classification, interfaces |
| Global process owners | Bi-weekly | End to end process design and KPIs |
| Wave program team | Daily during build and cutover | Wave plan, testing, training, cutover |
| Change control board | Weekly | Post go-live template releases |
Slide 6: Risks and readiness
Key risks to track per wave: master data quality at the site, local legal requirements discovered late, key user availability, interface changes in plant systems, and divergence between the template and site specific enhancements. Each risk gets an owner, a mitigation and a date.
Approvals
This is a starting outline, not a vendor methodology. Each heading is written so it can become one slide in your own PowerPoint master: export to Word, copy each block into a slide, and replace the example processes with your own scope. Align naming with SAP Activate phases if your program uses them.
Review your rollout plan
Send us the exported plan and we will comment on wave sequencing and the deviation rule. Optional, the template works without it.
Optional. The tool and every export work without this. No spam.
How to use this template
Fill in the program name, release, sponsor and the three wave lines. Choose your deviation rule, then export to Word or PDF. Each heading is written as a slide title, so you can paste the blocks into your corporate PowerPoint master and edit the tables in place. Replace the example process areas with your own scope statement and the owners with real names.
- Keep one slide per block, with the table as the main visual
- Name a global process owner for every scope row
- Put dates only on go-live, not on every activity
What a global template really contains
A template is more than configuration. It is a defined set of end to end processes, a single organisational structure (company codes, plants, purchasing organisations), a common master data model, a global chart of accounts, standard reports and interfaces, and the rules for extending all of that locally. The value comes from reuse: each wave should configure and localise, not redesign. If wave 2 starts with workshops about basic purchasing, the template was not complete enough.
Local deviations and wave planning
Most programs fail at the boundary between global and local. Decide the rule up front, log every request, and classify it as statutory, global improvement or local preference. Statutory needs (tax, e-invoicing, statutory reporting) are accepted; improvements go back into the template for all sites. For waves, start with a pilot of one or two representative plants, then place complex statutory regions later once the template is stable.
- Statutory: accept and localise
- Global improvement: change the template
- Local preference: reject unless approved at steering level
Common mistakes
Teams often present a wave plan without exit gates, so the next wave starts while the previous one is still unstable. Another trap is counting localisation as part of the template, which hides the real deviation load. Finally, governance is often defined for the project but not for the template after go-live. Name who owns template changes once the program ends.
Frequently Asked Questions
What is an SAP global template?
It is a standardised ERP design, covering processes, organisational structure, master data and configuration, that is built once and rolled out to many sites or countries. Each rollout wave reuses the template and adds only the local requirements, mainly statutory ones.
How many deviations are acceptable?
There is no fixed number. Track the count and the effort, and agree a limit with the steering committee. Statutory deviations are expected; local preference deviations should be rare because they raise build, test and support cost for every later release.
How should waves be sequenced?
Start with a representative pilot that proves the template and cutover method. Then group sites by shared localisation, such as the same country or region, and leave the most complex statutory or acquisition sites until the template has run stably for a few closes.
Can I use this for non-SAP programs?
Yes. The structure of scope, deviation policy, waves and governance applies to any multi-site ERP rollout. Only the process areas and example terms are SAP flavoured, and you can edit them freely before export.
If your template data lives in several ERPs, Netray can add a private AI layer over them so program and process teams can ask questions about open deviations, wave status and master data quality, running on your own infrastructure.
Related Tools
SAP MM BPML Business Process Master List Template
An editable MM business process master list with process IDs, transaction codes, owners and in or out of scope status, exportable to Excel.
SAPSAP MM Transaction Codes Reference
Searchable list of the SAP MM transaction codes consultants and buyers use daily, grouped by purchasing, inventory, invoice verification and MRP.
ERP OperationsSAP MM Support Ticket Template and Examples
A fill-in SAP MM support ticket with the details support needs to resolve it, plus a table of typical MM issues and the first things to check.
More ERP Migration & Selection tools
See all- S/4HANA Migration Business Case NPV Calculator
- SAP Migration Schedule Risk PERT Calculator
- SAP Migration Project Team Cost Calculator
- S/4HANA Migration Risk Register Worksheet
- S/4HANA Steering Committee Status Report Template
- SAP AVC Migration Checklist
- ERP TCO Comparison Calculator (5-Year)
- ERP Migration Risk Assessment
- Data Migration Effort Calculator
Keep exploring
Free tools
- SAP S/4HANA On-Prem Private AI Layer Blueprint GeneratorFill in your version, database, hosting and use cases to get an architecture plan for adding a private, on-prem AI assistant to SAP S/4HANA, with components, security controls and a three-phase rollout.
- SAP Delivery Block Reasons TemplateA fill-in document to define a new delivery block reason or record a block on an order, with level, justification and release rules.
- SAP QM Inspection Plan Design TemplateA design document you fill in before building an inspection plan in QP01: scope, operations, characteristics, sampling and sign-off.
ERP fixes and how-tos
- Private AI for SAP Business One: Service Layer, a read replica and a local modelAdd a private AI assistant to SAP Business One: Service Layer reads, SQL Server or HANA replica, document index, local LLM, permissions and approvals.
- How to create an inspection plan in SAP QM (QP01)Create an inspection plan in SAP QM with QP01: header, operations, master inspection characteristics, sampling procedure and material assignment, plus a plan report.
- How to Add a Private AI Layer to Global Shop Solutions On-PremHow to add a private on-prem AI assistant to Global Shop Solutions ERP: read-only data access, scheduling data, security mapping, GPU sizing and phased rollout.
Runs with your ERP
- Descartes Global Logistics Network and SAP ECC with SAP TMHow Descartes' Global Logistics Network connects SAP TM to carriers and customs filing, what flows, how to set it up, what breaks and where private AI helps.
- Loftware with SAP ECC and S/4HANA: label design and printing from SAP transactionsHow Loftware and the NiceLabel ABAP package drive labels from SAP ECC and S/4HANA, including SAP GLM Plus, data flows, setup steps and pitfalls to avoid.
- ShipEasy with SAP Business One: rate quotes and parcel labels from sales ordersHow ShipEasy from Third Wave connects SAP Business One to UPS, FedEx and USPS for rate quotes, address checks and tracking written back to documents.
Guides
- Multi-Site ERP Deployment StrategiesMultisite ERP deployment explained: single instance vs multi-instance, template-based rollout, site sequencing and data harmonization for manufacturers.
- SyteLine Global ERP Rollout Template GuidePlan a template-based global SyteLine rollout with standardized configuration, phased deployment, and localization for multi-country ERP implementations.
- AI Change Management on the Shop Floor: A Practical GuideAI change management on the shop floor: how to introduce agents to operators and planners without stalling production, with training, comms, and rollout steps.
AI on your ERP
- AI for SAP S/4HANA Sales and Distribution (SD) That Explains Orders, Pricing and BlocksAI for SAP S/4HANA SD: order status, delivery and billing blocks, pricing explanations and credit holds in plain English. Read-only, on-prem option.
- A CIO's Guide to Sequencing AI on Your Manufacturing ERPA practical CIO guide to sequencing AI on top of your manufacturing ERP: where to start, how to budget, who should own it, and how to avoid a pile of stalled pilots.
Integrations
- How to add AI agents to Global Shop SolutionsHow to add AI agents to Global Shop Solutions: a read-first tool layer over its data and APIs, approval before any write, and on-prem model options for job shops.
- How to add an AI chatbot to Global Shop SolutionsAdd an AI chatbot to Global Shop Solutions for employees or customers: grounded in job, PO and inventory data, with role limits and a fully on-prem option.
Software
- Global Shop SolutionsWhat Global Shop Solutions ERP is, how its estimating, scheduling and shop floor modules serve job shops, and which ERP alternatives to compare.
- SAP S/4HANASAP S/4HANA explained for manufacturers: core modules, deployment options, APIs and IDocs, honest limitations, alternatives and where AI helps on top of it.