Skip to Content
Jun 11, 2008 at 09:25 AM

Can really deactivate standard badi implementations? precautions/procedure?


Hi everybody,

sometimes, I have to create a custom BAdI implementation, but the BAdI already contains a standard implementation and it does not allow multiple implementations.

I read some sap documentation specific to particular applications, where I found SAP says precisely that we can "deactivate these BAdIs, but not these other ones".

If SAP does not give clearly this information that we can deactivate standard implementations, does it mean we can't deactivate?

Especially, I think of sap releases that would make this standard BAdI implementation mandatory in the future (who knows). If I deactivate some standard BAdI implementations, I am afraid that in the future, I have to change the way I implemented my custom code (use another BAdI, or implicit enhancement points, etc.) This is not how I understood the BAdI concept, where SAP officially reserved BAdIs to customers, and they are of course portable (ascendant compatibility).

For example, how can I know if I can deactivate standard implementation of BADI_FDCB_SUBBAS01 to make my own implementation? (if you know this BAdI, don't propose me to use BADI_FDCB_SUBBAS04 which is not used by sap yet, because who knows if they won't use it in the future!)

Do you know where I can find some general information about deactivating standard BAdI implementations? (sap notes, sap library, etc.)

Thank you very much for all your advice.