Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

ME2N : BADI ME_CHANGE_OUTTAB_CUS does not work for multiple implemantations

0 Kudos

We currently upgraded to EHP7 and post upgrade the BADI that we had implemented (the Z*XXX) is not called any longer. The runtime behaviour states "A non-default implementation will be called instead". The SAP implementation FMFG_OUTTAB_USKEY is called instead. Hence our custom logic and custom fields have stopped working. Please suggest how to get the custom implementation to work ?

1 REPLY 1

JL23
Active Contributor
0 Kudos

This sounds very strange, this BAdI just came with EHP4

and it is "designed for multiple use." as you can read in KBA 2455462 - How to enhance purchasing reports with new fields/change standard logic?

Did you activate other BAdIs or implements add-ons together with this upgrade which could eventually have a side-effect to your implementation?

As you can directly tie this error to the upgrade I would recommend to open a call at SAP Support