Greenfield: S/4HANA Cloud Setup & Configuration

On-premise SAP S/4HANA migration offers two routes; which one does the greenfield approach lock you into, and what must happen before anything else?

Before installing on-premise SAP S/4HANA, when can you skip sizing entirely — and when you can't, what does sizing actually determine?

During an on-premise SAP S/4HANA install, what installs the system from the media — and what happens to SAP HANA if a database already exists?

The S/4HANA Cloud development system has two tenants — what are they named, and how does each map to a SAP Central Business Configuration (CBC) project?

A team assumes the SAP Fiori frontend server is only needed for greenfield installs. When is it actually required?

Beyond finding install files, what decision can Maintenance Planner make for you before a brownfield conversion even starts?

How do you reach Maintenance Planner to plan an S/4HANA install — and what housekeeping step keeps you from losing track of the files you need?

In what order must S/4HANA Cloud tenants be provisioned, where is that initiated, and what blocks you from jumping ahead?

Two SAP Central Business Configuration (CBC) roles both sound like leadership; which one is unrestricted across all projects, and which is scoped to assigned projects?

You need custom roles in S/4HANA Cloud, public edition. Do you build them from scratch, and how do you even find the right starting point?

You spot the SAP Central Business Configuration (CBC) role SAP_CBC_CONSUMPTION_ACTIVITY_ALL and reach for it as a broad project-lead role. Why is that a mistake?

CBC distinguishes an evaluation project from an implementation project. Which systems does each drive, and what is each actually for?

For an evaluation project, do you have to model your whole company's organizational structure like you do for an implementation project?

Can several SAP Central Business Configuration (CBC) projects share one S/4HANA Cloud deployment target, or is the wiring per project?

In SAP Central Business Configuration (CBC) you can't jump straight to the organizational structure before selecting scenarios. How does this guided model differ from S/4HANA Cloud private edition?

When you set a deployment target's demo-data option, why is that a decision you can't afford to defer or get wrong?

In SAP Central Business Configuration (CBC), the Key User role can edit project activities within its assigned projects — so why can't a key user simply close out a phase?

In a fit-to-standard workshop for S/4HANA Cloud, what is the guiding question you ask about each business process — and why does the direction matter?

You search SAP Help for a business process and get no results. Before assuming it doesn't exist, what should you suspect?

A "fully implemented" process in S/4HANA Cloud public edition can be built from which three layers — and which layer tends to cost the most?

All project activities are done — what single action makes SAP Central Business Configuration (CBC) actually generate and push the configuration to the S/4HANA Cloud tenant?

For a given piece of functionality, where does its configuration live — SAP Central Business Configuration (CBC) or S/4HANA Cloud — and how do the test and production tenants get it?

To actually maintain a configuration entry in the S/4HANA Cloud tenant from SAP Central Business Configuration (CBC) and get it to test/production, what's the path — and what authorization catch bites here?

After the initial deployment, how do you adjust the preset configuration in SAP Central Business Configuration (CBC), and why don't you see every possible activity in the list?

Some S/4HANA Cloud settings can't be managed through SAP Central Business Configuration (CBC) at all and must be redone as manual rework in each system. What kinds of settings are these?

Name the four systems that make up the SAP S/4HANA Cloud public edition landscape (the "three-system landscape").

A requirement isn't exposed by CBC's guided configuration. When does that mean you drop to "advanced configuration management" rather than concluding it can't be configured?

You're choosing how much to invest in CBC skills and processes. Does SAP intend CBC to stay an S/4HANA-Cloud-only tool, and how should that shape the bet?

Is SAP Central Business Configuration (CBC) a one-time scoping wizard you run at kickoff, or something you keep using?

In the S/4HANA Cloud landscape, which system is where fit-to-standard workshops and early exploration happen — not where you build the transportable solution?

In CBC's Organizational structure area, can you just model your full org chart, or is the set of org elements constrained by something upstream?

Both the Starter and Development systems in S/4HANA Cloud have two tenants — what is the load-bearing difference in their role?

The Test and Production systems in S/4HANA Cloud each have one tenant — how do you tell which is which, and why does the distinction matter operationally?

Given its name, you might reach for the Business Adaptation Catalog (BAC) to build a custom adaptation. Is that what it's for?

You need to add a new country to a live S/4HANA Cloud solution. Is that a fresh initial implementation or a SAP Central Business Configuration (CBC) "delta deployment"?

In Maintenance Planner, which planning step adds optional products like Ariba integration, and what do you pick under Select Files before pushing to the Download Basket?

SAP Cloud Appliance Library has long built test/eval systems; what changed in 2022 that makes it viable for production, and on which hyperscaler?

You want a production-ready SAP S/4HANA on Azure without opening Maintenance Planner in a separate window. What does Cloud Appliance Library give you, and what account must you attach?

Trying to scope both IFRS and US GAAP for the United States, you find one becomes greyed out. Why, and what protects you here?

You have a high volume of configuration entries (or config already done in another tenant). How do you load it in bulk — and why can't you just open the upload app from the launchpad?

Where do CBC's steps actually sit within the SAP Activate methodology, and how do you isolate just the CBC-relevant steps in the roadmap?

How do SAP Cloud ALM and SAP Central Business Configuration (CBC) divide the work, and what's the concrete step to wire them together?

Can the SAP S/4HANA Fully-Activated Appliance stand in for a custom installation of a production system?

What is an 'up-to-date installation', and how does the Stack.xml file let you avoid re-registering a freshly installed system?

A third-party add-on can't be selected in Maintenance Planner, and afterward you must apply release-specific SAP Notes. Which transactions handle each?

For configuring SAP S/4HANA Cloud public edition, when do you use SAP Central Business Configuration versus the Fiori app Manage Your Solution?

You're setting up org structures in a fresh S/4HANA client. What is the smallest unit you must create for financial accounting, what drives you to define plants, and could any process run without org units at all?

Up to what point can you still restructure — change or delete — the organizational units you've created in SAP Central Business Configuration (CBC)?

How do developer extensions built during fit-to-standard in the Starter system get carried into the Development system?

For a sandbox SAP S/4HANA system, does SAP recommend splitting the ABAP backend and Fiori frontend, and how is that expressed in Maintenance Planner?

In CBC, what does each project's 'deployment target' point to, and by what path do extensions reach the production tenant?

In the Setup Organizational Structure activity, the number next to "Units to Create" is red. What does that mean, and is there a cap on how many units you add?

You need to maintain custom business-configuration objects in S/4HANA Cloud. Which app is the entry point, how do you navigate to it, and what authorization must your user hold?

A scenario you need isn't in standard provisioning or requires a separate license. How do you get it added to your solution scope?

For a fit-to-standard workshop, should SAP Central Business Configuration (CBC) hand stakeholders an empty system to build in, or a preconfigured one?

You open Define Scope in SAP Central Business Configuration (CBC). It first asks for country/region, then offers bundles — what do Baseline Accelerator, Enterprise Management, and Retail each cover?

Why must "Determine the solution scope" in SAP Central Business Configuration (CBC) be settled before you configure the organizational structure?

In S/4HANA Cloud public edition, why must you assign roles twice — once for the cloud system and once for SAP Central Business Configuration (CBC)?

What breaks if two parallel SAP Central Business Configuration (CBC) projects (e.g. configuring the starter system and the development system) share one configuration instead of separate "business configuration workspaces"?

SAP Central Business Configuration (CBC) integrates with SAP Activate and SAP Cloud Application Lifecycle Management (ALM). A practitioner with on-prem habits names a third tool here — which one, and why is it wrong?

With SAP S/4HANA in a private cloud (Infrastructure as a Service (IaaS)) versus SAP S/4HANA Cloud, who controls the update cycles and target release — and why might that decide the model?

Two SAP Central Business Configuration (CBC) roles are both read-only over project activities. What can one do that the other cannot, and why would you assign it?

You've confirmed the solution scope but SAP Central Business Configuration (CBC) still won't distribute the preconfiguration to the tenant. What's the missing prerequisite?

When setting up the first users on a newly provisioned SAP Central Business Configuration (CBC) / S/4HANA Cloud tenant, why can't you just start with any admin account, and who takes over afterward?

You want to explore configuration options without risking the development system. How do you set up a consequence-free environment in SAP Central Business Configuration (CBC)?

You're creating several company codes in SAP Central Business Configuration (CBC). Why does marking one of them as the default change how the system treats the rest?

What ensures fit-to-standard planning results are signed off before they move to development or production — and why does that let SAP Central Business Configuration (CBC) implementation skip further approvals?

Next to scoping and organizational structure, SAP Central Business Configuration (CBC) has core components that are easy to overlook. Which one guides you through the project, and which one adapts processes centrally?

When is an organizational structure considered "complete" in SAP Central Business Configuration (CBC), and who checks that — unlike older SAP operating models?