Optimal number of control and info parameters on event handler

[Former Member]

Hello Guru’s

We have integrated TM and EM for FO tracking, in few scenarios FO can have more than 200+ FU’s assigned to it.

We are using “ODT20_ASSIGNED_FU” control parameter to hold assigned FU’s information on EH, is it good to have more than 250+ control parameters on a EH? Is there any suggestion on optimal number of control and info parameters on event hanlder.

We also have FU’s as tracking ID’s on FO.

Thanks in Advance,

Vishwa.

[Former Member]

Hi Vishwanath,

Having so many parameters definitely will add to the performance, not just from parameters angle but from number of event handlers created as you said 1 FO can have more than 200+FUs. Best way to avoid performance issue is to having a good archiving and/or deletion plan as soon as you are done tracking like last event or expected event is posted.

Regarding number of parameters on EH, we had lot of parameters ( serial numbers ) in one of our project and we split them into control and info parameters to make it lean. This will depend on your situation/desing on when and how you are using these parameters like Ruleset/preprocessing/UI which typically impact the performance.

Thanks,

Vishnu

[Former Member]

Hi Vishwanath,

first of all you should only extract those parameters which you really need for your process (either for processing or for displaying). If you need to extract all the parameters for assigned FUs, you should ensure that you set the "Disable Loading of EH Data for Processing of Event Messages" flags in your EH type - otherwise the processing of event messages can get significantly slower. Of course, if you are using rule set activities which rely on having the control parameter data available, the performance of those will be impacted, because then the EH Control Parameter data needs to be loaded.

Apart from that it is a question (as Vishnu already stated) of how much disk space you have - this then should be regarded in the archiving strategy.

Best regards, Daniel