i am working on an OH implementation, and when running the EHSSERV - Edit Overview of Medical Services transaction, it populates with every medical service that was created in the system. After it populates, then you can select a filter vaule. Has anyone used this transaction for a period of time? Have you experienced long run times or performance issues when running this transaction before you are allowed to set filter values?
Thank you very much for your feedback. My concern is that the project is still in design phase and will be implemented at a company where there is 10,000+ employees. If every employee has at least one medical service entered, at a minimum, you are looking at 10,000+ records returned when executing the EHSSERV transaction for the first time. Most employees will have more than one medical service entered. This is my first implementation of OH and was looking for feedback based on experience with the initial execution of EHSSERV.
Also, thank you for letting me know where to post, as I wasn't sure. I will be closing this thread and reposting the question in EH&S.
Have never observed any performance issue with Medical Services even after putting on filter. Of course you can have issues on first run, did you try filtering later ? Are you getting run time error or there is issue with performance only ?
Further, please post OH related queries in Environment, Health & Safety (EH&S) forum, it has been separated lately from PLM forum for all EHS related issues.