SAP Community - ABAP Testing and Analysis

Include released successor objects from "cloudification repo" in your ABAP custom code migration

2025-07-17T15:35:03.728000+02:00

Many SAP customers are currently in the phase of migrating their SAP ERP systems to S/4HANA. For those who choose a brownfield or bluefield approach the old ERP system is converted and the customers extensions and own applications (Z* objects) become part of the new system.

Then, the process of Custom Code Adaptation kicks in where the ERP functionality is analyzed and corrected in a way that the objects run again in S/4HANA. See https://community.sap.com/t5/technology-blog-posts-by-sap/get-started-with-the-abap-custom-code-migration-process/bc-p/14049622 or https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/sap-s-4hana-system-conversion-custom-code-adaptation-process/ba-p/13337309 for more details.

The custom code correction process can be time consuming and challenging depending on the size and complexity of the original ERP system. A big part of the custom code objects will be touched. The basis for the checks and corrections is the ABAP Test Cockpit (ATC) with the check variant for S/4HANA (e.g. S4HANA_READINESS_2023).

In case the customer wants to move functionality to SAP BTP ABAP or the S/4HANA (public) Cloud versions it is not sufficient to make the old ERP code just S/4HANA ready. The cloud versions have a heavily restricted set of the ABAP language (so called language version 5 ) and furthermore access to SAP standard objects is allowed to (relatively few) released objects only. For instance, you must not use the MARA table to read materials but the I_PRODUCT CDS. This information is stored in the so called cloudification repository (https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/how-to-check-your-custom-code-for-abap-cloud/ba-p/13567124 ) which is regularly updated. (See https://github.com/SAP/abap-atc-cr-cv-s4hc for the Raw data).

It contains as well successor information for some of the old ERP objects in particular for the data base tables which makes it particularly interesting for the custom code migration process. See note https://launchpad.support.sap.com/#/notes/3284711 for installation of the according ATC check / check "Usage of Released APIs (Cloudification Repository)" in releases before 2023 FP 3.

The idea is now to use the officially released successors for the objects which need to be corrected anyway during the migration ERP -> S/4HANA.

A (simple) example: When accessing table SKA1 corrections could be necessary because of the new account type attributes e.g. GLACCOUNT_TYPE in S/4; secondary cost elements are saved now as well. This is found by the S4HANA_READINESS_2023. The same access is found by the "Usage of Released APIs (Cloudification Repository)" check as well:

The solution to solve both issues is to check if secondary cost elements are concerned and to follow the recommendation in the finding. In the correction the successor object (DDLS I_GLACCOUNTINCHARTOFACCOUNTS) should be used directly:

This combination approach makes a part of the own developments "cloud ready" and "S/4HANA ready" at the same time without a big additional effort. And anyway, it is better for upgrade stability to use officially released objects!

Here are 3 possible approaches to achieve this:

Approach 1: Out of the box: Combined Check

Create a Z ATC Check variant and select the checks from S4HANA_READINESS* and the check "Usage of Released APIs (Cloudification Repository)" . The easiest would be to copy S4HANA_READINESS* and then to select in the maintenance of the check variants (via transaction /nSCI):

Once you run the check you will see the result as in this example:

The findings from the combined check contain already all needed information but there are two shortcomings: the list contains many irrelevant entries; not all check categories (only when the successor is defined) nor all findings are relevant in the context of S/4HANA custom code adoption (e.g. Successor I_COUNTRY for T005 table doesn’t solve a Custom Code Migration issue).

Approach 2: Add information from Cloudification Repo manually

Instead of a combined check variant the successor information could be added via Excel / VLOOKUP (SVERWEIS in German) as well using these steps:

Run the standard ATC check for Custom Code Analysis (e.g. S4HANA_READINESS_2023)
Download the detailed list from ATC to Excel (include in any case the field reference object / Referenzobjekt)
Download the cloudification repo from here https://github.com/SAP/abap-atc-cr-cv-s4hc/blob/main/src/objectReleaseInfoLatest.csv
Open the data in Excel and copy the sheet to your original excel in a new tab
Add a new column to the first tab from ATC data and combine the data via VLOOKUP: find a possible successor objects in the released objects for the reference objects

A possible result could look like this:

I added an example excel for convenience reasons to Github here: https://github.com/Lutzi3/cloud_mig_atc/blob/main/ATC_S4HANA_CLOUDIF_REPO_EXAMPLE.xlsx

Then, when processing the ATC findings, the successor objects from Excel can be used directly in the corrections.

Approach 3: Using a custom enhancement to the SAP ATC S/4HANA: Released objects as additional information

In order to avoid the manual Excel steps and to have a lean combined list of the relevant findings only there is also the possibility to enhance the "additional information" section via an implicit enhancement or via another copy of the standard check classes in the S/4HANA Custom Code area. If you decide for the enhancement you can use the methode GET_DETAIL_FROM_DATA_BUFFER from the central utility class CL_CI_S4H_COMMON and add the successor object information there.

The result is that if there is the successor object available it will be put to the Additional Information Section of the findings as shows the following example:

There is an example version on Github for this as well: https://github.com/Lutzi3/cloud_mig_atc

Now the existing ATC S4HANA readiness check is enhanced by the new released object information such as that you can directly correct the old ERP object reference and replace it by the latest officially released SAP cloud ready object!

ABAP Cloud Sessions at SAP TechEd in 2025

2025-08-22T17:20:44.662000+02:00

🔥 Check out the🟢ABAP Cloud sessions at the SAP's Devtoberfest 2025! ‌‌🔥

Hey Everyone!

SAP TechEd in 2025 kicks off on the 4th of November 2025, and preparations are now in full swing at SAP!

SAP TechEd is the leading tech conference for all developers, IT professionals, business experts, tech visionaries, innovators, and leaders eager to gain in-depth knowledge of SAP’s solutions, platforms, and technologies, along with insights into their future direction. It also offer an opportunity to network and connect with peers and SAP experts.

In 2025, SAP TechEd goes hybrid, kicking off with parallel events in Berlin, Louisville, and online – followed by SAP TechEd on Tour stops in Australia, India, UK, and Germany for a unique opportunity for an in-depth, in-person learning experience. Except for the Berlin and Bangalore stops, the on-site events are organized in partnership with, and hosted by, SAP User Groups and SAPinsider.

The choice is yours: join us on-site in Berlin or Louisville (at ASUG Tech Connect), or online for the first events in the series!

Save the date and register now!
📅November 4 - 6, 2025
Berlin | Virtual (free of charge) | Louisville

ABAP Cloud at SAP TechEd in 2025

🔧 What to Expect

ABAP continues to evolve, and SAP TechEd events in 2025 are the best place to see what’s next. Beyond the integration of ABAP Cloud into SAP Build announced last year, and the integration of SAP Joule for Developers into the ABAP development tools along with the ABAP AI SK to infuse AI into your business processes earlier this year, you’ll have the opportunity to explore the latest innovations and updates in ABAP Cloud, AI-based custom code transformation, clean core practices, and the new clean core levels approach for SAP S/4HANA extensibility in both the private cloud and on-premise.

💡 Why Attending ABAP Sessions Matters

Get a clear direction for your ABAP strategy, whether you're on ECC, S/4HANA, or SAP BTP
Learn how to modernize custom development without touching the core
See how SAP Joule for Developers, ABAP AI capabilities can support faster, cleaner development
Take home practical skills for RAP, testing, ABAP Test Cockpit, governance, and more

Access the SAP TechEd 2025 session catalogs: SAP TechEd Berlin | SAP TechEd Virtual | ASUG Tech Connect. | SAP TechEd Bangalore 2025.

ABAP Cloud Sessions at SAP TechEd Berlin 2025

📅 Event Info:

Dates: November 4–6, 2025
Location: Messe Berlin (Berlin, Germany)
Session formats: Strategy talks, roadmap updates, deep dives, community talks, and hands-on workshops
9 Content tracks: ABAP sessions primarily in the tracks "Application Development & Automation (AD)" and "Digital Transformation with Cloud ERP (DT)"

🎤Keynote

KEY102v | Welcome to SAP TechEd 2025
AI, clean core, data, and agents are changing enterprise tech, but it all comes down to developers. See how SAP is equipping you with the tools, platforms, and learning to turn bold ideas into reality. Experience big announcements, live demos, and a clear view of what’s next.
Schedule: Tuesday, 4 November 2025 | 8:30 AM - 9:00 AM CET
Speakers:

Muhammad Alam, Executive Board, SAP Product & Engineering, SAP
Josh Bentley, Head of SAP Community, SAP
Anne Katherine Petteroe, Community Advocate, SAP
Nora Von Thenen, Developer Advocate, SAP

KEY100 | Beyond the hype: How SAP is supercharging developers for what's next
Some experts argue there’s a developer shortage. Others will say developers are no longer needed due to AI. Let’s get real: developers, architects, and technologists are here to stay, and their roles are more important than ever. Explore how the latest technology, tools, AI, agents, and learning from SAP can help you adapt these changing roles.
Schedule: Tuesday, 4 November 2025 | 4:00 PM – 5:30 PM CET
Speakers:

Muhammad Alam, Executive Board, SAP Product & Engineering, SAP
Philipp Herzig, Chief Technology Officer, SAP
Michael Ameling, President SAP BTP, SAP

KEY101v | Draft day for developers: Turning new technology into real-world wins
The picks are in, and developers, their tools, and frameworks are first-round talent. Get a front-row seat to SAP’s latest innovations built to accelerate how you code, automate, and scale. Explore how you can use SAP’s newest AI capabilities, generative agents, and enhanced tooling to build faster and smarter with less friction and more impact.
Speakers: Developer Advocates, SAP
Schedule: Wednesday, 5 November 2025 | 9:00 AM - 9:45 AM CET

KEY103v | SAP TechEd closing
Wrap up SAP TechEd with highlights, key takeaways, and a look at what’s ahead. From breakthrough demos to developer wins, celebrate what you’ve learned, where you’ve connected, and how you can keep the momentum going long after SAP TechEd is over.
Speakers: Josh Bentley (SAP), Shilpa Shankar (SAP), Laura Schmitz (SAP)
Schedule: Thursday, 6 November 2025 | 2:00 PM - 2:30 PM CET

🚉Demo Station

AD900 | SAP Build: AI-based development with ABAP Cloud, CAP, SAPUI5
Explore AI-driven application development with SAP Build solutions using ABAP Cloud, SAP Cloud Application Programming Model (CAP), and SAPUI5. Learn how to extend SAP solutions like SAP S/4HANA Cloud, integrate with the SAP Business Data Cloud solution, and boost productivity with the SAP Joule for Developers add-on and generative AI.
ABAP Cloud: Burcu Karlidag & On-Site Speakers
Schedule: Throughout the event

DT916 | Discover extensibility options for cloud ERP
Explore on-stack and side-by-side extensibility with the SAP Build solution to innovate while keeping a clean core. Learn about the clean core levels concept, innovations in ABAP Cloud, and how AI boosts developer productivity and custom code transformation. Partners can explore options for delivering extensions in a scalable model.
ABAP Cloud: Karl Kessler & On-Site Speakers
Schedule: Throughout the event

🎯Strategy Talks (25 minutes)

ST109 – SAP Build: ABAP Cloud Strategy | Livestreamed as ST109v at SAP TechEd Virtual 2025
The ABAP Cloud strategy as part of SAP Build and the SAP strategy go hand-in-hand. Explore in this session what this means for our major topics ABAP AI and Custom Code Transformation and how we integrate Business Data Cloud. Furthermore, learn about the ABAP IDE strategy and how we support the sovereign cloud.
Speakers: Sonja Liénard (SAP), Boris Gebhardt (SAP)
Schedule: Tuesday, 4 November 2025 | 12:30 PM – 12:55 PM CET

ST113 – Journey to unified extensibility in SAP Business Suite and cloud ERP | Livestreamed as ST113v at SAP TechEd Virtual 2025
Explore the strategy for extensibility across SAP Business Suite and cloud ERP. Learn why AI-driven development with the SAP Build solution including ABAP Cloud is key, and how the planned harmonization will make it easier to build extensions and support the clean core. Furthermore, learn about opportunities for partners to extend SAP solutions.
Speakers: Boris Gebhardt (SAP), Khaled Musilhy (SAP), Lilissa Chao (Exxon Mobil Global Services Co.)
Schedule: Thursday, 6 November 2025 | 9:00 AM - 9:25 AM CET

🗺️ Roadmap Sessions (25 minutes)

AD808 – SAP Build: ABAP Cloud road map
See our upcoming innovations for the ABAP Cloud development model including Joule and the Business Data Cloud integration in context and get updates on the roadmap ahead.
Speakers: Boris Gebhardt (SAP)
Schedule: Tuesday, 4 November 2025 | 2:45 PM - 3:10 PM CET

DT814 – Extensibility innovations road map for SAP Business Suite and cloud ERP
Explore upcoming extensibility innovations for SAP Business Suite and cloud ERP. Discover road maps for suite extensibility, harmonization, and partner enablement for commercial use cases. Learn more about upcoming innovations for AI-driven extensibility with the SAP Build solution including ABAP Cloud to support your clean core strategy.
Speakers: Oren Shatil (SAP), Boris Gebhardt (SAP)
Schedule: Wednesday, 5 November 2025 | 4:30 PM - 4:55 PM CET

🔍Deep Dives (45 minutes)

AD104 – Boost your ABAP development with Joule for developers | Livestreamed as AD104v at SAP TechEd Virtual 2025
In this deep dive session you will learn all aspects of the ABAP AI strategy, from accelerating your ABAP development, over developing custom AI scenarios, up to using Joule to transform your ABAP code.
Speakers: Simona Marincei (SAP), Olga Dolinskaja (SAP)
Schedule: Tuesday, 4 November 2025 | 2:30 PM - 3:15 PM CET

AD105 – Introduction to ABAP Cloud and how to get started
ABAP Cloud is the new way of developing ABAP—fully cloud-enabled and driven by AI. It combines cloud technologies with a clear separation of SAP and custom code, and in this way revolutionizes ABAP development. Grasp the major concepts of ABAP Cloud and learn how you can upskill. Also learn about Bosch Digital’s journey to ABAP Cloud and clean core.
Speakers: Carine Tchoutouo Djomo (SAP), Ajay Kulkarni (Robert Bosch GmbH)
Schedule: Wednesday, 5 November 2025 | 1:15 PM - 2:00 PM CET

AD201 – Explore ABAP Cloud in SAP Build - what's in for ABAP developers?
In this deep dive we will highlight the importance of our strategic approach of integrating ABAP Cloud in SAP Build. Learn how you can benefit from this for Fiori App development and how the graphical modeler helps you to create ABAP CDS models conveniently. Finally, get insights into the future direction.
Speakers: Dr. Anne Keller (SAP), Katja Zoch (SAP)
Schedule: Wednesday, 5 November 2025 | 5:15 PM - 6:00 PM CET

DT200 – Unravel the mysteries of Clean Core extensions in Cloud ERP Private
Learn about the new, enhanced clean core extensibility concept in SAP S/4HANA Cloud Private Edition. Learn about tools like ABAP Test Cockpit and RISE Dashboard, as well as guidance and best practices that help you to measure, govern, re-factor and develop your custom extensions in a clean core compliant, upgrade stable and cloud-ready way.
Speakers: Olga Dolinskaja (SAP), Markus Goebel (SAP)
Schedule: Wednesday, 5 November 2025 | 2:15 PM - 3:00 PM CET

DT201 – Extensibility with ABAP Cloud and AI in SAP Cloud ERP
Learn about the on-stack key user and developer tools in the ABAP Cloud development model, now enhanced with generative AI. See how you can extend standard SAP applications and manage your custom apps directly in SAP S/4HANA Cloud Public Edition. Get insights into latest innovations for transactional, analytical, and integration use cases, such as the extensibility AI Assistant, editable tree-views, custom queries for analytical SAP Fiori apps, ABAP SQL services and more.
Speakers: Carine Tchoutouo Djomo (SAP), Oren Shatil (SAP), Thomas Neuhaus (AGILITA Deutschland GmbH)
Schedule: Tuesday, 4 November 2025 | 2:30 PM - 3:15 PM CET

🛠️ Hands-On Workshops (2 hours)

AD162 – Explore Joule for developers, ABAP AI capabilities
Learn how to develop a RAP business object while exploring Joule's ABAP AI capabilities
Speakers: Sebastian Baskovich (SAP), Thomas Alexander Ritter (SAP), Dr. Anne Keller (SAP), Simona Marincei (SAP)
Schedule: Tuesday, 4 November 2025 | 10:00 AM - 12:00 PM CET

AD163 – Fusion Development with ABAP Cloud in SAP Build
In this session we will practice fusion development of ABAP Cloud in SAP Build by creating an ABAP Cloud project from the SAP Build lobby to develop a RAP BO including a Fiori application on top.
Speakers: Ingo Bräuninger (SAP), Sebastian Baskovich (SAP), Anne Keller (SAP), Katja Zoch (SAP)
Schedule: Thursday, 6 November 2025 | 11:30 AM - 1:30 PM CET

AD164 – Get started with ABAP Cloud for classic ABAP developers
Familiar with classic ABAP development? Join us to learn how similar development works with ABAP Cloud development model using the ABAP RESTful application programming model (RAP). ABAP Cloud is the comprehensive model for building cloud-ready business apps, services, and extensions that follow clean core principles by default – on SAP BTP and SAP S/4HANA, both in the cloud and on-premise.
Speakers: Volker Drees (SAP), Carine Tchoutouo Djomo (SAP), Boris Gebhardt (SAP), Jürgen Reidl (SAP)
Schedule: Thursday, 6 November 2025 | 11:30 AM - 1:30 PM CET

DT260 – Modernize classic extensions to clean core in Cloud ERP Private
In this session you will practice a clean core extensibility in SAP S/4HANA Cloud Private Edition. You will learn how to govern clean core development using the ABAP Test Cockpit, and how to use ABAP Cloud and clean core extensibility principles to modernize your custom on-stack extensions.
Speakers: Ingo Bräuninger (SAP), Olga Dolinskaja (SAP), Thomas Fiedler (SAP), Markus Goebel (SAP)
Schedule: Thursday, 6 November 2025 | 9:00 AM - 11:00 AM CET

DT261 – Build on-stack extensions with ABAP Cloud in Cloud ERP Public
Join us to discover how to build extensions, applications, and services with the ABAP Cloud development model, using the ABAP RESTful application programming model and generative AI. You will learn how to extend standard SAP applications, consume public SAP APIs, and build new apps and services from scratch. Get practical insights through exercises and take the opportunity to ask your questions.
Speakers: Ingo Bräuninger (SAP), Volker Drees (SAP), Steffen Mattes (SAP), Rushikesh Nagle (SAP)
Schedule: Wednesday, 5 November 2025 | 10:30 AM - 12:30 PM CET

DT266 – Troubleshoot and Optimize ABAP Cloud Extensions in Cloud ERP
Ensuring optimal performance and stability of your ABAP Cloud-based extensions is crucial to long-term success. Learn advanced techniques and best practices for troubleshooting and optimizing custom code in the Cloud ERP. Use powerful tools like ABAP Cross Trace to get deep insights into execution flows and resource consumption.
Speakers: Steffen Mattes (SAP), Juergen Reidl (SAP), Thomas Alexander Ritter (SAP), Thomas Fiedler (SAP)
Schedule: Wednesday, 5 November 2025 | 3:30 PM - 5:30 PM CET

👋Join Us

I hope this overview gives you even more reasons to join us at one of the SAP TechEd 2025 tour stops in Berlin (DE), Louisville (US), Sydney (AU), Bangalore (IN), Birmingham (UK), or Hamburg (DE) – or attend online, free of charge!

We look forward to meeting and interacting with you! 🤝 In the meantime, you can watch the replays of last year's events: ABAP Cloud at SAP TechEd Virtual 2024 and ABAP Cloud at SAP's Devtoberfest in 2024. You can also have a look at the 🔥ABAP Cloud sessions at the upcoming Devtoberfest 2025, running online and free of charge from September 29 to October 24, 2025! 🤝

Stay tuned – and see you there!

ABAP Cloud Sessions at SAP TechEd in 2025

2025-08-22T20:27:47.137000+02:00

Hey Everyone!

SAP TechEd in 2025 kicks off on the 4th of November 2025, and preparations are now in full swing at SAP!

The choice is yours: join us on-site in Berlin or Louisville (at ASUG Tech Connect), or online for the first events in the series!

Save the date and register now!
📅November 4 - 6, 2025
Berlin | Online (free) | Louisville

ABAP Cloud at SAP TechEd in 2025

🔧 What to Expect

💡 Why Attending ABAP Sessions Matters

Get a clear direction for your ABAP strategy, whether you're on ECC, S/4HANA, or SAP BTP
Learn how to modernize custom development without touching the core
See how SAP Joule for Developers, ABAP AI capabilities can support faster, cleaner development
Take home practical skills for RAP, testing, ABAP Test Cockpit, governance, and more

Access the SAP TechEd 2025 session catalogs: SAP TechEd Berlin | SAP TechEd Virtual | ASUG Tech Connect.

📌ABAP Cloud Sessions at SAP TechEd Berlin 2025

📅 Event Info:

Dates: November 4–6, 2025
Location: Messe Berlin (Berlin, Germany)
Session formats: Strategy talks, roadmap updates, deep dives, community talks, and hands-on workshops
9 Content tracks: ABAP sessions primarily in the tracks "Application Development & Automation (AD)" and "Digital Transformation with Cloud ERP (DT)"

🎤Keynote

🎯Strategy Talks (25 minutes)

ST109 – SAP Build: ABAP Cloud Strategy | also available virtually as ST119v
The ABAP Cloud strategy as part of SAP Build and the SAP strategy go hand-in-hand. Explore in this session what this means for our major topics ABAP AI and Custom Code Transformation and how we integrate Business Data Cloud. Furthermore, learn about the ABAP IDE strategy and how we support the sovereign cloud.
Speakers: Sonja Lienard (SAP), Boris Gebhardt (SAP)

ST113 – Journey to unified extensibility in SAP Business Suite and cloud ERP
Explore the strategy for extensibility across SAP Business Suite and cloud ERP. Learn why AI-driven development with the SAP Build solution including ABAP Cloud is key, and how the planned harmonization will make it easier to build extensions and support the clean core. Furthermore, learn about opportunities for partners to extend SAP solutions.
Speakers: Boris Gebhardt (SAP), Khaled Musilhy (SAP), tbd

🗺️ Roadmap Sessions (25 minutes)

🔍Deep Dives (45 minutes)

AD104 – Boost your ABAP development with Joule for developers | also available virtually as AD104v
In this deep dive session you will learn all aspects of the ABAP AI strategy, from accelerating your ABAP development, over developing custom AI scenarios, up to using Joule to transform your ABAP code.
Speakers: Simona Marincei (SAP), Olga Dolinskaja (SAP)

🛠️ Hands-On Workshops (2 hours)

AD163 – Fusion Development with ABAP Cloud in SAP Build
In this session we will practice fusion development of ABAP Cloud in SAP Build by creating an ABAP Cloud project from the SAP Build lobby to develop a RAP BO including a Fiori application on top.
Speakers: Ingo Braüninger (SAP), Sebastian Baskovich (SAP), Anne Keller (SAP), Katja Zoch (SAP)

DT261 – Build on-stack extensions with ABAP Cloud in Cloud ERP Public
Join us to discover how to build extensions, applications, and services with the ABAP Cloud development model, using the ABAP RESTful application programming model and generative AI. You will learn how to extend standard SAP applications, consume public SAP APIs, and build new apps and services from scratch. Get practical insights through exercises and take the opportunity to ask your questions.
Speakers: Ingo Bräuninger (SAP), Carine Tchoutouo Djomo (SAP), Volker Drees (SAP), Steffen Mattes (SAP)

👋Join Us

Stay tuned – and see you there!

ABAP Cloud Sessions at Devtoberfest 2025

2025-08-25T17:16:40.412000+02:00

Get ready – Devtoberfest 2025 from SAP is almost here! 🎉

The annual celebration of SAP technologies kicks off soon, bringing weeks of learning, community, and fun – all completely free and fully virtual. Following content tracks are available this year‌: 🟢 Monday – ABAP | 🟣 Tuesday – Tooling & Frontend | 🔴 Wednesday – Integration | 🔵 Thursday – Data & AI | 🟠 Friday – CAP | 🟡 All Week – Fun Activities.
Check out the blog post Devtoberfest 2025 Welcome! by Thomas Jung to learn more about the event.

Key event Info:
📅 Dates: September 29 – October 24, 2025
📺 Where: All sessions livestreamed or premiered on the SAP Developers YouTube channel
🔁 Tradition continues: Every Monday during Devtoberfest is ABAP Day 💚!
📚 Session Catalog: Explore the full session line-up in the SAP Community events area: Devtoberfest.

Check out the compact overview of ABAP Cloud sessions at Devtoberfest 2025 below. Session details are provided in the next section. Expect plenty demos and opportunities to interact with fellow developers and SAP experts!

📅[CW 40] WEEK 1 – 🟢 29th September 2025

Clean Core Extensibility Strategy powered by ABAP Cloud and Generative AI
Custom code development and transformation for Clean Core in SAP S/4HANA
Boost your developer satisfaction and productivity with SAP Joule for developers, ABAP AI capabilities

📅 [CW 41] WEEK 2 – 🟢 6th October 2025

News on SAP BTP ABAP environment
Explore the latest updates in ABAP CDS
Updates on Embedded Analytics in ABAP Cloud

📅[CW 42] WEEK 3 – 🟢 13th October 2025

What's new in the ABAP RESTful Application Programming Model (RAP)
Evolving data integration with SQL services and CDS external entities
Discover the latest innovations in the ABAP language
ABAP Development Tools for Eclipse - What's new

📅[CW 43] WEEK 4 – 🟢 20th October 2025

Exploring the path to SAP certification‌
Boost Your Developer Efficiency with IDE Actions

Session Details

Week 1

🟢 Clean Core Extensibility Strategy powered by ABAP Cloud and Generative AI
In this session we’ll explain how the new clean core approach makes systems ready for the future, how AI-powered capabilities can enhance development and transformation processes, and give an update on the latest ABAP Cloud innovations.
Speakers: Fabian Fellhauer (SAP)
Schedule: 29th September 2025, 9:30 am - 10:30 am CEST

🟢 Custom code development and transformation for Clean Core in SAP S/4HANA
In this session you will learn the enhanced guidelines for ABAP custom code development and governance for clean core supported by the new ABAP Test Cockpit checks. In addition, we provide the overview about the new Gen AI assistance in custom code management tools.
Speakers: Olga Dolinskaja (SAP), Thomas Fiedler (SAP)
Schedule: 29th September 2025, 1:00 pm - 2:00 pm CEST

🟢 Boost your developer satisfaction and productivity with SAP Joule for developers, ABAP AI capabilities
In what ways can AI support ABAP developers in their day-to-day activities? Find out more on the supported use cases, the generative AI road map, and insights on SAP Joule for developers, ABAP AI capabilities.
Speakers: Sebastian Baskovich (SAP), Jasmin Gruschke (SAP)
Schedule: 29th September 2025, 4:00pm - 5:00pm CEST

Week 2

🟢 SAP BTP ABAP Environment – How to Monitor and Support Custom Cloud Apps
SAP BTP ABAP Environment is the platform as a service for ABAP developers. It’s a cloud-optimized ABAP platform based on SAP HANA Cloud that serves as a development and runtime environment for cloud apps. This session gives you an update about the latest product news and explains with live demos how to use the Technical Monitoring Cockpit, and how to use the different tools for supportability and performance measurement.
Speakers: Frank Jentsch (SAP), Richard Scholz (SAP)
Schedule: 6th October 2025, 9:30 am - 10:30 am CEST

🟢 Explore the latest updates in ABAP CDS
As one of the fundamental technologies of ABAP Cloud, ABAP CDS continues to advance. This session will present the latest developments in ABAP CDS including CDS table entities, CDS Explain functionality, analytical query modelling features and, CDS aspects.
Speakers: Santiago Zuniga Garcia (SAP), Boyan Boychev (SAP)
Schedule: 6th October 2025, 1:00 pm - 2:00 pm CEST

🟢 Updates on Embedded Analytics in ABAP Cloud
ABAP Core Data Services (CDS) based embedded analytics provides easy-to-use analytical tooling and allows you to drill down, aggregate, and display data from your core solution modeled with ABAP CDS. In this session, we present the latest additions to embedded analytics in ABAP Cloud. You will experience the new review booklet app generator for building native, SAP Fiori apps on top of an analytical service exposure and will get to know the analytical modeling examples on GitHub that act as showcases for the latest features of CDS-based analytical queries.
Speakers: Andreas Riehl (SAP)
Schedule: 6th October 2025, 4:00pm - 5:00pm CEST

Week 3

🟢 What's new in the ABAP RESTful Application Programming Model (RAP)
ABAP Cloud is the powerful development model for building cloud applications on SAP Business Technology Platform (SAP BTP) and SAP S/4HANA, in the cloud and on premise. Experience live demos of the major ABAP Cloud capabilities around the ABAP RESTful application programming model which can be used to build and extend transactional and analytical applications
Speakers: Andre Fischer (SAP)
Schedule: 13th October 2025, 9:30 am - 10:30 am CEST

🟢 ABAP Development Tools for Eclipse - What's new?
In this session, learn about the latest developments regarding ABAP Development Tools for Eclipse, ranging from the new end-to-end integration between ADT and SAP Build Code to the new design options and an outlook on what's next for the ABAP Development Tools.
Speakers: Sachin B (SAP), Mani P S (SAP)
Schedule: 13th October 2025, 11:00 am - 12:00 pm CEST

🟢 Evolving data integration with SQL services and CDS external entities
In this session, we’ll present the latest advancements in ABAP Cloud data integration. On the data exposure side, we’ll cover ABAP-managed database procedures for advanced read scenarios and extensions of SQL services to enable data loading scenarios for SQL clients, using CDS writable view entities. On the consumption side, we’ll explore write scenarios, and the use of static CDS external entities for seamless integration of external data into aCDS view stack.
Speakers: Leon Stern (SAP), Yannick Rath (SAP)
Schedule: 13th October 2025, 1:00 pm - 2:00 pm CEST

🟢 Discover the latest innovations in the ABAP language
In this session, we 'll provide an overview of the latest features introduced to the ABAP language. Highlights include support for spatial data in ABAP SQL, enhanced JSON and Geo-JSON processing capabilities, Buffer Delegation in ABAP SQL, and new functionalities for probability distributions and advanced random number generation. We'll also share insights into the ABAP language roadmap.
Speakers: Kilian Kilger (SAP), Stefan Bresch (SAP), Gerd Forstmann (SAP)
Schedule: 13th October 2025, 4:00pm - 5:00pm CEST

Week 4

🟢 Exploring the path to SAP certification
This session will offer developers insights around navigating SAP learning offerings and the certification programs based on my own ABAP journey. Attendees will learn the most important steps toward SAP certifications, understand the differences between certification types (associate, specialist, professional), and how to choose the ideal certification based on your role and skill-set. We’ll also review preparation strategies, tips, and tricks to help you along your way.
Speakers: Sandra Solis (SAP Champion, external)
Schedule: 20th October 2025, 1:00 pm - 2:00 pm CEST

🟢 Boost Your Developer Efficiency with IDE Actions
In this session, you'll gain insights into developing IDE Actions with ABAP and how they can improve your efficiency in daily development. We'll focus on various areas of the ABAP RESTful Application Programming Model and optimize our workflows there.
Speakers: Björn Schulz (SAP Mentor, external)
Schedule: 20th October 2025, 3:00 pm - 4:00 pm CEST

____________________________________________________________________________________________

Curious to learn more? Join the sessions to explore the latest ABAP innovations and best practices firsthand.

In the meantime, catch up on last year’s highlights with the replays from SAP's Devtoberfest 2024 and SAP TechEd Virtual 2024. You can also have a look at the ABAP Cloud sessions at the upcoming SAP TechEd in 2025, starting November 4–6, 2025 on-site in Berlin and Louisville (ASUG Tech Connect) – and online for free! 🎉

We can’t wait to connect with you – stay tuned! 🍻

Debugging in ABAP Development Tool (Part 1)

2025-09-02T07:51:29.772000+02:00

Introduction

The Blog provides step by step guide on how to debug the report programs, classes and Function modules using Eclipse ADT (ABAP Development Tool).

In this blog, we will be covering
1.How to set the Toggle Breakpoint and the Soft Toggle Breakpoint.
2.How to debug in multiple sessions
3.How to check call stack
4.How to debug update Function module
5.How to set Watchpoint
6.How to set Conditional breakpoint
7.How to set user specific breakpoint
8.How to Activate, Deactivate and Delete the Breakpoints
9.How to Add new variable to observe the values in variables tab

Toggle Breakpoint (Regular/Hard Breakpoint):

This is the standard breakpoint type, typically indicated by a blue icon in the editor margin.
It serves to launch a new debugging session when the program execution reaches the line where it is set.

If no debugger session is active, encountering a regular breakpoint will automatically trigger the debugger and stop execution at that point.
To set Toggle Breakpoint, we can right click on the left vertical bar as shown

Soft Toggle Breakpoint:

This is a specialized breakpoint type, typically indicated by a green icon in the editor margin.
Crucially, a soft breakpoint cannot launch a new debugging session on its own.

It becomes effective only when a debugging session is already active. If a debugger is already running (e.g., initiated by a regular breakpoint or external debugging), a soft breakpoint will then cause the execution to pause at its location.

Soft breakpoints are often used in scenarios where you want to selectively stop execution within an already active debugging session, especially in situations with high-frequency calls or when you only want to debug specific parts of a larger process without repeatedly launching new sessions.

To set the Soft Toggle Breakpoint, we can Right click on the left vertical bar as shown

Debugging in multiple sessions

By clicking on Application run (maximum 4 debugging sessions can be opened), we can debug the same program in multiple sessions

After 4 debugging session if we again click on Application run it gives us error message at right edge of exclipse

Debugging through Call Stack

We can observe the events and navigate to the events in call stack at left side in Debug tab

Debugging Update Function Module

Click on ABAP Debugger Action icon and then click on Update Debugging.

Click on Ok to continue with update debugging.

Setting the Watchpoint

Right click on the variable and then click on the Set Watchpoint

we can observe the watchpoint for changed values

Term	Description
Recent Value	The value of the variable before the change that triggered the watchpoint.
Current Value	The value of the variable after the change, at the moment the debugger stops.

For SY-INDEX = 12, the current value changed

We can check the information whether watchpoint is reached or no

Setting the Conditional Breakpoint

Right click on the toggle breakpoint and then click on Breakpoint properties

Set the condition and then click on Apply and close

Before pressing F7

After pressing F7

Setting the User specific Breakpoint

In debugging right click the toggle breakpoint and then click on Debugging Properties

Select the User radio button and provide the username and then click on Apply and close

We can observe the u symbol on toggle breakpoint

Activating, Disabling (Deactivating) and Removing (Deleting) the Breakpoints

To deactivate the breakpoint, uncheck the checkbox

To activate the breakpoint, check the unchecked checkbox

To remove the breakpoint, click on remove icon

Adding new variables such as SY-TABIX and SY-INDEX in Variables tab

To add new variable in variable tab, click on Enter variable

Enter the name of the variable (SY-INDEX) and press Enter

Conclusion
Debugging in ADT isn’t just a technical exercise—it’s a strategic advantage. It transforms reactive troubleshooting into proactive insight. With its modern interface, modular object navigation, and precision tools like watchpoints and expression evaluators, ADT empowers developers to dissect complex logic, trace runtime behavior, and optimize code with surgical clarity.

Experimenting with AI-Enhanced ABAP Development Setup

2025-09-02T07:56:22.693000+02:00

The Challenge: I Can't Achieve the Same AI-Assisted Flow in ABAP as in Other Languages

When I tested tools like SAP Joule, Amazon Q, Github CoPilot and others, I encountered what seemed to be two main limitations:

Easy access to the ABAP platform file system or IDE workspace – In my testing, most AI assistants couldn't easily connect to the ABAP platform file system to work with actual source code. At least not as effortlessly and comprehensively as if these tools work with the local file system.
Lack of understanding of SAP standards – I found that LLMs often struggled with ABAP-specific syntax and (internal) standard APIs.

The result in my case: broken code, unclear suggestions, wrong use of standard components leading to short dumps.

The Goal: Enable a Seamless, Productive AI Workflow for ABAP

Inspired by a full stack AWS CDK & React project I was recently working on, I tried transferring some of the workflows and framework conditions to my ABAP development practice. The result is an experimental set up that - so far - seems very promising to achieve a comparable development flow and seamless integration of AI coding assistants as I experienced in projects outside of the ABAP universe.

The set up utilizes existing open source and community based tools and combines them to help the AI coding assistant to work as intended.

My Setup for Agentic ABAP Development

1. abapGit in the SAP backend

Crucial to sync ABAP code between the SAP dev system and a remote Git repository. I use the background option the keep the SAP system in sync with my local changes. The background option can be activated in the repo settings. Once activated, you can schedule a batch job of abapGit, which will then run the configured actions on the repo(s). In my case I configured the background auto pull function the keep the developments objects in the SAP dev system in sync with the changes I make locally & push to the remote.
Like this, the SAP dev system becomes more of a stage in a pipeline than a development environment.

auto pull option in abapGit repo

2. A Remote Git Repository

It acts as the bridge between the SAP system and my local development environment. I only do changes in my local environment (see 3) and push them to the remote repo. The background configuration (see 1) ensures that the SAP system stays in sync with the remote. Currently there is nothing more happening here, but I'd like to enhance the set up with some actions once changes are pushed/ merged in the remote. Maybe only trigger the sync in (1) only when a pipeline successfully executes.

3. A Local Development Environment Powered by AI

On my local machine, I use Visual Studio Code enhanced by these key tools:

An AI coding assistant
abaplint – The static code analysis tool by Lars Hvam to validate syntax and ensure code quality. This acts as a filter between AI output and real-world SAP code. The coding assistant can respond to the hints, warnings, errors given by the linter and therefore gets feedback whether it produces valid ABAP code, without the need for an actual ABAP platform underneath.
ADT MCP Server – A MCP server by Mario Andreschak that runs locally on my machine. It exposes SAP standard components to the AI engine. With this in place, LLMs can understand ABAP interfaces, function modules, and class signatures, etc. - making their suggestions much more relevant. I advise the LLM to use the first two parts of the Workflow ('searchObject' and 'getObjectSource') mentioned in the MCP repository to understand how it can get information about SAP standard objects.

Set Up Overview

What I've observed so far

My experience with this set up so far is really great. I mainly used it in a OO greenfield development, helping me to focus on software architecture and object composition and avoiding to deal with boilerplate code. I try writing to the AI assistant as with a development colleague, questioning my ideas and current problem solving approach.
I also let the assistant implement complete parts of the solution after creating and evaluating a detailed development plan upfront. It works really well as long as the current 'feature scope' is not too large and the implementation plan is well described.

This approach has given me what feels like a more tailored and extensible development experience compared to exclusively using the assistants mentioned at the beginning of this article without changing the complete set up.

--------------------------
This post was written with the help of GenAI.
Want to share your experiences with AI assisted coding? Get in touch!

AUnits steps for RAP

2025-09-26T08:51:38.675000+02:00

Introduction:
AUnits are unit tests written by ABAP developers to test each functionality of their code. In RAP, AUnits are used to test functionalities such as validations, determinations, actions, and CRUD operations etc. Your AUnits should aim for maximum coverage of your code. It is recommended to follow TDD(Test Driven Development), where you write the test cases first and then implement the logic. This ensures that the test cases are based on the actual requirements and are not influenced by the implementation.

Reference link for TDD: https://help.sap.com/docs/abap-cloud/abap-development-tools-user-guide/test-driven-development-with-abap-unit

Basics of AUnits:
Test classes can be either local or global. Unit tests should typically be implemented as local classes within the program object that is being tested. However, you can use global test classes to host reusable logic for unit tests across different programs. In Eclipse ADT, there is a separate environment for managing local test classes.

Reference link: https://learning.sap.com/learning-journeys/acquire-core-abap-skills/implementing-code-tests-with-abap-unit_b23c7a00-c2e8-406d-8969-b00db3f1fd87

Structure of test class:

*"* use this source file for your ABAP unit test classes
class ltc_zi_lfa1_2 DEFINITION FINAL for
  TESTING RISK LEVEL HARMLESS DURATION SHORT.
  PRIVATE SECTION.
  CLASS-DATA environment TYPE REF TO if_cds_test_environment.
  DATA td_zlfa TYPE STANDARD TABLE OF zlfa1 with empty key.
  DATA  act_results type STANDARD TABLE OF zi_lfa1_2 WITH EMPTY KEY.
  CLASS-METHODS class_setup RAISING cx_static_check.
  CLASS-METHODS class_teardown.
  METHODS setup RAISING cx_static_check.
  METHODS prepare_testdata.
  METHODS aunit_for_cds_method FOR TESTING RAISING cx_static_check.
  ENDCLASS.

For Testing: The addition FOR TESTING is used to identify a test class. These are the classes that will be executed when you run ABAPUnit tests. I will explain further how AUnits are triggered and how to execute them.

Risk Level:

CRITICAL: The test changes system settings or customizing data.
DANGEROUS: The test changes persistent data.
HARMLESS: The test does not change system settings or persistent data.

Duration:

SHORT: Execution time is imperceptible, expected to take only a few seconds.
MEDIUM: Execution time is noticeable, around a minute.
LONG: Execution time is very noticeable, taking more than a minute.

Methods in Test Classes:

Helper Methods: Helper methods are ordinary methods of the test class. They are not called by the ABAP Unit framework. You can use helper methods to structure the code of your test methods. For example, prepare_testdata is a helper method.
Test Methods: Test methods are defined with the addition FORTESTING after the method name. Each test method represents one test. The ABAP Unit framework performs this test by calling the corresponding test method. Test methods must not have any parameters. In the above example, aunit_for_cds_method is your test method.

Good Practices:

It’s a good practice to have a separate method for each functionality, with no dependencies inside the method. Each method should be treated as a single test case.
Always include both positive and negative test cases.

Flow of test case:

CLASS_SETUP
This static method is executed once before the first test of the test class. Use this method for fixtures that are time-consuming to create and for which you are sure the settings will not be changed by any of the test methods. Example: Setting up a test double in the test environment.

SETUP
This instance method is called before each test of the test class. Use this method for fixtures that you want to create fresh for every test case. Example: Creating an instance of the CUT (Class Under Test).

TEARDOWN
This instance method is called after each test of the test class. Use it to undo changes made in the SETUP method. It is especially important if SETUP modifies persistent data (such as system configuration, customizing, or master data). Example: Clearing test doubles so that each test starts with fresh data.

CLASS_TEARDOWN
This static method is executed once after the last test of the test class. Use it to clean up or destroy the test environment set up in CLASS_SETUP, once all tests are completed. Example: Tearing down the overall test environment.

To run ABAP units execute ABAP Unit Test. This will trigger the test class. If you run ABAP application it will not trigger test class.

Test double framework:
As I mentioned earlier, your unit tests should check only the functionality(CUT – Code Under Test) that you have written the test case for. However, in real-world scenarios, each component is usually interlinked and not standalone.

What is the issue?
To explain this, let’s take an example. Suppose you are testing an instance authorization method. This method is dependent on an authorization object. If the AUTH-CHECK of the authorization object fails, the instance authorization method will also fail. This means that even if your instance authorization method is working correctly, the test could still fail due to its dependency. Ideally, the failure of a dependency should not cause your unit test to fail when you are testing the functionality of the CUT itself.

Examples of dependencies in RAP

Instance and global authorizations: Dependency on authorization checks.
SAVE / SAVE_MODIFIED methods: Dependency on function modules or BAPIs.
Determinations: You might use EML of another BO, making your BO dependent.
Validations: Your CDS view could be a dependency; if the required record is not present in the CDS view, the validation might fail. And there are many more such cases.

Solution — Test Double Framework
So, how do we overcome this? Instead of relying on dependencies that are beyond our control, we mock or stub these dependencies. This allows us to influence how they behave and interact during testing, thereby avoiding test case failures due to external dependencies. This approach is implemented using the Test Double Framework.

The main purpose of both mock and stub is to not to test from actual data but rather a fake data that we can configure. Because our test class will fail if its dependent on real time data as it will be different in different
environment.

STUB: Stubs just provide predefined response.
MOCK: You design how the interaction should be. Like if you provide this value this is how the output would be and also verify it.

I will now discuss in detail how we write ABAP Unit tests with a simple example.

Requirement:
Write a positive test case to check the validation check_country, which should throw an exception if we pass a country code with more than2characters. Also, remove the dependency on the CDS view.

Steps:
Identify CUT and dependencies
Here, I have taken a validation method as an example for testing. The CUT(Code Under Test) is the validation method, and the dependency is the CDS view. So, I will use the STUB methodology to configure the response of the CDS view.

Creation of test class
Once you create the test class, you need to add it as a friend in the local handler class (since we are testing a validation). This is necessary because all the methods of the local handler class are inside the private section and cannot be accessed directly.

Inside the test class
I have already explained the use of SETUP, CLASS_SETUP, TEARDOWN, andCLASS_TEARDOWN earlier, so I will not repeat that here.
In this example, validate_check_country is our test method. I have added a test double for the CDS view, because the validation should be tested using the mock data we provide, not the actual data.
I create the mock data and insert it, so that the CDS view returns this data. Now, when we pass parameters to the validation, we can check if we get a value in reported, since we have provided a country code with 3 characters.

Note: This is just an example program. Typically, mocking, adding mock data, and different functionalities would be implemented in separate methods. It is not a good practice to combine everything into a single method. Each method should have only one responsibility. Here, I have combined them solely to showcase the concept.

class ltc_lfa1_validation IMPLEMENTATION.
    METHOD class_setup.
      cds_environment = cl_cds_test_environment=>create( i_for_entity = 'zi_lfa1_2' ).
     ENDMETHOD.
     METHOD setup.
       CREATE object cut for testing.
       cds_encironment->clear_doubles( ).
       ENDMETHOD.
     method validate_check_country.
       data: lfa1_mock_data type STANDARD TABLE OF zlfa1.
       data(system_uuid) = cl_uuid_factory=>create_system_uuid( ).
       DATA(uuid_x16) = system_uuid->create_uuid_x16( ).
       select * FROM zi_lfa1_2 into TABLE @DATA(lt_result).
         lfa1_ock_data = VALUE#( ( 
                                  Lifnr = uuid_x16 Name1 = 'Raj' Land1 = 'Ind' ) )
       cds_environment->insert_test_data( i_data = lfa1_mock_data ).
         select * from zi_lfa1_2 into TABLE @DATA(lt_result).
           i_keys = value #( ( Lifnr = uuid_x16 ) ).
           cut-> check_country( exporting key = i_keys
                                changing failed = c_failed reported = c_reported ).
           cl_abap_unit_assert=>assert_not_initial( act = c_reported msg = 'failed' ).
       ENDMETHOD.
       method teardown.
         cds_environment->destroy( ).
         ENDMETHOD.
         METHOD class_teardown.
           cds_environment->clear_doubles( ).
           ENDMETHOD.
    ENDCLASS.

Conclusion: Writing ABAP unit test in RAP ensures that the underling business logic is robust and reliable. Structured unit test not only improve code quality and reliability but also facilitate easier maintenance and refactoring.

Int4 Suite — your SAP Joule testbed and skills builder

2025-09-28T19:05:56.520000+02:00

Intro

Want to build reliable Joule skills and agents without breaking anything (or anyone’s nerves)? Treat Int4 Suite as your Joule testbed and skills builder: a place where you discover the real shape of a skill from historical traffic, scaffold its definition, rehearse end-to-end flows in a safe sandbox, and wire everything into MCP or CI/CD so quality checks can happen automatically.

This post shows a pragmatic playbook for S/4HANA + SAP BTP Integration Suite teams to use Int4 beyond SAP API testing and simulation as a preparation and enablement layer for SAP Business AI.

Why does Int4 belong in your Joule toolchain?

Reality-first inputs. Int4 stores and mines historical electronic messages (IDoc/OData/REST) and master data, gold for grounding AI skills in how your business actually runs.
Process-aware, agentic orchestration. It doesn’t just fire single APIs; it understands and can prepare the business context, chaining SO→Delivery→Invoice and fixing missing prerequisites on the fly. SAP Community
Safe simulation. Int4 Suite virtualizes third-party/partner systems so you can shadow-run agents end-to-end without touching production endpoints.
Modern hooks. SAP’s Joule Studio gives your agents standard tool interfaces; Int4’s actions and datasets slot right in.

1) Discover the real skill you need (from history)

Problem: Spec sheets rarely match production reality. Which fields are really required? What defaults do users rely on? Which edge cases appear in the wild?

How:

Mine historical interface messages across S/4HANA and Integration Suite: pull IDocs, OData/REST payloads for Sales Orders, Deliveries, Invoices, etc. Use them as canonical examples and edge cases for your skill’s inputs/outputs and constraints.

Figure - Int4 Suite - Robotic Crawler to fetch millions of historical API postings

Reconstruct end-to-end flows (e.g., SO→Delivery→Invoice) from those messages so your skill spec mirrors the actual business process, not just API docs. This is the core of process-aware agentic testing in Int4. SAP Community

Figure - Int4 Suite - Fix issues with missing stock for a business process posting (outbound delivery part of the Order to Cash process)

Why it matters: You stop guessing which fields matter and start from observed truth, exactly the inputs your Joule skill must handle.

2) Auto-scaffold skill definitions for Joule Studio

Problem: Turning messy real-world payloads into a clean skill I/O schema (and examples) is tedious and easy to get wrong.

How:

From mined payloads, extract: required vs. optional fields, typical defaults, allowed value ranges.
Turn that into your Joule skill definition (inputs/outputs plus example payloads) in Joule Studio.

Figure - Int4 Suite dimensions created automatically from historical API calls can be used to create Joule skills

Use Int4 Robotic Crawler outputs, hundreds of realistic variants, to seed positive, boundary, and negative examples that harden your prompts/spec.

Why it matters: You get a model-ready spec, grounded in real data, with examples covering the weird cases you’d otherwise miss.

3) Safe sandboxes for agent rehearsal (“shadow mode”)

Problem: Early skills need practice with all their integration touch-points but production endpoints are risky and partners are not always available.

How:

Use Int4 Suite to virtualize 3rd-party/partner APIs and even replay historical responses; point your early Joule skill/agent to this sandbox. Run full E2E flows, including error/failure drills, without touching live systems.
Pair with SAP S/4 or iFlow stubs so multi-step scenarios can execute safely (e.g., simulate 3PL delivery confirmations, EDI partner messages).

Why it matters: You “flight-test” the skill’s decisions and error handling in realistic conditions, safely.

4) Wire Int4 Suite into your MCP + CI/CD toolchain

Problem: Skills evolve. APIs and iFlows change. You need automatic quality gates—every time.

How:

Wrap Int4 actions as MCP tools so your dev copilot or even Joule Studio automations, can call them during build/validation.
Let SAP Cloud ALM/DevOps trigger Int4 suites when Joule skills or iFlows change; Int4 already supports automated test-case harvesting and orchestration around Integration Suite.

Why it matters: Every transport becomes self-verifying. Skills can’t drift out of compliance without getting caught.

How does this complement SAP’s Business AI?

Joule Studio remains where you author skills/agents. Int4 feeds it: schemas, examples, and safe endpoints.
MCP servers are how agents call tools; Int4 becomes a tool provider (testing, data seeding, etc.).
Integration Suite + Cloud ALM keep operations clean; Int4 strengthens them with evidence-driven regression around API and iFlow changes.

Figure - Int4 Suite - validate changed APIs or iflows

Where to learn more

Process-Aware Agentic Testing of SAP with Int4 Suite - why “agentic” tests matter and how Int4 auto-prepares missing context. SAP Community
Agentic Testing & Simulation with Int4 Suite’s SAP Business Knowledge Graph - democratizing simulation & semantic search over test cases. SAP Community
Cloud ALM with Integration Suite - monitoring and change-driven automation hooks. SAP Community

Foreign entity in RAP

2025-09-29T09:05:47.440000+02:00

Description:

A RAP BO entity which is not part of the BO composition tree for which it is defined. Defining a foreign entity in the behavior definition enables cross-BO message mapping between the two BOs.

Key Concepts:
RAP foreign entity is a component of the BC-ESI-RAP RESTful ABAP Programming Model. It is a representation of an external entity, such as a web service, that can be used in an ABAP program. The foreign entity is defined in the ABAP program and can be used to access data from the external source.

Tips & Tricks:
When defining a RAP foreign entity, it is important to ensure that all authentication information is correct. This will ensure that requests are sent securely and that responses are received correctly. Additionally, it is important to ensure that the URL of the external source is correct, as this will ensure that requests are sent to the correct location.

How to use it:
To use a RAP foreign entity, first define the entity in the ABAP program. This includes specifying the URL of the external source, as well as any authentication information that may be required. Once the entity is defined, it can be used to access data from the external source. This can be done using the RAP API, which provides methods for making requests and receiving responses from the external source.

Example :

"In our system, we have two distinct business entities: Inventory and Sales Order. Although they are separate, they are fundamentally linked. We manage this connection by using the product ID as the key identifier. This ensures that every time a sales order is created, the system automatically checks and deducts the correct quantity from the available stock in the inventory. This process maintains accurate, real-time stock levels, which is critical for our operations."

@EndUserText.label : 'inverty table' 
@AbapCatalog.enhancement.category : #NOT_EXTENSIBLE 
@AbapCatalog.tableCategory : #TRANSPARENT 
@AbapCatalog.deliveryClass : #A 
@AbapCatalog.dataMaintenance : #ALLOWED 
define table zscn_t_inventory { 

key product_id : abap.char(10) not null; 
stock_level : abap.int4; 
product_name : abap.char(40); 
create_at : timestampl; 
last_chdate : timestampl; 

}

@AccessControl.authorizationCheck: #NOT_REQUIRED 
@EndUserText.label: 'INTERFACE VIEW INVERNTORY' 
@Metadata.ignorePropagatedAnnotations: true 
define root view entity ZSCN_i_INVENTORY as select from zscn_t_inventory 
{ 
key product_id as ProductId, 
stock_level as StockLevel, 
product_name as ProductName, 
create_at as CreateAt, 
last_chdate as LastChdate 
}

@AccessControl.authorizationCheck: #NOT_REQUIRED 
@EndUserText.label: 'INVENTORY CONSUMPATION VIEW' 
@Metadata.ignorePropagatedAnnotations: true 
@VDM.viewType: #TRANSACTIONAL 
define root view entity ZSCN_C_INVENTORY 
provider contract transactional_query 
as projection on ZSCN_i_INVENTORY 
{ 
@UI.facet: [{ type: #IDENTIFICATION_REFERENCE }] 

@UI.lineItem: [{ position: 10 , label: 'Product Id' }] 
@UI.identification:[{ position: 10 , label: 'Product Id' }] 
key ProductId, 
@UI.lineItem: [{ position: 20 , label: 'Stock Level' }] 
@UI.identification:[{ position: 20 , label: 'Stock Level' }] 
StockLevel, 
@UI.lineItem: [{ position: 30 , label: 'Product Name' }] 
@UI.identification:[{ position: 30 , label: 'Product Name' }] 
ProductName, 
@Semantics.systemDateTime.createdAt: true 
CreateAt, 
@Semantics.systemDateTime.lastChangedAt: true 
LastChdate 
}

managed implementation in class zbp_scn_i_inventory unique; 
strict ( 2 ); 
with draft; 

define behavior for ZSCN_i_INVENTORY //alias <alias_name> 
persistent table zscn_t_inventory 
lock master 
total etag LastChdate 
draft table zscn_t_invent_d 
authorization master ( instance ) 
late numbering 
//etag master <field_name> 
{ 
create ( authorization : global ); 
update; 
delete; 
field ( readonly ) ProductId; 

validation vali_Stock on save { create; update; } 

draft action Activate optimized ; 
draft action Discard ; 
draft action Edit ; 
draft action Resume ; 
draft determine action Prepare ; 

mapping for zscn_t_inventory { 
CreateAt = create_at ; 
LastChdate = last_chdate ; 
ProductId = product_id ; 
ProductName = product_name ; 
StockLevel = stock_level; 
} 
}

In our system, a key validation for inventory is to prevent the stock level from ever going into a negative value.

METHOD vali_Stock.
    
LOOP AT keys INTO DATA(lv_key).

      READ ENTITY IN LOCAL MODE ZSCN_i_INVENTORY
       ALL FIELDS WITH VALUE #( (  %key = lv_key-%key ) )
      RESULT DATA(lt_result).

      CHECK lt_result IS NOT INITIAL.

      LOOP AT lt_result INTO DATA(lv_result).
        IF lv_result-StockLevel < 0 .
          APPEND VALUE #(  %tky = lv_result-%tky  ) TO failed-zscn_i_inventory.

          APPEND VALUE #(  %tky = lv_result-%tky
                 %msg = new_message_with_text( severity =
                 if_abap_behv_message=>severity-error
                 text = 'Stock value should not be negative value ' && ' ' && lv_result-StockLevel )
                 %element-stocklevel = if_abap_behv=>mk-on  ) TO reported-zscn_i_inventory .

        ENDIF.
      ENDLOOP.
    ENDLOOP.

  ENDMETHOD.

Sales order Entity

@EndUserText.label : 'SALES ORDER' 
@AbapCatalog.enhancement.category : #EXTENSIBLE_ANY 
@AbapCatalog.tableCategory : #TRANSPARENT 
@AbapCatalog.deliveryClass : #A 
@AbapCatalog.dataMaintenance : #ALLOWED 
define table zscn_dt_salesord { 

key sales_order_id : abap.numc(10) not null; 
product_id : abap.char(10) not null; 
quantity : abap.numc(5); 
customer_id : abap.char(10); 
order_date : abap.dats; 
@Semantics.amount.currencyCode : 'zscn_dt_salesord.currency' 
total_amount : abap.curr(13,2); 
currency : abap.cuky; 
create_at : timestamp; 
last_changed : timestamp; 

}

@AccessControl.authorizationCheck: #NOT_REQUIRED 
@EndUserText.label: 'SALESORD CONSUMPATION VIEW' 
@Metadata.ignorePropagatedAnnotations: false 
define root view entity ZSCN_C_SALESORD 
provider contract transactional_query 
as projection on ZSCN_I_SALESORD 
{ 
@UI.facet: [{ type: #IDENTIFICATION_REFERENCE }] 

@UI.lineItem: [{ position: 10 , label: 'Sales Order Id' }] 
@UI.identification:[{ position: 10 , label: 'Sales Order Id' }] 
key SalesOrderId, 
@UI.lineItem: [{ position: 20 , label: 'Product Id' }] 
@UI.identification:[{ position: 20 , label: 'Product Id' }] 
@Consumption.valueHelpDefinition: [{ 
entity: { name: 'ZSCN_C_INVENTORY', element: 'ProductId' } }] 
ProductId, 
@UI.lineItem: [{ position: 30 , label: 'Quantity' }] 
@UI.identification:[{ position: 30 , label: 'Quantity' }] 
Quantity, 
@UI.lineItem: [{ position: 40 , label: 'Customer Id' }] 
@UI.identification:[{ position: 40 , label: 'Customer Id' }] 
CustomerId, 
@UI.lineItem: [{ position: 50 , label: 'Order Date' }] 
@UI.identification:[{ position: 50 , label: 'Order Date' }] 
OrderDate, 
@UI.lineItem: [{ position: 60 , label: 'Total Amount' }] 
@UI.identification:[{ position: 60 , label: 'Total Amount' }] 
TotalAmount, 
Currency, 
@Semantics.systemDateTime.createdAt: true 
CreateAt, 
@Semantics.systemDateTime.lastChangedAt: true 
LastChanged 

}

managed implementation in class zbp_scn_i_salesord unique; 
strict ( 2 ); 
with draft; 

//foreign entity Zscn_i_inventory alias _inventory ; 
define behavior for ZSCN_I_SALESORD //alias <alias_name> 
persistent table zscn_dt_salesord 
lock master 
total etag LastChanged 
draft table zscn_dt_salord_d 
authorization master ( instance ) 
early numbering 
//etag master <field_name> 
{ 

create ( authorization : global ); 
update; 
delete; 
field ( readonly ) SalesOrderId; 

validation valid_ProductId on save { create; update; } 
determination stock_upadte on save { field Quantity; } 
 
draft action Activate optimized ; 
draft action Discard ; 
draft action Edit ; 
draft action Resume ; 
draft determine action Prepare ; 

mapping for zscn_dt_salesord 
{ 
CreateAt = create_at; 
Currency = currency; 
CustomerId = customer_id; 
LastChanged = last_changed; 
OrderDate = order_date;
ProductId = product_id; 
SalesOrderId = sales_order_id; 
Quantity = quantity; 
TotalAmount = total_amount; 

} 
}

without the foreign entity Zscn_i_inventory syntax , behavior definition of the ZSCN_I_SALESORD it only holding the structure of ZSCN_I_SALESORD it doesn't hold the structure Zscn_i_inventory .

Due to the separate entity definitions, errors from an inventory stock update cannot be directly propagated to the sales order user interface. In Failed and Reported structure will be miss match.

To propagate this we use of foreign entity syntax .

uncomment the //foreign entity Zscn_i_inventory alias _inventory ; in Behavior definition of Zscn_i_salesord .

After adding the Foreign entity Zscn_i_inventory alies _inventory ;

We can see the change in the entity Zscn_i_salesord structure .

Using the Determination we are update the stock of the inventory table based on the Product id in Behavior definition implementation class .

A critical validation has been implemented: when a sales order is created, if the requested quantity is greater than the available stock level, an error is raised in the inventory business logic. This error is then propagated to the sales order entity, making it visible on the sales order screen.

METHOD stock_upadte. 

LOOP AT keys INTO DATA(lv_key). 

READ ENTITY IN LOCAL MODE zscn_i_salesord ALL FIELDS WITH 
VALUE #( ( %key = lv_key-%key ) ) 
RESULT DATA(lt_result). 

CHECK lt_result IS NOT INITIAL. 

LOOP AT lt_result INTO DATA(lv_result). 
 
READ ENTITY ZSCN_i_INVENTORY 
ALL FIELDS WITH VALUE #( ( ProductId = lv_result-ProductId ) ) 
RESULT DATA(lt_result_inventory). 

LOOP AT lt_result_inventory INTO DATA(lv_inventory). 

 DATA(lv_stock) = CONV i( lv_inventory-StockLevel - lv_result-Quantity ). 

MODIFY ENTITY ZSCN_i_INVENTORY UPDATE FIELDS ( StockLevel ) 
WITH VALUE #( ( %key-ProductId = lv_inventory-%key-ProductId 
StockLevel = lv_stock ) ) REPORTED DATA(ltreported). 

if ltreported is not INITIAL. 
 
DATA: lt_dummy LIKE reported-_inventory. 
lt_dummy = CORRESPONDING #( ltreported-zscn_i_inventory ). 

APPEND LINES OF lt_dummy TO reported-_inventory.  

endif. 
      ENDLOOP. 
   ENDLOOP. 
ENDLOOP. 

ENDMETHOD.

In above code I am using CORRESPONDING #( ltreported-zscn_i_inventory ). because of while using the EML syntax the report will be early but inside the Behavior definition it will be late structure.

In inventory entity this are the possible product we have in that i will chose Titan watch

When creating a sales order for a Titan watch, if the requested quantity of 50 exceeds the available stock of 40, the system will prevent the transaction and display an error.

The error which is from the inventory entity by using the foreign entity concept we are propagating the error message of inventory in sales order entity.

Related Information:
For more information on using RAP foreign entities, please refer to the SAP Help documentation on BC-ESI-RAP RESTful ABAP Programming Model. Additionally, there are many tutorials available online which provide step-by-step instructions on how to use RAP foreign entities in an ABAP program.

Thanks for

What is RAP foreign entity in SAP BC-ESI-RAP? Definition & Tips

https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbdl_foreign.htm

Agentic AI Testing for Greenfield S/4HANA Outbound Interfaces - Part 1

2025-10-01T11:01:36.832000+02:00

Intro

Outbound interfaces are the lifeline between your new S/4HANA Greenfield or Selective Data Transition system and the outside world. Customers, vendors, 3PL partners, they still expect the same EDI (or non-EDI) output messages, even if you’ve reshaped half your internal processes in the course of the SAP S/4HANA transformation.

The real challenge? Functional consultants need to validate those outbound messages themselves, without waiting on an EDI provider, an integration colleague, or an EDI partner. That’s where Agentic AI validation with Int4 Suite comes in.

This playbook shows how functional consultants can independently test and validate outbound interfaces, step by step, without leaving the SAP S/4HANA + Int4 Suite environment.

Why functional consultants, not integration teams?

Most SAP projects (Greenfield, Selective Data Transition, or any other complex SAP S/4HANA upgrades) involve huge shifts inside SAP, but the outside world doesn’t care. Partner EDI flows must remain identical.

Traditionally, testing those flows meant:

Asking the EDI partner/provider for some sample messages
Trying to run the transaction in SAP S/4HANA
Asking the EDI provider to re-check/confirm outbound messages.
Pulling in a specialist from the integration team if something takes too long.
Repeating the same process multiple times with very little time to do it

Our approach flips this. It empowers the SAP functional consultant to:

Insert thousand of historical EDI messages from any productive system
Ask Int4 Suite to find the test data within those messages
Reproduce SAP transactions from historical payloads, like Sales Order Confirmation, Delivery (ASN) notification, Invoice Notification
Validate the EDI outbound messages directly in Int4 Suite by the functional consultant
The whole process takes minutes not hours and can be done hundreds of times per hour with no external dependencies (other partners)

No waiting on specialists, no bottlenecks, and much faster iterations.

Step 1: Reality-first message mining with Robotic Crawler

Use the Int4 Robotic Crawler to load hundreds or thousands of real historical messages (EDI or otherwise) into Int4 Suite. These are not toy examples — they’re your actual outbound payloads as they once moved through production.

Figure - Int4 Suite Robotic Crawler can fetch EDI messages from any supported archive or integration platform on mass scale

Why it matters: Consultants can work with authentic data, not spec sheets or made-up test cases.

Step 2: Conversational selection of test cases

Functional consultants don’t need to master payload filtering. Instead, they can simply chat with the agent to select which messages they want to test.

Want to see all outbound orders from a specific customer? Or deliveries with a particular Incoterm? Just ask the agent.

Figure - select a historical EDI messages using different criteria (business document, partner, material, etc.) and use this data for testing

Why it matters: Test-case discovery becomes intuitive, not a technical exercise.

Step 3: Reconstruct SAP business objects from payloads

Once a message is selected, the consultant can instantly recreate a business document (e.g., a Sales Order) inside S/4HANA using the data from that outbound message.

Figure - creating a sales order using the data from the historical EDI message as input

Now you have a living document in S/4HANA, built directly from the same payload your partners receive.

Why it matters: Consultants can validate the end-to-end logic of their own functional processes, with no dependency on integration experts.

Step 4: Agentic comparison of original vs. new outbound message

After posting the new Sales Order (or Delivery, or Invoice), the consultant sends the newly generated outbound reference back to the AI agent. The agent compares this outbound message to the original one from Step 1.

Figure - use the historical EDI message to compare with the new one and fetch is by just supplying the new order reference number

Are they still identical? Has anything in S/4HANA configuration changed the outbound structure? Did the partner-facing fields remain untouched?

Figure - display the comparison of the two EDI messages (original and the new one) to fix any SAP S/4HANA configuration issues (like line item category determination, substitutions, calculations, etc.)

Why it matters: Consultants get a precise answer immediately, without needing to export messages into external systems or call for backup.

Who benefits from this approach?

Functional consultants in SAP S/4HANA Greenfield or Selective Data Transition projects who must ensure message stability despite deep process changes.
Project teams that want faster, independent validation without pulling scarce EDI resources.
Business stakeholders who need assurance that partners will keep receiving the same documents as before, no surprises.

Who is this not for?

Integration consultants looking to stress-test iFlows or middleware mappings — this isn’t their playground. Int4 Suite has other features to facilite those requirements.
EDI providers who validate full partner connectivity, that’s still their domain.
Pure developers focused on code-level regression, this approach is tailored for business-facing validation.

Why it matters for S/4HANA programs where EDI messages remain the same but SAP S/4HANA can change?

Outbound interfaces are always the fragile bridge in any migration. By equipping functional consultants with agentic AI validation, you:

Shorten test cycles.
Reduce reliance on external partners.
Increase confidence in project quality.

Outbound messages stay consistent, partners stay happy, and your SAP S/4HANA Greenfield program keeps its velocity.

This approach isn’t about replacing integration experts — it’s about freeing functional consultants to independently confirm that what leaves the system is still what the outside world expects. It’s the missing puzzle piece for smooth, low-friction interface validation in SAP transformations.

Int4 Suite Agents Empowers Functional Consultants To Test Integrated SAP S/4HANA Business Processes

2025-10-03T11:41:59.491000+02:00

Introduction

Integrated business processes are the bloodstream of SAP systems. Every Sales Order, Purchase Order, Delivery, and Invoice has to flow smoothly, not just within SAP, but across EDI partners (customer, vendors, 3PL partners) banks, warehouses, tax portals.

Here’s the paradox: SAP S/4HANA projects have plenty of sophisticated automation tools, but they rarely help functional consultants in their manual tests. Instead, those tools get pushed into the narrow niche of automation testers. Functional consultants treat them like mythical dragons, complicated, dangerous, and likely to drag them away from their real work into procedural swamps.

The result? Slow testing cycles, dependency on integration specialists, and endless waiting for external partners to provide messages or confirmations.

Changing the story with simulation agents

The better path is not to force functional consultants into scripting or automation frameworks, but to give them simulation agents that mimic the system environment.

Instead of saying: “learn a test framework and run automated scripts,” we can say: “here are agents that simulate your missing EDI partner, your unavailable 3rd party/legacy system and you can test with them right now.”

This changes the game:

No competition with automation teams.
No learning curve with complex frameworks and procedural delays.
Consultants get something they instantly understand: realistic test conditions on demand, using actual historical production data.

How Int4 Suite Agents Work

With Int4 Suite, simulation agents provide a simple interface: the consultant performs the transaction in SAP, the agent feeds in authentic historical test data, and then automatically checks whether the newly generated EDI or non-EDI message matches what was sent in production.

Below are examples of key agents and how they fit into typical integrated OTC and P2P processes

Figure - meet the Int4 Suite Agents

EDI Partner Agent (based on historical data)

Role: Replays authentic production EDI messages from trading partners (ORDERS, DESADV, INVOIC).

How it works:

Consultant performs the transaction in SAP (e.g., creates delivery, sends invoice).
Agent provides historical test data from previously exchanged documents.
Agent automatically compares the newly generated EDI message with the production one for a similar case.

OTC examples:

Consultant in the OTC team replays historical ORDERS from the largest customer and verifies whether, after pricing condition changes, the system still calculates correctly.
Consultant tests goods receipt with historical DESADV data; agent compares the new EDI message against the production one.
Consultant issues a sales invoice (INVOIC) and agent validates it against the original production invoice, checking VAT rules.

Figure - Select Historical EDI messages from Production system which need to be rerun on Test System

P2P examples:

Consultant creates a purchase order; agent provides a historical ORDRSP where the supplier delivered partially, then compares the new outbound message.
Agent simulates a supplier INVOIC and verifies whether workflows behave the same after configuration changes.

Figure - manipulate the historical/production landscape EDI message data before sending that to the test environment

Unavailable System Agent (Non-SAP)

Role: Simulates external systems (banks, customs, WMS/TMS, tax portals) with historical production communications.

How it works:

Consultant runs the business process in SAP.
Agent injects historical test data from the external system.
Agent compares the new outbound message with the original production one.

OTC examples:

Consultant tests e-invoicing using a historically rejected invoice; agent checks whether the new output matches the original and if the new rules handle it.
Consultant tests shipment confirmations with historical WMS responses.

P2P examples:

Consultant tests bank payments; agent supplies historical payment files and checks the new output structure.
Consultant tests tax submissions; agent provides historical records and compares new vs. old messages.

Figure - Display the historical EDI data used on production landscape before rerunning that on the test environment

Historical Data Agent

Role: The production message librarian, replays large volumes or special cases directly from production.

How it works:

Consultant triggers transactions in SAP (bulk orders, invoices, returns).
Agent provides the historical payloads.
Agent verifies test messages against the production equivalents.

OTC examples:

Consultant replays a “Black Friday” scenario with 10,000 ORDERS; agent validates each new EDI message against its production twin.
Consultant tests credit memo flows from historical complaint cases.

Figure – run many historical messages on the test environment for bulk testing purposes

P2P examples:

Consultant tests bulk supplier invoices; agent validates the outputs against production.
Consultant tests blocked spare-parts orders with historical references.

Integration Consultant Agent

Role: A technical assistant that retrieves and compares messages from middleware layers (PI/PO, CPI).

How it works:

Consultant executes the business process in SAP.
Agent fetches the historical integration payload.
Agent highlights differences between new and historical messages.

OTC examples:

Consultant creates a sales order; agent compares the IDoc/XML message with the historical SAP Integration Suite payload.
Agent highlights mapping differences at field level after configuration changes.

Figure – fetch an EDI payload produced by the integration platform (SAP Integration Suite, etc.) from a newly created business document and compare with the historical one from the production landscape without asking SAP Integration Consultant for help

P2P examples:

Consultant enters a supplier invoice; agent pulls historical Ariba-CPI payload and checks consistency.
Agent validates purchase order messages across production and test runs.

Why it matters for SAP S/4HANA projects

In S/4HANA transformations, the external world doesn’t care about your internal redesigns. Customers, suppliers, and banks still expect exactly the same messages they used to get. Outbound and inbound interfaces are fragile bridges that must remain stable.

By equipping functional consultants with Int4 Suite agents:

Test cycles shorten dramatically.
Reliance on external partners and scarce integration resources drops.
Confidence in end-to-end quality rises.

This isn’t about replacing automation experts or integration teams. It’s about enabling functional consultants to independently confirm that what leaves SAP (or comes into it) is still what the outside world expects.

It’s the missing puzzle piece for smooth, low-friction testing of integrated business processes in SAP transformations.

More information:

Agentic AI Testing for Greenfield S/4HANA Outbound Interfaces - Part 1

Int4 Suite — your SAP Joule testbed and skills builder

Process-Aware Agentic Testing of SAP with Int4 Suite

Agentic Testing and Simulation with Int4 Suite's SAP Business Knowledge Graph

Taking Control of Clean Core: When to Use Project Kernseife in addition to Standard SAP Tools

2025-11-04T13:58:13.826000+01:00

TL;DR

Measuring SAP Clean Core involves a choice:

As a RISE with SAP customer, you can benefit from the out-of-the-box standard approach with SAP Cloud ALM. The RISE with SAP Methodology Dashboard provides you with a high-level standardized view with minimal effort.
Or you can choose an open-source, highly flexible, and customizable approach with Project Kernseife. You get custom classification to create actionable insights, but it requires ownership and additional effort.

This article will help you decide which path is right for your team's Clean Core journey.

How the RISE with SAP Methodology Dashboard measures Clean Core

SAP's answer on how to measure clean core is based on two standard tools: The ABAP Test Cockpit (ATC) (and its newly released checks as from SAP Note 3565942) and the RISE with SAP Methodology Dashboard in SAP Cloud ALM.

The process begins with the ATC, which analyzes your custom code against a well-defined set of rules. The key to this analysis is the classification of your custom extensions based on the official release status of the standard SAP objects they utilize. This release information is transparently published by SAP in the Cloudification Repository (Viewer).

As described in more detail in the Clean Core Extensibility Whitepaper (see chapter 3.3), the ATC assigns your extension a level based on the most critical SAP object it utilizes:

Level A - For extensions using only stable, released objects, ensuring maximum upgrade security.
Level B - For extensions whose most critical dependency is a classic API like a BAPI or classic technical frameworks.
Level C - For extensions touching any unreleased, internal SAP objects.
Level D - For extensions using objects that are explicitly not recommended.

The results of this structured analysis can then be uploaded to SAP Cloud ALM, populating the Clean Core Extensibility KPIs in the RISE with SAP Methodology Dashboard. Recently, the dashboard was enhanced with a display of the Clean Core Levels. This gives organizations a high-level, standardized view of their extensibility landscape, which is perfect for assessing their current situation and tracking progress. For the near future (Q1/2026) it is moreover planned to offer a deep dive dashboard that provides further details about the results.

What is "Project Kernseife"?

Project Kernseife is an open-source custom ATC Check for ABAP systems that enables you to flexibly score the usage of SAP objects in your system, e.g. to score the technical debt regarding clean core based on a custom, adjustable classification. More details on the parts and approach can be found in the blog "Project Kernseife - improving the measurement of Clean Core in ABAP".

Why Project Kernseife and its custom classification can be a Game-Changer for Clean Core Governance

Advantage 1: Fine-Tune SAP's Rules & Reduce "False Positives"

While SAP delivers thousands of released and classic APIs, it might still be not the perfect fit for your individual project and scope. Kernseife allows you to customly classify objects as "acceptable for your project", dramatically reducing noise and the need for mass ATC exemptions. Let's look into two different scenarios, to show you the benefits of custom classification:

Example 1: Stricter governance for direct table read

Within the standard classification, a direct read with a SELECT from any SAP table is considered as "Level C", which leads to warnings in ABAP Test Cockpit. In your project, you want to enforce the usage of ABAP cloud, you maybe have (see next point) identified many successor objects (custom and standard) and want to push developers to the successors objects (e.g., famous I_Product instead of MARA) by showing these as an error.
Remark: In standard ATC, you can adjust the priority of a check message in general (for example "Reading from DDIC database tables or DDIC table views is not recommended (successor available)", but not based on specific SAP objects you refer to.

Example 2: Need for usage of "internal object"

Now let's imagine you are working in a "clean core" project, but you need to extend processes around the Outbound Delivery Orders in EWM. After talking to experts, finding blog posts and even an "official" SAP Note, you identified the right interface: /SCWM/IF_API_WHR_OUTBOUND. Unfortunately, this is not yet listed as released or classic API. This would result in "warnings" in ATC and a classification as Level C ("Internal Objects" are used), although you did the best you can do. With Kernseife, you can now mark this SAP object as "recommended", which results in only "information" messages in ATC and leads to a "Level B" assessment of the custom code object / extension.

Based on these two examples, you can see: this is the power of a custom classification. You can overrule the SAP standard, be it because of timing (as you need the announced adjustments from the blog IMMEDIATELY) or scope (because SAP might not generally classify everything that you identify as "acceptable for your project" as "Classic API").

The possibility to "accept" usage of certain SAP objects will increase your governance quality, as your exemption approvers will not be flooded with hundreds of "false" exemption requests for objects that you generally accept in your project.

Advantage 2: Define and Enforce Custom Successors

While SAP is already delivering hundreds of the most important successor classifications (famous MARA -> I_Product), there might still be potential to guide your developers more precisely. Project Kernseife allows you to maintain a successor object in your classification, that will also be visible in the result of your ATC check - this makes it actionable for your developer!

Example 1: "Improve" Standard Successors

There are some more tables in the system, that have no successor mentioned officially, but where you can find (released!) CDS views as an alternative. To not flood you with details here, I simply refer to another blog based on the idea of @AndreasGraeber. But also for Function Modules or classes , there might be clear successors (e.g. not all READ_<table> might be having the successor information. There might be a lot of areas, where you want to decide in your project "don't use this, but use that!"

Example 2: Enforce and centralize Wrappers / custom successors

What happens if you create a wrapper for a standard SAP object, but your colleagues are not aware of it? They might re-create the same wrapper. With the possibility to also add Custom Objects (e.g. Z_WRAPPER_ABC) as a successor, you can also push your developers to harmonize the usage of wrappers.

Advantage 3: Enhance Dashboards for Measurement and Governance with consistent transparency

In several projects, we have already seen custom dashboards to track the current state of clean core. With the combination of the level concept and the "Technical Debt Score", you can assess systems and drill down into packages or even single objects.

Project Kernseife offers you direct access (e.g. with CDS-View ZKNSF_I_SCORING) to the data from ATC check runs to build these dashboards. You can use the Kernseife BTP Application to analyze your score - or create your own dashboard, for example with SAP Analytics Cloud, reflecting your custom rules to assign custom objects to business units (e.g. ZBR* is always Brasil).

The scoring is based on your configuration in the Kernseife classification, which allows you to own the definition of your clean core levels and deviate from SAP's standard definition - by this you own the definition of your clean core levels! To stick with the examples above, the usage of /SCWM/IF_API_WHR_OUTBOUND will impact your score in a limited way.

Advantage 4: Prioritize Your Cleanup Efforts with a "Potential Score"

After an analysis, you often face a daunting list of findings. The biggest challenge isn’t just identifying the issues, but knowing where to start the cleanup. This is where Kernseife's scoring mechanism becomes a powerful prioritization engine by providing two key metrics for each finding: a Score and a Potential Score.

The Score reflects the technical debt of the object as it exists today, based on your custom rules.
The Potential Score shows what the score would be if the developer refactored the code to use the defined successor.

Let's use our familiar example:

Your classification assigns a high "Technical Debt" Score of 10 for a direct SELECT on table MARA.
The officially released successor, I_Product, has a "clean" score of 0. Therefore, the finding's Potential Score is 0.

This creates a clear, quantifiable "improvement gap." An object with a Score of 10 and a Potential Score of 0 is a high-impact cleanup opportunity. In contrast, a finding with a Score of 2 and no defined successor (meaning its Potential Score is also 2) is a lower priority for immediate refactoring.

By sorting your findings based on the largest gap between the Score and Potential Score, you can instantly identify the "low-hanging fruits" and the refactoring tasks with the biggest impact. Let's be clear, this is just one piece of information, and maybe you shouldn't have any custom code in this area based on a process analysis, but I still believe it is important to have data to drive your decisions - and Project Kernseife offers you data for the technical insights.

Making the Right Choice: A Balanced Look at Both Approaches

Key Reasons to Adopt Project Kernseife

The main reason to use a Project Kernseife is typically the power of the custom classification (as the last chapter pointed out). You can adjust the classification of SAP objects based on your project reality and support your clean core journey with tailored data.

In addition, there might be a temporary, tactical benefit: As of today, Kernseife's dashboards can fill a gap until SAP's "Extensibility Deep Dive" dashboard is generally available.

Important Considerations: When the Standard Approach is a Better Fit

At the same time, I want to be very clear: Project Kernseife is not needed in every company and project.

1. The Need for Standard Alignment: If your primary goal is to align perfectly with SAP's out-of-the-box reporting and dashboards without deviation, the standard approach is more appropriate.
2. The Responsibility of Power: Custom classification is powerful, but it requires ownership. Someone must define, document, and maintain these custom rules. This is an ongoing responsibility (and effort!), which you can spare yourself when you go with the standard solution, i.e. RISE with SAP Methodology Dashboard.
3. Implementation and Maintenance Overhead: While straightforward for experienced teams, implementing and maintaining any non-standard solution requires effort that must be planned for. It is ironically against the clean core imperative of leveraging "standard"!
4. Unified Classification enables comparibility: Standardized classification leads to a comparability between different systems (e.g., you compare your central finance system with a peer system regarding the clean core level share), as the classification is the same for all systems.

Conclusion: Do you need to Take Control of Your Clean Core Strategy?

Project Kernseife is not for everyone. It is for organizations that find the standard clean core measurement too rigid and are ready to invest the effort to build a more nuanced, context-aware governance model. If you have the capacity and the architectural vision, it can transform your clean core initiative from a technical cleanup exercise into a strategic management of your system's extensibility.

Interested in more? Check out Project Kernseife: our open-source project where you can join the community, contribute, and support us with a GitHub star in the repository!

You Are Standing in an Open Field... Inside SAP GUI

2025-12-09T17:51:44.456000+01:00

How I ported Zork to ABAP in one day and made 46-year reunion of two mainframe legends possible.

1979 was quite a year for the mainframe: In Germany, SAP released R/2, the integrated ERP system that would define enterprise computing. In Massachusetts, Infocom was founded to commercialize Zork, the text adventure born on MIT's PDP-10 mainframes.

For 46 years, they ran on parallel tracks. Until last month.

Microsoft released the original source code for Zork I. The stars aligned. It was time for a family reunion.

I got nostalgic. I wanted to play Zork I: The Great Underground Empire. But I didn't want to play it in a browser or a terminal. I wanted to play it where I spend my time: In SAP GUI.

So, I decided to port the Z-Machine (Infocom's Virtual Machine) into SAP S/4HANA.

The Z-Namespace destiny... you knew it. In SAP development, every custom object must start with the letter Z: (Also Y, but Y is not used widely. And no one knows why Y is not used)

The Machine: Z-Machine.
The Transaction: ZORK.
The Package: $ZORK.

So it felt like it was meant to be here.

Building a VM in One Day (The "How")

"Alice," you say, "Writing a Virtual Machine in ABAP takes weeks of reading bit-level specs."

It took one day.

And I wrote almost none of it:

ZORK T-CODE in SAP GUI

99% Vibe coded

I used VSP (Vibing-Steampunk) — my open-source bridge that gives Claude (or Copilot/Codex/Mistral Vibe - any other Assistant) direct access to the SAP system via MCP. I treated the AI not as a chatbot, but as a Senior ABAP Developer who loves retro specs.

Here is what happened when my Z-Machine crashed on the first turn:

Me: "It crashes when I try to LOOK. Plz debug."

Claude didn't guess. Using VSP, Claude:

Set a breakpoint in the ABAP code.
Ran the game inside SAP.
Inspected the memory (finding a Big-Endian vs Little-Endian mismatch in the object table).
Fixed the code.

This isn't just generating text. This is Digital Archaeology assisted by Artificial Intelligence.

Why This Matters

I now have Zork running in S/4HANA.

But the real story isn't the game. It's the capability.

If an AI agent can read a 1980s technical spec, navigate a custom ABAP stack, and debug runtime errors to reunite two pieces of 1979 history...

...imagine what it can do for your 2005 legacy code ^_^ (Yes, even with ECC).

The Repo (ZORK-ABAP): https://github.com/oisee/zork-abap
The Tool (VSP): https://github.com/oisee/vibing-steampunk - ADT-to-MCP bridge.

Credits:

Infocom (1979) for the Z-Machine.
SAP (1979) for the R/2 legacy that led us here.
Graham Nelson for the Z-Machine Standards Document.
Claude (2025) for writing the code.

P.S. West of House. There is a transport request here.

#SAP #ABAP #Zork #RetroGaming #AI #MCP #DigitalArchaeology #OpenSource #Microsoft

Shout out to Scott Hanselman: Tnx for driving Open Source initiative ^_^

ABAP Platform in SAP S/4HANA Cloud Private Edition and SAP S/4HANA 2025

2025-12-14T23:10:11.122000+01:00

SAP S/4HANA Cloud Private Edition and SAP S/4HANA 2025 were released to the SAP customer base on October 8, 2025.

ABAP Platform 2025 is the technology platform underlying the release 2025 of SAP S/4HANA Cloud Private Edition and SAP S/4HANA and is shipped as part of these products, supporting only SAP HANA database with full exploitation of its advanced capabilities. In addition, ABAP Platform 2025 is part of SAP S/4HANA Foundation 2025 for SAP HANA-only Add-Ons.

ABAP Platform 2025 is not shipped as a standalone product. ABAP Platform 2025 consists of the AS ABAP, the ABAP development tools for Eclipse, and several additional technology components which are required to run SAP S/4HANA Cloud Private Edition and SAP S/4HANA.

Previous versions of SAP S/4HANA Private Edition and SAP S/4HANA such as 1610, 1709, 1809, 1909, 2020, 2021, 2022 and 2023 can be upgraded directly to the 2025 release, which is based on ABAP Platform 2025 (corresponding to SAP_BASIS 816).

Product Highlights

Presentation

This presentation provides the SAP official external slide deck, just click on it to view:

Overview

ABAP Platform 2025 delivers innovations for the ABAP stack in different areas.

Clean core development

In August 2025, SAP enhanced its extensibility guidelines by introducing the new Clean core extensibility white paper. The sustainable and upgrade-safe ABAP extensibility model in SAP S/4HANA Cloud Private Edition and SAP S/4HANA fully relies on SAP clean core guiding principles, aiming to decouple custom extensions from SAP standard whenever possible. The refined SAP guidance for extensibility replaces binary clean core decisions with a more nuanced evaluation of classic ABAP extensions based on the clean core level concept. Evolving from the previous 3-tier model, the new extensibility model categorizes extensions into four levels (A, B, C, and D) and provides rules for ABAP classic extensions to meet the clean core level qualifications. Following this new clean core extensibility guidance the ABAP extensibility guide was updated with technical guidelines to support the clean core level concept. The ABAP extensibility model was changed from 3-tier model to ABAP Cloud development (level A) and classic ABAP development (levels B, C and D).

The overall clean core guidance remained unchanged: always striving for the highest possible level of extensibility. ABAP Cloud is the SAP’s recommended development model for all new custom extensions in SAP S/4HANA private cloud and on-premise systems, whereby the classic ABAP extensibility can still be used to reach clean core, with a focus on upgrade-stability and code quality. This enables SAP customers and partners to transition to a clean core incrementally and at their own speed. SAP provides guidance for ABAP clean core development by offering a recommended list of APIs (so-called “classic APIs”) to be used in classic ABAP development. For governance of ABAP clean core development, the ABAP test cockpit (ATC) now supports the clean core level concept with new ATC checks (see the blog post ABAP test cockpit (ATC) recommendations for governance of clean core ABAP development). For governance of ABAP development for clean core in SAP S/4HANA private cloud or on-premise systems the remote ATC in SAP BTP ABAP environment is the SAP recommended approach.

SAP Joule for Developers, ABAP AI capabilities

SAP Joule for Developers, ABAP AI capabilities are now key components and an integral part of AI-assisted ABAP Cloud development, also facilitating custom code transformation from ECC to SAP S/4HANA. The capabilities supporting developer tasks include Joule copilot in ABAP development tools for Eclipse, predictive code completion, code explanation and unit test generation for ABAP and ABAP CDS, app and service generation (including RAP BO generation), predictive business logic for RAP BOs, and OData consumption. The provided ABAP AI SDK, powered by Intelligent Scenario Lifecycle Management (ISLM), can be utilized for the implementation of AI capabilities in custom applications.

The custom code migration capabilities include docs chat for questions around custom code migration and S/4HANA simplifications, explanation of business purpose and processing logic of legacy code (ABAP reports), explanation of S/4HANA-related ATC findings in custom code, along with resolution recommendations based on S/4HANA simplification items and cookbooks (see the blog post SAP Joule for Developers Expands to Private Cloud: Accelerating ABAP Innovation and Transformation).

ABAP RESTful Application Programming Model (RAP)

Another major investment area in the 2025 release is the ABAP RESTful Application Programming Model, which powers modern development in both ABAP Cloud and classic ABAP, enabling the creation of delightful transactional SAP Fiori apps as well as local and web APIs. This release delivers new features to accelerate and enhance the development with RAP, including new generators to boost efficiency, support of CDS table entities as persistence layer, various capabilities for SAP Fiori elements-based UIs, such as collaborative draft, cross-BO scenarios, tree views, and event-driven side effects, as well as end-to-end extensibility options.

New ABAP Cloud generators for creating OData UI services with RAP BOs (with one or more entities) from scratch, with or without AI assistance, or for generating custom UI service based on RAP BO interface are provided. ABAP CDS table entities can be used as active persistence layer for managed RAP BOs without draft, replacing classic dictionary database tables.

Enhancements for building of SAP Fiori elements-based apps with RAP include the collaborative draft handling, which allows multiple users to work simultaneously and collaboratively on the same draft instance of an entity without blocking one another. You can now also build SAP Fiori UIs that use multiple RAP BOs interacting with each other. These cross-BO scenarios rely on cross-BO transactional enablement, where the entities of the participating RAP BOs are linked through so-called cross-BO associations. Read-only and editable tree view supports displaying and manipulating hierarchical data in SAP Fiori UIs, with options for drag and drop, cut and paste, reordering, and cascading delete. Event-driven RAP side effects enable asynchronous updates in SAP Fiori UIs. When such a specific RAP business event is raised, the associated side effect is triggered, and the defined targets are reloaded in the UI.

The privileged context can now be propagated in subsequent Entity Manipulation Language (EML) requests in reading and modifying operation. Further enhancement for the behavior definitions and the behavior pools are provided with this release.

ABAP development tools for Eclipse (ADT)

Various enhancements are provided in ABAP development tools for Eclipse for ABAP development, RAP and ABAP CDS related development aspects, testing and troubleshooting, as well as overall IDE and productivity improvements.

Refactoring support for ABAP classes and interfaces was improved by activation of renaming changes by default, validation of new names and displaying long texts of exceptions. The new where-used dialog enables prefiltering of search results to focus on usages relevant for the concrete use case. There is a new property abaplv to filter object searches with the ABAP language version. There are new editors like for example for working with software component relations, Adobe Forms or maintaining intelligent scenarios and intelligent scenarios models which are required to run a solution based on generative AI. It is possible to create and edit CDS table entities and create for them behavior definitions.

In the area of ABAP unit tests, method calls in test classes can now be highlighted in different colors to distinguish their method contexts. Quick actions allow tests to be launched or templates for test classes to be inserted with a single mouse click. The failed assertions and status of test methods can be displayed directly in the source code editor. The unit tests can be rerun with coverage and coverage results can be cleared in the ABAP Coverage view. Additionally, there is a new AMDP Test Double Framework, and the CDS Test Double Framework now supports CDS hierarchy views.

In the ABAP debugger, it is now possible to display the memory consumption of a debugged ABAP program in the new ABAP Memory (Debugger) view. The ABAP Memory Snapshot view lists all memory snapshots, which can be opened in the editor to show memory objects ranked by size. These views make it easier to analyze the memory usage of an ABAP application. Internal tables can now be easily compared using the table comparison tool within the ABAP debugger. Beyond this, the ABAP debugger can now consider variables with hidden values (for sensitive data), display variables of type JSON, and show component groups for nested structures in the Variables view. Collaborative error analysis is supported by export/import of ABAP Cross Trace results to/from JSON file or export of short dumps as ZIP file in the ABAP Runtime Error Viewer.

Beyond this there are also enhancements in transport management for adding an object to a transport or searching and grouping transport requests.

ABAP Language

The modern, declarative, and expression-oriented ABAP language allows writing simple and concise ABAP code through features such as inline declarations and constructor expressions. Advanced operations for internal tables include grouping, filtering, and the CORRESPONDING( ) operator. The cloud-optimized version “ABAP for Cloud Development” is used for ABAP Cloud development.

There are further enhancements for internal tables, including support for arbitrary logical expressions and equality conditions, as well as harmonization of table expressions and READ TABLE statement. New ABAP system classes for probability distributions are provided, enabling the generation of random number and the calculation of quantile, probabilities, and other aspects. These classes support various discrete and continuous distributions. This release also delivers enhancements for expressions and functions, as well as for transformations, such as the new domain XSDGEO for serializing and deserializing spatial data between the Extended Well-Known Binary (EWKB) representation and the GeoJSON format.

SAP HANA-centric optimizations & Data Integration scenarios

Modern ABAP development on SAP HANA has been enhanced with several advanced, database-centric features also enriching data integration scenarios. Recent innovations in data integration focus on data exposure, including ABAP-managed database procedures for advanced read scenarios. With CDS updatable view entities it is now possible to wrap existing DDIC database tables (or CDS table entities) and expose a native CDS signature, which can be used with ABAP SQL in combination with DCL-based access control.

On the consumption side, new write scenarios, the use of static CDS external entities, and the possibility to create ABAP CDS models based on imported CDS models make it easier than ever to integrate external data seamlessly into an ABAP CDS view stack.

Additional enhancements, such as CDS table entities to define and manage SAP HANA database tables as native CDS repository objects, a CDS generation wizard to simplify and automate the creation of hierarchically structured data in ABAP CDS, and AI-powered CDS Explain to get semantical context information about CDS entities further brighten the ABAP development landscape.

Embedded analytics

For embedded analytics scenarios it is now possible to expedite development workflow using ABAP Cloud generator wizards for creation of multidimensional analysis apps, Review Booklet apps, or native CDS hierarchy definitions. With the introduction of reusable measures and filters, the key figures, measures, filters and many more features can now be defined centrally, based on user needs to better manage and align analytical reporting. They can also be utilized in CDS view entities to ensure homogenous definition of complex calculations and unification of coherences of the running business.

Event Enablement & Business Events

The event-driven architecture of SAP S/4HANA Cloud Private Edition and SAP S/4HANA is strengthened, and the interoperability across enterprise solutions is improved through seamless integration with SAP Event Mesh Advanced Plan and support of SAP Cloud Application Event Hub to consume events published by SAP Order Management Foundation on SAP BTP.

The event-driven processing and monitoring was enhanced with new outbound event filtering, enabling selective publishing based on configurable criteria, and dynamic topics in SAP Event Mesh Advanced Plan for more efficient routing. Operational transparency was improved through comprehensive event logging, including local capture and logging of successfully processed events. Events of the same type and object within a session can now be grouped as activities, improving traceability and reducing monitoring noise. Together, these features provide a scalable and well-governed foundation for event-driven architecture.

Process integration & Connectivity

Key highlights of process integration include a robust OData service consumption model with Swagger UI preview and advanced OData V4 capabilities, such as bulk processing and asynchronous communication integrated with AIF. The API governance and communication management was enhanced by introducing Communication Targets within Communication Arrangements, enabling more granular control over connectivity endpoints. API lifecycle management is improved through API-to-package assignment and the ability to create API packages for better organization across API types. Additionally, OData-based access to Communication Management data increases automation, transparency, and integration with external tools.

Additional connectivity improvements include outbound communication enablement via HTTP and RFC, support for setting the AIR key as a custom HTTP header in SOAP requests for more secure message handling, direct push-based data exchange between ABAP systems via RFC, and SSE support in the ABAP HTTP client and server for efficient real-time event delivery in distributed scenarios.

Key user extensibility

Further improvements are provided for key user extensibility. It is now possible to generate a Fiori elements application for a custom business object with just one click and maintain behavior extensions for SAP-provided RAP business objects using key user extensibility. Moreover, using developer extensibility it is now possible to implement feature control for custom fields that were created via the Custom Fields app. The new extension field wizard provides a better development efficiency by boosting the creation of custom fields via developer extensibility.

Security

Key updates include support for OAuth Authorization Code with PKCE (RFC 7636) and JWT-based client authentication (RFC 7523), as well as SAP-managed client certificates for secure integration in S/4HANA Private Cloud (2025 FPS01). TLS 1.3 is now supported across HTTP, WebSocket RFC, and SMTP, with OAuth Client Credential Grant enabled for SMTP outbound scenarios such as Exchange Online.

Additional enhancements include new OpenID Connect features, improved troubleshooting guidance (SAP Note 3111813), and a new OAuth Client Configuration UI (SOAUTH_CLIENT) with built-in testing and token metadata display.

Useful Blog Posts, Community pages and Learnings

ABAP Community Topic Pages:

ABAP Development Community
ABAP Testing and Analysis Community
ABAP Extensibility Community
ABAP Connectivity Community
SAP BTP ABAP Environment Community
SAP S/4HANA Cloud ABAP Environment Community

ABAP at SAP Events:

ABAP Cloud at SAP TechEd in 2025
ABAP Cloud at Devtoberfest in 2025

Clean Core

Clean core extensibility white paper
ABAP Extensibility Guide – Clean Core for SAP S/4HANA Cloud - August 2025 Update
ABAP test cockpit (ATC) recommendations for governance of clean core ABAP development
ATC on SAP BTP: blog | overview presentation
Certification of Partner Solutions following Clean Core

SAP Joule for Developers, ABAP AI capabilities

SAP Joule for Developers Expands to Private Cloud: Accelerating ABAP Innovation and Transformation
ABAP AI Revolution Accelerates: The ABAP Developer Who Built Enterprise Apps in Minutes
From Legacy to AI-Powered: RISE Transformation Revolution with Joule for developers
ABAP AI - Chapter 2

ABAP Cloud:

ABAP Exensibility Guide
Become SAP Certified Associate – Back-End Developer - ABAP Cloud
ABAP Cloud FAQ
SAP Build and ABAP Cloud Basic Trial Offering
Developer Guide: From Classic ABAP to ABAP Cloud on SAP Help Portal

Further blog posts and topic pages:

State-of-the-Art ABAP Development with ABAP RESTful Application Programming Model (RAP)
ABAP Tools for Clean ABAP

Useful Links

Release Notes for ABAP Platform 2025
Documentation on SAP Help Portal
Product Availability Matrix (PAM)
The ABAP Platform Strategy
ABAP Platform Releases and Consumers
SAP Note 3612209 – ABAP Platform 2025 – General information

Previous landing pages

ABAP Platform for SAP S/4HANA 2023
ABAP Platform for SAP S/4HANA 2022
ABAP Platform for SAP S/4HANA 2021
ABAP Platform for SAP S/4HANA 2020
ABAP Platform for SAP S/4HANA 1909
ABAP Platform for SAP S/4HANA 1809
SAP NetWeaver AS for ABAP 7.52
SAP NetWeaver AS ABAP 7.50

Building a Custom Stock/Requirements Report in SAP ABAP

2025-12-16T06:16:16.031000+01:00

Introduction

In SAP Materials Management, the Stock or Requirements List MD04 is one of the most frequently used transactions for planners and production teams. It provides a real-time view of current stock, incoming receipts, and outgoing requirements for a material at plant level. However, in real project scenarios, users often need a simplified, customized, or report-based version of MD04 that can be enhanced further or adapted to specific business needs.

During one such requirement, I worked on building a custom ABAP report that replicates the core functionality of MD04 while keeping the logic transparent and flexible. This blog explains how a custom Stock/Requirements Report can be built using standard SAP tables and function modules, without modifying standard SAP transactions.

Solution Review :

The custom report ZSTCOK_912 is designed to display stock and MRP elements for a given Material and Plant, closely mirroring the MD04 output.

1. Selection Screen

The report starts with a simple and user friendly selection screen:
Material Number MATNR
Plant WERKS
Both parameters are mandatory to ensure accurate stock evaluation.

2. Material Number Conversion

Since SAP stores material numbers with leading zeros, the report uses:

CONVERSION_EXIT_ALPHA_INPUT

This ensures the material number is in the correct internal format before database access.

3. Current Stock Determination

To calculate the opening balance:

Table MARD is read
All unrestricted stock LABST across storage locations is summed
This provides the current physical stock, which becomes the starting available quantity.

4. Fetching Stock or Requirements Data

The core of the solution uses the standard SAP function module:

MD_STOCK_REQUIREMENTS_LIST_API

This is the same API used by MD04 and returns:
MRP elements receipts and requirements
Quantities
Planning and control data
The data is stored in internal tables such as MDPSX, MDEZX, and MDSUX.

5. Display Logic and Running Stock Calculation

Each MRP element is processed sequentially:
Receipts increase available stock
Requirements reduce available stock
A running available quantity is calculated and displayed line by line, giving users a projected stock position over time.

6. Output Format

The report displays:

Date
MRP element type Receipt, Requirement, Dependent Requirement, etc.
Document number
Receipt quantity
Projected available stock
Additionally, summary information such as total records processed and current stock is displayed at the end.

The Complete Solution Code

*&---------------------------------------------------------------------*
*& Report ZSTCOK_912
*&---------------------------------------------------------------------*
*& Custom Stock/Requirements  Report
*& Purpose: Display stock and requirements similar to MD04 transaction
*&---------------------------------------------------------------------*
REPORT ZSTCOK_912.

*&---------------------------------------------------------------------*
*& DATA DECLARATIONS
*&---------------------------------------------------------------------*

" Reference to standard SAP tables for material master data
TABLES: mara, " General Material Data
marc. " Plant Data for Material

*&---------------------------------------------------------------------*
*& SELECTION SCREEN
*&---------------------------------------------------------------------*
" Input parameters for the report - both are mandatory
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE TEXT-001.
PARAMETERS: p_matnr TYPE matnr OBLIGATORY, " Material Number
p_werks TYPE werks_d OBLIGATORY. " Plant
SELECTION-SCREEN END OF BLOCK b1.

*&---------------------------------------------------------------------*
*& INTERNAL TABLES AND WORK AREAS
*&---------------------------------------------------------------------*

" Internal tables to store data returned by the function module
DATA: gt_mdpsx TYPE TABLE OF mdps, " MRP element data (dates, doc numbers)
gs_mdpsx TYPE mdps, " Work area for MDPSX
gt_mdezx TYPE TABLE OF mdez, " MRP element quantities
gs_mdezx TYPE mdez, " Work area for MDEZX
gt_mdsux TYPE TABLE OF mdsu, " Summary data
gs_mdsux TYPE mdsu. " Work area for MDSUX

" Structures for exporting parameters from function module
DATA: gs_mt61d TYPE mt61d, " Material requirements planning data
gs_mdkp TYPE mdkp, " MRP controller and configuration
gs_cm61m TYPE cm61m, " MRP list control data
gs_mdsta TYPE mdsta, " MRP statistics
gv_ergbz TYPE ergbz. " Result indicator

" Variables for processing and display
DATA: gv_labst TYPE labst, " Unrestricted stock quantity
gv_available TYPE labst, " Available quantity (opening stock)
lv_running_stock TYPE mng01, " Running available stock
lv_matnr TYPE matnr, " Material number with leading zeros
lv_txt TYPE char30, " Text for MRP element description
lv_count TYPE i. " Counter for total records

*&---------------------------------------------------------------------*
*& START-OF-SELECTION
*&---------------------------------------------------------------------*
START-OF-SELECTION.

"*------------------------------------------------------------------*
"* Step 1: Convert Material Number with Leading Zeros
"*------------------------------------------------------------------*
" SAP stores material numbers with leading zeros in database
" This conversion ensures proper format for database queries
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = p_matnr
IMPORTING
output = lv_matnr.

"*------------------------------------------------------------------*
"* Step 2: Get Current Stock from MARD Table
"*------------------------------------------------------------------*
" MARD contains storage location data for materials
" We sum all unrestricted stock (LABST) across storage locations
SELECT SINGLE SUM( labst )
INTO gv_labst
FROM mard
WHERE matnr = lv_matnr
AND werks = p_werks.

" Initialize available quantity based on query result
IF sy-subrc = 0.
gv_available = gv_labst. " Stock found
ELSE.
gv_available = 0. " No stock found
ENDIF.

"*------------------------------------------------------------------*
"* Step 3: Call Function Module to Get Stock Requirements List
"*------------------------------------------------------------------*
" MD_STOCK_REQUIREMENTS_LIST_API is SAP standard FM used by MD04
" It returns all MRP elements (receipts and requirements)
CALL FUNCTION 'MD_STOCK_REQUIREMENTS_LIST_API'
EXPORTING
matnr = lv_matnr " Material number
werks = p_werks " Plant
IMPORTING
e_mt61d = gs_mt61d " Planning data
e_mdkp = gs_mdkp " MRP configuration
e_cm61m = gs_cm61m " Control data
e_mdsta = gs_mdsta " Statistics
e_ergbz = gv_ergbz " Result indicator
TABLES
mdpsx = gt_mdpsx " MRP element master data
mdezx = gt_mdezx " MRP element quantities
mdsux = gt_mdsux " Summary data
EXCEPTIONS
material_plant_not_found = 1 " Material doesn't exist
plant_not_found = 2 " Plant doesn't exist
OTHERS = 3. " Other errors

" Error handling for function module call
IF sy-subrc <> 0.
WRITE: / 'Error getting stock requirements data'.
WRITE: / 'Return Code:', sy-subrc.
EXIT.
ENDIF.

" Check if any data was returned
IF gt_mdpsx IS INITIAL AND gt_mdezx IS INITIAL.
WRITE: / 'No stock requirements data found for Material:', p_matnr,
'Plant:', p_werks.
EXIT.
ENDIF.

"*------------------------------------------------------------------*
"* Step 4: Display Report Header Information
"*------------------------------------------------------------------*
WRITE: / 'Stock/Requirements List as of', sy-datum, sy-uzeit.
WRITE: / sy-uline(155).
WRITE: / 'Material:', p_matnr, ' Plant:', p_werks.
WRITE: / sy-uline(155).
SKIP 1.

" Display MRP configuration details if available
IF gs_mdkp IS NOT INITIAL.
WRITE: / 'MRP Controller:', gs_mdkp-dispo. " Person responsible
WRITE: / 'MRP Type:', gs_mdkp-dismm. " Planning strategy
WRITE: / 'Lot Size:', gs_mdkp-disls. " Lot sizing procedure
SKIP 1.
ENDIF.

"*------------------------------------------------------------------*
"* Step 5: Display Column Headers
"*------------------------------------------------------------------*
" Column positions are carefully aligned for readability
WRITE: / 'Date', " Date of MRP element
15 'MRP Element data', " Type of element (receipt/requirement)
45 'Doc Number', " Document number reference
70 'Receipt Qty', " Quantity of receipt
90 'Available Qty'. " Running available stock
WRITE: / sy-uline(155).

" Initialize running stock with opening balance
lv_running_stock = gv_available.

"*------------------------------------------------------------------*
"* Step 6: Display Opening Stock
"*------------------------------------------------------------------*
" Show current available stock as starting point
WRITE: / sy-datum USING EDIT MASK '__/______', " Today's date formatted
90 gv_available. " Opening stock quantity
WRITE: / sy-uline(155).

"*------------------------------------------------------------------*
"* Step 7: Process and Display MRP Elements
"*------------------------------------------------------------------*
" Loop through all MRP elements (receipts and requirements)
LOOP AT gt_mdpsx INTO gs_mdpsx.

" Get corresponding quantity data for this MRP element
" Match by date (dat00) and planning number (plumi)
READ TABLE gt_mdezx INTO gs_mdezx
WITH KEY dat00 = gs_mdpsx-dat00
plumi = gs_mdpsx-plumi.

IF sy-subrc = 0.

"*----------------------------------------------------------------*
"* Determine MRP Element Type Description
"*----------------------------------------------------------------*
" DELKZ field indicates whether element is receipt or requirement
CASE gs_mdpsx-delkz.
WHEN 'V'.
lv_txt = 'Receipt'. " Incoming material
WHEN 'B'.
lv_txt = 'Requirement'. " Outgoing material demand
WHEN 'L'.
lv_txt = 'Delivery Schedule'. " Scheduled delivery
WHEN 'A'.
lv_txt = 'Dependent Reqmt'. " From BOM explosion
WHEN 'U'.
lv_txt = 'Stock Transfer'. " Between storage locations
WHEN OTHERS.
lv_txt = gs_mdpsx-delkz. " Display code if unknown
ENDCASE.

"*----------------------------------------------------------------*
"* Calculate Running Available Stock
"*----------------------------------------------------------------*
" Receipts (+) increase stock, Requirements (-) decrease stock
IF gs_mdpsx-delkz = 'V'.
" Receipt: Add to available stock
lv_running_stock = lv_running_stock + gs_mdezx-mng03.
ELSE.
" Requirement: Subtract from available stock
lv_running_stock = lv_running_stock - gs_mdezx-mng02.
ENDIF.

"*----------------------------------------------------------------*
"* Display MRP Element Line
"*----------------------------------------------------------------*
" Show each element with aligned columns
WRITE: / gs_mdpsx-dat00 USING EDIT MASK '__/______', " Date formatted
15 lv_txt, " Element type description
45 gs_mdpsx-delnr, " Document number
70 gs_mdezx-mng03, " Receipt quantity
90 lv_running_stock. " Projected available stock

" Increment record counter
lv_count = lv_count + 1.

ENDIF.

ENDLOOP.

"*------------------------------------------------------------------*
"* Step 8: Display Summary Information
"*------------------------------------------------------------------*
WRITE: / sy-uline(155).
SKIP 1.

" Show total number of MRP elements processed
WRITE: / 'Total Records:', lv_count.
" Show current physical stock
WRITE: / 'Current Stock:', gv_labst.

" Display summary data count if available
IF gt_mdsux IS NOT INITIAL.
SKIP 2.
WRITE: / 'Summary Data Available - Total Entries:', lines( gt_mdsux ).
ENDIF.

*&---------------------------------------------------------------------*
*& END OF REPORT
*&---------------------------------------------------------------------*

Output for standard MD04 real stock view:

Output for custom Report output:

Conclusion :

This custom ABAP report demonstrates how standard SAP functionality like MD04 can be replicated and customized using clean ABAP logic and standard APIs. By leveraging MD_STOCK_REQUIREMENTS_LIST_API and combining it with stock data from MARD, the report provides a clear and reliable view of stock movements and future requirements.

From my experience, building such custom reports not only helps meet specific business requirements but also improves understanding of SAP’s internal MRP data flow. This approach offers flexibility for further enhancements such as ALV output, additional filters, or integration with planning dashboards, making it a practical alternative to standard transactions when customization is required.

Thanks for Reading My Blog..

ABAP Connectivity

SAP BTP ABAP environment .

Stop Treating SAP Patches Like Punishments - it's a gift

2025-12-24T08:00:57.339000+01:00

We need to talk about the collective groan that echoes through IT departments when the notification arrives: SAP Patch Tuesday is coming. For decades, in the on-premise world, patching was viewed as a necessary evil. It meant downtime, manual regression testing, late nights, and the terrifying possibility that fixing one thing might break ten others. The instinct became preservation through stagnation: "If it’s not broken, don't touch it and turn off the auto-updates."

But this mindset is a trap. In the modern digital landscape, treating your SAP landscape like a delicate museum piece isn't "safe." It’s a slow-motion disaster. We need a radical re-framing. Receiving a patch, an update, or a new feature drop isn't a threat; it’s a present. It is an injection of resilience, security or even a new capability. This isn't just a new cloud IT philosophy. It is a fundamental truth rooted in biology, echoed in mythology, and proven by the most robust systems on the planet. The lesson is simple: whatever remains static dies; whatever learns to adapt survives. Here is why we must stop fearing the patch and start embracing it.

The Lesson from Biology: The Immune System

Consider your own body. You don't exist in a sterile bubble; you exist in a hostile environment of constantly evolving bacteria and viruses. How does your body survive? Not by building a static stone wall around itself, but through a highly adaptive, rapid-response immune system. When your body encounters a new threat or receives a vaccine (a biological "patch")—it doesn't shut down. It learns. It updates its internal threat library. It develops antibodies specifically designed for that new reality.

The exposure to the "patch" makes the system stronger. If your immune system refused to update because it was "too risky," the first novel virus you encountered would be fatal. Your SAP environment is no different. A patch isn't an annoyance; it’s an antibody against a new security threat or a vitamin injection for better performance.

The Lesson from Mythology: The Power of Metamorphosis

Ancient myths understood that also and throughout Greek mythology, the ability to undergo metamorphosis is often the difference between life and death. When faced with an insurmountable threat, heroes and nymphs didn't stand still and brace for impact. They changed. Daphne transformed into a laurel tree to escape pursuit and the characters who refused to change, like Narcissus, paralyzed by his own static reflection, faded away.

In our world, the market, regulations, and competitors are constantly shifting. An SAP system that is "stuck in its ways" because we fear the update process is like a mythological figure refusing to shapeshift when danger approaches. The ability to rapidly intake new code is your primary mechanism for escape and survival.

The Lesson from IT: Embracing "Chaos"

For a long time, IT success meant "five nines" of uptime achieved by locking everything down. Then came the cloud giants, who realized that the only way to guarantee reliability at scale was to constantly break things.

Netflix famously developed "Chaos Monkey," a tool that randomly terminates instances in their production environment. Why on earth would they do that? They realized that if they feared failure, their system would become brittle. By constantly injecting small failures (forced changes), they forced their engineering teams to build systems that could automatically heal, reroute, and adapt instantly. They turned patching and redeployment from a terrifying manual event into everyday muscle memory. By automating the "pain," they eliminated the fear. They proved that a system in constant flux is infinitely more resilient than one that is static.

The SAP Cloud Reality: It's Time to Open the Present

Moving to SAP S/4HANA Cloud or utilizing BTP Services means accepting a fundamental shift in this philosophy. SAP is now delivering continuous innovation and security tightening on a schedule you can set your watch by. The temptation for many organizations migrating to the cloud is to bring their old on-premise anxieties with them, to find ways to delay, defer, or turn off these automated updates. They want the benefits of the cloud with the static comfort of 2005 but… Don't do it. When you turn off automated patching, you aren't "stabilizing" your system. You are voluntarily opting out of evolution. You are choosing to make your system dumber while the threats get smarter.

Every patch is an opportunity to validate that your automated testing (also with Int4 Suite) is working. Every deployment is a chance to prove your architecture is decoupled and resilient. Every update is a gift of new functionality that your business counterparts are desperate for. It’s biology. It’s mythology. Stop trying to preserve a statue. Start building a living organism that gets stronger every time it changes. Open the present.

Find out more:

SAP Learning course on Automated testing using APIs - Avoid SAP S/4HANA Project Delays with Third-Party Systems Service Virtualization

BAPI :FINDING AND TESTING

2026-01-21T07:23:42.177000+01:00

INTRODUCTION:

Functional consultants need to use bapi's when it is not possible to meet client requirements with standard screens.

This blogg is useful to give A general idea about finding bapi's and also to test them.

BAPI

BAPI(Business Application Programming Interface) is a business-level programming interface provided by SAP to execute standard business processes in a controlled and validated way.

In short they simulate the business logic behind the functional screens ,BAPI validate data before updating to tables so they reduce the risk of data corruption,

BAPI are used to connect sap system with non-sap system and also in developing custom screens to meet the business requirement

HOW TO FIND BAPI’S

Method:1

TCODE: BAPI

We can find bapis using bapi transaction and can search with respect to module.

Method2:

SE37

Search with *BAPI_* to find the bapi

Method3:

Just search in google or with ai.

IMPORTANT DETAILS REGARDING BAPI

1.Please read the bapi documentation clearly. Sometimes it will save lot of time

To find the documentation pass the bapi

Pass the bapi in se37 and click on display and then in new screen click on function module documentation

which fields are mandatory?

In se37 after executing the bapi we get screen as below

The screen has import parameters and tables.

To get clarity on mandatory fields.

Step1: read documentation it will sometimes have values related to import parameters.

Step2:

By following above path we can see if fields are optional or mandatory and can also see default values

Similarly we can check for tables. if there is no optional tickmark its mandatory to pass values in that field or table .

We can take reference from standard screens on what data to pass as bapi replicate business logic behind standard screens.

TESTING BAPI

For most of the bapis , bapi transaction commit also need to be passed for changes changes to reflect in system but there are few exceptions like BAPI_PRODORD_RELEASE where there is no need to commit.

After clicking on execute we are in first bapi

Pass the mandatory values

Then execute

Click on back button

Now we are in commit BAPI

Pass ‘X’ and execute

Click on back button again

RESULT:

Before executing BAPI

After executing BAPI

We can copy the test data to test data directory for future reference or to pass the test data to ABAP team.

To check the executed test data

Click on the record number we can check what data was passed.

CONCLUSION:

Please follow above steps for finding bapi's and also to test them.

Your 2026 Roadmap to Getting Started with ABAP AI and ABAP-1

2026-01-21T18:01:36.956000+01:00

The era of "Wait and See" for AI in ABAP development is officially over. With the general availability of Joule for Developers (J4D) and the planned availability of ABAP agentic AI frameworks in 2026, the question isn't if you should use AI, but where you should start.

The "Start Here" Recommendation: For 90% of developers, the best starting point is SAP Joule for Developers integrated within ABAP Development Tools (ADT) for Eclipse. In addition you can also experiment with the first versions of ABAP-1 model to analyze and explain code on your own - but be aware that this is currently not for code generation and only for those which want to be independent of J4D. Therefore starting with J4D is the fastest but also the most powerful way to start with ABAP AI.

Why should I start with Joule for Developers (J4D)?

Contextual Intelligence: Unlike generic LLMs, Joule for Developers is additionally trained on over 250 million lines of proprietary SAP code and is aware of your specific ABAP Cloud context. In general J2D is powered by a combination of third-party foundation models (e.g. OpenAI, Gemini, Anthropic, Mistral AI), alongside SAP-centric models like the LLMs, trained specifically on ABAP and purpose-built for cloud-based SAP development.
It’s Free (For Now): SAP has extended the free promotional period for Joule for Developers until September 2026.
Native Skills: It handles predictive code generation (e.g. RAP generation), "Explain" skills for legacy code, and unit test generation directly within your IDE. So it can do way more then ABAP-1 right now.
J4D is out of the box integrated in Eclipse ADT.

The Three Paths for ABAP AI Evolution:

1. The Standard Path: Joule for Developers in ADT

Best for: Daily coding, documentation, and unit testing.
Action: Request access through your administrator (Material 8019124 for customers and 8019541 for partners) and activate it in ADT.

2. The Innovation Path: ABAP AI SDK & BTP Free Tier

Best for: Building your own AI-powered business applications (e.g., automated invoice processing).
Action: Use the SAP BTP Free Tier to access the Generative AI Hub and the ABAP AI SDK to connect your custom ABAP code to external foundation models.

3. The Modernization Path: VS Code with ABAP Cloud (Roadmap Q2/2026)

Best for: Developers looking for a lightweight, file-based experience and for those which want to be the first to leverage agentic ABAP AI in side-by-side approach.
Action: Explore the new side-by-side ABAP Cloud Extension for VS Code (GA planned for Q2 2026) with built-in Agentic AI assistance powered by an ABAP MCP server. This will support a broader range of SAP S/4HANA Private Editions and provide faster update cycles.

Key Takeaway for 2026:
Don't get bogged down trying to "prompt engineer" experimental models like ABAP-1 for production code generation. Instead, leverage Joule for Developers mature "Explain" and "Generate" skills to maintain a Clean Core and accelerate your migration to SAP S/4HANA.

Here you can learn more:

More high-level insights about Joule for Developers/ABAP AI and ABAP platform can be found here . Here you find more on ABAP- 1,

Custom code migration to SAP S/4HANA powered by SAP Joule for Developers, ABAP AI capabilities

2026-02-18T14:23:51.235000+01:00

Custom code migration during system conversion to SAP S/4HANA Cloud Private Edition is usually complex and time-consuming process. The whole custom code developed in the SAP ECC systems since years must be assessed and analysed for SAP S/4HANA and finally adapted after system conversion.

Customers often face challenges to understand S/4HANA simplifications and their relation to the custom code due to scattered documentation across various channels like SAP simplification notes, SAP Help, blog posts. To find an answer to the specific SAP S/4HANA custom code migration question, one needs to go through multiple sources of information.

The IT project managers have a tough time to carry out the custom code migration projects on time and within budget because they experience difficulties during execution of their tasks like defining custom code migration scope, getting high-level understanding of custom code issues, creating effort estimations and project plans and finding the right development experts for adaptation. Ability to meet a decision whether to migrate custom code to S/4HANA or not assumes understanding of its business purpose which is quite challenging primarily due to the absence of documentation for legacy code. Custom Code Migration app on SAP BTP can execute custom code analysis for S/4HANA readiness, but S/4HANA comes along with more than 430 simplification items which affect custom code. Thus, to get at least a high-level understanding of issues reported by the Custom Code Migration app to assign appropriate work packages to custom code migration developers a project manager needs to deep dive into these lengthy simplification items and provided cookbooks, which is time- and effort-consuming activity.

Along with this custom code migration developers, who finally must adapt the code for S/4HANA need to understand the old legacy code in all details: not only the business logic, but also the technical processing flow which is quite tedious task due to missing documentation. ABAP test cockpit (ATC) in ABAP development tools for Eclipse can check custom code for S/4HANA readiness, but developers still invest high effort into studying related simplification items and cookbooks to understand the issues in detail. The ATC issues in custom code should be fixed ideally with a high automation rate, but the quick fixes provided for S/4HANA ATC issues in ABAP development tools for Eclipse can support about 40%-60% of the typical S/4HANA simplification use cases like conflicts with MATNR field extension or missing ORDER BY in SELECTs, the remaining ATC issues must be fixed manually by developers.

To support IT project managers and developers during custom code migration projects to speed up the analysis and adaptation tasks and enhance productivity the AI-based skills were delivered for custom code management tools within SAP Joule for Developers, ABAP AI capabilities. This will shorten the custom code migration projects timelines, reduce project risks and enhance capacity to meet deadlines and budget constraints.

Let’s look at them in detail.

AI-based custom code migration support for IT project managers

Starting with SAP BTP ABAP environment 2602 AI-based custom code analysis support for IT project managers is integrated in the Custom Code Migration app. To use it the SAP Joule for Developers, ABAP AI capabilities must be activated in your SAP BTP ABAP environment system. See the SAP note 3571857.

Understand legacy code in the AI-based Custom Code Migration app

You will get short and clear AI-based explanation of the code in the pop-up window, which will support your migration decision. Subsequently you can use Explain business purpose in detail and Explain processing logic in detail options to get more details to deepen the clarification.

Finally, you can use Scope part of the Custom Code Migration app to add or remove the object from scope based on your decision.

Understand S/4HANA ATC issues in the AI-based Custom Code Migration app

After execution of remote SAP S/4HANA readiness ATC check run over the custom code in the ECC system with the Custom Code Migration app in SAP BTP ABAP environment it is now possible under the Analyze Findings view to select an ATC issue in the Findings table and use ATC Explain capability to get an explanation of an S/4HANA related ATC finding. The explanation is provided in the pop-up window along with the proposed step-by-step resolution and contains also referenced S/4HANA simplification materials like simplification notes or cookbooks. Referenced documents are offered as clickable links within the AI-based response for navigation to further details.

This will enable you to grasp the root cause quickly without having to read through numerous SAP S/4HANA simplification information materials.

AI-based support for custom code migration developer in ABAP development tools for Eclipse

Starting with SAP S/4HANA Cloud Private Edition 2025 AI-based custom code analysis and adaptation support for developers is provided in ABAP development tools for Eclipse within SAP Joule for Developers, ABAP AI capabilities. To find out how to activate it see the blog post SAP Joule for Developers, ABAP AI capabilities for SAP S/4HANA Cloud Private Edition 2025.

NOTE: Code Explain for module pools and ABAP classes along with the deep dive explain (code in INCLUDEs and called methods outside of the source code object) will be delivered with SAP S/4HANA Cloud Private Edition 2025 FPS01.

Using Docs Chat for questions around custom code and S/4HANA simplifications

In most cases you as a custom code migration developer before starting with your adaptation activities first need to gain general understanding of S/4HANA simplifications related to your functional area of expertise to get an overview as well as deep dive into SAP standard changes relevant to your custom code.

Docs Chat capability utilizes SAP simplification notes, related technical information and SAP Help documentation to deliver based on this extensive input quick and accurate answers.

Select /docs topic in the Joule chat window and ask your question, for example “What are the data model changes in Sales and Distribution?”. Joule will list all technical changes along with affected objects including also reference links for further information. You can also ask follow- up questions for your query.

Now for example after finding out that VBUK and VBUP tables were eliminated in S/4HANA and knowing that this has direct impact on your custom code, you can ask Joule ”How can references to VBUK and VBUP be eliminated in my code?”. Joule will deliver short and concrete answer providing code proposals considering different use cases based on the information provided in the extensive cookbook about the VBUK and VBUP adaption.

Understanding of old legacy code

Generally, you as a custom code migration developer starting with your adaptation activities need to understand the old legacy code, which must be analysed and adapted for S/4HANA. Thereby you are confronted with the following problems: the code has been implemented many years ago, often expands over multiple pages, has very little or no documentation, the author of the code is not available any more for questions and so on. Thus you have a tedious and long-time task to digest this code to verify if it is still needed from the business perspective and understand it’s implementation logic for the adaptation.

The Explain for ABAP report and Explain for module pools as interactive Dynpro-based applications capabilities significantly speed up and make more accurate the task of understanding of old legacy code.

Just select an old ABAP report in the Project Explorer and use context menu Joule ->Explain. Joule will explain its business purpose and processing logic and will list all called objects. You can further deep dive into details using Explain business purpose in detail or/and Explain processing logic in detail features in the Joule chat window or ask Joule to explain called objects.

In the example below the business purpose of this custom ABAP program is to upload customer email addresses, which length exceeds 50 characters since the standard ABAP program cannot handle it, and this custom functionality will be still required in the S/4HANA system.

Therefore, you as developer can for example follow up on the details of processing logic to understand the program better for the upcoming adaptation.

You can also select the source code snippet in the editor and ask Joule to explain it:

Here is one example of the module pool explanation by Joule. In addition to the general overview and business purpose Joule describes user flow, which is very important for screen-based Dynpro applications to follow on the screen logic along with technical details for the processing logic of the screens (PBO/PAI) comprising deep-dive into INCLUDEs and Dynpro logic:

Understanding of S/4HANA related ATC findings

The basis for all custom code adaptation activities is the execution of S/4HANA readiness checks with ATC over custom code in your S/4HANA system in ABAP development tools for Eclipse. The ATC check result contains the list of S/4HANA incompatibility issues in custom code, which must be adapted, explaining the error and providing as a reference the link to the corresponding simplification information. The custom code migration developer needs to read through it to find out how to apply it to solve the error in the particular custom code object, which is time-consuming task.

The Explain ATC finding capability offers clear and short explanation of the S/4HANA related issue in custom code based on information provided in S/4HANA simplification items and cookbooks along with step-by-step recommendation on how to solve the issue.

After execution of the ATC check run with S/4HANA readiness check variant S4HANA_READINESS_2025 over your custom code the ATC findings are displayed in the ATC Problems View. In the Details of an ATC finding you see the description of the error, in this example “DB Operation found (KONV, see Note(s) 0002220005)” and the link to the related SAP simplification note 2220005, which must be examined to understand how to resolve this issue. Instead of doing this just select the ATC finding and use the context menu Joule->Explain.

Joule will deliver a crisp explanation telling you that the table KONV was replaced in S/4HANA with the table PRCD_ELEMENTS, which must be accessed using the new pricing result API. This explanation is based on the information provided within the cookbook about pricing conditions techniques attached to the related SAP simplification note 2220005. Joule can also provide step-by-step recommendations on how to fix the issue and can answer follow-up questions for further clarification. The referenced documents (related SAP simplification note in this example) are offered as clickable links within the Joule response for navigation to further details.

This will allow you to quickly grasp the root cause without having to read through numerous SAP S/4HANA simplification information materials.

Getting code proposal for adaptation of S/4HANA related issues

The final step for a custom code migration developer is to fix S/4HANA related ATC findings to adapt the code to S/4HANA.

The ATC findings which can be resolved using deterministic quick fixes are marked with the yellow light bulb in the ATC findings list. The resolution of the remaining findings must be done manually based on simplification information, which is quite laborious and time-demanding task.

The Code proposal capability allows you to fix the issue in custom code based on AI-based proposal emulating the same process as deterministic quick fixes and can be utilized for S/4HANA issues where deterministic quick fixes are not available.

After AI-based explanation of an ATC finding just click Generate Code Proposal in the Joule window

The AI-based code proposal is UI friendly: it can be generated either after explanation of the ATC finding (as suggested above) or from a source code line in the editor.

For generating code proposal from source editor just click on the ATC finding marker like this:

After Joule proposed the code change, you have different options. You can Copy the code proposal for pasting it into the editor later or Insert the code at the cursor position in the editor, or use Apply (recommended).

If selecting Apply, then in the same way as for deterministic quick fixes the Code Review Dialog will be shown displaying the original source code and the source code containing code proposal.

You as developer can review the code proposal and apply as needed. AI-based Code Proposal allows you to save the manual efforts and benefit from the semi-automated code adaptation as you already know it from the deterministic quick fixes.

Further information

Discover generative AI capabilities for ABAP custom code migration by watching the video: Unleash the power of GenAI for ABAP Custom Code Migration.

For more details about ABAP AI capabilities for custom code migration refer to the SAP Help Portal documentation Using Custom Code Migration AI assistant including also video tutorials.

How to resolve atc issues

2026-02-19T08:03:25.934000+01:00

Hi all
in this blog i have explained how to resolve ATC issues

Introduction:

ATC (ABAP Test Cockpit) issues in SAP are quality findings, errors, or warnings flagged during automated code analysis, identifying syntax errors, performance bottlenecks, security flaws, or deviations from best practices in custom ABAP code (Z-code). These issues are crucial for maintaining code quality,, especially during upgrades to S/4HANA.

ATC (ABAP Test Cockpit)

let's consider you are getting error in ZOL test system

step 1: run ATC CHECK

use SE80 -> search for object -> run ATC check
or
use checkman transaction -> select the object type and paste the object -> enter

step 2:

We need to check for same error in development system in my case EWE is the development system.

If the same checkman issue is coming up over there or not, if not then it has been fixed or exempted

then i checked there was no ATC error found

Step 3:

In my case no error found in EWE system, then that means error been fixed or exempted

Next -> check for exemption

To check -> ATC_SHOW_EXEMPTION -> click on execute -> after click on filter and search for object (as of now no hits found – that means no exemption was raised )

If no exemption – then has it be fixed

step-4

next we need to check if there were any changes being made against this object (yes in line number 10 they have added t- code but this was missing in ZOL)

Step-5

Then go ahead make the changes, try cross porting the changes through SCWB by finding the TR in EWE which had these changes

In ZOL system

enter t code SCWB -> click on Sap Note/ Request (pop up will get open)-> select source request -> paste the TR

to find that TR
open that object in EWE system -> utilities -> version->version management-> search for related description-> if you get select and click on display or details (check for details) -> if details are matched go back and copy the TR (in this case TR is ER1K8A55CZ)

step 6

enter t code SCWB ZOL system-> click on Sap Note/ Request (pop up will get open)-> select source request -> paste the TR-> copy the TR and paste and select right mark -> then you can see below screen

there select both rows and click on right mark -> then below screen you can see

here you need to paste TR (this TR we need to create for system ZOL in which i need to store changes which i have copied in EWE system)

this TR we need to create through corrective measure

step-8

select abap corr measures-> click on create->provide details(application component, description,software component,)-> create corrective measure->copy the workbench request

step-9
copy workbench request and paste in step 6

This solves your ATC issue

Conclusion :

in this blog i have explained how you can resolve ATC by cross porting the TR from the system where that code is working as expected that TR we are cross porting to system where it is not working (coping TR from working system and pasting in test system) in this way you can resolve your ATC issue or else by raising an exemption you can resolve it
in this ATC issue T Code was missing that we are cross ported from EWE system.