Introduction
EHS Classic allows lot of options to manage data. We have data elements like
- identifier
- Specification header
- Specific topics as Reference / Inheritance
- Component type / exception values
- Phrase based characteristics
- Regulatory LIst based characteristics
- Other types of characteristics
and much more
Depending on you starting point: there are some rules you should use to avoid a crash of your data model.
Assumption is now: you use 3E / SAP Standard model
Hints of topics to avoid
- For phrase based characteristic: do not add customer specific phrases to the phrase set; only if you are sure that the characteristic is not used by a 3E rule set: you should do a mix of 3E and customer specific phrases
- Do not add e.g. own compontent types / exception values or own Regulatory lists as long as you now: what is 3E Standard and what is the reason to add something new
- Do never manipulate SAP EHS classes/characteristics
- If needed: always "copy" the SAP class to a customer specific one
- Keep in mind the VERY important topic of "Unit of Measurement"; if you are not taking care here: you will get a mess
- You should only carefully adapt the 3E original WWI templates to your need and you should have a good documentation what was changed and you need potentially a strategy: hwo to make updates whicih happens in 3E WWI templates and copy them to your customer specific one
- You should use a "most primitive set up" of your system. There are so many options to enhance the system; at some point in time you might not have the overview what was changed
What you can do with low risk
- prepare own new value assignment tyes plus if needed classes/characteritics
- prepare own property tree
- Define whatever kind of strategy for using the "Substance Authority group"
- If you would like to use your customer specific topics in a customer specific WWI template: yo can do so
For Superusers
If you have understood all the options provided by SAP you can do a clever set up to support the maintenance in many places. But you need to check: what option is the best. As one example: you can prepare a "dyanmic phrase set" strategy; but there is much more you can use if needed.
And if you are the "super super" user: you can completely change look and feel in CG02/CG02BD.
How to start with EHS Classic
The above listed data model is of no value if you do not understand th interaction of EHS to other SAP modules / processes.
The following topics are critical to carify before you start an EHS Classic project.
Processes
It need to be clarified which processes must be supported. E.g. it can be assumed that you will use
SAP SD, SAP MM, SAP PP, SAP TM; potentially SAP QM, SAP GTS and may be other stuff.
For EHS Classic these are the most critical data elements / topics to consider.
Countries / Regions
You do no believe that this is critical? Sorry. his is critical. The reason is: Based on countries / region we have the "Validity Area" in EHS and we have the data linked to the Business Partner.
E.g. to support the BREXIT: you must understand this topic.
Unit of Measument
This is the most critical topic for EHS. This is something you MUST carefully manage in a SAP project and has DRAMATIC effects on EHS if you do it wrong (and you do not have a proper managemnet of that),
Material Master Data
This is critical as well. You need to understand the "DG Profile", The "Environmental flag" and potentially (because of SVT) some material class. You need to define: what material types need an EHS connection? and how you try to manage the link ot materil number to EHS.
BOMBOS
This is a more "niece to have". The main reason is: yes you can generate specifications using this process. But tehre is no add on data. So the EHS Processes can not really start.
Enterprise company set Up
This is cricital to understand because of many reaons. You should have a very good understading regarding te link of EHS to other processes.
1.) how is this related to Safety Data Sheet shipment
2.) to DG Processes
3.) to SVT
4.) to Label Management
5) to warehouse / site logistic processes
6) and much more
Data management
A very important toic is the decsision what do you use to manage the data? Do you buy 3E content; content from other companies and much more like that.
Keep in mind: the data which will come is focussed only on the core data (LIST_SUB/PURE_SUB/DG_CL_SUB etc,) data,
Anything else: You need to manage be your own.
Other critial topics
TODO
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.