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,

Vishnu, Daniel and Gopi thank you for your valuable suggestions.

Vishnu:

Sure, we will consider moving the parameters evenly across control and Info parameters.

Regarding Archiving still we have not considered archiving option which will be on-boarded soon, suggestion is Archiving should be considered after go-live after observing data growth as a separate project.

Daniel:

Sure I will consider "Disable Loading of EH Data for Processing of Event Messages" on EH type after few basic cross-checks.

Thank you for your suggestion.

Gopi:

In my case, we are not going more than 200+ parameters, but, one of the parameter "Assigned freight units" can have more than 200+ values on FO event handler.

Yes, we are using EM web UI for reporting events - and we have not gone beyond 15 parameters (columns) on EM web UI display

My only concern is more than 200+ parameter values for assigned FUs.

Regards,

Vishwa.

[Former Member]

Hi Viswa,

1. We suggested earlier, yes it will have impact the system performance.  Do one thing, do the prototype in development for one of parameter which you said.  Send 200+ values for 10 FO event handler at same time and calculate the time how long it takes.

Take that calculation and calculate with your production peak data hours how many FO event handlers create and update in an hour to check performance side.

2. I know many organizations do not have archiving strategy and they are keeping more than 5 years data and  billions of transactions in system and they are just increasing the hardware inside.

If you think the FU update lesser than 10000 per day then you may go ahead with 200+ values for one of parameter update.

Check the calculation per day volume and let us know.  Let's precisely address this what would be the impact current and future.

I have see some project loads 2 million of data without any issue but has lesser parameter value on parameters.

Regards

GGOPII

[Former Member]

Hi Vishwa,

Additionally,

You can separate the parameters based on the your Ruleset, WEBUI. What I mean is see if you can put all the parameters which are used in ruleset in Control parameters, WEBUI selection screen in System Parameters and WEBUI display parameters in the INFO. This way you are segregating the parameters on need basis which will help in your system performance.

There maybe few parameters which might be applicable for both Ruleset and WEBUI though and you can decide where to put it based on how many you have in Control and Info.

Thanks,

Vishnu

[Former Member]

Hi Vishwa,

As of now I never come across restriction in 250 + control parameters and info parameters.  One of the project, when we thought about control parameters to load then we moved most of the key fields to we crossed more than 300 control parameters, however other than performance.  You have to think about SAP EM Web UI performance on control parameters if you client view data through WebUI too.

SAP EM WebUI not strong enough to hold more than 50 columns to retrieve data and you get round symbol and takes more time to retrieve data.  If you don't use SAP EM WebUI then well enough.

As you know, control and info parameters are different data records those are in  data container and used Parameter name and value string and index method.  So, it will impact the performance even you have a robust system in place to address.  If data volume increases over the period, then each FU loading time takes extra bit time and updating 250+ fields consumes more and more memory, CPU and disk space.

Best approaches:

1. You can move most of key fields to System parameter if those are not holding multiple values in it.

2. Check with client what are the important fields require for business to load data (most of clients not using 70% data which they requested initially in the project)

Regards

GGOPII

[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