Recreating event handler due to significant changes

[Former Member]

Hi,

May I know, when we will expect message  "Recreating event handler due to significant changes". in the application log and reason behind the same.

Also All the expected and unexpected events are triggered as a subsequent task in this process

Regards,

Ratnakar

[Former Member · Accepted solution]

Ratnakar,

Generally, when you make any changes on the application document and if those changes are directly/indirectly impact Expected Events or critical parameters, system will try to re-create the EH ( means it will re-create Expected Events, updates the parameters, and re-processes the existing events again) but will not create a new EH.

If you want to avoid this, implement BADI /SAPTRX/BADI_EH_S~CHECK_FOR_CHANGES. If you have TM, check the implementation /SAPTRX/GEN_EH_S_IMPL for this method.

If not let me know and I can guide you on the logic.

Thanks,

Vishnu

[Former Member · Accepted solution]

Thanks Gopi and Vishnu..

Hi Vishnu,

The scenario explained by you seems appropriate in our case.

Can you please elaborate the process , how to put the check...and whether it will cause any performance issue.

Regards,

Ratnakar

[Former Member · Accepted solution]

Hi Ratnakar,

Is your scenario, TM Objects or ERP objects?

If you are tracking ERP transactions, simply check UPDKZ = 'I' in your AO Type relevance ( EKPO-UPDKZ, VBAP-UPDKZ

I prefer the BADI though:

The following is the code from standard implementation provided by SAP which you can use in your ZBADI implementation for any AO Type ( TM, ERP or anywhere ).

From the screen, just replace it with your AO_TYPE

Thanks,

Vishnu

[Former Member · Accepted solution]

Hi,

Thanks Vishnu.. Its RDS OTC Process

Regards,

Ratnakr

[Former Member · Accepted solution]

Hi Ratnakar,

Vishnu is right. To avoid the recreation of existing event handlers you should implement BAdI method /SAPTRX/BADI_EH_S~CHECK_FOR_CHANGES.

If you bypass the recreation, this should not have a negative impact on the performance: Since recreation of EHs and the reporcessing of the related event messages is avoided, it should have positive impact on the performance.

But, of course, you will loose the functionality that event messages are reprocessed if the expected events have changed for an EH.

Best regards, Daniel

[Former Member]

Hi Ratnakar,

1. If you change Source System ApplicatioN ID then it creates a new event handler.

2. The system uses the application object type (AOT) together with the application object ID (AO ID) and the name of the application system to define the unique reference between application object and event handler.  If any of changes then it will create a new event handler.

3. Application system use the event type together with tracking ID to assign the event to even handler.  If any of the thing changes, then it create a new event handler.

4. Tracking ID code set change, it creates a new event handler.

Regards

GGOPII

[Former Member]

Hi Ratna,

Did you find the solution?

Regards

GGOPII