Critical Issue in Production - BADI Runtime behaviour

[Former Member]

Dear Users,

Apologies for the alert in the Subject.

We have a critical production issue after applying Enhancement Packs version 4. We use a BADI WORKORDER_UPDATE with multiple implementations for our bespoke updates. However, we have discovered that on applying the EHP4 in production, the Implementation's Runtime Behaviour got changed to "The implementation will not be called".

The surprising thing is it's Runtime Behaviour in Development and QA environments which says "The implementation will be called".

Could someone please guide me through this?

Thanks,

Vijay

[Former Member]

Hi

Have you tried to active it again?

Max

[Former Member]

Buon Giorno!! Thanks for the quick reply Max.

I cannot activate it in the production system. What I don't understand is the reason behind it being active in Dev and QA environments and inactive in production. We haven't transported anything related to this object during the EHP4 implementation either!

[Former Member]

Hi

I suppose both enviroments DEV and QA was upgrated to EHP 4, so u can create a new transport for that object in order to active it in production.

It's very hard to say what happens while upgrading the system, I can suppose the different behavior is because the systems are not the same, there are some differences....but I don't know which is process you've followed for upgrade.

Max

[Former Member]

Grazie Max !!!

I have reactivated the BADI and transported it into production. It works.