# SAP Global Template Rollout Plan Template (PPT Outline)

> Source: https://netray.co/tools/sap-global-template-rollout-plan-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Fill-in rollout plan for an SAP global template: scope, local deviation rules, wave plan and governance, laid out so each block becomes one slide.

## Category

erp-migration

## Erp

SAP S/4HANA

## Audience

- SAP program manager
- Template lead
- PMO

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Program name

**Key:** program

**Type:** text

**Default:** Global ERP Harmonisation Program

#### Company

**Key:** company

**Type:** text

**Default:** Acme Industrial Group

#### Global template name

**Key:** template_name

**Type:** text

**Default:** ACME Core Template v1.0

#### SAP release

**Key:** release

**Type:** text

**Default:** SAP S/4HANA 2023, private cloud edition

#### Executive sponsor

**Key:** sponsor

**Type:** text

**Default:** Group COO

#### Global template lead

**Key:** template_lead

**Type:** text

**Default:** Head of Business Process Excellence

#### Wave 1 sites and date

**Key:** wave1

**Type:** text

**Default:** Plants DE01 and PL01, go-live 2027-04-01

#### Wave 2 sites and date

**Key:** wave2

**Type:** text

**Default:** Plants US01, US02 and MX01, go-live 2027-10-01

#### Wave 3 sites and date

**Key:** wave3

**Type:** text

**Default:** Plants IN01 and CN01, go-live 2028-04-01

#### Local deviation rule

**Key:** deviation_policy

**Type:** select

**Options:**

- No deviation without steering committee approval
- Statutory deviations only
- Design authority may approve minor deviations

**Default:** Statutory deviations only

#### Rollout objectives

**Key:** objectives

**Type:** textarea

**Default:** 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.

**Blocks:**

#### Slide 1: Program and objectives

**Body:** Program: {{program}}
Company: {{company}}
Global template: {{template_name}} on {{release}}
Executive sponsor: {{sponsor}}
Template lead: {{template_lead}}

Objectives:
{{objectives}}

#### Slide 2: Template scope (what is global)

**Table:**

**Columns:**

- Process area
- Global standard
- Local extension allowed
- Owner

**Rows:**

**0:** Procure to pay (MM, FI-AP)

**1:** One purchasing org structure, release strategies, 3-way match

**2:** Local tax codes, e-invoicing

**3:** Global process owner P2P

**0:** Plan to produce (PP, QM)

**1:** MRP settings, routings, inspection plans

**2:** Plant specific work centers

**3:** Global process owner PTP

**0:** Order to cash (SD, FI-AR)

**1:** Order types, pricing procedure, billing

**2:** Country pricing conditions, statutory documents

**3:** Global process owner O2C

**0:** Record to report (FI, CO)

**1:** Chart of accounts, cost center hierarchy, close calendar

**2:** Local statutory ledger, local GAAP

**3:** Global process owner R2R

**0:** Master data

**1:** Material, vendor and customer data model and naming rules

**2:** Country specific tax fields

**3:** Data governance council

#### Slide 3: Local deviation policy

**Body:** Policy: {{deviation_policy}}.

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

**Table:**

**Columns:**

- Wave
- Sites and go-live
- Focus
- Exit gate

**Rows:**

**0:** Wave 1 (pilot)

**1:** {{wave1}}

**2:** Prove the core template, validate cutover approach

**3:** Hypercare closed, KPIs stable for 2 closes

**0:** Wave 2

**1:** {{wave2}}

**2:** Add country localisation, first reuse of template

**3:** Deviation count within agreed limit

**0:** Wave 3

**1:** {{wave3}}

**2:** Complex statutory regions, remaining plants

**3:** All sites on one release and one support model

#### Slide 5: Governance

**Table:**

**Columns:**

- Body
- Cadence
- Decides

**Rows:**

**0:** Steering committee

**1:** Monthly

**2:** Scope, budget, wave dates, deviation escalations

**0:** Design authority

**1:** Weekly

**2:** Template changes, deviation classification, interfaces

**0:** Global process owners

**1:** Bi-weekly

**2:** End to end process design and KPIs

**0:** Wave program team

**1:** Daily during build and cutover

**2:** Wave plan, testing, training, cutover

**0:** Change control board

**1:** Weekly

**2:** Post go-live template releases

#### Slide 6: Risks and readiness

**Body:** 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

**Signatures:**

- Executive sponsor
- Global template lead
- Program manager
- Finance controller

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use this template

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Bullets:**

- Statutory: accept and localise
- Global improvement: change the template
- Local preference: reject unless approved at steering level

#### Common mistakes

**Body:** 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.

**Cta:** 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.

**Faq:**

#### What is an SAP global template?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

sap global template rollout ppt, sap global template rollout plan, sap rollout template, sap template approach, sap global design template, sap wave plan template, sap local deviation policy, sap s/4hana rollout governance

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json