SAP S/4HANA Cloud, public edition
Customer Local Version Early Adoption Program
Hemanth Garg, SAP
INTERNAL – SAP and Partners Only
Download Latest Deck
Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.
INTERNAL – SAP and Partners Only 2
Customer Local Version
Customer Local Version Early Adoption Program
Extend the coverage of the SAP S/4HANA Cloud, public edition to additional 160 countries/regions
Configuration Localization Tool: Create customer local version using Germany’s reference Localization as a
content and further country/region-specific adaptation of content with SSCUIs self-service for
SAP S/4HANA
Other Localization Extensibility features: Develop country/region-specific functions required toCloud
manage legal requirements and changes
Early Adopter Application and Approval Process
(2 options)
Pre qualified for Approval in DDA After Contract Signage
EA Program Benefits:
Fast Track
Enablement & Guidance Fast Track criteria* fully met Fast Track
Prospects Formal Approval
Early (before GA) usage of CLT Regular Track
Fast Track criteria* not fully met
Close collaboration with Product experts
Help shape the solution
Regular Track
Customers Formal approval
* No showstopper in release restrictions, agree with risk mitigation approach, no missing scope
INTERNAL – SAP and Partners Only 3
Venezuela: Get approval from SAP Export Compliance & Legal before proceeding with the deal execution
EA Approach for Prospects & Customers
Pre-Qualification during DDA Qualification – Quick formal approval after deal closure
PROSPECTS CUSTOMERS
Pre-Qualified for Approval
Formal Approval
(Auto)
Meet Pre-Qualification criteria for Fast Track via DDA Have received Pre-Qualification during
No missing Scope in “Scope Localization Matrix” in Localization DDA review
Section of DDA Seek approval by sending email
Fast Track
Fast Track
No other show-stopper identified from release restrictions
Agree with risk mitigation approach
Quick Formal Approval (Quick Formal Approval.msg)
Register using link (SAP employees) or send registration Onboarding of customer to EA
email (Partners) with questionnaire to get pre- Program
Deal
qualification Product experts assigned
New Customer Local Version EA Program Request for S_4HANA Cloud_ public edition (Prospect) .msg
Closure
Periodic feedback to EA Program team
Pre-Qualified for Approval
Formal Approval
(Manual review)
(Without Pre-qualification Approval)
Pre-Qualification criteria for Fast Track via DDA not met
Regular Track
Reg Approval
Trigger Brand Guardian Review (Consulting with EA
Program team) to confirm on missing scope item
guidance and risk mitigation approach
See Details
Register using link (SAP employees) or send email
(Partners) with questionnaire to get pre-qualification
New Customer Local Version EA Program Request for S_4HANA Cloud_ public edition (Prospect) .msg
INTERNAL – SAP and Partners Only 4
Venezuela: Get approval from SAP Export Compliance & Legal before proceeding with the deal execution
Formal Approval – Other Scenarios (Existing customers etc.)
Formal approval after agreement on risk mitigation
2
Formal Approval – Customers with ongoing/live projects
(Without Pre-Qualification Approval)
NOT received pre-qualification during DDA review
Analyze scope coverage (availability of requested scope) and agree on way forward when scope
is missing
Regular Approval
Availability Check
Agree with SAP’s risk mitigation approach
Seek approval by sending email along with scope coverage analysis
Formal Approval_ Customer Local Version EA Program Request for S_4HANA Cloud_ public edition (Customer) .msg
Onboarding of customer to EA Program
Product experts assigned
Periodic feedback to EA Program team
Venezuela: Get approval from SAP Export Compliance & Legal before proceeding with the deal execution
INTERNAL – SAP and Partners Only 5
Risk Mitigation for Customer Local Version Development
Step 1: Simulate & Test Customer Local Version* Step 2: Develop Customer Local Version
Partner Cloud test, demo, a
nd development
CBC for SAP S/4HANA Cloud,
one system landscape (
FAQs)
(3 months min subscription)
Option 1: Partner Environment CBC S/4HANA Cloud, public edition
SAP Demo data should not be installed (3-system landscape)
OR
SAP S/4HANA Cloud, public
Customer Production Environment
edition, sandbox tenant
CBC (SKU# 8014491)
(3 months min subscription but
need approval from DL)
Option 2: Customer Sandbox Environment *Mandatory to participate in projects wherein customer is already live with
SAP Demo data should not be installed SAP S/4HANA Cloud or has other SAP standard local versions as part of
INTERNAL – SAP and Partners Only
current rollout plans. Refer to guidance for further reasoning. 6
Customer Local Version Early Adoption Program
Challenges and Guidance
Challenges Understanding of legal requirements of the target country and to judge if this can be achieved with localization as a self-service for SAP
S/4HANA Cloud
Rolling back development of customer local version in the production environment
Guidance
Only SAP S/4HANA Cloud, public edition customers with 3-system landscape (3SL) can participate. Others, see field guidance here.
Developing customer local versions has two distinct steps – creating local version from Germany local version’s reference content using CLT and covering
legal requirements with other localization extensibility features available with localization as a self-service for SAP S/4HANA Cloud
Review Commercial Considerations and plan for any additional subscriptions accordingly
CLT: Careful preparation and consideration when developing a new customer local version on project basis
Till SAP releases parallel project configuration environment (in development) supporting reset and merge to main production configuration environment,
SAP requires either implementation partner to subscribe to new partner Test, Demo & Development (refer FAQs on CLT activation instructions) OR
customer subscribe to 3SL sandbox tenant (SKU# 8014491 – min 3 months subscription required, get approval from DL).
Mandatory for customer who is already live or have rollout plans with any other SAP delivered standard local versions rollout in the wave 1.
SAP wants to avoid any impact to their production environment and project timeline in case of running into any issues with development of customer
local version. Please note that once the country is activated in the production environment, SAP cannot purge, delete or conceal the respective
countries.
Project has to further adapt specific settings such as currency settings, fiscal year variants, organization structure & assignments, taxes, payments etc. for
these customer local versions
Understand the release restrictions in the note 3107866 for the supported list of countries and supported scope items with CLT.
Localization Extensibility: Customer owns clear responsibility/accountability for the complete collection of legal requirements required, development and
changes for the customer local version
Plan to define these requirements early in the project with your legal and business teams
Ensure project team has good understanding of localization as a self-service for SAP S/4HANA Cloud (Learning: OpenSAP for CBC,
SAP Learning on SAP S/4HANA Cloud extensibility and Developer Extensibility)
Validate legal requirements can be managed with localization as a self-service for SAP S/4HANA Cloud
INTERNAL – SAP and Partners Only 7
Key Resources
Overview Before You Start Technical Guides
L2 Deck – Localization as a Self-Service CLT Restrictions and Limitations Project Experience
for SAP S/4HANA Cloud, Project Experience: Configuration Locali
public edition Partner Test & Demo Development zation Tool
System (TDD) FAQs
Configuration Localization Tool – Introdu Localization as a Self-Service help docu
ction Video mentation guide
Field Guidance on Localization
| Demo
Localization as a self-service
Learn More Engage with Us
CLT Overview Tutorial Register for Live Sessions | SAP Learn
ing Hub
Partner FAQ - SAP S/4HANA Cloud Localization
Localization as a self-service for SAP
Leveraging SAP S/4HANA Cloud with SAP Central S/4 HANA Cloud Community
Business Configuration |
openSAP Course
What’s new | Video Tutorials
Stay current | Learning Journey
INTERNAL – SAP and Partners Only 8
Appendix
Commercial Considerations
SAP S/4HANA Cloud subscription based on 3SL SKUs (base or premium option)
Addon subscriptions of any priced scope items that is part of implementation scope and supported by
CLT as outlined in the release restrictions note
Extensibility – most built-in tools (key user and developer extensibility along with Configuration
Localization Tool) are included with SAP S/4HANA Cloud base subscription but there are some additional
subscription required to use certain tools outlined in localization as a self-service for SAP S/4HANA Cloud
to cover last mile localization
SAP Document and Reporting Compliance SKU# 8013658 may be required to access design time
environment to develop statutory reporting or e-invoicing solution
BTP subscription (optional) may be required if you intend to use side-by-side extensibility
Digital Access (optional) may be required if you need to create documents (refer
service description guide on SAP Trust Center for SAP S/4HANA Cloud, public edition) using
custom app or 3rd party app beyond what is included with SAP S/4HANA Cloud subscription
INTERNAL – SAP and Partners Only 10
Use Slide Show
SAP S/4HANA Cloud Customer Local Versions1
Configuration & Extensibility
Localization as a
Localization Extensibility Examples
self-service
CBC Key User Developer2 Custom Document & Custom
Payment APIs
Number Reporting Business
Formats
Range Compliance3 Logic Business Technology
Platform3
3. Develop country-specific
1. Configuration Localization Tool 1
33 Languages functions using built-in tools
Customer Local Version
2. Further
Adaptations
Pre-Configured Country/Region-specific
Scope Items
Content Localizations
1
In early adoption program and only 3SL customers can participate
INTERNAL – SAP and Partners Only
2
Only available for 3SL installations 11
3
May require additional subscription
SAP S/4HANA Cloud Localization
SAP Delivered Vs Customer Local Versions
SAP Delivered Local Versions Customer Local Versions1,3 Early Adoption
Program
Countries/Regions 59 1602
Supported
Languages 33 Use SAP delivered languages
Best Practice Included Derived (Country-specific adaptation via SSCUI)
Preconfigured Content Country-specific content Included Use SAP CBC – Configuration Localization Tool 3 (part of
localization as a self-service for SAP S/4HANA Cloud) to create
Further adaptations via Self-Service Configuration UI
(SSCUI) configuration content by copying/transforming from a selected
“source” local version – see scope item list supported
Further adaptations via SSCUI
Country/Region-Specific Included4 Use
localization as a
Not Included
Functions Meet a wide range of local financial
reporting standards, legal frameworks, tax
self-service for S Use localization as a self-service for SAP S/4HANA Cloud
AP S/4HANA Cl to manage regulatory requirements
calculations, logistics scenarios(eWay Bill, oud
stock transfer), customs forms, electronic to further
document exchange and statutory extend/adapt on
reporting requirements as mandated by project-basis
regulatory authorities
Provide Legal Changes SAP Customer Customer
1
Refer to roadmap for specific timelines, subject to change
2
Belarus, embargo countries and SAP delivered/planned Local Versions are excluded. .
3
INTERNAL – SAP and Partners Only Currently in early adoption program for customers with 3-system landscape environment. Review guidance and qualifying criteria for participation. Current customers using solution 12
builder or CBC with 2-system landscape, first needed to be converted to 3-system landscape with CBC to utilize CLT. Refer to FAQ for more details.
4
May require additional subscriptions/licenses. Refer to help document on legal requirements that is included with local versions.
SAP S/4HANA Cloud, public edition
3-system landscape Overview
SAP S/4HANA Cloud, public edition with 3-system landscape (3SL) is an installation option wherein SAP provisions 3
systems namely a Development (DEV), Test (TST) and Production (PROD) system. This separation makes it possible
to have advanced development projects, enabling developer extensibility options.
• Development System: Provides safe environment
for implementation and development projects that
include advanced coding projects
• Test System: Test your custom implementation and
development before rolling out to production system
• Production System: Productive work environment
with the required and tested configuration and
development to run your business
• SAP Central Business Configuration: Central
tool connected to your development system, used for
scoping, organizational setup and configuration.
• Environments:
• Main Line: Primary scoping and configuration activities based on SAP reference content are carried out in the customizing tenant and are made available
subsequently to test and production tenants using transport management
• Development Line: Additional environment with a development tenant that provides access to build your own development extensions based on lifecycle
stable SAP objects
• Parallel Project Line (in development, subject to change): The end state architecture will include an additional configuration environment to support parallel
projects that may have different go-live dates or to implement customer localizations (currently in early adoption program)
INTERNAL – SAP and Partners Only 13
Follow all of SAP
www.sap.com/contactsap
© 2022 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
