How to evaluate SAP S/4HANA BAdIs and user exits
Enhancement points should be evaluated as part of a controlled extension strategy, not as a quick technical shortcut. A BAdI or user exit can be the right place for validation, enrichment or process-specific branching, but it can also create hidden behavior that is hard to test after upgrades.
The search should be used to identify the enhancement name, area, implementation context and call location. From there, the team should inspect whether the enhancement is released, whether it is called before or after database update, and which business object state is available at that point.
For GTS and S/4HANA projects, document the business reason for every enhancement. Include trigger condition, expected input, expected output, fallback behavior, test cases and owner. That documentation is often more valuable than the implementation code during audits and upgrades.