SAP Enhancements & BAdIs Interview Questions Part2

Interviewers don't ask "what is a BAdI?" They ask what you did when it didn't trigger, why you chose that hook over the other three, and what happens to it at the next upgrade.

This 32-page PDF is built around those questions. Every one starts with a real project scenario, then gives you the question as an interviewer phrases it, a plain-language answer you can say out loud in about a minute, the trap that quietly exposes a memorised answer, and the follow-up that usually comes next.

What's inside — 30 questions in 6 blocks

• Fundamentals & strategy — enhancement vs modification, choosing between four techniques that would all work, user exit vs customer exit, upgrade impact (SPDD, SPAU, SPAU_ENH), an enhancement that killed performance, clean core in S/4HANA
• Implicit & explicit — point vs section, enhancement spots, where implicit points actually live, replacing SAP logic when only a point exists, implementation types
• Customer exits — function, menu and screen exits end to end, transports that work in DEV but not QA, exits that fire five times
• Classic BAdIs — architecture and the adapter class, filter-dependent BAdIs, raising an error that actually stops the save, the "it's never called" checklist, multiple use
• New / kernel BAdIs — GET BADI / CALL BADI, fallback classes, filters that silently exclude you