Configuring with SAP Central Business Configuration

Objectives
After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Get an introduction to SAP Central Business Configuration
  • Review the system landscapes and setup activities
  • Identify characteristics of the implementation project experience
  • Activate scope, countries, and define the organizational structure
  • Define configuration values for the business processes
  • Complete the production system settings

Introduction to SAP Central Business Configuration

Introduction to SAP Central Business Configuration

SAP Central Business Configuration is a tool that will make it possible to configure business processes spanning different SAP cloud solutions from one central place. Currently, SAP Central Business Configuration supports the system provisioning and configuration of SAP S/4HANA Cloud, public edition since January 2021. The future vision is for SAP Central Business Configuration to support implementation of all solutions in SAP’s Intelligent Enterprise to enable end-to-end provisioning and configuration of solutions such as SAP SuccessFactors, SAP Ariba, and others. 

Solution characteristics:

  • Built on the foundation of SAP Best Practices for SAP S/4HANA Cloud preconfigured business process content.
  • Scoping via Business Adaptation Catalog (BAC) & end-to-end processes.
  • Quick access to a preconfigured, ready-to-run system.
  • Option to adapt preconfiguration to customer needs
  • Extended configuration for areas not equipped with preconfiguration content.
  • Enable delta deployment of scope extensions (for example, additional countries/regions with preconfiguration).

Components of SAP Central Business Configuration

SAP Central Business Configuration aims to increase business process flexibility, reduce time to value and total cost of ownership, and support roll-out of business processes in smaller iterative steps.

SAP Central Business Configuration consists of the following components; select each component to read more.

Configuration Process Overview

SAP Central Business Configuration enables you to manage your configurations for SAP cloud implementations and ongoing operations centrally via the Project Experience.

The guided workflow process steps include:

  1. Scope: Select the scope items (business processes) and countries in which to activate them, then assign systems as the deployment targets.
  2. Organizational Structure: Specify primary finance settings such as group currency and fiscal year variant, set up the organizational structure, and deploy the settings.
  3. Product-Specific Configuration: Carry out configuration activities to define business processes and release transports to the target systems. The configuration activities visible are based on the active scope.
  4. Production System Settings: Maintain current settings in the productive system such as bank accounts for company codes and financial statement versions.
    Note
    Releasing transports and maintaining the production system settings only occurs in a 2-system landscape. In a 3-system landscape, these activities are handled in SAP S/4HANA Cloud. In addition, there is no Production System Settings phase in SAP Central Business Configuration for a 3-system landscape.

Maintaining SAP S/4HANA Cloud after Go-Live

SAP Central Business Configuration is used to continuously maintain SAP S/4HANA Cloud after go-live. For example, if a new business process is released, a customer will start at the beginning of the workflow to first select the scope to activate, make any changes or additions to the organizational structure (if necessary), complete the relevant configuration activities, and finally maintain any necessary production system settings. The workflow ensures all required steps are completed for new scope to be successfully activated.

Important Dates & Milestones

Customers who implemented SAP S/4HANA Cloud prior to January 2021 still use the Manage Your Solution and Configure Your Solution Fiori apps in their SAP S/4HANA Cloud system to maintain configuration values for different business processes. These customers will be contacted by SAP individually to schedule their conversion to SAP Central Business Configuration. Conversion is executed by SAP and will not affect the customer’s existing configuration. After the switch, all future configuration changes, such as activating new business processes or countries will take place in SAP Central Business Configuration.

Customers who implemented SAP S/4HANA Cloud after January 2021 received an SAP Central Business Configuration system along with their Quality and Production systems. These customers have a 2-system landscape (2SL), referring to the Quality and Production systems.

In September 2022, the ability to have a third system landscape with development capabilities became available. The development system is called the SAP S/4HANA Cloud ABAP Environment. Customers who implemented SAP S/4HANA Cloud after September 2022 received an SAP Central Business Configuration system along with their Development, Test (formerly Quality), and Production systems. These customers have a 3-system landscape (3SL).

The following training information will explain how to provision SAP S/4HANA Cloud system landscapes, activate business processes, and define the organizational structure and product-specific configurations for both 2SL and 3SL scenarios.

Old Configuration Method vs. New Configuration Method

Prior to SAP Central Business Configuration, the Manage Your Solution and Configure Your Solution apps in the SAP S/4HANA Cloud Fiori launchpad were used to complete configuration activities. Customers that implemented SAP S/4HANA Cloud prior to January 2021 will continue to use this method to maintain their systems until their systems are converted by SAP. Until all customers are converted to SAP Central Business Configuration, the Manage Your Solution app will not be removed from the launchpad.

Embedded User Assistance

User assistance is accessed through the question mark icon in the top right corner of the SAP Central Business Configuration system. You will find:

  • In-app help: On-screen "hot spots" describing elements of the user interface with links to detailed information and tutorial videos.
  • SAP Help Portal links: Application help with interactive graphics, concepts, task descriptions and tutorial videos.

Additional Resources:

  • SAP Central Business Configuration in the SAP Help Portal
  • SAP Central Business Configuration in the SAP Community
  • SAP Central Business Configuration free training on openSAP
  • SAP Central Business Configuration Learning Journey (SAP Learning Hub subscription required)

Try it out

Access the SAP Central Business Configuration In-App Help.

System Landscapes

SAP Cloud ALM & SAP Central Business Configuration

SAP S/4HANA Cloud is the system where your enterprise business data lives. SAP Central Business Configuration is a separate system that lives in SAP Business Technology Platform where you provision your systems, activate the business scope, and complete configuration-related activities. Both systems are integrated with the customer's SAP Cloud Identity tenants. SAP Cloud Identity Services includes two tenants: Identity Authentication Service (IAS) and Identity Provisioning Service (IPS).

SAP Cloud ALM is used by implementation consultants and customers to manage the project implementation tasks of SAP S/4HANA Cloud and complete the regular system maintenance tasks after go-live. The implementation tasks are populated from the SAP Activate Roadmap tasks for SAP S/4HANA Cloud. An integration can be set up between SAP Cloud ALM and SAP Central Business Configuration to allow you to navigate directly to the SAP Central Business Configuration in relevant tasks. The customer's IT organization also uses SAP Cloud ALM as a powerful tool to monitor the health of all systems in the integrated landscape.

SAP Central Business Configuration Release Upgrades

SAP Central Business Configuration is its own individual product with a feature roadmap independent from SAP S/4HANA Cloud and other SAP Cloud solutions. The current focus is on each SAP Central Business Configuration release providing enhancements to the configuration capabilities for SAP S/4HANA Cloud. In the future, additional SAP Cloud solutions will be included.

Because SAP Central Business Configuration is an independent product, release features will not be published with the RISE with SAP S/4HANA Cloud content. Instead, refer to the What's New information in the dedicated SAP Central Business Configuration Help Portal webpage.

SAP Central Business Configuration and SAP S/4HANA Cloud 2SL

In SAP S/4HANA Cloud implementations, first a starter system is deployed with preconfigured organizational and product-specific data that aligns directly with the test scripts for different business processes on SAP Best Practices Explorer. The purpose of this system is for consultants to demonstrate the business processes to customer experts who do the relevant job tasks in each LoB to determine if there are any special customization requirements and to gather the data necessary to set up the customer's future SAP S/4HANA Cloud systems.

SAP Central Business Configuration is used to activate content in the starter system. First, you create a dedicated workspace for the starter system, called the Evaluation Project. Next, you follow the guided workflow activities in SAP Central Business Configuration to activate the predefined scope, organizational structure and product-specific configuration to complete the set-up of the starter system. After the starter system is activated, you can log into the system to create users and assign permissions for members of the implementation team to use the system to demonstrate to customers and gather configuration data.

In the 2-system landscape (2SL), the customer's actual SAP S/4HANA Cloud systems are called quality and production. The starter system is ultimately decommissioned after quality and production are configured, because it's no longer necessary. In SAP Central Business Configuration, you create a dedicated workspace for the quality and production systems, called the Implementation Project. Next, you follow the guided workflow activities in SAP Central Business Configuration to trigger provisioning of the SAP S/4HANA Cloud systems, activate the customer's actual scope, build their unique organizational structure, and configure their product-specific configurations. These tasks occur first in the quality system, then are transported to the production system. These transports are triggered in SAP Central Business Configuration.

In a 2-system landscape, the Implementation Project in SAP Central Business Configuration consists of the following phases:

  • Scope and Organizational Structure: define business scope, define primary finance settings, setup organizational structure, and request activation of license-dependent business scenarios.
  • Product-Specific Configuration: perform configuration activities, request production system, and release configuration to production system.
  • Production System Settings: perform required configuration activities that must be done directly in the production system.

Learn about Initial System Access for SAP S/4HANA Cloud in your 2-system landscape.

SAP Central Business Configuration and SAP S/4HANA Cloud 3SL

The 3-system landscape (3SL) refers to the addition of a development system, called the SAP S/4HANA Cloud ABAP Environment. Another relevant change is the quality system has been renamed to the test system. The concept is still the same, meaning the test system is used to test out configurations or extensions before transporting to production; this is simply a name change.

A development system is unique in that it has two different tenants with different purposes. Another term for tenant is client. A client is an organizational unit in the system with specific user master records and authorizations. The development tenant/client is used by developers with expertise in ABAP code, because ABAP is the coding language SAP uses for its software. For example a developer could build a new SAP Fiori app in the development system and assign the app to a business catalog to make it accessible to users in the customizing tenant. An administrator in the customizing tenant could then create a new business role for this new app, or assign the app to an existing role and move the app with it's permission to the test system for further analysis. If the app passes further testing in the test system, it would then be transported to the production system for productive use.

Development objects, such as a custom app are built in the development tenant, but can be accessed in the customizing tenant if permission is granted. This is because development objects are stored in database tables without a client column. These objects are therefore client-independent and are accessible by other clients/tenants.

However in the customizing tenant, you could create a business role and that role would not be accessible in the development tenant. This is because master data and transactional data is stored in database tables within a client column for the customizing tenant. This data is client-dependent, meaning it is only accessible in the respective client/tenant.

With the introduction of a development system, there comes a need to have two separate workspaces in SAP Central Business Configuration to handle the two different tenants/clients. The Evaluation Project is still created specifically to contain the Starter System, and the Implementation Project is still created to contain the customer's actual SAP S/4HANA Cloud systems, including development, test, and production. Data from the starter system can be moved to the development system through abapGit, an open source developed Git client for the ABAP server to import and export ABAP objects between ABAP systems.

The development tenant (also called Client 080) in the development system is used for developer extensibility, meaning ABAP experts working with ABAP code. The customizing tenant (also called Client 100) in the development system is used for business configuration and key user extensibility. Business configuration refers to activating content, building the organizational structure and defining product-specific configuration in SAP Central Business Configuration and transporting those configurations to the SAP S/4HANA Cloud customizing tenant in the development system. In the customizing tenant, you can also use the in-app extensibility tools, such as Custom Fields, Custom Logic, Custom Business Objects, and others to build lifecycle-stable extensions with the SAP Fiori apps. Transports from the Implementation Project workspaces to the development system occur in SAP Central Business Configuration. Transports between the development system, test system, and production system are handled with SAP Fiori apps in SAP S/4HANA Cloud to export and import software collections.

In a 3-system landscape, the Implementation Project in SAP Central Business Configuration consists of the following phases:

  • Scope and Organizational Structure: define business scope, define primary finance settings, setup organizational structure, and request activation of license-dependent business scenarios.
  • Product-Specific Configuration: perform configuration activities, request production system, and release configuration to production system.

Learn about Initial System Access for SAP S/4HANA Cloud in your 3-system landscape.

Try it out

Start the provisioning of your SAP Central Business Configuration, SAP S/4HANA Cloud, and SAP Cloud ALM tenants for 3-system landscape.

Set up and enable users for SAP Central Business Configuration using the Identity Authentication Service and Identity Provisioning Service.

Project Experience

Project Experience Overview

SAP Central Business Configuration is designed to provide guidance for your implementation project by controlling the sequence of activities that are completed. In the Project Experience, you can manage your team members, complete activities to set up and configure your systems, and view the project status. Activities are grouped into phases, and each phase ends with a milestone.

Milestones serve the following functions:

  • Trigger the change of project phases
  • Lock project activities of project phases that are currently not active
  • Trigger and control processes in the background to simplify the user experience

The Project Status lets you know the current state of your project and can give an indication of what activities are occurring in the backend. Project Statuses can be:

  • Active: the project is available or in use and project activities can be executed.
  • Closed: after the final milestone in the last phase has been completed, the project switches to ongoing operations mode where it is locked for changes, but remains active. This mode still allows you to perform manual rework, maintain current settings, or use the Initiate Change functionality to move the project to a previous stage.
    Note
    Ongoing operations mode is not displayed in the user interface.
  • Decommissioned: this status is used for the evaluation project when it is no longer necessary and can be decommissioned.
  • Setup: the project is being initially set up, upgraded, or there are operations being performed by the SAP Support team.

Try it out

Navigate the Project Experience and interact with the user interface in SAP Central Business Configuration

One-time Login Message

On the initial login to SAP Central Business Configuration, each user will be presented with a one-time popup window, requesting users to click 'proceed' in order to acknowledge they have read and understood the provided information and hyperlinked privacy statement. Without clicking 'proceed', access to SAP Central Business Configuration will not be possible. Please refer to the popup message and the hyperlinked privacy statement for details.

Note
In order to click 'proceed', no certification is required by the user.

Project Phases & Switching Projects

For the Evaluation Project, the Scope, Organizational Structure, and Product-Specific Configuration phases are available. In the Implementation Project, these three phases are available, in addition to the final Production System Settings phase.

Note
The Production System Settings phase is not visible in a 3-system landscape project.

You can easily switch between projects and create additional projects. You can also move to an earlier phase by using the Initiate Change functionality. This allows you to unlock activities for an earlier phase and then sequentially move forward through the required activities. For example, after a customer goes live with SAP S/4HANA Cloud, a new business scenario (scope item) may be released in an upgrade they want to activate. The customer would use the Initiate Change functionality in SAP Central Business Configuration to move back to the Scope phase to activate the new scenario, then continue through the Organizational Structure phase (some scenarios may require additional organizational entities), the Product-Specific Configuration phase to complete any necessary configuration for the scenario.

Try it out

Perform evaluation project activities and create the implementation project.

Project Team

The Teams tab provides an overview of project team members and their specific project roles. Some activities, like scoping, can only be processed by one user at a time. This ensures the data is consistent. Other activities, such as defining the organizational structure and configuration of business scenarios (scope items) allow multiple users to work at the same time.

Systems and Deployment Targets

The Systems tab provides an overview of your systems and their provisioning statuses after scoping is complete. It allows you to request system provisioning, and you have the capability to release configuration settings to the productive environment.

The Systems tab only becomes visible if a deployment target has been assigned to the project. The deployment target is the system where the content you scope and configure in SAP Central Business Configuration should go. The deployment target is created and maintained in the backend by SAP, but in the Project Experience, a consultant or customer still needs to assign the target on the Deployment Targets tab. The assigned deployment target automatically sets up the corresponding technical business options in scope for the project.

Note
The Systems tab is not relevant for a 3-system landscape project, because transports between the development, test, and production systems are not managed in SAP Central Business Configuration, they are managed using the import and export software collection apps in SAP S/4HANA Cloud.

Logs

The Logs page provides detailed information on the changes performed in Project Experience. For audit purposes, it's important to have tracking and logging history in place that captures changes in project activities with the time, name, fields changed, and area.

Scope and Organizational Structure Activities

Select Countries/Regions

In SAP Central Business Configuration, you start scoping in the Project Experience area with the Define Scope project activity. You begin scoping by providing basic information about your company, such as the countries/regions and industry you operate in. The tool will propose relevant bundles and scenarios with predefined content. You can then further adjust the business scenarios in your solution. Built-in rules ensure that your selected content is logical and consistent from a technical and business point of view.

With SAP Central Business Configuration, customers are able to scope:

  • Countries in which the chosen business processes will run
    Note
    When defining your initial scope or using the Initiate Change functionality to define additional scope, we strongly recommend not to scope more than five countries or regions at a time.
  • Predefined scenario bundles
  • Additional non-standard scenarios

Select Bundles/Scenarios

You first select a bundle that includes many scenarios (scope items) grouped into a package. Additional scenarios can be added after selecting a bundle. License-dependent and non-standard scenarios show a "lock" icon because they need to be requested. Within a bundle or scenario, you can choose which country/region to activate the scenario in. The documentation of each scenario provides a link to SAP Best Practices Explorer for additional information.

Select a Group Ledger Scenario

You must choose a group ledger scenario when defining the initial scope. The two choices are:

  • Accounting and Financial Close - Group Ledger IFRS (International Financial Reporting Standards)
  • Group Ledger US GAAP (United States Generally Accepted Accounting Principles)

Review Scoping Selection

My Selected Scope provides an overview of all business scenarios (scope items) you have chosen. You have the ability to filter scenarios by country/region.

Request License-Dependent or Non-Standard Scenarios

You must request license-dependent scenarios from the SAP Service Center by creating a case. Selecting the Open button in this activity brings you to SAP Best Practices Explorer to find the relevant app IDs and scope item information.

Note
Find information on requesting SAP S/4HANA Cloud license-dependent or non-standard scenarios in SAP Help Portal.

Try it out

Add countries/regions, bundles, and scenarios to your scope. Request license-dependent and non-standard scenarios via ticket.

Assign Deployment Target

This activity requires you to assign a deployment target for your system. The deployment target is created and maintained in the backend by SAP, but in the Project Experience, a consultant or customer still needs to assign the target. The assigned deployment target automatically sets up the corresponding technical business options in scope for the project.

Note
Once a deployment target is assigned, it cannot be decoupled from the assigned system.

Try it out

Assign a deployment target to your project.

Confirm Scoping is Completed Milestone

Relevant configuration activities are identified based on the scoping selection.

Try it out

Confirm that you've finished your scoping by completing the milestone.

Specify Primary Finance Settings

Next, you define the fiscal year variant and group currency. The fiscal year variant defines the number of posting periods in a fiscal year and how many special periods are needed. The group currency is used as the global currency and allows amounts to be compared in a single currency.

Note
The fiscal year variant and group currency are applied to the entire system and cannot be changed after confirmation.

Try it out

Define the fiscal year variant and group currency for your project.

Set Up Organizational Structure

The Organizational Structure app allows you to easily create and adapt your company's organizational structure (org structure). The selected scope defines which organizational entities are required to run the underlying processes. The system also runs consistency checks to ensure all organizational hierarchies contain the relevant entities (for example, every plant requires at least one storage location if logistics is in-scope), and that all required relationships are defined (for example, every distribution chain requires at least one plant to be assigned).

The following types of relationships exist between the units of an organizational structure:

  • Tree relation: Country-specific parent-child relationship (1:n). For example, plant to legal entity.
  • Additional relation: Relation of an organizational unit from a country-specific tree to another organizational unit of the same tree or to a global organizational unit. Additional relationships have an n:n cardinality, meaning each of the organizational units for which an additional relationship is possible may have an additional relationship with one or several organizational units.

Local Entity

Local entities are assigned to defined countries, and are the highest level of the organizational structure. Company is the root node and may have one legal entity as a child. Under legal entities, you can add these organizational units:

  • Sales Organization for Sales & Distribution
  • Plant for site logistics

Global Entity

Global entities can be assigned to enterprise structures in one or more countries. For example, a Shipping Point can be assigned to several Plants which are in more than one country. You can create the following types of global entities:

  • Distribution Channel
  • Division
  • Purchasing Organization
  • Sales Office
  • Shipping Point
  • Shipping Point for Raw Materials
  • Standard Shipping Point

Organizational Structure App Display Views

The Organizational Structure app allows you to easily create and adapt your company's organizational structure (org structure) with several different views:

  • Graphic view: Graphical, scope-dependent, and guided creation of organizational units
  • Table view: All org units are listed in a table
  • Simplified mode: The buttons that guide you through the creation of new org units are hidden in this mode to gain a better overview of your org structure
Note
Non-confirmed entities are in the "staging" area, where they can be easily changed or deleted. Make sure you confirm only the units you want to deploy to the back-end system. Once confirmed, the entity cannot be deleted!

Confirm Organizational Entities & Complete Milestone

When you are finished maintaining the organizational structure, select the Confirm button to confirm the entities, then complete the activity.

Try it out

Create organizational units and assignments between units, then confirm the organizational structure of your company.

Confirm the milestone to complete the first phase of your project and display information about the progress of the milestone confirmation.

Deploy Quality System

The Confirm Scope and Organizational Structure is Completed milestone initiates the installation of the Quality system. You can check the provisioning status of your systems from the Systems tab in SAP Central Business Configuration.

The provisioning statuses are:

  • Installing System: Triggered by completion of the Confirm Scope and Organizational Structure is Completed milestone.
  • Ready for initial deploy: System installation is complete and ready to receive the initial business configuration deployment.
  • Installing content: Content is being deployed and the progress is visible with a progress bar in the Operation Status column.
  • Activating: When the deployment progress reaches 100%, the status changes to activating. Activation can take approximately 4-5 hours, depending on the scope.
Note
This activity is not relevant for a 3-system landscape project.

Product-Specific Configuration Activities

Request SAP S/4HANA Cloud Production System

In the Product-Specific Configuration phase, the Production System can be requested from the Systems tab. In weekly sprints, configuration of business scenario (scope item) data should take place in SAP Central Business Configuration. At the end of each sprint, the configuration is released to the quality and production systems through a transport. Configuration activities during this phase enable you to define detailed settings for the business scenarios.

As with the Quality system, the Production system must also be assigned to a deployment target.

Note
This activity is not relevant for a 3-system landscape project.

Try it out

Access the Systems tab and request the production system for a 2-system landscape project.

Initiate Change to an Earlier Phase (if necessary)

If you need to change or add something done in a previous phase, you can select the Initiate Change button in the upper right corner of SAP Central Business Configuration. You will then be prompted to choose the information you wish to change, for example, activating an additional country or business scenario (scope item).

Try it out

Initiate a change to enhance your scope, organizational structure, or configuration settings.

Configuration Activities

The configuration activities in SAP Central Business Configuration are designed to support customers in adapting the preconfigured SAP Best Practices content to their requirements. The available configuration activities are based on the active scope and country selections. Configuration activities may vary by country, because not all business scenarios (scope items) are available in all countries. Configuration activities can be mandatory, recommended, or optional.

Configuration Activity Types:

  • Mandatory: Must be configured. For example, organizational structure.
  • Recommended: Default content exists that a customer can use, but many will need to change the standard content or add their own content. For example, Chart of Accounts or Pricing.
  • Optional: Default content exists and most customers don't need to change the standard information. For example, Delivery Block Reasons.

Try it out

Configure a business process in a 2-system landscape by opening a configuration activity and making changes to the configuration settings.

Configure a business process in a 3-system landscape by adapting configuration settings, releasing transport tasks, and executing a transport request.

Activities Completed in Other Systems

Several activities during implementation are listed in SAP Central Business Configuration, but not actually completed within the configuration tool, such as data migration, business process testing, and integration setup. In these cases, the activity in SAP Central Business Configuration links to the most applicable area or information to complete the task.

For example, the Integration Setup activity in SAP Central Business Configuration links to the Integration Setup deliverable and corresponding tasks and accelerators in the SAP Activate Roadmap Viewer. The Business Process Test activity in SAP Central Business Configuration links directly to the Test Your Processes app in the SAP S/4HANA Cloud Quality or Test System.

Release Transports

Configurations done in SAP Central Business Configuration need to be transported to the SAP S/4HANA Cloud Quality (Q) system for testing, then the Production (P) system. On the Systems tab, you select the Release Transport button for the Q system. After the initial transport, you are able to release transports to the P system.

The Operation Status column provides a progress bar indicating the status of the transport.

Note
This activity, where transports are released on the Systems tab in SAP Central Business Configuration is not relevant for a 3-system landscape project. This is because there is no Systems tab in a 3-system landscape project. In a 2-system landscape, SAP Central Business Configuration is used to trigger transports of business configuration changes to the SAP S/4HANA Cloud quality and production systems. In a 3-system landscape, SAP Central Business Configuration only triggers the transport of business configuration content to the SAP S/4HANA Cloud development system. Further transports moving data between the development to test, and test to production systems are triggered in the SAP S/4HANA Cloud Fiori apps to export and import the software collection.

View Transport History

Each transport generates a log, where you can view the user that released the transport, transport description, and the date and time of the transport.

Try it out

Transport the business configuration into the production system of a 2-system landscape system, sign off phase deliverables, and confirm the milestone.

Production System Settings Activities

Production System Settings

Some configuration activities must be done directly in the production system. In the Production System Settings phase, maintenance of the current settings and relevant manual rework activities are completed. After all open activities have been completed, the last milestone is Confirm Production System Settings are Completed.

Note
This activity is not relevant for a 3-system landscape project, because there is no Production System Settings phase.

New features and business scenarios (scope items) will continue to be released with each SAP S/4HANA Cloud upgrade. Customers will use SAP Central Business Configuration to activate new scope and countries/regions, make additional configurations, initiate transports, and complete other configuration-related tasks to maintain their SAP S/4HANA Cloud systems.

Try it out

Maintain the current settings in the production system of a 2-system landscape project and confirm the milestone.

Save progress to your learning plan by logging in or creating an account