Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8493

Re: How many types of SDS we have with standard SAP?

$
0
0

Hello

 

if you install "from scratch" an EHS system and you have adopted all of the required customizing you should "find" a "STANDARD" and an "OBSOLETE" property tree in your system. Because of historical reasons:

 

The "properties" (value assignment types) are "grouped" in the STANDARD tree, Using your screenshot:

 

1.) you have a group of properties refering to the topic "Regulations"

2.) to the topic "IUCLID Properties"

3.) etc.

 

PAY ATTENTION: this structure is not stable ! if you check history you will find clearly less/other "nodes" and less/other properties.

But as explained i a different thread: this "STANDARD" tree is "developped" by SAP in close cooperation with chemical industry and is "state of the art" for EHS, Normally roughly twice a year you will get an update of this tree (how you get this depends or your legal alignment with SAP. If you "buy" content you will get per "update" always the most recent tree. If you don't buy this then the only option to get the most recent version is: you must implement the most curretn/recent SP (as valid for your system) and then you need to apply the "standard" approach to "transport" the new tree to productive system. There is one major OSS note available regarding the process (how to do it. So please check SAP marketplace: Note is: "Delivery of Enhancements to the EH&S Property Tree STANDARD" (having number 1761696).


 

But this tree is only a "proposal" of "data container structures" to be used as "Best Practise"

 

It is clear: any update of the tree will require as well "on top" actions (e.g. generation of new report symbols etc.).; you must check for "phrase based" characteristics (and create the phrase sets)

 

Coming back to:

"The thing is we can customize reach property tree according clent requirement what i required is it will come with standard SAP."

 

you can clearly "custoimize" your own trees (based on what SAP delivers) and this is as well "Best practise"  (but in many cases it is done customer specific). As an example:

 

You can create a tree called may be "Z_REACH", or "Z_OSHA" etc. combining any properties to be used in "REAch" or "OSHA" process.

 

C.B.

 

PS: SAP provides this "docu":

The property tree offers a structured display of all the value assignment types that you can edit in the value assignment of specifications.

 

But they do not specify "which" property tree should be used/prepared ETC:

 

Document: Assigning New Property Tree to Specification Types

could be therefore of interest

E.g. as well: EHS - property tree | SCN

property tree in specifications - add new node ... | SCN

Problem with Property Tree Value Assignments - ... | SCN


Viewing all articles
Browse latest Browse all 8493

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>