ERPClimb logoERPClimb

SAP ABAP BAdI Interview Questions

In SAP ABAP rounds, badi questions are where configuration knowledge meets day-to-day behaviour — what a setting does, and what breaks in a live system when it is wrong.

Master Business Add-Ins with classic BAdIs, new BAdIs, filters, multiple implementations, fallback classes, debugging and S/4HANA enhancement strategy.

This page carries 9 reviewed SAP ABAP badi interview questions, each with a complete written answer and no sign-in required. The set breaks down into 1 foundational, 3 mid-level and 5 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

Rehearse these out loud rather than reading them. If you can explain each answer in your own words, including one realistic way it goes wrong on a project, you are covering what a normal SAP ABAP round on badi expects.

Read the full guide: SAP BAdI and Enhancement Interview Questions

9 BAdI questions with answers

mediumBAdI

1. What is the difference between classic and new (Enhancement Framework) BAdIs?

Classic BAdIs (SE18/SE19) are single-use or multiple-use, based on interfaces and filter values, and are called via CL_EXITHANDLER=>GET_INSTANCE. New BAdIs are part of Enhancement Spots, support context-based filters, are called with GET BADI / CALL BADI, offer better performance (no cross-client lookup at every call) and support fallback classes.
mediumBAdI

2. A BAdI implementation is active but not getting triggered. What would you check?

I would check whether the correct business process is being executed, whether the BAdI is called in that process, whether the implementation is active, whether filter values match, whether multiple implementations exist and whether the breakpoint is placed in the correct method.
hardBAdI

3. How do you design a BAdI implementation for maintainability?

I keep the BAdI method small, use guard conditions, delegate business logic to a service class, avoid heavy database logic, use configuration where required, handle messages consistently and document the purpose. This keeps the implementation easier to debug, test and support.
hardBAdI

4. Why are released BAdIs important in S/4HANA clean-core strategy?

Released BAdIs are intentionally provided extension points and are generally more upgrade-safe than implicit source-code enhancements. In S/4HANA clean-core strategy, teams should prefer released extensibility options such as BAdIs, APIs, key-user extensibility, RAP/CDS extensions or side-by-side extensions before using risky source-code enhancements.
mediumBAdI

5. How do you find the correct BAdI to enhance a transaction?

Set an SE24 breakpoint on CL_EXITHANDLER=>GET_INSTANCE, run the transaction and observe which BAdIs are called. For new BAdIs, set a breakpoint on GET BADI/CALL BADI or search the transaction's package for enhancement spots in ADT.
easyBAdI

6. What is the difference between BAdI definition and BAdI implementation?

A BAdI definition defines the enhancement option and method interface. A BAdI implementation contains the actual custom logic written by the developer. SE18 is commonly used to view definitions and SE19 is used to create or manage implementations.
hardBAdI

7. BAdI slows down document save by 200 ms. What do you do?

Profile with SAT the exact call, remove any DB SELECT inside the loop, buffer master data at session start, batch DB reads with FOR ALL ENTRIES, and consider a background job if the logic is not strictly real-time.
hardBAdI

8. BAdI CHANGING parameter is not reflected in caller. Why?

New BAdIs pass parameters by value by default; declare parameters as CHANGING in the interface and confirm the standard code uses the returned values. If the standard reads a separate copy, you may need a different hook.
hardBAdI

9. How would you structure BAdI implementations for a large program?

Keep the BAdI implementation class thin — delegate immediately to a service class in a domain package. This isolates business rules from framework code and enables ABAP Unit tests independent of the BAdI runtime.

Related lesson

Filter-Dependent BAdIs

Related topics

Internal TablesOpen SQLABAP CoreEnhancementsDebuggingOOP ABAPIDocUser ExitsPerformance TuningWorkflowSmartForms

Next practice step

Practice with Interview AITake a mock test