SAP Customizing
SAP Customising is the adaptation of an SAP system to company requirements via the IMG – without changing the standard code.
What is SAP Customising?
SAP Customising refers to the individual adaptation of an SAP system to the specific requirements of a company – without changing the SAP standard code. It is the key to integrating business processes into SAP and thus to making optimal use of the software.
Customising is carried out using the Implementation Guide (IMG), in which system parameters for business processes are defined. Examples range from defining company codes to setting up document types or pricing procedures.
Customising is becoming even more important, particularly in the context of SAP S/4HANA, as many processes are standardised but still flexible.
Steps to successful SAP customising (on-premises/private cloud)
A structured approach is crucial to the success of a customising project. The typical steps include:
1. Requirements analysis: Recording and documenting business requirements in close cooperation with the specialist departments.
2. Understanding system architecture: Analysing the existing SAP landscape and relevant modules.
3. Concept development: Creation of a customising concept that takes into account processes, organisational structures and data flows.
4. Customising in SAP IMG: Implementation of configurations in the SAP Implementation Guide (IMG).
5. Testing and quality assurance: Performing integration tests and validation with the specialist departments.
6. Documentation: Complete and comprehensible documentation of all settings.
7. Go-live: Transporting the settings via transport orders.
8. Support and optimisation: Ongoing maintenance during operation.
SAP-Customizing in der Public Cloud (SAP S/4HANA Cloud, Public Edition)
Customisation in the public cloud differs fundamentally from the classic on-premise approach.
Basic principle: "Fit-to-standard" instead of "Design-to-customise"
While processes can be highly customised in on-premise systems, the public cloud takes a standardised approach:
- Use of predefined SAP best practices and scope items
- Configuration only within approved parameters
- No modification of the SAP core
- Strict separation between configuration and extension (in-app/side-by-side)
The focus is on adapting processes to the standard, not on adapting the standard to the company.
Procedural model in the public cloud
Implementation typically follows the SAP Activate methodology with a fit-to-standard workshop approach:
1. Discover & 2. Prepare
- Selection of suitable best practice scenarios and scope items as part of the DDA (Digital Discovery Assessment)
- Setup of the starter system
3. Explore (fit-to-standard workshops)
- Running through predefined SAP processes
- Identifying deviations (gaps)
- Decision: use standard, adapt configuration or develop extension
4. Realise
- Configuration via Central Business Configuration (CBC) with self-service configuration UIs
- Implementation of approved extensions
- Conducting training and tests
5. Deploy
- Data migration
- User enablement
- Go-live
6. Run
- Continuous optimisation
- Use of release updates (half-yearly updates)
Tools in the public cloud
In contrast to the classic IMG, configuration is carried out via:
Central Business Configuration (CBC): Central tool for defining:
- Organisational structures
- Country and financial configuration
- Scope activation
- "Customising"
Self-Service Configuration UIs (SSCUI): Fiori-based interfaces for customising specific settings.
Expert Configuration: Limited access to deeper customising settings (only within a defined scope).
In-app extensibility
- Custom fields
- Custom logic (key user extensibility)
- UI customisations
Side-by-side extensibility (SAP BTP)
Developer extensibility
- For complex enhancements outside the S/4HANA core.
Key differences: On-premises vs. public cloud
| Area | On-Premise | Public Cloud |
| IMG access | Complete | Not available |
| Modification | Possible (not recommended) | Not permitted |
| Transport sector | Traditional transport orders | Export/Import Software Collection |
| Updates | Project-driven | Automatically every six months, with Delta Scope check |
| Process freedom | Very high | Standardised |
| extensions | ABAP | Key User + BTP + Developer Ext. |
Advantages of the public cloud approach
- Faster implementation through best practices
- Lower project complexity
- Update security
- Reduced maintenance effort
- Higher speed of innovation
Challenges in the public cloud
- Limited customisation
- Shift in thinking from "customisation first" to "standard first"
- Strict governance required
- Dependence on SAP release cycles
Best Practices für Customizing in der Public Cloud
| Recommendation | Benefit |
| Consistent use of best practices | Faster implementation |
| Document GAP analysis clearly | Transparent basis for decision-making |
| Extensions only if they offer genuine added value | Maintainability and upgradeability |
| Early involvement of specialist departments | Greater acceptance |
| Establish release management | Stability despite half-yearly updates |
FAQ – Frequently asked questions about SAP Customising
Is classic IMG customising still available?
No. Configuration is carried out using CBC, SSCUIs and Fiori-based tools.
Are custom developments possible?
Yes, but preferably via in-app extensibility, developer extensibility or side-by-side extensions on the SAP Business Technology Platform (BTP).
How do transports work?
Via software collections – not via classic transport requests.
How do updates work?
Updates are performed automatically every six months, but require delta checks of the new release. Therefore, enhancements and configurations must be upgrade-stable.
Fazit
SAP Customizing im Wandel
While maximum flexibility was the main focus in the classic SAP environment, the public cloud emphasises standardisation, governance and innovation. Customisation remains essential in the cloud – but with a clear paradigm shift: from individual system design to the intelligent use of standardised processes. Especially in the context of digital transformation, this not only creates efficiency but also ensures long-term future security.
![[Translate to English:] Person in Business-Kleidung steht vor einer Wand, auf der verschiedene Symbole und Icons im Zusammenhang mit Business-Strategie](/fileadmin/_processed_/0/7/csm_strategie_cfbca1f3e7.jpg)
![[Translate to English:] Abbildung zeigt mehrere Glühbirnen nebeneinander mit Projekt-Management-Begriffen darin](/fileadmin/_processed_/d/e/csm_SAP_Activate_55947d6325.jpg)
