Product Lifecycle Management Blogs by Members
Get insider knowledge about product lifecycle management software from SAP. Tap into insights and real-world experiences with community member blog posts.
Showing results for 
Search instead for 
Did you mean: 
Active Contributor


The Blog: is old and partially not up to date any more. So it is time to have a restart.

Since the set up of the blog as mentioned above: SAP is still on track to prepare a new software to be used based on modern IT architecture (either as a "Cloud" variant or as a "On Premise" variant).

More precisely: we can define at least "two new softwares" which will come. One still called "EHS" and the other called "Product Compliance".

The two new solutions will support different communities and different legal needs to support.

So there is not "one" software any more (like EHS Classic) but two Software components.

Both have different SAP Roadmaps (for S/4 HANA environment).

But let us start the theory on EHS Classic (refer below). And the theory depends on "SAP System" which is used as the basis (the "version" of SAP).

R/3 Installation

With "R/3" we have to check this online help describing the software.

Here SAP describes the Software as "Environment, Health and Safety (EHS)". This term is not a "good" one (reasons to be discussed below).

But I just call this "EHS Classic".

A software to check (potentially) is described here:

This software is called: Component Extension for SAP EHS Management (in most cases linked as well to the term "EHSM")

There is some overlap (regarding functionality) to the above listed SAP software.

SAP hast stopped investment in the use of "Enhancement Packages" (currently we have version 8 in the game).

So the so called "SAP EHS Classic" version is getting only updates if needed (error fix) and there is no new functionality to expect in the near future.

Only exemption: if there is the new to support some legal change. A good example was BREXIT. Here SAP has supported us by delivering some improvements for EHS Classic so that we can support the "North Ireland" special story of BREXIT.

On the top: there is a trend at SAP that they will not deliver any more all components which are relevant from regulation/legislation point of view. One example: SAP is not delivering a solution to support the "Poison Notification Law" to be supported in Europe (e.g.


S/4 HANA Installation

With a "S/4 HANA" installation:

is a starting point but with a big "BUT"

SAP has "simplified" the EHS Classic. So some solutions of EHS classic are not available any more based on a S/4 HANA installation or we need to use a new/different solution etc.

If you use this component in the "old" EHS: Occupational Health (EHS-HEA) => then you need to check the "new" version (which is now, according to my understanding, available as an "Add On" (please check the many threads, e.g. example as

If you have used the component: Waste Management (EHS-WA) ==> this software is NOT available in S/4 HANA. Currently no follow up solution exists but SAP is working on a new solution (Please check SAP Roadmaps and many other locations to collect informations regarding the new solution).

For reference; There is a new comment added to this Blog:

regarding the options in S/4 HANA.

If you "migrate" to S/4 HANA (whatever approach you might use): be aware of the fact that nealy any Business Function of EHS classic as available in R/3 is activated automatically and there is no option back.

There is only one exemption: the first "Enhancement Package" functionality as part of Enhancement Package 3 is NOT activated automatically. But in this Enhancement Package you will find some interesting features.

The New Software

As mentioned above: SAP is working hard on the follow up solution of EHS Classic. Please check this very good Blog (refer below) to get an overview about status of the new solution etc.

The new solution is described here:

THIS BLOG is a must to READ one:

if you need to most current informations shared by SAP regarding the new solution (Product Compliance solution).

On the top you will find Blogs like:

New/Old Terms

In the "old" days more or less two terms have been used: EHS (= EHS Classic) and EHSM (Component Extension of SAP EHS Management).

In the S/4 HANA world: these are not good terms. We have a "New" EHS version (e.g. linked to "Incident" and "Accident" etc. part) and we have the "Product Compliance" version.

And we have "Waste management" as part (or will become part of) "Environment Management" (

Still we have some "Recipe Development" (Recipe Management is not available in a S/4 HANA environment). What will happen with this software; we do not know exactly but we can assume that SAP will rearrange the software as well.

And there is more to be checked if you take a look on SAP Roadmaps / Strategy.

And, and this is the most important fact: at some time in the future R/3 is not supported any more and you need to use S/4 HANA version (please check SAP Marktplace and other locations to collect informations (e.g. SAP Roadmap Explorer)).

EHS Classic

Until the "Product Compliance" solution is ready to be used: you will use EHS Classic e.g. for topics like:

    • "Dangerous Goods Management",
    • "Substance Volume Tracking"
    • Report generation/Report shipment (e.g. Safety Data Sheet)
    • to generate a "Label" (and then using "Global Label Management)
    • etc.

Especially because of "REACh": there is still a "hype" in the use of "Substance Volume Tracking" as more and more countries are implementing a similar law.

What will happen with REACh? We can expect to get a new/updated "REACh" legislation in the next may be 2 years. Focus will be on "Polymers".

But still the "old" trends need to be supported as well:

    • Changed or new GHS implementations
    • More and more regulations to be supported (e.g. the need to "get" and "use" content is much higher than in the past)
    • For many companies in the Chemical industry: the "customer" and the "Supplier" (of raw materials) is more in the focus. So the need to exchange data using IT options is a clear trend (e.g. generation of XML like data streams)
    • The use of a "Portal" of many kind to support the Customer is in our days more or less now a "must" (sometimes they are called "Productfinder"; sometimes the Portals are "so big" that the customer can direct "buy" something like in "Amazon")

So to be "up to date" in the areas of

  • Legal Content
  • Rule Sets
  • WWI Layouts

are drivers for IT investments.

On the top: many companies are planning to migrate R/3 installation to S/4 installation (and clearly: many SAP customers check if a "Cloud" variant is a good option/choice).


As explained above: The "Product Compliance" is currently not ready to be used. This might change partially with the next version of the software coming end of 2023.

IMPORTANT: the new version of "Product Compliance" (Version 2023) is released now to the SAP customers. PLEASE CHECK ONLINE HELP (REFER ABOVE)

IMPORTANT: read carefully any Blog or thread here or check SAP Marketplace regarding "SAP Roadmap" especially for "S/4 HANA" Software and for "Product Compliance".

KEEP IN MIND: SAP has a different strategy for "On Premise" and "Cloud" architecture. The roadmap is different. This difference can be a driver if you plan to start a project (installation and use of "Product Compliance")

IMPORTANT: you need to understand the the scope of "Product Compliace" solution is different than EHS Classic. This has an impact mainly for the labeling part.

SO KEEP IN MIND: Cloud solution will be deployed first; and therefore: Cloud Architectures are as well of high interest.

But we have "hard" facts from market (and legislation/regulation as well). We must collaborate much better. The so called" Supply Chain" is getting more and more important.

Therefore: we have two partnes in the game:

- the supplier of chemistry


- the customer of the chemistry

(and in many cases: We have legal departments to be supported like "ECHA" and many similar ones).

Because of "REACh" and many other similar regulations: the company acting must take care to manage the communication efficient for both directions.

So still many companies are working on IT solutions to scan a Safety Data Sheet; to determine "text patterns" and to "decompose" the data and to "map" it and then to "load" the data to EHS structures to avoid human" power to enter the data in the system.

How "Artificial Intelligence" will help here... we will see.

Because of the "S/4 HANA Product Compliance" initiative: many companies start to analyse their IT landscape; what can be simplified? how to prepare the "best" to use later the new Software etc.

Therefore we will see two challenges: we need to find function/technical consultants who can support EHS Classic AND who can support the "Product Compliance" in the near future.

As the concepts of the new software are different to the old one: this is a chance and challenge.

You need to decide (in context of move to S/4 HANA):

    • Should I use "greenfield" approach?
    • Should I use "brownfield" approach?
    • And how can I support better my business (you should not only check the new software; you should try to optimize the currently used processes)?

Current scope of discussion in this FORUM

Using some examples from current running discussions: we will see: EHS Classic still has some challenges. Here a short list of examples should be presented, but in a nutshell we can identify these "top 10" topics:

    1. WWI Development
    1. Substance Volume Tracking
    1. Data Sharing (reading, inserting, updating, and deleting as well)
    1. Data Import / Data Export
    1. Dangerous Goods Management
    1. Safety Data Sheet distribution/shipment
    1. Global Label Management
    1. BOMBOS interface
    1. Content Handling (including: Rule Sets etc. etc.)
    1. How to start an EHS Career

On either "zero" level or a very low level of discussion we can list:

    • Occupational Health
    • QM/EHS interface
    • Waste topics
    • Hazardous Substance Management

So the situation is not really different in comparison to 10 years ago.


Topic Goods Management Set Set development import Distribution/Shipment Development Distribution/Shipment Distribution/Shipment Development Development Development + GLM + GLM Volume Tracking / Share Data

Career / How to start?

Still there is interest to get an idea: how can  I start an "EHS Career"? Or how to start anyhow (what is "EHS classic" about)?

Still the same is true as in the past:

To start with EHS Classic you need Know How in these areas:

    1. SAP MM
    1. SAP SD
    1. SAP PP
    1. SAP DMS (and anything around)
    1. SAP Classification System
    1. And some "ABAP" knowledge is needed as well (at least you should be able to work on "Customizing" activities)

Your starting position as a "pure" ABAPer is not good enough. EHS Classic deals with "regulation/legislations" and EHS Classic tries to support this.

Therefore: You need as well a good understanding regarding the needs: why do we need to use SAP EHS classic (in the chemical etc. industry).

Second: In contrast to SAP MM etc. Regulation/Legislation does not "stop". So you are always (some how) any year on a learning  curve (example might be the "Poison Notification Stuff on Europe).

Currently we still can see a kind of "REACH roll out idea" in many countries. Same as for "GHS".  And because of political discussion: anything around as "emissions" etc. is of high interest (Carbon dioxide emission, etc. etc.).

EHS Classic Structure

We can differentiate these submodules in EHS Classic:

    • EHS-BD (called "Basic Data and Tools")
    • EHS-SAF (called "Product Safety")
    • EHS-SAF-GLM (called simply "GLM")
    • EHS-HSM (Hazardous Substance Management)
    • EHS-DGP (Dangerous Goods)
    • EHS-WA (Waste Management)
    • EHS-HEA (Occupational Health)
    • EHS-IHS (Industrial Hygiene and Safety)

This "online" help fits as well to the node structure in SAP GUI (EHS Classic is "linked" to the node "Logistics" in the explorer like structure) and the same structure is used if you need to check and do research in the SAP marketplace.


We can define this component as the "Heart of EHS Classic". If you have issues in understanding concepts (like why do we need a REAL_SUB, a PURE_SUB, a LIST_SUB, a DG_CL_SUB object etc.) STOP here and try to understand before you go on.

As this part of the software is really big. we have a substructure like:

    1. EHS-BD-SPE (Specification Mangement)
    1. EHS-BD-SIS (Specification Information System)
    1. EHS-BD-RDF (Report Definition)
    1. EHS-BD-PHR (Phrase Management)
    1. EHS-BD-TLS (Tools)
    1. EHS-BD-CCK (Compliance Checks)

The last topic is only of interest if you use Recipe Management (PLM-RM).

Phrase Management

The "easiest" option to get in touch with the EHS-BD part is to understand the "phrase concept" first. Basicly: a phrase is a "data container" to be used (in most cases) in the data maintenance.  A phrase can be assigned to a phrase set and a phrase set is linked to a characteristic and a characteristic is part of an EHS Class and therefore available in the property tree (as linked to a "value assignment type) and by using this option you can maintain data in SAP transaction CG02/CG02BD. E.g. you can generate a phrase like "Green" (a "text"). This text can be translated in many language (transaction CG12). Any phrase must contain at least one "text" for one language.

The data model is explained here:

Phrases are needed as well in the context of:

    1. WWI development (including topics like: Cover Sheet, etc.)
    1. Dangerous Goods Management
    1. etc.

If you buy content: in most cases you will get a huge number of relevant phrases in daily business (BUT MAY BE NOT ALL NEEDED phrases) in "all" the needed languages. So they are a core element of EHS data Maintenance.


SAP has decided to assign these "subtopics" to the main topic "Tools":

    1. Import / Export options (
    1. ALE distribution options (
    1. EHS workflow (nearly on "zero" level of discussion here) (
    1. EHS / QM Interface ( (very low discussion here)

A "must" to understand is clearly the "Import / Export" part and the "ALE" topic. You will find lot of discussions regarding these topics here.

E.g. many functional and technical consultants start learning EHS Classic because there is a need to move data from a "legacy system" to EHS classic.

The reason is simple: To get a result: YOU MUST LEARN AND UNDERSTAND BY HEART the data model of transaction CG02/CG02BD.

In our days: the "extraction" of data and documents is getting more and more important. And ALE is only one option. A further option is the use of "Output Variants" which are part of: EHS-BD-SIS.

The "interaction" of data (in / or out) is currently a "hype". You will need to learn on "RFC" calls, WebServices, potentiallý use of oData services and many other stuff (so we have "synchron" data exchange and a "asynchron" variant).

Many companies use own developped "Workflow" tools to "collect" data and to publish them in EHS classic.

The EHS Workflow is used rarely. I believe there are not more than 10 threads of discussion in this FORUM.

Specification Information System

To manage data in EHS: you need to enter the data (create/instert, update, delete), you need to do a "research" for data (explained below) and you need partially to do "outputs" of the data. The Specification Information System is such an option to "output data". SAP is delivering, what is called "Output Variants" to get on touch with the stored data. But you can easily extend this and luckily: this extension is a natural option to enlarge the existing functionality (IT IS NOT A MODIFICATION) and therefore stable even of you perform an Update/Upgrade of your system.

Report Definition

If you take a look on these Blogs:

(please check Blog: for further references to many other Blogs, discussions etc.

We can define the "WWI" tool as the "Top 5" discussed story here. So functional and technical consultants "love" and "hate" this tool.

The reasons is may be simple: You need to get in touch with some "external" software (called WWI) either located on your client or is present on a server farm. You need to have good/very good understanding how to manage a:

    1. Windows installation
    1. WinWord Installation
    1. SAP Gui installation
    1. Set up of RFC connections
    1. WWI Admin topics (how to monitor the process, how to get rid of problems in the process) etc.

On the top: we can see "complex" demands to be solved using WWI (you will find many threads here). So you need not only to have good understanding regarding the "basics" of WWI: you must have understood: what standard options are existing sing EHS Classic and how can you create (if needed) own "Report symbols" with own developped Function modules to support the demand. And at the end: YOU NEED TO SUPPORT the full E2E process, starting from maintenance point of view) including: how is "WWI" retrieving the data and present the data using WinWord as the tool (topic of: how can the process determine "Fonts" to be used during the presentation of data). On the top: you need to have knowledge about: what is an "Include" and how to use it properly etc.

Long ago (before the "Include" technique was available): a WWI layout used to generate a Safety Data Sheet for Europe can have more than 100 pages with "cryptic" code (you need to understand the WWI code options (Symbols etc.). So yes: with the Include option this is better now. But as always... there is a "but". Now you need to be able to properly manage the "Include" option.

WWI can be used as well to present "Barcodes". And it is a useful tool for preparing "Label" like WWI layouts. But here: you need as well good knowledge in SAP SD, SAP PP processes as you will use quite often so called "final report parameter symbols) and here you must "CODE" (using really ABAP code) your solution by your own. For Safety Data Sheets: You could decide to just "buy" (what is called) content and you will receive a usefull WWI Layout.

Report process

We can define these "subtopics" to address in the "WWI Report" topic:

1.) The WWI template (ignoring for a second the topic of "Inbound documents")

2.) The generation variant (which links the "Report type" with the WWI layout)

3.) Transaction CG50 (Manage the report)

4.) Transaction CG54 (Report Information system)

Most of the normal enduser are using only CG50/CG54.

Functional/technical consultants work on WWI layouts and generation variants.

Even the "generation variant" might look like "EASY TO UNDERSTAND".. this is not the fact as you must habe very good knowledge regarding:

    • What is a "report type" and why we need this?
    • What is a "Rating" and why we need this?
    • What is the "leading" validity area?
    • What is the "discrete" validity area? How is it used?
    • If needed you need to have an understanding regarding how the Status is used on Phrase level
    • etc.

If you need hints for the story: Start with the online help. Even if the "Online help" seems to contain only "simple" facts you should really read it.

BUT without training (how to generate customer specific report symbols) etc. and many other stuff: it is a long challenge to start with WWI to get an expert (and it need some time to get an expert in this area).

Therefore: check the many Blogs and threads existing here. And start "Simple"

The "highest" challenge is to handle "Labels", "Dangerous Goods Data".

In the context of "Report Management": e.g. a challenge might be to understand "how to use report header references" and how can this simplify the daily maintenance (but you will increase complexity).

Specification Management

First: you should try to understand why we have the SAP transaction CG02 AND CG02BD in the game (what is the difference, purpose etc.).

This part of the software is the "biggest" one and if you have no clue about the structure: just stop.


You will find some hints why we have "CG02BD" in the game. But most of the consultants and companies focus on using of "CG02"

The first topic to learn is:

    • What is a REAL_SUB, PURE_SUB, LIST_SUB etc. and why we need these objects
    • Then you need to undertand by heart: What is a "property tree" about? How to extend change and use this?
    • What "Search options" do I have to find data etc. (and how to extend EHS Classic to get more search options)
    • You should (not to say you must) have a good unerstanding regarding "Change numbers" (why are these objects in the game; how to use them properly etc.)
    • Topics like "Reference", "Inheritance" etc. are not easy to understand. The most complex topic to learn is regarding "Inheritance"

Key data elements in CG02/CG02BD

Before you start EHS Classic you should have a good understanding regarding this (check e.g.


Which topic? (you need to know / understand etc.)


Specification category

Very high

Specification type

Very high


Very high


Very high

Authorization group

Very high

Substance Nature








Material Assignment

Very high

"Property" / "Property tree"

Very high

Regulatory List

Very high


Very high



User Defined Text


Value Assignment Type

Very high

Key Date (Change Number handling in EHS)


Niece to have (understanding CG02/CG02BD)

Topics which are helpful in the daily work are e.g. topics like (which are explained in the Online help)

    • Query Management
    • Hit List
    • Drilldown Reporting Job
    • Where-Used List for Specifications
    • Secondary Data Determination

Only if you have understood these options: you can really support EHS Classic.

Material/Specification Assignment

A correct material / specification assignment is the core element so that EHS Classic can integrate with SAP MM, SD etc. The material/specification assignment is important (in SAP Standard data model) on level of:


The "correct" link is important to support these processes (sublist):

    • Dangerous Goods Management
    • Report Distribution
    • Substance Volume Tracking
    • Global Label Management
    • Hazardous Substance Management
    • etc.

In EHS classic you fill find a huge number of technical options ot make sure that the "correct" material / assignment can be established (so that one material is linked (from functional point of view) to one specification only.

Status Management

On the level of the specification header you can use a "Status management". This can be combined with a "Status Management" on phrase level.

The "Status Management" on specification header level can be extended/enriched (there are enhancement options availbale; Check Customizing of EHS).

How you will use the "Status Management": it is a totally company specific decision and mainly based on organisational set up of the company acting and other topics to consider.

There is a low level of discussion here regarding "Status Management". So it is used by companies.


Depending on the fact at which point in time you started EHS Classic: you will use "Reference" or "inheritance" to support the daily maintenance activities.

The "reference" option is robust to use and "simple". The "inheritance" option can be complex in daily use but it is much more flexible in comparison to the "Reference". One profit of the use of inheritance is: you can interit (if needed) as well identifiers.

The complexity of inheritance is corrlated to the "Inheritance template" used.

With higher SAP releases (by using "Enhancements" in the "Enhancement Packages") the "inheritance" option was optimized.

But the users must have a good understanding about the idea of "Inheritance" and there are some "ABAP Jobs" on the topic to consider to support the inheritance.


The topic if "Restrictions" is described here:

In daily practise: there might be some benefit to use this option in the software But the benefit is (from my point of view) limited.

Secondary Data Determination <> Rule Sets

One option to differentiat the two terms could be just to define it as:

    • If we talk about "Rule Sets" we are using "Expert Server like rules"
    • And if we do not use an "Expert Server": then we talk about "Secondary Data Determination"

In the area of "Expert Server": you can buy content (so you will get predefined Rule Sets etc.) or you can try ot set up own rules.

In the area of "Secondary Data Determination" you are free to use/prepare own developed ABAP structures in correlation to existing data on the level of the specification.

But still there is an issue. If you check "Customizing" you will find as well enhancement options which can be used in CG02/CG02BD which are having partially an overlap to the "Secondary Data Determination" structure.

But in a nutshell: what ever option you try to use: you can enrich the data; ideally without the fact that really a "user" is working on the data.

One term used often in discussion is: to "automate" the work.

EHS Workflow

There is as well an option to use a "Workflow" architecture in EHS. In most cases the idea to use a workflow is based on splitted responsibilities. That means organisation A in the company is responible for something different than organisation B.

Using a simple example:

You can set up a workflow like: if data was changed, which might some have some relevance for the data which is valid in tontext of "Dangerous Goods" and the Dangerous Goods data is maintained e.g. centrally... then it could make sense to use the "workflow" option.

Report distribution

In the "Report distribution" part the most important subprocesses are:

    • SD_CALL (SAP SD integrates with EHS)
    • MAN_CALL (EHS is the starting point of a report distribution/shipment)
    • SUB_CALL (important for any process; new major version of a report exists)
    • EXP_CALL (extracts of documents to be used in a huge amount of suprocesses

To a certain extent: the import process of a document is as well important to support potentially the report distribution. The  import process is dedicated to upload documents from "suppliers" (therefore linked to (in most cases) "raw materials" to be used in a subsequent process.

The Report Distribution/Shipment process is linked to the WWI process. So it can only work if the WWI server farm is up and running.

To set up the full process: luckily we have here a SAP OSS Note (a consulting note) in place which can be used as a reference. A quite high list of decisions are needed to prepare a up and running report distribution process. Not only is the SAP SD integration not easy to understand (nor to do a set up here) but we have as well some "customer exits" in the game which need to be analyzed based on business demand. As the communication to the customer is a core piece  in the daily work: this process (to ship/distribute a Safety Data Sheet) is a must to be set up.

The "Report Distribution/Shipment process" is one of the core processes in EHS classic. It is not easy to understand as we have the SAP SD interface, a huge customizing to consider a lot of "side" effectt to take care (e.g. set of of Cover Letter, SAP Printers etc.).

In a nutshell: in most cases it is a "must to use" process. Luckily: SAP is providing a special OSS Note (a consulting note) to help you in doing the sep up; but may be you need 5 cycles of set up to really understand it "by heart" (how to do a proper set up etc.).

Dangerous Goods Management

The "Dangerous Goods Management" process is explained here:

Only some critical success factors should be listed here:

Success Factor 1

Split the "maintenance" part from the "use" of Dangerous Goods Data. Always start with the "maintenance" part.

We have in the game:

Material Number





But this is only true if you use the "Dangerous Goods Filling" process starting from the EHS-BD module.

This filling process is described here:

But you can maintain the dangerous goods master as well manually (without filling).

During the filling data from REAL_SUB and many other objects is retrieved and mapped to the dangerous goods master.

The "driving" factor of this is a "transport regulation" like "IMDG" (transport sea / international); IATA (Air Passenger / Carrier transport) etc.

To understand the conceps as used by SAP you must read e.g. this online help:

You should have read as well this document:

and this

to get some ideas regarding the concepts as used in this piece of software.

The most important fact to understand is the "material part" and the "packaging concept" which is important to understand the dangerous goods process.

Success Factor 2

Understand the "regulation" first and based on regulation: set up the corresponding Regulatory List" (or use e.g. "Content" from a content provider).


First you should understand how the data is handled/managed to support the end to end process in dangerous goods.

Substance Volume Tracking

Many countries/regions have set up regulations which are quite complex to understand (e.g. REACh legislation). As part of this bunch of regulations: a chemical company must "track" how a "chemical" is used within the company. In most cases the use is related to the process like:

Import the chemical


Produce the Chemical

but you can use to control the Export as well.

Many countries are now starting "REACh" initatives. Therefore: at that point in time as REACh comes in the game SAP has delivered the "Substance Volume Tracking" solution. The design of this solution is flexible and therefore you can support there REACh like regulations e.g. Korea etc. etc.)

BUT YOU MUST DO THAT BY YOUR OWN and SAP is giving you the guidance that the solution is no guarantee that you are "compliant".

Substance Volume Tracking is heavily integrated with SAP SD, MM and PP processes. Therefore: if you have now clue how these processes are designed by SAP and used in your company: DO NOT START !

And keep in mind: Substance Volume Tracking expects High Data quality (Master Data Quality). Most important data is here

    • is the material relevant for SVT?

    • do you have maintained a composition?

    • Is there a registration limit existing?

The options to analyse what is wrong,  why does it not work, why was A tracked but not B are very limited.

And your generate (based on the size of your company and the number of regulations which you try to suport in SVT) a huge amount of data ! especially if you use the software for a long time.

Global Label Management



A list of potential, interesting Blogs (NOT INTENDED TO BE COMPLETE)


LinkTopic of Reference Shipment Shipment Tree set up extraction options in CG02/CG02BD Management Management Management options in GLM options in GLM Packages + Barcode Templating SAP Notes / Helpful OSS Notes learn (for EHS beginners) Asian Languages Basics Volume Tracking Goods Management Career (ho to learn EHS Classic) Goods Management Sharing management Management Management Strategy Management Management Types Strategy handling in SDS/MSDS EHS Set up handling in EHS classic migration using LSMW Page EHS Load options of OCC status of EHS Classic Strategy of BAPIs in EHS Classic in EHS Classic load options Expert Server HANA challenge Regulations how needed a (to be an EHS Consultant) Management Strategy providing distribution Data Determinaton Classic data model Volume Tracking of classification system in EHS of Change numbers Demand Sharing Strategy aspects of EHS classic Exits migration