Professional Documents
Culture Documents
Sha 1
Sha 1
Sha 1
Key Objectives
▪ SAP Central Business Configuration conceived as
central configuration tool for the Intelligent
Enterprise, starting with SAP S/4HANA Cloud,
public edition
▪ Increased business process flexibility and reduced
configuration efforts
▪ Reduced time to value and total cost of ownership
thanks to faster implementation
▪ Flexibility through go-lives in smaller iterative steps
Guided SAP cloud Scope your solution – select Configure integrated end-to- Manage parallel projects
implementations countries/regions, business end business processes
processes, and solution across cloud solutions Manage company rollouts via
capabilities from SAP templates
Content
Fueled by SAP Best Practices preconfiguration content and the business adaptation catalog (BAC)
Organizational structures and other Parallel implementation projects are Start from a pre-scoped workspace
central configuration values are planned to be supported, along with (via processes, roles, industries,
stored and maintained only once, the deployment of configuration into functional capabilities) with fine-
centrally in SAP Central Business different data centers (template granular scoping allowing a higher
Configuration, and used across the approach) grade of preconfiguration, reducing
Intelligent Enterprise (IE) the need for configuration
open@sap.com
Follow all of SAP
www.sap.com/contactsap
SAP Central Business Configuration allows you to manage your configurations for SAP cloud implementations
and ongoing operations centrally via Project Experience.
Continuous Innovation
SAP Central Business Configuration is the tool that you use to carry out the configuration-related
tasks of the proven SAP Activate implementation methodology for SAP S/4HANA Cloud, public
edition.
All of the SAP Activate tasks are available in SAP Roadmap Viewer
(https://go.support.sap.com/roadmapviewer/).
SAP Central Business Configuration is the central place for customers and partners to look at SAP cloud business
processes, learn about their value, and select the suitable processes for their business.
Customers and partners can manage SAP S/4HANA Cloud, public edition implementation projects centrally, with the aim to
deploy the configurations to the target systems. The implementation project experience includes:
Scoping
▪ Scoping of the SAP S/4HANA Cloud, public edition solution
▪ Multi-country scoping
▪ Country-dependent scoping of non-standard scenarios
Configuration
▪ Configuration activities during the Product-Specific Configuration phase
SAP Central Business Configuration is intended to make project implementations for SAP cloud solutions easier and
more efficient, and enable customers and partners to run their projects more autonomously.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
The Project Experience app is the main user interface of SAP Central Business
Configuration and guides you through your evaluation and implementation
projects, as well as ongoing operations. Every project is structured into phases,
which contain specific activities that you need to carry out.
Prerequisites:
▪ You’ve requested the provisioning of your SAP
Central Business Configuration and SAP S/4HANA
Cloud tenants via SAP for Me
▪ You’ve finished the user setup and access via the
identity authentication service (IAS) and identity
provisioning service (IPS)
open@sap.com
Follow all of SAP
www.sap.com/contactsap
Context-sensitive
▪ Depending on your current screen
open@sap.com
Follow all of SAP
www.sap.com/contactsap
SAP Central Business Configuration ensures the consistency of the scope selection.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2
Scoping and deployment targets
What to scope
Scenarios that cannot be selected directly will be displayed with a grayed-out selection box and a lock.
On mouse-over, additional information on how can they be added to the scope is displayed.
Make use of the different filter options (Industry, Line of Business etc.) to be able to narrow down the results in
the Scenarios section.
Then you can use the Add All / Remove All buttons to easily add / remove the filtered selectable scenarios to
scope all at once.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11
Scoping and deployment targets
Features (3)
As well as country/region selection, you can select public sector scope for certain countries/regions.
For public sector projects, a specific Public Sector Management (PSM) bundle is available. It includes sector-
independent content from the private sector and content specific to the public sector. Optional scenario
selections are available on top of the bundle.
open@sap.com
Follow all of SAP
www.sap.com/contactsap
▪ The Organizational Structure milestone icon in the Milestones timeline turns to green and the project will
move to the Product-Specific Configuration phase.
▪ Configuration activities in the Product-Specific Configuration phase cover detailed settings of the solution
process.
open@sap.com
Follow all of SAP
www.sap.com/contactsap
open@sap.com
Follow all of SAP
www.sap.com/contactsap
▪ Business is more global and changing faster than ever. Customers want to
use SAP S/4HANA Cloud in the countries/regions in which they operate.
Localization
▪ SAP already provides localized business configuration for 51 countries/
makes a regions, with 8 more planned.
difference
▪ Big demand to be even more flexible in creating new countries/regions –
often requested by partners and customers.
Early Adoption
SAP Delivered Local Versions Customer Local Versions3 Program
Countries/ 51 1592
Regions Supported 8 more on roadmap1
landscape, first needed to be converted to 3-system landscape with CBC to utilize CLT(more specific timelines to be shared in due course; subject to change)
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4 May require additional subscriptions/licenses
4
Configuration Localization Tool
Localization as a self-service for SAP S/4HANA Cloud
Configuration Localization Tool1 (SAP Central Business Configuration) – Create Customer Local Versions Early Adoption
▪ UI field layout, custom forms and templates ▪ Develop custom ABAP code Integration with SAP BTP services
▪ Custom business objects ▪ Extensions of SAP S/4HANA Cloud solutions ▪ AI business services
▪ Custom CDS views ▪ Partner extensions ▪ Data marts and analytics
▪ Custom business logic using cloud BAdIs ▪ Directly on SAP S/4HANA stack ▪ IoT and Big Data
▪ Using CLT is a pure implementation approach. No features specific to the target country/region are delivered.
▪ Country-specific legal requirements need to be achieved with the generated localized configuration, the
configuration capabilities of the chosen source country/region, or by using the localization extensibility
possibilities to extend the solution.
▪ The localized business configuration is the responsibility of the partner or customer. This also applies to
keeping the solution legally compliant in the future (“legal changes”).
Currently, just Germany released as a source country. More countries/regions under evaluation
CLT is currently in early adopter mode (controlled shipment) – limited seats available
Currently, set of 400+ scope items are available with SAP S/4HANA Cloud 2308 release and more planned
open@sap.com
Follow all of SAP
www.sap.com/contactsap
Supporting 3500+ customers and partners in implementation and operations* * July 2023
SAP Cloud ALM provides the harmonized implementation experience for the Intelligent
Enterprise, covering all relevant SAP solutions for all customers
Build Test
Design Deploy
Open
Out-of-the-Box
Integrated
Cloud-Native Traceable
SAP Standard Content
Design
▪ Start with SAP Best Practices content to run your fit-to-standard
workshops
Cloud-Native
▪ Create own processes with integrated authoring capabilities
Out-of-the-Box ▪ Collect requirements as an initial backlog
Build
SAP Standard Content ▪ Based on the SAP Activate methodology with template roadmaps
for agile implementation projects
▪ Extended by your own tasks and user stories
▪ Integrated planning and reporting
Open Test
Integrated ▪ Manage all tests from user acceptance to regression
▪ Manual testing with test-step-based approach
Traceable ▪ Integration of automatic execution engines
Deploy
▪ Plan your releases and orchestrate consistent deployment to
production
▪ Enable change and provide traceability and audit trails
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
SAP Cloud ALM
Capabilities in detail
Go Live
Manual
Testing Deployment
Rich Text-Based Planning
Documentation Project & Task Test Integration of
Management Orchestration Test Automation Change Feature
Process Status & Approval*
Requirements Providers Enablement Delivery
Management Document Refinement Test
Management Defect Deployment
Project Planning
Integration* Configuration* Planning* Management Change Automation &
Task Distribution Documentation & Confirmation*
Extension Test
Task Templates Preparation Reporting
Fit-to-Standard Management*
Workshops Gantt Chart Traceability &
Integration
Audit Trail
Process Scoping Landscape Management*
& Viewer SAP Standard
Process Test Cases
Authoring Documentation Deployment
SAP Activate Test Execution Orchestration
Requirements Roadmaps
Collection
Project Execution
SAP Process & Tracking
Content
Project
Start
Continuous Innovation
SAP Activate
Discovery Fit-to-Standard Scope and Migrate, Integrate, Onboard and Operate, Monitor,
Access Analysis Configure Extend, Test Deploy Support
SAP for Me
Integrated Tools
SAP for Me
Based On Based On
▪ Business adaption catalog ▪ Intelligent Enterprise scenarios
open@sap.com
Follow all of SAP
www.sap.com/contactsap
Trigger Trigger
Tenant Tenant
SPC Setup
Handover
Setup
Handover
E-Mails E-Mails
Trigger
CBC On- Start
CBC boarding Project
… Content
Deploy
S/4HC
S/4HC Content
On-
Starter Activation
boarding
Manual Steps
▪ Customer needs to actively request the SAP Central Business Configuration by Customer
(for reasons of space abbreviated to CBC) and SAP S/4HANA Cloud (S/4HC) tenants
▪ Automated procedures in the service provider cockpit (SPC) do the provisioning and integration
▪ Handover e-mails for the CBC and S/4HC tenant are sent to the customer
▪ The S/4HC tenant is ready to use once the first content deployment is done
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
SAP S/4HANA Cloud 3-system landscape
Demo 1 – SAP for Me
Landscape
▪ 2SL: Starter, Q, P tenant all with client 100
▪ 3SL: Starter and DEV tenant with client 080 & 100,
TST and PRD tenants with client 100
▪ Only for 3SL: developer extensibility
▪ No client 050 / 051 for lifecycle calculation
SAP Central Business Configuration
▪ Overall two starter (new term: evaluation project) and
two implementation projects for Starter and DEV tenant
▪ Backsync only from Starter and DEV tenant
▪ No interaction with TST and PRD tenant
▪ No System tab but app for assigning deployment targets
SAP S/4HANA Cloud
▪ Transport from DEV → TST → PRD via ATO tool (Adaptation Transport Organizer)
Tenant Provisioning & Lifecycle
▪ Tenant provisioning always triggered by customers via SAP for Me
▪ Content update is triggered manually by customers after the SAP S/4HANA Cloud software upgrade is complete (will be improved with next
releases)
▪ Calculated only for Starter and DEV tenant (both clients)
▪ Customers are in charge of transporting settings to TST and PRD
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
Parallel Testing: A single line project does not facilitate parallel work. With parallel projects,
users can perform scoping, org creation, and configuration changes in parallel such that all
decisions made in the parallel project do not impact the ”main” line. For example, users can
validate CLT in a parallel line and accordingly decide if they wish to use the same scope in the
main line or discard the project if not required.
Traffic Distribution: The parallel project enables parallel processing, which reduces the traffic in
the single line.
Risk for Production: The parallel project provides the opportunity to test configuration changes
in parallel such that the user has the flexibility to move these changes to the main line (connected
to production) only if the tests were successful.
Note that the Parallel Project Line feature is not yet generally available.
Branching
Main Line
Product-Specific
Scoping Org
configuration
Project Line
▪ Main Line: This is the project via which configuration is deployed to the SAP S/4HANA Cloud development (dev) system that is connected
to the test system, which is further connected to production. Customers go live with the main line and work productively with it.
▪ Project Line: This is the project that is created as a “copy” of the main line, wherein the customer can add (extend) scope on top of what is
copied from the main line. Customers can also extend the org structure and perform configuration changes. The project line is connected to
the SAP S/4HANA Cloud dev, which is further connected to test but does not have any connection to production.
▪ Branching: This is the process by which the project line is created as a copy of the main line. The project line is created when the customer
is already in the state of performing configuration changes in the main line.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Parallel project line
Demo: Creating a project line
Project Line
Rebase
▪ Rebase: All changes done in the main line since the creation of the project line or the last merge are brought into the project line by this
process. It is a necessary step before moving changes in the project line to the main line.
▪ Merge: All changes done in the project line since the creation or the last rebase are moved into the main line by this process.
▪ Scoping Conflicts: Scope decisions made in the project line that invalidate or defy the scope decisions made in the main line are reported
as scoping conflicts.
▪ Configuration Conflicts: Configuration changes made in a configuration activity for the same record in both main line and project line,
such that the changes are not the same.
▪ Conflict Resolution: For successfully moving changes between project line and main line, it is mandatory to resolve the conflicts.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Parallel project line
Managing configuration conflicts
open@sap.com
Follow all of SAP
www.sap.com/contactsap
Unit 1: Vision Unit 2 – 7: Project Experience and its tools Unit 12: Outlook
Strengthen
Provide further
Project Experience
Capabilities for Partners
Processes
▪ Org-dependent scoping
Org Setup
▪ Mass handling and copy functionality
…
SAP Central Business
Configuration
1st
SAP S/4HANA Cloud
Today
a one-off copy of an SAP-provided
localization to a country/region outside
SAP’s localization scope
SAP S/4HANA Cloud Quality System SAP S/4HANA Cloud Dev. Quality System
Lifecycle Layer Lifecycle Layer
Active Configuration Active Configuration
Transactional & Master Data Transactional & Master Data
SAP S/4HANA Cloud Prod. System SAP S/4HANA Cloud Prod. System
Active Configuration Active Configuration
Transactional & Master Data Transactional & Master Data
* Applicable only for customers who started their SAP S/4HANA Cloud journey prior to the availability of SAP Central Business Configuration
open@sap.com
Follow all of SAP
www.sap.com/contactsap