badi-enhancement

To create an ABAP BAdI, define an enhancement spot, create the BAdI interface, implement the BAdI, and optionally add a fallback class for default behavior to extend SAP standard processes without modifying core code.

A fallback class in ABAP enhancement spots provides default behavior for a BAdI when no active implementation is found. You need it to ensure standard process continuity if custom BAdI implementations are not registered or active.

Yes, BAdIs and enhancement spots can be applied across ABAP Cloud, RAP, and traditional ABAP environments. This allows you to extend SAP standard functionality using both new BAdI patterns and classic BAdI frameworks.

New framework BAdIs use enhancement spots and definitions for clean separation of concerns, while classic BAdIs use older explicit enhancement points. Both extend SAP standard functionality but differ in architecture and cloud readiness.

Key user extensibility works alongside ABAP BAdIs by allowing users to add custom logic, fields, and CDS views through guided patterns. This enables SAP standard extensions without deep developer intervention or core code modifications.

You should use enhancement spots instead of modifying SAP standard code to maintain clean separation of concerns and ensure upgrade safety. This framework allows custom BAdI logic to hook into standard processes without altering the core application.