Recommand std EHS substance structure, properties, characteristic ?

[Louis-Nicolas]

Dear EHS experts,

As a newby in EHS module, and before setup or specification database I am wondering about the best ways to setup our specification structure. As specification type, property tree, class, char. ... are the heart of the EHS database, I am wondering if I could setup these 4 types of object manually with Z object :

I means by creating :

=> ZREAL_SUB specification type,

=> ZCEHS_XXXX value assignement,

=> ZCEHS_XXXX class,

=> ZEHS_xxx characteristic,

=> ZEHS_xxx phrase Set,

Does this way of EHS customizing is dangeurous ?

Does some characteristics are very sensitive to any process ?

Our EHS final scope will be : Safety Data, Dangeurous Goods checks, Waste Mgt, IHS.

Thanks for your help.

Regards,

[Louis-Nicolas]

Thanks for your advice. I will keep as possible the EHS standard structure and class/char.

Regards.

[christoph_bergemann]

Hello all

as explained. yes you could try to prepare a complete EH&S setup using "Z naming" convention. This is not recommended. Normal approach is: use a "sandbox client" install the SAP standard and then think of customer specific enhancements. Then take over SAP standard and customer specific enhancement in development line. Do not ! mix SAP standard EHS classes with Z characteristics. Be aware of the fact that by implementing "Enh. Pack", "Support Packs" etc. new EHS classes will be delivered.

If you would be "consequent" you need to prepare Z phrase sets etc. E.g. identifers like NUM CAS it does not make really sense to implement NUM ZCAS only to be in customer name space.

Further: sources, user defined texts customizing (regulatroy lists etc.) need to may be adapted too. The whole work is not worth the result. The SAP standard is a really good starting point to use and only if necessary you should add further e.g. classes etc.

With best regards

C.B

[Louis-Nicolas]

Hello all,

With other SAP Module, I am used to setup Z sap object, in order to be able to compare (if necessary) my Z customizing object to the standard.

Here, I am thinking the same way. For example, on the REAL_SUB, I would like to setup some custo point (for example the tabs that I will not used ...). By customizing entirely the substance, I will be much more confident on how EHS works and how the substance is customized. It's also a good method for me to learn the way of customizing EHS.

The other reason why I am thinking about this, is that I do not know how to use all the default characteristic assign to a class. Those characteristics do not "talk to me" ... sometimes, even for end-user.

So my idea, is to defined with end-user, the list of value assignment needed, and for each, all characteristic & data that could apply to it. By bulding this all Value assignment-Charactiristic tree, I will be probably much more confident with solution ...

By Z naming convention, I was thinking of : Substance (like ZREAL_SUB), Z property tree, Z Value Assignent (property) with Z class assigned, in which I will setup Z characteristic. I will not mix Z char with SAP_EHS class.

For other point, I will keep std custo (for identifiers ID, regulation list, Rating/Valididty Area ...)

Thanks for your recommandation.

[Ralph_P]

Hi Tyller,

If you want to play around in a system in order to understand how it works I'd rather you use a sandbox instead of a running system. Everything you mentioned can be done in the standard anyway, there is no need to go into the Z-namespace.

Ralph

[christoph_bergemann]

Hello

I totally agree to what Ralph has explained. You can "play" aound in a sandbox or different client but it is absolutely not worth the work to "map" the "whole" standard SAP customizing into a Z namespace customizing. You need to adapt so my standard program (or check if they will run) that you lose only time and may be budget).

By the way: the characteristic assigned ot th SAP classes does all make sense. These standard structure has been now developped other the last year with the assistance of many other SAP EH&S users and e.g. the chemist and others which will normally use EH&S should "immediatley" understand why this characteristic is in place.

Keep in mind that EH&S PS, EH&S DG, EH&S Waste etc. combined in property trees etc. so the SAP Standard tree supports a lot of EH&S processes

With best regards

C.B.

Edited by: Christoph Bergemann on Feb 19, 2012 1:46 PM

Edited by: Christoph Bergemann on Feb 19, 2012 1:47 PM

Edited by: Christoph Bergemann on Feb 19, 2012 2:02 PM

Edited by: Christoph Bergemann on Feb 19, 2012 2:04 PM

[Ralph_P]

Hello Louis,

Yes you can. But you ought to be careful somewhat, it does not make sense to create an object in the Z-namespace that already exists in the standard like the ZREAL_SUB you mentioned in your post. From my experience: The closer you stick to the standard, the lower the possibility to run into issues at some time later on.