Hi All,

Our client is using Meridium tool to do Root Cause Analysis for incidents recorded in SAP EHSM.

We have requirement to integrate the Meridium tool with SAP EHSM.

.

We need to integrate these two systems such that we send the data from SAP EHSM to Meridium and get the processed data (Root cause analysis data) from Meridium to SAP EHSM.

If you have any details regarding the interface to connect these two systems will be helpful for us

Hello Experts ,

I created a custom property tree with class which I copy from standard ( say color ) . I  used   the standard characteristics in the custom class and added few more custom characteristics as well . I want to share information on standard characteristics between sap provided property tree sand custom property tree . Any idea , how can I achieve this .

Hello Experts ,

How can we do mass copy functionality in sap specification workbench . Looks like easy experts can only do mass change . Do we have any standard way of doing this or some codes which we can write in rule editor which copies VAT from one place and add to other .

Regards,

K G

Hello everyone,

I hope you are well.

I was wondering if anyone had any insight into this "500 SAP Internal Server Error" that I receive whenever I click on the "Risks" or "Tasks" tab on the Risk Assessment OIF.

Please see the screenshots below and the ST22 error dump attached.

This is an "UNCAUGHT_EXCEPTION", Except. "/BOBF/CX_FRW_FATAL" in program "BOBF/CL_CONFRT_COMPLETE======CP"

We have ran report "/BOBF/CONF_SHM_CHECK" and all checks seem to be successful.

Category               ABAP Programming Error

Runtime Errors         UNCAUGHT_EXCEPTION

Except.                /BOBF/CX_FRW_FATAL

ABAP Program           /BOBF/CL_CONFRT_COMPLETE======CP

Application Component  AP-RC-BOF-CFN

Date and Time          06/22/2016 17:54:24

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Short text                                                                                        |

|    An exception occurred that was not caught.                                                    |

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What happened?                                                                                    |

|    The exception '/BOBF/CX_FRW_FATAL' was raised, but it was not caught anywhere                 |

|     along                                                                                        |

|    the call hierarchy.                                                                           |

|                                                                                                  |

|    Since exceptions represent error situations and this error was not                            |

|    adequately responded to, the running ABAP program                                             |

|     '/BOBF/CL_CONFRT_COMPLETE======CP' has to be                                                 |

|    terminated.                                                                                   |

----------------------------------------------------------------------------------------------------

Dear All,

After creating Action in EHSM - Incident Management, work item is not coming into work overview list for Implementer or Responsible persons worklist. For Maintenance and other notification still configuration is not done but standard action should be notified to implementer.

Any guess....

Regards

Bhuwan

Hi Experts,

Identifier is not filling above highlighted place.

Could you please anybody face the same issue in identifier filling.

Thank You,

Rajesh

Introduction

After using now WWI as a technique to collect data and print the data in a document for some years on a daily basis it is quite interesting to say: there is still some "surprise" possible in using the technique. This document is intended to collect some important topics which may help the EHS community in the future. As mentioned in http://scn.sap.com/docs/DOC-45645 it might be a challenge if you are a beginner in using WWI and you arein charge to develop WWI layouts. Topics like "conditional output", "blank compression" (with or without alternative) etc. might not be easy to understand. Many people do have the trend to  extend WWI layout with "complex" "if then else" logic but may be do not consider that sometimes by simply adapting the maintenance rules simpler WWI layouts or generation variant set up's are possible. Especially the topic of labeling is a challenge as the amount of data which need to be collected, but not coming from SAP EHS, is clearly higher than in comparison to an e.g. safety data sheet (and there are difference regarding set up of generation variant as well). As well the topic of generation variant, language topics, validity areas etc. are "mixed" sometimes in Label content.  If you really try to use GLM solution in EHS you will realize that it is not easy to define "good" solutions because of the complexity of the topic. On the top in most cases you need to print the same information in many languages as mentioned before (and it is not easy to define these languages) on a label and therefore you need additional WWI code to do so and you need to enhance the generation variant as well. And you have with the LabelView on material level and their maintenance an "on top complexity" (especially in context of how to select the right labels to be printed in the different label printing scenarios). On the topic during label generation you have in most of the cases to take care about "Bar code" printing because of several reasons. As well you need to print Batch information on the label, data like: produced on, country of origin etc. which in most cases need to be selected from SAP ERP data.  Regarding Bar Code printing etc. SAP EHS has been enhanced with EnhPack7 as well.

Out of scope of this document is e.g. WWI documents related to "Waste" or "Industrial Hygiene" etc. WWI documents related to these topics might be a challenge too.

Quite interesting is the "application object" as part of the generation variant. Here you have a lot of options to "enhance" / "use" WWI and to enhance CG54/CG50 (but cleary you need to invest in definition of function modules etc.). Especially this object is used in context of GLM.

Many people trend to use "output conditions" (and/or "if else endif"; refer above) similar techniques in WWI as well (you will find a lot of threads in this FORUM dealing with that). Yes it is a nice feature. But the result is, or can be, a challenge (in my opinion) for ongoing support (most important question to take care: why is this data printed and not a different one?). Therefore: if you have the need to use these techniques and you should create a  good (very good !) technical documentation of what you have done and you should train the users and your ongoing support ! You should ask yourself: can I achive the same by proper maintenance of data? Can I use e.g. a rule set to  populate EHS in such a way that I do not need this special WWI technique to show/print something. For those who know EHS it is "quite" tricky to analyze (e.g. via analyzing specification change documents) why this (and not a different) information is shown in the report. And we do not discuss the topic that e.g. a phrase text, code etc. has been corrected/changed or a new/changed identifier is present. A further challenge might be the use of "identification listings" in a WWI report. It can take "hours" to discuss, if needed, why this identifier has been printed and not a different one. If you are using change numbers or e.g. inheritance, status management on phrase level or status management on specification level etc. it can take a while to analyze the content of a WWI report.

Additional challenges in analysing WWI results is that some times you use "identification listing" to retrieve data, or you would like to "hide" data (e.g. Trade Secret topic) or you need to print different material texts depending on print scenario. Please check SAP marketplace etc. For "Trade Secret" a solution package exists.

Some SAP EHS Management Issues

If you maintain identifiers, phrases or user defined text sometimes there is the need to have more than a number of characters (132) to be maintained.If so you start a special editor (you maintain then a "long text"). Based on your general setup of SAP etc. you can use in the text e.g. "carriage return" or other special characters. In the past I was aware of the fact that it is important to use the "right" editor in maintaining the "long text" to generate no trouble in WWI etc. Now I understand "more" the issues and the reasons behind.

Refer e.g. to: abap | saphelpdeskinfo | Page 3; subtopic: "System error when you create new report bodies" or e.g. MS Word as Editor in SAPscript and Smart Forms | SAP Script ABAP Tutorials | SAP Techies

Check as well e.g. OSS Note 559066, 1064655, 990560, 1333100.

IMPORTANT NOTE: the "long text" indicator is not only used to indicate that the text is longer than 132 characters. It can be set e.g. if your text does contain e.g. a "carriage return" (refer to phrase example below). The reason of this is the internal handling of the data in the database.

Out of scope

GLM and other reports as e.g. SOPs (SAP EHS IHS) or WWI reports to be used in the area of Waste Handling etc. are out of scope. Only some "high" level tipps are shown (and links are provided). In regards of Label and the use of GLM check e.g.:  What is a "Label" and how support SAP EHS Management "Labeling"

Out of scope is the use of WWI in context of e.g. new SAP techniques with new UI (e.g. WebDynpro etc.). This can be tricky.

Recommendation

If possible: always use current WWI version on local client and generation servers. With so called GLM+ solution (as part of EnhPack 7) new options are supported in the context of GLM mainly to support printing etc. of labels. Try to make sure that WWI generation servers are always up and running (check WWI cookbook; restart options of WWI services have been improved; performance etc. have been improved as well, and there is now a local WWI DMS available)).

Keep in mind: at least two times per year a new WWI version is available. As well WWI is one of those areas with lot of OSS messages. So you should regularly check SAP marketplace.

There is some indication that based on SAP version and language used (refer to following chapter) there are still issue in data maintenance in "long texts". These issues can then show up in WWI reports as well. Some threads are linked to this document.

Recommendation

• MANDATORY ! READ THE MANY THREADS ABOUT WWI SET UP ISSUES
• READ THE WWI COOKBOOK (Set up of WWI server)!
• Makesure that you understand the difference to local WWI installation
  
• DO INSTALLATION STEP BY STEP AS DISCUSSED IN THE COOKBOOK.
• DO NOT IGNORE CONTENT AND IGNORE ONE STEP.
• Look for Windows/Winword etc. experts (topic of user administration, how to do the "server set up" etc.).
• DON'T IGNORE THE UNICODE TOPIC (RFC CONNECTION ETC.).
• SET UP THE NECESSARY JOBS in SAP system AS DISCUSSED AND REQUIRED IN THE COOKBOOK.

Understand the difference between:

• WWI set up for reports as used for e.g. SDS/MSDS generation/dispatching
• and WWI set up for GLM and other stuff (e.g. WebGui use).
• Understand the different options used for "WWI sizing" for e.g. GLM and e.g. SDS/MSDS
  

KEEP IN MIND: IF YOU WOULD LIKE TO USE OPTIONS AS AVAILABLE BY THE SO CALLED GLM+: take your time to understand the options and the required set up (e.g. printer installation, DMS installation etc.). TAKE CARE IF NEEDED ABOUT WWI COMPRESSION AND REQUIRED SET UP.

Maintaining identifiers, user defined texts, phrases

You can maintain these objects using (if you have the correct SAP release):

• MS Word (The PC Editor (Microsoft Word as SAPscript Editor) - BC Text Processing with the SAPscript Editors - SAP Library)
• using what I call the "graphical editor" (http://help.sap.com/erp2005_ehp_07/helpdata/en/4e/0823e78117001ce10000000a42189c/content.htm?frameset=/en/4e/0825bd8117001ce10000000a42189c/frameset.htm); please check note here: with higher releases of SAP you can only use the Word version and the graphical editor is not supported)
  
• using what I call the "line" editor (The Line Editor - BC Text Processing with the SAPscript Editors - SAP Library)
• and you can "import" these data objects using OCC or EHS standard import
  

If you need more information here check e.g.:

SAPscript Text Editors - ABAP Development - SCN Wiki

BC - Textverarbeitung mit den SAPscript-Editoren - SAP Library

and similar pages.

Based on a recent issue I have learned that (that means e.g. if there is a long text available) the content of the so called "value file" is different or "not normal". Now I have learned the reason behind this is the "handling" of maintenance of these objects and how the data is stored in the database and how they are retrieved and passed on to WWI server/client.

May be check as well: CG12 - Phrase creation/editing - issues

Similar topic: Celsius Degree Symbol (° C) displayed as '#' in SDS for Thai language

But what was the issue and what was the finding?

I have analyzed a WWI report and detected that a phrase is printed in a look and feel which was not normal. A different phrase was printed correct. After some analysis the reason behind that was how (that means by using which SAP tool) the phrase has been maintained in the corresponding language. As you can have the same effect with identifier or userdefined text (the effect is independant of object but related to identifier, phrase or user defined text only) it might be of interest to get more ideas about "what is going on here". In the example in the WWI report a "carriage return" showed up in the middle of the text. Using this example of a phrase (which is related to the old EU labeling system)

I try to explain the issue. By whatever reason the phrase was maintained in the database something like this:

"Extreme risk of explosion by shock, friction,

fire or other sources of ignition"

Therefore a carriage return is part of the phrase text. And in WWI report it will be displayed like it is maintained and therefore in the WWI report the phrase was distributed between two lines (it took me a while to identify this !). Normally the user is not checking the content of WWI layout on that "deep" level but only checking for e.g. missing phrase translations or missing informations. But especially in the context of label printing this might be critical as you print more data  on labels (which are sometimes quite small) in comparison to SDS/MSDS.

Now after investing here a little bit: assuming now that you might use the Word Editor to maintain these objects. Here you can e.g. format the text as "left aligned", "centered", "right aligned", you can enter carriage returns etc. etc. and it is printed like that (what you maintain you will get) in the WWI report. This can be done even if the text is shorter than 132 characters. So the "longtext" indicator does not only indicate if more than 132 are used but the flag is set e.g. if you would format a text like "SAP EHS is a great tool" as right aligned (refer above). (technically: the SAP system is setting the flag if the text need to be distributed on many  entries in the same table; so if you "count" the text characters you get may be 132 only; but if you use "special" formatting sometimes SAP is forced to "set" the long text flag).

This feature might be a "nice" one but can give a number of troubles if you deal with "Labels", "SDS/MSDS" etc. and it is not easy to detect the issue as in CG02 or CG12 it is not detectable easily.

WWI Problems (how to debug)

For analyzing of WWI problems the use of procedures as described in OSS note 959195 might help. A lot of OSS notes exists regarding SAP and use of WWI in context of Unicode especially taking into account the important topic of font selection. E.g. OSS note 733416.

If you detect WWI problems sometimes you have the feeling: there can I start with "debug" to get "ideas" what is going wrong as there is no real debugger in place? One option to do so is: you need "only" to remember the WWI process (and sometimes you should reduce the data shown and maintain only the data which gives rise to problems on some test specifications). In most cases these questions will help to identify the issues (and potential solutions):

1. Is the effect only related to one specification and on a different specification you get the wished result or is it related to use a different language or a special generation variant?
2. Was there a change in layout?
3. Was there a change in generation variant definition?
4. Was there a change in function modules related to customer specific report symbols?
   
5. Was there a change in WWI set up (New WWI version)?
6. Was there a change in Word Version used (locally and/or on generation server)?
7. Is WWI version on server and locally the same?
8. Is wwi.ini on server and locally the same?
   
9. Check if you use only SAP standard symbols or did you enhanced WWI using own symbols?
10. Check whether the effect is the same on dev, test environment etc.?
11. Is layout the same on dev, test, prod enviroment?
12. E.g. on context of GLM: is LabelView maintained the same on dev, test, prod?
    
13. Are the report symbols the same (e.g. no error fix missing etc.) ?
14. Is the effect related to user activities (therefore may be one user does not have same access rights compared to a different one)?
15. Do you have enough access rights to retrieve the data and to display it in WWI report?)
16. The WWI version used on any gen server of dev, test and prod is the same?
17. Is the data record (which should show up in WWI report) "active" (active indicator is set per rating/validity area combination)
    
18. Does rating of data record fit definition of generation variant?
19. Does validity area of data record fit definition of generation variant?
20. Etc.
    

If you use e.g. "Create report from template" a number of files are downloaded to your client (if you use a local WWI installation !). These file can be classified as:

• the value file
• the layout file
• and some control files
  

After the process is ready a new file is available (the final WWI report with the data). As in the "Report from template" process you can fill in the parameter symbol data as well we can define the resulting file as the "Final Report" and not the "Raw Report". Only if you do not enter any parameter data then you generate a kind of a  "Raw report".

Now if you carefully execute an analysis of e.g. the value file in many cases you can learn a lot (you need a suitable "text file editor" to do so ! WinWord etc. is here of no help). As well the content of the control files can give you additional hints and may be afterwards you understand "better" how the process is designed (on high level).

Keep in mind: in most of the cases we have two steps to consider:

1. Generation of a raw report
2. Generation of the final report
   

In step 1 you will get a value file and in step 2 you will get a much smaller value file (in most of the cases). If you use CG42 and check the "tmp" directory (as explained above) you will realize that there is "temporarly" a structure file generated as well in the folder. Checking this you might be able to understand better the WW report layout process.

Generation variant

By clever use (definition/set up of generation variant) you can make sure that only the relevant data sets are pulled by the WWI process. One important topic to consider here is the "Rating". Using the Rating (and by clever data maintenace) you can avoid to use complex conditions in WWI logic. Clearly there is a "con". You need to may be prepare suitable additional ratings and you need may be adapt your access concept and clearly your maintenance concept need to be adapted as well but WWI logic will be simpler and in most cases "ongoing" business might be simpler (support topic of endusers). What you need ot pay attention is: the "rating" does have effect on any data of interest ! Don't forget that. In most cases you need identifies, value assignment data.

Keep in mind: the validity area topic is "special". Depending on the settings used (related to the validity area) in the generation variant the data selected is / might be different.

This is not  only related to the generation variant but how you use EHS at all. Remember that you can use as the validity area (if needed) e.g. plant codes, company codes etc. (as long as the information is CHAR10 or smaller). Can be a quite useful option to use this type of validity area (e.g. plant code, company code etc.) but you need to pay attention here in your maintenance concept in CG02.

So in theory you can maintain e.g. a "color" in CG02 based on plant codes and not on validity area which are based in most cases on "countries" (you can e.g. have more than one plant per country or validity area). E.g. you can use other options as well. E.g. you can use the value "TEXAS"; therefore you can use "subregions" of a country etc. Keep in mind that by using the validity area you can create "regions" as well. E.g. you could define: REG_NAFTA (containing e.g. US, MX, CA...) or similar validity areas. Keep in mind that REG_WORLD is special  ! and you should not change here standard SAP set up.

Validity Area

Keep in mind, that you can use "PLANT'S" or other objects as "Validity areas" as well. As long as the technical key of the object is not longer than 10 characters you can use this option (e.g. you can use a "company code", "Plant code", "sales org code" etc. as validity area: PAY ATTENTION IN USING THIS FEATURE IN WWI context. It should work ! but the "REG_WORLD" one "special" solution does not apply any more.

Languages in Generation variant

As you know: by clever use of "G repeating" groups and the defintion of the generation variant you can print in one WWI report data in more than one language. But keep in mind: the report it self does have always a "leading" language. This topic is explained here: Editing Ratings and Validity Areas for Generation Variants - Basic Data and Tools (EHS-BD) - SAP Library

As this type of demand is related to the "Repeating group types" should should read this chapter of SAP Help: Repeating Group Types - Basic Data and Tools (EHS-BD) - SAP Library

A good example of the use of a "G Group" is shown here: Example: Repeating Group of Type G - Basic Data and Tools (EHS-BD) - SAP Library but you should have read as well this: Taking Validity Areas into Account - Basic Data and Tools (EHS-BD) - SAP Library

Language topics in general

You can prepare a suitable SAP set up in such a way that different log on languages are supported as well as different e.g. phrase languages. Keep in mind: WWI report to print data using arabic, hebrew etc. are "special" language (written from right to left and not Left to Right). Here the "printing" of data might be a challenge with WWI.INI, Font selection and WWI layout definition. You should avoid to mix in one WWI report languages with "left to right" and "right to left" writing. You can do this, but the WWI code which comes up is complex. A lot of OSS notes are available regarding topic of right to left languages but as well regardian asian like languages so may be check SAP marketplace (e.g. current WWI supports much better now asian characters).

Label Wizard

The topic of the use of the "Label wizard" is explained here:

Using the WWI Label Wizard - Basic Data and Tools (EHS-BD) - SAP Library

in chapter "Using the WWI Label Wizard". Therefore if you have use the Label Wizard and then check content of WWI document in CG50/CG54 the labeling tool is started. Further information about that can be found here: Using the Labeling Tool - Basic Data and Tools (EHS-BD) - SAP Library (Chapter: Using the Labeling Tool). Once again: by "clever use" of the application object you can "restrict" use of generation variants etc.

If the label Wizard has been used, the corresponding raw report in CG54/CG50 will be displayed using a different icon in the report tree.

General topics

In different threads it has been asked how to generate WWI there "nearly" no data is coming from EHS core but nearly 100% is coming from other SAP modules and how to do it. I am sorry to say:

1. Even if you do not print EHS core data you need always a specification to make it happen
2. As well you need always a generation variant
3. and a WWI layout
   

A lot of options exists in EHS to support this type of demand. That means e.g. you need reports (in most cases Label reports) as part of the GLM process and you need as mnetioned above therefore one specification as without it will not work. One nice option to support this demand (and may be not well known enough) is the "Reference" as part of the report header. By using this option you need to generate only one released WWI report and can use the "reference" option to make this report valid for a lot of other specifications.

About Change Marks

Do you really understand the topic of change marks in WWI reports? Pay attention: SAP has improved this and some optimizations are available by using EnhPack 3 as well. Most people have really a big problem in understanding how "Change Marks" are coming up/handled in WWI reports. From experience: most user (even key users) do have problem in understanding the "Usage" and the effect of that on data retrieved (in context of generation variant) and the Change Mark as such (as well regarding "WWI.INI") and how it works. As mentioned SAP has improved this; but to a certain extent: it is now complexer as before !!

Let us start high level: to support the "Change mark" you need to "tag" the generation variant. Check e.g. WWI for Beginners and chapter "Change Mark" or the SAP online help.

The next story starts with "Data maintenance". Here we need to differentiate the "type" of data. As you know: in most cases data is retrieved from database using value assignment types "A" (Class type), "B" (Specification Listing), "C" (Composition data) and the special DG data.

You might think "A" is easy to understand in how it works to get a "change mark". You are wrong (to a certain extent). Let us differentiate first the different data situations:

a.) REAL_SUB does have "local" data

b.) REAL_SUB does have data coming via "Reference"

c.) REAL_SUB does have data coming via "Inheritance"

In case of a.): if you are not using the enhancements coming with EnhPack 3 story is "simpler" (but not easy). By using the "Relevance indicator" you can steer if a change mark should show up or not.

In case b.) and c.) the story is more "complex" as the data is coming from other sources. Honestly I did not have execute a new analysis of the two cases: but keep in mind: on REAL_SUB header: you have new "flags" now (using higher SAP ERP versions) and therefore we have two "subcases" to discuss:

1.) You enter for the first time a "reference/Inheritance" on header level

2.) you cange data on "source" level (e.g. REAL_GRP) used by the REAL_SUB

So the "change mark" can be quite tricky in this context.

For value assignment types "B" and "C" the story depends on how you have defined your WWI layout. And it can take you days to get an idea why in this case a "change mark" is shown but not in the other case.

Let us make a "primitive" example of value assignment type "B". In most cases this is used to show up identifiers in WWI report (other options are possible as well).

Let us imagine that on REAL_SUB level you have prepared a data record with three components and you get e.g. a CAS number in the WWI report. Now you must enter e.g. a fourth component. What should now show up in the WWI report (which "line/text" should be marked as "changed")? High level the optimal solution would be to get a highlighted CAS number only coming from the forth new component (it is a relevant change). It is not easy to achive this.

And let us imagine now that you need not to print any more three CAS numbers but only two (delete one specification). How to show it in WWI report? I would assume that this case might not come up often but most of the companies will have a different solution to make clear (to the customer) the difference in the new report in comparison to the old report.

Honestly: you can really write a "Book" on that and the challenges therein only explaining something which might look simple. So it is a good idea to prepare some guidelines company internally to make sure that the look and feel regarding "Change marks" is the same considering the whole product portfolio.

Further documents which might help

As an example: Refer as well to these documents:

Application Object

The application object is part of the generation variant. A generation vairant can have one or more than one assigned application objects. Normally you need not really investigate here to understand the use but in some circumstances the use of this object can help handling to detect the right report. This is shown e.g. in SAP Online help: Defining Application Objects - Basic Data and Tools (EHS-BD) - SAP Library Chapter "Defining Application Objects" Here as well you will find in chapter " Example: Using Application Objects" an example how you can use this option. By using this approach you can enlarge the selection options of CG54 and CG50 if needed (but you need a good and robust approach to do so !) but you have as well influence on WWI content (data content) if needed.

In general: CG54 and CG50 contains some "UserExits". These are listed here: http://scn.sap.com/docs/DOC-41655. Therefore it is quite easy to enhance CGC50 and CG54 by these exists. But the use of the "application object" and anything related to that can enhance these transactions as well. The UserExit approach is more "general" and enhances CG54/CG50 on a general level. The use of application object (LABELSTOCK) is in many cases related to GLM topics.

WWI structure

Long ago I planned to start a similar document based on a thread: http://scn.sap.com/thread/3431722

Here some interesting question was raised: what is a report symbol type? How can they be used to enhance WWI? And why can I (as a developper) not use all of them ? And how are those report symbols used which can not be used by the developper (there must be a reason why they exists). Up to now I still only enhanced the thread mentioned with some answers I found. But up to now I did not have had the time to investigate further. Now based on the new informations may be It is time to go on here, as this "report symbol type" is related to how WWI internally is designed (in SAP) and how you can enlarge WWI. Clearly: it is not the aim of this document to explain all (That means the whole WWI process; this would take a book to do so) but some ideads should be listed which might help you in the future.

From high perspective we can split the WWI process in two parts: one part is related to the "collection of data" (which is done within SAP) and the other part is related to the topic to show the result in a proper way (that means to create the report on WWI server with data, applying font selection etc. etc.). If a WWI report is created in the database we have to consider a third process part but this is only an SAP EHS internal "handling" as the WWI process is finished an only the result should be stored.

We need to remember in this context that e.g. in the raw report only report symbols and phrase symbols are retrieved and no parameter values. This is a very important concept as well for e.g. SDS/MSDS generation or to some extent for Labels as well. Therefore we have to differentiate between a value file of the "raw report" and the final report. Regarding this and GLM: may be refer to Logging in Global Label Management - Global Label Management (EHS-SAF-GLM) - SAP Library; chapter "Logging in Global Label Management".

On high level: the process "Create report from template" and "Create report" is the "same". That means there is "no" difference in how SAP is collecting the data but only how the WWI process is started. "Create report from template" uses in most cases a local WWI installation (with higher SAP releases you can use the WWI generation farm as well) and "Create report" uses always the WWI generation server farm. A further difference is, that the "Create report" process establish new entries in SAP tables (e.g. ESTDH) and the "Create report from template" process do not generate these entries.

Be aware of the fact that based on GLM set up GLM can behave different regarding the generation process of WWI reports. Check e.g. Label Generation - Global Label Management (EHS-SAF-GLM) - SAP Library

Chapter: Label Generation

Based on the discussion in the thread mentioned above I believe this help page of SAP is quite important as a "starter" to talk about "report symbol type".

Document Template Objects - Basic Data and Tools (EHS-BD) - SAP Library

Check Chapter: Document Template Objects

As well this SAP Help Link is important: Process Diagrams for Report Creation - Basic Data and Tools (EHS-BD) - SAP Library

Chapter "Process Diagrams for Report Creation" which is really a "must" to read to understand the WWI process (on high level).

Still some very good documents exists in this FORUM dealing with report symbol generation etc. This documents will try to go "deeper" and is related more to the content of the value file.

Use of WWI in context of e.g. Recipe Management

For those who would like to learn about WWI "more": this nice document can provide some input how to generate a WWI document with own ABAP code:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b85f25-d99f-2e10-b8a2-96e0b54cccdc?overridelayout=t…

By studying this nice ABAP example may be you can create your own code etc. (e.g. as an UserExit in CG02/CG50/CG54).

Use of WWI in context of GLM

For those of you who have the need to take care in regards of WWI development in context of GLM: the WWI layout (and GLM design/print process) is one of the most complex one in EHS area. Many people mix "language" and "validity area" topics; pay attention that you should not mix (topic of "G repeating group") these two terms. This special technique (use of G group) can increase the complexity of your WWI layout a lot and in combination with the topic of generation variant it can be a disaster.

Recommendations for WWI development

• don't use complex data models so that the logic "which data to display" is part of WWI layout (e.g conditional outputs) (and if there is no other option than to use complex WWI layout. creste good documentation !)
• Try to use as much as possible as selection criteria "Rating/Validity Area"
• Try to avoid of complex "if/elseif/else/endif" conditions
• Only use customer reports symbols with new function module if there is really no other alternative
• Check language dependency ! (G groups etc.)
• avoid logics like "if value in value assignment X = A then print value from value assignment B"
• Use the "stack" option only as the last option to solve the demand
  

WWI basics

May be you should read cross as well these SAP Help Chapters:

Structure file

The topic of structure file is mentioned as well in SAP Online help. Refer to Process Diagrams for Report Creation - Basic Data and Tools (EHS-BD) - SAP Library. May be as a starting point check these links:

ESTLS EHS: Report Template Symbol - SAP Table - ABAP

SAP Table ESTLS - EHS: Report Template Symbol

Therefore this "structure" file topic is an important link between WWI layout and how SAP will retrieve later the data (based on definition of generation variant as well and how the data is maintained). May be check as well the "same" topic in context of import/export of report templates. Here the layout is exported/imported together with symbol definition (therefore two files are generated/processed).

The table ESTLS therefore containes the symbols as used in your WWI report.

E.G. Check:

Therefore to understand the use of the "report symbol types" etc. it is a good idea to check the content of this table for one WWI report (you need to specify the version of the WWI report layout).

In doing so you can identify if or if not report symbols of type:

1. Phrase
2. Specification
3. Parameter
4. Descriptor
5. Standard Repeating Group
6. Special Repeating Group
7. Blank Compression Group
8. Optimized Repeating Group
9. IF Repeating Group
10. Template
11. Version Information
12. Language Information
13. Language Switch
14. Generation Date
15. Control Command
16. Comments

are used in the WWI layout. By digging deeper you will identify very easily why may be a report symbol type is part of ESTLS especially if you look at the WWI report layout definition. This can really help in such a way that you understand the "WWI layouting" topic and the use of report symbol much better.

Value file

The topic of "Value file" is mentioned in SAP Online help: Examples are:

EH&S Native Language Support - Basic Data and Tools (EHS-BD) - SAP Library

Chapter: Value file

Or e.g. http://www.erphome.net/plm_concept/content/data/EH_S/FactSheets_WhitePapers/CINativeLanguageSupport.pdf

Chapter: WWI Generation Server

Attached is a list of function modules or references which might be of general interest.

WWI/Important OSS notes

According to analysis of EHS Forum one of the top 10 issues is the handling of WWI (how to install, proper setup, how to update etc.).

Keep in mind:

- WWI is solution based on software provided by Microsoft

- It uses as operating system "Windows"

- It uses WinWord as application (formatting etc.)

Therefore may be this list  of most important OSS messages might helpt (will be enhanced may be):

General links of interest

WWI / RTF

Keep in mind: WWI is only a tool on the top of Microsoft Word. Here we deal with "RTF" code, Therefore sometimes it might help to know about "RTF". Therefore check recent version of that: Download Word 2007: Rich Text Format (RTF) Specification, version 1.9.1 from Official Microsoft Download Center

There are a lot of "online" Tutorials available on the top in Internet as well. With higher WinWord version RTF is only available because of portability etc. but will not be enhanced further.

Further tips and tricks regarding "test" scenarios

If you use only "standard" options in WWI you need not to prepare "sophisticated" test cases. But if you use e.g.:

1. if else symbols, condition type symbols
2. parameter symbols
3. discrete validity areas
4. phrases with refernce to  graphics files
5. WWI code with reference to user defined texts
6. WWI code with reference to documents stored in user defined texts
7. etc.
   

it is "good practise" to prepare suitable test cases. Especially in the area of GLM this is not easy. But the same is true if we talk about an eSDS.  Here you need really to prepare very good test cases (as more as better). Therefore you should have test cases on more than one specification to prepare. You should "play" around e.g. if you with more than one data record (using active flag), you should "change" the sequence of data records, you should check for the" if" conditions (and blank etc. compression as well). Some times only by using special data situation you will detect that you have a problem.

WWI issue: E302 RTF value in value file is corrupted

Error while proccessing print preview

Error in Report preview

Error when creating a WWI report for a particular specification .

Issue in Generating label in WWI

The "handling" of the correct WWI template on dev, test and prod environment might be an issue as well. To document WWI template content is not easy and to identify useful options (e.g. in Word, EXCEL etc.) to describe the WWI layout might not be easy but a very goode idea as it helps you to handle the "versioning" and identification if "content" differences. Keep in mind. Sometimes you are not changing the WWI layout but only execute "bug" fixing in function module to retrieve parameter symbols.

Cover Letter

Cover letter topics are not discussed often here. Somt threads are listed here only as an example:

Coverletter - Output of material data

Re: How to Create/Change Coverletter in MSDS

Parameter Symbols not appearing in Coversheet and/or Acknowledgement Receipt

How to create Cover letter

Cover letter design might be a challenge as well. One need to understand the existing parameter etc. symbols; how they retrieve the data from which infromation etc. and in CVD1 you can not see the "final" cover letter report. This is related to the expansion time of th symbols used. Only e.g. phrases are available in the report. In most cases you get the final cover letter report only in case if dispatching. Therefore is is not easy to identify errors etc.

Very special WWI techniques

Because of new threads discussed a new document has been generated which might be of interest. May be check: SAP EHS MANAGEMENT FOR EXPERTS

About "Includes"

Currently I believe we have some "suboptions" options to use "INCLUDES". Examples of discussion of includes are: WWI - Include functionalityand e.g.:

• Windows Wordprocessor Integration (WWI) - Basic Data and Tools (EHS-BD) - SAP Library
• Inclusion of Document Templates - Basic Data and Tools (EHS-BD) - SAP Library
• Creation and Use of Building Blocks - Basic Data and Tools (EHS-BD) - SAP Library

To use this functionality need some "preparation" (Business/IT Blue Print). First: the "total" layout expected should be "large" enough (e.g. like SDS: having 16 chapters for UN version). Second: the layout should have some "organisation" structure as e.g. "paragraphs/chapters" or other structures (e.g. in context of GLM labels you can think about "design elements"). Clearly the use of this feature does have pros. In some thread it has been explained that the use of "Includes" can have "cons". The con is especially some effect on performance (which was discussed in one of the threads as mentioned). If you are planing to use this option you should do a good test before you go live. Experience has shown that the use of includes is not easy and sometimes data constellation "crashes" the WWI process. On the top the use of includes is "more" sophisticated if you think about "dev" => "test" => prod" (that means you need to pay more attention if you move the layouts within your system architecture. But especially the use of the "Building blook" principle seems to have some advantages.

Important threads in this FORUM

Examples of threads dealing with "special" WWI topics (only listed those which might be of general interest) which are addressed often in this FORUM etc. I have tried to create "subtopics" so that may be you can find "easily" a suitable thread in this FORUM. I have done a "subselection" of topics discussed in this FORUM which may be help WWI Experts in their daily work. Especially regarding GLM topic (e.g. Bar Code printing) you will find a lot of more threads.

This is a list of links to SAP help. Additional some add on links are shared:

This list of threads is only a collection of discussions in this FORUM. In regards of topics to discuss in WWI development area it can never be complete. The topic of WWI can be rated under the "top 5" which are discussed here.

Genifix (and other quite special stuff)

There are some threads existing discussing "Genifix" a solution which is not available any more. Examples are:

Genifix / Current WWI version / Options?

Use of WWI functionality for customer programs?

Especially the last thread is worth to look closer.

If you do a kind of research you will find e.g. these standard function modules:

C12H_WWI_DISPLAY_WEBGUI

C12H_WWI_DISPLAY_DIRECT

C12H WWI DISPLAY WINGUI

You should analyse them and the different use of them. Important: if you plan using WebDynpro application then you need to look for the "correct" function module to read and display the document

Set up of local WWI

There are some threads here discussing theneed to install WWI locally (on client of SAP Gui). These are the examples:

WWI.INI / Some questions

CG42 templates will not display after Office 2016 update

Using the existing SAP options: to use the approach to avoid local WWI installation can be a good idea (only for layouting purposes you need then a local WWI). The pros and cons of this options are:

- no need to take care of any kind of WWI roll out including graphic files etc. for local clients for most of the SAP users

- no risk for local PC regarding wrong WinWord version

- You need more generation servers (may be)

The issue is: we don't know many users would like to use the options e.g. as "Report from template", "Report information system" and "Report management system" at the same time.

For using this option: you must activate Business Functions of EHS as part of EnhPack 3.

DEAR ALL

PAY ATTENTION: Because of lack of time: i will just add further "threads" links if needed and not try to make the link in the right "chapter" (to get some grouping or to do regrouping). There are to many discussions in context of WWI running here.

Status May 2016: I used term "wwi" as search criteria. There are rougly 73 pages coming back (each page with roughly 10 threads). So please uset the search option. There is a good chnace that your topics was discussed in the past.

Please use the "search" function in SCN to find suitable threads.

Collection of other WWI related documents

Hi Experts

Can anyone please tell the step by step procedure of Waste management & recycling

How its work ?

What to create first ?

Step involved in Waste Management & recycling ?

Example in MM : -

First Create PR - Send RFQ - Collect Quotation from vendor - Price Comparison - PO - Release PO - PO Send to Vendor  - Material Receive - GRN.

In the same way can any one tell the process flow & what are the things we have to maintain for it

Example for PO

Need Company - Plant- Pur Org- Pur Group- Vendor - Materail - Storage Location

In the same way can any one tell the what to create for completing the proceed like e g : what is container & use of it y we create & where to assign it

Please revert back waiting for your reply

Regards

Idrees

Hi Gurus,

Status Schema for Change Request - SAP Management of Change - SAP Library

I want to add new status in the MOC Change Request Life Cycle.

I checked in spro customization and a few view clusters for SAM settings but I did not see where these settings are made.

Please let me know where/How can I do that. Any help will be appreciated.

Thanks in advance.

Dear Experts

I would like to know how to make characteristics invalid / how to delimit the characteristics so that they no longer appear in the transaction.

I tried to delete the characteristics, however, it wont allow me to delete them due to assignments.

Thanking you in advance for your time and assistance in helping me resolve my request.

With Kind Regards

Miss Nash Govender

Hi Experts ,

Does anyone has experience the logic used to output section 8 in wwi ?

Can anyone suggest how SDS authoring can be done through sap erd more efficiently ? With the new updates on content , how can we trigger to re author based on the changes coming from the content provider and to be upto  date with the new regulations . What are the other different ways of authoring msds in sap ?

Can someone help me with t code for reach module which usually starts with /n/...

Hi all,

I am trying to change a list of phrases Phrase group, and i am trying to do this by uploading the phrase DAT file, which reflects the new PHRGRP. The new PHRGRP exists in the phrase library.

However, after the upload, the phrase still belongs to its old phrase group.

Does the phrase loading program not update the PHRGRP?

thanks,

Scott

Hi All,

In the Engineering Record,We have an option to get change log for header status in the additional functions.

In the same way ,I need to show a log history for all the header data & the Change Items( for Recipe,Specification,Material ,Material BOM & Etc ).For this a new custom function will be added to Additional Functions and it should give the detail like below template.

Thanks in advance for your help.

Regards,

Mahendran

Hi,

Is there a way to amend an existing label printer that has been created on SAP?

Whenever I receive a request to add a new label printer, it is passed to our  SAP Wintel team for action.

After I've received notification it's been added, I then go into transaction S_SH8_84000394 to transfer the label printer.

Is there any way to apply a change within the transaction S_SH_84000394? I can't seem to make a change and wondered whether:

1) it cannot be done using this transaction

2) SAP Authorisation need to change my level of access within S_SH_84000394 to enable this feature

3) Delete the printer altogether and start again?

Thanks a lot.

Maria

ie are implementing SAP EHSM on netweaver portal, we facing a lock issue / cache issue in our QA system. The first incident opened after logon keeps opening regardless of the incident chosen on the initial entry screen. Also we are observing that the locks are not cleared in the backed ECC system even after logoff.

This issue doesn't occur in our dev system (which is a single instance), the issue is happening only in QA system (which is high availability). We are close to go-live any help in this regard would be appreciated.

Thanks!

Bharath

Introduction

It seems to be that it is time to have a document in place for beginners in SAP EHS Management. This FORUM has showed that there is a regular need to support beginners. On High Level the most important Tipps and Tricks or Information should be collected and published. On regular basis this document will be updated.

Please check as well on regular basis the FORUM SAP for Chemicals

You will find there a lot of helpful information as well. On top check: Sustainability & CSR

and take a look as well here: Product Compliance

Introduction / Career

On regular basis questions regarding how to start an EHS/EHSM career are coming up. Please use the "search" option in SCN to find threads regarding this topic or check the SCN Career platform. If you just "google" you will find a lot of job opportunities on functional, technical or manager level. 

Please check for Career options: Career Center

You will find a lot of similar threads e.g.

SAP EHS Functional Consultant Role

What career in working as ABAP developer in EHS module?

SAP-EHS for Safety Officer (Oil&Gas) with BSc.Computer Science graduation

SAP GDC Hiring for SAP EHS Consultants - Bangalore Location

Need Expert Advise

ATTENTION: A NEW SECTION WAS ADDED. You will find additional links (EHS training, how to start EHS career). PLEASE CHECK !

As SAP HANA is as well a suitable approach which will be used more and more by SAP customers: a number of documents in context of use of EHS/HANA can be found using an inquiry in SCN; some of them have been now added in the document list. It can be expected that SAP will invest a lot of money and time to enable EHS to be used in SAP HANA context; SAP ERP 6.0 EnhPack 6 is released to be used with SAP HANA).

Currently there is a high interest in "Component Extension for SAP EHS Management". This product is/has been enhanced in the last years a lot and SAP is using this new platform to reorganize old solutions which are still available as well.

S/4 HANA

SAP goes on with the generation of new solutions and with a consolidation of solutions. S/4 HANA will be the successor solution of SAP ERP / SAP Business Suite etc.  Pay attention:

• EHS Waste is NOT supported in S/4 HANA ==> NO SUCCESSOR SOLUTION AVAILABLE
• EHS IH is NOT supported in S/4 HANA (you must switch to EHSM)
• EHS OH is NOT suported in S/4 HANA ==> NO SUCCESSOR SOLUTION AVAILABLE
  

You willl find very helpful OSS notes and other documentaiton on this in SAP marketplace. Some discussion regarding this is still running in this FORUM. We need to wait now how SAP will consolidate the existing SAP EHS solutions in S/4 HANA.

Sustainability

SAP EHS Management as described here:

http://www.sap.com/solution/lob/sustainability/software/ehs-management-health-safety/index.html

and here

http://help.sap.com/ehs

is part of a bunch of applications of the SAP Sustainibility approach as described here:

http://www.sap.com/solution/lob/sustainability/software/overview/highlights.html

and here

http://www.sap.com/corporate-en/sustainability/index.epx

Training/Certification

• Trainings are offered e.g. by SAP or by other providers  (please check e.g. https://training.sap.com/v2/course/sus310-sap-ehs-management---essentials-and-functions-eef-classroom-096-de-de/)
• There is no certification available regarding SAP EHS Management
  

SAP Marketplace

SAP EHS Management can be found easily in SAP marketplace. You can search for OSS Notes, try to understand differences between different SAP releases (e.g. based on different support package etc.)  and try to understand the use of Business Functions in SAP EHS Management.  Most important are OSS notes of type "Consulting", "Additional Information" or which deals with upgrades/updates.

Be aware of the fact that depending on the license you have SAP EHS Management contains "more" or "less" software (please refer to discussion as part of this document).

There are some "must to read" OSS notes available regarding e.g.

1. WWI Cookbook/WWI Setup
2. Report distribution
3. SVT installation
4. Component Extension for SAP EHS Management (Installation/Migration topics etc.)
   

Regarding some other stuff you will not find suitable consulting OSS notes (e.g. DG related topics etc.).

SAP Licence model

SAP EHS Management is part of SAP ERP (if we talk about EHS classic).  To understand the SAP license model is not easy. Therefore use your SAP contacts for help to get better understanding. E.g. Component Extension for SAP EHS Management is still an "add on" to SAP ERP. But this is only the "technical point of view". The license perspective can be different. PAY ATTENTION: SAP is going on to align the current license strategy taking into account future enhancements of the software solution (software solution bundle).

Overview about SAP EHS Management solutions

If you check this link: SAP Environment, Health, and Safety Management (SAP EHS Management) – SAP Help Portal Page

SAP defines the solution as:

SAP Environment, Health, and Safety Management (SAP EHS Management)

having these subcomponents or solution options:

• Component Extension 6.0 for SAP EHS Management
• Mobile Apps for SAP EHS Management
• SAP Environmental Compliance 3.0
• SAP Product and REACH Compliance 2.0
• SAP EHS Management as Part of SAP ERP
• SAP EHS Regulatory Content
• SAP Product Stewardship Network
• SAP EHS Regulatory Documentation OnDemand
• SAP Energy and Environmental Intelligence 1.0, Powered by SAP HANA

Discussions in many threads etc. has shown that this structure is not well understood. On top the community does have problems in differentiating "license topic" (how to get the software) and SAP software set up (which software must be downloaded, installed etc.)

Most of the threads in this FORUM are related to these topics:

Many persons acting in this FORUM asking to get a "functional overview" regarding these solutions especially focusing on the differences between the solutions but as well on the overlaps existing to get a better picture which process is supported by these solutions. If you check "simply" the corresponding SAP Online help the high level difference is obvious. But for some other topics you need to drill down more in SAP Online help.

E.g. check: SAP EHS DISCUSSIONS !!!!: January 2009

For those who are interested: if you just google you will find lots of videos and other related stuff of any kind of quality etc. Some are good, some are "nice" etc. So check YouTube as well !

SAP EHS Management Core Overview

Check e.g. these links:

SAP EHS Management Core

SAP EHS Management is implemented as a SAP Extension in SAP ERP solution from technical point of view and therefore you need to prepare SAP ERP system and activate the extension before you can use SAP EHS Management. And there is some "afterwork" to be done to start with EHS. On SAP marketplace there exists some OSS notes referring to this topic (e.g.: EH&S installation: Composite SAP Note or more special: Composite SAP Note: Relevant notes for EHS dangerous goods ). After activation and if you use recent SAP release (actually SAP ERP 6.0, Enhancement Package 7) you can activate further EHS relevant business functions. Not in all cases SAP is delivering here "default" implementations regarding the extensions as part of the Business Functions. During some upgrade projects (which have been mentioned here) e.g. issues come up in e.g. Dangerous Goods integration. So you should read carefully anything which you find on SAP marketplace. In context of "Component Extension for SAP EHS Management" you will find lots of information in SAP marketplace (e.g. master guide to install the software; migration aspects etc.).

SAP EHS Management

There is no version number used in context of SAP EHS Management any more. It is part of SAP ERP. But there is some "conflict" with naming convention by SAP. Now SAP delivers as well a "Component Extension 6.0 for SAP EHS Management" (currently: roughly any year a new version is delivered by SAP) which does have actually a version number but is not the same as SAP EHS Management classic. As mentioned above: This solution is to my knowledge not part of SAP ERP but installed as an "add-on". We can expect that may be SAP will change this in the future (as has been done with EHS classic).

Component Extension is sometimes abbreviated as "EHSM" sometimes SAP EHS Management is called "EHSM".

From technical point of view: you can not compare the old SAP EHS Management classic solution with the Component Extension for SAP EHS Management solution.

On the top there is still a version number used in context of the "SAP Product and REACH Compliance" solution (actually version 2.0 is the recent/current one).

v what will happen with the SAP Product and REACH Compliance Suite on long term; but it can be expected that this solution will be mapped (may be) to Component Extension Solution if time goes on.

NEWS NEWS NEWS

It seems to be that there will be a new book to come and in  english ! "Incident Management with SAP EHS Management". According to the link identified: you can now ! dowbload the book. Please check: ISBN 978-1-4932-1330-6

SAP Best Practices for Chemicals

The use of the SAP Best Practise approach as shown here: http://help.sap.com/bp-chem can help to speed up if there is the need to prepare a "general" set up regarding SAP EHS Management.

The topic of "Best Practise" is mentioned often together with links to the documents. So please check this FORUM. Keep this in mind: not for all of the SAP EHS solutions you will find a "Best Practise" and in most cases the Best Practise approach is only providing you an idea: how to do the job; in most cases the discussion of gaps etc. can take lot of time.

KEEP IN MIND: SAP is not delivering e.g. WWI templates for MSDS/SDS or other similar stuff (you get some examples). You have to do the job by your own (same for rule sets and a lot of similar stuff);

KEEP IN MIND: using SAP EHS software the system is nearly "empty" (ok: some basic customizing exists if you have done set up properly); therefore establishing phrases and other important business content must be done by YOU !!

PLEASE CHECK LINK: What is the main difference between product reach compliance and product safety stewardship

PLEASE SEARCH FOR (using e.g. google) E.G. using term "SAP Best Practices for Environment, Health and Safety Management", with "Solution Scope Document".

What is new in SAP ERP

Please check e.g. What's New in SAP ERP - SAP ERP - SAP Library

You can then drill down by SP (support package) and Enhancement package. Might be helpful

The "management story"

Recently a number of documents has been generated which are dedicated for "Management purposes"

Just check: Strategic Imperatives for the Chemical Industry – Part 9: IT Strategy, Alignment & Delivery

You will find reference to additional documents

"Naming conflict"/"History"

Years ago there was a different term used in this context: "EH&S". Generally you should now always use the term "SAP EHS Management" and you should not use the term EH&S any  more.  But you need take care regarding this "naming". In most cases: if term EHSM is used then you can think about: classic EHS together with Component Extension. But sometimes people use the term EHSM for the "Component Extension" part of the software solution. If EHS is used most of the people talk about EHS classic (refer to comments/discussion in this document). Sometimes "problematic" is the discussion how "SAP Product and REACh Compliance Suite" is related to that. Here we have in most case two perspectives: topic and status of your SAP license and topic of software architecture etc. As SAP is still adapting/improving their license model no clear answer might be possible. Therefore: make it simple. Just ask SAP about your status and how to extend (if needed). From software point of view: "SAP Product and REACh Compliance Suite": this is an own software layer (on the top) to SAP EHS Management classic. And there is a trend to move functionality from SAP Product and REACh Compliance Suite into the new "Component Extension" solution. Currently roughly any 12 - 18 month a new "Enhancement Package" is delivered by SAP to add new functionality to SAP ERP.

History of SAP EHS Management

SAP EHS Management is now part of SAP ERP as an extension. In former times SAP EH&S (name used in the past) has been developed by TechniData and was implemented as an "add on". Here a short list of history (not intended to be complete)

• Completely part of: SAP ERP 6.0 EnhPack 7
• Completely part of: SAP ERP 6.0 EnhPack 6
• Completely part of: SAP ERP 6.0 EnhPack 5
• Completely part of: SAP ERP 6.0 EnhPack 3
• Completely part of: SAP ERP 2005
• Completely part of: SAP ERP 2004
• SAP EH&S 3.2 (SAP Enterprise Extension 2.0)
• SAP EH&S 3.1 (SAP Enterprise Extension 1.1)
• SAP EH&S 2.7b
• SAP EH&S 2.7a
• SAP EH&S 2.5b
• SAP EH&S 2.5a
• SAP EH&S 2.2b
• SAP EH&S 2.2a
• SAP EH&S 2.1b
• SAP EH&S 2.1a
  

For those who love history here some links (you will find may be more of that type):

May be check this link:

http://www.stechno.net/sap-notes.html?view=sapnote&id=122400

or the SAP note: 122400 which provides an overview about SAP EHS "classic" installation.

For those of you who are in charge of "managing" an SAP EHS system: Refer to SAP note: 1870650.

E.g. SAP EHS DISCUSSIONS !!!!: Missing Value assignments under property tree or similar links might be of interest as well.

Books regarding SAP EHS Management

Only one book is available and only in german to deal with SAP EHS Management. Refer to: http://scn.sap.com/thread/3337768

This book does not cover e.g. "Component Extension Solution" and GLM topics. There is no indication that the book will be translated in english nor that there will be an update of this book.

Training documents

For EHS beginners I found these nice links (refer below). You should read them to get an idea about SAP EHS classic (even if the content seems to be based on release something like EH&S 2.5 the content is very useful to start with).

http://www.bfsgroup.biz/FB/FB/EN/PDF/EHS/36201_XX.PDF

Change XX with these values and "BE HAPPY" to get such nice EH&S documentation !

XX: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12

On the top check may be: SAP Environment, Health & Safety (SAP EHS) - How to Start Learn? | TechnoSAP - SAP Training | Help | Tutorials |…

Standard Database Structure

Rarely there is a discussion "how to adapt" EHS? What is best practise. One example is: Recommand std EHS substance structure, properti... | SCN

For those which do not have access to SAP marketplace: may be check: http://www.saptechies.org/delivery-enhancements-ehs-property-tree-standard/

For those which do have access: check SAP note 1761696. May be SAP note 1375848 could be of interest as well.

For those who use Recipe Development (PLM-WUI-RCP): SAP note 1659423 may be of interest.

Use of SAP EHS Management

SAP EHS Management is integrated very well in the relevant SAP ERP processes. Normally it is not used as a "standalone" application/module. It support companies to be compliant regarding chemical products. The main integration points are:

1. SAP MM
2. SAP DMS
3. SAP SD
4. SAP PP
5. SAP QM
6. SAP PM
   

SAP EHS Management classic uses as well the SAP class/characteristic system. By using this you can "easily" enhance EHS to maintain additional data which is not possible by using SAP standard. Keep in mind that SAP delivers update to SAP Standard property tree sometimes (please check SAP marketplace; you will find an important OSS note regarding this (Standard property tree)). If you are owning a SAP Regulatory Content license you will get these updates "nearly" automatic.

For those who would like to start with SAP EHS Management especially these modules are of importance and therefore you should invest some time to understand the use of them and the relation to SAP EHS Management:

1. SAP MM (definition of the material master, assignment of material to specification; use of material classes)
2. SAP SD (basic know how needed because of e.g. SDS/MSDS distribution and Dangerous Goods Management integration)
3. SAP DMS (basic know how needed to understand how e.g.  WWI reports are managed (stored) in SAP; it is recommended that you should have basic know how in the area of "ArchiveLink" and similar solutions
   

What the "hell" is a specification (and what about specification type and specification category)?

For those who start with EHS classic it is not easy to differentiate these terms. Think of a specification of a "number" (but need not to be number)  for an object in EHS classic. SAP provides a number of SAP transactions in EHS. Therefore on the topic you might have some problems in understanding the difference.

The topic of specification category is explained here:

Specification Category - Basic Data and Tools (EHS-BD) - SAP Library

and that of the specification type here:

http://help.sap.com/erp2005_ehp_07/helpdata/en/4d/936efaed6834b7e10000000a42189c/content.htm?frameset=/en/c1/eda0f591ec12408b25e7a1b369ca45/frameset.htm

In EHS Classic mainly these transaction codes are used to prepare data:

Hazardous/dangerous -- what is the difference?

If you read cross chemical legislation/regulations you will find the term "Hazardous" and "Dangerous". These two terms are sometimes mixed. On high level this is true:

If people talk about "hazardous substances/materials" they are interested in topics as:

• SDS/MSDS generation
• SVT
• Hazardous Substance Management (e.g. what is allowed to be stored together)
• SOP generation
• Handling/Storage advices
• Labeling
• etc.

If people talk about "dangerous substances/dangerous goods management/dangerous materials" they are interested in topics as

• how to transport the product safe
• in which region (e.g. regulations like IMDG, IATA, ADR, ADNR etc.) should the transport happen and what is the "mode of transport"
• what can be transported together
• In which kind of "package" is the transport allowed
• etc.
  

Hazardous Substance Management

Currently there is a high frequency of threads to be detected in the area of "Hazardous Substance Management". I am sorry to say that one could write books regarding this topic. I can only try to give some may be helpful hints.

• There is a kind of overlap in "understanding" and "use" of this term with SAP EHS IHS
• There is a functional overlap with Component Extension for SAP EHS Management
• and there still exists in SAP ERP an "old" solution; according to the analysis here: nobody seems to use this solution any more (there is nearly no thread): some rare examples: Hazardous material not maintained in Region, Hazardous material URGENT, Hazardous Materials Management - Warehouse Management System (WMS) - SAP Library
• There is an integration option available with SAP eWM (topic of what is allowed to be stored together in a "location")
  

If you check carefully the optons delivered with "Component Extension" Solution the story is now getting "complexer" as we have now a kind of functional overlap.

Dangerous Goods Management

The "Dangerous Goods management" solution does have a long history. By using Enhancement Packages on top of ECC 6.0 there are now a lot of new options available. E.g. using recent SAP releases you can integrate SAP EHS DG as well with SAP TM.

Further links regarding Sustainability

Check may be:

• http://www54.sap.com/solution/lob/r-and-d/software/overview/highlights.html
• http://www54.sap.com/solution/lob/sustainability/software/overview/highlights.html
• http://www54.sap.com/solution/lob/sustainability/software/overview/supply-chain.html

Substance Volume Tracking

For those who might be interested: for any company doing business in Korea a "REACh" like regulation is now in place. Take a look here: Korean REACH passed on April 30th

It can be expected that in Asia more regulation will come in place which are REACh like. So there might be the need so set proper SVT scenario for the new countries. E.g. take a look here: Korean Reach compliance

GHS

In more and more countries the GHS principle is used. This does have impact on e.g. WWI layout, rulesets and other topics as well. Most of the regulations create "lists" (e.g. europe) in whicht the GHS classifícation/labeling is fixed for a specific chemistry. Therefore the topic of content handling is important as well.

Data management in EHS solutions

A lot of discussion can be listed in context of  "mass update", "upload options". Because of the many SAP solutions; let us concentrate on EHS classic.

On very high level you might differentiate:

• Set up of a new SAP ERP system (and EHS classic) using data from a legacy system
• Doing mass updates in the EHS system of any kind (insert, update, delete)
• Options to extract data from SAP ERP system
  

Any of these topics are addressed in many threads in this FORUM (and some links to threads are provided as well). Therefore: please check this document and the many threads.

It is always a good practise to consider as well "documents" in your scope. Here more or less the option to "import" documents or "export" is of interest; but sometimes as well there is the need to generate by mass new documents in EHS classic based on new data. Here as well you will find lot of references in this document and in this FORUM.

In most cases the demand is such specific, that you will in most cases use a company specific approach.

Sustainability Solutions

This section is intended to provide short links to SAP documentation. It is not intended to be complete etc.

PLEASE CHECK SERVICES e.g. provided FROM SAP

SAP EHS Regulatory Documentation OnDemand – SAP Help Portal Page

SAP Architecture

On regular/irregular basis question come up in context of  SAP license strategy, about how the software can be combined etc. Especially the activation of SAP EHS as part of SAP ERP is asked sometimes (e.g. EHS management prerequisites). Here some general links for beginners with SAP or SAP ERP.

The design / set up of a a useful SAP landscape is not an easy taks. E.g. as an example:

Data / Document archiving

This topic is discussed rarely. The story is quite simple. SAP delivers a standard strategy to "archive" documents but not the data. So if you use EHS for a long term (> 3 years) and based on your company size etc. the number of data records in the EHS core tables can increase "dramatically". There is only one option to delete "old" data but you can not archive this data (based on what SAP delivers).

Other sources of information

Please check YouTube ! A lot of people uploaded here videos (e.g. maintenance and training examples) about EHS of any kind.

Reference to other documents in SCN

Blog Posts

Wiki Blogs

Recipe Development/Recipe Management

Very rarely discussion comes up about the solution "Recipe Development" or "Recipe Management". This is normally discussed in SCN in Forum "PLM (Product Life Cycle Management; check may be:: Product Lifecycle Management (SAP PLM)).

Recipe Develoment does have "Business Function" extensions as well. E.g.

Information regarding "Recipe Development" can be found here:

http://help.sap.com/erp2005_ehp_07/helpdata/en/65/ee1a3a0792a622e10000000a114084/frameset.htm

Information regarding "Recipe Management" can be found here:

http://help.sap.com/saphelp_erp60_sp/helpdata/en/60/ee1a3a0792a622e10000000a114084/content.htm

As you can see: the link is different and the solution approach is different. Both applications use SAP EHS core elements as well.

Component Extension for SAP EHS Management

Component Extension for SAP EHS Management is a "new" solution (now available as version 6.0). It is an "Add On" (own software layer). This new solution can not be compared with SAP EHS Management "classic" and is implemented different. The actual scope of the application does have some overlap with SAP EHS Management "classic". To a certain extent part of SAP EHS Management "classic" can be used if you start with the Component Extension (you can "migrate" existing data). Discussion in several threads in this FORUM showed that SAP will "reorganize" their applications. Therefore some old functions will not be developped any more but money / time etc. will be invested in the Component Extension. Please check carefully this FORUM. A number of useful hints are provided regarding installation of the new solution, migration topics etc.

E.g. check: SAP EHS DISCUSSIONS !!!!: SAP EHS and SAP EHSM – Where to start learning

GLM/Global Label Management

Discussion in this FORUM showed that SAP is restructuring and enhancing the GLM solution as well. Last update has been done with Enhancement Package 7. Some old TechniData solutions seems to be still supported by SAP using the SAP Consulting service. Especially the new options regrading GLM in Enhancement Package 7 are worth to be studied if you need to implement GLM. Especially the topic "how to install WWI correct" is a "problem" in this context. Because of recent dicussions in this FORUM some links to "Bar Code" discussion taking place in this FORUM has been added. GLM is as well one of those topics discussed very often in this FORUM.

MSDS/SDS/XML

On an irregular level discussion is coming up if it is possible to "convert" a WWI related MSDS/SDS into XML for data exchange. To make it short: there are options to do so but there is lack of availability of XML schemata. Here I have the feeling that people believe XML is something like "TXT", "DOC", "PDF" etc. To a certain extent this is correct but in context of MSDS/SDS and data exchange this is wrong. The main "issue" here is: data exchange can be only done if sender and receiver talk the same language. Examples of data interchange options via XML is the "IUCLID" format. Here you need to prepare a XML data stream according to the rules of ECHA. And this is the "crucial" issue in exchange of data using XML. The XML file content must "fit" a XML schema. (there is a "rule" to do so). But there is a trend on chemistry / legislation etc. to use XML as the "data format (but per "legislation" there is a different rule in place) and clearly if you look close on SAP functionality you can generate XML (there are a number of options to do so). But e.g. if you would like to exchange an US related MSDS or an European MSDS via XML you have a different internal structure etc. Here we have now to a certain extent the link to WWI. WWI is used to "collect" together the data for US MSDS and EU MSDS. Using XML in theory you can do the same but because of lack of "common" rules (as with the IUCLID format) you can not use XML generally to exchange MSDS/SDS data. In most cases you need to think about "mapping" of XML Data stream to your EHS structure (may be you use different phrases, identifiers etc. etc.).

WWI / Adobe Forms

In some SAP EHS Management related software Adobe Forms are used (Example SAP Product and REACh Compliance Suite). For SDS/MSDS/Label etc. reports WWI is and will be the standard tool. It can be assumed that Adobe Forms will be integrated "better" in the future and that it will be used more often but if a complex layout has to be designed WWI is  the only available tool to do so especially in the area of Label Management.

Portal solutions/MSDS download and related stuff

On regular basis discussion is coming up regarding:

• MSDS import
• MSDS export
• MSDS display in portal
  

PLEASE CHECK THIS FORUM first or check this document. The topic has been discussed really often.

Dear EHS Community: please go on in preparing documents and blogs !

Any idea to improve this section is appreciated. Please provide ideas regarding topic or subtopic so that may be beginner can find more easily the answer.

Please help to improve so that Beginners in SAP EHS Management are supported. What do you Beginner in SAP EHS Management need as a "starter package"?

Frequently Asked Questions

This section is intended to help beginners to find easily a thread in this FORUM which might help regarding the issue. This section will grow step by step. Ideas of topics which should be collected can be added based on feedback of community.

The "WWI" section part of this FAQ will be updated only rarely. The same is true for "GLM" part. There are too many threads regarding this tool/technique. It is nearly not possible to do a "sorting" or to select properly may be helpful threads. Please refer to some of the documents as mentioned here. They try to help more.

The same is true regarding Report distribution, Component Extension for SAP EHS Management as well as Dangerous Goods Management topics etc. It is not easy to sort questions asked so that it might help a SAP EHS beginner.

This is my personal list of those topics which are asked for very often:

• WWI (layout topics, server installation) (it is nearly impossible to take care about that many threads regarding this tool/this solution in this FORUM; therefore: please search first ! and then ask your question)
• How to use WWI to define e.g. MSDS/SDS layout (what are the basic steps)
• MSDS generation (e.g. what are the steps required etc.) (e.g. SAP EHS DISCUSSIONS !!!!: WWI Template Creation and (M)SDS Authoring)
  
• Report distribution (e.g. general set up; distribution of inbound documents)
• Report import/export (Most frequently asked are: Import: Inbound documents; Export: Mass download topics)
  
• Label/GLM topics of many kind (A lot of topics regarding GLM (e.g. label scenario); GLM Bar Code printing (how to use BAR codes etc.) ; synchronous WWI server
• Dangerous Goods (filling, checks and to a certain extent maintenance topics)
• CG02 extensions (e.g. use of output variants)
• Where used list (compositions, specification listings)
• CG50/CG54 (e.g. download by mass of documents, portal solutions)
  
• Regulatory content; how to use etc.
• How to start with EHS? What are the customizing steps etc.
• Use of "Component Extension" (how to install, migrate etc.)
• What are the "career" options in EHS? What are the prerequisites to start with EHS?
• SVT Topics
  

It is recommended to use the "search" functionality in SDN to check if your problem has been discussed yet. It is not intended to have a "100 % "FAQ section here and not 100 % quality (that means a thread can appear e.g. twice etc. in one section).