Accenture SAP ABAP Developer Interview Questions 2026: 30 Questions with Answers

Accenture is one of the largest SAP partners in the world, and in India that means a steady stream of ABAP openings: freshers trained into ABAP under the Custom Software Engineering Associate title, and experienced developers hired directly for S/4HANA implementations and migrations. The technical round is run by people who write ABAP for a living, so the questions are concrete: which internal table type, why FOR ALL ENTRIES misbehaves, how exactly you implement a BADI. This page explains the 2026 process and gives 30 questions with sample answers for freshers and developers up to about five years.

How the Accenture SAP ABAP process works in 2026

As of September 2026, candidate reports on Glassdoor and 2026 interview guides describe three steps.

Step 1: online assessment. On HackerEarth or Accenture's own portal. Logical reasoning, basic programming and sometimes domain questions. For fresher ABAP tracks the programming questions are language-agnostic; for experienced roles some drives skip this step.

Step 2: technical interview, 45 to 60 minutes. A senior SAP developer or architect covers ABAP fundamentals, Data Dictionary, internal tables, reports, enhancements, forms, performance tuning and debugging, then S/4HANA concepts: CDS views, AMDP and code pushdown. Reported questions include how to implement an exit and a BADI, and how you will prepare for AI-assisted ABAP development. For experienced candidates the project walkthrough takes a third of the time.

Step 3: HR interview. Background, motivation, location and shift flexibility, notice period and compensation.

Levels. Freshers and candidates with up to two years are hired as Custom Software Engineering Associate or Analyst on the SAP ABAP track; experienced developers come in at Senior Analyst and above with role-specific postings.

Difficulty and timeline. Glassdoor's aggregate for Accenture SAP ABAP Developer interviews shows 3.1 out of 5 for difficulty, 53 percent positive experiences, and an average of about 14 days to hire.

Compensation. Not published on the job posts and dependent on level, city and SAP experience. Confirm the level in your offer and compare it for that level.

What the Accenture ABAP interviewer is testing

• Fundamentals with reasons. Not "what is a sorted table" but "why would you pick it here".
• Performance instinct. Nested SELECTs, FOR ALL ENTRIES traps, hashed-table lookups, index use.
• Enhancement craft. Exits, BADIs, enhancement spots: how to find them and how to implement them.
• S/4HANA readiness. Code pushdown, CDS, AMDP, and what breaks in a migration.
• Debugging and support. How you find the cause of a wrong value in a production report.
• Team and client fit. Working with functional consultants, documenting, and following transport discipline.

30 Accenture SAP ABAP interview questions with sample answers

ABAP basics and Data Dictionary

1. What is the ABAP Data Dictionary, and what are domains, data elements and structures?

"The Data Dictionary (SE11) is the central metadata repository. A domain defines technical attributes: type, length, value range. A data element adds semantics: field labels, documentation, search help, and references a domain. A structure groups fields without database storage; a transparent table is a structure with a database table behind it. Reusing domains and data elements keeps field behaviour consistent across tables and screens."

2. Transparent, pooled and cluster tables. Which exist in S/4HANA?

"A transparent table maps one to one to a database table. Pooled and cluster tables stored several logical tables inside one physical table and were used for customising and text data. In S/4HANA on HANA, pooled and cluster tables are converted to transparent tables, which is one of the migration checks."

3. What is the difference between a check table and a value table?

"A check table is assigned at the foreign-key level of a table field and enforces referential integrity at input time. A value table is defined on the domain and only proposes itself as the check table when a foreign key is created; on its own it enforces nothing. Interviewers ask this because candidates often assume the value table validates data."

4. Explain the types of ABAP reports and when you use ALV.

"Classical reports write a list; interactive reports allow drill-down through secondary lists and AT LINE-SELECTION. ALV (SAP List Viewer) gives sorting, filtering, totals and export for free. In 2026 I write ALV with CL_SALV_TABLE for simple cases and CL_GUI_ALV_GRID when I need editable grids or custom events, and I keep data selection separate from display."

5. What is a modularisation technique, and how do subroutines, function modules and methods differ?

"Modularisation splits a program into reusable units. Subroutines (FORM) are local and obsolete in new code. Function modules live in function groups, can be remote-enabled (RFC) and have typed interfaces; BAPIs are function modules with a business interface. Methods belong to classes, support object orientation and are what new development should use. I write classes and expose function modules only when RFC is needed."

6. What are SY-SUBRC, SY-TABIX and SY-DBCNT?

"SY-SUBRC is the return code of the last statement; zero means success and I check it after every SELECT, READ TABLE and function call. SY-TABIX is the index of the current or last-read internal table row. SY-DBCNT is the number of rows affected by the last database operation. Not checking SY-SUBRC is the most common bug in fresher code."

Internal tables and performance

7. Standard, sorted and hashed internal tables: when do you use each?

"Standard: index access and appends, linear search on keys, fine for small tables or sequential processing. Sorted: kept sorted by key, binary search on key reads, O(log n), supports partial key access; good for large tables read by key and sequential range processing. Hashed: O(1) key access, unique keys only, no index access; best for large lookup tables accessed by full key. For a 500,000-row material master lookup I would use a hashed table."

8. What goes wrong with SELECT ... FOR ALL ENTRIES, and how do you write it safely?

"Three things. If the driver table is empty, the WHERE clause is dropped and you select the whole table, so I always check the driver table first. Duplicate driver entries produce duplicate selections, so I sort and delete adjacent duplicates. The result set removes duplicate rows, so I must select the full key. I would also mention that a JOIN is usually better when both tables are database tables, and FOR ALL ENTRIES is for an internal-table driver."

9. Why is SELECT inside a LOOP bad, and what do you do instead?

"It fires one database round trip per iteration; a loop of 10,000 rows becomes 10,000 queries. Instead, select all needed rows in one statement into an internal table using a join or FOR ALL ENTRIES, then READ TABLE with a binary search or a hashed table inside the loop. I would show the before-and-after in the ABAP runtime analysis (SAT) if asked for proof."

10. What are field symbols, and how are they different from work areas?

"A field symbol is a pointer-like reference to an existing data object. LOOP AT itab ASSIGNING <fs> lets me modify the table row in place without the copy-back a work area needs, which is faster on wide rows. Field symbols also allow dynamic programming with ASSIGN COMPONENT. Risk: using an unassigned field symbol dumps, so I check IS ASSIGNED."

11. How do you find the cause of a slow custom report?

"Runtime analysis with SAT or the ABAP Profiler to see whether time is in the database or ABAP. SQL trace (ST05) for expensive statements and missing index use. Then fix the usual suspects: SELECT * replaced with a field list, nested SELECTs replaced with joins, standard tables searched linearly replaced with sorted or hashed, and unnecessary SORTs removed. Finally check whether logic can be pushed to the database with a CDS view."

12. Explain the difference between READ TABLE with BINARY SEARCH and a hashed table read.

"Binary search on a sorted standard table is O(log n) and requires the table to be sorted by the key used; forgetting to sort returns wrong results silently. A hashed table read is O(1) but only with the full unique key. For repeated lookups with the full key I use hashed; for partial keys or range processing, sorted."

13. What is the difference between MODIFY, UPDATE and INSERT on a database table, and what does COMMIT WORK do?

"INSERT adds a row and fails if the key exists; UPDATE changes existing rows and fails if none; MODIFY inserts or updates. COMMIT WORK ends the database logical unit of work and makes changes permanent; ROLLBACK WORK discards them. In update-task processing, I bundle changes in CALL FUNCTION ... IN UPDATE TASK and commit once, so a partial failure rolls back consistently."

Enhancements, interfaces and forms

14. Walk me through implementing a user exit.

"Find the exit: SMOD for the enhancement, or search CMOD by package or transaction. Create a project in CMOD, assign the enhancement, activate the components. Open the function exit and create the include ZX... inside it, write the logic, activate, and activate the project. Test by debugging with a breakpoint in the include. I would mention that user exits are single-implementation, unlike BADIs."

15. How do you implement a BADI, classic and new?

"Find the BADI definition: SE18, or set a breakpoint in CL_EXITHANDLER=>GET_INSTANCE (classic) or GET_BADI (kernel BADI) and run the transaction. Classic: create an implementation in SE19, implement the interface methods, activate. New enhancement-framework BADI: create an enhancement implementation in an enhancement spot, add a BADI implementation with filter values if required, implement the class, activate. Kernel BADIs support multiple implementations and filters and are faster."

16. What are enhancement spots, implicit and explicit enhancements?

"The enhancement framework lets you add code to standard objects without modification. Explicit enhancement points and sections are placed by SAP in standard code; implicit enhancement options exist automatically at the start and end of includes, methods, function modules and forms, and at the end of structures. I use them only when no BADI or exit exists, and I document them because they are hard to find during upgrades."

17. BAPI versus RFC versus IDoc: when do you use each?

"A BAPI is a standardised, released business interface implemented as an RFC-enabled function module; use it for synchronous business operations like creating a sales order. RFC is the underlying protocol for calling function modules remotely. IDocs are asynchronous document-based messaging for EDI and system-to-system integration with reprocessing and monitoring (WE02, BD87). I choose IDoc for asynchronous, high-volume or partner integrations and BAPI for synchronous calls."

18. Smart Forms versus Adobe Forms, and how do you attach a custom form to a standard output?

"Smart Forms are the older SAP form tool with a graphical editor and a generated function module; Adobe Forms use the Adobe Document Server and are the S/4HANA standard for new forms. To attach, I create the form and a driver program, then configure the output type in NACE (or the output management in S/4HANA BRF+) to call my driver program and form routine."

19. What is an ALV with an editable field, and how do you capture changes?

"CL_GUI_ALV_GRID with the field catalog setting EDIT = 'X' for the column. Register the edit event, and handle DATA_CHANGED or DATA_CHANGED_FINISHED to validate and process the modified cells. I keep validation in a separate method so it can be unit tested with ABAP Unit."

20. Explain a change you made through a transport request from development to production.

Describe the path: development, unit test, release, import to quality, functional test, import to production during a change window. Mention the checks: ATC or Code Inspector, dependency order of transports, and what you did when a transport failed in quality. Accenture panels use this to check whether you understand delivery discipline, not only syntax.

S/4HANA and modern ABAP

21. What is code pushdown, and why does it matter on HANA?

"Moving data-intensive logic from the application server to the HANA database, where column store and parallel processing make aggregations and joins fast. The old pattern was 'data to code': select everything, process in ABAP. On HANA it is 'code to data': use CDS views, AMDP and Open SQL features like aggregations and joins so less data travels to the application server."

22. What is a CDS view, and how is it different from a database view in SE11?

"A CDS view is defined in a DDL source with annotations, supports joins, associations, aggregations, calculated fields, parameters and access control (DCL), and can be exposed as an OData service for Fiori. An SE11 database view is a plain projection or join with no annotations, no parameters and no associations. In S/4HANA I build read models as CDS views and consume them from ABAP or Fiori."

23. What is AMDP, and when do you use it instead of a CDS view?

"ABAP Managed Database Procedures let me write SQLScript inside an ABAP class method that runs on HANA. I use AMDP when logic needs procedural steps, loops or intermediate results that a single CDS view cannot express, such as complex pricing recalculations. CDS first, AMDP when CDS is not enough."

24. What breaks in custom code during an ECC to S/4HANA migration?

"Table changes: KONV to PRCD_ELEMENTS, MATNR length 18 to 40, VBUK and VBUP status tables merged into VBAK and VBAP, and pooled or cluster tables becoming transparent. Removed transactions and function modules. Code that relied on implicit sort order of SELECTs breaks on HANA. I would run the custom code migration app or ATC with the S/4HANA checks and fix findings by priority."

25. How will you prepare for AI-assisted ABAP development? (a reported Accenture question)

Be practical. "I already use assistants for generating boilerplate, test cases and explaining unfamiliar standard code, and I review every suggestion against the Data Dictionary and performance rules. The value shifts to knowing the business process, choosing the right enhancement, and validating output. I would keep my S/4HANA and CDS skills current, because the assistant is only as useful as the person checking it."

Scenario and HR

26. A production report shows wrong totals for one company code. How do you debug it?

"Reproduce with the same selection in quality. Set a breakpoint after data selection and compare internal table contents with the database for that company code. Check currency conversion and unit handling first, because most 'wrong totals' are those. Check recent transports touching the report or its CDS view. Once found, fix in development, add a test case, and transport through the normal path with the change documented."

27. A functional consultant gives you a spec that is technically impossible as written. What do you do?

"Explain what is impossible and why, in business terms, and offer the closest achievable option with its trade-off. Get the revised requirement in writing. I would not build something different silently, and I would not just say no."

28. Explain your current SAP project in three minutes.

Client industry, modules, whether ECC or S/4HANA, your objects (reports, enhancements, interfaces, forms), one hard problem you solved, and the transport and testing process. Practise it aloud; experienced ABAP interviews are decided largely on this answer.

29. Why Accenture for SAP?

"The scale of S/4HANA programmes, exposure to greenfield and brownfield migrations, and the chance to work on modern ABAP: CDS, RAP and Fiori rather than only supporting legacy code. I want to be where the migration work is happening."

30. What is your notice period and expected CTC?

State facts: notice days, negotiability, buyout. For CTC, ask for the level and band first, then give a range. Keep this consistent with anything you told the technical panel.

Mistakes that get ABAP candidates rejected at Accenture

• Not checking SY-SUBRC in any code you write on the whiteboard.
• Defending SELECT inside LOOP or FOR ALL ENTRIES without the empty-table check.
• Only classic ABAP. Zero vocabulary on CDS, AMDP or code pushdown fails a 2026 S/4HANA panel.
• "I have done enhancements" with no steps. Panels ask you to walk through an exit or BADI.
• No transport discipline story. Accenture delivers to clients; process matters.
• A vague notice period in HR.

How to practise the Accenture SAP ABAP round

The ABAP technical round is a spoken exam on reasons: why this table type, why this enhancement, what breaks on HANA. Candidates who have said the answers aloud, with someone pushing back, do better than those who have read the same material twice.

In MockMate Practice, attach your resume and paste the Accenture SAP ABAP job description, choose a technical round and run an adaptive session in the browser. The interviewer persona asks about your objects and project, follows up on performance and enhancement answers the way a senior ABAPer does, and can ask you to write a snippet in the built-in editor. The report shows each answer, response timing, coaching evidence and recurring weaknesses, with a recommended next practice. Eligible accounts get three free Practice starts of up to ten minutes each as of September 2026. Use MockMate Live assistance only in interviews or meetings where the organisation or interviewer permits it; Accenture selection rounds do not, so stay with Practice for this interview.

A one-week plan: two days on internal tables and performance spoken aloud with reasons; one day rehearsing exit, BADI and enhancement-spot steps; one day on CDS, AMDP and migration checks; one day narrating your project; then a Practice round, a report read, and a second round on the weakest group. For the broader process see the Accenture hub, and for the manager conversation the Accenture managerial round page.