Skip to Content

Help on EHS data selection for labeling scenario (without GLM)

Hi EHS expert,

After implement DGM, I am starting to investigate the way we could print label (stock label & customer label) with EHS data.

Let’s says that I have 1 material code which could be delivered anywhere on the globe.

We have implemented the “GHS” globally, with the regional implementation (GHS_CLP for Europe, GHS_US for US, GHS_ASIA for Asia Pacific, etc.). It’s included symbols, signal words, hazard phrases, precaution phrases, etc.

Hard point 1: EHS storing information

If I use the SAP std classification & characteristic, I would have to separate each GHS implementation into 1 VA/Class such as:

GHS implementation (EMEA) // VA/class = SAP_EHS_1023_094

GHS implementation (NA) // VA/class = SAP_EHS_1023_095

GHS implementation (PA) // VA/class = SAP_EHS_1023_096

Or … would not be easier to maintain into 1 ZEHS VA/Class and … segregate the implementation with different usage such as?

REGION/GHS_CLP,

REGION/GHS_US,

REGION/GHS_ASIA …

I am confused ... 😕

Hard point 2: print EHS data

The printing logic for label is to print the correct information for the ship-to country. I tried to read the EHS notes/help portal, but I did get the point on how SAP can select the appropriate VA/characteristic under a certain validy area … from the country (ship-to).

As I understand on the EHS GLM documentation it's seem to be a manual process ...

Ex: if ship-to party = US, then relevant GHS_US data would have to printed.

Also, depending on point 1) I am confused …

I planned to NOT use GLM with WWI … and try to select and export these data on a standard spool output. (We use a external label/barcode solution.)

Do I have the normal EHS approach?

Does the bapi BAPI_BUS1077_GETDETAIL is the best way to select & extract the characteristic data? (seems difficult to use with a validy area condition)

Appreciate any help, suggestion and comment! 😊

Thanks.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Feb 19, 2014 at 08:44 PM

    Dear Louis

    EHS data model does have a history. SAP does have now the trend to "split" properties in "subproperties" (per region).

    Proposal: use the data model as it is. There are several reasons why SAP is now using these standard classes (e.g. access concept). PAY ATTENTION IF YOU USE RULESETS from a data provider (refer below). Don't use in this case a "Z" Class (it is possible but..)

    So you are right:

    "If I use the SAP std classification & characteristic, I would have to separate each GHS implementation into 1 VA/Class such as":

    this is true; this is the "preferred" way to do it and on daily basis nobody has a problem with that.

    Regarding:

    "Or … would not be easier to maintain into 1 ZEHS VA/Class and … segregate the implementation with different usage such as?

    REGION/GHS_CLP,

    REGION/GHS_US,

    REGION/GHS_ASIA …"


    You can prepare this setup; no doubt; result on high level is the same as in the SAP approach; there e.g. is one big "con": If you use rulesets from data providers you should not do it like that as in most cases they use standard SAP model.


    regarding:

    Hard point 2: print EHS data

    This is WWI basic. Please check e.g.:

    WWI for Beginners

    WWI for Experts


    You must understand first the WWI approach; then the answer to your questiot is "easy" (ok: this is not really true; but you come closer to the "real" answer; referring to: The printing logic for label is to print the correct information for the ship-to country. I tried to read the EHS notes/help portal, but I did get the point on how SAP can select the appropriate VA/characteristic under a certain validy area … from the country (ship-to).)


    => On high level: you use a generation variant, a corresponding WWi layout, you maintain the label view, you maintain the data in the proeprties with useful usages and then SAP is able to select (in most cases) the right label (and data on the label) to be printed.

    May be check as well: SAP EHS Management for Beginners

    Regarding:

    I planned to NOT use GLM with WWI … and try to select and export these data on a standard spool output. (We use a external label/barcode solution.)


    This is an option; but I would use different options:

    Several solutions for your demand exists.

    Option 1: Use of an output variant => manual process but it will work (e.g. output variant can be called by external system as well via RFC !)

    Option 2: Use of ALE; substance master data is distributed to "third party" system and processed there to "collect" the nneded data to be printed; here a lot of "suboptions" exists (e.g. use of PI/XI etc. betweep SAP ERP and third party solution)


    I would not use the "Spool" option as you have mentioned and I am not sure if it will really work


    regarding:

    Do I have the normal EHS approach?

    Does the bapi BAPI_BUS1077_GETDETAIL is the best way to select & extract the characteristic data? (seems difficult to use with a validy area condition)


    Use the options mentioned above; they are stable etc. Option 1 does have one "con": it is 80% manuall process; Option 2 ist better; but you must push for the first time the data to the third party system (refer to: )


    Use of BAPIs is possible but you need a "good" ABAP frame to get a solution (e.g. via RFC (like in the case of outputvariant as mentioned above)


    C.B.



    Add comment
    10|10000 characters needed characters exceeded

    • Hello Christoph,

      SDS are generated from a legacy system, which is connected to SAP-EHS. We try to keep the same extraction data logic in both system. Unfornulately, we could not used WWI for that.

      For that, as you notice we transfert Phrases & specification with PHRMAS and SUBMAS. It's tricky but, as far as I know .. it should work.

      The c) scenario is our choice. 😉 ... working with usage filtering.

      Thanks.