Skip to Content

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.


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    Posted on Oct 25, 2019 at 09:34 AM

    Here is the answer given by "Former Member" on Nov 27, 2013 (Mikael):

    • Hello Sandra and all others,
    • This is an old posting (4 years now) but still it helped me and I think I have a solution.
    • In my case I worked with BADI - CL_PT_ARQ_REQ and I created an implementation of my own that
    • I could not activate since it was blocked by SAP original that was active. You have to deactivate the original one via IMG (trx SPRO). (You can not do it via SE19 since a key is needed.)
    • Regards Mikael
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 11, 2008 at 09:40 AM

    Hi there.

    I undestand your point. But you don't need to deactivate standard BADI to create a new one. Just create a Z badi definition (copy from standatd definition) and then create you implementation.

    For details on BADI, check this link,


    Valter Oliveira.

    Add a comment
    10|10000 characters needed characters exceeded

    • Thanks Valter, but my question was about deactivating standard BAdI implementations. For exemple SAP provides an implementation (named FM_BADI_FDCB_BAS) to BADI_FDCB_SUBBAS01 and this BAdI does not allow "multiple use". My question is about deactivating implementation FM_BADI_FDCB_BAS, not about deactivating BADI_FDCB_SUBBAS01.

  • Posted on Jun 11, 2008 at 10:36 AM

    To all,

    if there is no sap documentation, please just tell me how you usually proceed, did you experience re-engineering of custom BAdI implementations (on standard BAdIs where you had to deactivate standard implementation) during upgrades, or you had never to re-engineer?


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 25, 2009 at 03:44 PM

    My conclusion : if possible, I prefer to implement implicit enhancement options at the beginning of the standard implementation, rather than deactivating a standard implementation. For BAdIs like BADI_FDCB_SUBBAS0* (they are used to add custom subscreens to standard screens of a few applications), I must do a compromise by using the last available BADI_FDCB_SUBBAS0* (number 05), and hope it is not used by SAP in the future.

    I didn't find any SAP recommendation about that.

    Add a comment
    10|10000 characters needed characters exceeded