Standard BADI Implemeantation is not listed in SPRO badi implemenation list for deactivation

[Karthik_Gali]

Dear Community,

For few BADI's, SAP has created implementations for testing purposes. These implementations are not called as they are dependent on activation of the business function. However, we cannot create our custom implementations, as these BADI's are not enabled for 'Multiple Use' and they use the same filter values which we have to use for our custom implementation.

So far, for other BADI's , I have deactivated the standard implementations from SPRO, but for a particular BADI, the standard implementations are not listed in SPRO implementation list.

Can someone please explain, what is the actual technical configuration which lists the implementations in SPRO and what is the way forward to go ahead to deactivate these standards implementations?

In these cases, is it suggested to raise a ticket with SAP (or) simply use the access key and deactivate from SE19 ?

Thanks in advance!

Regards,

Karthik

[RAF]

Please provide an example

[Karthik_Gali]

The BADI: HRPIQ00AD_STATUS has the following standard implementations, you can see these implementations are not active.

The below screenshot is from SPRO, where none of the above implementations are listed except for one custom implementation which uses other filter.

[RAF]

Hi,

these are implementations from a switch.

You would have to modify for example the BADI defintion to Multiple Use.

[Karthik_Gali]

Thanks for reply Robert!

Yes, these are switch implementations. Either deactivating the standard implementations or enabling the Multiple-use both require an access key. I would like to know, whether it is recommended to raise an issue with SAP to deactivate these implementations as they were created only for test purposes (or) customer should modify using the access key? as when customer modifies it takes additional efforts during upgrades, which we would like to avoid.

Moreover, enabling multiple use still does not work in our case, as we have to make use of the same filters used for the standard default implementations.

[RAF]

Hi Karthik,

if you plan to go for a modification you and you are on enterprise support you can trigger the modification justification check

https://launchpad.support.sap.com/#/notes/1281532

[Sandra_Rossi]

If SAP defined explicitly an implementation as "not switchable via SPRO" (look at the properties of the implementations), then it's clearly to say that the clients shouldn't deactivate it.

Maybe you can discuss with SAP if you really feel it's an error (how do you know they did it "for testing purposes"), but if your reason is just for adding your own implementation SAP probably won't accept.

So better go for any possibility of enhancement, whatever it's via a modification key or via the enhancement framework, it depends on your exact case.

[Karthik_Gali]

Thanks for the reply Sandra!

You have precisely answered almost everything. If possible, could you please clarify the below questions, as it helps to complete the dicussion.

1) The property 'Active' not switchable in customizing(IMG)' is not selected/checked for all the implementations delivered in this enhancement spot in question. Therefore, I assume that clients are allowed to deactivate it, could you please confirm? as this property text or the F1 help documentation of this property is not clear. If my understanding regarding this property is correct, these changes in SPRO can be overwritten during system upgrades?

2)In extension to the above question, for one of the implementation, the property 'Active' not switchable in customizing(IMG)' is not selected/checked and at the same time, this is not listed in SPRO. What is the actual technical configuration which lists the implementations in SPRO? I have compared with other implementations but could not find any difference.

The reason I mentioned they might have been created for test purpose is that, as per the documentation of the application in question, these BADI's have been delivered for the customer use, as the functionalities vary and are specific from customer to customer. Moreover, most of these BADI implementations are named as a test and also the code inside does not make suit the customer implementations.

[Sandra_Rossi]

Karthik Gali

1) If 'Active' not switchable in customizing(IMG)' is checked, then the BAdI implementation will not be shown in SPRO.

2) if you are talking about those *active* implementations (i.e. not assigned to a switch, or assigned to an active switch), then I don't know why they are not proposed in your IMG activity. Note that if it displays only one implementation, maybe the activity refers only to this implementation (I don't know if the "switch" flag applies in that case), instead of "all" implementations of a given BAdI definition.

PS: thank you for the explanation about "testing" (I feel it's more "examples"), so it's worth asking SAP support - please revert back if you get an explanation. By the way, are you sure they have not been developed by SAP consulting services for your company only? (then you should have a SAP specific support so that they remove them)