Showing posts with label ABAP Interview. Show all posts
Showing posts with label ABAP Interview. Show all posts

Tuesday, 17 November 2026

ABAP Cloud interview questions and answers: clean core and released APIs (2026)

Updated: 17 November 2026. Every SAP fact below was checked on SAP Learning, help.sap.com, SAP News, SAP's GitHub and ASUG that day.

Illustrated hero: an interviewer and an ABAP developer face each other across a table. The interviewer asks 'Is this API released?' and the developer answers 'Check the API State: C1, released for cloud development'. Fact chips read 3 ABAP language versions, 5 release contracts C0 to C4, 4 clean core levels A to D, and C_ABAPD exam facts: 3 hours and a 67% pass score.

ABAP interviews in 2026 test whether you can write code that survives upgrades. Expect questions on ABAP Cloud, the three ABAP language versions, release contracts C0 to C4, how to find a released API, and SAP's clean core levels A to D.

We wrote ten practice questions on these topics, with model answers built from SAP's own documentation, so you can check each one and say it in your own words. Classic topics such as internal tables, debugging and performance are not repeated here.

Why do ABAP interviews now ask about clean core and released APIs?

Interviewers ask because ABAP Cloud limits developers to released APIs, and SAP now rates every extension on a clean core scale. A developer who ignores both writes code that blocks upgrades.

The ABAP Cloud definition in the ABAP Keyword Documentation lists four limits: the language version is ABAP for Cloud Development, access to other repository objects is limited to released APIs, only ABAP Development Tools for Eclipse (ADT) can be used with no SAP GUI, and the transactional model is the ABAP RESTful Application Programming Model (RAP). The same entry says ABAP Cloud is fully or partly mandatory in SAP Business Technology Platform (SAP BTP), ABAP environment, SAP S/4HANA Cloud Public Edition and SAP S/4HANA Cloud Private Edition.

Sonja LiƩnard, Senior Vice President and Head of ABAP Platform at SAP, said in an SAP News interview on 18 August 2026: "ABAP Cloud is at the center, as the modern, clean-core variant of our language for long-term stability." The same interview says ABAP development has also been possible in Visual Studio Code since Q2 2026, initially for ABAP Cloud development, next to Eclipse.

Question 1: Is ABAP Cloud the same as the SAP BTP ABAP environment?

No. ABAP Cloud is a development model, and the SAP BTP ABAP environment is one place where you can run it. You can also use ABAP Cloud on SAP S/4HANA on-premise and in both SAP S/4HANA Cloud editions.

This mix-up is common enough that SAP's product lead addresses it directly. Fabian Fellhauer, Product Lead for ABAP Cloud and RAP at SAP SE, told ASUG in an interview published on 1 May 2025: "What I want to emphasize is that ABAP Cloud is not an environment." He added: "But ABAP Cloud is the development model to build cloud-ready applications."

A strong answer adds one practical point. On the ABAP platform of SAP S/4HANA on-premise, the ABAP Cloud entry says it is available next to classic ABAP, so one system can hold both kinds of code.

Question 2: What are the three ABAP language versions?

The three versions are Standard ABAP, ABAP for Cloud Development and ABAP for Key Users. Each program carries one of them as a property, and the version decides which statements and repository objects the program may use.

The ABAP language versions page gives the details in one table. The short version:

Language version Version ID What it allows
Standard ABAP X The full language scope of classic ABAP
ABAP for Cloud Development 5 A restricted set of statements, access only to released APIs, the strictest ABAP SQL check, client isolation enforced
ABAP for Key Users 2 Restricted ABAP for key users who implement SAP-provided enhancement options

A good follow-up remark: in ABAP for Cloud Development "most developments can be implemented in methods only", so the stricter syntax rules of classes apply automatically.

Two panels. Left: the three ABAP language versions, Standard ABAP (version ID X), ABAP for Cloud Development (ID 5) and ABAP for Key Users (ID 2), with what each allows. Right: the five release contracts C0 extend, C1 use system-internally, C2 use as remote API, C3 manage configuration content, C4 use in AMDP.

Question 3: What makes an API "released", and what do C0 to C4 mean?

A released API needs two things: a release contract that governs how SAP may change it, and visibility for a restricted language version such as ABAP for Cloud Development.

That two-part rule comes from the released API glossary entry. The release contract entry lists five contracts:

Contract Name in the docs What it guarantees
C0 Release Enhancement fields can be added at specified extension options
C1 Use system-internally A stable interface for use inside the ABAP application server
C2 Use as remote API A stable interface for use outside the ABAP application server
C3 Manage configuration content A stable persistence for configuration content
C4 Use in ABAP-Managed Database Procedures (AMDP) A stable interface of AMDP methods for use in other AMDP methods

If you can only remember one, remember C1. It is the contract on almost everything you call from ABAP Cloud code.

Question 4: How do you check whether an object is released?

Open the object in ADT, go to the Properties view and select API State. It shows the release contract and whether the object is released for cloud development.

SAP's own ABAP Cloud cheat sheet on GitHub walks through this with the class CL_ABAP_RANDOM_INT, which shows contract C1. The same cheat sheet names three more routes, and a strong answer mentions at least two:

  1. Released Objects tree. In the ADT Project Explorer, the Released Objects node lists what you may use.
  2. SAP Business Accelerator Hub. SAP Learning's lesson "Exploring Released APIs" says it shows remote APIs, events, Core Data Services (CDS) views, RAP business object interfaces and Business Add-Ins (BAdIs).
  3. The Cloudification Repository. SAP's Cloudification Repository on GitHub holds the released APIs of SAP Cloud ERP in one JSON file, plus objects that are not released with their successor objects. The ABAP Test Cockpit (ATC) check "Usage of Released APIs (Cloudification Repository)" reads that file.

The third route matters for SAP S/4HANA projects where code still runs as classic ABAP. You can scan it with ATC before you move it.

Question 5: What happens if you read table T005 in ABAP Cloud?

You get a syntax error, because table T005 (countries) is not released. The error names the released replacement, CDS view I_COUNTRY, so the fix takes one line.

SAP Learning uses this exact example in its lesson on exploring released APIs. The message it shows is:

The use of table T005 is not permitted. Use CDS Entity I_COUNTRY instead.

Here is the worked example we use for practice. Put the statements in a class method such as if_oo_adt_classrun~main, because ABAP for Cloud Development code runs in methods. The first statement fails; the second one is the released route:

" Fails: T005 is not a released API
SELECT FROM t005 FIELDS * INTO TABLE @DATA(countries_raw).

" Works: I_COUNTRY is released with contract C1
SELECT FROM i_country FIELDS * INTO TABLE @DATA(countries).

A natural follow-up is the system date. The cheat sheet marks sy-datum and sy-uzeit as fields that should not be used in ABAP for Cloud Development. SAP's released classes cheat sheet uses cl_abap_context_info=>get_system_date( ) instead, which returns the date in UTC:

DATA(today_utc) = cl_abap_context_info=>get_system_date( ).

Say "UTC" out loud in the interview. It is easy to assume it returns the user's local date.

Question 6: What are SAP's clean core levels A to D?

The clean core levels rate an extension by how upgrade-safe it is. Level A uses only released, stable interfaces; Level D uses techniques SAP does not recommend, such as modifications.

SAP described the four levels in an SAP News article on 12 August 2025 by Rudolf Hois, senior vice president and chief product owner of Cloud ERP Private at SAP; Priyadarsana Panda, senior vice president and general manager of Cloud ERP Solution Area at SAP; and Steffen Pietsch, vice president and head of SAP BTP Product Management at SAP. They wrote: "SAP has evolved its original three-tier model into the clean core level concept". The article defines the levels as follows:

Level Name in SAP's article What it covers
A Extend with SAP Build Only publicly released, stable SAP interfaces with formal stability contracts
B Leverage classic APIs Level A plus SAP's classic APIs and technologies
C Accesses internal objects Partly compliant; accesses SAP internal objects
D Not recommended extensions Modifications, write access to SAP tables, implicit enhancements

The change shows up in the tools too. In the released API list of the ABAP Keyword Documentation, the ATC check variant ABAP_CLOUD_DEVELOPMENT_3TIER is marked Deprecated, with ABAP_CLEAN_CORE_DEVELOPMENT as its successor.

Ladder of SAP's clean core levels, from A (fully compliant) to D (not clean): Level A uses only publicly released, stable interfaces; Level B adds classic APIs; Level C accesses SAP internal objects; Level D is not clean, with modifications, write access to SAP tables or implicit enhancements.

Question 7: How many released APIs are there, and what does "deprecated" mean?

There is no fixed number, because the list grows with every release. On 17 November 2026 we counted 7,196 rows in the released API list of the ABAP Keyword Documentation; 245 of them were marked Deprecated.

The released API list shows every released object of the documentation system with its contract, its visibility and its state. Our count of that page:

What we counted Rows
All rows 7,196
Contract C1 7,063
Contract C2 61
Contract C3 59
Contract C0 13
Visible for ABAP for Cloud Development 6,607
Visible for ABAP for Key Users 1,895
State Released 6,951
State Deprecated 245 (45 name a successor)

Deprecated means the object should no longer be used in new code; the list names a successor when one exists (45 of the 245). One example from unit testing: the unit test class CL_AUNIT_ASSERT is deprecated, and its successor is CL_ABAP_UNIT_ASSERT. In an interview, the right answer is "switch to the successor in the next change, and let ATC find the rest".

Bar chart of our count of the released API list in the ABAP Keyword Documentation on 17 November 2026: 7,196 rows, of which C1 7,063, C2 61, C3 59 and C0 13; 6,951 released and 245 deprecated.

Question 8: Which programming model and tools does ABAP Cloud use?

ABAP Cloud uses RAP as its transactional model and ADT as its development tool, with no SAP GUI. Data models are built with CDS view entities, and services are exposed through the Open Data Protocol (OData).

Expect a hands-on follow-up such as walk me through a RAP business object. The short answer is: table, root CDS view entity, behaviour definition, behaviour pool, service definition and service binding. If you want to practise that order end to end, our walkthrough of the smallest RAP business object builds one from an empty package.

Question 9: Where is ABAP Cloud mandatory, and where is it optional?

ABAP Cloud is fully or partly mandatory in the SAP BTP ABAP environment and in both SAP S/4HANA Cloud editions. On SAP S/4HANA on-premise it is available next to classic ABAP, so the team decides.

A good answer then explains the trade-off. Code written in ABAP Cloud on-premise is ready to move to a cloud edition later, while classic code may need rework first. Fabian Fellhauer, SAP's product lead for ABAP Cloud and RAP, made the same point to ASUG: the core business processes that should keep receiving innovations should be migrated toward ABAP Cloud, even on systems that do not run in the cloud yet.

Question 10: A business user wants a new field on a standard table. What do you propose?

Propose a released extension point first, not a modification. A C0-released object lets you add enhancement fields at its extension options, which keeps the extension on a released, contract-backed interface: the Level A end of SAP's clean core scale.

Then show the order of options. Check whether the business object offers a C0-released extension option. If it does not, ask whether a custom table linked by key, or a side-by-side app on SAP BTP, solves the need. A modification of the SAP table is the Level D answer, and you should say why you avoid it: it is the kind of change that makes upgrades expensive.

How do interviewers tell a weak answer from a strong one?

A strong answer names the rule, the source and one real object. A weak answer repeats a slogan such as "clean core means no custom code", which SAP's own level model contradicts.

We wrote this scorecard for practice. Score yourself on each row before an interview:

Question Weak answer Strong answer
ABAP Cloud vs BTP ABAP environment "They are the same thing" Model vs environment; ABAP Cloud also runs on S/4HANA on-premise
Released API "An API SAP published" Release contract plus visibility for a language version; C1 for local use
Reading T005 "Use a SELECT" Syntax error; use released CDS view I_COUNTRY
Clean core "No custom code" Levels A to D; aim for A, explain why D blocks upgrades
System date "sy-datum" cl_abap_context_info=>get_system_date( ), returns UTC
Scorecard comparing a weak and a strong interview answer for four ABAP Cloud questions: ABAP Cloud versus the BTP ABAP environment, released APIs, reading table T005, and clean core levels.

How should you prepare for these questions in five days?

Spend five short sessions in a real ABAP Cloud system rather than reading. Each day, open one object type, check its API State, and say the answer to one or two questions out loud in under a minute.

  1. Day 1. Questions 1 and 2. Read the ABAP Cloud and language version entries once, then explain them without notes.
  2. Day 2. Questions 3 and 4. Open three classes and three CDS views in ADT and note each API State.
  3. Day 3. Question 5. Write the T005 and I_COUNTRY statements yourself and read the error.
  4. Day 4. Questions 6, 7 and 10. Sort five extensions you have built into levels A to D.
  5. Day 5. Questions 8 and 9, then a mock interview with a colleague using the scorecard.

If you are also planning SAP's certification, the same skills carry over. The C_ABAPD certification page lists SAP Certified - Backend Developer - ABAP Cloud (Beta Version) as a 3-hour System-Based Assessment (SyBA) with one activity and a 67% pass score. Its topics are Using ABAP and Building Data Models (61%), Designing Effective Object-Oriented Code (21-30%) and Applying Basic Techniques and Concepts (11-20%). For the classic interview themes this post skips, such as internal tables, debugging and behavioural questions, ERPPrep's ABAP interview guide covers six themes.

Frequently Asked Questions

Q: What are the most common SAP ABAP interview questions for experienced developers in 2026?

Expect questions on ABAP Cloud, released APIs, release contracts, clean core levels and RAP. Expect scenario questions too, such as how to add a field to a standard object without a modification.

Q: Do I need SAP BTP experience to answer ABAP Cloud interview questions?

No. ABAP Cloud is a development model that also runs on SAP S/4HANA on-premise next to classic ABAP. Any system where you can create ABAP Cloud objects in ADT is enough practice.

Q: Do interviewers still ask about SAP's three-tier extensibility model?

Prepare for both terms. SAP moved from the three-tier model to clean core levels A to D in August 2025. Learn the levels first, and know that the matching ATC check variant is now ABAP_CLEAN_CORE_DEVELOPMENT.

Q: Which release contract matters most for ABAP developers?

C1, "use system-internally". Almost every object you call from ABAP Cloud code carries it. C0 matters for extensions, and C2 for remote APIs.

Q: Where can I see the full list of released ABAP APIs?

Use the Released Objects tree in ADT, SAP Business Accelerator Hub, or SAP's Cloudification Repository on GitHub. The ABAP Keyword Documentation also lists the released objects of its own system.

Q: Does the C_ABAPD certification test these topics?

SAP's page says C_ABAPD validates RAP skills and the use of Joule for developers, in a 3-hour System-Based Assessment (SyBA). Released APIs are part of everyday ABAP Cloud work in that system, so this practice helps.

More ABAP Cloud notes are on the SAP ABAP Central homepage.