Skip to Content
avatar image
Former Member

Reference Value - property tree

Hi EHS SAP Gurus.

I am trying to define the Reference value for Occupational Exposure Limit for an Agent Risk.

About this I have two questions:

1) I would put the Occupational Exposure Limit in the field "Limit Value" in the Standard Property Tree, but I am not finding the Standard Unit of measure that allow me to have for example 80 V, having 80 in the field of Limit Value and V (voltage) in the unit of measure field.

Is it correct? What do I need to change?

2) I created a phrase dB(A) and I assigned it to Unit of measurement, but when I call the reference value in the measurement project, the System doesn't recognise the unit of measurement and gives me an error about unit dimensions (they must have the same unit dimension) Where can I choose the unit of measure to fill correctly the "non standard unit of measure" in the value assignment instance in the standard property tree? Is there any specification or customizing activity for Property Tree?

Thanks in advance.

Regards,

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

6 Answers

  • Best Answer
    Apr 21, 2012 at 05:58 PM

    Hello

    I try to give you a small feedback:

    Property: "Occupational Exposure Limit": I am "surprised" to read that you would like enter 80 V (Volt). Normally in SAP EH&S the defintiion like this is true:

    Occupational Exposure Limits (OELs) help to control exposure to dangerous substances in the workplace, by setting the maximum amount of (air) concentration of a substance that can safely be allowed.

    That means we are normally not talking about "Voltage" but concentration of substances; may be you can explain/add further infos?

    Regarding the phrase topic: i belvie we are talking about SAP IHS ? Normally you can not use phrase based information to handle unit of measurement topics; SAP is providing a number of characteristics (like you have described); but in most cases the content is used only for MSDS generation or similar topics. Once again in most cases the "non standard unit of measure" is either phrase based or "freetext";

    The handling of UoMs in a SAP system is not easy especially in the area of EH&S.

    C.B.



    Add comment
    10|10000 characters needed characters exceeded

  • Apr 23, 2012 at 12:21 PM

    Hi Michelle,

    Christoph is right, non-standard units of measurement are phrase- or free-text based. As such, they cannot be compared with a reference value.

    Ralph

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 24, 2012 at 07:16 PM

    Hello Michele

    a.) SAP is providing you with "standard" properties. It is allowed to enhance the EH&S system using own properties. I am not aware of any property which you could use to deal with:

    "noise, vibration, electromagnetic field, optical radiation, and other physical agent risk " as you would like to do it (but as SAP Standard tree changes by release may be there might be some suitable property)

    b.) The property you have used is from my point of view clearly the wrong one.

    So one option in my opinion is to check the tree you have to identify suitable properties. If you are not able to find one: create one. In doing so you are "totally" free in defintion. Therefore you can describe "noise", and other similar stuff by preparing suitable characteristics. Now these characteristics can have an UOM (e.g. dBA .... etc.) and therefore you can use "conversion" rules (e.g. kg to g etc.). Now you are able to maintain the data.

    Now lets think a little bit about your demand: normally you have a "location" which you would describe (the work area in SAP IH). Here there could be the danger of "noise" etc. you canget into contact with an electromagnetic field etc.

    Now "noise" is not something which can / should be described by using a specification.

    A "suitable" specification in the sense of SAP IH might be: you can get into contact with en.g. nitrogen, oxygen or whatsoever.

    Now a specification can emit radiation (like element "Radon", "Urane" etc. But a specification is not useful to describe electromagnetic behaviour etc.

    May be this helps to go on

    C.B.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Michele,

      If I understood correctly, you defined a new property tree and in this tree you copied the same class/characteristic as you had in the standard tree? If so, then of course it doesn't work since you still have the problem of comparing a UoM woth a phrase. You need to define a new characteristic for your value so that the UoM in thisa characteritic is actually maintained as a UoM. Potentially, you have to define the UoM as well if it doesn't exist yet. Then, probably via a FM, you can comapre the two values.

      Ralph

  • avatar image
    Former Member
    Apr 24, 2012 at 02:12 PM

    Christoph and Ralph thanks for your answers.

    I have understood like you said, that from Standard Property it is possible to manage and define only agent risks like Air, biological substance, chemical substance…..and similar data, isn’t it? Let me try to explain better my difficulties. In that property Tree is very difficult for me to define the Limit Value for example noise, vibration, electromagnetic field, optical radiation, and other physical agent risk because I suppose to put their limits in the respective field like: value in Value in Non-standard Unit and the unit of measure in Non-standard Unit (using phrase).

    See the picture “Limit value in standard property tree”.

    The other step that verify and use the data defined the first is the follow.

    When I am searching to call the reference value for a measurement of an agent risk, in the transaction CBIHM2 (edit measurement project), to compare the reference value with measured value, this value is not charged correctly (because of the property tree definition) and the unit of measure is not charged correctly and consequently it is not realized the comparison.

    See the picture “Measurement project – reference value – unit of measure”

    Probably the table CCIHS_MJVAIOT that the ABAP code uses is not the same that is used in the Agent workbench Abap code and there are some problems on the correct setting of Property Tree.

    I hope that I was more clear and regret for any other answers.


    Add comment
    10|10000 characters needed characters exceeded

    • Hi Michele,

      That is exactly what doesn't work. Since you maintain the non-standard UoM as a phrase, the system cannot compare it with the UoM DBA. It is like comparing apples with oranges, it just doesn't work. I am sure that there is a way to enter reference values in a way that they can be compared with the measured values, but I have no idea how to do that, you need an IH/OH person here.

      Ralph

  • avatar image
    Former Member
    Apr 27, 2012 at 07:47 AM

    Hi Michele,

    In your case Phrase management wouldn't works. You have to play with the numeric values, when you are comparing with measured values and reference values.

    Check your characteristic in property tree, which you are using.

    That characteristic should have been maintained Data type - as "Numeric format".

    Y

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 27, 2012 at 07:50 AM

    Hi Michele,

    In your case Phrase management wouldn't works. You have to play with the numeric values, when you are comparing with measured values and reference values.

    Check your characteristic in property tree, which you are using.

    That characteristic should have been maintained Data type - as "Numeric format". (CT04)

    Select the Number of chars, Decimal places & "Unit of measure". which is very important.

    whenyou are entering the data, the numeric format pick the UOM automatically.

    I hope answered your quesiton.

    Regards

    kamal

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Michele

      I am not experienced in using CBIHM2 (and the corresponding customzing) but may be I can provide further "help".

      a.) I would like to come back to this:

      "International Occupational Exposure Limits and in particular the values put in the three standard fields by the system (value in ppm, value in ml/m3, value in mg/m3 and Value in Non-standard unit)"

      Some comment: To my knowledge this is SAP approach: they are collecting demands of many customers and try to think abou useful property structures and they adapt the tree regularly (by using now Enhancement Packages). If you need tree updates you need to check the "content" area of SAP. I did not check this area recently but last time I did check that there was no "service" available to get a "tree" direct (and you need not to wait and to install recent Enh.Pack) but may be come into contact with SAP regarding this topic.

      Now back to your example. Property "International Occupational Exposure Limits" is defined using e.g. these characteristics:

      value in ppm

      value in ml/m3

      value in mg/m3

      Value in Non-standard unit

      and

      "non Standard unit"

      Now let us discuss this structure a little bit: if you check Standard tree and compare that to other properties you will find similar structures very often

      What is the idea behind that? Answer: based on demands of customers and their feedback characterisics like

      value in ppm

      value in ml/m3

      value in mg/m3

      have been defined. Using characetristic "value in ml/m3" you can enter any value together with any UOM which you can convert

      (ml/m3 => m3/m3 etc. etc.) (volume per volume); using "value in mg/m3" you can enter and convert anything like:

      mg/m3 => kg/m3 => mg/ml etc. (mass per volumen); Regarding ppm: this does mean "parts per million"; normally I believe it is "dimensionless" defined

      Now by checking legal requirements etc. SAP has decided to prepare these characteristics:

      "Value in Non-standard unit"

      and

      "non Standard unit"

      These should be read/used always together. Example from legislation: if you make a survey you will find values liek this (as limit values)

      1000 fibres/m3 (having the meaning that iv you check the air the company must make sure that not more than 1000 fibree (likes Asbest) are allowed per "m3"

      in the air. These type of "UOMs" are used very often in legislation. SAP was not able to prepare here a "suitable" structure. There is no "conversion" rule available to

      com from "fibres" and to convert that to "kg" (mg etc.). Therefore SAP propose to use "fibres/m3" as a "phras" which is linked to "non Standard unit" and the value should be maintained in "Value in Non-standard unit".

      In your example you would like to used "herz" etc.

      In handling IHS issues (like your noise example, radiation example) there are in my opinion a lot of similar demands. The "only" chance you have is: you need to discuss with your business and then per demand add a further "Z characteristic" in the "Z Class" etc.

      PLease check once again this link:

      http://help.sap.com/erp2005_ehp_06/helpdata/en/8a/3b6e361b2fac0be10000009b38f839/frameset.htm

      and the subchapter: "Entering Reference Values" and read carefully (may be) once again the "prerequisite" chapter there some advice is provided regarding the "reference value" (sorry I am not an expert in SAP IHS)

      May be somebody different can help you how to prepare the correct custumozing etc

      With best regards

      C.B.