2023 Apr 25 9:22 AM
I implemented a BADI ZME_PROCESS_PO_CUST. in DEV system it is working properly but after transporting to QAS the BADI is not called. when I check in SXC_EXIT table there is already implemented BADI but different name ZMM_PROCESS_PO_CUST and different code.I tried to put a break-point for these two but both of these badi is not called.
why the implemented badi is not called both is already active . is it because the ZMM_PROCESS_PO_CUST is already implemented ? if yes but why in dev system, the implemented badi is working?
the only objects i have in DEV System
class -> ZCL_IM_ME_PROCESS_PO_CUST
Enhancement Implementation -> ZME_PROCESS_PO_CUST
Business Add Ins -> ZME_PROCESS_PO_CUST
2023 Apr 25 9:28 AM
ZME_PROCESS_PO_CUST is an own developed BADI so we can't give you specific help. You need to check its definition and implementation in QAS and DEV. E.g. is it defined as a multiple use BADI?
2023 Apr 25 9:55 AM
Since this is a custom BAdI, I am not sure what customizations your system has. Some generic things to check.
1) Check if the transport has moved correctly to QAS. Also, check whether all the customizing transports have moved too.
2) Check the properties(Regarding multiple use ) / implementation is active or not in SE18.
3) Put a breakpoint at CL_EXITHANDLER and GET BADI to check whether your BAdI is getting triggered.
2023 Apr 25 10:01 AM
2023 Apr 25 10:50 AM
about the Multiple Use check box , I tried but changing it is not allowed after transport
i know i can change it if i unrelease the transport and delete the object in the transport using RDDIT076 then create new transport but i am not allowed to unrelease the transport
do you know other ways to change it to multiple use?
btw thanks for the answer
2023 Apr 25 11:00 AM
2023 Apr 27 11:22 AM
Changing the BADI definition into multiple use is a SAP modification that is not preferred and most IT teams do not allow.
You might create a customer BADI definition and set multiple use. Then create a single SAP BADI implementation that does call the customer BADI definition that allow multiple implementation. More easy would be to merge the 2 existing BADI implementations into a single one.
2023 Apr 27 2:18 PM
jack.graus2 A custom multiple use BADI seems the best solution in my view.
2023 Apr 27 2:27 PM
Why matthew.billingham? I'm not much used to those things, but if the standard one is not multi, why to create a custom one? If it's because readability, you just must (you will do it anyways) to cut your implementation in pieces and call them the same way you'd call multiple implementations.
What am I missing?
2023 Apr 27 3:57 PM
vicen.lozano The advantage is that you decouple the implementations from the main BADI and each other. If you want another implementation, you can just add it, without changing the main BADI or anything else.
2023 Apr 27 4:07 PM
But you need to mess with a standard SAP thing... I don't like it. If the BAdI was "multi", then I'd go for multiple implementations, but for a standard single one... not sure.
Anyways, thanks for the answer, mate.
2023 Apr 25 9:59 AM
2023 Apr 25 10:43 AM
yes the badi definition is ME_PROCESS_PO_CUST and the badi implementation name is ZMM_PROCESS_PO_CUST
2023 Apr 25 10:59 AM
ZMM_PROCESS_PO_CUST and ZME_PROCESS_PO_CUST is the implementation name
2023 Apr 25 11:21 AM
The BAdI ME_PROCESS_PO_CUST doesn't allow multiple use, check its definition with SE18 (the box Multiple Use is not checked)
2023 Apr 25 11:48 AM
bolivs22 Did you see Matthew question? Please answer. Hopefully Raymond has checked for you.