Multiple use BADI benefit
Can you please tell me a scenario where multiple active implementation of a BADI is absolutely necessary? For example, we have a BADI ME_PURCHDOC_POSTED which is multiple-use. But why do we need this as multi-use, is there any functionality that we would have missed if it was a single implementation BADI?
Yes, you are right, but probably you did not get my comment. For "Multiple use" you have the flexibility to switch off/on any implementation you want and when you need, but for single use as you have stated you just cannot do that.
For "Multiple use" you have the option to trigger either A, B, C or A,B or B,C, or A,C or A,B,C,
so 3! = 6 combination possible.
For "Single use"
Only one you have the option to run Either A or B or C. So 3 combination possible.
For more implementation the difference will increase. And as per me I would be happy with more combination here rather than making changes in code to have more combinations which I have explained already.
But there are some restriction SAP has put in case of some BADIs to purposefully make them "Single use" to put the onus on the customer.
Sometimes you might have noticed that there are implementation created by SAP . Since the Normal BADIs are owned by SAP, they want to control how we use SAPs code. Along with SAP's code ( "Multile Use" ) or Ignore SAP's code to apply your own code ( "Single use " ). It is something like switch.
It is all about option. Either way it will work but as I explained there are other aspects behind it.
Hope it makes sense now.