mixture from different standard SAP_EHS_10* value assignments

[holger_hartung]

Hi Gurus,

are there any reason to don't add to an existing and used value assignment (SAP_EHS_1023_044) characterisics from other SAP_EHS_* value assignment? If not, what are other Options?

[satya11719 · Accepted solution]

Hello daytona80

Yes , You are not supppose to mix up every class and characteristics have the exact purpose and a standard report symbol is assigned to it and when ever there is update on property tree your changes will be impacted,

if you have any specfic requirement then you can create customized VAT , class ,char's and report symbol it fulfill your requirements.

SAP recommans to donot change anything in the standard property tree.

cct.png

I hope this helps.

Regards

Satya

[holger_hartung]

Hi Satya,

in other words, you would mixture sap standard classes? I mean that I have read recommondation do not...

[christoph_bergemann]

Dear Holger

if you "manipulate" the SAP classes or SAP characteristics: this is from SAP point of view a "modification". Technically: you can try to do it and according to my knowledge: it will work, BUT YOU SHOULD AVOID IT

The reasons are (e.g.):

1.) if you do a "SP" update (or upgrade) fo your SAP system normally you would like to use the "most up to date" Standard tree; ufter update/upgrade you must "implement" then the tree (i skip here the technical details how you go implement it) and the you "overwrite" the changes you have done (or there is a risk to do so)

The topic of "SAP Standard" was discussed e.g. here: https://answers.sap.com/questions/9078051/recommand-std-ehs-substance-structure-properties-c.html

If you are not satisfied with the SAP standard the "Best practise" (from my point of view) is

Copy the "SAP" Standard to a "Z Customer" space and use the "Z" properties etc. in your set up.

Many consultant have a trend to "reuse" charactistics. in "classes". The reason is as well related a little bit to SAP standard (e.g. characteristics of type "GLP"). You should avoid this process/this approach. There are to many pitfalls in this approach.

DO not mix SAP classes with Z characteristics etc. (or the other way around use a "Z class" wtih SAP characteristics)

Some weeks ago i have identified the relevant SAP tables in SAP which "steer" the "modification" story. SO do not change SAP standard (this just add more riskfor maintenance of the relevant SAP system (there are much more reasons to list here))

The "best" approach depends on your specific situation, E.g. do you buy "content" (rule sets etc.) or not

If you use "content": then the "Z approach" is not "optimal" (but your only choice) as the "content" is designed to be used in 100% SAP Standard. So the afterwork to consider the "Z" part can be high (but clearly: from technical point of view: this is possible)

Honestly: if you execute a small survey here in this FORUM you will find some threads discussing the story (looking back to history etc.): many companies seems to use "Z classes" etc. And this is the correct approach.

C.B.

PS: https://blogs.sap.com/2015/07/04/sap-ehs-standard-data-model-ehs-classic/ could be of interest

[satya11719]

Hello daytona80

Again your question is not clear, you are asking about why we will not add one class (VAT) characteristics into other class (VAT) ??

Please describe the question.

Regards

Satya