Standard clean-core-remediation-benchmarks often fail to account for the complexity of legacy business processes embedded in custom ABAP code. While some consultants advocate for stripping out custom logic to achieve a ‘clean’ state, this approach often destroys the proprietary intellectual property that keeps a business running.
The Myth of the Pristine Core in Enterprise SAP
Standard industry advice often pushes for a “clean core” strategy, suggesting that organizations should strip away all custom ABAP and move logic to external platforms to simplify S/4HANA maintenance. This approach ignores the reality of complex enterprise operations. For many companies, custom code is not a technical debt burden; it is the codified history of their specific business processes, and removing it often breaks the very workflows that make the business profitable.
ETZ rejects the idea that a perfectly pristine core is the only path to a successful S/4HANA migration. Forcing an enterprise to move deeply integrated, custom-built logic into the SAP Business Technology Platform (BTP) simply to satisfy a “clean core” ideal often creates more integration points and complexity than it solves. We believe that custom code is valuable intellectual property. Instead of purging it, the focus should be on modernizing that code - refactoring legacy ABAP to modern standards while keeping it within the core where it belongs.
Maintaining a manageable environment does not require a total purge of customizations. It requires a pragmatic approach to technical debt. When looking at clean-core-remediation-benchmarks, the most successful transitions occur when companies prioritize stability and functionality over dogmatic adherence to a “pure” standard. We focus on keeping the system functional and manageable, ensuring that the core remains stable enough for upgrades while preserving the custom logic that defines your competitive advantage.
Why Custom ABAP is Proprietary Business IP
Custom ABAP code is not technical debt; it is the encoded logic of your unique business processes. Over decades, these modifications in the core and on-core layers capture specific regulatory requirements, localized tax logic, and unique manufacturing workflows that standard SAP functionality cannot replicate. When a company strips out these customizations to satisfy a “clean core” ideal, they are effectively deleting their own competitive advantages and operational history.
Most enterprise SAP environments rely on custom Z-programs and modified standard objects to function within specific market constraints. These modifications represent the only way the business can execute its specific goals in a given geography or industry. Moving this logic to a separate layer or replacing it with generic functionality often results in a loss of granular control and requires extensive manual workarounds to achieve the same result.
ETZ treats custom code as a vital asset. Instead of purging these capabilities during an S/4HANA migration, we focus on modernizing the existing ABAP code to ensure it remains performant and compatible with the HANA database. This approach preserves the business’s intellectual property while ensuring the system remains maintainable. We focus on keeping the logic where it belongs - within the core - so the business continues to run exactly as it did before the transition.
Analyzing Clean-Core-Remediation-Benchmarks
Standard clean-core-remediation-benchmarks often rely on theoretical metrics that fail to account for the complexity of legacy ABAP logic. Many consultants claim that moving custom logic to SAP BTP simplifies the upgrade path, but they rarely calculate the overhead of maintaining and synchronizing two separate environments. If a business process requires specific, complex calculations in a production module, decoupling that logic into an external sidecar creates integration points that require constant monitoring and maintenance.
Real-world performance is measured by the time it takes to validate and deploy a quarterly SAP release. In a strictly
Technical Debt vs. Business Value in S/4HANA
Many organizations view custom ABAP code as technical debt that must be purged to reach a “clean” state. This perspective ignores the reality that custom logic often encodes specific, high-value business rules that standard SAP functionality cannot replicate. When a company replaces a 20-year-old custom Z-program with a standard process, they risk losing the nuanced edge that defines their competitive position in the market.
Instead of chasing a theoretical purity, focus on the actual ROI of the code. If a custom development in a warehouse management module reduces manual entry errors or accelerates shipping cycles, it provides measurable business value. Stripping this out just to satisfy a “clean core” checklist creates a new type of debt: the cost of re-engineering lost functionality. We prioritize the preservation of your proprietary IP during the move to S/4HANA.
Analyzing clean-core-remediation-benchmarks often shows that the time required to re-engineer complex custom logic into the standard core is substantial. For example, some organizations spend months trying to find a standard workaround for a specific tax calculation logic that was already perfected in their legacy system. We advocate for modernizing this existing code - refactoring it to run efficiently on HANA - rather than discarding it. This approach maintains the integrity of your operations while ensuring the system remains stable and performable.
Managing Complex Environments with Managed Services
Managed services provide a practical way to maintain system stability while keeping custom business logic intact. Many organisations struggle to balance the requirements of an S/4HANA migration with the ongoing demand for high availability and performance. A managed service model addresses this by handling the heavy lifting of platform maintenance, patching, and performance tuning of the SAP production environment.
Instead of internal teams spending their time on routine monitoring or resolving common infrastructure bottlenecks, they can focus on business-critical projects. This is particularly important when managing complex, non-standard ABAP code that reflects specific manufacturing processes or unique supply chain rules. By outsourcing the “keep the lights on” tasks to experts who understand the nuances of SAP technical debt, companies can maintain their custom IP without it becoming a burden on internal resources.
Reliability is measurable in the speed of operational responses. For example, a managed service approach can significantly reduce the time required to validate quarterly releases or apply SAP Notes. Rather than spending weeks testing the impact of a patch on custom objects, a managed service team provides a consistent, documented process to ensure that the environment remains stable. This consistency provides a clear alternative to the volatility of internal teams juggling both innovation and maintenance.
Modernizing Legacy Code Instead of Replacing It
Many organizations treat custom ABAP as a burden to be purged during an S/4HANA transition. This approach ignores the reality that custom code often contains the specific business logic and competitive advantages that define a company’s operations. Instead of trying to rebuild these processes from scratch in a “clean” environment, the focus should be on modernizing the existing code base to ensure it remains performant and maintainable on the HANA database.
Modernization means moving away from obsolete techniques, such as nested selects or inefficient loops, and replacing them with modern ABAP syntax and HANA-optimized SQL. This preserves the core business logic while improving execution speed. By updating the underlying code structure rather than discarding the functionality, companies retain their intellectual property while satisfying the technical requirements of the S/4HANA platform.
When comparing clean-core-remediation-benchmarks, the delta between a standard
Practical Strategies for S/4HANA Stability
Stability in S/4HANA depends on the reliability of your custom ABAP code during SAP upgrade cycles. Instead of attempting to strip out every customization to meet a theoretical “clean” standard, focus on refactoring legacy code into modern ABAP syntax. This approach preserves your business logic while ensuring the code remains compatible with the latest SAP NetWeaver and HANA database requirements.
Conduct a thorough impact analysis of your existing Z-programs and modifications before moving to S/4HANA. Identify specific areas where custom logic interacts with standard SAP tables, such as those in the MM or SD modules. By modernizing these specific components using ABAP for SAP HANA, you maintain the functional integrity of your business processes while making the system easier to maintain during periodic updates.
Managed services provide a practical way to maintain this stability. Instead of your internal team spending time on manual regression testing or bug fixing after every SAP patch, a managed service model handles the ongoing application and platform management. This allows your team to focus on core business goals while ETZ ensures the underlying S/4HANA environment remains stable and performant.
Reliable stability is measurable. In practical terms, a well-managed environment reduces the time required for quarterly-release validation. By maintaining a stable codebase that doesn’t require constant firefighting, organizations can move from weeks of testing to a simplified validation process, ensuring that system updates do not disrupt daily operations.
How ETZ Global helps
ETZ Global manages the technical debt and complex ABAP code that powers your core business processes. We provide managed services to maintain your custom infrastructure, allowing your internal teams to focus on growth instead of routine system maintenance.
Contact ETZ Global to discuss your S/4HANA roadmap.
Related reading: SAP S/4HANA migration strategy, ABAP modernization.