SAP Central Business Configuration Tutorial: Scope, Countries and Org Structure (Part 3)

SAP Central Business Configuration Tutorial: Scope, Countries and Org Structure

What you will build

You will understand the main CBC configuration sequence and the reason each stage exists.

CBC provides guided configuration for S/4HANA Cloud Public Edition. The exact screens can change by release, so focus on the lifecycle rather than memorizing button positions.

1. Project setup

A CBC project represents the configuration initiative.

Before choosing scope, establish:

• project ownership;
• implementation landscape;
• countries/regions;
• business scope;
• organizational assumptions;
• governance for configuration decisions.

2. Select countries and regions

Country/region choice matters because localization can influence:

• legal reporting;
• tax;
• payment formats;
• business documents;
• local processes.

Do not add countries “just in case.” Scope decisions should reflect the rollout.

3. Select business scope

Choose the business processes required for the implementation.

Review dependencies.

A process may rely on another process, organizational unit, integration or master-data setup.

The scope should match signed business decisions from fit-to-standard.

4. Define organizational structure

Organizational design determines how transactions are owned and reported.

Typical concepts can include:

• company/company code structures;
• plants/locations;
• sales/purchasing organizations;
• other application-specific units.

Do not copy the ECC organizational model automatically. Use the cloud transformation as a chance to simplify where possible.

5. Configuration activities

After scope and organizational decisions, configuration activities refine process behavior.

Examples can include:

• finance settings;
• number ranges;
• document rules;
• workflow-related settings;
• local process parameters.

The exact activity set depends on chosen scope and release.

6. Configuration governance

Every configuration decision should have:

• business owner;
• reason;
• target system;
• test case;
• transport/deployment expectation;
• documentation.

This matters because cloud systems continue to evolve after go-live.

7. CBC is not the only configuration surface

Public Edition can involve configuration across CBC and in-app configuration experiences depending on the setting.

The key is to know:

• where the setting is owned;
• how it is transported/deployed;
• who is authorized to change it;
• whether it is customer-specific or SAP-delivered.

Checkpoint

You should now be able to explain the chain:

Project → Country/Region → Scope → Organizational Structure → Configuration Activities → Deployment/Test

Common mistakes

• Selecting scope before business sign-off.
• Copying the old organization structure without challenge.
• Making CBC changes without traceability.
• Assuming every configuration setting exists in the same tool.
• Ignoring localization effects.

Interview takeaway

“CBC centrally guides Public Edition configuration. I use fit-to-standard decisions to drive country, scope and organizational setup, then maintain configuration activities with clear ownership and test evidence. I also distinguish CBC-managed configuration from other in-app configuration surfaces.”

A global project copies the old company-code and plant structure into CBC. During design review the team discovers several legal entities are no longer operational. Simplifying the model before configuration avoids unnecessary roles, master data and reporting complexity.

• Scope before process decision.\n- Old org structure copied blindly.\n- No configuration owner.\n- No deployment/test traceability.

• Drive CBC from signed fit-to-standard decisions.\n- Keep org design intentional.\n- Document localization decisions.\n- Link every configuration change to a test.

Explain what CBC does and the correct order of scope, organization and configuration decisions.