From SPRO IMG customizing to SSCUIs and Central Business Configuration (CBC)

Why customizing changes in S/4HANA Cloud

In SAP ECC and on-premise SAP S/4HANA, consultants maintain business configuration across thousands of implementation guide (SPRO IMG) activities and customizing tables. In SAP S/4HANA Cloud Public Edition, direct access to arbitrary SPRO tables is replaced by governed Self-Service Configuration UIs (SSCUIs) managed through SAP Central Business Configuration (CBC) or the Manage Your Solution app.

Common migration gaps between SPRO and CBC

When moving a business process or company code template from an existing system to S/4HANA Cloud, several structural differences appear:

• No 1:1 SSCUI equivalent. Some classic customizing tables are pre-delivered by SAP standard content and cannot be modified by customers.
• Namespace and key format constraints. Organizational units, document types and number ranges follow stricter naming conventions in cloud configuration.
• Prerequisite scope items. An SSCUI is only editable when its underlying scope item is activated in the CBC project workspace.
• Replacement by BRFplus or key user extensibility. Logic previously stored in customizing exits or condition tables moves to decision tables or released BAdIs.

How to audit SPRO settings before fit-to-standard

1. Export the active customizing table entries and modified IMG activities from the source system.
2. Map each table and IMG activity to its target SSCUI, scope item or pre-delivered standard setting.
3. Flag entries that rely on customer namespaces or classic user exits that are unavailable in the target edition.
4. Feed unresolved configuration gaps into the fit-gap backlog with clear clean core alternatives.

ERP Preflight's SPRO2Cloud and SAP Gap Radar engines evaluate exported customizing metadata and identify cloud configuration mappings and fit-gap risks with verifiable evidence. See Migration & Clean Core.