Defining Scope and Localizations

The deployment target is where SAP Central Business Configuration will activate the business processes and country/regions. Each workspace should be connected to one of the two SAP S/4HANA Cloud development system tenants.

Learn how to assign a deployment target in SAP Central Business Configuration in this tutorial:

When the partner lead configuration expert opens the scope activity, you are prompted to select the customer's sector (private or public sector), then choose the country/region(s) in which the development system content should be activated. You can also select any languages besides the default associations. For example, German is the default language for the country, Germany, but you could also turn on additional languages. Please note that English is a default language for all countries (in addition to that country's primary language), and cannot be de-selected.

Localization is the process of adapting business processes and languages to fit different countries and regions. SAP S/4HANA Cloud Public Edition covers approximately 55 standard local versions in 33 languages, with additional local versions and languages being continuously added each release. We differentiate localizations into two main categories: SAP-delivered local versions and customer local versions.

In the scope activity in SAP Central Business Configuration, you will see a button called More Countries/Regions if the Configuration Localization Toolkit (CLT) is enabled. Select this button to choose a source country/region (where business content is inherited from) and a target country/region. Currently, only Germany can be selected as the source country/region. The full list of target countries are documented in SAP Note 3107866.

Watch this video to learn how the Configuration Localization Toolkit works in SAP Central Business Configuration, and further extensions that can be made in SAP S/4HANA Cloud.

• Are there unique reporting and/or compliance requirements for this country/region?
• In which lines of business are there unique requirements?
• Do we need to change existing reports or create new, custom reports to align with requirements?
• Are the built-in features of Advanced Compliance Reporting enough to align with local requirements? If not, consider SAP Document and Reporting Compliance, which is an end-to-end solution that enables you to create, process, and monitor transactional documents and periodic regulatory reports across countries or regions.
• Do we need to change any process flows, applications, or output documents to align with requirements?

After selecting the Sector, Country/Region(s), and Languages, the partner lead configuration expert selects the scope bundle. There are two scenarios for the different bundles:

• Baseline Accelerator bundle - the customer needs some business processes across a few lines of business (LoBs). This bundle preselects a set of approximately 60 business processes that are absolutely necessary for the core Administrative ERP processes between Finance, Sales, and Sourcing and Procurement to function correctly. From there, you can add additional processes in other LoBs ad-hoc to align with the finalized scope documented in SAP Cloud ALM.
• Enterprise Management bundle - the customer needs many business processes across most LoBs. Keep in mind, business processes that are part of the bundle cannot be removed because there are technical interdependencies between many of these processes.

After choosing a bundle, select the My Selected Scope button to view a list of all the selected processes and compare with the chosen processes in SAP Cloud ALM.

Next, select the group ledger scenario(s). During this initial scoping, you must decide which (if any) additional valuations are needed for the customer's financial data. By default, the system is delivered with a single, leading ledger (0L) assigned to the local accounting principle. The leading ledger is from the business process J58: Accounting and Financial Close, which is always active.

In SAP S/4HANA Cloud Public Edition, you can choose to add an additional ledger and accounting principle to cover:

• Ledger 2L (non-leading ledger): Accounting and Financial Close - Group Ledger IFRS (International Financial Reporting Standard) (1GA)
• Ledger 3L (non-leading ledger): Accounting and Financial Close - Group Ledger US GAAP (United States Generally Acceptable Accounting Procedures) (2VA)
• Ledger 4G (non-leading ledger): Group Valuation (5W2)

Selecting additional ledgers during scoping is critical because you can’t modify the settings after completing the activity. The SAP S/4HANA Cloud system is fixed with the valuations you chose during initial scoping.

If there will be multiple countries/regions, it's possible to select both ledgers and choose for which countries/regions the different ledgers are used.

Learn more about Ledger Scenarios and Assigning Accounting Principles to Ledgers and Company Codes.

In addition, there are several integration-related business processes that are excluded from the default bundles because they require a license for an additional product. Only add these to the scope if they are relevant for the customer - meaning the customer has a license for the other required product(s). After making these selections, complete the activity.

Learn how to define the scope and localizations in SAP Central Business Configuration in this tutorial:

Not all integration scenarios can be activated in SAP Central Business Configuration. For scenarios not available in the scoping, create a case in SAP for Me → Services and Support dashboard to request activation.