Solution : https://service.sap.com/sap/support/notes/1521903 (SAP Service marketplace login required)
Summary :
Some BAdI implementations in SAP systems may not execute as expected, despite being active. This issue primarily affects Kernel BAdIs on SAP_BASIS version 701 and above, necessitated by discrepancies between the runtime and design-time BAdI tables, potentially after upgrades or support package installations. The noted inconsistencies likely stem from errors in enhancement spot generation. Resolution involves applying the fix from SAP Note 1548839 and executing the report ‘ENHS_BADI_ANALYZE_GENERATE_ALL’ to regenerate inconsistent BAdIs, ensuring alignment with the original BAdI definitions. For details or further action, BADI_RSANALYZE can be used for individual BAdI checks.
Key words :
-migrated badis arenot affected, design-time tables, design time repository, individual badi definition, check meta data, terms badi generation, applying sap note 1548839, enhancement spot generation, generate inconsistent badis, check runtime data
Related Notes :
| 1589303 | Runtime data of deleted badis remains in the system |
| 1549751 | Enh. Implementation ENHO_SEU_BADI_IMPLS is inconsistent |
| 1548839 | Transport of Enhancement Spots cause BAdI impl. to be lost |
| 1522742 | Excise details are not updated during GR in MIGO - EHP4 |
| 1461985 | Enhancements of interfaces for object assignment |
| 822379 | Known problems with Support Packages in SAP NW 7.0x AS ABAP |