BAdI
Business Add-In
An enhancement spot defined by SAP where custom ABAP logic plugs into a standard process without modifying SAP code.
SAP defines BAdIs at points where customers may add their own logic, for example to fill a custom field or to influence a determination. The implementation is custom code; the interface belongs to SAP.
In SAP S/4HANA Cloud, key users implement released Cloud BAdIs in the Custom Logic app. Because the logic lives outside the standard, it has to be re-validated after every upgrade.
In ERP Preflight
Custom Field Flow Doctor reports propagation steps that need a Cloud BAdI implementation that does not exist; FormDoctor reports form fields that are declared by the form interface but only a BAdI could populate.
Problems that involve BAdI
- MajorField declared by the form interface but not populated
- MajorRequired Cloud BAdI implementation missing
- MajorLegacy object needs a cloud extension
- CriticalRequirement implies a Clean Core violation (tier 11)
- MajorBusiness change without the expected change pointer (expected vs observed)
- CriticalBound field absent from runtime XML
- CriticalRequested field cannot be supplied to the form
- CriticalLegacy SAPscript detected
Related terms
Free tools
- Knowledge & error search
Search the reviewed knowledge base, SAP objects and the finding codes of the analysis engines.
Background articles
- Custom fields with key user extensibility: why a field does not appear in the app, form or APIHow custom fields created with key user extensibility reach UIs, reports, forms and APIs, and why a field that exists on one document is missing on the follow-on document.
Written for ERP Preflight · reviewed September 27, 2026
All glossary termsERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.