BAdi not getting called after applying CRM7.0 ehp1

[jeannet_berrones]

Hi experts,

We applied EHP1 to our Sandbox system and now Badi: CRM_MKTPL_OL_OBJ is randomly getting called.

I went to se18 enter the enhancement spot and once i enter the Badi Implementation I can see under

Runtime Behavior that the implementation is active. However the description in Effect in Current Client says:Execution depends on runtime filter values

While in our other client in which we havent applied EHP1 the Effect in Current client: Implementation is called

I know that is just the description but I am not sure if somthing has changed with EHP1

For both clients the implementation is active, but in the client in which we applied EHP1 the Badi is not getting called where expected.

Does anyone please have any suggestions.

your help is appreciated.

thanks,

Jeannet.

[CarstenKasper · Accepted solution]

Hi Jeannet,

probably have a look at the filter values in the BAdI implementation as well. It says it has got filters. Maybe the BAdI is only activated for Campaigns but not Elements?

If that does not bring the conclusion do a where used list on the interface for the BAdI. It will bring you to the place where it is called in ABAP and you see the direct cause why it sometimes is called or not.

I implemented the mentioned BAdI on CRM 6 as well as 7 and 7.1 had no problems I can remember so far.

cheers Carsten

[jeannet_berrones · Accepted solution]

Hi Carsten,

Thanks for you reply. The Badi has a filter 'CPG' is implemented for Campaigns. The Badi is not getting called when updating attributes of the Campaign and where it should be getting called, so all attributes in the Header area are blank out.

I noticed the description in the 'Runtime Description' is different in our sandbox(EHP1 applied) and DEV although filters are set in both systems.

I don't know what could be causing the issue. I have submitted an OSS note to SAP.

thanks,

Jeannet.

[Former Member]

HI Jeannet,

Good day..!

There may be a change in the sap standard runtime behavior for this badi. I guess SAP support must solve it then.

Cheers, Satish

[Former Member]

Hello,

We are encountering the same issue after upgrading from 6.0 to EPH1. Where there are BAdi's are active but the implementaions are not getting called.

After inactivate and activate again, then we have seen them it is getting called. Looks like there is a behaviour change EPH1 and anybody got any response from SAP on this issue.

I would appreciate, if you can share the details.

Regards,

Prasad