Skip to Content

Recommand std EHS substance structure, properties, characteristic ?

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,

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Feb 10, 2012 at 03:05 PM

    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.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 11, 2012 at 07:48 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

    • 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

  • Posted on Feb 20, 2012 at 04:02 PM

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

    Regards.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.