Skip to Content

This blog belongs to a series of blogs regrouped on the SCN page “SAP PLM Recipe Development for Beginners”.



With SAP PLM Recipe Development the following mass change tools are available:


Let’s now also take a quick look at the EHS Easy Expert.

With the EH&S Easy Expert you can create sets of rules directly in the SAP system. With these sets of rules, you can easily make mass changes to data in specifications that are stored in the EHS specification database.


EHS Expert is basically a calculation engine where you can design and apply certain rule sets which can change certain value in the property tree of your specifications in the EHS specification database.



This is quite common in the area of EHS where you can use the so called “Secondary Data Determination. For the creation of MSDS (Material Data Safety Sheets) a lot of information needs to be maintained in the various chapters of the property three of a specification. With the “Secondary Data Determination” it is possible that some of the data in some of the chapters in the property tree is automatically derived from other data already existing in the property tree. To do this, you need to make use of the so called “rule sets” which do this job for you.


EHS Easy Expert.jpg



This is great you will say and ask if you can also use these functions for Recipe Development related specification mass changes.


The answer is yes and no.

Yes: If you are experienced with EHS and if you know how to work with the EHS Easy Expert, then you might consider this toll also for Recipe Development related mass changes.  Especially during the data migration phase of an implementation project (technically experience EHS consultants) can leverage this tool for required mass changes in specifications.

No: If you are a business user without much technical knowledge, I would not recommend trying to use this rather technical tool. Recipe Development business users usually only work in the WEB-UI. As you can see from the screenshot above, this tool is however triggered from SAP-GUI transaction CG02.

Please also take a look at those links and check the service marketplace for more information on SAP component “EHS-BD-TLS-EXP”:

SAP Help – EHS Easy Expert Mass Changes

SAP Help – Sample Set of Rules for EH&S Easy Expert

SAP Help – How the EHS Expert Works

SAP Help – Creating Set of Rules with EH&S Easy Expert

SCN document – SAP EHS Management for Beginners

SCN document – Rule Sets / Secondary Data Determination

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Christoph Bergemann

    Hello

    fantastic document. Thanks for sharing this valuable informaiotn

    C.B.

    PS: only one question: is teh rereally somebody out there and using the “Easy Expert” as it is?? For me: it does note “really” add value.

    (0) 
  2. Luk Declerck

    Hi Christophe,

    I used the tool in a number of circumstances.

    In my first encounter With EH&S, the implentation of the solution was done by SAP. We did not have the need to “calculate” data since all data was either purchased externally or entered manually (Limited amount of data). Hense, Expert server was not considered. For simple mass updates on the other hand, Easy Expert was introduced.

     

    In my second major EHS Project, secondary data was calculated using a 3rd party solution. For basic mass changes however (e.g. mass change of a single value in a characteristic), Easy Expert was used. This works very well for the super users.

     

    The 3rd time I used Easy Expert was again for a Client where we did not require any complex rules. Standard Composition Calculation we developed ourselves as a menu extension. Again for simple updates, we installed an easy expert server. Given that the super users are highly skilled, they actually managed to set up rather complex rules in combinations with queries

     

    Red line in all Three cases was the Level of skills for the users and a safe approach. build a rule in a test system, test it on a realistic set of data, replicate in production. Reason for this safe approach was an experience were the data got messed up big time.

    (0) 

Leave a Reply