Classic BAdI vs New BAdI

Explanation

Classic BAdIs were introduced before the enhancement framework and are usually found through SE18 and implemented through SE19. New BAdIs are part of the enhancement framework and are integrated with enhancement spots. New BAdIs support better performance and advanced options such as filters and multiple implementations depending on design. In day-to-day work, consultants often maintain both types because older ECC processes may still use classic BAdIs, while newer frameworks and S/4HANA components rely on enhancement framework BAdIs. The important interview point is not only naming the difference, but explaining how to find, implement and debug them.

Code example

* Practical comparison notes:* Classic BAdI:* - Usually analyzed in SE18* - Implementation created in SE19* - Common in older ECC processes * New BAdI:* - Part of enhancement framework* - Often assigned to enhancement spot* - Supports filter and multiple implementation design * Interview-ready answer:* Do not only say old vs new.* Explain where you find it, how you implement it and how it runs.

Real project scenario

An ECC purchasing process may use a classic BAdI, while a newer S/4HANA process may provide a BAdI under an enhancement spot with filter-dependent implementations.

Common mistakes

- Only saying classic is old and new is new. - Not mentioning enhancement spots. - Not knowing SE18 and SE19 usage. - Not checking filter and multiple implementation behavior.

Best practices

- Check BAdI documentation in SE18. - Check enhancement spot for new BAdIs. - Understand filter and implementation type. - Debug runtime to verify actual implementation.

Interview angle

Interviewers expect a practical answer: classic BAdI is older, new BAdI belongs to enhancement framework, and both are analyzed/implemented with standard BAdI tools.