Migrating Classic ABAP to Modern Extensions

I’m thrilled to share a hobby project I've been working on - a generative AI prototype designed to analyze custom ABAP code from ECC or S/4HANA systems and propose clean core compliant ways to transition the code to a future state. 🌟 🔍 What It Does: Analyzes the program’s business purpose and flow. Works with complex ABAP developments (most complex I tried consisted out of over 400 objects), considering all objects like Data Dictionary, Function Modules, Classes, SmartForms, etc. Conducts research on APIs, Events, CDS Views, BTP Services, and standard S/4HANA features. Provides detailed implementation approaches and suitable APIs, CDS Views, Events, and more. Advises on whether to retire, refactor, or rebuild the code, offering a comprehensive report for each analyzed program. 💡 Why It’s Useful: Supports the transition of legacy ABAP code to “clean core”-style extensions. Helps in planning both green field and brown field transitions. Issues reports in any language, making it versatile for global teams. I’d love to hear your thoughts and suggestions! Would you use such a tool?Let me know in the comments! 👇 #ABAP #S4HANA #CleanCore #GenerativeAI #SAP #TechInnovation #CodeAnalysis

I recently implemented SAP's Clean Core strategy for a major FMCG client. SAP Clean Core strategy includes a method to enhance SAP S/4HANA Cloud systems in a way that is safe to upgrade. The SAP Clean Core concept advocates for a strategy that maintains the core system as standard and uncluttered as possible. This approach prioritizes minimal customization to ensure the core remains streamlined and efficient. Here are some key takeaways from my assignment to achieve a Clean Core: 1.Identify custom developments (Z-objects, User Exits, BAdIs, Enhancements, etc.) -decommissioning unused custom objects. 2. Run SAP Readiness Check for SAP S/4HANA to analyze custom code impact -modernizing to ABAP cloud syntax. 3. Identify unused or obsolete customizations that can be retired. 4.Use SAP Standard Best Practices instead of custom transactions - moving to standard SAP delivered functionality. 5.Replace custom Z-tables with SAP CDS Views & Embedded Analytics. 6.In-App Extensibility (Embedded ABAP, Key User Tools) -migrating to key user extensions. 7.Build Custom Applications on SAP BTP instead of modifying SAP S/4HANA -SAP RAP /CAPM development. 8.Use API-first approach → Leverage SAP API Business Hub - maximizing use of released APIs and CDS views. 9.Replace SAP GUI-based transactions with SAP Fiori apps. 10.Use SAP Build Apps for business-user-driven custom UI development. 11.Implement Business Process Automation with SAP Workflow Management.  #Clean #Core #CloudPlatform #INDIA #TechnologySolutions #BTPInnovations #SAPLearning #ABAP #AI #Developers #SAPBTP #BusinessTechnologyPlatform #Innovation #RAP #CDS #SAPTechnology #SAPCloud #Innovation #EY #EYINDIA #SAP #SAPBuild #EYGCC #DigitalTransformation #EnterpriseTechnology #RisewithSAP #Transformation #SAPGROW #SAPbusinessSuite  #SAPHANA #CloudPlatform #TechnologySolutions #BTPInnovations #SAPLearning #LinkedInTechPost #S4PublicCloud #S4PrivateCloud SAP Wouter van Heddeghem #SAPBTP #EYGCC #S4PublicCloud #S4PrivateCloud #RISE #GROW #Business #SAPCleancore #SAPCloud #SAPIntegration #DigitalTransformation #CloudComputing #EnterpriseTechnology #SAPHANA #SAPDevelopment

I’ve heard that many custom programs written in ECC6 might not work as-is in S/4HANA. Does that mean our legacy ABAP code needs to be rewritten or restructured for S/4? And when developers say they’ve ‘upgraded their S/4 ABAP skills,’ what exactly does that mean. Is ABAP itself different in S/4HANA, or is it more about how the code interacts with the new system architecture? ECC6-era custom code often needs refactoring or retirement in S/4HANA. Not always, but often. "Custom code" in ECC6 context means: Decades-old mods done with the finesse of a chainsaw: Z-tcodes, enhancements in core includes, wild table updates. Riddled with direct SELECTs from internal tables (goodbye CDS!), hard-coded logic, and assumptions about screen flows that no longer exist. Why those ECC6-era custom codes are trouble in S/4HANA: Data model changed. Think of material master split into multiple views (MATDOC replacing MKPF/MSEG for example). T-codes vanished or refactored. Frameworks evolved. No more classic Dynpros for some flows; it's CDS Views, Fiori, OData, and embedded analytics now. Tech stack shifted. You're expected to play with: - ABAP RESTful Application Programming Model (RAP) - Core Data Services (CDS) - Fiori/UI5 integration - Event-driven architecture (with BTP or even inside S/4) So when an ABAPer says: “I upgraded my S/4HANA ABAP skills.” They mean: “I stopped SELECTing from tables like it’s 2004.” “I know what a CDS View is and how annotations work.” “I can build APIs and wrap logic in the modern extension model.” “I stopped stuffing logic into user-exits like a turkey on Thanksgiving.” #S4HANA #SAPCloudERPPrivatepackage #SAPCustomeCode ECC6 Custom Code in Trouble in S/4HANA