PUBLIC

SAP Central Business Configuration

2024-10-28

Project Experience
© 2024 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Project Experience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Shell Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Standard Roles and Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Standard Authorization Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Status Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4 Project Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Evaluation Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Implementation Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Working with Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
1.5 Scoping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Country/Region-Specific Scoping and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Variant Operating Chart of Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Defining Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Confirming Scoping Is Completed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
1.6 Deployment Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Deployment Targets in a 2-System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Deployment Targets in a 3-System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Assigning a Deployment Target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
1.7 Specifying Primary Finance Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
1.8 Organizational Structure Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Organizational Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Setting Up Organizational Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
1.9 Completing the Scope and Organizational Structure Phase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
1.10 Configure Your Business Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Changing the Status of Configuration Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Searching for Configuration Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Performing Configuration Activities and Calling Up Setup Instructions . . . . . . . . . . . . . . . . . . . . 69
1.11 Deployment to the Production System (2-System Landscape). . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Requesting the Production System (2-System Landscape). . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Assigning a Production System (2-System Landscape). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Releasing Configuration into Production System (2-System Landscape). . . . . . . . . . . . . . . . . . . 73
1.12 Completing the Product-Specific Configuration Phase (2-System Landscape). . . . . . . . . . . . . . . . . 74
1.13 Maintaining Current Settings in SAP S/4HANA Cloud Public Edition Production System. . . . . . . . . . 75

Project Experience
2 PUBLIC Content
1.14 Performing Manual Rework (2-System Landscape). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
1.15 Completing the Production System Settings (2-System Landscape). . . . . . . . . . . . . . . . . . . . . . . . 76
1.16 Changes via Edit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Editing Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Editing Organizational Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Editing Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
1.17 Change Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
1.18 Lifecycle Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
1.19 Product Feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

2 Accessibility Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

3 What's Changed in this Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Project Experience
Content PUBLIC 3
1 Project Experience

In SAP Central Business Configuration, you can centrally manage new implementations of SAP cloud solutions.

This user guide walks you through the entire implementation process step by step.

Process Flow

• Defining Scope [page 41]

• Evaluation Project [page 12]
• Implementation Project [page 18]
• Working with Projects [page 23]
• Defining Scope [page 41]
• Specifying Primary Finance Settings [page 54]
• Configure Your Business Processes [page 66]
• Setting Up Organizational Structure [page 61]
• Assigning a Deployment Target [page 53]
• Requesting Quality System (2-System Landscape) [page 17]
• Releasing Configuration into Production System (2-System Landscape) [page 73]
• Working with Projects [page 23]

Project Experience
4 PUBLIC Project Experience
• Project Management [page 11]
• Scoping [page 29]
• Organizational Structure Management [page 55]
• Configure Your Business Processes [page 66]
• Deployment to the Production System (2-System Landscape) [page 70]
• Lifecycle Management [page 81]

About Project Experience in a 2-System Landscape and 3-System Landscape

2-System Landscape 3-System Landscape

Phases • You have three phases: You only have two phases:

• Scope and Organizational • Scope and Organizational Struc-

Structure ture
• Product-Specific Configura- • Product-Specific Configuration
tion
• Production System Settings

Project Types You work with two projects: You work with four projects:

• One evaluation project

• Two evaluation projects
• Two implementation projects
• One implementation project

Deployment Target [page 45] In the Deployment Targets app, you In the Deployment Targets app, you
assign a deployment target to your assign a deployment target to your
project for each system (starter, quality, project for the following systems:
and production).
• Starter system: You assign one
starter customizing tenant and one
starter development tenant.
• Development system: You assign
one customizing tenant and one
development tenant.

Systems In Systems, you need to carry out the Systems is not displayed since its re-
following: lated activities are handled outside SAP
Central Business Configuration.
• Request systems (quality system,
production system)
• Release configuration settings into
the production system (Q2P)

Ongoing Operations After completing the last milestone The project remains open in the Prod-
Confirm Production System Settings Are uct-Specific Configuration phase. The
Completed, the project switches to on- project will not close or switch to ongo-
going operations mode. ing operations.

For more information on system landscapes in SAP S/4HANA Cloud, see System Landscapes in SAP S/
4HANA Cloud.

 Note

Please contact your SAP account executive to check the availability of the 3-system landscape.

Project Experience
Project Experience PUBLIC 5
Related Information

Evaluation Project [page 12]

Implementation Project [page 18]
Phases, Activities, and Milestones in an Evaluation Project [page 14]
Phases, Activities, and Milestones in an Implementation Project [page 19]

1.1 Shell Bar

The shell bar is on the top of the screen and gives you access to various functions.

The following table lists the standard icons available in the shell bar.

Icon Name Description

SAP logo Displays the SAP logo. If you choose it, you return to the Overview page.

Menu Expands or collapses the navigation pane.


Help Activates or deactivates the in-app help (SAP Companion). When activated, the
 help panel appears. You can also use F1 to open or close the help.

Built-In Support Provides an embedded support experience. You can access recommended con-
 tent and search for additional documentation. You can also report an issue
directly to SAP.

Product Feedback
 Launches a product feedback survey about SAP Central Business Configura-
tion.

 Notifications Opens the Notifications area with more notification details related to your
project.

The icon also shows a badge with the number of new notifications you have
received.

Profile Opens the user actions menu where you can access the following.

• Settings: You can choose your theme and view your roles and logon lan-
guage (system language is English).
• About: You can find general information about the project, application, and
system.
• Sign Out: You can sign out of the system.

Help Panel (SAP Companion)

Project Experience
6 PUBLIC Project Experience
Icon Name Description

Help Topics Shows the Help Topics view with a list of help topics.

Learning Shows the Learning view with the recommended learning content and a button
to open the Learning Center.

What's New Shows the What's New view with the What's New help topics.

1.2 Authorization

SAP Central Business Configuration provides a set of generic standard roles for different tasks and business
scenarios.

Prerequisites

The Administration Expert has assigned authorizations to you according to your role. For more information, see
Creating Business Users and Providing Access Rights.

Related Information

Standard Roles and Authorizations [page 7]

Standard Authorization Concept [page 8]

1.2.1 Standard Roles and Authorizations

Roles and authorizations allow the users to access the system and relevant features in a secure way.

SAP Central Business Configuration provides a set of standard roles providing authorizations to perform
different implementation tasks. The system can be accessed only by users with authorizations.

Users can access only those projects to which they are assigned. The only exceptions are users with program
manager and auditor roles who will always have access to all projects.

As a program manager or project manager, you can assign users to projects in the Team view.

Users can see their assigned roles in the Team view or in Profile Settings User Settings .

For more information, see Maintaining Team Members of a Project [page 26].

Project Experience
Project Experience PUBLIC 7
Roles and Authorizations provided by SAP Central Business Configuration
Role Names Role IDs / User Groups Authorizations and Tasks

Program manager SAP_CBC_CONSUMPTION_PRO- Performing Project tasks across all projects, with-
GRAM_LEAD out being assigned to the projects. There is no
access restriction to specific projects.

Project manager SAP_CBC_CONSUMPTION_PROJECT_LEAD Performing tasks within assigned projects.

Project manager (depre- SAP_CBC_CONSUMPTION_ACTIVITY_ALL Performing tasks within assigned projects.

cated)
 Note
We recommend that new customers do
not use this role. Both project manager
roles have the same authorizations, but the
SAP_CBC_CONSUMPTION_PROJECT_LEAD
role follows the new naming convention.

Key user SAP_CBC_CONSUMPTION_KEY_USER Performing tasks within assigned projects, except

critical activities such as creating a project and
initiating a change.

Display user SAP_CBC_CONSUMPTION_DISPLAY_USER Read access to tasks within assigned projects.

Auditor SAP_CBC_CONSUMPTION_AUDITOR Read access to tasks, access to the Change Logs

view and download change logs CSV across all
projects.

Content processor SAP_CBC_CONTENT_PROCESSOR Read access to tasks and access to Download My

Configuration within assigned projects.

 Note

When new roles become available in SAP Central Business Configuration, the list of related user groups
needs to be updated in the Identity Authentication service. See Running Jobs for Pushing Roles.

1.2.2 Standard Authorization Concept

The standard authorization concept shows the authorized tasks and activities per role.

 Note

A Program Manager can perform the same tasks as the Project Manager, but across all projects. The
Project Manager can perform tasks only within the assigned projects.

Standard Authorizations per Role

Project Display Content
Tasks and Activities Manager Key User User Auditor Processor

Creating a New Project [page 24] Perform Display Display Display Display

Editing Name and Description of a Project [page 26] Perform Display Display Display Display

Project Experience
8 PUBLIC Project Experience
 Project Display Content
Tasks and Activities Manager Key User User Auditor Processor

Changes via Edit [page 78] Perform Display Display Display Display

Maintaining Team Members of a Project [page 26] Perform Display Display Display Display

Requesting quality and production systems Perform Display Display Display Display

Specifying Primary Finance Settings [page 54] Perform Display Display Display Display

Releasing configuration into production system Perform Display Display Display Display

Completing and confirming milestones Perform Display Display Display Display

Defining Scope [page 41] Perform Perform Display Display Display

Releasing optional content Perform Perform Display Display Display

Setting Up Organizational Structure [page 61] Perform Perform Display Display Display

Performing Configuration Activities and Calling Up Perform Perform Display Display Display
Setup Instructions [page 69]

Creating master data manually Perform Perform Display Display Display

Performing business process unit tests Perform Perform Display Display Display

Maintaining current settings in production system Perform Perform Display Display Display

Performing Manual Rework (2-System Landscape) Perform Perform Display Display Display
[page 76]

Assigning a Deployment Target [page 53] Perform Display Display Display Display

Assigning a Production System (2-System Landscape) Perform Display Display Display Display
[page 72]

Change Logs [page 80] Not visible Not visible Not visible Display, Display
download
change
logs CSV

Downloading Template Configuration [page 28] Not visible Not visible Not visible Not visible Perform

 Note

For more information on the corresponding role IDs / user groups, see Standard Roles and Authorizations
[page 7].

Project Experience
Project Experience PUBLIC 9
1.3 Status Management

There are different types of status related to your project and activities.

Project Status

Your evaluation or implementation project is an active project. However, your project can be locked due to an
ongoing upgrade. In this case, a notification is displayed and a lock ( ) icon appears next to the project name.
During this time, changes are not possible and functions in the system are locked.

In the Switch Project dialog, you can view the processing status of a project. It can have one of the following
processing statuses:

• Scoping in Preparation
• Scoping Confirmation in Progress
• Scoping in Error
• Scoping Completed
• Deployment in Preparation
• Deployment in Progress
• Deployment in Error
• Deployment Completed
• Activation in Error
• Activation Completed
• Synchronizing Business Configuration
• Synchronizing Business Configuration for P
• Scoping and Organizational Structure Completed
• Product-Specific Configuration
• Transport in Progress (2-system landscape only)
• Transport in Error (2-system landscape only)
• Transport Completed (2-system landscape only)
• Ongoing Operations

Activity Status

In the Overview page, each activity in the Activities section is marked with a status. You can easily track the
status in the Status column. The status is either Open, Reopened, In Progress, or Completed.

Once you start working on an activity with status Open, the status changes to In Progress automatically.

Project Experience
10 PUBLIC Project Experience
Milestone Status

Each milestone is listed in the Activities section and marked with a status. In the Status column, the status is
either Open, Reopened, In Progress, or Completed.

Only once the activities of a certain phase are completed, you can confirm a milestone. Go to the Action column
and choose Confirm. The status changes to In Progress automatically. Depending on the milestone, a progress
bar in the Status column indicates the progress. After successful completion, the status changes to Completed.

Status of Business Processes Configuration

This section refers to Configure Your Business Processes [page 66]. The statuses of configuration activities
are managed manually once the activity is updated. Following are the various statuses:

• Open / Reopened
• In Progress
• Completed

All mandatory configuration settings are marked with an asterisk ( * ).

1.4 Project Management

You can work with two different project types: an evaluation project or an implementation project.

For more information, see:

• Evaluation Project [page 12]

• Implementation Project [page 18]

Related Information

Selecting Your Project (Initial Logon) [page 23]

Creating a New Project [page 24]
Switching Between Projects [page 25]
Maintaining Team Members of a Project [page 26]
Editing Name and Description of a Project [page 26]
Deleting a Project [page 27]
Downloading Template Configuration [page 28]

Project Experience
Project Experience PUBLIC 11
1.4.1 Evaluation Project
To support the implementation of your solution, you can create an evaluation project manually.

You then connect your evaluation project to a starter system or similar system.

One of the following systems can be connected:

• Starter system
• Partner demo system (separate license required)
• Customer sandbox system (separate license required)
• Training system

 Note

Transports into other systems are not supported.

Starter System

Once the starter system is activated, it offers preconfigured content and demo data that you can use to test
and evaluate business processes. For more information on the availability of demo data, see Systems and
Demo Data [page 13].

You can use the evaluation project for the starter system to get familiar with its predelivered content and
preselected values. As you carry out activities, such as Define Scope or Set Up Organizational Structure, it helps
you to understand how to proceed in your implementation project later. You can also use the evaluation project
to conduct your fit-to-standard workshops.

 Note

Consider the following recommendations:

• Focus on critical configuration settings in the starter system as your target system will be set up later in
the implementation project.
• On first use, select only one country/region and use the default settings provided by SAP to get your
starter system activated.
• If you want to add additional countries/regions, scope, organizational elements, or configuration
settings afterwards, you can initiate a change (see Changes via Edit [page 78]) and then perform
the required enhancements or changes.

The evaluation project uses the SAP Best Practices content (for example, configuration and demo data) for the
starter system. You can adapt several areas of the SAP Best Practices content and make configuration settings
that will be consumed by the starter system.

 Note

The starter system is only activated once you have completed all activities in the Scope and Organizational
Structure phase and set its milestone to completed (see Completing the Scope and Organizational
Structure Phase [page 65]). By completing the milestone of the Scope and Organizational Structure phase,
SAP Best Practices content and configuration settings are deployed to the starter system and activated.

Project Experience
12 PUBLIC Project Experience
  Caution

The starter system will be decommissioned 30 days after the production system is provisioned.

Related Information

Phases, Activities, and Milestones in an Evaluation Project [page 14]

Switching Between Projects [page 25]

1.4.1.1 Systems and Demo Data

A system is connected to your evaluation project. Depending on the system type, demo data is already
available in the system or can be added optionally.

Systems

You connect the evaluation project to one of the following systems:

• Starter system
• Partner demo system (separate license required)
• Customer sandbox system (separate license required)
• Training system

 Note

In an evaluation project, transports into other systems are not supported.

Demo Data

Depending on your system type, demo data is already available in the system and ready to use. For example,
the starter system already contains predelivered demo data.

There are systems where the use of demo data is optional. In these cases, you can add the demo data when
you assign a deployment target, see Assigning a Deployment Target [page 53].

For details, refer to the table below:

System Type Demo Data

Starter Predelivered

Project Experience
Project Experience PUBLIC 13
System Type Demo Data

Starter Customizing Predelivered

Starter Development Predelivered

Partner Demo Customizing Optional

Partner Demo Development Optional

Customer Sandbox Customizing Optional

Customer Sandbox Development Optional

Related Information

Assigning a Deployment Target [page 53]

1.4.1.2 Phases, Activities, and Milestones in an Evaluation

Project

In the evaluation project, you prepare the settings that will be deployed to the starter system later.

The evaluation project offers preconfigured content and demo data that you can use to test and evaluate
business processes once the starter system is activated.

You can create an evaluation project manually and connect it to a starter system in the Deployment Target app.

 Note

2-System Landscape

If you work with an evaluation project in a 2-system landscape, you can request the quality system, but
it is not possible to request the production system or perform transports into the quality and production
systems.

The evaluation project covers the Scope and Organizational Structure phase and the Product-Specific
Configuration phase of SAP Central Business Configuration. Each phase consists of various activities relevant
to managing the project. Activities guide you through the different phases and unlock the milestones that you
must complete in each phase. Once you complete a milestone, processes in the background are triggered and
you move to the next phase.

Scope and Organizational Structure

In this phase, you carry out activities to define the scope, specify primary finance settings, and set up the
organizational structure. In the evaluation project, these activities already contain demo data that you can
review or enhance.

Project Experience
14 PUBLIC Project Experience
Activity / Milestone Description

Defining Scope [page 41] The evaluation project only offers a limited scope selection.
Two scenarios are available for parallel ledger accounting.
You can choose either the group ledger scenario Accounting
and Financial Close - Group Ledger US GAAP or Accounting
and Financial Close - Group Ledger IFRS. Depending on your
country/region and sector (private/public) selection, addi-
tional scenarios and bundles may be available.

You can also add scope by importing a JSON file. For more
information, please refer to Importing Scope [page 43].

 Tip
When you first work with the evaluation project, we rec-
ommend choosing only one country/region. You can
add more countries/regions later via Edit.

Requesting Quality System (2-System Landscape) [page 2-System Landscape

17]
You must request your quality (Q) system in the Systems
view.

Assigning a Deployment Target [page 53] 2-System Landscape

Once you've created an evaluation project, you can assign

the deployment target corresponding to your starter system
to it.

3-System Landscape

Once you've created your evaluation projects and the sys-

tems (customizing and development) are provisioned, you
must assign the corresponding deployment target to each
one.

Confirming Scoping Is Completed [page 44] Via this milestone, your selected scope is being prepared for
the later activation of the starter system. This connected
system activity may take some time.

Specifying Primary Finance Settings [page 54] If you have included demo data in your system, you can only
choose K4 - Cal. Year, 4 Special Periods as fiscal year variant
and USD as group currency.

Project Experience
Project Experience PUBLIC 15
Activity / Milestone Description

Setting Up Organizational Structure [page 61] The evaluation project contains a preconfigured organiza-
tional structure, with all organizational units confirmed al-
ready.

You can enhance the preconfigured organizational structure

by creating your own organizational units. If you want to
deploy the organizational units you created to the target
system, you need to confirm them. Otherwise, you can just
choose Complete Activity without confirming them and the
unconfirmed organizational units will not be available in the
target system.

 Note
• The preconfigured organizational structure may
need some time to build up completely and may
not be visible first. Refresh your screen until it ap-
pears.
• No demo configuration or master data comes with
the organizational units you create additionally. You
need to maintain the data with configuration activi-
ties or the required master data.
• The organizational structure can be enhanced dur-
ing the initial setup, but it is recommended to do it
later via Edit.
• When you create new organizational units in evalu-
ation projects, please refer to Using the Set Up Or-
ganizational Structure App [page 62] for instruc-
tions about unit IDs.

Completing the Scope and Organizational Structure Phase Make sure that all activities of the Scope and Organizational
[page 65] milestone
Structure phase have the status Completed before confirm-
ing this milestone.

After setting this milestone to completed, the configuration

settings will be deployed to the starter system. The starter
system will be activated. This process may take a while. You
can see the progress in the Status column.

After activation, the starter system contains the following:

• SAP Best Practices content and demo data

• Preselected scope that you can extend
• Preconfigured organizational structure that you can en-
hance

In case there are errors during activation, the system dis-

plays an Issues badge indicating the number of issues and
that SAP is already working to resolve these issues.

Project Experience
16 PUBLIC Project Experience
After completing all activities and setting the project milestone of the Scope and Organizational Structure
phase to completed, you can continue with the Product-Specific Configuration phase and an updated activity
list.

Product-Specific Configuration

In this phase, you carry out configuration activities that cover detail settings of the solution process.

After completing all activities, you can still add enhancements, such as additional countries/regions or
organizational entities, to your evaluation project via Edit.

Activity / Milestone Description

Perform Configure Your Business Processes [page 66] Configuration activities must be performed to further adjust
system settings to specific business requirements.

Decommission SAP S/4HANA Cloud Starter System mile- The starter system will be decommissioned 30 days after
stone the production system is provisioned. That is done automati-
cally with no actions from your side.

Changes via Edit

To add any enhancements (for example, additional countries/regions, scope, organizational elements, or
configuration settings), you can use the Edit functionality. For more information, please see Changes via Edit
[page 78].

 Tip

We recommend working with the demo data first and perform the required enhancements or changes after
the starter system has been activated.

1.4.1.3 Requesting Quality System (2-System Landscape)

In your evaluation project, you need to request the quality system.

Context

 Note

Requesting a quality system is only relevant if you work in a 2-system landscape.

Project Experience
Project Experience PUBLIC 17
The quality system is your configurable system during implementation. It acts as a test environment for further
configurations.

Procedure

1. Go to the Request Quality System activity and choose Open.

The Systems view opens and the activity status has automatically been set to status In Progress.
2. A systems list is displayed. Go to the row for the quality system and choose Request Q System.

The quality system is then provisioned by the Service Center. The Provisioning Status column reflects the
provisioning status until the provisioning is complete. Once the status changes to Completed, the quality
system is connected to SAP Central Business Configuration.
3. Go back to the Overview and set the status of the Request Quality System activity to Completed.

Once you have set the status of the activity to Completed, Request Q System in the Systems view
disappears. However, if you change the activity status to Open or In Progress, then Request Q System
appears again.

Next Steps

You can assign the deployment target for the quality system later in your implementation project (see
Assigning a Deployment Target [page 53]).

1.4.2 Implementation Project

The implementation project includes all activities required to implement your SAP solution.

It covers the following phases:

2-System Landscape 3-System Landscape

Scope and Organizational Structure Scope and Organizational Structure

Product-Specific Configuration Product-Specific Configuration

 Note
The project remains open in the Product-Specific Con-
figuration phase. The project will not close or switch to
ongoing operations.

Project Experience
18 PUBLIC Project Experience
2-System Landscape 3-System Landscape

Production System Settings

 Note
You prepare the settings that will be deployed to the
quality system. These configuration settings can be
transported to the production system after they have
been tested.

You can create and work with multiple implementation

projects, but only one implementation project can be
deployed.

Each phase consists of various activities relevant to managing the project. Activities guide you through
the different phases and unlock the milestones that you must complete in each phase. Milestones trigger
processes in the background required to move to the next phase.

New notifications related to your project are displayed on the Notifications ( ) icon on the top of each screen.
Choose the Notifications icon to read the detailed notification information.

If your project is locked due to an ongoing upgrade, a lock ( ) icon appears next to the project name. Changes
are not possible in the system during this time.

Related Information

Phases, Activities, and Milestones in an Implementation Project [page 19]

Switching Between Projects [page 25]

1.4.2.1 Phases, Activities, and Milestones in an

Implementation Project

Each phase in an implementation project contains specific activities that you need to carry out.

In each phase, you carry out various predefined activities and milestones that are displayed in an Activity list.
The activity list is a list of tasks to help you to manage your implementation project and guide you through the
whole process.

Project Experience
Project Experience PUBLIC 19
2-System Landscape

Scope and Organizational Structure

In this phase, you carry out activities to define the scope, specify primary finance settings, and set up the
organizational structure.

After completing all activities and the milestone of the Scope and Organizational Structure phase, you will
continue with the Product-Specific Configuration phase and an updated activity list.

Activity / Milestone Description

Defining Scope [page 41] You define the scope of your solution. First, you select one or
multiple countries/regions, then you add bundles and sce-
narios with predefined content according to your business
needs.

You can also choose sector (private/public). The displayed

bundles and scenarios are based on the chosen sector.

You can also extend your scope later via Edit option.

Assigning a Deployment Target [page 53] You assign a deployment target for your quality system.

Confirming Scoping Is Completed [page 44] By confirming the Scoping milestone, your selected scope is

milestone being prepared for the later activation of the quality system.
This connected system activity may take some time. You can
see the progress in the progress bar.

Specifying Primary Finance Settings [page 54] You set the fiscal year variant and group currency.

 Caution
Specifying the primary finance settings is a one-time
decision. The settings cannot be changed after being
saved.

Setting Up Organizational Structure [page 61] You model your organizational structure with predefined or-
ganizational units and templates.

You can also enhance the organizational structure later via

Edit option.

Completing the Scope and Organizational Structure Phase Make sure that all activities of the Scope and Organizational
[page 65] milestone
Structure phase have the status Completed before confirm-
ing this milestone.

After confirming this milestone, the configuration settings

will be deployed to the quality system. The quality system
will be activated. This process may take a while. You can see
the progress in the Status column.

In case there are errors during activation, the system dis-

plays an Issues badge indicating the number of issues and
that SAP is already working to resolve these issues.

Project Experience
20 PUBLIC Project Experience
Product-Specific Configuration
In this phase, you request the production system, carry out Business Processes Configuration, and release the
configuration into the production system.

After completing all activities and confirming the milestone of the Product-Specific Configuration phase, you
proceed to the Production System Settings phase.

Activity / Milestone Description

Requesting the Production System (2-System Landscape) You request the production (P) system in the Systems view.
[page 71]

Performing Configure Your Business Processes [page 66] You perform Business Processes Configurations to further
adjust system settings to specific business requirements.

Assigning a Production System (2-System Landscape) [page You assign a deployment target for your production system.
72]

Releasing Configuration into Production System (2-System You release the configuration for transport into the produc-
Landscape) [page 73] tion system.

Completing the Product-Specific Configuration Phase (2- After completing all previous activities, you choose this mile-
System Landscape) [page 74] milestone
stone to confirm that the Product-Specific Configuration is
completed.

The project proceeds to the Production System Settings

phase.

Production System Settings

In this phase, you perform all required Business Processes Configurations which need to be maintained directly
in the production system (current settings).

After completing the activities and confirming the milestone of the Production System Settings phase,
configured content is transported into the production system.

Activity / Milestone Description

Maintaining Current Settings in SAP S/4HANA Cloud Public You perform Business Processes Configurations that need
Edition Production System [page 75] to be maintained directly in the production system (current
settings).

Performing Manual Rework (2-System Landscape) [page You perform Business Processes Configurations that require
76] manual rework in the production system.

Completing the Production System Settings (2-System After completing all previous activities, you confirm the mile-
Landscape) [page 76] milestone stone of the Production System Settings phase. The imple-
mentation project switches to ongoing operations mode.

Any enhancements or minor configuration changes can be

made later via Edit.

Project Experience
Project Experience PUBLIC 21
3-System Landscape

 Note

Please contact your SAP account executive to check the availability of the 3-system landscape.

Scope and Organizational Structure

In this phase, you carry out activities to define the scope, specify primary finance settings, and set up the
organizational structure.

After completing all activities and the milestone of the Scope and Organizational Structure phase, you continue
with the Product-Specific Configuration phase and an updated activity list.

Activity / Milestone Description

Defining Scope [page 41] You define the scope of your solution. First, you select one or
multiple countries/regions, then you add bundles and sce-
narios with predefined content according to your business
needs.

You can also choose sector (private/public). The displayed

bundles and scenarios are based on the chosen sector.

You can also extend your scope later via Edit option.

Assigning a Deployment Target [page 53] You assign deployment targets for your development sys-
tems.

Confirming Scoping Is Completed [page 44] By confirming the Scoping milestone, your selected scope is

milestone being prepared for the later activation. This may take some
time. You can see the progress in the progress bar.

Specifying Primary Finance Settings [page 54] You set the additional fiscal year variant and group currency.

 Caution
Specifying the primary finance settings is a one-time
decision. The settings cannot be changed after being
saved.

Setting Up Organizational Structure [page 61] You model your organizational structure with predefined or-
ganizational units and templates.

You can also enhance the organizational structure later via

Edit option.

Project Experience
22 PUBLIC Project Experience
Activity / Milestone Description

Completing the Scope and Organizational Structure Phase Make sure that all activities of the Scope and Organizational
[page 65] milestone
Structure phase have the status Completed before confirm-
ing this milestone.

After confirming this milestone, the configuration settings

will be deployed. You can see the progress in the progress
bar.

In case there are errors during activation, the system dis-

plays an Issues badge indicating the number of issues and
that SAP is already working to resolve these issues.

Product-Specific Configuration
In this phase, you carry out Business Processes Configurations to further adjust your system settings. After
completing all activities, your project remains open in the Product-Specific Configuration phase.

Activity / Milestone Description

Performing Configure Your Business Processes [page 66] You perform Business Processes Configurations to further
adjust system settings to specific business requirements.

Editing Your Configuration Activities

Use the Edit button to make changes to the completed configuration activities. To add any enhancements (for
example, additional countries/regions, scope, organizational elements, or configuration settings), you can use
the Edit button. For more information, please see Changes via Edit [page 78].

1.4.3 Working with Projects

Familiarize yourself with some common tasks in your project.

1.4.3.1 Selecting Your Project (Initial Logon)

After the first logon, you must select or create the project you want to work on.

Prerequisites

• You have received the welcome email with a link to your system.

Project Experience
Project Experience PUBLIC 23
• You have the relevant authorization for creating and selecting projects. For more information, see Standard
Roles and Authorizations [page 7].

Procedure

1. Log on to the system.

The Projects dialog opens.

2. In the Projects dialog, you can perform the following:
1. Create a new project.
To create a new project, choose Create New. In the New Project dialog, you can enter a title, the project
type, and an optional description. Then, choose Create.
2. Select an existing project.
If there is already an existing project in the system to which you are assigned, you can select to work on
it. Go to the Action column and choose Switch Project. This project is set as your default project.

1.4.3.2 Creating a New Project

You can create a new project from scratch.

 Note

Only program managers and project managers have authorization to create a new project. The user
creating a project automatically gets assigned to the project. For more information, see Authorization
[page 7].

The following ways of creating a new project are available:

• After the first logon to the Project Experience system. For more information, see Selecting Your Project
(Initial Logon) [page 23].
• In the Switch Project function. For more information, see Switching Between Projects [page 25].

 Note

You can create multiple Evaluation and Implementation projects. However, the number of available
deployment targets you can assign to your projects is limited. For more information, please see
Deployment Target [page 45].

Project Experience
24 PUBLIC Project Experience
1.4.3.3 Switching Between Projects

You can switch between different projects that are assigned to you based on your role.

Context

You can create several evaluation and implementation projects and switch between these projects or open
these projects in different browser tabs. Note that you can only switch between the projects you are assigned
to. See also Maintaining Team Members of a Project [page 26].

 Note

As a project manager you can create as many projects as needed. There is no limitation to the number of
projects. This gives you more options when you configure new or different capabilities depending on your
requirements.

You also need to assign a deployment target for each project (see Assigning a Deployment Target [page
53]).

If a project was created by mistake, you can delete it (see Deleting a Project [page 27]).

Procedure

1. In the navigation pane, choose Settings.

The Settings view appears.

2. Choose Switch Project.
3. In the Projects dialog, you can perform the following:
1. Switch between projects.
Select the project that you would like to work on and in the Action column choose Switch Project. This
is set as your default project.
2. Open project in a new tab.
Select the project you would like to open in a new browser tab. In the Action column, choose Open in
New Tab.

 Note

The project that you open in a new tab, is not your default project. If you refresh the page ( F5 ), the
default project is displayed.

3. Create a new project.

To create a new project, choose Create New. In the New Project dialog, enter a title and a project type.
Then choose Create.
Your newly created project opens automatically.

Project Experience
Project Experience PUBLIC 25
1.4.3.4 Maintaining Team Members of a Project

Assign team members to your project.

Context

As program manager or project manager, you can assign team members to your project or remove them from
the project. The list also serves as an overview of the team members assigned to a project. You can easily sort
and filter the table using the sort and filter options available in the table column header.

The roles of team members are displayed in the Team list and the Add User dialog. Roles are ensuring that team
members have restricted access to projects. For more information, see Standard Roles and Authorizations
[page 7].

Procedure

1. In the navigation pane, choose Settings.

The Settings view appears.

2. In the Team section, choose Add User to assign team members to your project.
3. In the Add User dialog, assign team members to your project by choosing Add.
4. Choose Close to finalize the assignments.

The assigned project team members will appear in the Team section. To remove team members from the
project, choose Remove.

 Note

Team members who are removed from their default project will no longer have that project marked as
their default. In their next logon, the removed team members will have to choose a new default project.
For more information, see Switching Between Projects [page 25].

1.4.3.5 Editing Name and Description of a Project

Change the project name to a suitable name and enter a description for your project.

Context

As a program or project manager you can edit the name and the description of a project for easier recognition
or to reflect any changes in the content.

Project Experience
26 PUBLIC Project Experience
Procedure

1. In the navigation pane, choose Settings.

The Settings view appears.

2. Go to the Project Details section and choose Edit.
3. You can edit the name and the description of your project.
4. Choose Save.

1.4.3.6 Deleting a Project

You can delete a project if you no longer need it.

Context

 Note

Only program or project managers have authorization to delete a project. For more information, see
Authorization [page 7].

You can delete a project that is not needed or has been created by mistake. Note that it is only possible to
delete projects for which the deployment hasn't been performed, that is, before confirming the Completing the
Scope and Organizational Structure Phase [page 65] milestone.

Procedure

1. Switch to the project that you want to delete.

2. In the navigation pane, choose Settings.

The Settings view appears.

3. In the Project Details section, choose Delete Project.
4. In the dialog, confirm with Delete.

The project is deleted.

Project Experience
Project Experience PUBLIC 27
1.4.3.7 Downloading Template Configuration

You can download a zip file with information on configuration data and scope of your project.

Prerequisites

Before you download configuration data, make sure of the following:

• You have the Content Processor role assigned to your user. For more information, see Authorization [page
7].
• Your project must be in the Product-Specific Configuration phase.

Context

You can download a zip file which contains the following spreadsheets:

• Summary file:
• A list of the configuration adaptations that you have maintained.
• A list of the selected scope.
• Individual files for each configuration activity with the settings you have made.

 Note

In a 2-system landscape, the download contains the settings made in the quality system.

Procedure

1. In the navigation pane, choose Settings.

The Settings view appears.

2. As a first step to download the configuration data of your project, choose Prepare Download of My
Configuration.

This prepares the download. You need to wait until the button changes to Download My Configuration.
3. Choose Download My Configuration.
4. Enter a name for your file and choose SaveDownloads folder.
5. Once the zip file download is complete, Download My Configuration changes to Prepare Download of My
Configuration and you can perform the action again.

 Note

If you use the Apple Safari browser, refresh the browser manually after the download of the zip file has
been done to display Prepare Download of My Configuration again.

Project Experience
28 PUBLIC Project Experience
 The download is logged in Change Logs.

1.5 Scoping

In scoping, you define the capabilities of your solution by choosing the countries/regions and business
scenarios relevant for your business. This process enables SAP Central Business Configuration to put together
the preconfigured settings for this individual solution.

Key Features

• The Define Scope activity guides you through the process of defining the scope of your solution. See
Defining Scope [page 41].
• You define the scope of your project by selecting countries/regions and scenarios. A scenario contains
predefined content for the implementation of a business process. Scenarios are also be grouped in
bundles.
• Because each company has unique business requirements, the system enables you to make a series of
business decisions to adjust the content and determine which of the available features and functions you
want to incorporate into your solution.
• Built-in rules ensure that your selected content is logical and consistent from a technical and business
point of view.
• The system calculates the configuration settings that are needed to realize the business scenarios for the
countries/regions that you have selected for this project. See Confirming Scoping Is Completed [page
44].
• You can add any additional countries/regions or scope later via the Changes via Edit [page 78]
functionality.

Related Information

Deployment Target [page 45]

1.5.1 Country/Region-Specific Scoping and Configuration

SAP Central Business Configuration provides country/region-specific scoping and configuration.

The countries/regions that you select for your scope have an impact on the activities and selections you
perform later in the project:

• Scoping is country/region-specific. When you select a bundle, you will get a different set of scenarios for
each country/region. For example, Germany and Philippines will have a different number of scenarios.
Whenever a scenario is not available for a particular country/region, its configuration is also unavailable.

Project Experience
Project Experience PUBLIC 29
• The scope of a project can include multiple countries/regions. If you scope more than one country/region
in one project, you can select different bundles and scenarios for each country/region.
• Some configurations activities are available for all countries/regions, while some are specific to a
particular country/region. The availability of certain configurations activities for a country/region is based
on their rules and regulations as well as services provided by SAP.

 Example

The Define business places configuration activity is available in the Philippines but not in Germany.
Configuration activities specific for the European Union is not available for Philippines.

When you click on the link to a particular configuration activity, it leads to your product, for instance SAP
S/4HANA Cloud Public Edition, and you can configure the functions according to your business needs.
• Public sector is only available for Canada, the United States of America, and Germany.

Related Information:

• SAP uses country/region codes and IDs during configuration to create country/region-specific values.
Some country/region-specific values use the country/region code while others use the IDs. You can find
the list of country/region codes and IDs here:
• You can find information on standard country/region functions available in SAP S/4HANA Cloud Public
Edition here: Country/Region-Specific Functions
• You can check the available languages for the country/region-specific business configuration of your
product in the Product Availability Matrix (PAM).

1.5.1.1 Country/Region Codes and IDs

The country/region codes and IDs can be used to create values associated with a country/region.

Some country/region-specific values use the code, and others use the ID. A value can consist of the country/
region code or ID alone, or consist of both the country/region code or ID and additional characters.

The country/region codes in the table follow the ISO 3166-1 alpha-2 standard.

 Note

Please be aware that not all the countries/regions listed below might be available for scoping and
configuration.

Country/Region Codes and IDs

Country/Region Name Country/Region Code SAP S/4HANA Country/Region ID

Afghanistan AF 9B

Aland Islands AX 9F

Albania AL 86

Project Experience
30 PUBLIC Project Experience
Country/Region Name Country/Region Code SAP S/4HANA Country/Region ID

Algeria DZ 71

American Minor Outlying Islands UM F4

American Samoa AS 9E

American Virgin Islands VI F7

Andorra AD 9A

Angola AO 76

Anguilla AI G2

Antarctica AQ 9D

Antigua and Barbuda AG 9C

Argentina AR 31

Armenia AM 8X

Aruba AW 6O

Australia AU 30

Austria AT 39

Azerbaijan AZ 9G

Bahamas BS 7Y

Bahrain BH 7G

Bangladesh BD 7Z

Barbados BB 9H

Belarus BY 80

Belgium BE 25

Belize BZ 6J

Benin BJ 8A

Bermuda BM 8E

Bhutan BT 9J

Bolivia BO 99

Bonaire, Sint Eustatius and Saba BQ 6Q

Bosnia and Herzegovina BA 7F

Botswana BW 7N

Bouvet Islands BV 9K

Brazil BR 14

British Indian Ocean Territory IO A8

British Virgin Islands VG 8G

Brunei Darussalam BN 8S

Project Experience
Project Experience PUBLIC 31
Country/Region Name Country/Region Code SAP S/4HANA Country/Region ID

Bulgaria BG 38

Burkina Faso BF 7U

Burundi BI 8J

Cabo Verde CV 9P

Cambodia KH 7X

Cameroon CM 96

Canada CA 29

Cayman Islands KY 6M

Central African Republic CF 9M

Chad TD 8Y

Chile CL 46

China CN 13

Christmas Island CX 9Q

Cocos (Keeling) Islands CC 9L

Colombia CO 48

Comoros KM B1

Congo CG 7T

Cook Islands CK 9N

Costa Rica CR 89

Cote d'Ivoire CI 8C

Croatia HR 40

Cuba CU 9O

Curaçao CW 6N

Cyprus CY 95

Czechia CZ 20

Democratic Republic of the Congo CD 98

Denmark DK 32

Djibouti DJ 6A

Dominica DM 9R

Dominican Republic DO 82

Ecuador EC 77

Egypt EG 73

El Salvador SV 7A

Equatorial Guinea GQ A3

Project Experience
32 PUBLIC Project Experience
Country/Region Name Country/Region Code SAP S/4HANA Country/Region ID

Eritrea ER 9T

Estonia EE 50

Eswatini SZ 8Q

Ethiopia ET 7E

Falkland Islands FK 9V

Faroe Islands FO 9X

Federated States of Micronesia FM 9W

Fiji FJ 9U

Finland FI 45

France FR 12

French Guyana GF 9Z

French Polynesia PF D1

French Southern Territories TF E7

Gabon GA 7L

Gambia GM 6B

Georgia GE 7O

Germany DE 10

Ghana GH 90

Gibraltar GI A0

Greece GR 34

Greenland GL A1

Grenada GD 9Y

Guadeloupe GP A2

Guam GU A5

Guatemala GT 85

Guernsey GG 6L

Guinea GN 6C

Guinea-Bissau GW 8K

Guyana GY A6

Haiti HT 8B

Heard and McDonald Islands HM A7

Honduras HN 7I

Hong Kong HK 62

Hungary HU 21

Project Experience
Project Experience PUBLIC 33
Country/Region Name Country/Region Code SAP S/4HANA Country/Region ID

Iceland IS 8R

India IN 18

Indonesia ID 51

Iran IR 70

Iraq IQ 7B

Ireland IE 42

Isle of Man IM 6R

Israel IL 47

Italy IT 23

Jamaica JM 8Z

Japan JP 15

Jersey JE 6K

Jordan JO 7V

Kazakhstan KZ 94

Kenya KE 91

Kiribati KI B0

Korea, the Republic of KR 43

Kuwait KW 74

Kyrgyzstan KG A9

Laos LA B4

Latvia LV 52

Lebanon LB 88

Lesotho LS 8L

Liberia LR 6F

Libya LY B7

Liechtenstein LI B6

Lithuania LT 53

Luxembourg LU 7K

Macao MO 7H

Madagascar MG 7W

Malawi MW 8I

Malaysia MY 54

Maldives MV C6

Mali ML 7R

Project Experience
34 PUBLIC Project Experience
Country/Region Name Country/Region Code SAP S/4HANA Country/Region ID

Malta MT 6I

Marshall Islands MH C0

Martinique MQ C4

Mauretania MR 8M

Mauritius MU 7Q

Mayotte YT G1

Mexico MX 55

Moldova MD 6E

Monaco MC B8

Mongolia MN C2

Montenegro ME 6G

Montserrat MS C5

Morocco MA 49

Mozambique MZ 7P

Myanmar MM C1

Namibia NA 8V

Nauru NR C9

Nepal NP C8

Netherlands NL 37

New Caledonia NC 8U

New Zealand NZ 69

Nicaragua NI 8F

Niger NE 8N

Nigeria NG 72

Niue NU D0

Norfolk Islands NF C7

North Korea KP B3

North Macedonia MK 7S

North Mariana Islands MP C3

Norway NO 44

Oman OM 7D

Pakistan PK 56

Palau PW D5

Panama PA 93

Project Experience
Project Experience PUBLIC 35
Country/Region Name Country/Region Code SAP S/4HANA Country/Region ID

Papua New Guinea PG 8W

Paraguay PY 6H

Peru PE 57

Philippines PH 58

Pitcairn Islands PN D3

Poland PL 26

Portugal PT 35

Puerto Rico PR 8D

Qatar QA 75

Republic of South Sudan SS E4

Reunion RE D6

Romania RO 28

Russian Federation RU 16

Rwanda RW 8O

Saint Barthelemy BL 9I

Saint Helena SH D9

Saint Kitts and Nevis KN B2

Saint Martin MF B9

Samoa WS G0

San Marino SM E1

Sao Tome and Principe ST E5

Saudi Arabia SA 59

Senegal SN 7M

Serbia RS 60

Seychelles SC D8

Sierra Leone SL 8P

Singapore SG 61

Sint Maarten (Dutch part) SX 6P

Slovakia SK 27

Slovenia SI 41

Solomon Islands SB D7

Somalia SO E2

South Africa ZA 64

South Georgia and the Southern Sand- GS A4

wich Islands

Project Experience
36 PUBLIC Project Experience
Country/Region Name Country/Region Code SAP S/4HANA Country/Region ID

Spain ES 24

Sri Lanka LK 81

St. Lucia LC B5

St. Pierre and Miquelon PM D2

St. Vincent and the Grenadines VC F6

State of Palestine PS D4

Sudan SD 79

Suriname SR E3

Svalbard SJ E0

Sweden SE 19

Switzerland CH 22

Syria SY 78

Taiwan TW 63

Tajikistan TJ E8

Tanzania TZ 97

Thailand TH 68

Timor-Leste TL F0

Togo TG 8T

Tokelau Islands TK E9

Tonga TO F2

Trinidad and Tobago TT 7C

Tunisia TN 83

Turkey TR 36

Turkmenistan TM F1

Turks and Caicos Islands TC E6

Tuvalu TV F3

Uganda UG 7J

Ukraine UA 65

United Arab Emirates AE 33

United Kingdom GB 11

Uruguay UY 84

USA US 17

Uzbekistan UZ 87

Vanuatu VU F8

Project Experience
Project Experience PUBLIC 37
Country/Region Name Country/Region Code SAP S/4HANA Country/Region ID

Vatican City VA F5

Venezuela VE 66

Vietnam VN 67

Wallis and Futuna Islands WF F9

West Sahara EH 9S

Yemen YE 92

Zambia ZM 8H

Zimbabwe ZW 6D

1.5.2 Bundle

A bundle is a set of predefined scenarios with a certain business focus.

Scenarios are grouped into bundles for quicker and easier scoping. Bundles are country/region-specific,
meaning that the scenarios within a bundle can vary depending on your selected countries/regions. When
you define your scope, you can choose from the following bundles:

• The Baseline Accelerator bundle contains the necessary scenarios required for a well-functioning SAP
S/4HANA Cloud Public Edition solution. It contains mainly finance-related scenarios.
• The Enterprise Management bundle contains sales, procurement, and manufacturing scenarios. This
extensive bundle is appropriate for large enterprises.
• The Retail bundle contains all scenarios from the Enterprise Management bundle and scenarios relevant for
the retail industry. This bundle is license-dependent.
• The Public Sector Management bundle contains scenarios which manage the budget of revenue and
expenditure at public institutions, such as federal, state, and local authorities. For example, for a
government, nonprofit, or educational organization in the US that needs to comply to funds and budget
accounting (including US-GASB), you need to add this bundle.
• The Finance-Led and Professional Services bundles have been deprecated. They are only available for users
who selected them before deprecation.

 Caution

You need to add at least one bundle in your scope.

 Tip

Choose the title of a bundle to view a list of all scenarios it contains. You can download a list of the scenarios
by choosing the Download List button.

When you choose a Scenario ID, more detailed information is displayed.

Project Experience
38 PUBLIC Project Experience
1.5.3 Scenario

A scenario contains predefined content for the implementation of a business process.

When you define your scope, you determine which of the available scenarios you want to incorporate into your
solution. To learn more about a scenario, choose the scenario title to open a more detailed description.

Each scenario has a unique three-digit ID, which is displayed in brackets after the scenario title. It allows you to
quickly find the scenario via the search function. For example, Time Recording (1Q4).

Note that if a scenario becomes newly available for a country/region in scope (for example, after an upgrade
or update) and you have previously selected the same scenario for your other countries/regions, your current
scope is not affected. If you want to add this scenario also to the scope of the missing country/region, you can
use the Changes via Edit [page 78] functionality.

Group Ledger Scenarios

A group ledger scenario is linked to a full set of scenarios that are relevant for reporting and financial
statements in accounting. When you define your scope for the first time, you have to decide which group
ledger scenario you want to use. Depending on your business requirements, it is also possible to choose both
group ledger scenarios.

Two group ledger scenarios are available:

• Accounting and Financial Close – Group Ledger US GAAP (2VA)

• Accounting and Financial Close – Group Ledger IFRS (1GA)

When you select a group ledger scenario, its dependent scenarios are added automatically to your scope and
are displayed in My Selected Scope.

 Caution

Consider your group ledger selection carefully, because you cannot add or remove group ledger scenarios
after your initial scope has been finalized. Changes via Changes via Edit [page 78] cannot be made.

For more information on available ledger combinations and scenarios in SAP S/4HANA Cloud Public Edition,
please refer to Ledger Scenarios: Choosing the Right Combination for Your Business Needs.

License-Dependent Scenarios and Non-Standard Scenarios

Some scenarios are not included in the standard content. For example, the scenario is license-dependent
(requires an additional license), or non-standard (the availability depends on your individual scope).

License-dependent scenarios and some non-standard scenarios are marked with  (lock) icon. To request
these scenarios, you need to create a ticket with the subject 'Activation of New Licensed Scenarios' in
component XX-S4C-OPR-SRV, and list the scenario name(s) as they appear in the Define Scope app.

Project Experience
Project Experience PUBLIC 39
For the non-standard scenarios which are marked with  (warning) icon, when you try to add them, you
receive warning messages with detailed information. If you confirm adding the scenario, a log will be created in
Change Logs.

Constraints

The logical dependencies between scenarios are defined by constraints. These built-in rules ensure that your
scope selection is consistent and scenarios are compatible with each other. A constraint can specify that, for
example, if scenario A is selected, then scenario B must be selected. Or, adding scenario A will remove scenario
B.

Due to a constraint, it's possible that adding a scenario removes another scenario, or adding a scenario adds a
dependent scenario.

1.5.4 Variant Operating Chart of Accounts

For some industries and countries/regions, you can choose to map the standard G/L account numbers, as well
as the descriptions, to the numbers and descriptions specific to a certain industry or country/region.

By default, the standard G/L account numbers delivered by SAP are used. You can use variant operating charts
of accounts for specific industries or countries/region by mapping. For more information about the chart of
accounts template for SAP S/4HANA Cloud Public Edition, please refer to General Information about the Chart
of Accounts (YCOA) Template for SAP S/4HANA Cloud.

 Note

Once deployed, the mapping cannot be reverted.

Public Sector

To use the variant operating chart of accounts for Public Sector, you can do the mapping in Scoping phase by
choosing SAP S/4HANA Cloud Public Edition scenario 5R0 (Account Mapping for US GASB).

 Note

• Scenario 5R0 only applies for Public Sector industry.

• Scenario 5R0 only applies for the USA.
• You can only choose to use this feature during the initial implementation. You cannot add scenario 5R0
by using the Changes via Edit [page 78] functionality.

Project Experience
40 PUBLIC Project Experience
1.5.5 Defining Scope
In the scoping app, you define the scope of your solution.

Context

You are guided through the process of defining the scope of your solution. First you select the countries/
regions you operate in, then you determine which of the available bundles and scenarios you want to
incorporate into your solution.

You can also add scope by importing a JSON file. For detailed information, please refer to Importing Scope
[page 43].

Procedure

1. In the Activities list, go to the Define Scope activity, or choose Scope in the navigation pane.
2. In the Select Country/Region dialog, choose Private or Public sector.

To use the Public Sector Management feature:

• For the USA: choose Public sector, then choose Public Sector Management bundle.
• For other countries/regions where the public sector management feature is applicable: choose Private
sector, then choose Public Sector Management bundle.

 Note

The Public Sector Management bundle is only available for USA, Canada, and Germany.

3. Choose the countries/regions in which your company operates in.

 Note

When you define your scope for the first time or use the Changes via Edit [page 78] functionality, we
strongly recommend limiting the number of countries/regions to no more than five.

4. Based on your country/region selection, the system displays available business scenarios. Now you can
Add the bundles and scenarios that you need for your business to your scope.

 Tip

Scenarios are grouped by line of business. You can also use filters (for example, the Industry filter) to
narrow down your selection.

 Note

If you want to activate Foreign Plant feature, you need to add scenario 5RP (Do you run business in a
foreign country?) in your scope.

For more information about this feature, please refer to Foreign Plant [page 58].

Project Experience
Project Experience PUBLIC 41
5. You can adapt your scope selection for countries/regions (country-dependent scoping).
a. Go to the bundle or scenario and choose Countries/Regions. In the dialog, deselect the country/region
for which the bundle or scenario isn’t relevant.
b. Use the Countries/Regions filter to display only one country/region. Now you can Add or Remove the
relevant bundles or scenarios.

 Tip

Next to the bundle or scenario title, some information about the number of countries/regions is
displayed. For example, if you have four countries/regions in scope and the scenario has been added to
two countries/regions, 2 of 4 is displayed. Hover over this information to view which countries/regions
contain this scenario.

6. (3-system landscape) Select languages.

As determined by law, some countries/regions require the use of mandatory languages. Based on your
country/region selection, the system adds these mandatory languages automatically. They cannot be
removed. Besides the mandatory languages, you can use the Select Languages functionality to choose
other languages.

Please note that selecting languages in scoping does not change the installed languages in the target
system. When you log into the target system (for example, SAP S/4HANA Cloud Public Edition) with
a language that is out of scope, you will not be able to use any app or configuration activity in which
descriptions for configuration settings in that language are required.

 Note

• This functionality is only relevant if you work in a 3-system landscape.

• English is the default language and cannot be deselected.
• If you choose a 2-system landscape deployment target in activity Assigning a Deployment Target
[page 53], you will receive a message indicating that selecting languages is not available and all
languages are selected.

7. You can review your scope in My Selected Scope. By choosing Download Selected Scope you can download
a list of the selected scenarios, countries/regions, and languages to a PDF file.
8. Complete scoping by choosing Complete Activity.

 Caution

Initial Scope (private sector)

You can only select group ledger scenarios when you define your scope for the first time. It is not
possible to add any group ledger scenarios later via Changes via Edit [page 78].

For more information about ledgers, please refer to Scenario [page 39].

The status of the Define Scope activity changes to Completed.

Project Experience
42 PUBLIC Project Experience
Next Steps

After defining your scope, make sure you have assigned a deployment target. Then, you can confirm and
finalize your scope via Confirm Scoping is Completed. Note that you cannot delete any countries/regions,
bundles, or scenarios after this milestone.

To add any additional countries/regions or scope later, you can use the Changes via Edit [page 78]
functionality.

1.5.5.1 Importing Scope

You can add scope by importing a JSON file.

Context

You can include your scope selection in a JSON file and import it to the Define Scope app. For example, you can
download a JSON file of your scope selection from the digital discovery assessment tool and then import it. The
import does not affect the already selected countries/regions, bundles, and sector.

Due to constraints, the imported scenarios may cause the removal of already selected scenarios. For more
information about constraints, please refer to Scenario [page 39].

 Note

• In a JSON file downloaded from the digital discovery assessment tool, the content version and bundle
definition may be different from SAP Central Business Configuration. As a result, some bundles and
scenarios in the JSON file may be not available. You can see the details in the list of rejected scenarios.
Once the import is completed, please view the imported scope in My Selected Scope.
• To avoid activation error, do not import countries/regions which are not localized by SAP.

Please maintain your JSON file in the following format. The <italic text> is sample input:

{"ContentVersion":"<2308.0.200>","Countries":["<COUNTRY_AT>"],"Sectors":
["<Private>"],"UserSelectedElements":["<SG_X4_BL>","<SC_X4_19E>","<SC_X4_19M>"]}

You can download a sample JSON file to see the structure.

Procedure

1. Choose Select Countries/Regions button, then choose Import Scope from JSON File.
2. Choose a JSON file and import.

Project Experience
Project Experience PUBLIC 43
  Tip

• We strongly recommend limiting the number of countries/regions to no more than five.

• If your JSON file contains a large number of scenarios, the import may take some time.

Results

Some scenarios may be rejected. You can choose to cancel the import, or ignore those scenarios and continue.
The reasons of rejection include:

• Not available in content: the scenario is not available in the content version of your project.
• Constraint exists: the scenario has constraint with other scenarios.
• Needs to be requested via ticket: the scenario is not included in the standard content. You need to request
it by creating a ticket.
• Not applicable to your scope: the scenario is incompatible with selected scope.
• Invalid ID: the ID of the scenario or country/region is invalid.
• Non-standard country/region: the country/region is not localized by SAP.

1.5.6 Confirming Scoping Is Completed

You confirm and finalize your scope by completing this milestone.

Prerequisites

You have completed the following activities:

• Defining Scope [page 41]

• Assigning a Deployment Target [page 53]

Context

By Confirming Scoping Is Completed, relevant configuration activities are being calculated. The subsequent
activities are dependent on the chosen scope.

 Caution

After confirming your scope, you cannot delete any countries/regions, bundles, or scenarios. These
choices are irreversible.

It is possible to add enhancements (for example, additional countries/regions) later. For more information,
see Editing Scope [page 78].

Project Experience
44 PUBLIC Project Experience
  Note

There is no system-supported license check in place for license-dependent scenarios. Before confirming
this milestone, make sure you have requested these scenarios and the ticket has been completed. For more
information, see Defining Scope [page 41].

Procedure

1. You are in the Scope and Organizational Structure phase. Choose Confirm for Confirm Scoping Is
Completed. By confirming this milestone, you indicate that you have finished defining and verifying your
scope.
2. In the dialog, choose Confirm Milestone.

 Caution

Do not refresh the page before the process is completed. The progress bar indicates the progress in
percentage terms. It gives you an estimation of how long the scope activation process takes.

Scope finalization takes a while and depending on your selected scope, it may take up to several hours.
You need to wait until the process is finished and the progress bar finally reaches 100%. Then, you can
continue with your next activity.

After successful activation, the status of Confirm Scoping Is Completed is set to Completed. The
subsequent activities become available.

1.6 Deployment Target

A deployment target represents a dedicated system tenant of the assigned solution. To exchange content from
your projects to the leading product, you must specify a deployment target in the Deployment Target app,
where deployment targets are listed and can be assigned or removed.

When opening the app, you see a list with deployment targets that are available and provisioned by SAP
cloud operations. You can only assign deployment targets that are not assigned to any other project. The
available deployment targets also depend on your project type (evaluation or implementation project). In case
no system tenant has been provided, the list will be empty.

 Note

• You can assign or remove a deployment target only for the current active project and before confirming
the first milestone Confirm Scoping Is Completed .
• You can assign a specific deployment target to only one project.

There are different deployment statuses as described in the following table.

Project Experience
Project Experience PUBLIC 45
Deployment Status Description

Not Assigned Indicates that a system for the initial deployment has not
been assigned yet.

Assigned Indicates that a system for the initial deployment is already

assigned to a project.

Assigned with Demo Data Indicates that a system with demo data is assigned to a
project.
 Note
This status is only relevant if you work in a partner demo
system, an evaluation system, or a sandbox system in a
3-system landscape.

Deployed Indicates that the initial deployment has been success-

ful. This status is displayed after completing the second
milestone Scope and Organizational Structure Phase is
Completed.

Related Information

Assigning a Deployment Target [page 53]

Assigning a Production System (2-System Landscape) [page 72]
Deployment Targets in a 2-System Landscape [page 46]
Deployment Targets in a 3-System Landscape [page 49]

1.6.1 Deployment Targets in a 2-System Landscape

 Note

This documentation is only relevant if you work in a 2-system landscape.

In a 2-system landscape, you assign deployment targets to three different systems:

• In your evaluation project, you assign a deployment target to your starter system.
• In the Scope and Organizational Structure phase of your implementation project, you assign a deployment
target to your quality system.
• In the Product-Specific Configuration phase of your implementation project, you assign a deployment
target to your production system.

Deployment Targets in Your Evaluation Project

In a 2-system landscape, you begin working in your evaluation project to which you must assign a deployment
target. Open the Assign Deployment Target activity and assign the right deployment target from the list. It is

Project Experience
46 PUBLIC Project Experience
possible that a starter system tenant is already provisioned. However, you must make sure that the deployment
target is assigned correctly.

You also need to request the quality system in your evaluation project (see Requesting Quality System (2-
System Landscape) [page 17]), but you continue in your implementation project to assign the deployment
target to the quality system.

Evaluation Project
Deployment Sta-
Leading Product System Role URL Project tus Action

SAP S/4HANA Starter <URL> <name> Assigned Remove

Cloud Public Ed-
ition 2-System
Landscape

Assigning a Deployment Target in Your Implementation Project

In the Scope and Organizational Structure phase of your implementation project, you assign a deployment
target to your quality system via the Assign Deployment Target activity.

 Note

Note that there are dependencies between the assignment of deployment targets and the Confirm Scoping
Is Completed milestone:

• You can remove a deployment target only before the first milestone Confirm Scoping Is Completed.
• You can confirm the first milestone Confirm Scoping Is Completed only after having assigned a
deployment target.

After having assigned the deployment target to your quality system, you should have two assigned deployment
targets, one assigned to your evaluation project, and one assigned to your implementation project.

Evaluation Project
Deployment Sta-
Leading Product System Role URL Project tus Action

SAP S/4HANA Starter <URL> <name> Deployed Remove

Cloud Public Ed-
ition 2-System
Landscape

Implementation Project
Deployment Sta-
Leading Product System Role URL Project tus Action

SAP S/4HANA Quality <URL> <name> Assigned Remove

Cloud Public Ed-
ition 2-System
Landscape

Project Experience
Project Experience PUBLIC 47
Assigning a Production System in Your Implementation Project

In the Product-Specific Configuration phase of your implementation project, you assign a deployment target
to your production system before you release any configuration into the production system. See the activity
Assigning a Production System (2-System Landscape) [page 72].

 Note

Note that there are dependencies with transports into the production system:

• You need to assign a deployment target to your production system before you release any
configuration into the production system.
• You can remove the deployment target that is assigned to your production system only before a
transport into the production system is released.

After having assigned the deployment target to your production system, you should have three assigned
deployment targets, one assigned to your evaluation project and two assigned to your implementation project.

Evaluation Project
Deployment Sta-
Leading Product System Role URL Project tus Action

SAP S/4HANA Starter <URL> <name> Deployed Remove

Cloud Public Ed-
ition 2-System
Landscape

Implementation Project
Deployment Sta-
Leading Product System Role URL Project tus Action

SAP S/4HANA Quality <URL> <name> Deployed Remove

Cloud Public Ed-
ition 2-System
Landscape

SAP S/4HANA Production <URL> <name> Assigned Remove

Cloud Public Ed-
ition 2-System
Landscape

Related Information

Assigning a Deployment Target [page 53]

Project Experience
48 PUBLIC Project Experience
1.6.2 Deployment Targets in a 3-System Landscape

 Note

This documentation is only relevant if you work in a 3-system landscape.

Please contact your SAP account executive to check the availability of the 3-system landscape.

In a 3-system landscape, you assign the following deployment targets:

• Starter system: You assign one starter customizing tenant and one starter development tenant.
• Development system: You assign one customizing tenant and one development tenant.

Deployment Targets in Your Evaluation Projects

In a 3-system landscape, you begin working in your evaluation projects (Evaluation, Evaluation Extensibility).
In each evaluation project you must assign a deployment target via the Assign Deployment Target activity.
All available deployment targets are displayed in a list. It is possible that a starter system tenant is already
provisioned. However, you must make sure that the deployment targets are assigned correctly.

Evaluation Project
Deployment Sta-
Leading Product System Role URL Project tus Action

SAP S/4HANA Starter Customiz- <URL> Evaluation Assigned Remove

Cloud Public Ed- ing
ition 3-System
Landscape

SAP S/4HANA Starter Develop- <URL> Evaluation Extensi- Assigned Remove

Cloud Public Ed- ment bility
ition 3-System
Landscape

Deployment Target in Your Implementation Projects

In the Scope and Organizational Structure phase of each implementation project (Dev, Dev Extensibility), you
assign a deployment target to your development system. Open the Assign Deployment Target activity to assign
an available deployment target from the list.

After having assigned the deployment targets in your implementation projects (one per project), you should
have four assigned deployment targets, two assigned to your starter systems and two assigned to your
development systems.

Project Experience
Project Experience PUBLIC 49
Evaluation Project
Deployment Sta-
Leading Product System Role URL Project tus Action

SAP S/4HANA Starter Develop- <URL> Evaluation Extensi- Deployed Remove

Cloud Public Ed- ment bility
ition 3-System
Landscape

Evaluation Project
Deployment Sta-
Leading Product System Role URL Project tus Action

SAP S/4HANA Starter Customiz- <URL> Evaluation Deployed Remove

Cloud Public Ed- ing
ition 3-System
Landscape

Implementation Project
Deployment Sta-
Leading Product System Role URL Project tus Action

SAP S/4HANA Development <URL> Dev Extensibility Assigned Remove

Cloud Public Ed-
ition 3-System
Landscape

Implementation Project
Deployment Sta-
Leading Product System Role URL Project tus Action

SAP S/4HANA Customizing <URL> Dev Assigned Remove

Cloud Public Ed-
ition 3-System
Landscape

Related Information

Assigning a Deployment Target [page 53]

Checking the Deployment Details (3-System Landscape) [page 52]

Project Experience
50 PUBLIC Project Experience
1.6.2.1 Deployment Target Details and Deployment History
(3-System Landscape)

In a 3-system landscape, the Deployment Target app features more info on the deployment target details and
the deployment history.

Deployment Target Details

Deployment Target Details lists detailed information about your assigned deployment target. For example, you
can view the initial deployment status and the operation status. You can also check whether demo data is
included or not.

You have the following options:

• Edit: You can edit the name of your deployment target.

• Change Assignment: You can open the list with all available deployment targets and choose another
deployment target, if needed.

 Note

You can only change the deployment target before the first milestone Confirm Scoping Is Completed.
Afterwards it's not possible anymore.

• Remove Assignment: You can remove an assigned deployment target.

 Note

You can only remove an assigned deployment target before you confirm the Confirm Scoping Is
Completed milestone for the first time. Afterwards it's not possible anymore.

Deployment History

The Deployment History table shows more details about your previous deployments, such as External
Deployment ID, Date and Time, Deployment Type, Deployment Status, and Deployment Description.

You can select different filters to narrow down your deployment history. You can also sort and filter data using
the Sort Ascending, Sort Descending and Filter options available in the table column header.

To check the details of the deployments in SAP S/4HANA Cloud Public Edition, you can choose Go to
Deployment Target and the Display Stagings app in SAP S/4HANA Cloud Public Edition opens. See also
Checking the Deployment Details (3-System Landscape) [page 52].

Project Experience
Project Experience PUBLIC 51
1.6.2.2 Checking the Deployment Details (3-System
Landscape)

In a 3-system landscape, you can navigate to the Maintain Business Configuration Staging app in SAP S/
4HANA Cloud Public Edition to check the details of the deployment status.

Prerequisites

Make sure the following prerequisites are met:

• You have the BPC_EXPERT role in SAP S/4HANA Cloud Public Edition and the business catalog Business
Configuration - Stagings (SAP_CORE_BC_CBC_STA_PC) is assigned to your role.
• A deployment target is assigned.
• The Confirm Scoping Is Completed milestone is completed.

Context

Once you have assigned a deployment target and completed the Confirm Scoping Is Completed milestone, you
can navigate to the Maintain Business Configuration Staging app in SAP S/4HANA Cloud Public Edition to view
the deployment details. For more information, see Display Stagings.

When the initial deployment of your project is completed, the details of the deployment and activation status
become visible.

You may also need to check the deployment details when you perform a change via the Edit option.

Procedure

1. Go to the Deployment Target view.

The Deployment Target Details and the Deployment History are displayed.
2. In the Deployment History area, choose Go to Deployment Target.

The Maintain Business Configuration Staging app in SAP S/4HANA Cloud Public Edition opens in a new tab.
Once the initial deployment is completed, you can view the details of the deployment status.

Project Experience
52 PUBLIC Project Experience
1.6.2.3 Removing an Assigned Deployment Target (3-
System Landscape)

In a 3-system landscape, you can remove an assigned deployment target.

Context

This step can only be performed before you complete the Scoping milestone for the first time (initial scope
calculation).

Procedure

1. Go to Deployment Target.
2. In the Deployment Target Details area, choose Remove Assignment.
The deployment target assignment is removed from your project and the status of the Assign Deployment
Target activity is set to In Progress.

1.6.3 Assigning a Deployment Target

You assign a deployment target to your project.

Context

 Note

Only program managers and project managers have authorization to assign a deployment target. For more
information, see Authorization [page 7].

This step is a prerequisite to confirm the first milestone Confirm Scoping is Completed.

Procedure

1. Go to the Assign Deployment Target activity and choose Assign.

A dialog with a list of available deployment targets is displayed.

2. In the Assign Deployment Target dialog, you can do the following:

Project Experience
Project Experience PUBLIC 53
 • Choose Available (default): The list displays available deployment targets.
• Choose All: The list displays all deployment targets.
• Enter Deployment Target Name: The system proposes a default name that you can use. You can also
enter a new deployment target name.
• Select Include Demo Data (available for certain systems): You can select whether to include demo data
or not.

 Caution

Partner Demo System / Customer Sandbox System (Test, Demo, and Development for SAP
S/4HANA Cloud Public Edition, 1-System Landscape)

If you work in an evaluation project with an assigned partner demo system, or a customer sandbox
system (each system requires a separate license), you can assign a deployment target with demo
data. Choose the Include Demo Data checkbox to add demo data.

Be aware that this is a one-time decision. You cannot add any demo data at a later stage.

3. Select a deployment target and choose Assign.

The deployment target is assigned to your project and the status of the Assign Deployment Target activity
is set to completed.

1.7 Specifying Primary Finance Settings

In this phase you need to specify the fiscal year variant and group currency.

Prerequisites

Activity Defining Scope [page 41] is completed and milestone Confirm Scoping is Completed is confirmed.

Context

 Caution

Specifying the primary finance settings is a one-time decision. The settings cannot be changed after being
saved.

Further Information:

Fiscal Year

Currencies

Project Experience
54 PUBLIC Project Experience
Procedure

1. Open the activity Specify Primary Finance Settings.

The status of the activity is automatically set to In Progress.

2. Select the finance settings as needed.

For fiscal year variant, if you choose configurable template SZ, you will be able to configure the fiscal
year variant with configuration activity Maintain Fiscal Year Variants. For more information, please refer to
Defining Your Own Fiscal Year Variant.

 Note

If you have included demo data in your system, you can only choose K4 - Cal. Year, 4 Special Periods as
fiscal year variant and USD as group currency.

3. Choose Save and confirm your choices.

4. Choose Complete Activity to complete this activity.

1.8 Organizational Structure Management

You can use the Set Up Organizational Structure app to set up your organizational structure.

The Set Up Organizational Structure app supports in modeling your organizational structure with predefined
organizational units and templates before activating any content. The tool supports you to:

• Define your organization structure and then activate the content data.
• Enhance your organization structure as per the business requirement, when you have been using an
activated solution already and would like to enhance your organizational structure using the tool, for
example to add a new plant to your existing organizational structure.

The Set Up Organizational Structure app is closely connected with the scoping. The selected scope specifies
which organizational units are required to run the underlying processes.

The Set Up Organizational Structure app is a key user application. You need to specify all relevant parameters
for every organizational unit.

The Set Up Organizational Structure app is a very flexible tool with which you can create your organizational
structure while following some rules:

• All countries/regions you have chosen in scoping should have at least one company code defined, and one
of the company codes is defined as the default company code.
• Every sales organization should have a plant assigned as the recommended delivery plant.
• Please note that there are restrictions and limitations when you create relationships between
organizational units. For detailed information, please refer to Organizational Units [page 56].

After the organizational structure is confirmed, two follow up actions are triggered:

• Organizational structure templates with all dependent configuration settings are instantiated to the
workspace.

Project Experience
Project Experience PUBLIC 55
• Organization dependent configuration activities can be identified (for example, specify the company code
currency).

1.8.1 Organizational Units

You can use various organizational units to create your organizational structure.

Overview

The graphic below illustrates the country-specific organizational structure of a company. This is a generic
model which may be subjected to change.

• Each company code should be assigned to a company.

• For every country/region, there should be one default company code. The default company code is
required for activating the organizational structure in the target system.

The graphic below illustrates the relationships between the units of an organizational structure:

Project Experience
56 PUBLIC Project Experience
• Tree relation
Country-specific parent-child relation (1: n), for example relation of a plant to a company code.
• Additional relation
Relation of an organizational unit from a country specific tree to another organizational unit of the same
tree or to a multi-assignment organizational unit. Additional relationships have an n:n cardinality, in
other words each of the organizational units for which an additional relationship is possible may have
an additional relationship with no, one, or several organizational units. For example, plant and sales area
have an n:1 cardinality, which means that one plant can only be assigned to one sales area, while one sales
area can be assigned to 1 or more plants.

Company Code

Company codes are assigned to defined countries/regions. They are the highest level of the organizational
structure. Under company code, you can add these organizational units:

• Sales Organization [page 59] for Sales & Distribution

• Plant [page 57] for site logistics

Multi-Assignment Unit

Multi-assignment units can be assigned to enterprise structures in one or more countries/regions. For
example, a Shipping Point can be assigned to several Plants which are in more than one country/region.

You can create the following types of multi-assignment units (depending on your scoping):

• Cloud Warehouse
• Distribution Channel
• Division
• Extended Warehouse Management Integration
• Purchasing Organization
• Sales Office
• Shipping Point for Customer Consignment
• Shipping Point for Raw Materials
• Standard Shipping Point
• Warehouse Number

1.8.1.1 Plant

A plant is a place where materials are produced, or goods and services are provided.

Use organizational unit plant to divide an enterprise according to production, procurement, maintenance,
and materials planning. A plant can be assigned to several combinations of sales organization channels and
distribution channels.

Project Experience
Project Experience PUBLIC 57
Shipping Point

A shipping point is an organizational unit that performs shipping processing. The shipping point is the part of
the company responsible for the particular type of shipping, the necessary shipping materials, and the means
of transport.

Possible shipping points include a mail depot or a company's plant railway station.

Storage Location

A storage location is a place where stock is physically stored within a plant. A plant may contain one or more
storage locations. Physical inventories are carried out at storage location level. Storage locations are always
created within a specific plant.

Warehouse and Warehouse Number

You combine an entire physical warehouse under one warehouse number. You can use the warehouse number
to manage several storage facilities, which together form the complete warehouse complex. The warehouse
number encompasses the organizational and physical aspects of a warehousing complex as a single concept.
For example, a unit of weight is defined at the level of the warehouse number.

1.8.1.1.1 Foreign Plant

The Foreign Plant feature enables you to create a plant or a shipping point in a country/region which is
different from the country/region of the plant's company code, or can be outside of the scoped countries.

 Note

To activate the Foreign Plant feature in SAP Central Business Configuration, you need to add scenario 5RP
(Do you run business in a foreign country?) in your scope.

The countries/regions which are Registration for Indirect Taxation Abroad (RITA) enabled and foreign plant
enabled can be chosen as the countries/regions for your foreign plants or foreign shipping points. When you
create a plant or a shipping point, you can see a list of available countries/regions in the Countries/Regions
drop-down list. If you choose a different country/region than the country/region of the plant's company code,
or a country/region which is not in your scope, a Foreign Plant or Foreign Shipping Point checkbox appears and
is automatically selected to indicate that it is a foreign plant or a foreign shipping point.

For the list of countries/regions which can be chosen for the foreign plant or foreign shipping point, please refer
to RITA Pragmatic Approach , the Where RITA and the Foreign Plant Feature Can Be Used section:

Project Experience
58 PUBLIC Project Experience
• For the countries/regions which are RITA enabled, foreign plant enabled, and country/region activation
NOT required, you can choose them for the foreign plant or foreign shipping point without adding them to
your scope, provided that you have chosen the required scenarios in Define Scope as listed below:

Scenarios for Compliance

Scenarios for VAT Tax Cal- Scenarios for Intrastat Formats - Support Prepa-
Country/Region culation and Reporting Processing ration

Belgium (BE) 5IS 5PA 5P9

Czech Republic (CZ) 5Z2 5Z4 5Z7

Germany (DE) 55U 5OL 5O6

Sweden (SE) 5Z1 5Z3 5Z6

South Africa (ZA) 5Z0 Not in scope 5Z5

Please note that if these countries/regions are not in scope, they can only be included in the Countries/
Regions drop-down list when the required scenarios are in scope.

• For other countries/regions with foreign plant enabled, if you need the RITA feature, you need to add them
to your scope before you use them for the foreign plant or foreign shipping point. They can only be included
in the Countries/Regions drop-down list when they are in scope.

For more information about RITA, please refer to Registration for Indirect Taxation Abroad (RITA).

 Note

• We strongly recommend that you read SAP Note 2907372 to understand the business abroad
logistic or financial processes related to RITA.
• Creating a foreign plant in Taiwan in the Set Up Organizational Structure app only supports the
logistic processes involving the foreign plant. For a company to have a foreign plant in Taiwan, there
are legal requirements to comply with. Before creating a foreign plant in Taiwan, please review your
organizational setup from the legal compliance perspective. Please also understand that the creation of
foreign plants in Taiwan does not enable the local requirements of Taiwan supported by SAP S/4HANA
Cloud Public Edition.

1.8.1.2 Sales Organization

A sales organization is an organizational unit which structures the company according to its sales
requirements. It is responsible for the sale and distribution of goods and services.

Sales Area

A combination of sales organization, distribution channel, and division is known as a sales area.

Project Experience
Project Experience PUBLIC 59
Division

A division is an organizational unit based on responsibility for sales or profits from salable materials or services.
Product groups, i.e. divisions, can be defined for a wide-ranging spectrum of products. For every division you
can make customer-specific agreements on, for example, partial deliveries, pricing, and terms of payment.
Within a division you can carry out statistical analyses or set up separate marketing procedures.

Distribution Channel

A distribution channel represents the channel through which salable materials or services reach customers.
It is mainly defined for defining different types of sales in a sales organization. Typical distribution channels
include wholesale, retail, and direct sales.

A sales organization and a distribution channel form a distribution chain.

Sales Office

A sales office is an organizational unit in a geographical area of a sales organization. A sales office establishes
contact between the company and the regional market. It represents the physical location (for example, a
branch office) that is responsible for the sale of products or services within a given geographical area.

Sales Group

By using sales groups, you can designate different areas of responsibility within a sales office. When you
generate sales statistics, you can use the sales group as one of the selection criteria.

1.8.1.3 Purchasing Organization

A purchasing organization procures materials and services, negotiates conditions of purchase with vendors,
and is responsible for such transactions. It subdivides an enterprise according to the requirements of
purchasing. You can use purchasing organizations to define different prices for the same goods or services.

The purchasing organization is responsible for the complete processing of purchasing activities (such as
purchase requisitions and purchase orders). It can independently maintain relationships with suppliers and
may have its own supplier-specific procurement conditions. A purchasing organization must be assigned to
one or more plants.

The different assignment combinations between company code, plants and purchasing organizations yield
different categories of purchasing organization. There are three categories of purchasing organization:

• Plant-specific purchasing organization: assign the purchase organization to one company code and one
plant which belongs to that company code.

Project Experience
60 PUBLIC Project Experience
• Cross-plant purchasing organization: assign the purchase organization to one company code and multiple
plants which belong to that company code.
• Cross-company-code purchasing organization: leave the company code field blank. Assign the purchase
organization to plants belonging to different company codes.

1.8.2 Setting Up Organizational Structure

In this phase, you need to create organizational structure.

Prerequisites

• Activity Defining Scope [page 41] is completed and milestone Confirm Scoping is Completed is confirmed.
• Activity Specifying Primary Finance Settings [page 54] is completed.

Procedure

1. Open the activity Set Up Organizational Structure.

The status of the activity is automatically set to In Progress.

2. In the Set Up Organizational Structure app, create your organizational structure. For detailed information
about using the app, refer to Using the Set Up Organizational Structure App [page 62].
a. Start the organizational structure creation from creating company code. You can either choose the
Create button and then choose Company Code, or choose the box marked with Create Company Code.
Enter the ID, name, and country/region for the company code.

 Note

You need to assign the company code to a company. You can either choose an existing company or
create a new one.

b. Under the company code, you can create Sales Organization [page 59] and Plant [page 57], depending
on the scope you have chosen earlier. Also you can create multi-assignment units (for example,
shipping points and divisions) as needed by choosing Create button.

Your country/region-dependent scenarios setting may affect the country/region selection for certain
organizational units. For example, if scenario Logistics with Third-Party Warehouse Management (1ZQ)
is only applied for one country/region, then when you create storage location of subtype 3rd Party
WMS, you can only choose that country/region for the storage location.

For some types of organizational units, for example company codes and plants, you can choose to add
an address for a unit, otherwise a dummy address will be assigned.
c. Once an organizational unit is created, only its name and address are changeable.
d. For some organizational units, you can create assignments by choosing the organizational unit and
choosing the Relations tab in the side panel.

Project Experience
Project Experience PUBLIC 61
  Tip

Relation Plant to Sales Organization and Distribution Channel allows multiple distribution channels
in one relation. To assign more than one distribution channels in an existing plant to sales
organization and distribution channel assignment, go to Relations Plant to Sales Organization
and Distribution Channel , choose the name of that assignment. Then you can change the
distribution channel selection in the Edit Assignment dialog.

e. Once you finish the organizational structure creation, confirm the organizational structure by choosing
the Confirm button. You can choose the organizational units to be confirmed. The confirmation may
take some time. There will be a progress bar to show the progression.

 Note

• When you choose an organizational unit to confirm, its parent units (if any) will be
automatically selected for confirmation.
• Once an organizational unit is confirmed, its address will be invisible to avoid inconsistency in
case the address is changed via configuration activities. The changes made to the addresses in
the Product-Specific Configuration phase will not be synced back to the Set Up Organizational
Structure app. You can change or refine the addresses in the Product-Specific Configuration
phase via Configure Your Business Processes [page 66].
• Once an organizational unit or assignment is confirmed, it cannot be deleted or unassigned.
• For the confirmed organizational units, you can change their names and reconfirm.

3. After all mandatory organizational units are created and confirmed, you can use the Complete Activity
button to complete the Set Up Organizational Structure activity. A consistency check will be triggered
to check if all mandatory organizational units and relations are created. You can also set activity Set Up
Organizational Structure to Completed.

Results

Now the organizational structure is created. You can open the Set Up Organizational Structure activity in read
only mode.

The organizational structure will be deployed to the target system after the Scope and Organizational Structure
Phase Is Completed milestone is confirmed. For more information, please refer to Completing the Scope and
Organizational Structure Phase [page 65].

You can change the organizational structure with the Changes via Edit [page 78] functionality.

1.8.2.1 Using the Set Up Organizational Structure App

The Set Up Organizational Structure app provides an intuitive way which allows a graphical, template based,
scope dependent creation of organizational units.

When you open the Set Up Organizational Structure app, you can see boxes marked with possible
organizational units. You can choose the boxes to create the corresponding organizational units. During the

Project Experience
62 PUBLIC Project Experience
creation of your organizational structure, the app also suggests subsequent organizational units (for example,
plants and sales organizations for company codes) in boxes. You can choose these boxes to create the
organizational units.

 Note

For all unit types which appear in the boxes, at least one unit should be defined. There is no upper limit for
the number of organizational units you create for each unit type.

Features

• Create: choose this button to create a company code or a multi-assignment unit. Enter the ID and name
for the unit. The list of countries/regions which you can choose from depends on the countries you have
chosen in scoping.
When you create a company code, you can select the Default Company Code for country/region checkbox
to define it as the default company code for the selected country/region.
• The IDs of the organizational units should not contain lower case letters. When you enter IDs for your
organizational units, the lower case letters are automatically changed to upper case letters.
In evaluation projects, when you create new organizational units, please enter unit IDs according to the
following guidelines:
• For distribution channels and divisions, you create alphanumeric IDs with at least one alphabetic
character.
• For other organizational units, you create alphanumeric IDs, with the last two characters being
alphabetic. For example, you create an organizational unit with ID 10AB or XYAB.
Please note that this guideline does not apply to storage locations.
• When you choose an organizational unit, an Edit or Display panel for that organizational unit is displayed.
Depending on this specific organizational unit, you may see one or more tabs in the panel:
• Relations: you can see the possible additional relations to this unit in this tab, and possible actions
under Actions.
• Status: the confirmation status of this unit.
• Attributes: type of this unit.
• Address
• For the following unit types, you can maintain unit names in different languages:
• Distribution Channel
• Division
• Shipping Point (all types of shipping point)
• Warehouse (all types of warehouse)
• Warehouse Number
• Sales Organization
• Sales Office
• Sales Group
For these types of organizational unit, the organizational unit name displayed is decided by your logon
language. The unit name does not show if the unit has no name maintained in the logon language. When
you create or edit an organizational unit, you need to have a unit name maintained in the logon language
before you can save the unit. In a 3-system landscape, you can choose the Edit in Scoped Languages link

Project Experience
Project Experience PUBLIC 63
 next to the Name field to create unit names in your scoped languages. In a 2-system landscape, you can
use this link to maintain unit names in all available languages.

 Tip

We recommend that you maintain unit names in all scoped languages if you will use the units in those
languages, to avoid further maintenance.

 Note

Please contact your SAP account executive to check the availability of the 3-system landscape.

For other types of organizational unit, you can only maintain one unit name in one single language. These
unit names are always displayed, regardless of the logon language.
• Units to Create and Units to Confirm indicators: these two indicators show the number of organizational
units you need to create and confirm. You can choose them to see the detailed list of organizational units to
be created or confirmed.
When there are mandatory organizational units to be created, the Units to Create indicator is red, the Units
to Confirm indicator is grayed out, as well as the Confirm button and the Complete Activity button. After
all mandatory organizational units are created, the Units to Create indicator turns green and the Units to
Confirm indicator turns red, with the number of organizational units needed to be confirmed, and you can
proceed to confirm your organizational structure with the Confirm button.
• Stacking: several multi-assignment organizational units of same type can be stacked. You can choose
<number> more to unstack the units, and choose Stack above the first unit to stack them. Please note that
sales offices cannot be stacked.
• Close: choose this button to go back to the activity list. Your changes will be saved but not confirmed.
• Complete Activity: choose this button to complete the Set Up Organizational Structure activity. When you
complete this activity, a consistency check is triggered.
• Simplified: when this checkbox is selected, the prompts for subsequent entities creation are hidden. In this
mode, you can see the subsequent entities and choose to create under Actions.
• Graphic view ( ) and table view ( ) buttons: with these two buttons you can switch between graphic and
table views.

 Note

If the size of your organization structure is near the threshold that the application can support in terms
of rendering and displaying, when you open the Set Up Organizational Structure app, your organization
structure opens in table view by default. Please use table view to avoid performance issue.

• Full-screen button ( ): use this button to enter and exit full-screen mode. In the full-screen mode, the
cursor changes to a hand. You can click in the screen and drag to navigate your organizational structure.
• Zoom in ( ) and zoom out ( ) buttons: in graphic view, you can use these buttons to adjust the size of
the diagram.

Project Experience
64 PUBLIC Project Experience
1.9 Completing the Scope and Organizational Structure
Phase

You indicate the completion of the Scope and Organizational Structure phase by confirming this milestone.

Prerequisites

Before you confirm this milestone, make sure you’ve completed all activities of the Scope and Organizational
Structure phase. Each country/region must have a complete organizational structure.

Procedure

1. In the Activities section, go to the Scope and Organizational Structure Phase Is Completed milestone.
2. In the dialog, choose Confirm Milestone.

In a 3-system-landscape, you can enter an optional description of the deployment. The description will be
visible in the staging application in the deployment target.

The confirmation takes some time and consists of two steps (deployment and activation). A progress bar
at milestone level displays the progression of the process. The percentage reaches 100% only once both
steps of the process are completed.

1. Deployment from SAP Central Business Configuration to the deployment target.

2. Scope activation in the deployment target.
Please note that the process may take up to several hours.

After successful activation, the milestone has the status Completed and the project will move to the
Product-Specific Configuration phase.

 Note

In case there are errors during activation, the system displays an Issues badge indicating the number of
issues and that SAP is already working to resolve these issues.

Next Steps

After completing this milestone, you proceed to the Product-Specific Configuration phase.

Project Experience
Project Experience PUBLIC 65
1.10 Configure Your Business Processes

To adjust system settings to your business requirements you carry out configuration activities in the Configure
Your Business Processes app.

To Configure Your Business Processes, the Scope and Organizational Structure phase activities must be
completed and then you are in one of the following phases:

• Product-Specific Configuration or Production System Settings phases (2-system landscape)

• Product-Specific Configuration phase (3-system landscape)

In the Configure Your Business Processes app, you can see the configuration activities organized hierarchically
according to their business areas. You can also see the number of configuration activities in each hierarchical
level. Each configuration activity has a unique identifier (ID) used in the reference materials.

In the Status column, you can see the status of a configuration activity and change it if you are in the Product-
Specific Configuration phase. Once the organizational structure is finished, you can see the final status of
your configuration activity. For further information about the option change the status of your configuration
activities at a mass level, please refer Changing the Status of Configuration Activities [page 68].

Position the cursor on the numbers to see detailed information of the configuration activity status.

The message displayed in the message banner also explains why certain configuration activities cannot be
performed in Central Business Configuration.

The availability of a configuration activity including its documentation depends on the selected scope
(scenarios and countries or regions).

 Note

Launching a configuration activity in the Project Experience opens the target system where you can
process the activity. To process a configuration activity, you must have corresponding authorizations in the
target system as well.

Under the Go-Live Relevance field, the configuration activities are labeled as Mandatory, Optional, or
Recommended.

• Mandatory configuration activities are implementation and project management activities that you must
complete before you can go live with your solution.
• Optional configuration activities: These are configuration activities where making configuration changes is
not critical for "Go Live" and is purely based on the customer needs.
• Recommended configuration activities are not critical for "Go Live", and users need not complete all
recommended activities before Go live. However, these are marked by SAP to indicate the recommended
usage of these activities for making configuration changes on the ones which are very commonly used to
adapt or change some configurations.

In the Product-Specific Configuration phase, the configuration activities are used to configure your business
processes. They are launched in the target system, where a user with necessary authorizations can make
changes as needed and save those changes. For example, Define Sales Organization. Some configuration
activities (configuration applications used to make configuration changes) provide easy access to setup
instructions (CIAS) or setup guides.

Project Experience
66 PUBLIC Project Experience
• Toggle ON: When the toggle is on, you can create new template variants
• Toggle OFF: When the toggle is off, you cannot create new template variants, but get a message on the
screen to reach out to SAP support.

2-System Landscape

Configuration activities which need to be performed directly in the production system are presented in the
Production System Settings phase of the initial implementation project (current settings). The following
diagram shows the configuration activities in the Product-Specific Configuration phase and Current Settings in
the Production System Settings phase.

 Note

Alternatively, once the initial transport to the production system is done, only the current settings for the
configuration activities are accessible and can be executed.

3-System Landscape

 Note

Please contact your SAP account executive to check the availability of the 3-system landscape.

The following diagram shows the Business Processes Configuration details in the Product-Specific
Configuration phase in a 3-system landscape.

Project Experience
Project Experience PUBLIC 67
1.10.1 Changing the Status of Configuration Activities

Context

The Status of a configuration activity can be changed if you are in the Product-Specific Configuration phase.
Once the organizational structure is finished, you can see and change the final status of your configuration
activity. You can use this function to change the status of multiple configuration activities at once. To mass
change the Status of your configuration activities, perform the following steps:

Procedure

1. Under Configuration, you can see the list of configuration activities.

2. Select either a single configuration activity, multiple configuration activities, or the parent configuration
(node). The selection of configuration activities works in both expanded and collapsed state.
3. You can find a configuration activity through the Search field as well.
4. The Mark As button gets enabled when the configuration activities are selected. It has three dropdown
options: Mark as Open, Mark as In Progress, and Mark as Completed.
5. Change the Status as needed. A success banner message is displayed on the screen. The Status Log shows
Original value and the New value of the configuration activity.

1.10.2 Searching for Configuration Activities

You can search for the configuration activity you need.

In the filter bar, you can expand or limit your search using filters such as Search, Go-Live Relevance, Status, and
Business Area. When you search with a name or ID, fuzzy match is supported. You can enter part of the name
or ID and get all the matching results.

The Search is now enhanced with an extended search feature to display all the nodes expanded to the level of a
configuration activity you are looking for. To search for a configuration activity, proceed as follows:

1. In the filter bar, enter the name, keyword, or ID of the configuration activity in the Search field. For example,
• to search a configuration activity with its name, enter Sales in the Search field, and you can see a list
of all the configuration activities with sales in their names.
• to search a configuration activity with its ID, enter the ID (for example, 102182) in the Search field, and
the particular configuration activity assigned to this ID is displayed.
2. Make use of the other filters such as Status, Go-Live Relevance, Business Area, and Country/Region in the
filter bar and to limit your search.

Project Experience
68 PUBLIC Project Experience
Downloading Configuration list

In the Configure Your Business Processes page, you can now download the configuration list as it is displayed in
the UI, including all the filters applied to it in a .CSV file.

Filtering Configuration list

The Filter  icon helps you to diplay or hide the filter parameters. The Adapt Filter button on the right hand
side provides an option for you to narrow down the displayed configuration data according to your business
needs.

You can use the Country/Region filter in the Adapt Filter screen to apply wider filtering options.

• Filter values are determined via countries selected during Scoping.

• Multiple country value selection results in the union of all the selected listed values.

Expanding and Collapsing Nodes in Configuration List

You can now right-click on a node and use the newly introduced context menu with Expand All and Collapse All
option to see different levels of configuration activities and do the same on individual nodes as well.

You can enable the Expand All and Collapse All option in the toolbar as well.

Expand and Collapse Behavior

Previously, the configuration list provided the Search and Filter options, but the structure would move back to
collapsed state whenever a search or filter has been executed. This behavior of the expand/collapse feature is
now fixed to enable easy access to your configuration activities in a faster manner. For a given session, now the
expand/collapse selection made by you is retained as is in cases of search, an applied filter, or a selection of a
different filter attribute done by you.

1.10.3 Performing Configuration Activities and Calling Up

Setup Instructions

The following procedure describes how to perform a configuration activity or call up setup instructions.

Prerequisites

• Milestones Confirm Scoping is Completed and Confirm Scope and Organizational Structure Phase is
Completed are confirmed.

Project Experience
Project Experience PUBLIC 69
Procedure

1. In the navigation pane, go to Configuration. The Configure your Business Processes application page opens.
2. Find the configuration activity you need in the Search field.
• When you select a configuration activity, you are directed to the corresponding configuration step in the
target system.
• To call up a setup instruction, choose the Open Guide hyperlink in its row.
3. After performing the activity, choose Complete Activity to set the Status of this configuration activity to
Completed.

 Note

You need to save your configuration in the activity to have the configuration performed in SAP S/
4HANA Cloud Public Edition. Marking a configuration activity as Completed in SAP Central Business
Configuration does not necessarily mean the configuration is performed in SAP S/4HANA Cloud Public
Edition. The Completed status is only for your reference to give you an overview of the activity status.

1.11 Deployment to the Production System (2-System

Landscape)

 Note

Deployment to the production system is only relevant if you work in a 2-system landscape.

After the initial activation of the business configuration at the end of the Scope and Organizational Structure
phase (via the Scope and Organizational Structure Is Completed milestone), you get access to the quality (Q)
system again. The project will switch to the Product-Specific Configuration phase to perform configuration
settings that will be transported to the production (P) system.

Related Information

Configure Your Business Processes [page 66]

Requesting the Production System (2-System Landscape) [page 71]
Releasing Configuration into Production System (2-System Landscape) [page 73]

Project Experience
70 PUBLIC Project Experience
1.11.1 Requesting the Production System (2-System
Landscape)

In your implementation project, you need to request the production system.

Prerequisites

 Note

Requesting a production system is only relevant if you work in a 2-system landscape.

Before you request a production system, make sure of the following:

• All activities in the Scope and Organizational Structure phase have been carried out.
• The Scope and Organizational Structure Phase Is Completed milestone has been set to completed.

Procedure

1. You are in the Product-Specific Configuration phase. Go to the Request Production System activity and
choose Open.

The Systems view opens. The activity status is automatically set to In Progress.

 Tip

You can also directly navigate to Systems from the navigation pane.

2. A systems list is displayed. Go to row for the production system and choose Request P System.

The production system is then provisioned by the Service Center. The Provisioning Status column reflects
the provisioning status until the provisioning is complete. Once the status changes to Completed, you can
access the production system.
3. Go back to the Activities view to set the Request Production System activity to completed.

Next Steps

During the production system provisioning, you can change the configuration for the quality system in the
implementation project.

Project Experience
Project Experience PUBLIC 71
1.11.2 Assigning a Production System (2-System Landscape)

You assign a deployment target for your production system.

Context

 Note

Assigning a production system is only relevant if you work in a 2-system landscape.

Procedure

1. Go to the Assign Production System activity and choose Open.

A list of available deployment targets is displayed.

 Tip

You can also directly navigate to Deployment Target from the navigation pane.

2. Go to the Action row of your chosen deployment target and choose Assign.

 Note

• You can remove the assigned deployment target only before a transport into the production
system is released.

3. Go back to the Activities view to set the Assign Production System activity to completed.

Related Information

Deployment Target [page 45]

Project Experience
72 PUBLIC Project Experience
1.11.3 Releasing Configuration into Production System (2-
System Landscape)

In your implementation project, you release configuration settings into the production system.

Prerequisites

 Note

Releasing configuration into the production system is only relevant if you work in a 2-system landscape.

• The quality and production systems must have the provisioning status "Completed".
• You have assigned a deployment target for your production system.

Context

After performing configuration activities, you use this procedure to release the configuration settings into the
production system.

 Note

During implementation, it is recommended to repeat this procedure and release transports into the
production system at regular intervals. In this way, you avoid large transports that may lead to errors.

 Note

Once you have completed this procedure for the first time, you can start Maintaining Current Settings
in SAP S/4HANA Cloud Public Edition Production System [page 75]. You do not need to switch to
the Production System Settings phase to access these current settings. This way, you can maintain the
configuration settings both in the quality and production system already after the first transport.

Procedure

1. You are in the Product-Specific Configuration phase. Go to the Release Configuration into Production
System activity and choose Open.

The Systems view opens. The activity status is automatically set to In Progress.

 Tip

You can also directly navigate to the Systems view from the navigation pane.

Project Experience
Project Experience PUBLIC 73
2. In the Quality row, choose Release Transport.
3. In the Release Transport dialog, you can enter an optional description. Choose Release.
4. Optional: After a transport has been released, you can check the transport details. Choose Transport
History to view detailed log information about the release of the transport, such as description, user ID,
date and time.
5. Go back to the Activities view to set the Release Configuration into Production System activity to
completed.

 Note

Set this activity to completed when no further transports into the production system are planned.

1.12 Completing the Product-Specific Configuration Phase

(2-System Landscape)

You indicate the completion of the Product-Specific Configuration phase by confirming this milestone.

Prerequisites

All activities pertaining to the Product-Specific Configuration phase have been completed.

Context

 Note

This milestone is only relevant if you work in a 2-system landscape.

You verify that the Product-Specific Configuration phase is completed and that your project can proceed to the
next phase (Production System Settings phase).

Procedure

1. Choose the Confirm Product-Specific Configuration Is Completed milestone.

2. In the dialog, choose Confirm Milestone.
The milestone has the status Completed.

Project Experience
74 PUBLIC Project Experience
1.13 Maintaining Current Settings in SAP S/4HANA Cloud
Public Edition Production System

You need to maintain the current settings manually, as those settings do not get transported to the production
system.

Some configuration activities (current settings) need to be maintained directly in the SAP S/4HANA Cloud
Public Edition production and testing systems.

2-System Landscape

In a 2-system landscape, you maintain the current settings either in the Production System Settings phase
of the initial implementation project or any time once the initial transport to the production system has been
done.

1. Open Business Processes Configuration.

2. Enter current settings in the search field to filter all relevant configuration activities.

 Tip

Current settings are not categorized by business areas. They are all listed under General Settings
Further Settings .

3. After maintaining all the current settings, set the status of activity Maintain Current Settings in Production
System to Completed.

Once you've defined your current settings in the production system, you can complete the Production System
Settings phase by setting the Confirm Production System Settings are Completed milestone to Completed.

3-System Landscape

 Note

Please contact your SAP account executive to check the availability of the 3-system landscape.

In a 3-system landscape, you can use dedicated apps in SAP S/4HANA Cloud Public Edition to maintain
current settings. For details, please refer to:

• Configuration Environment in a 3-System Landscape

• Implementation Activities

Project Experience
Project Experience PUBLIC 75
1.14 Performing Manual Rework (2-System Landscape)

Configuration activities that require manual rework in the SAP S/4HANA Cloud Public Edition production
system are presented in the Production System Settings phase of the initial implementation project.

Context

 Note

Performing manual rework is only relevant if you work in a 2-system landscape.

In SAP S/4HANA Cloud Public Edition, all configuration settings which are automatically deployed and which
you have manually adapted in the Quality system get transported into the Production system.

Some configuration settings cannot be transported from the Quality system and you have to manually
maintain them again in the Production system after the configuration transport has been imported.

This kind of activity is called Manual Rework activity. You have to check and execute these activities in the
Production system. This must be done whenever configuration settings have been transported, for example,
after initial implementation scope and scope enhancements (new country/region, new scenario).

Procedure

1. In the Production System Settings phase of your implementation project, open the Manual Rework activity.

This leads you to a comprehensive documentation Manual Rework Activities in the Production System
on how to execute manual rework activities. Review the individual topics about how to make the manual
settings in the production system for certain areas.
2. After manually maintaining these configuration settings in the Production system, go back to the Manual
Rework activity and choose Complete Activity to set the status to Completed.

1.15 Completing the Production System Settings (2-System

Landscape)

You indicate the completion of the Production System Settings phase by confirming this milestone.

Prerequisites

All activities belonging to the Production System Settings phase have been completed.

Project Experience
76 PUBLIC Project Experience
Context

 Note

This milestone is only relevant if you work in a 2-system landscape.

With this milestone, you confirm that the Production System Settings phase is completed. This will close the
configuration tasks. Your project will remain in this phase and will be used to handle future changes via Edit, see
Changes via Edit [page 78].

In addition, you must create a support case to set the production system to live. This has to be done only once.

Procedure

1. In the Activities section, go to the Confirm Production System Settings are Completed milestone.
2. Choose Confirm.

The milestone has the status Completed and the project switches to ongoing operations mode.

 Caution

Once you have confirmed this milestone and the project switches to ongoing operations mode, the
project will be locked for changes but remain active.

This mode allows to perform manual rework, maintain current settings, or use the Edit option to make
any edits.

 Note

Please be aware that the ongoing operations mode is not displayed in the user interface. The
project type Implementation Project remains unchanged.

3. Create a support case with the subject 'Production System Live' in component XX-S4C-OPR-SRV. You can
use the description 'Please set the production system to live. We are using the system productively.'

You have to create this support case only once.

Next Steps

In your implementation project, you can use the Edit option to add any enhancements (for example, additional
countries/regions, scope, organizational elements, or configuration settings) later. For more information,
please see Changes via Edit [page 78].

 Note

If you make any configuration changes to your project, for example, a scope extension, you must confirm
the Confirm Production System Settings are Completed milestone again.

Project Experience
Project Experience PUBLIC 77
1.16 Changes via Edit

With Edit you can easily make changes to the scope, organizational structure, and configuration.

In your current evaluation or implementation project, you can use Edit in the following apps:

• Define Scope
• Organizational Structure
• Configure Your Business Processes

 Note

You carry out activities and milestones in a specific sequence. Using Edit will revoke one or multiple already
confirmed milestones and may change the phase you're working in. You need to confirm the respective
milestones again.

If you want to add individual languages, you can also use Edit in Define Scope.

1.16.1 Editing Scope

Use the Edit functionality to make changes in your confirmed scope.

Context

If you want to edit your scope after it is confirmed, you can use the Edit functionality in the Define Scope app.
You can also add individual languages with this functionality.

 Note

When you perform scope extension in an evaluation project, if any existing organizational unit shares the
same ID as a unit ID in the demo data, and the first two characters of this ID represent a country/region
code which is not initially included in your scope, then this country/region cannot be added.

For example, you have an organizational unit ID 1010 in your evaluation project, where the first two
characters, 10, represent the country code for Germany, and Germany is not in your scope. As this ID
is also present in the demo data, you cannot add Germany in the scope extension.

For further assistance, please create a support case in component X4-CBC-ORG.

Procedure

1. Open the Define Scope activity. Choose the Edit button.

Project Experience
78 PUBLIC Project Experience
 Choose whether you want to manually change the status of Configure Your Business Processes back to
Open. The Set Up Organizational Structure activity will be reopened automatically.

The status of the already confirmed milestones will be set to Reopened.

2. The scope is editable now.

 Note

• You can only add scope. It is not possible to delete any countries/regions, bundles, or scenarios.
• When adding new countries/regions, the recommendation is to limit the number of countries/
regions to no more than five.
• You can also use this option to enhance your scope after an upgrade or update. Note that if a
scenario becomes newly available for a country/region in scope and you have previously selected
the same scenario for your other countries/regions, your current scope is not affected. Use this
option to add the scenario to the scope of the missing country/region.

3. Complete scoping by choosing Complete Activity.

1.16.2 Editing Organizational Structure

Use the Edit functionality to make changes in your completed organization structure.

Context

If you want to edit your organization structure after you have completed the Set Up Organizational Structure
activity, you can use the Edit functionality.

 Note

You can only add or edit organizational units and relations via the Edit functionality. It is not possible to
delete confirmed organizational units.

Procedure

1. Open the Set Up Organizational Structure activity. Choose the Edit button.

Choose whether you want to manually change the status of Configure Your Business Processes back to
Open.

The status of the already confirmed milestones will be set to Reopened.

2. The organization structure is editable now.
3. Complete editing by choosing Complete Activity.

Project Experience
Project Experience PUBLIC 79
1.16.3 Editing Configuration

Use the Edit feature to make changes to the completed configuration activities in the Configure Your Business
Processes Configuration app.

Context

 Note

Please be aware that only the completed configuration activities are reopened here, and Scope or Org
changes have to be toggled via the Edit option in each application.

The Edit button in the Configure Your Business Processes Configuration app is visible only after completion
of the Product-Specific Configuration activity. It triggers the initiated change for Product-Specific
Configuration. Once the Edit button is clicked, a pop-up is displayed that prompts you to "Change the
status of Configuration Activities back to Open".

Procedure

1. Open the configuration activity. Choose the Edit button.

2. Edit the configuration activities as needed.
3. Complete the activity by choosing Complete Activity.

1.17 Change Logs

The change log records actions performed in SAP Central Business Configuration and can be used by auditors
to review the information.

All changes done during the evaluation or implementation project, including changes in activities,
milestones, and deployment target are tracked in the Change Logs view. Users with the role
SAP_CBC_CONSUMPTION_AUDITOR have access to the Change Logs view.

In the filter bar, you can select different categories or use the Search field to narrow down the result.

You can also sort and filter data using the Sort Ascending, Sort Descending and Filter options available in most
table column headers.

To refine the list further, you can download the change logs first and use the Microsoft Excel functions.

In the Details column, you can choose Open to get more information on the task performed.

SAP Central Business Configuration takes care of capturing your change logs. For more information, see
Security in SAP Central Business Configuration.

Project Experience
80 PUBLIC Project Experience
Download Logs

You can use the Download Logs functionality to download the CSV file of the filtered logs. Downloading logs can
be done using the following browsers:

• Google Chrome
• Microsoft Edge
• Opera

The downloaded logs display the detailed tasks of each log.

1.18 Lifecycle Management

Lifecycle management in SAP Central Business Configuration supports the central configuration lifecycle and
ensures that the business configuration performed in the SAP Central Business Configuration system are
always in a consistent state.

These capabilities enable controlled adaptations without compromising the ability to adopt new scope and
features. The lifecycle management framework also ensures the priority of the lifecycle processes by queuing
them and then picking for execution.

Upgrades and Updates

In a 3-system landscape, your system regularly imports upgrades or updates. New business content is
automatically deployed to your development system, and if available to your starter system during the software
upgrades and updates governed and executed by SAP. The new business content will then be transported
from the development system using customizing transports. For more information, see Working in the Export
Customizing Transports App.

Project Locks

During the lifecycle of a project, there are several stages, where the project goes into a locked state. This
happens during certain background processes are running. Examples for such background processes are
upgrades, deployment and scoping. When the project is in a locked state, users cannot perform any activities
that would write to the underlying workspace. This is indicated by a lock icon next to the project name and
detailed notification information.

Project Experience
Project Experience PUBLIC 81
1.19 Product Feedback

SAP Central Business Configuration provides an in-application way for users to provide feedback on our
product.

The in-application way to provide feedback helps us to continually improve our software. You can choose the
Product Feedback ( ) icon to launch the survey.

We've also integrated push surveys which are displayed periodically or after certain actions to capture your
feedback.

Our software is continuously being improved with your feedback with regards to product security and user
experience, including comments or suggestions on corrections and enhancements. For more information
about the security aspect for SAP Central Business Configuration , see Security in SAP Central Business
Configuration.

Project Experience
82 PUBLIC Project Experience
2 Accessibility Settings

You can choose the Settings according to your preferences and navigate in SAP Central Business
Configuration.

 Note

The declarations about accessibility in the SAP disclaimers applies to all the accessibility related
documentation.

2.1 Setting a Theme

To select a theme according to your preference, proceed as follows:

Procedure

1. Go to the  (Profile) icon and select Settings.

The Settings screen contains information about your User Account, Appearance, and Language.
2. Go to Appearance to select a desired theme for your business processes configuration.

The four theme options available are: Morning Horizon, Evening Horizon, High-Contrast Black Horizon, and
High-Contrast White Horizon.
3. Click Save.

Project Experience
Accessibility Settings PUBLIC 83
3 What's Changed in this Documentation

Date Version Short description More information

2024/09/30 CBC 2409 We've updated the Shell Bar topic. Shell Bar [page 6]

2024/09/30 CBC 2409 We've updated the Setting Up Setting Up Organizational Structure
Organizational Structure topic. [page 61]

2024/09/30 CBC 2409 We've updated the Editing Scope Editing Scope [page 78]
topic.

2024/09/30 CBC 2409 We've introduced the Country/ Configure Your Business Processes
Region field in the Adapt Filter op- [page 66]
tion.

2024/10/28 CBC 2409 FD1 We've introduced the mass status Configure Your Business Processes
change option for your configuration [page 66]
activities.

2024/09/03 CBC 2406 FD3 We've added a Version column in -

this table.

2024/09/03 CBC 2406 FD3 We've updated the Setting Up Setting Up Organizational Structure
Organizational Structure topic. [page 61]

2024/09/03 CBC 2406 FD3 We've updated the Deployment Deployment Target Details and Deploy-
Target Details and Deployment ment History (3-System Landscape)
History (3-System Landscape) topic. [page 51]

2024/09/03 CBC 2406 FD3 We've updated the Change Logs Change Logs [page 80]
topic.

2024/09/03 CBC 2406 FD3 We've updated the Maintaining Team Maintaining Team Members of a Project
Members of a Project topic. [page 26]

2024/08/05 CBC 2406 FD2 The App name was changed from Configure Your Business Processes
Business Processes Configuration to [page 66]
Configure Your Business Processes.

2024/08/05 CBC 2406 FD2 We've updated the Defining Scope Defining Scope [page 41]
topic.

2024/08/05 CBC 2406 FD2 We've added the Foreign Plant topic. Foreign Plant [page 58]

2024/08/05 CBC 2406 FD2 We've updated the Changes via Edit Changes via Edit [page 78]
topic.

2024/08/05 CBC 2406 FD2 We've harmonized the terminology Deployment Targets in a 2-System Land-
in the Deployment Targets in a 2-
scape [page 46]
System Landscape and Deployment
Targets in a 3-System Landscape Deployment Targets in a 3-System Land-
topics. scape [page 49]

Project Experience
84 PUBLIC What's Changed in this Documentation
Date Version Short description More information

2024/07/07 CBC 2406 FD1 We've enabled the message banner Configure Your Business Processes
to explain why certain configuration [page 66]
activities cannot be performed.

2024/06/19 CBC 2406 We've added the Filter and Down- Searching for Configuration Activities
load Configuration Activities fea- [page 68]
tures topic.

2024/06/19 CBC 2406 We've established the behavior of Searching for Configuration Activities
expand/collapse feature in the con- [page 68]
figuration list irrespective of any
other action performed.

2024/06/19 CBC 2406 We've updated the Working with Working with Projects [page 23]
Projects topic.

2024/07/07 CBC 2406 FD2 We've updated the Changes via Edit Changes via Edit [page 78]
topic.

2024/06/19 CBC 2406 We've updated the Using the Set Up Using the Set Up Organizational Struc-
Organizational Structure App topic. ture App [page 62]

2024/04 CBC 2403 We have updated the user guide for

Hotfix 4" April 22.

2024/04 CBC 2403 We've updated the Specifying Specifying Primary Finance Settings
Primary Finance Settings topic. [page 54]

2024/03 CBC 2406 The user experience enhancements

are reflected throughout the docu-
mentation.

2024/03 CBC 2406 We've updated the Defining Scope Defining Scope [page 41]
topic.

2024/03 CBC 2406 We've updated the Importing Scope Importing Scope [page 43]
topic.

2024/03 CBC 2406 We've updated the Using the Set Up Using the Set Up Organizational Struc-
Organizational Structure App topic. ture App [page 62]

2024/03 CBC 2406 We've updated the Removing an Removing an Assigned Deployment Tar-
Assigned Deployment Target (3- get (3-System Landscape) [page 53]
System Landscape) topic.

2024/03 CBC 2406 We've updated the Shell Bar topic. Shell Bar [page 6]

2024/01 We've updated the Bundle topic. Bundle [page 38]

2024/01 We've updated the Defining Scope Defining Scope [page 41]
topic.

2023/12 We've updated the Phases, Project Phases, Activities, and Milestones in an
Activities, and Milestones in an Evaluation Project [page 14]
Evaluation Project topic.

2023/12 We've added the Product Feedback Product Feedback [page 82]
topic.

2023/12 We've updated the Scenario topic. Scenario [page 39]

Project Experience
What's Changed in this Documentation PUBLIC 85
Date Version Short description More information

2023/12 We've updated the Defining Scope Defining Scope [page 41]
topic.

2023/12 We've added the Importing Scope Importing Scope [page 43]
topic.

2023/12 We've updated the Using the Set Up Using the Set Up Organizational Struc-
Organizational Structure App topic. ture App [page 62]

2023/12 We've added the Removing an Removing an Assigned Deployment Tar-

Assigned Deployment Target topic. get (3-System Landscape) [page 53]

2023/12 We've updated the Shell Bar topic. Shell Bar [page 6]

2023/12 We've updated the Initiating Change Editing Scope [page 78]
topic.

2023/09 We've updated the Phases, Project Phases, Activities, and Milestones in an
Activities, and Milestones in an Evaluation Project [page 14]
Evaluation Project topic.

2023/09 We've updated the Phases, Project Phases, Activities, and Milestones in an
Activities, and Milestones in an Implementation Project [page 19]
Implementation Project topic.

2023/09 We've updated the Shell Bar topic. Shell Bar [page 6]

2023/09 We've updated the Defining Scope Defining Scope [page 41]
topic.

2023/09 We've updated the Country/Region- Country/Region-Specific Scoping and

Specific Scoping and Configuration Configuration [page 29]
topic.

2023/09 We've updated the Using the Set Up Using the Set Up Organizational Struc-
Organizational Structure App topic. ture App [page 62]

2023/09 We've updated the Setting Up Setting Up Organizational Structure

Organizational Structure topic. [page 61]

2023/09 We've updated the Completing the Completing the Scope and Organiza-
Scope and Organizational Structure tional Structure Phase [page 65]
Phase topic.

2023/08 We've updated the Assigning a Assigning a Deployment Target [page

Deployment Target topic. 53]

2023/07 We've updated the Standard Roles Standard Roles and Authorizations
and Authorizations topic. [page 7]

2023/07 We've updated the Assigning a Assigning a Deployment Target [page

Deployment Target and Checking 53]
the Deployment Details (3-System
Checking the Deployment Details (3-
Landscape) topics.
System Landscape) [page 52]

2023/07 We've added the Deployment Target Deployment Target Details and Deploy-
Details and Deployment History (3- ment History (3-System Landscape)
System Landscape) topic. [page 51]

Project Experience
86 PUBLIC What's Changed in this Documentation
Date Version Short description More information

2023/07 We've added the Deleting a Project Deleting a Project [page 27]
topic.

2023/07 We've added the Organizational Organizational Units [page 56]

Units topic.

2023/07 We've updated the Shell Bar topic. Shell Bar [page 6]

2023/07 We've updated the Bundle topic. Bundle [page 38]

2023/07 We've updated the Defining Scope Defining Scope [page 41]
topic.

2023/07 We've updated the Using the Set Up Using the Set Up Organizational Struc-
Organizational Structure App topic. ture App [page 62]

2023/05 We've updated the Variant Operating Variant Operating Chart of Accounts
Chart of Accounts topic. [page 40]

2023/05 We've updated the Setting Up Setting Up Organizational Structure

Organizational Structure topic. [page 61]

2023/05 We've updated the Maintaining Maintaining Current Settings in SAP S/

Current Settings in SAP S/4HANA 4HANA Cloud Public Edition Production
Cloud Production System topic. System [page 75]

2023/05 We've updated the Configuration Configure Your Business Processes

Activities and Performing
[page 66]
Configuration Activities topics.

2023/05 We've updated the Evaluation Evaluation Project [page 12]

Project topic. We've also added a
new topic for Systems and Demo Systems and Demo Data [page 13]
Data.

2023/05 We've updated the Scoping, Bundle, Scoping [page 29]

Scenario, and Defining Scope topics.
Bundle [page 38]

Scenario [page 39]

Defining Scope [page 41]

2023/02 We've updated the Assigning a Assigning a Deployment Target [page

Deployment Target topic.
53]

Project Experience
What's Changed in this Documentation PUBLIC 87
Date Version Short description More information

2023/01 We've updated the Evaluation Evaluation Project [page 12]

Project , Selecting Bundles and
Scenarios, Reviewing Your Scope, Bundle [page 38]
Requesting SAP S/4HANA Cloud
License-Dependent or Non-Standard Completing the Scope and Organiza-
Scenarios, Completing the Scope tional Structure Phase [page 65]
and Organizational Structure Phase,
Assigning a Deployment Target [page
Assigning a Deployment Target,
Industry Chart of Accounts for Public 53]
Sector Management and Performing Variant Operating Chart of Accounts
Configuration Activities topics.
[page 40]

2023/01 We have added the 2-System Land- Deployment Target [page 45]
scape and 3-System Landscape sec-
tions in the Deployment Targets. Deployment Targets in a 2-System Land-
scape [page 46]

Deployment Targets in a 3-System Land-

scape [page 49]

2022/11 We've updated the Define Defining Scope [page 41]

Scope, Deployment Targets,
Lifecycle Management, Performing Deployment Target [page 45]
Configuration Activities. We have
also newly added Checking the Lifecycle Management [page 81]
Deployment Details (3-System
Landscape).
Checking the Deployment Details (3-
System Landscape) [page 52]

2022/08 New section on project locks is Lifecycle Management [page 81]

available.

2022/06 We've updated the Calling Up Setup

Instructions topic.

2022/05 We've updated the Evaluation Evaluation Project [page 12]

Project for the Starter System,
Defining Scope and Configuration Defining Scope [page 41]
Activities
Configure Your Business Processes
[page 66]

2022/01 We've updated the Project Experi-

ence end user guide.

2021/12 We've updated the Deployment Deployment Target [page 45]

Targets, Defining Scope and
Localization topics. Defining Scope [page 41]

Country/Region-Specific Scoping and

Configuration [page 29]

Project Experience
88 PUBLIC What's Changed in this Documentation
Date Version Short description More information

2021/10 We've updated the Organizational Organizational Structure Management

Structure Management and [page 55] and Configure Your Business
Configuration Activities topics. Processes [page 66]

2021/07 We've updated the Phases, Project Phases, Project Activities, and Mile-
Activities, and Milestones in a Starter stones in a Starter Project [page 14] and
Project and Requesting SAP S/ Requesting SAP S/4HANA Cloud Quality
4HANA Cloud Quality System topics. System [page 17]

2021/06 We've published a new version of the

Project Experience application help.

2021/03 We've published a new version of the

Project Experience application help.

2021/02 We've published a new version of the

Project Experience application help.

2021/01 We've updated the Starter Project Evaluation Project [page 12]
topic.

2020/10 We've published a new version of the

Project Experience application help.
It's now available to everyone.

2020/08 We've published a new version of the

Project Experience application help.

2020/06 We've updated the Creating Creating Business Users and Providing
Business User topic. Access Rights

2020/05 We've published a new version of the Confirming Scoping Is Completed [page
Project Experience application help.
44]

Setting Up Organizational Structure

[page 61]

Completing the Scope and Organiza-

tional Structure Phase [page 65]

2020/02 We've changed the product name

from Business Application Factory,
central business configuration to
SAP Central Business Configura-
tion.

2020/01 Early adopters can now access the

Project Experience application help.

Project Experience
What's Changed in this Documentation PUBLIC 89
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Project Experience
90 PUBLIC Important Disclaimers and Legal Information
Project Experience
Important Disclaimers and Legal Information PUBLIC 91
www.sap.com/contactsap

© 2024 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.

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.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN