Many SAP customers assume that modern development practices such as Git, CI/CD pipelines, and automated testing only become possible after moving to S/4HANA Public Cloud.
Organisations running S/4HANA Private Cloud can adopt these practices today while maintaining a Clean Core architecture.
The key is not the deployment model; it’s how development is structured around the ERP system. This article explores how organisations can modernise ABAP development using Git integration, automated pipelines, and quality governance, while keeping their S/4 core stable and upgrade ready.
What Clean Core Means in Private Cloud
A Clean Core strategy focuses on maintaining the integrity of the SAP core system while enabling innovation through controlled extensions
In practice this means:
- Keeping S/4HANA close to standard
- Using released APIs and extension points
- Avoiding modifications to SAP standard objects
- Moving integrations and external logic outside the ERP core
- Enforcing governance through automated quality checks
Clean Core does not mean eliminating custom development.
Instead, it means ensuring custom logic is implemented in a way that remains upgrade-safe and maintainable over time.
Why Modern Engineering Practices Matter
Many SAP landscapes still rely on traditional development models:
- SE80 development
- manual transports
- limited automated testing
- little or no version control
This approach creates several challenges:
- slow delivery cycles
- higher regression risk
- difficulty collaborating across teams
- limited traceability
Modern engineering practices solve these problems by introducing:
- Git-based version control
- CI/CD pipelines
- automated testing
- automated code quality checks
- Eclipse IDE enabled for SAP Development (ADT)
These practices are standard in modern software engineering and are increasingly becoming part of SAP development environments as well.
Git Integration for ABAP Development
There are two primary ways to integrate Git with SAP systems.
1. Git-enabled Change and Transport System (gCTS)
gCTS is SAP’s native Git integration.
Instead of relying solely on traditional transports, developers commit ABAP changes directly to a Git repository.
Typical workflow:
Developer → Git commit → CI/CD pipeline → Deployment to SAP system
Benefits include:
- distributed version control
- branching and merging
- integration with modern DevOps tools
2. abapGit
abapGit is an open-source tool widely used in the SAP ecosystem.
It allows ABAP repositories to synchronise with Git platforms such as:
- GitHub
- GitLab
- Asure DevOps
Many organisations adopt abapGit as an initial step toward Git-enabled SAP development because it integrates well with existing transport landscapes.
Introducing CI/CD Pipelines in SAP Landscapes
Once code is stored in Git, organisations can implement CI/CD pipelines to automate development workflows.
A typical SAP pipeline may include:
- Code commit to Git
- Automated code quality checks (ATC)
- Execution of ABAP Unit tests
- Integration tests for APIs and services
- Deployment to QA or integration environments
This pipeline reduces manual effort while ensuring consistent quality standards across development teams.
Automated Quality Gates with ATC
The ABAP Test Cockpit (ATC) plays a critical role in Clean Core governance.
ATC checks can enforce rules such as:
- preventing usage of unreleased APIs
- identifying performance issues
- enforcing secure coding standards
- detecting obsolete syntax
- ensuring compliance with Clean Core principles
When integrated into CI/CD pipelines, ATC becomes a quality gate that prevents non-compliant code from entering the system landscape.
Automated Testing for ABAP Applications
Testing automation is another key component of modern SAP development.
Common testing layers include:
ABAP Unit Tests
Used to validate business logic in isolation.
Integration Tests
Used to test OData services, APIs, and system interactions.
UI Testing
Used for validating Fiori applications and user workflows.
When integrated into CI/CD pipelines, these tests allow teams to deploy changes with significantly greater confidence.
The Role of SAP BTP
In a Clean Core architecture, SAP Business Technology Platform (BTP) complements the S/4 core.
BTP can host:
- side-by-side applications
- integration services
- workflow automation
- external APIs
However, it is important to emphasise that BTP is not required for all custom logic. Business logic that belongs within ERP processes can still be implemented safely inside S/4 using modern ABAP development patterns such as RAP and released APIs.
A Modern SAP Development Architecture
A modern SAP DevOps architecture typically includes:
- Developers using ADT (Eclipse) and Git
- Git repositories for version control
- CI/CD pipelines for automated validation
- ATC checks enforcing Clean Core rules
- Automated testing before deployment
- S/4HANA Private Cloud running stable ERP processes
- BTP services supporting integration and extensions
This architecture allows organisations to combine the stability of ERP systems with the agility of modern software development.
Conclusion
Clean Core is not simply about reducing custom code.
It is about building an ERP landscape that:
- remains upgradeable
- supports modern development practices
- enables innovation without compromising system stability
By introducing Git integration, CI/CD pipelines, automated testing, and governance through ATC, organisations can modernise their ABAP development environments while continuing to run S/4HANA Private Cloud.
The result is an ERP landscape that is both stable and adaptable, capable of supporting evolving business requirements and modern engineering practices.
If your organisation is exploring how to modernize SAP development while maintaining a Clean Core strategy, our team at ETZ Global can help design and implement a modern SAP DevOps architecture.