SAP S/4HANA Cloud Public Edition

Multi-Country Approach

Customer Facing External

February, 2025
Agenda

Planning a multi-country waved

approach
Practical insight for Live & Implementing
scenarios
Configuration
Waved approach for Live and future
deployment
Governance
Managing & Coordinating Transports

What Else?
Project Planning example, Operations &
RACI

INTERNAL – SAP and Customers Only 2

 SAP S/4HANA Cloud Public Edition
Grow your business

with compliant expansion into new regions with the widest and deepest localization coverage of any SaaS ERP

Go global with
confidence with globally-
ready localizations
59 local versions
delivered by SAP

• Deep: Country-level
localizations integrated
end-to-end at a deep
33 Languages supported

functional level
Any
other country/region rollout with
• Compliant: Up-to-date localization as a self-service for
regulatory compliance for SAP S/4HANA Cloud Public
tax, statutory reporting, Edition (1)
and business-to-
government interactions
• Everywhere: Geographic
coverage for 59
countries/regions in 33
languages. Expand further
with localization-as-a-self-
service tools
Includes content for: Accounting Tax Payments
Invoicing Reporting

urrent S/4HANA Cloud customers using SAP Central Business Configuration (CBC) with 3-system landscape environment can participate in Customer Local Version early adoption program.. Belarus, Venezuela, embargo countries
nd SAP delivered/planned Local Versions are excluded.

INTERNAL – SAP and Customers Only 3

SAP S/4HANA Cloud Public Edition
Multi-country roll-out

Ensuring Success
Best practice & practical insight based
on large ‘multi country’ roll-outs.
Governance & Cloud Mindset.
Configuration Do’s and Don’ts.
SAP S/4HANA Cloud Out of Presentation Scope
Public Edition
• Parallel Project Lines (Currently in Early Adopter program mode)
• Specific guidance on Localization Requirements
• Content Localization Toolkit

INTERNAL – SAP and Customers Only 4

Planning Multiple Waves: Cloud Mindset
How to create successful multi-country strategy

Key pillars that drive

success

Cloud Focused Central Understand localizations Plan Change Management Data & Access
Authority & CCoE & Business volume & Wave Roll-Out Management:
approach Best Practice
• Use of Activate and CCoE • Bring in right people from • Geographic location – reduce • Ensure sufficient lead-time for
governance Business – don't overlook local complexity of ‘mixing’ regions in roll- data migration (Data migration
knowledge out. cockpit). Assign responsibility
• F2S for each wave roll-out
customer/partner
• Verify consistency and availability • Identify highest generating billing • Waved Approach vs Big-Bang
of each country requirements ( countries, consider to go-live at
• Engage the business – change agents • Identify any complex needs:
link). later point or start with smaller Asset + other extensibility
to execute & secure sponsorship
subsidiaries objects
• Ensure global consistency for. • Enablement, documentation and
• Plan country activation (Max. of 5 identify language requirements
• Role + IAM strategy – plan central
• Forms, (output mgmt.) countries per project line) governance and change strategy
• Roles & role strategy • Include the upgrade periods in the (upgrades etc.)
• Identify any local data privacy, implementation schedule.
• Localization templates & security, Datacenter or legal
needs; rules. • SAP Note 3151804 - Country
e.g. e-docs, billing, identify Activation Guidance in Central
priorities Business Configuration
such as local FYV changes,

INTERNAL – SAP and Customers Only 5

 SAP Activate: Single and Multi-Country Deployment
Approach specific for SAP S/4HANA Cloud, 3-system landscape

• Single country deployment can be structured as incremental deployment waves that drive faster time to value or deployed in big-bang
go-live.
• Multi-country deployment uses a template country rollout approach.
• This is based on a configuration/process set defined in the Explore phase that is implemented across all countries and regions.
• This produces a consistent repeatable processes at all locations with the organization.
• The template approach divides the overall implementation into smaller waves to reduce complexity and the time to value.
Scenario 1 – Interim Go-Lives: (a) Single country deployment with multiple deployment waves or (b) Global Template deployment in multiple
countries with multiple go-lives. Cutover and go-live at the end of each wave. This allows a quicker time to realizing the initial value.

Go-live wave 1 Go-live wave 2 Go-live wave 3

Prepar Deplo
Explore Realize Run
e y
Exp Deplo
P Realize
. y
Exp Deplo
P Realize
Scenario 2 – Big-bang Go-Live: . y
(a) Single country implementation with interim release to production steps with big-bang go-live
(b) Global Template with interim release to production steps. Countries are configured and tested in each wave and go-live with last wave.
All countries go-live at the same time.

Release to Release to Go-live

Production Production
Prepar
Explore Realize Exp. Realize Exp. Realize Deploy Run
e

INTERNAL – SAP and Customers Only 6

 Configuration: Live & Implemented Countries

Scenario 2. Global Template and interim Go-Lives with countries cutover and Go-Live at the end of each phase. Quicker time-to-
value.

Go-Live 1
Prepare Explore Realize Deploy Operations

P E Realize
Deplo Go-Live 2
y Go-Live 3
Deplo
P E Realize
y

• Wave1 is live, Wave2 deployment is about to start.

• One single Production landscape (and system) common for all countries.
• Scenario is stable until Project Parallel Line (PPL) is available for GA.

Additional Considerations:
• How to roll out Wave2+ with no impact on live companies.
• How to stay on schedule while ensuring quality in Wave2+ configuration and transport orders.

INTERNAL – SAP and Customers Only 7

Country Activation and Configuration
for Three-system Landscape

​Forcustomers starting with 3-System Landscape and SAP

Central Business Configuration, the Scoping Experience
gives option for Multi-country scoping.

With SAP Central Business Configuration, customers are

able to choose:
• Countries in which the chosen business processes
are run
• Pre-defined scenario bundles
• Additional non-standard scenarios

Best Practice: SAP recommends activating max. of 5

countries per transport and planned in accordance with Bundled Scenarios:
overall localization roll-out plan. SAP Note 3151804 • Enterprise
• Professional • Finance-Led ERP
Services Management
• Accelerated Third-
• Accelerated Party Returns • Accelerated Third-
Customer Returns Party Returns from
Seller to Supplier

INTERNAL – SAP and Customers Only 8

SAP Activate Best Practices for Multi-country Rollout
Go-live in Phases (3SL)

Standard (Scenario 1) or Standard (Scenario 1) or

Release to Production Release to All Go-
(Scenario 2) Wave 2 – Activation ofProduction(Scenario 2) Live
New Wave 3 – Activation of New
Wave 1 – (Initial Country Activation) Countries Countries

Initial country(s) implementation and global template Additional waves of countries using the global template
• Multiple Countries can be selected in one time within CBC. • Minor Explore for localized topics and to build configuration backlog (i.e.
• SAP’s best practice is to activate no more than 5 countries per tax, etc.)
activation run. Multiple activation in batch can be done within each
deployment wave. Customers should deploy business content activation
• Additional Fit-to-Standard Analysis can be performed in the Development
transports before starting any configuration activities. system using the previous country’s scenarios and data. Alternatively, the
new countries can be configured with template configuration and sample
• SAP recommendation for country activation can be found in data and used during the Fit-to-standard.
SAP Note 3151804 - Country Activation Guidance in Central Business
Configuration. • Realize configuration for all the countries in scope.
• SAP recommends to Complete implementation activities such as Scoping, • Follow same mechanism for transports as in Wave 1. Utilize weekly sprints
Configuration, Extensions for Initial Countries. After the Go-Live (Scenario 1) and transport to production as recommended by SAP.
or Release to Production (Scenario 2) of the first phase countries, move to
second wave and activate the new countries. • With the Release to Production, all countries go-live at the end of the last
wave.
• Fit-to-Standard executed using the Starter System
• Additional waves are possible as required.
• Realize configuration for all countries included in the wave.
• Go-live options for the initial rollout or interim waves:
• Standard go-live where business operations are executed in the
Production system after each wave.
• Release to Production where the wave is tested, and Production is
configured but business operations remain on the legacy system.

INTERNAL – SAP and Customers Only 9

Multi-Country Process Leveraging the Parallel Line Feature in SAP S/4HANA
Cloud
After go live of Wave 1, the implementation project can continue leveraging the Parallel Line. During Wave 2, Mainline is reserved
for (1) maintenance of the productive scenario (2) support process (Hotfix Collections from SAP); upon completion of Wave 2,
configuration is merged into main line.
Scenario 1 – Interim Go-Lives: (a) Single country deployment with multiple deployment waves or (b) Multiple countries
with multiple go-lives.
Go-live
Cutover and go-live at the end of each wave. wave 3
Go-live wave 1 Go-live wave 2
Prepar Deplo Deplo
Explore Realize Run
e y y
Rebase Continue
* in
Main Line existing
Explor Realiz Deploy parallel
Parallel Line Branch
e e *
Merge 2 line
Re-Branch
1 new
parallel line

​(1)
Branch to establish the Parallel Line ​(2) two options:
RECOMMENDATIONS: Branch after Go-live Wave 1 • Option 1: Continue next wave in existing Parallel Line
• Option 2: Re-branch and implement subsequent wave

Legenda
RECOMMENDATIONS: If the application data created in the
Line
parallel line for Wave 2 are instrumental to configure also Wave
SAP Activate
phase 3 (e.g. quicker set up for intercompany-transfer with an
PPL-specific step existing Country, then suggestion is to keep working in exisitng
*if config changes happen in parallel line; else, suggestion is to reBranch a clean new
main line after Branch parallel line.

INTERNAL – SAP and Customers Only 10

Recommended Governance Model
Avoid impacting live companies

Governance model will be required from now on. The single Production instance is the driver for the
need. Parallel Project Line will help with emergency changes and parallel rollouts, but a governance
model will be required even after all companies are live due to the common production tenant.

Key phases: Global Rollout via waves to additional

countries
Month 1 Month 2 Month 3 Month 4
Go-Live
• Beginning of Realize Go-Live

Deploy Deploy
Realize
• Rest of Realize Explore Explore
7 8 9
Waves
• Deployment and Go-live C4 continue until
C5 all countries
C6
are live
Three pillars: Integration
Walk-
through

Bi-annual Upgrade
Testing C4, C5, C6
• Coordination R

Data Migration
• Documentation Cutover Cutover Planning Cutover

• Testing Change Management Execution

Heavy configuration
Light configuration
INTERNAL – SAP and Customers Only 11
Recommended governance model
Coordination

Golden rules
• Follow during Waves 2+ and Operations, live countries take priority.
• Nominate a single Central authority who will synchronize with regional/country coordinators.
• Design and publish standard process and schedule with bi/weekly sprints with predefined schedule and
deadlines.
• Socialize endexample
Sprint schedule to end process of steps to follow when planning, performing, and transporting changes.
Monday Tuesday Wednesday Thursday Friday

AM – Sprint locked,
Audit
Configuration & Configuration & Configuration & AM – Transport orders
PM – TAT regression
Documentation Documentation Documentation moved to P-system
testing & issue
resolution
Emergency process

• Agree on what is considered an emergency for live companies. Document & review each scenario

• Outline a procedure on how to manage configuration items not fully completed.

• Establish a communication process and meetings to other countries and companies.

• Include steps for Test Automation Tool (TAT) as part of the approval process.

INTERNAL – SAP and Customers Only 12

Recommended governance model
Documentation and Testing

​Documentation

• Create a central repository for all sprint

related documentation.
• Collect all configuration changes in a single
document for all coordinators and
configuration experts so everyone is aware
of the changes.
• Ensure that the impact of the changes
are understood and communicated.

Testing
• Enforce the completion of configuration
changes testing ahead of the sprint project
release.
• Set up critical business processes in the Testing
Automation Tool (TAT) so they run at least
weekly.
• Execute regression testing as part of the
regular weekly routine with the processes in TAT.

INTERNAL – SAP and Customers Only 13

Key Factors for Success
Configuration

• Understand heavy vs. light configuration times and designate “configuration freeze” periods for live
companies
(only break-fix).

• Define a solid process for emergency transports during the weekly sprints for transports to Production.

• Identify the right people for transport order control (design) authority and coordinators.

• Provide a central location and guidelines for configuration documentation and testing.

• Build automated test scripts and leverage the Test Automation Tool for each country as part of the
configuration testing phase.

INTERNAL – SAP and Customers Only 14

 Sample Plan: Wave 1+Wave 2 & 3 approach

Jan Feb Mar April May June Jul Aug Sept Oct Nov Dec
Prepare Explore Realize Run
Deploy

Test Phase 1

Test Phase 2
Regr. Test

UAT | User Acceptance Testing

Project Prep F2S Workshops
Illu
stra
Wave 2

Regression Test

Upgrade Period
Master Data definition
Upgrade Period

Config
Local / Global ti ve
E XA
values /
System Config.
Designs
Optional
Local Approved CRs execution
MP
requirements
Mandatory
Int./Ext.
Mandatory Int. / Ext.
development
LE
design
Data Collection, Cleanup & Unit
DL1
Test
DL2
DL3
Cutover
OCM / Training Hypercare

Realize Deploy Run

Global System

protect Wave2
Blackout to

UAT
Test Phase 2
Local System Config.
Config.

Optional Local approved CRs execution

Wave 3

Approved CRs execution

Mandatory Int. / Ext.

Mandatory Int./Ext development
development
Data Prep and Data Load (DL) Unit Test DL1

Upgrade Period
DL2
Upgrade Period

DL3

Test Phase 1
OCM / Training
Cutover
Hypercare

INTERNAL – SAP and Customers Only 15

 Project Plan – Multi-Country Rollout
Template Approach using SAP CBC - Scenario 1: Interim Go-lives
Feb Mar Apr May Jun Jul Aug Sept Oct Nov

Global Template and initial country(ies) Global Rollout via waves to additional
te te e
countries
at
e
at Go-Live at
e e
at Go-Live
Ga Ga G G G G
Q Q Q Q Q Q
Prepar Deploy Deploy
Explore Realize Explor Realize Explor
e
e e
Country Activation Activate
Sets
Activate
Configure first wave
addition Waves
Initial al Configuration
Project
Countries countries Countrie
second wave
continue until
Fit-to-Standard in batches s
planning of 5 Walk- in batch countries Walk- all countries
throug of 5 throug are live
Self- h h
Config Definition
enablement
Integration Integration
Integration Design

Regressio
Test Preparation Testing n testing Testing

Upgrade Period
Upgrade Period

Data Migration Planning Data Migration Data Migration

Cutove Cutove
Cutover Planning Cutover Planning
r r

Change Management Plan Change Management Execution Change Management Execution

Starter System Development System and Test System

Production System
• To optimize processing time, it is recommended to limit the number of countries in each activation. See SAP Note -
3151804 - Country Activation Guidance in Central Business Configuration.
• After the initial countries are activated, new countries are added in sets as the defined in the activation schedule. After
each activation, the countries activations are moved to P. The specific customer situation must be assessed to
INTERNAL – SAP and Customers Only 16
determine the optimal plan.
 Project Plan – Multi-Country Rollout
Template Approach using SAP CBC - Scenario 2: Release to Production
Feb Mar Apr May Jun Jul Aug Sept Oct Nov

Global Template and initial country(ies) Global Rollout via waves to additional
te te te
countries te
Ga Ga Ga Release to Ga Release to
Q Q Q Production Q Production
Deploy
Prepar Expl Expl
Explore Realize Realize
e -ore -ore
Activate Activate
Country Activation
Sets
Initial
Countrie
Configuration first wave New
Countrie
Waves
countries
Project
s s continue until
Fit-to-Standard C1, C2, C6, C7, Configuration
planning C3, C4, Walk- C8, C9, second wave of cutover and
C5 throug C10
countries then all
Walk-
h
Self-
Config Definition
throug countries Go-
enablement h
Integration live
Integration Design Integration

Regressio
Test Preparation Testing n testing Testing

Test Data Cutove

Upgrade Period
Upgrade Period

Data Migration Planning Data Migration

Migration r
Initial Cutover
Cutover Planning
Planning

Change Management Plan Change Management Execution Change Management Execution

Starter System Development System and Test System

Production System
• To optimize processing time, it is recommended to limit the number of countries in each activation to 5 or less.
• After the initial countries are activated, new countries are added in sets as the defined in the activation schedule. After
each activation, the countries activations are moved to P.
INTERNAL – SAP and Customers Only 17
Multi-Country Rollout with Config. Localization Tool
only available for selected early adopter customers

• Refer to the SAP Note

3107866 - SAP Central Business Configuration : Configuration Localization Tool restricti
ons and limitations
to check the current limitations, restrictions, and additional information for using CLT.
• Create localized business configuration for a target country/region in an
implementation project, by inheriting as much as possible from a source country/region
provided by SAP, in combination with Configuration and Extensibility.
• Also check that SAP has provided the system language for the target country, if
language is also a requirement from the customer.
• Currently Germany is only available as Source country. In future SAP will release more
countries to be source country to have more regional coverage.
• Fit to Standard have a very significant value when using CLT as implementation partner
is responsible for all the additional configuration and extension for the nonlocalized
country, that should match all the local and legal requirements.
CLT – Configuration Localization tool Kit

INTERNAL – SAP and Customers Only 18

Thank you.

© 2024 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material.
 Sample Questions Received

 What is relevant for a template coming from wave 1 and how to build a template for wave 2 and further
waves?

• Activate Accelerator Configuration Activity.xlsm

 What must be part of a template, what should be part of a template?

• Must be = Global + mandatory localized. Should be = recommended and optional localized

 How to align with the releases and updates?

• Project plan should consider major releases so the testing (UAT) happens with the new release

 Is there a tool for CBC that would allow to see what SSCUI were updated during Wave 1?
• CBC Activity status “Completed” + CALM custom status. 5 countries can be initiated per transport. However, avoid ‘packing’ transports to
reduce risk of performance issues etc.

 What is the recommended process of activating new Countries in CBC?

• CBC in phase = scoping

 How to identify most used apps in Wave 1 countries in Production or reporting to indicate if particular app
was used
• Internal SAP tools & some usage analysis possible via SAP for Me, also within the Product.
INTERNAL – SAP and Customers Only 20