SAP EHS Regulatory Content Administration Manual

SAP EHS Regulatory Content
Administration Manual
SAP EHS Regulatory Content Administration Manual

Version 2011-1
Published May 2011
Copyright 2011 SAP AG, Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany
The content of this document is the intellectual property of SAP AG. Any forwarding to third parties or publication even of parts
thereof requires express and written approval by SAP AG.
1. Introduction ....................................................................................................................... 1
1.1. Objective ................................................................................................................ 1
1.2. How to use this guidance document ..................................................................... 1
1.2.1. Structure of this manual .............................................................................. 1
1.3. Security/Authorization ............................................................................................ 2
1.4. Support options ..................................................................................................... 2
1.4.1. Customer Helpdesk .................................................................................... 3
2. Installation ......................................................................................................................... 4
2.1. Prerequisites .......................................................................................................... 4
2.2. Implementation overall procedure ......................................................................... 5
3. Property Tree ................................................................................................................... 7
3.1. General Information ............................................................................................... 7
3.1.1. Prerequisites ............................................................................................... 7
3.1.2. Content of Property Tree packages ............................................................ 8
3.2. Implementation ...................................................................................................... 8
3.2.1. Upload property tree transport files ............................................................ 9
3.2.1.1. How to upload property tree transports files .................................... 9
3.2.1.2. Settings .......................................................................................... 10
3.2.2. Import transports ....................................................................................... 10
3.2.2.1. How to import transports (customizing or workbench) .................... 10
3.2.2.2. Execute Reports ............................................................................. 12
3.2.2.3. Settings .......................................................................................... 13
3.2.3. Allocate phrase sets ................................................................................. 13
3.2.3.1. How to allocate phrase sets ........................................................... 13
3.2.3.2. Settings .......................................................................................... 15
3.2.4. Generate WWI symbols for reports .......................................................... 16
3.2.4.1. How to create WWI report symbols ............................................... 16
3.2.5. Set up Table-based Value Assignment (EHS 3.2 and higher releases)
..... 16
3.2.5.1. How to set up the Table-based Value Assignment ......................... 17
3.3. Check Implementation ......................................................................................... 21
3.3.1. Checking Procedure ................................................................................. 22
4. SAP EHS Regulatory Content - multilanguage phrase library for hazard communication ...................................................................................................................................... 23
4.1. General Information ............................................................................................. 23
4.1.1. Prerequisites ............................................................................................. 23
4.1.2. Structure of CED phrase catalogue for EHS ............................................ 23
4.1.2.1. Phrase groups ................................................................................ 23
4.1.2.2. Phrase keys ................................................................................... 23
4.1.2.3. Allocation of bitmaps to phrases .................................................... 23
4.1.2.4. Phrase sets (PAWM) ..................................................................... 24
4.1.3. Language/Codepage/Font ......................................................................... 24
4.1.3.1. Prerequisites / important notes ....................................................... 24
4.1.3.2. Classification of phrase languages into different groups ................ 24
4.1.3.3. Handling of different code pages within SAP R/3 ........................... 25
4.1.3.4. Setup of language keys for phrase items within the phrase administration .................................................................................................. 25
4.1.4. Proposals .................................................................................................. 26
4.1.4.1. Proposals for changes, corrections or expansions ......................... 26
4.1.4.2. Correction of mistakes ................................................................... 26
4.1.5. Content of Phrases packages ................................................................... 26
4.2. Implementation .................................................................................................... 26
4.2.1. Create passive phrase catalogue CED ..................................................... 26
iii
SAP AG

4.2.1.1. How to create passive phrase catalogues ......................................
4.2.2. Upload files ...............................................................................................
4.2.2.1. How to upload files ........................................................................
4.2.2.2. Load of import files into EHS .........................................................
4.2.3. Import phrases ..........................................................................................
4.2.3.1. How to import phrases ...................................................................
4.2.3.2. How to merge phrases ...................................................................
4.2.3.3. How to import phrase set assignments ..........................................
4.2.4. Individual changes on CED phrases .........................................................
4.2.4.1. How to create phrase variants .......................................................
4.2.4.2. Adding of customer specific phrase groups ...................................
4.2.4.3. Customer specific changes / extensions of phrases .......................
4.2.4.4. Adding CED permutations ..............................................................
4.3. Check Implementation .........................................................................................
4.3.1. Checking Procedure .................................................................................
5. SAP EHS Regulatory Content - substance lists and reference data ..............................
5.1. General Information .............................................................................................
5.1.1. Prerequisites .............................................................................................
5.1.2. Schematic Diagram Open Content Connector ..........................................
5.1.3. Content of substance lists and reference data packages ..........................
5.2. Implementation ....................................................................................................
5.2.1. EHS OCC .................................................................................................
5.2.1.1. Install EHS OCC ............................................................................
5.2.1.2. RFC connection .............................................................................
5.2.2. SAP EHS Customizing .............................................................................
5.2.2.1. Secondary Data Determination User Exit .......................................
5.2.2.2. Data Origin .....................................................................................
5.2.2.3. Phrase Catalogue ..........................................................................
5.2.2.4. User defined text types ..................................................................
5.2.2.5. Regulatory Lists .............................................................................
5.2.2.6. Literature Source ............................................................................
5.2.2.7. Identifier Types ...............................................................................
5.2.2.8. Dangerous Goods Master Data .....................................................
5.2.2.9. Validity Area ...................................................................................
5.2.2.10. Update Hit List Functionality ........................................................
5.2.3. Phrases .....................................................................................................
5.2.3.1. Upload files ....................................................................................
5.2.3.2. Import phrases ...............................................................................
5.2.4. XML substance database .........................................................................
5.2.4.1. Install XML substance database ....................................................
5.2.5. Mapping Database ....................................................................................
5.2.5.1. Setup Mapping Database ...............................................................
5.2.6. Analysis Tool for Excel .............................................................................
5.2.6.1. Install Analysis Tool for Excel ........................................................
5.2.7. Adjustments ..............................................................................................
5.2.7.1. Configure EHS OCC ......................................................................
5.2.7.2. Configure User Exit ........................................................................
5.2.7.3. Adjust Mapping ..............................................................................
5.2.8. Cache ........................................................................................................
5.2.9. Review New Filter Settings .......................................................................
5.2.9.1. Adapt Dangerous Goods Filter Settings .........................................
5.3. Check Implementation .........................................................................................
iv
26
27
27
28
28
28
30
32
34
34
34
34
35
35
35
37
37
38
38
39
39
39
39
41
45
45
52
53
54
55
56
57
60
65
68
69
70
71
76
76
77
77
80
80
81
81
84
86
88
89
89
90
SAP AG

5.3.1. Check List Product Safety ........................................................................ 90
5.3.2. Check List Dangerous Goods Packaging Data ......................................... 91
6. SAP EHS Regulatory Content - expert rules for substance and mixture classification
.............................................................................................................................................. 92
6.1. General Information ............................................................................................. 92
6.1.1. Prerequisites ............................................................................................. 92
6.1.2. Content of Expert Rule set packages ....................................................... 92
6.2. Implementation .................................................................................................... 92
6.2.1. EHS Expert ............................................................................................... 92
6.2.1.1. Install EHS Expert .......................................................................... 93
6.2.1.2. Setup RFC connection ................................................................... 93
6.2.1.3. Configure EHS Expert .................................................................... 98
6.2.2. SAP EHS Customizing ........................................................................... 103
6.2.2.1. User Exit ...................................................................................... 103
6.2.2.2. Multi Rule Call .............................................................................. 109
6.2.2.3. Data Origin ................................................................................... 109
6.2.2.4. Literature Source .......................................................................... 110
6.2.2.5. User Defined Text Type ............................................................... 111
6.2.2.6. Regulatory Lists ........................................................................... 111
6.2.2.7. User-Defined Dangerous Goods Texts ........................................ 112
6.2.2.8. Value Assignment Rating ............................................................. 113
6.2.3. SAP EHS Regulatory Content - expert rules for substance and mixture
classification ...................................................................................................... 114
6.2.3.1. Install Expert Rule Sets ................................................................ 114
6.2.3.2. Run Expert Rule Sets .................................................................. 117
6.2.3.3. Adjust Expert Rule Sets ............................................................... 117
6.3. Check Implementation ....................................................................................... 121
6.3.1. Check List ............................................................................................... 121
7. SAP EHS Regulatory Content - material safety data sheet (MSDS) templates ............ 122
7.1. General Information ........................................................................................... 122
7.1.1. Prerequisites ........................................................................................... 122
7.1.2. Content of material safety data sheet (MSDS) template packages ......... 122
7.2. Implementation ................................................................................................... 123
7.2.1. Import transports ..................................................................................... 123
7.2.1.1. How to import transports (customizing or workbench) .................. 123
7.2.2. Setup identification listings ...................................................................... 125
7.2.2.1. How to setup identification listings ............................................... 125
7.2.3. Upload files ............................................................................................. 125
7.2.3.1. How to upload files ...................................................................... 125
7.2.4. Import report template ............................................................................ 126
7.2.4.1. How to import report templates .................................................... 126
7.2.5. Create generation variant ....................................................................... 127
7.2.5.1. How to create generation variant ................................................. 127
7.3. Check Implementation ....................................................................................... 128
7.3.1. Checking Procedure ................................................................................ 128
A. How To ... ..................................................................................................................... 129
A.1. How to upload property tree transports files ..................................................... 129
A.2. How to upload files ........................................................................................... 129
A.3. How to import transports (customizing or workbench) ...................................... 130
A.4. How to import BC sets ...................................................................................... 132
A.5. How to allocate phrase sets .............................................................................. 134
A.6. How to create WWI report symbols .................................................................. 136
SAP AG

A.7. How to set up the Table-based Value Assignment ...........................................
A.8. How to create passive phrase catalogues ........................................................
A.9. How to setup number ranges ............................................................................
A.10. How to import phrases ....................................................................................
A.11. How to merge phrases ....................................................................................
A.12. How to import phrase set assignments ...........................................................
A.13. How to combine/retire phrases .......................................................................
A.13.1. Combining Duplicate Phrases ..............................................................
A.13.2. Retired Phrases ....................................................................................
A.14. How to create phrase variants ........................................................................
A.15. How to install EHS OCC .................................................................................
A.15.1. Initial Installation/Upgrading of older OCC versions ..............................
A.16. How to setup a RFC connection .....................................................................
A.17. How to test the RFC connection .....................................................................
A.18. How to extend entry in secondary data determination ....................................
A.19. How to manage user exits ..............................................................................
A.20. How to add user defined text types ................................................................
A.21. How to add data origins ..................................................................................
A.22. How to add regulatory lists .............................................................................
A.23. How to add literature sources .........................................................................
A.24. How to add identifier types .............................................................................
A.25. How to add dangerous goods master data .....................................................
A.25.1. Dangerous Goods Classes and Classification Codes ...........................
A.25.2. Risk Potentials ......................................................................................
A.25.3. Hazard Identification Numbers .............................................................
A.25.4. Danger Labels ......................................................................................
A.25.5. Packing Instruction Numbers ................................................................
A.25.6. Categories of Instructions for Enclosure and Instructions for Enclosure
............................................................................................................................
A.25.7. Packing Codes .....................................................................................
A.26. How to add validity areas ................................................................................
A.27. How to create extended search user exit ........................................................
A.28. How to setup/update XML substance database for substance lists and reference data ..................................................................................................................
A.29. How to setup/update mapping database for SAP EHS Regulatory Content substance lists and reference data ...........................................................................
A.30. How to install the Update Analysis Tool for Excel ...........................................
A.31. How to configure EHS OCC ...........................................................................
A.32. How to configure the User Exit for SAP EHS Regulatory Content - substance
lists and reference data ............................................................................................
A.33. How to adjust the Fact Mapping .....................................................................
A.34. How to adjust the Record Mapping .................................................................
A.35. How to adjust the Phrase Mapping .................................................................
A.36. How to write the Last Run Date ......................................................................
A.37. SAP EHS Regulatory Content - substance lists and reference data (Product
Safety) Update Data Load ........................................................................................
A.37.1. Review Regulatory Changes ................................................................
A.37.2. Update Cached Data ............................................................................
A.37.3. Review New Filter Settings ..................................................................
A.37.4. Hit List of List Substances ....................................................................
A.37.5. Simulate Data Load ..............................................................................
A.37.6. Analyze Changed Data .........................................................................
vi
137
141
142
143
144
146
148
148
149
150
150
151
151
154
155
161
162
162
162
163
164
165
165
166
166
166
166
167
167
167
168
169
170
173
173
176
178
178
179
180
180
180
180
181
181
183
184
SAP AG

A.37.7. Load Changes to SAP EH&S ...............................................................
A.37.7.1. Manual update load ...................................................................
A.37.7.2. Mass Load / Autoload ................................................................
A.38. How to install EHS Expert ...............................................................................
A.38.1. Initial Installation of Expert ...................................................................
A.38.2. Upgrading of older Expert versions ......................................................
A.38.3. Implement Expert patches ....................................................................
A.39. How to configure SAPRFC.INI ........................................................................
A.40. How to configure EHS Expert Server using EHS Service Administration ........
A.41. How to configure EHS Expert Server as a Windows Service ..........................
A.42. How to configure EHS Expert Server as a console program ...........................
A.43. How to add user-defined DG texts ..................................................................
A.44. How to add a value assignment rating ............................................................
A.45. How to load rule sets onto the Expert server ..................................................
A.46. How to register rule sets .................................................................................
A.47. How to execute rules ......................................................................................
A.48. How to display the Explanation Component ....................................................
A.49. How to generate Log Files ..............................................................................
A.50. How to adjust external table values ................................................................
A.51. How to adjust the Group Mapping ..................................................................
A.52. How to setup identification listings ..................................................................
A.53. How to import report templates .......................................................................
A.54. How to create generation variant ....................................................................
B. Technical Settings Property Tree Packages ................................................................
B.1. Settings to implement the last SAP EHS Management Property Tree Package
Product Safety ..........................................................................................................
B.2. Overview about existing property tree packages delivered in the past ..............
C. Technical Settings Multilanguage Phrase Library 2011-1 ............................................
C.1. Settings to implement the Multilanguage Phrase Library (Standard) .................
C.1.1. File Overview ..........................................................................................
C.2. Settings to implement the Multilanguage Phrase Library (APA) ........................
C.2.1. File Overview ..........................................................................................
C.3. General Settings ...............................................................................................
C.3.1. Phrase Groups .......................................................................................
C.3.2. Name spaces .........................................................................................
C.3.2.1. Phrase keys .................................................................................
C.3.3. Language/Codepages ............................................................................
C.3.4. Language keys .......................................................................................
D. Technical Settings Substance Lists and Reference Data 2011-1 ................................
D.1. Settings to implement the Substance Lists and Reference Data (Product
Safety) .......................................................................................................................
D.1.1. File Overview ..........................................................................................
D.1.2. User Exit Settings ...................................................................................
D.1.3. Other Settings ........................................................................................
D.2. Settings to implement the Substance Lists and Reference Data for Dangerous
Goods ........................................................................................................................
D.2.1. File Overview ..........................................................................................
D.2.2. User Exit Settings ...................................................................................
D.2.3. Other Settings ........................................................................................
E. Technical Settings Expert Rules 2011-1 ......................................................................
E.1. Settings to implement the basis rule set package .............................................
E.1.1. File Overview ..........................................................................................
vii
185
185
186
186
187
188
189
189
189
191
193
193
193
194
195
197
198
199
201
202
202
203
203
205
205
205
209
209
209
210
210
211
211
212
212
215
217
220
220
220
222
222
222
223
225
225
227
227
227
SAP AG

E.1.2. Settings in Admin Tool ...........................................................................
E.1.3. User Exit Settings ...................................................................................
E.1.4. Other Settings .........................................................................................
E.2. Settings to implement the rule set package for GHS ........................................
E.2.1. File Overview ..........................................................................................
E.2.3. Settings in Admin Tool - Sub Rules .......................................................
E.2.5. Other Settings .........................................................................................
E.3. Settings to implement the rule set package for APJ .........................................
E.3.1. File Overview ..........................................................................................
E.3.5. Other Settings .........................................................................................
E.4. Settings to implement the rule set package Europe ..........................................
E.4.1. File Overview ..........................................................................................
E.4.5. Other Settings .........................................................................................
E.5. Settings to implement the rule set package for National Regulations EU ..........
E.5.1. File Overview ..........................................................................................
E.5.5. Other Settings .........................................................................................
E.6. Settings to implement the rule set package for the Americas ............................
E.6.1. File Overview ..........................................................................................
E.6.5. Other Settings .........................................................................................
E.7. Settings to implement the RegStat rule set package ........................................
E.7.1. File Overview ..........................................................................................
E.7.5. Other Settings .........................................................................................
E.8. Settings to implement the DangGoods rule set package ..................................
E.8.1. File Overview ..........................................................................................
E.8.5. Other Settings .........................................................................................
E.9. Settings to implement the MSDSMaker rule set package .................................
E.9.1. File Overview ..........................................................................................
E.9.5. Other Settings .........................................................................................
E.10. Settings to implement the DPDplus rule set package .....................................
viii
227
228
229
229
229
231
231
233
234
235
235
243
248
249
259
260
260
263
264
265
268
269
269
273
277
277
284
285
285
291
294
295
304
305
305
306
306
307
308
309
309
309
310
311
312
312
312
313
313
314
314
314
SAP AG

E.10.1. File Overview ........................................................................................
E.10.2. Settings in Admin Tool .........................................................................
E.10.3. Settings in Admin Tool - Sub Rules .....................................................
E.10.4. User Exit Settings .................................................................................
E.10.5. Other Settings .......................................................................................
F. Technical Settings MSDS Templates 2011-1 ...............................................................
F.1. Settings to implement the MSDS Templates for APJ ........................................
F.1.1. File Overview ..........................................................................................
F.1.2. Other Settings .........................................................................................
F.1.3. Generation variant ..................................................................................
F.2. Settings to implement the MSDS Template for EMEA ......................................
F.2.1. File Overview ..........................................................................................
F.2.2. Other Settings .........................................................................................
F.3. Settings to implement the MSDS Template for GHS .........................................
F.3.1. File Overview ..........................................................................................
F.3.2. Other Settings .........................................................................................
F.4. Settings to implement the MSDS Templates for the Americas ..........................
F.4.1. File Overview ..........................................................................................
F.4.2. Other Settings .........................................................................................
Index .................................................................................................................................
ix
315
315
315
316
317
318
318
318
319
320
321
321
322
323
323
324
324
325
325
326
326
327
330
SAP AG
Chapter 1. Introduction
1.1. Objective
This SAP EHS Regulatory Content Administration Manual comprises all relevant steps and
guidelines for implementation and update of the SAP EHS Regulatory Content products (phrases, regulatory data, Expert rules, MSDS-templates) in SAP EHS. Appropriate related How Tos
are included to facilitate the implementation and update procedure. Information for all relevant
implementation steps is provided.
This manual does not replace release notes or functional descriptions for the individual content
products. Release notes are provided for each new version of the individual product to give
an overview over new and changed features. Functional descriptions are provided for each
individual product as detailed documentation on all functions and settings.
This manual describes all available SAP EHS Regulatory Content products. These products
need to be licensed. The manual may describe products that are not licensed by your company
and thus not delivered to your company. If you would like to check your SAP EHS Regulatory
Content license status, please contact SAP.
1.2. How to use this guidance document

There are different approaches how you can use this document.
If you are not familiar with SAP EHS Regulatory Content we recommend to use this manual
as a step by step documentation of how to implement SAP EHS Regulatory Content. Each
step which is necessary to implement SAP EHS Regulatory Content is described in the logical
sequence. Links refer to specific settings and related topics.
If you are a more experienced user and are interested in a specific topic you could use the
different appendixes to find the information your are looking for, especially the How To - Appendix. As a special service all necessary actions throughout the process of implementing
SAP EHS Regulatory Content are collected in this place.
The Technical Settings appendixes are available for all SAP EHS Regulatory Content products.
They contain general settings and information which is relevant for the current release.
User of the printed version should refer to the table of contents and the index to find the information they need. The links which are embedded in the PDF file could be used if this document
is viewed on the computer.
The following chapter Structure of this manual gives an overview over the structure of this
manual.
1.2.1. Structure of this manual

The general structure of this document is as follows:
Introduction: This part gives an introduction to this manual. It provides information how to
use it, conventions used in it and the available support options as well as a short overview
about the SAP EHS Regulatory Content product scope and the appropriate license status.
SAP AG
Introduction
Installation: This chapter provides information about the general prerequisites for the implementation of SAP EHS Regulatory Content as well as an overall implementation procedure.
Property tree: Beside some general information about property trees this part provides a
detailed step by step description of all activities which are necessary to deal with property
trees.
Multilanguage phrase library for hazard communication: This part contains all relevant information concerning phrases.
Substance lists and reference data: In this part, guidance is given throughout the process
of implementing regulatory data.
Expert rules for substance and mixture classification: This section covers all information
necessary for Expert rules.
Material safety data sheet (MSDS) templates: The aim of this part is to provide information
which is relevant to setup and create MSDS Report Templates.
How To ...: The aim of this section is to provide fast and easy to use advice on how to perform
different actions throughout the process of implementing SAP EHS Regulatory Content.
Technical Settings Property Tree: This section provides information about all relevant files,
settings and more concerning the property tree.
Technical Settings Multilanguage phrase library for hazard communication: All necessary
information with regard to phrases is aggregated in this part. It is structured according to
the different phrase packages.
Technical Settings Substance lists and reference data: This part of the documentation provides a collection of all information related to current version of regulatory data.
Technical Settings Expert rules for substance and mixture classificatin: This section contains
the release related information for the Expert rules. The settings are structured according
to the rule set packages they belong to.
Technical Settings Material safety data sheet (MSDS) templates: An overview which settings
are relevant for the MSDS Report Templates could be found here.
1.3. Security/Authorization
Starting with the download of the SAP EHS Regulatory Content package, the customer is solely
responsible for the integrity of the content, e.g. to protect the content against manipulation.
We strongly recommend to store the SAP EHS Regulatory Content in a restricted environment,
accessible only by authorized persons involved in content implementation or updates. For
further details regarding user authorization in your file system please see the user manual of
your operating system.
In SAP EHS access rights to SAP EHS Regulatory Content can be administrated via authorization profiles. For further details we refer to User and Role Administration of AS ABAP and
Roles for Environment, Health and Safety (EH&S) in the SAP Library (http://help.sap.com).
1.4. Support options

There are various ways of getting support.
Technical problems dealing with the EHS system should be reported via OSS.
Problems dealing with the SAP EHS Regulatory Content products (Property Tree, Multilanguage Phrase Libraries, Substance Lists and Reference Data, Expert Rules for Substance
and Mixture Classification, Material Safety Data Sheet (MSDS) Templates) should be reported via the customer helpdesk. Customers will get fast and well-founded response to
their problems.
SAP AG
Introduction
1.4.1. Customer Helpdesk

Our customer helpdesk http://support.technidata.de allows you to ask your questions and report your problems 24 hours a day. This offers you an easy possibility to contact SAP if any
problems occur with SAP products. Your issues are forwarded automatically to the appropriate contact person. Automatic feedback e-mails inform you about the status of your issues or
alternatively you can actively follow the status yourself.
You can report different types of issues, such as bugs, questions or requests for new features
or improvements and address them to the CSM-CLEO Data, Rules and Services project.
The customer helpdesk also provides the opportunity to bring in suggestions and requests for
further development of SAP EHS Regulatory Content.
For
questions
about
online
access
or
available
services
please
address
to:
<OD_LoB_CaaS_Helpdesk@sap.com>.
SAP AG
Chapter 2. Installation
This chapter describes the prerequisites which are necessary to implement SAP EHS Regulatory Content.
2.1. Prerequisites
This chapter describes the overall prerequisites in order to implement SAP EHS Regulatory
Content. There might be additional prerequisites which are related to separate parts of the
SAP EHS Regulatory Content. These prerequisites are defined within the respective part of
the documentation.
EHS - Release
Please see SAP note 568302 for system requirements
To determine which EHS version is installed run transaction CGVERSION.
Unicode SAP system required for full language support.
Non-Unicode systems might have limited functionality, depending on the scope of data licensed.
EHS Expert/OCC
Current version of EHS Open Content Connector (OCC) and EHS Expert (see SAP note
586302).
EHS WWI
Current version of WWI
Customizing
Basic customizing settings are described here. Special customizing activities for the different
parts of SAP EHS Regulatory Content are described in the corresponding chapters.
Number ranges for phrase keys: To import the phrases related to the Multilanguage
Phrase Library and the Substance Lists and Reference Data the external number range
0E must have the alphanumeric interval from A to ZZZZZZZZZZZZZZZ. Additionally we
recommend to designate the internal number range 0I for numeric values only (interval
100000000000000 to 899999999999999). The number range intervals have to be set in the
customizing activity Specify Number Ranges for Phrases
Language keys in the phrase management: Before importing the phrase translations the
language keys for the languages which shall be imported must have been set up in the EHS
customizing.
Language-dependent data: If language-dependent data shall be read or written by the EHS
Expert, the MULTI_CODEPAGE_SUPPORT environment parameter needs to be set in the
customizing for Basic Data and Tools at "Specify Environment Parameters".
Units of measurement: Units of measurement are maintained (e.g. for pressure: mmHg as
well as hPa if expansion method for pressure conversion is to be used ); please make sure
that translation into every necessary language is available.
SAP AG
Installation
SAP authorisation
All Expert rules and OCC users need SAP authorization S_RFC authorization for RFC access.
All OCC users need SAP authorization S_TABU_DIS Table Maintenance.
Front-end computer for data load

Detailed information is provided within SAP Note 568302
Front-end computer with a minimum of 512 MB main memory, recommend is at least 1 GB
main memory, Vista and later 2 GB.
Operating System for front-end computer Microsoft Windows 2000, XP Vista and later.
OCC communicates with the SAP System via Remote Function Call (RFC). For RFC, the
TCP/IP ports 3300 to 3399 are used. You must enable these accordingly.
Changes in the mapping database require a Microsoft Access version 2000 or higher. Users
that only load data and do not want to edit the mapping database, do not need an MS Access
installation.
2 GB of data storage space for the XML substance databases with read access for all OCC
users
SAP Notes
SAP Note
Remark
568302
See for information how to download the latest version of OCC and additional system requirements.
1061242
EH&S: Availability and performance of WWI and Expert servers
1408534
Import of phrases terminates with a runtime error
1418024
Incomplete long text when you merge phrases
1299868
EH&S Expert/EH&S OCC Unicode support
1407091
Check function for EC numbers
1424476
Phrase import does not update all phrase items
1371276
Identifier/user-defined text languages are not loaded
1434736
Update task: Most important notes
1454105
Uploading/downloading a file does not work
1466900
By mistake phrases were labeled as changed
This list is not exhaustive but contains some general notes as well as important notes of the
last few months. Please check if the appropriate note is available for your EHS release.
2.2. Implementation overall procedure

This document provides information and instructions for the SAP EHS Regulatory Content
implementation procedure.
The graph shows the sequence of the implementation.
SAP AG
Installation
Detailed information which steps are necessary to implement SAP EHS Regulatory Content
are collected in the content related check lists:
Check list: Property tree

Check list: Multilanguage Phrase Library
Check list: Substance Lists and Reference Data (PS)
Check list: Substance Lists and Reference Data (DG)
Check list: Expert rules
Check list: Material safety data sheet (MSDS) templates
Important
Before starting the implementation procedure please review the enclosed documentation.
Caution
It might be necessary to update your EHS or to implement SAP notes.
Tip
Collect all transports contained in the delivery. If you upload all transports at once you
can skip the appropriate upload activities mentioned in the check lists.
SAP AG
Chapter 3. Property Tree

3.1. General Information
The EHS Standard Functionality includes the definition of properties in order to maintain data
in the EHS specification data base. These properties are delivered together with the property
tree STANDARD. The EHS property tree STANDARD is continuously improved. Extensions
to the EHS property tree STANDARD are delivered with the SAP standard delivery of the
corresponding release or enhancement package.
SAP EHS Regulatory Content - expert rules for substance and mixture classification, SAP EHS
Regulatory Content -substance lists and reference data and SAP EHS Regulatory Content material safety data sheet (MSDS) templates make use of the new properties and new characteristics. Therefore, property tree packages are created in order to provide the new standard
properties and characteristics as a predelivery for older EHS versions as well. These packages
contain everything needed to set up and use the new and changed characteristics and classes/properties added to SAP EHS in an existing EHS 2.7B (on R/3 4.6C), EHS 3.1, EHS 3.2,
EHS 2004 or ERP 6.0 (former name ERP 2005) system.
Each Package contains files for the R/3 Transport Management System (TMS) for new and
changed classes, characteristics, value assignment types and positions in the property tree
STANDARD. Descriptions of classes, characteristics and value assignment types are delivered in English and German.
Since property tree package EHS 2004/2005 new properties including new classes and the
assigned new characteristics and new value assignment types are delivered as a separate
transport. Changed properties and changed characteristics as well as new characteristics assigned to existing properties are delivered in a second transport. This gives the user the possibility to decide whether to import only the new properties or the changes as well.
Since property tree package EHS 2004/2005 help texts are delivered in English and German
for SAP Enterprise Releases (PLM 2.00 with EHS 3.2 or higher releases) and for EHS 2.7B
in R/3 4.6C as separate transports. As an additional service, the help texts are delivered also
as a text document.
3.1.1. Prerequisites
The EHS property tree needs to be updated to the latest release status referring to the EHS
Property Tree Section.
The prerequisite for the import of the allocation of phrases to phrase sets is that the standard
properties tree has been set up in SAP EHS and that the phrase sets have been generated
to all text fields. The allocation of phrases to customer designed properties has to be done
manually.
If the explanation component shall be used and the phrase sets were generated
by the automatic customizing functionality "Create Standard Phrase Sets", it is necessary to remove the phrase set assignment manually at least from the characteristic
SAP_EHS_0101_002_RULESET. Otherwise the explanation cannot be stored in the specification database for later use.
Customers with an EHS 2.7B, 3.1, 3.2, ERP 5.0 (= ERP 2004), ERP 6.0 and ERP 6.0 EnhP
3 system must ensure that the earlier property tree packages have already been installed
SAP AG
Property Tree
before loading a new package. If the installation sequence is reversed, some of the changes
within the new package will be overwritten by older packages. An overview about the existing
property tree packages is given in the Appendix.
Customers with an EHS 2.7B system (on R/3 4.6C) have to import the specific help text
transport delivered for this release. If help text transports created for EHS 3.2 and higher
releases are imported in an EHS 2.7B system (on R/3 4.6C), technical problems can be caused
in the specification data base.
All classes where new characteristics are added or characteristics are changed should not
have been changed manually because these changes will be overwritten by the transports.
In addition, the flags and parameters of the existing value assignment types such as "CharCopy active", "New val. actv.", "Usage profile" etc. will be overwritten by the standard values
(for example Usage profile = PROF001) with the import of the transport requests which include the value assignment types . Therefore, if any of the classes, characteristics and value
assignment types mentioned in the files Changes_.....pdf do already exist or were changed
in the destination system, it is recommended to make a copy of them first before installing
this package. Furthermore, if the property trees STANDARD and OBSOLETE were changed
(which is not recommended), copies should be made of these property trees as well.
The import of the transport requests with the assignments to the property tree STANDARD and
OBSOLETE is optional. If the transport requests are not imported, the new properties have to
be assigned manually. Within EHS 2004, the property tree STANDARD was restructured and
the property tree OBSOLETE was newly created. The complete property trees STANDARD
and OBSOLETE for EHS 2004 are included in the package EHS 3.2/2004. The import files
with the assignments in the property tree packages EHS 2004/2005, ERP 6.0 EnhP 3, 2007-2
and 2008-1 are based on this structure in EHS 2004. Therefore, the property tree EHS 2004
has to be imported before importing the transport requests with the assignments of the more
recently generated property tree packages.
3.1.2. Content of Property Tree packages

Each EHS property tree package consists of the following parts:
List of changed and new properties and characteristics
Files for the R/3 Transport Management System (TMS) for new and changed classes, characteristics, value assignment types and positions in the property tree STANDARD (with English and German descriptors)
Since property tree package EHS 2004/2005: Files for the R/3 Transport Management System (TMS) for help texts (in English and German) for SAP Enterprise Releases (PLM 2.00
with EHS 3.2 or higher releases) and for EHS 2.7B in R/3 4.6C as separate transports.
Since property tree package EHS 2004/2005: Help texts in English and German as a text
document
A detailed list of transports and files delivered with the property tree package of the corresponding SAP EHS Regulatory Content Update is given in the Appendix.
3.2. Implementation
The following steps describe how to implement property tree packages. Please note that the
transports within a package or sub-package have to be imported in the order given in the
SAP AG
Property Tree
Appendix. The steps "Allocate phrase sets" and "Generate WWI symbols for reports" have to
be done after the import of the transports on each EHS system. The step "Setup Table-based
Value assignments" has to be performed for EHS 3.2 and higher releases only.
3.2.1. Upload property tree transport files

New and changed classes and characteristics as well as help texts are delivered as workbench
transport requests for the SAP Transport Management System. In addition to that, customizing
transports requests are delivered which contain the assignment of properties to the property
tree STANDARD.
Before property tree transport requests can be imported into an EHS system, the corresponding files have to be uploaded onto the SAP application server.
Please note that the file names of the transport requests for the SAP Transport Management
System have the following structure:
Co-files start with an "K"
Data files start with an "R"
The extension of a transport file stands for the name of the SAP system where the transport
request was created.
An example:
Transport request: SH2K102047
Co-file: K102047.SH2
Data file: R102047.SH2
The following chapter describes how the upload of property tree package transport files has
to be performed:
3.2.1.1. How to upload property tree transports files

The upload process consists of three steps:
1. Find out the directory name and path of the import queue for the SAP Transport Management System.
2. Load the transport files into the import directory using the transaction CG3Z.
3. Attach the transport request to the import queue
In the following, the three steps are described:
You may ask your SAP system manager or proceed as follows:
Run transaction AL11.
The first part of the directory path is listed after the entry DIR_TRANS, for example "F:
\usr\sap\trans".
Within this directory two sub-directories exist:
The sub-directory "cofiles" where the co-files are stored.
The sub-directory "data" where the data files are stored.
9
SAP AG
Property Tree
Start transaction CG3Z.
Enter in the field "Source file on front end" the transport file name including the complete
path on your computer or file server, for example "d:\transfer\K102047.SH2" for a co-file
or "d:\transfer\R102047.SH2" for a data file.
Enter in the field "Target file on application server" the same file name and the complete
path on the SAP Application Server which you found out in Step 1, for example "F:\usr
\sap\trans\cofiles\K102047.SH2" for a co-file or "F:\usr\sap\trans\data\R102047.SH2" for
a data file. Make sure to enter "BIN" in the field "Transfer format for data".
Start the upload process with the push button "Upload". When the upload process has
been successful a message appears.
Navigate to the SAP Transport Management System (transaction STMS).
Choose push button "Import Overview (F5)".
Navigate to the transport domain of your SAP system: Position the cursor on the transport
domain and choose the push button "Display Import Queue" or choose "Double click".
Choose in the menu "Extras" -> "Other requests" -> "Add".
Enter in the field "Transp. Request" the name of the transport request, e.g.
"SH2K102047". The field "Import Queue" is already filled with the selected import queue.
Start the process with the push button "Continue". The transport request is added to the
bottom of the import queue with the highest number.
Please note that the listed "Owner" is the SAP user who created the transport request not
the login-user who started the upload process!
3.2.1.2. Settings
The files which need to be uploaded depend on the property tree package and are summarized
in the Appendix.
3.2.2. Import transports

This chapter describes in detail the import of transports and reports.
3.2.2.1. How to import transports (customizing or workbench)

If transports have been uploaded (cg3z) they should be available in the transport queue.
With the transaction "stms" you can import transports from the queue into the system.
10
SAP AG
Property Tree
On the second screen you will see a list of available queues (After pressing the van-icon).
Depending to your system you may have virtual transport queue(s) or not. The virtual queue
enables you to transfer transports between multiple systems if you uploaded the transports
into the virtual queue (and the systems are connected to the virtual queue).
Double click the queue you want to work with.
If you have uploaded the corresponding pair of files (co-file and datafile) to the appropriate
places they appear in the transport queue. If not you may use the menu ->"Extras->other
11
SAP AG
Property Tree
requests->add". Then you will get a dialog box to choose additional transport files to be shown
in the actual transport queue.
There is a naming convention :
Zxxxxxxx.yyy is the name of the file where Z is K for the co-file and R for the data file.
x is a numerical value. y is the extension. The extension is the System ID (i.e. SH2, TD3 ... )
After you uploaded the file you will find the files in the queue with a different name! In the
queue they will appear like:
yyyKxxxxxxx (The system ID as a prefix followed by the "K" of the co-files and the numeric
value.)
Example : K102002.SH2 and R102002.SH2 would be the filenames and the list entry would
be : SH2K102002
Setting filters :
To find the transports you may use a filter. The transports can be identified by user who created
the transport - not the user who did the upload!
Setting the filters is initiated by a mouse click on the column to be filtered and then a click on
the filter-icon. More than one filter can be defined. To delete a filter start the same way but in
the dialog click on the bin - icon.
To specify the transports to be imported use the 4th button (black arrow pointing to the red
button) you may mark more than one item. Be careful, some transports have dependencies
so those cannot be imported at once.
If the selection is complete start the import by pressing the van-icon with the small orange top
edge. A dialog will appear where you can give additional options. In most cases the standard
flags will be sufficient.
If you start the import you will see the van-symbol on the right side of the list of transports. If you
refresh the screen with the (first icon in the screen shot above) the van symbol will disappear
when the transport has finished.
3.2.2.2. Execute Reports

Additionally in case of importing a report the report has to be executed via transaction SA38.
Please start the ABAP program as described in the steps below:
1. Execute transaction SA38 ABAP: Execute Program
2. Choose the appropriate program name, e.g.
12
SAP AG
Property Tree
3. Execute the program (F8)

4. Depending on the program, you will get a screen with further options as next step or the
program will start immediately if no further settings are required
3.2.2.3. Settings
Please see which files are provided for import.
3.2.3. Allocate phrase sets

Neither new phrases nor phrase sets nor allocations of phrase sets to characteristics are delivered with a property tree package. In order to make use of new characteristics which were defined for phrases, phrase sets have to be set up and allocated to the new characteristics. This
chapter describes in detail how to set up and allocate phrase sets for these new characteristics. Please note that only characteristics have to be considered which are described as "new,
CHAR 30, multiple phrases" or "new, CHAR 30, single phrase" in the files "Changes_......pdf".
3.2.3.1. How to allocate phrase sets

There are two ways to generate phrase sets:
1. Manual generation and allocation of phrase sets
2. During an initial setup: Customizing activity "Generate Standard Phrase Sets"
In the following, both ways are described:
Ensure that no one is working with the affected property tree or is using the affected the
properties and characteristics in the EHS specification workbench.
Run transaction CGCZ "Match Up Master Data" with flag "Match Up ValAss Type and
Char." only. This function determines all characteristics to which phrases can be assigned
- that are characteristics of type CHAR 30. These characteristics are transferred to the
table Phrase set - Attribute assignment (transaction CGAB).
13
SAP AG
Property Tree
Choose transaction CG1B "Edit phrase sets" and create manually phrase sets for all
characteristics which are described in the file "Changes....pdf" as "new, CHAR 30, multiple phrases" or new, CHAR 30, single phrase. Enter the characteristic key as the new
phrase set key. Add appropriate phrases to the new phrase sets. Exceptions are characteristics such as "Accuracy" or "GLP". For these characteristics, phrase sets already
exist (SAP_EHS_XXXX_XXX_PREC, SAP_EHS_XXXX_XXX_GLP) and can directly be
assigned.
Customers of SAP EHS Regulatory Content - multilanguage phrase library for hazard
communication receive the allocation of phrases to phrase sets of new characteristics
with the corresponding update.
Choose transaction CGAB "Edit phrase set-attribute assignment". Assign all new phrase
sets to the appropriate characteristics.
Run transaction CGCZ "Match up master data" with flag "Activate Phrasing of Characteristics." only. This function assigns the function module
C14K_PHRASECHARACT_CHECK to all phrase-related characteristics. This enables
the system to call an assigned phrase set in the specification data base.
14
SAP AG
Property Tree
If an EHS system is set up initially the customizing activity "Generate Standard Phrase
Sets" is used in general to create and allocate phrase sets to all characteristics of type
CHAR 30.
Navigate to the activity "Generate Standard Phrase Sets" in the SAP customizing (IMDG)
(path within EHS 3.2 and higher releases: Environment, Health & Safety -> Basic Data and
Tools -> Specification Management -> Specification Data Base Structure -> Settings for
Value Assignment). A complete overview about this activity is given in the corresponding
IMDG activity documentation.
Start the activity.
Phrase sets are generated and allocated to all characteristics of type CHAR 30. Phrases
are not allocated to the new phrase sets. Assignments of phrase sets to characteristics
that already exist are not overwritten by the system.
Some characteristics defined as CHAR 30 are not meant to be assigned to phrase sets,
for example "Value in Non-Standard Unit". These characteristics shall be used to store a
numerical value and a unit but were unfortunately defined as a free text fields of CHAR
30. In this case, the assigned phrase set has to be deleted in the table "Edit phrase
set-attribute assignment" (transaction CGAB) after the standard phrase sets have been
created.
Run transaction CGCZ "Match up master data" with flag "Activate Phrasing of Characteristics" only. This function assigns the function module
C14K_PHRASECHARACT_CHECK to all phrase-related characteristics. This enables the system to call an assigned phrase set in the specification data base.
If the phrase set was deleted in the table "Edit phrase set-attribute assignment" (transaction CGAB) before carrying out this transaction, then the function module
C14K_PHRASECHARACT_CHECK is deleted in the corresponding CHAR 30-characteristic and this characteristic can be filled as a free text field.
3.2.3.2. Settings
Phrase sets have to be allocated to new characteristics which are described as "new, CHAR
30, multiple phrases" or "new, CHAR 30, single phrase" in the files "Changes_......pdf". The
15
SAP AG
Property Tree
corresponding characteristic key can be found in the files "Changes_.....pdf" as mentioned in
the Appendix.
3.2.4. Generate WWI symbols for reports

In order to print out the content of new characteristics on a WWI report symbols have to be
created for all new characteristics, which can be used in the definition of WWI templates. This
chapter describes in detail how to generate WWI symbols.
3.2.4.1. How to create WWI report symbols

Run transaction CGCZ "Match up master data" with flag "Generate Symbols" only. This will
generate the necessary new WWI symbols for the new characteristics.
Additional information:
In a standard R/3 System symbols are generated with descriptions in the logon language. The
flag "Regenerate Symbol Descriptions" within transaction CGCZ can be used to generate the
symbol descriptions in another language different from the logon language.
If the transaction CGCZ is run with the flag "Match Up Symbols-Phrase-Enabled Characteristics" the symbol definitions for the characteristic symbols that have been changed from phraserelated to non-phrase-related (or vice versa) will be updated..
3.2.5. Set up Table-based Value Assignment (EHS 3.2 and

higher releases)
In EHS 3.2 and higher releases, specification data are entered in the specification data base in
a table on the "Value assignments" tab page. The fields of a property which are to be displayed
in the data entry table are specified in the customizing activity "Set up Table-based Value
Assignment".
Therefore, for EHS 3.2 and higher releases the new and changed properties have to be configured for the Table-Based Value Assignment. This step is NOT necessary for EHS 2.7B!
For new properties the Table-Based Value Assignment has to be set up newly. For existing
properties were new characteristics were assigned the already existing Table-Based Value
16
SAP AG
Property Tree
Assignment has to be extended. This chapter describes in detail how to set up the Table-based
Value Assignment in both cases.
Please note, that the property keys of new and extended properties can be found in the files
"Changes_.....pdf" as mentioned in the Appendix.
3.2.5.1. How to set up the Table-based Value Assignment

There are two ways to set up the Table-based Value Assignment:
1. Set up Table-based Value Assignment for new properties
2. Set up Table-based Value Assignment for existing properties with new characteristics
1.1. Navigate to the activity "Set Up Table-Based Value Assignment" in the SAP customizing (IMG) (path within EHS 3.2 and higher releases: Environment, Health & Safety ->
Basic Data and Tools -> Specification Management -> Specification Data Base Structure
-> Settings for Value Assignment -> Set Up Table-Based Value Assignment). A complete
overview about this activity is given in the corresponding IMG activity documentation.
1.2. Start the activity. The following screen appears:
1.3. Choose the entry "Create Entries for the Value Assignments". The window "Filling
Customizing Table for Table-based Value Assignment" appears:
17
SAP AG
Property Tree
1.4. Enter a property key of a new property or a series of property keys in the field "Value
assgmt type" and start the process (pushbutton "Execute").
A general example for a property key is SAP_EHS_1023_043 (for property "GHS Classification"). Select the property keys of the new properties within a specific property tree
package from the file "Changes_.....pdf". The file name for a specific property tree package can be found in the Appendix.
Please avoid to execute this process with the same property key multiple times because
this would create multiple entries in the customizing table!
1.5. Return to the previous window (push button "Back"):
18
SAP AG
Property Tree
1.6. Choose the entry "Set Up Table-Based Value Assignment". The complete customizing table opens. Check all entries for the configured property/properties:
1.8. Repeat the steps 1.2 to 1.7 to create the necessary entries for all new properties.
For EHS 3.2 and higher releases you have to change the configuration of existing properties where new characteristics were added and which were already configured for the Table-Based Value Assignment. The recommended procedure is to delete all entries for existing properties with new characteristics in the customizing table and to create the entries
for these properties again (see the following steps 2.1 to 2.14).
If the configuration of the Table-Based Value Assignment for properties with new characteristics was already changed, then these changes should be documented before deleting the
entries. In this case, an alternative could be not to delete all entries for a changed property
but to update the Table-Based Value Assignment for the existing property only (follow steps
1.1 to 1.8). Then, the new characteristics would be appended to the already existing entries
for this property. The correct order of the characteristics would have to be set up manually.
Please note, that the Table-based Value Assignment customizing table can only be changed
in SAP systems where the direct customizing is enabled. If the direct customizing is disabled
(for example in a production system), then the Table-based Value Assignment should be set
up in a system where the direct customizing is enabled (for example a development system).
The correct entries can be then transported to the system with the disabled customizing
(customizing transport).
19
SAP AG
Property Tree
2.3. Choose the entry "Set Up Table-Based Value Assignment". The complete customizing table opens.
2.4. Choose the push button "Position", enter a property key of an existing property with
new characteristics and navigate to this property. Select the property key from the file
"Changes_.....pdf". The specific file name for a certain property tree package can be found
in the Appendix.
2.5. Select all entries for this property.
2.6. Delete the selected entries (push button "Delete").
2.7. Return to the previous window:
20
SAP AG
Property Tree
2.9. Enter the property key of the property, which entries you deleted in the previous step,
in the field "Value assgmt type":
2.10. Start the process (pushbutton "Execute").
2.12. Choose the entry "Set Up Table-Based Value Assignment" again. The customizing
table opens. Check all entries for the configured property:
2.14. Repeat the steps 2.2 to 2.13 to create the necessary entries for all existing properties
with new characteristics.
3.3. Check Implementation

21
SAP AG
Property Tree
The following steps describe how to check the implementation of Property Trees.
3.3.1. Checking Procedure

Please use the following check list as guidance through the property tree implementation and
as check list after the implementation.
Status
Where to do
What to do
General
O
Review documentation
Technical Part
O
SAP EHS (cg3z)
Upload files
SAP EHS (stms)
Import transports
SAP EHS (cg1b)
Create phrase sets
SAP EHS (cgcz)
Match up master data
SAP EHS (cgab)
Assign phrase sets to characteristics
SAP EHS (cg3z)
Activate phrase set assignment to characteristic
SAP EHS (cgcz)
Create WWI symbols
Customizing (spro)
Update table based value assignment
22
SAP AG
Chapter 4. SAP EHS Regulatory

Content - multilanguage phrase
library for hazard communication
SAP provides Multilanguage Phrase Libraries, previously known as CED (Chemical Exchange
Directory) Catalogue. This is a collection of more than 9.000 phrases for product safety issues
in currently 41 languages, 31 of them for EMEA and Americas. Data is delivered in the EHS
import format, which can then be loaded directly into the customer's SAP EHS system.
Update deliveries include enhancements, customer proposals and corrections to the phrase
library and delivery of new languages.
The latest version of the CED phrase library needs to be imported according to the respective
sections in this documentation.
Most Expert Rules for Substance and Mixture Classification delivered with a SAP EHS Regulatory Content update will require the latest phrase library version.
To determine which CED catalogue is current, have a look at Customizing -> Environment,
Health and Safety -> Basic Data and Tools -> Phrase Management -> Specify Phrase Libraries
and Phrase Groups. Choose the CED library and have a look at details.
4.1.2. Structure of CED phrase catalogue for EHS

4.1.2.1. Phrase groups
The phrases of the CED Phrase Library are divided into the following phrase groups analogous
to the chapters of an European safety data sheet in the version before REACh 2007. Change
of the sections 2 and 3 did not result in change of the phrase groups in the CED library as this
would have caused changes of phrase keys as well and therefore was not acceptable.
Please see annex for further information on phrase groups.
4.1.2.2. Phrase keys

The assignment of phrase keys is based on a content dependent systematic. Please see annex
for details.
4.1.2.3. Allocation of bitmaps to phrases

At present the CED-EHS-library contains the allocations of the hazard symbols to the correspondent phrases.
If a customer has maintained own graphics by allocation of bitmaps to phrases these allocations will be overwritten by an update. The same applies for the fields phrase code and phrase
remark at the phrase item level!
23
SAP AG
SAP EHS Regulatory Content - multilanguage phrase library for hazard communication
4.1.2.4. Phrase sets (PAWM)

The standard phrase sets are set up of the same name as the phrase based characteristics
of the EHS standard properties tree.
The phrase set assignments of the CED Phrase Library are based on the latest SAP EHS
properties tree.
4.1.3. Language/Codepage/Font
4.1.3.1. Prerequisites / important notes
Prior to importing an update, it may be necessary to extend the language setup of your SAP
R/3. Please see the CED release notes that come with each update for information on which
new languages will be added with the update.
The new language(s) must be added in EHS customizing.
To make US English available for all customers including those with non-unicode systems
we decided to deliver this language with a language code coming from the customers reserve.
Please maintain the correspondence language Z8 (master language should be English) in
your system using transaction SE38 and RSCPCOLA and RSCPINST. More information on
this can be found in Note 302063.
If Z8 is already used as language in your system, please contact us for further assistance.
Do not import the US English file in this case!
To make Brazilian available for all customers including those with non-unicode systems we
decided to deliver this language with a language code coming from the customers reserve.
Please maintain the correspondence language Z9 (master language should be Portuguese)
in your system using transaction SE38 and RSCPCOLA and RSCPINST. More information
on this can be found in Note 302063.
If Z9 is already used as language in your system, please contact us for further assistance.
Do not import the Brazilian file in this case!
Mexican, Canadian, Vietnamese, Hindi and Philippine (Tagalog) will only be available as
Unicode languages. Please make sure the import file for Unicode files are NOT opened as
this might destroy the data due to incorrect conversion of characters!
For Hindi please make sure your Regional Options in Windows are set up including Hindi
as the SAP GUI uses the Windows code pages to display these language symbols.
In Windows XP please check "Install files for complex script and right-to-left languages (including Thai)" and "Install files for East Asia languages".
4.1.3.2. Classification of phrase languages into different groups

CED phrases are provided in language groups according to the character sets they are based
upon. The different translations of the CED phrases are based on six different character sets
for the standard library. Therewith the translations can be divided into six language subgroups
according to their character sets as shown in the appendix (Languages/Codepages). The ISO
norm character set ISO 8859-1 is often referred to as ISO Latin 1.
Character sets are implemented on computer systems using code pages. Unfortunately, the
code pages of different systems are based in general on different character sets. SAP R/3 code
24
SAP AG
pages are based on the ISO norm character set whereas MS Windows NT or MS Windows
95 use a Microsoft format character set as basis for their code pages. Microsoft code pages
follow to an extent the ANSI norm. In general, the code pages from Microsoft differ from standard SAP R/3 code pages. An exception is the code page for Western European languages
which are identical for SAP R/3 and Microsoft.
CED phrases are provided in the Microsoft format using the Microsoft code page. No special
precautions have to be taken into account for western European languages (Latin code page).
In contrast to that, the handling of the other languages is more complicated. It is important to
note that Latin characters without any special characters are incorporated in each code page.
The fonts presented in the table are the fonts in which the phrases are supplied. In addition,
the corresponding language group specific true type fonts for Times New Roman and Courier
New provided for MS Windows NT 4.0 are also based on the Microsoft norm and can also
be used for the presentation of texts of the language group 3. Other fonts have to be tested
by the customer.
There are certain languages that can only be provided for Unicode systems as Hindi or Canadian French. Traditional Chinese will be provided as non Unicode file also, but please be aware
that not all characters are supported by the non Unicode version. Due to this we decided to
deliver Traditional Chinese as Unicode language.
Serbian (Serbocroatian with central European code page) comes with a language key d as
proposed by SAP; a Serbocroatain version using language key 0 is available on request for
customers that have maintained this as such. Normally 0 should be used for the cyrillic version
of Serbian. This cyrillic version is not within the scope of the CED languages.
Please see appendix (Languages/Codepages) for further information on code pages and necessary fonts.
4.1.3.3. Handling of different code pages within SAP R/3

In general, R/3 data are stored in SAP R/3 in the ISO norm. In case of a language that belongs
to a language group with a code page other than Western European, Microsoft and SAP code
pages differ. Therefore, a conversion takes place between the front end and the R/3 application
server. In order to do that, the SAP Native Language Support (NLS) has to be used.
4.1.3.4. Setup of language keys for phrase items within the phrase administration
All different language keys within the R/3 system are delivered by SAP as standard settings
which the customer must not change. The following language keys have to be adjusted in
the customizing for the phrase management (Specify language selection) to ensure a correct
allocation of translations to phrase items during the library import. These settings apply to R/3
3.x as well as to R/3 4.x (up to R/3 4.5A).
The language keys are presented as two characters in the R/3 application with release R/3
4.x and higher. Internally they are still handled as one character codes. Before presentation
of the language codes during the application they are internally converted. Therefore single
character language keys are still applied in the import file up to R/3 4.5A
4.1.3.4.1. Language keys of Western European phrase translations
Please see annex (Language keys) for additional information on SAP EHS language keys for
western european languages.
25
SAP AG
4.1.3.4.2. Language keys of other phrase translations
Please see annex (Language keys) for additional information on SAP EHS language keys for
other languages.
4.1.4. Proposals
4.1.4.1. Proposals for changes, corrections or expansions
Proposals for additional phrases of general interest or improvements of existing phrases
are welcome. If you want to pass a proposal on to us please use the proposal sheet
Phrase_Services_Proposals.xls and attach the maintained file to a new issue in our helpdesk
system. If you rely on regulatory documents or have any other source for your phrase proposal
it is always helpful to attach this information and the related document as well.
4.1.4.2. Correction of mistakes

In case you find an spelling error you are also welcome to pass this information on to us. We
will get back to you as soon as possible with an information on if and how the phrase texts
should be corrected. Please do not change CED phrases without this process as these might
be overwritten in one of the next updates.
4.1.5. Content of Phrases packages

The phrase delivery contains importfiles in Windows and Unix format for direct use in SAP
EHS. For a complete overview of all multilanguage phrase library files included in this delivery,
please see the list of phrases files.
4.2. Implementation
To make use of the phrases following steps have to be done: Create passive phrase catalogue
CED, upload the delivered files and import phrases. The following chapters describe how to
do this.
4.2.1. Create passive phrase catalogue CED

First of all the passive phrase catalogue CED has to be created.
4.2.1.1. How to create passive phrase catalogues

To create a passive phrase catalogue start the IMG customizing (transaction spro) navigate
to Environment, Health & Safety -> Basic Data and Tools -> Phrase management -> Specify
Phrase Libraries and Phrase Groups.
Requirements : You have already defined the number ranges for the phrase key.
Note
One library has to be the active library.
It is possible to adopt phrase libraries from non-SAP systems.
26
SAP AG
You can use all libraries available on the market that support the conversion formats
of the SAP component Environment, Health and Safety (EHS).
Following entries must be made:
Phrase library
CED
Label
CED for EHS
Note
optional
Active library
remains empty
Distributor
Chemical Exchange Directory
Publication Date
Version
library version
Phr. ChkRtn
Object name
ESN_PHRID
Int. no. range
0I
Ext. no. range
0E
4.2.2. Upload files

This chapter describes which files have to be uploaded and how this upload has to be performed.
4.2.2.1. How to upload files

Upload all phrase import files and the phrase set assignment file from your local drive to the
application server.
Ask your administrator for the upload path on your application server. You may check for the
path also via transaction AL11.
For example :
\\<server>\ \\Globaltrans\trans or F:\usr\sap\trans\upload
Use transaction CG3Z for uploading and choose BIN(ary) transfer format as shown in the
screen shot below.
Size of path and filename is limited. It may be necessary to either shorten the import file names
or choose a short directory path to upload the files.
27
SAP AG
Please check that you upload the correct files for the operating system of your application
server. The update delivery includes import files formatted for MS Windows and UNIX. You
can get info about the OS in R/3 at -> System -> Status. Under the "Host data" header you can
see the operating system used by the R/3 server. You may also have to consider if Unicode
or Non Unicode system.
The upload of import files onto the application server and the import into EHS are completely
independent from any language specific settings on the front-end PC, i.e. phrases can be
uploaded and imported with every regional default setting.
4.2.2.2. Load of import files into EHS

Apart from the special settings which are necessary for a correct display the import file can be
loaded into the system according to the previous descriptions as update of the passive CED
phrase library.
4.2.2.2.1. Editing the header entries of the import file
In general changes to the importfiles are not recommended.
In case an importfiles has to be altered for special reasons, please use a text editor as Notepad
or Textpad to display and edit the files.
Apart from changes to header data (e.g. library date) no changes must be made within the
import file! The library key must contain characters from the English alphabet only (no special
characters).
Warning:
Do not open unicode files! They could be destroyed due to character conversion when opening
the files with an improper tool.
4.2.2.2.2. Special features concerning languages with differing codepages
The import of translations beyond the Western European codepage into a system that already
contains Western European phrases is to be handled as a library update . As the allocation
of phrases to phrase sets is language independent it has not to be updated when the phrase
set allocation has been loaded before.
4.2.3. Import phrases

After uploading the files, the phrases will be imported in EHS in the passive phrase catalogue,
merged up with the active catalogue and assigned to the phrase sets.
4.2.3.1. How to import phrases

Choose Data Transfer - > Phrases (Transaction CG31) ; please see screen shot below.
"File with path" - Enter the path and file name (same as target file section upload files )
"Character standard" - Choose MS-NT for all files that have no _unicode.dat ending in their
filename; this applies also to unicode systems!
For files with unicode only languages ( with _unicode.dat ending in their filename) choose
UTF-8 as character standard.
28
SAP AG
You can leave all other options blank
Optional: You can limit the import to certain languages if you want (Button "Language selection" )
Check the file (F5)
Carefully check the displayed information before importing the phrases. Make sure you import to the passive CED or TDCLE library, the versions are correct and no errors are displayed.
If necessary approve the message "Date of phr. lib. to be imported is identical to date of
current library", this is just for your information.
However if the file you want to import is older than the library in your system, you can not
import it. Please make sure you have chosen the correct import file. In section upload files
you can also find information on how to change the header data of your import files.
Choose "Transfer/start time" (F6)
Choose "Immediate" or specify a time
Save
Note
For the TDCLE phrase library you have the choice to import either a single unicode
file including all languages, except for American English and Canadian French, or
separate import files based on the language group.
Due to the size of the phrase library and technical limitations with the phrase import
functionality, the option of a single import file for all languages is currently not available for the CED library.
Phrase import files for CED and TDCLE libraries include all phrases of the library,
not only those that are new or updated. Please be aware that all manual changes
made in your CED or TDCLE phrases will be overwritten.
Caution
Please do not set the flag for full import as this will delete your
passive library!
29
SAP AG
4.2.3.2. How to merge phrases

To merge phrases from a passive catalogue into the active, use transaction cg12 and start
with :
1. Select the phrases to be merged.
If you are updating your phrase library, we recommend to restrict the phrase selection to
only new and revised phrases. Please use the Phrase created/changed... functionality with
the settings shown in the screenshot:
30
SAP AG
2. Go to the menu bar ->extras->merge
and select merge.

3. Pressing the "Adopt phrase ID" Button you will take the same phrase IDs into the active
catalogue as you have in the passive one.
31
SAP AG
Note
It is not recommended to press the "Determine target phrase" - button as this may
select phrases as target phrases that are not appropriate or may not have e.g. all
language translations.
Note
The merging process normally does not perform well when processing several thousand phrases at one time. Therefore, we strongly recommend that only a part of the
phrase library is merged at one time (e.g. filtered by phrase groups or phrase keys).
4.2.3.3. How to import phrase set assignments

Prior to importing phrase set assignments, the phrases have to be merged into the active
library. After uploading the phrase set assignment file, the assignments should to be imported
into SAP EHS.
Choose Data Transfer - > Phrases (Transaction CG31)
Check the "Phrase Set Assignmt" option as shown in the screenshot below
Check the file (F5)
32
SAP AG
Sometimes none or only a few assignments are imported. If you encounter this error, the first
step would be to run this import several times until no more phrases are assigned to phrase
sets. If this does not help an easy work-around is to change the name of the phrase library in
the import file to the name of your active library. Upload and import this modified file. In section
upload files you can also find information on how to change the header data of your import files.
As the phrase set assignment files are based on the latest SAP EHS standard property tree
there will be warnings in the logfile of the import if your system is not updated with the latest
standard property tree. These warnings can usually be ignored. Customers with valid maintenance contracts for SAP EHS Regulatory Content - expert rules for substance and mixture
classification or - substance lists and reference data receive the latest tree as part of their
33
SAP AG
regular maintenance. Should you need any additional info on this topic please feel free to
contact us.
4.2.4. Individual changes on CED phrases

This chapter provides information how to create phrase variants.
4.2.4.1. How to create phrase variants

In the phrase library there are several phrases including.? in the phrase text, e.g. .?C. If you
wish to use such a phrases with a specified temperature e.g. 10C, please create a variant
of this phrase.
To do so, create a hit list with the original phrase, mark the phrase and create a copy
(Phrase_CopyTemplate). Then choose a new phrase key starting with P (for permutation) and
safe the new phrase.
Replace the ? in each language of the new P phrase with the chosen number or customer
specific information, in this case 10, and safe again.
Please do not alter the original CED phrase as your changes might be overwritten in one of
the following updates.
It is also possible to replace the qualifier .? automatically by using special user exits at the
phrase. Please see SAP Note 1373615 for more information.
In addition there is a standard functionality for special qualifiers available, that may insert phrases like target organs into another phrase.
Example:
"Causes damage to organs (/$/*_ORG_SING_ORAL/$/) if swallowed." The functionality
would replace the placeholder with the values stored in *_ORG_SING_ORAL (e.g. in
SAP_EHS_1023_044 GHS Target Organs for single exposure, oral). Please note that this
functionality might not work correctly in all languages, because the value used might have an
impact on the wording of the phrase in some languages. It usually works in most Western
and Eastern European languages. Until now, this functionality is able to manage phrases only.
Other values as e.g. numerical ones are not yet covered.
Please see SAP Note 146663 Placeholder phrases for EH&S reports for details on how to
implement the placeholder functionality and how to use it in phrases and WWI templates.
4.2.4.2. Adding of customer specific phrase groups

Customer specific phrase groups within an active library can only have alphanumeric codes
as CED uses numeric coded phrase groups only (e.g. X.... or Y.....). The CED phrase groups
18.00 Reserve 1 and 19.00 Reserve 2 are only available for CED!
4.2.4.3. Customer specific changes / extensions of phrases

There are no other changes on the CED library allowed than the described correction of spelling
or grammar mistakes. All changes will be overwritten with the following update. In case the
customer wants to modify an existing CED phrase or add a new phrase he must copy it to
new own phrase key.
34
SAP AG
These phrase keys must not be within the CED name space! For this two possibilities are
available:
a) The new phrases can be added using the automatic key assignment. In this case the system
itself assigns the phrase keys automatically from the internal number range (0I). However if
these phrases shall be transferred to any other system later on there might be the danger of
overlapping phrase keys concerning the automatically edited keys and the keys of the target
system. An automatic phrase import would then not directly be possible. The phrases had
rather to be loaded as passive library and then to be merged into the active library.
b) New phrases can be added using keys from the external number range (0E). To make these
customer phrases distinguishable from CED phrases the corresponding customer phrase keys
have to start with X or Y only with the exception of those phrases beginning with P (see below).
4.2.4.4. Adding CED permutations

The CED-library contains about sixty phrases with a question mark within the text. These
phrases can be completed as defined by the customer. Example: N15.00511320 "Keep at
temperature not exceeding .?C.. In order to enable a specific usage of this phrase the customer has to copy his desired permutation to a new phrase key beginning with P (permutation).
Example:
P15.00511320 "Keep at temperature not exceeding 25C.
P15.00511321 "Keep at temperature not exceeding 30C.
After the question mark has been replaced by the desired value in every phrase item the phrase
is available within the complete scope of translations.
In case the question mark does not symbolize a numeric value but one or several words (e.g.
N07.00312430 "Keep contents under .?) CED offers a customer specific translation service
on demand (subject to extra charges).
In addition to that, from EHS 2.5B on the functionality is available to replace the placeholder ?
by a value from a different field in the EHS properties tree.

The following steps describe how to check the implementation of SAP EHS Regulatory Content
- multilanguage phrase library for hazard communication.

Please use the following check list as guidance through the phrase library implementation and
as check list after the implementation.
Status
Where to do
What to do
General
O
Technical Part
O
Customizing (spro)
Create passive phrase catalogue
35
SAP AG
O
SAP EHS (cg3z)
Upload phrases
Upload phrase set assignments
SAP EHS (cg31)
Import phrases
SAP EHS (cg12)
Merge phrases
SAP EHS (cg31)
Import phrase set assignments
36
SAP AG

Content - substance lists and
reference data
SAP EHS Regulatory Content provides substance lists and reference data for Product Safety
and transport regulations for Dangerous Goods for SAP EHS. Data will be delivered through
the open interface tool SAP EHS Open Content Connector (OCC) which allows manual and
automatic loading of data into the specification database of SAP EHS.
Available data for Product Safety are:
Classification and labelling

Occupational Exposure Limits
Global Inventories
Prohibitions and restrictions
Numerous national regulations for amongst others product safety, health and environment,
e.g. German WGK, US state Right-to-know, Danish MAL-Code
Data is available for the following Dangerous Goods regulations:
ADG - Australian Dangerous Goods Code

ADR - European Carriage of Dangerous Goods by Road
ADN - European Carriage of Dangerous Goods by Inland Waterways
49CFR - USA Code of Federal Regulations 49 - Transportation
CN_DG - Road Transportation of Dangerous Goods in China
IATA - International Air Transport Dangerous Goods Regulations
IMDG - International Maritime Dangerous Goods Code
KR_DG - Korea Dangerous Goods Regulations
MERCOSUR - Dangerous Goods Regulations South America
MX_DG - Regulation for the land transport of hazardous materials and wastes in Mexico
NZ_DG - New Zealand standard for transport of dangerous goods on land
RID - European Carriage of Dangerous Goods by Rail
TDG - Canadian Transport Dangerous Goods Directorate
UN_DG - UN model regulations (orange book)
beside Dangerous Goods classification additional data are available for some of the regulations
mentioned above as:
Packaging codes and maximum quantities

Limited and excepted quantities
Special provisions
Storage categories
37
SAP AG
SAP EHS Regulatory Content - substance lists and reference data

Transport category
The following chapters describe the initial implementation of SAP EHS Regulatory Content. If
you are using both Product Safety and Dangerous Goods data, you have to do all steps twice,
for each package separately. If the process is different for Product Safety and Dangerous
Goods, it will be mentioned in the documentation.
The substance lists and reference data require additional customizing activities. These customizing entries are described in the respective area in this documentation's appendix. It is
recommended to perform these steps before implementing the substance lists and reference
data.
The following prerequisites exist for implementing and using substance lists and reference
data:
If substance lists and reference data is used with the Expert Rules, the latest data should be
loaded before running the Expert Rules.
This implies importing the newest phrases, too, which is a prerequisite for loading the data
correctly.
If the latest Expert Rules are run on old data, wrong results may be determined.
5.1.2. Schematic Diagram Open Content Connector
38
SAP AG
5.1.3. Content of substance lists and reference data packages

Each substance lists and reference data implementation package consists of the following
parts:
Documentation including user manual, release notes, content reports and training presentations.
Latest SAP EHS Open Content Connector setup
SAP EHS customizing transports and/or BC sets
Phrase import files
Substance lists and reference database
Mapping database
Other files like analysis tools, acceptance report
For a complete overview of all files included in this delivery of substance list and reference
data, please see the list of data files.
5.2. Implementation
The following chapters describe how to implement SAP Regulatory Content - substance lists
and reference data. The basic implementation is identical for all packages, both Product safety
and Dangerous Goods. Differences are always highlighted by notes in the relevant chapter.
The implementation process consists of the following steps divided into a technical part and
a part for regulatory experts:
Technical Part
Install SAP EHS Open Content Connector

SAP EHS Customizing
Import of multilingual phrases
Installing the substance lists and reference database
Installing the mapping database
Installation of additional tools
Manual adjustments
Regulatory Part
Review Filter Settings
Use of additional tools
5.2.1. EHS OCC

The following steps describe how to install and configure EHS OCC.
5.2.1.1. Install EHS OCC

On each front-end computer that is used for substance lists and reference data loads, SAP
EHS Open Content Connector (OCC) needs to be installed. OCC in the latest version is part
of the SAP EHS Expert installation package.
39
SAP AG

If your current OCC version is lower than Service Pack 18, we highly recommend that you upgrade all OCC installations to this version. See the Release Notes document for new features
of the latest OCC version.
5.2.1.1.1. What is EHS OCC
EHS OCC or OCC is the abbreviation for SAP EHS Open Content Connector.
OCC is an interface based on an open XML format which allows content providers to provide
regulatory content and other data into SAP EHS specifications.
OCC is part of SAP EHS and does not require an additional license. OCC is bundled with
SAP EHS Expert into the same setup package and shares some common functionalities and
program files with Expert.
OCC offers functionalities for manual single substance data loads, automatic mass loads, as
well as update and simulation functionalities.
5.2.1.1.2. Where to get EHS OCC
You will find the installation program for EHS OCC on the current SAP Server Components
CD.
The current EHS OCC Version and patches for EHS OCC are also available on the SAP
Support Portal on SAP Service Marketplace. You can find the patches for EHS OCC on SAP
Service Marketplace under 'Support Packages & Patches' (http://service.sap.com/patches)
Detailed information on how to obtain the latest version of OCC can be found in SAP note
568302.
5.2.1.1.3. How to install EHS OCC
On each front-end computer that is used for loads of SAP EHS Regulatory Content - substance
lists and reference data, SAP EHS Open Content Connector (OCC) needs to be installed.
OCC in the latest version is part of the SAP EHS Expert installation package. If your current
OCC version is lower than Service Pack 20, we highly recommend that you upgrade all OCC
installations to this version. See the SAP EHS Regulatory Content Release Notes document
for new features of this OCC version.
Note
For installation local administrator rights might be required. Registry settings will be
added under the following paths:
SAP EHS OCC Service Pack 20 and below:
HKEY_LOCAL_MACHINE\SOFTWARE\TechniData\EHS-AddOns\Systems
HKEY_LOCAL_MACHINE\SOFTWARE\TechniData\EHS-AddOns\Instances
SAP EHS OCC Service Pack 21 and higher:
HKEY_CURRENT_USER\Software\EHS-AddOns\Systems
HKEY_CURRENT_USER\Software\EHS-AddOns\Instances
HKEY_CURRENT_USER\Software\EHS-AddOns\Open Content Connector
40
SAP AG

5.2.1.1.3.1. Initial Installation/Upgrading of older OCC versions
1. Make sure that your front-end computer fulfills the system requirements listed in chapter
Prerequisites.
2. Download the latest SAP EHS Expert and OCC setup files. See chapter Where to get EHS
OCC for details.
3. Run Expert/OCC Setup
4. Choose Option "Open Content Connector". If Expert rule sets are used on this computer,
additional setup options may be required.
5. ODBC-(Database) drivers to access mapping databases are installed automatically, if they
do not already exist.
5.2.1.2. RFC connection

Check that the RFC-connection EHS_OCC exists and is working. If it does not exist, create a
new TCP/IP RFC connection with the following parameters:
RFC Destination
EHS_OCC
Connection Type
T (TCP/IP connection)
Description
EHS Open Content Connector
Start on Front End Workstation
$shell\ehsOCC.exe
Detailed information how to create and test a RFC connection can be found in the following
chapters.
5.2.1.2.1. Why do you need a RFC connection
EHS OCC is an Microsoft Windows PC program that is executed on the front-end computer
and not on the SAP EHS application server. This program communicates via RFC connection
with the EHS database using a standardized BAPI interface.
5.2.1.2.2. How to setup a RFC connection
The Remote Function Call destination (RFC destination) in the SAP system has to be set up for
EHS Expert and OCC. It is recommended to use the EHS Administration Service and therefore
a RFC destination for the Administration Server has to be set up additionally.
To set up a RFC destination choose from the SAP Easy Access screen Tools --> Administration --> Network --> RFC Destination (transaction sm59). The Display and Maintain RFC Destination screen appears. Then setup the RFC connection for the EHS Service Administration,
the EHS Expert and OCC as follows:
RFC Destination for EHS Management Service
1. Choose Edit -> Create.
The RFC Destination screen appears. Enter the following data:
RFC destination: We recommend you
EHS_MGMT_<computer name of server>
Connection type: T
41
structure
the
name
as
follows:
SAP AG
2.
3.
4.
5.
Gateway options: If your SAP system comprises a number of application servers, you
must specify under Gateway Options the gateway under which the EHS management
server has registered itself.
Description: Enter a text to describe the RFC destination.
Confirm your entries.
On the Technical Settings tab page in the Activation Type screen area, set the flag to Registered Server Program.
In the Registered Server Program screen area, enter the PROGID entry from your installation (see How to install EHS Expert or entry in the file SAPRFC.ini) in the program ID field.
Save your entries
RFC Destination for EHS Expert

RFC destination: Name of your RFC destination, for example EHS_EXPERT
This entry corresponds to the entry for the EXPERT_DESTINATION parameter for the
user exit of the EHS Expert (see Extend Entry in Secondary Data Determination). We
recommend to use the same name for your systems in order to transport customizing
settings easily.
Connection type: T
2. Confirm your entries.
3. On the Technical Settings tab page in the Activation Type screen area, set the flag to Registered Server Program.
4. In the Registered Server Program screen area, enter a unique identification in the Program
ID field. The program ID corresponds to the PROGID in the SAPRFC.ini.
42
SAP AG

5. If the SAP system comprises a number of application servers, you must specify under Gateway Options the gateway of the application server under which the EHS Expert server has
registered itself. Enter the values for the parameters GWHOST and GWSERV from the
SAPRFC.INI file of the EHS Expert server for the input fields Gateway host and Gateway
service.
6. Save your entries
RFC Destination for OCC

RFC destination: Name of your RFC destination, for example EHS_OCC
user exit(s) of SAP EHS Regulatory Content - substance lists and reference data (see
Extend Entry in Secondary Data Determination). We recommend to use the same name
for your systems in order to transport customizing settings easily.
Connection type: T
43
SAP AG

Description: Enter a text to describe the RFC destination: EHS Open Content Connector
3. On the Technical Settings tab page in the Activation Type screen area, set the flag to Start
on Frontend Work Station.
4. In the Start on Frontend Work Station Program screen area, enter $shell\ehsOCC.exe
5.2.1.2.3. How to test the RFC connection

To test the RFC destination, you must have started the EHS Expert server and the above step
Create the RFC Destination must have been completed.
In the SAP Easy Access screen, choose Tools -> Administration -> Administration -> Network -> RFC Destinations (transaction SM59).
44
SAP AG

In the RFC Destinations tree, choose TCP/IP connections -> <name of your RFC destination> and open the destination with a double-click.
Choose Test connection.
The test is running successfully if transmission duration times are displayed in the SAP window.
5.2.2. SAP EHS Customizing

The use of OCC as interface requires some additional settings in SAP customizing. In addition,
substance lists and reference data makes use of SAP EHS customizing settings that are not
part of the SAP standard and which need to be added.
The following customizing tasks are described below:
Setting up a secondary data determination user exit

Adding data origins
Adding a passive phrase library
Adding user defined text types
Adding regulatory lists
Adding literature sources
Adding identifier types
Adding dangerous goods master data settings
Checking validity areas
Extending the specification search functionality
5.2.2.1. Secondary Data Determination User Exit

In order to use OCC to load data into the specification database, a secondary data determination user exit must be created in SAP EHS customizing. Product Safety and Dangerous Goods
content package require two separate user exits.
45
SAP AG

The required user exits are included in the customizing transport Basic Customizing of each
content package for substance lists and reference data. As an alternative, you can create the
user exits manually with the description below.
5.2.2.1.1. via customizing transport
Please see which files are provided for upload.
Upload files
Additional information how to upload files is provided within this document Section 4.2.2.1,
How to upload files
Import transports
Please find detailed information about this customizing activity within this document Section 3.2.2.1, How to import transports (customizing or workbench)
Import BC-Sets
Please find detailed information about this customizing activity within this document Section A.4, How to import BC sets
5.2.2.1.2. via manual customizing
5.2.2.1.2.1. How to extend entry in secondary data determination
In the example at the bottom you can see the typically used entries for secondary data determination with Expert rule sets and OCC data loads. The required entries for the specific rule
sets are explicitly given in the functional description of the rule set and in the appendix for SAP
EHS Regulatory Content - substance lists and reference data.
Activities
1. In Customizing for Basic Data and Tools, call the IMG activity Manage User Exits.
2. Create a new user exit with user exit category SUB_SEDACA using
C1E5_SUB_EXPERT_EVALUATE as Function Module (copy the entry of a DEMO-rule set
as template for your new user exit).
3. Choose Parameters and Values.
46
SAP AG

The following environment parameters must be set up for the reference modules
C1E5_SUB_EXPERT_EVALUATE:
EXPERT_COMMIT_MODE
Specifies the backup mode for secondary data determination by the EHS Expert.
If you enter the value I, the SAP system creates the new data records that were determined
by the EHS Expert without changing other data records.
If you enter the value D, the SAP system deletes all the existing data records and creates
the newly determined data. If the EXPERT_RES_BY_SRSID_OWNID_FLG parameter is
set, then only those data records are deleted that were determined during previous runs of
the EHS Expert. Using the data origin (parameter EXPERT_WRITE_SOURCE_ID) and the
data provider (parameter EXPERT_WRITE_OWNER) the SAP system recognizes which
data was determined previously by the EHS Expert.
Note
You can determine the address number of the data provider in Customizing for Basic
Data and Tools in the IMG activity Specify Authorization Groups. To do this, call the
input help for the Data prov. field in the IMG activity. You will find the value you require
in the Addr. no. field. The address number is not displayed in address management
in the Product Safety component.
If you enter the value C the SAP system resets the active indicator for the newest of the
data records and deletes all other existing ones. The number of data records to be deactivated can be derived from the parameter EXPERT_NUM_OF_DEACT_VALUATION.
The data records that were newly determined by the EHS Expert are also created. If the
EXPERT_RES_BY_SRSID_OWNID_FLG parameter is set, then only those data records
are deleted that were determined during previous runs of the EHS Expert. This helps
you prevent data records being deleted inadvertently. The SAP system uses the data origin (parameter EXPERT_WRITE_SOURCE_ID) and the data provider (parameter
EXPERT_WRITE_OWNER) to recognize which data was determined previously by the EHS
Expert.
EXPERT_DESTINATION
Corresponds with the name of the RFC destination that is entered under Tools -> Administration -> Administration -> Network -> RFC Destinations (transaction SM59) (for example
EHS_EXPERT).
EXPERT_READ_RATING and EXPERT_READ_VALIDITY_AREA
Determine the rating and validity area for which the data is transferred from the SAP system
to the EHS Expert.
EXPERT_WRITE_RATING and EXPERT_WRITE_VALIDITY_AREA
Determine the rating and validity area with which the data determined is stored in the SAP
system. In the EHS Expert set of rules you can also specifically define a different rating and
validity area that are used when storing data in the system.
EXPERT_READ_USAGE_1...n and EXPERT_WRITE_USAGE_1...n
These parameters can be used in addition to the two previous parameter pairs. You can
specify any number of usages in the format VACLID/RVLID/EXCLFLG (rating/validity/exclude indicator). The parameter numbering has to start with 1 and has to be consecutive.
47
SAP AG

Examples
EXPERT_READ_USAGE_1:PUBLIC/REG_EU EXPERT_READ_USAGE_2:PUBLIC/DE/X
In this example, the system reads all data records that are valid in the EU but not in Germany.
EXPERT_WRITE_USAGE_1:PUBLIC/REG_EU
EXPERT_WRITE_USAGE_2:PUBLIC/US
In this example, the system writes all data records that are valid both for the EU and for
the USA.
EXPERT_WRITE_SOURCE_ID
Data origin that must be created in the IMG activity Specify Data Origin.
If no data origin is created, the system issues an error.
EXPERT_RULE_SET
Name of the rule set
The following environment parameters can be set up for the reference module
C1E5_SUB_EXPERT_EVALUATE (not all possible parameters are described here):
EXPERT_COMMIT_FLG
If you set this indicator to X, the system calls the update function specified in the parameter
EXPERT_COMMIT_FUNCTION after the calculation is finished on the Expert server.
If you do not set this indicator, the EHS Expert server directly calls the update function. In
a productive system, we recommend that you set the indicator so that the Expert server is
available again more quickly for other parallel calls. During development and testing it may
be useful to not set the indicator, so that error messages from the update function are logged
in the log files and so you have the option of displaying the runtime of the update function
on the console or in the event display.
EXPERT_NUM_OF_DEACT_VALUATION
Determines the number of data records that are not deleted for save mode C, but are set
to inactive.
EXPERT_PARAMETER_CHANGE_MODE
If you enter the value S (default), the SAP system displays the Determine Secondary Data dialog box in display mode when starting secondary data determination using the EHS
Expert.
If you enter the value E you can revise the environment parameters in the Determine Secondary Data dialog box when starting secondary data determination using the EHS Expert.
The environment parameters you specified in Customizing are displayed as default values.
If you enter the value H the SAP system does not display the Determine Secondary Data
dialog box when starting secondary data determination using the EHS Expert.
EXPERT_RES_BY_SRSID_OWNID_FLG
Set this indicator if in backup modes C or D only data is to be deleted by the EHS Expert
that was determined during previous runs of the EHS Expert.
48
SAP AG
Warning
If you do not set this indicator, data that has also been entered manually or imported
can be deleted in backup mode C or D by the EHS Expert during secondary data
determination.
EXPERT_WRITE_OWNER
Data provider that you must have created in the SAP component Product Safety under Tools
-> Addresses -> Edit Data Providers. The data provider must always be entered with 10
digits.
If you do not specify a data provider, the SAP system uses the authorization group for the
specification to determine the respective data provider (see IMG activity Specify Authorization Groups). If the SAP system does not find any data providers there, it creates the data
without a data provider.
EXPERT_HIDDEN_PROCESSING_MODE
You can choose between two operating modes.
ONLINE (default): The EHS Expert run starts immediately after you choose Execute.
BACKGROUND: The EHS Expert runs as a background job. The indicator for the parameter
EXPERT_ASK_FOR_STARTTIME must be set for the start time prompt.
EXPERT_ASK_FOR_STARTTIME
If you set this indicator, you will be prompted in a dialog box when the EHS Expert is to start
as a background job.
EXPERT_ADD_PARAM_1...n
You can pass any number of parameters to the set of rules. This means you can make sets
of rules configurable. In the set of rules you must create a fact for this purpose that is mapped
to the external ID P:I_TAB_PARAM in fact mapping.
EXPERT_WRITE_RUN_DATE
With this parameter, the Expert will write the current date with each run of
the given Expert rule: Enter the value X here, and set the further parameters EXPERT_EXPLANATION_ESTCAT, EXPERT_EXPLANATION_RULE_PROP, and
EXPERT_EXPLANATION_DATE_PROP as described below.
You set up the explanation component (optional) of the EHS Expert using the following parameters:
EXPERT_EXPLANATION_DISPLAY
If you set this parameter to X and allow the set of rules to run in the foreground, the system
displays the explanation immediately after the set of rules run. For sets of rules that run in
the background, the system does not display the explanation automatically.
EXPERT_EXPLANATION_SAVE
Set this parameter to X if you want to save the explanation for the set of rules run in the
specification. If you set the parameter to X, you must also edit the following parameters:
EXPERT_EXPLANATION_ESTCAT
49
SAP AG

In this parameter you specify the value assignment type in which the explanation is to be
saved as a user-defined text. The standard version of the demo sets of rules contains the
entry SAP_EHS_0101_002. This value assignment type is not in a property tree because
the explanation is not displayed as a user-defined text but in the menu.
EXPERT_EXPLANATION_RULE_PROP
In this parameter you specify the characteristic in which the name of the set of rules is
saved to allow its assignment when displayed at a later stage. The characteristic must be in
the same value assignment type as the user-defined text for the explanation. The standard
version of the demo sets of rules contains the entry SAP_EHS_0101_002_RULESET.
Note
If you run a master data match up, the system automatically appends a phrase set
and a check module to the characteristic. You must remove this check module again.
EXPERT_EXPLANATION_DATE_PROP
In this parameter you specify the characteristic in which the current date is written with each
rule run. The characteristic must be in the same value assignment type as specified in the
parameter EXPERT_EXPLANATION_ESTCAT. The standard version of the demo sets of
rules contains the entry SAP_EHS_0101_002_RUN_DATE. The last run date is only written
when triggered separately with the parameter EXPERT_WRITE_RUN_DATE.
EXPERT_EXPLANATION_TEXTCAT
In this parameter you specify the user-defined text type with which the explanation is to be
saved in the specification. The standard version of the demo sets of rules contains the entry
EX.
EXPERT_ADD_PARAM_1
In this parameter you specify the path and name of the index / header file of your SAP EHS
Regulatory Content database.
EXPERT_ADD_PARAM_2
In this parameter you can specify a user name to access your SAP EHS Regulatory Content
database if it is stored in a password protected storage location or web server.
EXPERT_ADD_PARAM_3
In this parameter you can specify a password to access your SAP EHS Regulatory Content
EXPERT_TAB_FIELD_1
This parameter is the specification key from SAP EHS, it should not be changed.
EXPERT_TAB_FIELD_2
In this parameter you specify the identifier that OCC should use when looking for substance
data. This is usually either the CAS or the UN number.
EXPERT_TAB_FIELD_3
In this parameter you specify the identifier that OCC should use for display. Choose an
identifier that is available for all substances like synonym name.
EXPERT_TAB_FIELD_4
50
SAP AG

In this parameter you can specify a second identifier that OCC should use when looking for substance data. This is identifier is only used when the identifier specified in
EXPERT_TAB_FIELD_2 does not give a search result. The main purpose is for loading data
that is not assigned to CAS numbers.
Typical Example Expert Rule set:
Environment parameter
Sample value
EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION
C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
SAP_EHS_0101_002
SAP_EHS_0101_002_RULESET
EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_READ_RATING
PUBLIC
EXPERT_READ_VALIDITY_AREA
REG_WORLD
EXPERT_RULE_SET
ZEXP_GHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHS
EXPERT_WRITE_VALIDITY_AREA
REG_WORLD
Typical Example OCC data load:

Sample Value
EXPERT_ADD_PARAM_1
headerurl=<path
to
CLEO
PS
DB>\PS_DB
\header.xml
EXPERT_ADD_PARAM_2
usernameurl=x
EXPERT_ADD_PARAM_3
passwordurl=x
EXPERT_CALL_ONCE
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_OCC
51
SAP AG

EXPERT_READ_RATING
EXPERT_RULE_SET
CLEO_PS
EXPERT_TAB_FIELD_1
<subid>
EXPERT_TAB_FIELD_2
<identifier>[NUM,CAS]
EXPERT_TAB_FIELD_3
<identifier>[NAM,SYN]
EXPERT_TAB_FIELD_4
<identifier>[NAM,TRIV]
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
TECHNIDATA
REG_WORLD
5.2.2.1.2.2. Settings
Please find the proposed settings for the user exits.
5.2.2.2. Data Origin

OCC is writing substance lists and reference data with a specific data origin into the specification database, which must be created in SAP EHS customizing. Product Safety and Dangerous Goods content package use the same settings.
The required data origin is included in the customizing transport Basic Customizing of each
content package for substance lists and reference data. As an alternative, you can create the
data origin manually with the description below.
Upload files
How to upload files
Import transports
If you maintain the data origins manually, please find the proposed settings for the data origin(s)
5.2.2.2.2.1. How to add data origins
To add new data origins use transaction "spro" for the IMG customizing. Navigate to Environment, Health & Safety ->Basic Data and Tools -> Tools -> Import ans Export -> Basic Settings
for Import and Export -> Specify Data Origins.
Press F5 or "New Entries"
52
SAP AG
Enter the Data Origin (limited to 10 characters)

Optionally you may assign an Exchange Profile
Give a note / description
Save your settings
5.2.2.3. Phrase Catalogue

SAP EHS Regulatory Content - substance lists and reference data makes use of multilingual
phrases stored in a SAP EHS phrase catalogue. A new passive phrase catalogue TDCLE
needs to be added in customizing.
The required phrase catalogue is included in the customizing transport Basic Customizing
of each content package for substance lists and reference data. As an alternative, you can
create the phrase catalogue manually with the description below.
Note
Dangerous Goods Basic data package does not require a phrase catalogue, only Product Safety and extended Dangerous Goods with packaging data make use of phrases.
Upload files
How to upload files
Import transports
This chapter describes how to create passive phrase catalogue TDCLE and how to setup
number ranges.
Please find the proposed settings for the phrase catalogue .
53
SAP AG

5.2.2.3.2.1. How to create passive phrase catalogues
Requirements : You have already defined the number ranges for the phrase key.
Note
Phrase library
CED
Label
CED for EHS
Note
optional
Active library
remains empty
Distributor
Publication Date
Version
library version
Phr. ChkRtn
Object name
ESN_PHRID
Int. no. range
0I
Ext. no. range
0E
5.2.2.3.2.2. How to setup number ranges

Here the interval limits of the internal (0I) and the external number range (0E) must be entered.
The internal number range is assigned by the system itself while the automatic key definition
whereas the external number range must contain all phrase keys which are not produced
automatically but entered manually or by phrase import.
EH&S 2.5B and newer: Implementation Guide for R/3 Customizing (IMG) / Environment, Health
& Safety / Product Safety / Phrase Management / Specify Number Ranges for Phrases
EH&S 3.2 and newer: Implementation Guide for R/3 Customizing (IMG) / Environment, Health
& Safety / Basic Data and Tools / Phrase Management / Specify Number Ranges for Phrases
To import the CED phrases the external number range 0E must have the alphanumeric interval
from A to ZZZZZZZZZZZZZZZ.
We recommend to designate the internal number range 0I for numeric values only (interval
100000000000000 to 899999999999999).
5.2.2.4. User defined text types
54
SAP AG

OCC uses a special user defined text type called OCCUNQID (OCC unique record ID) that is
required to link data sets between SAP EHS and the external substance lists and reference
database. In addition, some packages of SAP EHS Regulatory Content - substance lists and
reference data require additional user defined text types like NOL (name on list). These user
defined text types need to be created in SAP EHS customizing.
The required user defined text types are included in the customizing transport Basic Customizing of each content package for substance lists and reference data. As an alternative,
you can create the user defined text types manually with the description below.
Upload files
How to upload files
Import transports
Please find the proposed settings for the User Defined Text Type. .
5.2.2.4.2.1. How to add user defined text types
To add new data origins use transaction "spro" for the IMG customizing. Navigate to Environment, Health & Safety ->Basic Data and Tools -> Specification Management -> Additional Information for Value Assignment -> Specify User-Defined Text Types.

Enter the user defined text types (limited to 10 characters)
Assign a specification category
Save your settings
5.2.2.5. Regulatory Lists

All data sets and identifiers in the substance lists and reference database are assigned to a
specific regulatory list. These regulatory lists need to be created in SAP EHS customizing.
The required regulatory lists are included in the customizing transport Master Data Customizing of each content package for substance lists and reference data. As an alternative, you can
create the regulatory lists manually with the description below.
Upload files
How to upload files
55
SAP AG

Import transports
Please ask us for details if you want to manually customize regulatory lists for substance lists
and reference data.
5.2.2.5.2.1. How to add regulatory lists
Start transaction "spro" and navigate to: Environment, Health and Safety -> Basic Data and
Tools -> Specification Management -> Specification Master -> Specify Regulatory Lists
Press F5 or " New Entries"

Enter the short form of the regulatory list (limited to 10 characters)
Give a description and other additional information
switch to the navigation side bar on the left side and double click "Specification Category"
Enter new Entries e.g "SUBSTANCE" for which the List will be valid.
Save your settings
5.2.2.6. Literature Source

All data sets in the substance lists and reference data are assigned to a specific literature
source. These literature sources need to be created in SAP EHS customizing.
The required literature sources are included in the customizing transport Master Data Customizing of each content package for substance lists and reference data. As an alternative,
you can create the literature sources manually with the description below.
56
SAP AG

Upload files
How to upload files
Import transports
Please ask us for details if you want to manually customize literature sources for substance
lists and reference data.
5.2.2.6.2.1. How to add literature sources
Enter the sources and assign a specification category to each source. You can assign the
source key as required.
You can create new sources at any time, even in a productive system, from the EHS menu by
choosing Basic Data and Tools -> Tools -> Current Settings -> Specify Sources.
Or : Start IMG customizing with transaction "spro".
Navigate to Environment Health and Safety -> Basic Data and Tools ->Specification Management -> Additional Information for Value Assignment -> Specify Sources.

Enter the new source ID (limited to 10 characters) and additional information
Switch to the left navigation sidebar and double click on the "Specification Category" entry.
Pressing F5 or "New Entries" you can enter the Specification category like "SUBSTANCE".
5.2.2.7. Identifier Types
57
SAP AG

Substance lists and reference data makes use of some additional identifier types that are not
available in the SAP EHS standard. These additional identifier types need to be created in
SAP EHS customizing before substance lists and reference data can be used.
The required additional identifier types are included in the customizing transport Master Data
Customizing of each content package for substance lists and reference data. As an alternative, you can create the identifier types manually with the description below.
Upload files
How to upload files
Import transports
Please ask us for details if you want to manually customize identifier types for substance lists
and reference data.
5.2.2.7.2.1. How to add identifier types
Start transaction "spro" navigate to Environment, Health and Safety -> Basic Data and Tools
-> Specification Management -> Specification Master -> Check Identification Types.
Enter the Identification category (NAM, NUM FRM....) as work area.
With F5 or "New Entries" you can enter a new identification type and additional settings.
You may only enter values within the "Z"- namespace. Others are possible but are not recommended - if really necessary - ignore warnings and safe.
Go to the navigation sidebar and double click on the "Specification Category" entry and enter
a new entry e.g. "SUBSTANCE"
save your Setting.
58
SAP AG
59
SAP AG
5.2.2.8. Dangerous Goods Master Data

The SAP EHS Regulatory Content - substance lists and reference data for dangerous goods
requires some additional dangerous goods master data. These additional settings need to be
done in SAP EHS customizing before substance lists and reference data for dangerous goods
can be used. These additional settings include:
Mode of Transport
Dangerous Goods Regulations
Dangerous Goods Class and Dangerous Goods Letter (Tables THM009, THM010, THM011,
THM012)
Risk Potentials (Table THM071)
Hazard Identification Numbers (Table THM031
Danger Labels (Table THM017)
Packing Instruction Numbers (Table THM075)
The required additional DG customizing entries are included in the customizing transport DG
Master Data of the substance lists and reference data for dangerous goods Content Package.
As an alternative, you can make the settings manually using the description below.
Most of the customizing required for substance lists and reference data for dangerous goods
is included on two customizing transports available for Unicode and Non-Unicode systems.
Please be aware that these transports include DG master data customizing and should be
carefully checked and tested before used in a system with existing DG customizing.
Note
For international, European and North American regulations we provide additional
packing data. The customizing tables for these data are just available in system releases from ERP 6.0 on. If you use a system release before ERP 6.0 please implement the
customizing transports without packing data only.
Note
Two different options are provided for CFR and TDG: Either data can be provided with
a split by mode of transport (air, road, rail, ...) or combined into one data set. Please
choose the correct customizing transports to support your preferred data model.
60
SAP AG

5.2.2.8.1. Check Mode of Transport
Please check that the following modes of transport exist in your system. The entries highlighted
(MTrCat. 7, 8 and 9), most likely do not exist in a system with standard customizing. Only
create these entries if you want to use CFR/TDG data with a split by mode of transport. If
combined CFR/TDG data is used, no entries are required.
-> Environment, Health & Safety -> Dangerous Goods Management -> Basic Data and Master
Data -> Common Settings -> Specify Mode-of-Transport Category
MTrCat.
DescModeTransCateg.
Base MTC
Road
Rail
Inland waterway
Sea
Air cargo
Air passenger
Road passenger
Rail passenger
Inland waterway passenger 3
20
Pipeline
20
97
Road and Rail
98
Road, rail, inland waterway
99
All mode of transport cate- 7

gories
61
SAP AG

5.2.2.8.2. Check Dangerous Goods Regulations
Please check that the following dangerous goods regulations exist in your system. The entries
highlighted, most likely do not exist in a system with standard customizing.
-> Environment, Health & Safety -> Dangerous Goods Management -> Basic Data and Master
Data -> Common Settings -> Specify Dangerous Goods Regulations
Regulation
Validity Area
MTrCat.
ADG
AU
97
ADN
ADN
ADR
ADR
CFR_AIR_C
US
CFR_AIR_P
US
CFR_INWTR
US
CFR_RAIL_C
US
CFR_RAIL_P
US
CFR_ROAD
US
CN_DG
CN
IATA_C
REG_WORLD
IATA_P
REG_WORLD
IMDG
REG_WORLD
KR_DG
KR
MERCOSUR
MERCOSUR
MX_DG
MX
NZ_DG
NZ
97
RID
RID
TDG_INWT_C
CA
TDG_INWT_P
CA
TDG_RAIL_C
CA
TDG_RAIL_P
CA
TDG_ROAD_C
CA
TDG_ROAD_P
CA
UN_DG
REG_UN_DG
98
Only create the above highlighted entries if you want to use CFR/TDG data with a split by
mode of transport. If combined CFR/TDG data is used, replace these by combined entries as
shown below:
Regulation
Validity Area
MTrCat.
CFR
US
99
TDG
CA
99
62
SAP AG

Upload files
How to upload files
Import transports
Please contact us for details if you want to customize the DG master data settings manually.
Due to the huge number of customizing entries, these are not listed in this documentation.
5.2.2.8.4.1. How to add dangerous goods master data
SAP EHS offers wide customizing options regarding dangerous goods master data. Maintenance of these customizing settings is done in transaction SPRO at Environment, Health and
Safety - Dangerous Goods Management - Basic Data and Master Data. Here there are three
further sub-nodes, Common Settings, Basic Data, and Master Data, each consisting of multiple customizing items. In the following those customizing activities that may be relevant are
described in detail.
5.2.2.8.4.1.1. Dangerous Goods Classes and Classification Codes
Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Common Settings - Specify Dangerous Goods
Classes and Classification Codes:
Enter the DG regulation the class and letter are relevant for
Enter the DG class and give a description
Switch to the navigation side bar on the left side and double click "Classification Code"
Enter the classification code together with a description
Save your settings
5.2.2.8.4.1.2. Risk Potentials
Management - Basic Data and Master Data - Basic Data - Specify Risk Potential:
Enter the DG regulation and class the risk potential is relevant for
Enter the risk potential (and classification code if applicable)
Enter a description for the new risk potential
Save your settings
63
SAP AG

5.2.2.8.4.1.3. Hazard Identification Numbers
Management - Basic Data and Master Data - Common Settings - Specify Hazard Identification
Numbers:
Enter the DG regulation the new hazard identification number shall be relevant for
Enter the new hazard identification number together with a description
Save your settings
5.2.2.8.4.1.4. Danger Labels
Management - Basic Data and Master Data - Common Settings - Specify Danger Labels:
Enter the DG regulation (and class if applicable) the new danger label shall be relevant for
Enter the danger label together with a description
Save your settings
5.2.2.8.4.1.5. Packing Instruction Numbers
Management - Basic Data and Master Data - Common Settings - Specify Packing Instruction
Numbers: (these entries are just used in RiscClssification for creation of transport documents)
Enter the DG regulation the packing instruction number shall be relevant for
Enter the packing instruction number and a description
Save your settings
5.2.2.8.4.1.6. Categories of Instructions for Enclosure and Instructions for Enclosure
Management - Basic Data and Master Data - Common Settings - Specify Categories for Enclosure: (these entries of packing instructions are used in PackingRequirements)
Choose Categorie or enter a new one if necessary
Switch to the navigation side bar on the left side and double click "Specify Instructions for
Enclosure"
Enter Instruction for Enclosure and regulation the new instruction shall be relevant for
Save your settings
5.2.2.8.4.1.7. Packing Codes
Management - Basic Data and Master Data - Common Settings - Specify Packing Codes:
64
SAP AG

(these entries of packing codes are used in PackingRequirements, do not use Packing Codes
(old))
Enter Packing code with description and regulation the new code shall be relevant for
Save your settings
5.2.2.9. Validity Area

SAP EHS Regulatory Content makes use of some additional validity areas that are not available in the SAP EHS standard. These additional validity areas need to be created in SAP EHS
customizing before SAP EHS Regulatory Content data can be used.
The required validity areas are included in the customizing transport Validity Area Customizing of each content package for substance lists and reference data. As an alternative, you can
create the identifier types manually with the description below.
Note
Validity areas for SAP EHS Regulatory Content - substance lists and reference data
for dangerous goods are not included in a customizing transport. Please see the next
chapter for details on validity areas required for substance lists and reference data for
dangerous goods.
Note
Validity Area REG_EU is not part of our transports as REG_EU is a standard value
of SAP EHS. As the European Union has new member countries, please carefully
check that validity area REG_EU includes all of the following countries. If countries are
missing, please add them to REG_EU after consultation of the responsible persons.
See also chapter Section 5.2.2.9.3.1, How to add validity areas for details on how to
extend existing validity areas.
Code
Country
Code
Country
AT
Austria
IE
Ireland
BE
Belgium
IT
Italy
BG
Bulgaria
LT
Lithuania
CY
Cyprus
LU
Luxembourg
CZ
Czech Republic
LV
Latvia
DE
Germany
MT
Malta
DK
Denmark
NL
Netherlands
EE
Estonia
PL
Poland
ES
Spain
PT
Portugal
FI
Finland
RO
Romania
FR
France
SE
Sweden
GB
United Kingdom
SI
Slovenia
GR
Greece
SK
Slovakia
HU
Hungary
65
SAP AG

5.2.2.9.1. Validity Areas for SAP EHS Regulatory Content - substance lists and reference data for dangerous goods
SAP EHS Regulatory Content - substance lists and reference data for dangerous goods makes
use of the following validity areas, which are not included in the customizing transports. Please
see the chapter about manual customizing below on how to check / add these validity areas.
VAreaCat
Val. area
Descr. for validity area
REGION
AU
Australia
REGION
ADN
ADN states
REGION
ADR
ADR states
REGION
CA
Canada
REGION
CN
China
REGION
KR
Korea
REGION
MERCOSUR
MERCOSUR states
REGION
MX
Mexico
REGION
NZ
New Zealand
REGION
RID
RID states
REGION
US
USA
REGION
REG_UN_DG
Val. Area for UN model regulations
REGION
REG_WORLD
World

Upload files
How to upload files
Import transports
Please ask us for details if you want to manually customize validity areas for SAP EHS Regulatory Content data.
5.2.2.9.3.1. How to add validity areas
The validity area determines in which jurisdictions values assigned to specifications apply. You
specify validity areas depending on the validity area categories. You can use the validity area
categories to define plants, business areas or regions, for example, as validity areas. You can
assign individual jurisdictions or organizational units at a lower level to each validity area, for
example:
66
SAP AG

You can assign countries and regions from the country table as validity areas for validity areas
of the category REGION. You can assign other organizational units for validity areas of another
category.
The definition of validity areas is closely linked to the requirements for reports. The validity
areas for this IMG activity are also used in the R/3 component Dangerous Goods Management.
Caution
Be aware, that the validity area "REG_WOLRLD" is "empty" and
has the default behaviour to recognize all countries.
Once you have used a validity area in a productive system, it can
no longer be deleted.
Newly created validity areas are not evaluated correctly by the
Expert before restarting the Expert Server.
Go to the IMG customizing ("spro"):
Navigate to Environment, Health and Safety -> Basic Data and Tools -> Additional Information for Value Assignment -> Usage ->Specify Validity Areas.
Press F5 or "New Entry" and enter the Validity area category (e.g. REGION) and the new
area as well as the description. Mark the entry and switch to the navigation sidebar
67
SAP AG

Double clicking the "Assign Validity Area/Country" entry the list of countries belonging to
this area opens (- empty). There you can assign all countries that shall belong to this new
validity area.
5.2.2.10. Update Hit List Functionality

Through the extended substance search functionality, you will be able to search for list substances that have new and/or changed data available from the mapping database for SAP
EHS Regulatory Content - substance lists and reference data. The result will be given as a
hit list directly in SAP EHS.
Note
If either the package ZEHS_OCC, the function group ZEHS_C1H0_OCC or one of the
function modules already exist in your system, you cannot use the provided transport.
This functionality is only available for SAP EHS 3.2 and newer releases. Please skip this
step if you are installing SAP EHS Regulatory Content - substance lists and reference
data on older EHS releases.
This functionality is only available for listed substances (product safety), it is not available for UN listed substances (dangerous goods).
5.2.2.10.1. Import report
The extended functionality is included in a workbench transport included in the implementation package. Import the workbench request to all SAP clients where this new functionality is
needed.
The following objects are included:
Package
ZEHS_OCC
Function Group
ZEHS_C1H0_OCC
Function Modules
ZEHS_OCC_SUB_FIND_BY_FILE
ZEHS_OCC_SUB_FIND_BY_FILE_CMD
ZEHS_OCC_SUB_FIND_BY_FILE_PARA
68
SAP AG

Upload files
How to upload files
Import transports
5.2.2.10.2. Create Extended Search User Exit
A new user exit entry of type SUB_QUERY in SAP EHS is required to use the extended search
functionality.
5.2.2.10.2.1. How to create extended search user exit
A new entry for an extended search user exit can be added in SAP EHS customizing.
Activities
2. Create a new user exit of user exit type SUB_QUERY with the following values:
User Exit Type
SUB_QUERY
User Exit Name
SUB_FILE
Specific. categ.
SUBSTANCE
Function Module Name
User exit description
EN: List substance with new data...

DE: Listenstoff mit neuen Daten ...
C1H0_SUB_FIND_BY_VALU
3. Parameters and Values are not required for a search user exit and you can leave them
empty.
5.2.3. Phrases
SAP EHS Regulatory Content makes use of a multilingual phrase library. The required phrases
are provided as SAP EHS phrase import files for different operating systems.
All phrases are available in English language and in all other languages that a regulatory list
was published, e.g. phrases for the German WGK list will be available in English and German
only.
Each SAP EHS Regulatory Content package includes all necessary phrase import files. The
basic steps for a phrase import are:
Upload phrase files
Import all required languages into the passive library TDCLE
Merge all phrases into the active library
69
SAP AG

Import phrase set assignments
Detailed information for all steps will be provided in the following chapters.
Note
Please note that SAP EHS Regulatory Content data is always based on the latest EHS
property tree. If the property tree is not updated, importing phrase set assignments will
cause error messages.
SAP EHS Regulatory Content - substance lists and reference data for dangerous goods
basic data package does not require a phrase import.
Please see which files are included in your package.
5.2.3.1. Upload files

This chapter describes how to upload phrase import files and which files are included in your
SAP EHS Regulatory Content package.
5.2.3.1.1. How to upload files
application server.
For example :
screen shot below.
70
SAP AG

5.2.3.2. Import phrases

The following chapters describe in detail how to import phrases into a passive catalogue, merge
them into an active catalogue and assign them to phrase sets.
5.2.3.2.1. How to import phrases
Check the file (F5)
Save
Note
Caution
passive library!
71
SAP AG
5.2.3.2.2. How to merge phrases

with :
72
SAP AG
and select merge.

73
SAP AG
Note
Note
5.2.3.2.3. How to import phrase set assignments
into SAP EHS.
Check the file (F5)
74
SAP AG
75
SAP AG

contact us.
5.2.4. XML substance database

The XML substance database is a collection of XML files which contain the data in a format
that the SAP EHS Open Content Connector (OCC) is able to read and import into SAP EHS.
Each substance or UN number has its own specific XML file.
5.2.4.1. Install XML substance database

This chapter describes how to install the XML substance database locally or on a network
drive. Please see which files are provided for installation.
5.2.4.1.1. How to setup/update XML substance database for substance lists and reference data
Note
This step is not required if substance lists and reference data is loaded from the SAP
EHS Regulatory Content webserver, only if a local copy of the database is used.
No database server is needed, any file server with a fast connection and sufficient
storage space is suitable.
Your data implementation or update package contains a setup file e.g. cleo_2009-2_region.exe
which includes all required database XML files. Please execute this file and choose the correct
path to your SAP EHS Regulatory Content - substance lists and reference data (Product Safety
or Dangerous Goods) database installation. The path must match the entry of the secondary
data determination User Exit for data load, see chapter How to configure the User Exit.
Note
If you are updating an existing database, the setup program will suggest a path for
the installation based on the storage path of the last installation from this computer.
Please carefully check this installation path to avoid mixing up e.g. productive and test
databases.
In your XML substance database folder, a text file called version.txt is stored which
will have information about the currently installed database. Please check the version
file before updating the database to avoid overwriting your database with the same or
older files.
Each installation of the substance lists and reference data XML substance database takes
approximately 1,5 GB for Product Safety and 1,1 GB for Dangerous Goods database.
After installation of the XML files, the structure of the database should look like:
Product Safety:
<path to XML substance database>\CLEO\
main folder with index file and version info

(header.xml and version.txt)
<path to XML substance database>\CLEO\1 subfolder with all CAS numbers starting with 1
76
SAP AG

<path to XML substance database>\CLEO\... subfolders for other CAS numbers starting
with 2 to 9
<path to XML substance database>\CLEO\G subfolder with all substance groups
<path to XML substance database>\CLEO\N subfolder with all non-substances data, e.g.
mixtures and data with no CAS number
Dangerous Goods and Dangerous Goods with Packaging Data:

(head.xml and version.txt)
<path to XML substance database>\CLEO subfolder with all data for DG regulation
\ADN
ADN(R)
<path to XML substance database>\CLEO\... subfolders for other DG regulations
<path to XML substance database>\CLEO subfolder with all available UN numbers
\UN
Alternatively extract the files and burn a DVD if no network folder should be used (performance
loss!). The network path for database must be accessible for all users (read access). For
security reasons, access should be limited to persons allowed to load SAP EHS Regulatory
Content - substance lists and reference data. Please note the path to the database in the
installation protocol.
It is possible to have separate databases for Test, Development and Productive systems. This
allows testing of data updates without impact on the productive data load. If you want to do this,
copy the whole database including all subfolders to a different storage location. In addition,
changes to the mapping database and user exit are required to support multiple databases
(see also chapters How to configure the User Exit, How to configure EHS OCC and How to
setup Mapping Database).
Note
Please make sure that you have a fast network connection between your OCC frontend computer, SAP application server and the storage location of the XML substance
database. WAN connections are usually unsuitable for OCC as large amounts of data
have to be transferred. See also SAP note 1235663 for further hints to improve the
OCC performance.
5.2.5. Mapping Database

OCC makes use of a mapping database that allows to match values in the XML substance
database to values used in SAP EHS. This includes information like properties, phrases, regulatory lists and literature sources.
Substance lists and reference data is provided with a standard mapping database, which
makes use of the latest EHS standard property tree, Substance lists and reference data related
phrases and multilanguage phrase libraries for hazard communication. Use of other properties
or phrase libraries is possible, but not explained in this document. Please contact us for details.
5.2.5.1. Setup Mapping Database

Each installation of SAP EHS Regulatory Content - substance lists and reference data requires
its own mapping database. The following chapter describes in detail how to install the mapping
77
SAP AG

database. OCC mapping databases are Microsoft Access databases. If changes to the mapping database are required, the PC must have Microsoft Access 2000 or higher installed. For
a standard user only loading substance lists and reference data MS Access is not required as
all necessary data base drivers have been installed with OCC.
Please see which files are provided for installation.
5.2.5.1.1. How to setup/update mapping database for SAP EHS Regulatory Content substance lists and reference data
The mapping database file is included in folder 5-Mapping-Database of your SAP EHS Regulatory Content -substance lists and reference data package. The mapping file is named
td_cleo.mdb for product safety and td_cleo_dg.mdb for dangerous goods.
Initial setup of mapping database
This mapping database can either be installed locally for each user or used as a central network-database for all users.
Advantages of a local database:
Fast access during data load
Cache during the first data load is created much faster
No access conflicts if several person are loading data at the same time
Disadvantages of a local database:
During updates, each database needs to be changed/replaced.
Users can have different mapping for phrases, properties and other values, potentially creating inconsistencies in SAP EHS.
Advantages of a central database:
Only one database needs to be maintained/updated
All users have the same mapping settings
Disadvantages of a central database:
If network access is slow or bandwidth is limited, response time during data load might be
longer. Especially creating the cache will be much slower.
In rare cases conflicts in opening the database if several persons are loading substance lists
and reference data at the same time
Note
Please make sure that you have a fast network connection between your OCC frontend computer and the storage location of the mapping database. WAN connections
are usually unsuitable for OCC as large amounts of data have to be transferred. As the
mapping database is used to store cached data for improved performance, this file can
get quite big (over 100 MB). See also SAP note 1235663 for further hints to improve
the OCC performance.
If you are copying the mapping database from a CD/DVD to your local drive/network,
please remove the write protection of the file td_cleo.mdb after copying to your local
drive.
78
SAP AG

If the active phrase library is different than CUST, changes to the mapping database are required:
1. Open td_cleo.mdb / td_cleo_dg.mdb in MS Access
2. Open table ExpPhraseMap
3. Choose column External_id and replace CUST:
Search for: CUSTReplace with:????- (name of active phrase library)
Search in: External_id
Compare: Beginning of field
Replace all
Note
If several installations were done for the database (test/dev/prod), we recommend a
separate mapping database for each of the installations.
The OCC mapping database follows the same structure as SAP EHS Expert mapping databases. There are separate mapping tables for properties, phrases and other values:
Updating the mapping database
We recommend replacing the mapping database with the new version included in your update package as additional phrases and regulatory lists are added in the phrase mapping
table. If you have already made your own changes to the mapping database, e.g. renamed
identifiers or phrase mapping changes, please contact us and we will support you in updating
your database. If your active phrase library is different than CUST, changes to the mapping
database as specified above are required.
You can find the path of your mapping database in the ExpertAdmin tool installed on your front
end computer. On the instances tab there should be entries for e.g. CLEO_PS or CLEO_DG
which specify the path to the current mapping database. Please see Section 5.2.7.1.1, How
to configure EHS OCC for details.
Repeat the above steps for all installations of the SAP EHS Regulatory content - substance
lists and reference data mapping database if you are using more than one mapping database
or if each user has a local copy of the mapping database.
Note
We recommend to create a backup copy of your existing mapping database before
overwriting it with the new version of the mapping database.
Tables of the mapping database
ExpRecordMap: Property Mapping

ExpFactMap: Characteristics, Identifiers, Free Text, ... and display order
ExpPhraseMap: Phrases and other values
ExpGroupMap: Not used for OCC
79
SAP AG

ExpSubstanceMap: Individual filter settings for each substance based on the last load for
this substance
History: Version information and change log
CacheHeaderInfo: Cached information about the index file. Only available after the first data
load.
CacheHeaderAvailableSubstances: Cached data about all available substances in the
database. Only available after the first data load.
CacheHeaderGroup: Cached data about all group assignments in the database. Only available after the first data load.
In all tables, Internal_id means the key/value in the database and External_id the corresponding key/value in SAP EHS.
5.2.6. Analysis Tool for Excel

OCC has a functionality to simulate a data load and compare existing data in SAP EHS with
updated data in the XML substance database, without loading the new data into SAP EHS. As
OCC only generates a text file with the result, analyzing the changed data is not easily possible.
SAP EHS Regulatory Content includes a tool for Microsoft excel, which uses the simulation
file generated by OCC as input and allows an enhanced analysis of changed data.
The following chapter describes the installation of the tool. Use of the tool is explained in the
update guide for SAP EHS Regulatory Content - substance lists and reference data.
Note
This tool is currently only available for product safety data. You can skip this step if you
are only using dangerous goods.
5.2.6.1. Install Analysis Tool for Excel

If you are using the OCC simulation to help analyze the impact of regulatory updates, we
recommend installing the enhanced simulation tool for Excel on all front-end computers with
SAP EHS OCC. The tool is available as a Microsoft Excel template for Excel 97 or higher.
We recommend using the Excel 2007 version as not all functionalities are supported in other
versions of the tool.
Please see which files are provided for installation.
5.2.6.1.1. How to install the Update Analysis Tool for Excel
The Simulation Tool for SAP EHS Regulatory Content - substance lists and reference data
is included in folder 6-UpdateTools and can be installed on front-end computers with a few
simple steps:
Copy either cleo_simulation.xlt (MS Excel 97 - 2003) or cleo_simulation.xltm (MS Excel 2007) to your Excel template folder, usually ...\Documents\<user>\Application Data\Microsoft\Templates
As an alternative, open cleo_simulation.xlt in Microsoft Excel 97-2003 and choose "Save
as...". Use the option for Excel templates *.xlt and the correct path to the template fold-
80
SAP AG

er should be preset. Save as xlt-file to this folder. For MS Excel 2007, open choose
cleo_simulation.xltm and save as "Excel Template with macros" *.xltm
Note
You need to activate the macros in cleo_simulation.xlt / cleo_simulation.xltm or you
will not have access to any of the functionalities of the tool. If you have installed previous versions of the Simulation Tool for Excel you may want to make a copy before
overwriting with the new version. If you do not want to activate macros, we recommend
using the previous version of the tool which was not making use of any macros but
has limited functionality.
Note
In MS Excel 2007, you need to save this Excel file in a trusted directory or you cannot
activate the macros.
5.2.7. Adjustments
After the initial installation of SAP EHS Regulatory Content - substance lists and reference
data, manual changes are required to adapt OCC and the database to specific settings and
requirements. The following chapters have information on
Configuring SAP EHS OCC
Configuring the secondary data determination user exit
Adjust the mapping database
5.2.7.1. Configure EHS OCC

Changes to the settings of OCC are necessary on each front-end computer with an OCC
installation. The changes described below add the settings required to make a connection
between SAP EHS, the front-end computer and the mapping database.
5.2.7.1.1. How to configure EHS OCC
The following settings in OCC must be created to support the data load of SAP EHS Regulatory
Content - substance lists and reference data.
Note
Please note that everything described in this chapter is only valid for SAP EHS Open
Content Connector (OCC) Service Pack 21 (November 2009) or higher. Please update
OCC to this version or contact us for the settings in older OCC versions.
Note
If multiple installations of the database exist for test, development and productive systems, the below steps must be repeated for all of them. Assign the name of the instances as specified in the user exit parameter EXPERT_RULE_SET and assign the
appropriate mapping database.
Product Safety
A new instance entry has to be configured for Product Safety data:
81
SAP AG
Execute OCC: ->Start -> Programs -> EHS -> Open Content Connector
Choose: Options -> Instance Configuration ...
Choose Add
Name: CLEO_PS
System: EHSOCC
Mapping: Path to your mapping database TD_CLEO.mdb which was part of the installation
in step "How to setup Mapping Database"
Dangerous Goods / Packaging Data

A new system entry has to be configured for Dangerous Goods/Packaging Data:
Choose: Options -> Preferences ...
Switch to the Systems tab
Choose Add
Name: EHSOCCDG
Options: All settings should have been automatically copied when the EHSOCCDG key was
created. No changes necessary.
Choose Apply
82
SAP AG
A new instance entry has to be configured for Dangerous Goods/Packaging Data:

Choose Add
Name: CLEO_DG
System: EHSOCCDG
Mapping: Path to your mapping database TD_CLEO_DG.mdb which was part of the installation in step "How to setup Mapping Database"
83
SAP AG
5.2.7.2. Configure User Exit

Changes to the secondary data determination user exit are necessary to configure the connection between SAP EHS, the front-end computer and the XML database.
5.2.7.2.1. How to configure the User Exit for SAP EHS Regulatory Content - substance
lists and reference data
The user exit for secondary data determination substance lists and reference data needs to
be adapted to the installation path of the XML substance database for Product Safety or the
XML substance database for Dangerous Goods. EXPERT_ADD_PARAM_1 of the User Exit
has to be changed to reflect the path of the database index file of either the productive or the
test database.
Environment, Health & Safety -> Product Safety -> Basic Settings -> Manage User Exits
User Exit Category
SUB_SEDACA
User Exit Name
CLEO_PS or CLEO_DG
EXPERT_ADD_PARAM_1
headerurl=<path
to
database>\header.xml
84
XML
substance
SAP AG
If multiple installations of the database exist for test, development and productive systems,
copy the UserExit for each separate installation of the database. Change the following two
parameters:
EXPERT_ADD_PARAM_1
PS: headerurl=<path to XML substance

DG: headerurl=<path to XML substance
database>\head.xml
EXPERT_RULE_SET
Instance name given to the database in

step How to configure EHS OCC, usually
CLEO_PS or CLEO_DG
85
SAP AG
Example 5.1. Example:

An additional database for the test system was created at F:\CLEO-TEST:
Additional registry-key needed for instance CLEO-TEST
Path to mapping database for new instance in registry changed to F:\CLEO-TEST
\td_cleo.mdb
Existing User Exit, e.g. CLEO_PS copied to new key, e.g. CLEO_TEST
In new User Exit, change EXPERT_ADD_PARAM_1 to: headerurl= F:\CLEO-TEST
\header.xml
In new User Exit, change EXPERT_RULE_SET to: CLEO-TEST
5.2.7.3. Adjust Mapping

After the implementation of SAP EHS Regulatory Content - substance lists and reference data,
mapping can be changed according to customer needs. The following items can be changed
in the mapping database:
Mapping of data to different properties or characteristics

Mapping of identifiers to different names
Using different phrases or regulatory list names
Assigning different validity areas (only on property level, not on list level)
As SAP rule sets and WWI templates are designed to work with our standard mapping, any
changes in mapping may cause changes to SDS template and rule sets. If mapping changes
are required, please contact the Content as a Service team for detailed info and support.
The following chapters describe the mapping database tables and their fields.
Note
Substance lists and reference data for dangerous goods requires mapping changes
depending on the data model you have chosen for North-American DG regulations
(CFR, TDG). Please see the next chapter for details.
5.2.7.3.1. Dangerous Goods - Configure Mapping for Split/No-Split
No changes are required if you are using CFR and TDG without the split into modes of transport. You can use the TD_CLEO_DG.mdb as provided. If a split into modes of transport for
CFR and TDG is required, please change the following settings:
Open TD_CLEO_DG.mdb
Open table ExpFactMap
In the column IsPhrase remove all checkmarks (5 in total)
Note
If you use a system with release before ERP 6.0 it contains no structures for additional packing data. In this case please use a mapping database named without
pack only.
5.2.7.3.2. How to adjust the Fact Mapping
86
SAP AG

The fact mapping table contains the settings for mapping facts in the set of rules or OCC data
to characteristics or other elements in the EHS data model.
Table Fields in the Fact Mapping Table (ExpFactMap)
Table Field
Meaning
Internal_Id
Name of the fact in the set of rules / OCC XML file
Record
Optional assignment of the fact to a record in the set of rules / OCC XML file
Group
Optional assignment of the fact to a composition in the set of rules
External_Id
Name of the assigned data element in EHS
Descriptions
Description text for the fact
Options
Options that govern access to the data in EHS more closely
IsPhrase
Identifies whether the fact contains values that are to be subject to value
conversion via phrase mapping tables. This will mostly be used for facts
that represent characteristics with phrases assigned in order to convert
an easily recognizable phrase identification used in the set of rules / OCC
XML file to the phrase key in EHS and vice versa.
The first three fields together form a unique identifier for the fact in the set of rules.
5.2.7.3.3. How to adjust the Record Mapping
The record mapping table contains the settings for mapping records in the set of rules or OCC
to value assignment types in EHS.
Table Fields in the Record Mapping Table (ExpRecordMap)
Table Field
Meaning
Internal_Id
Name of the record in the set of rules / OCC XML file
Group
Optional assignment of the record to a composition in the set of rules
External_Id
Name of the assigned value assignment type in EHS
Descriptions
Description text for the record
Options
The first two fields together identify the record uniquely in the set of rules.
5.2.7.3.4. How to adjust the Phrase Mapping
The phrase mapping table contains the regulations for mapping phrase codes used in the set
of rules or OCC XML files to phrase keys in EHS.
Note
Phrase mapping allows an assignment to be made between an internal and an external
value for any fact value. The phrase does not have to be an EHS phrase. The corresponding conversion takes place if the IsPhrase indicator is set in fact mapping.
Expert generates a warning message if the rule set or OCC reads phrases which are
not contained in the Mapping table.
Table Fields in the Phrase Mapping Table (ExpPhraseMap)
87
SAP AG

Table Field
Meaning
Internal_Id
Phrase code in the set of rules. The rule editor uses a special syntax for
phrase codes to distinguish them from normal texts. For this purpose the
phrase codes are enclosed in square brackets and number signs, for example [#R20#] .
External_Id
Phrase key in EHS
Phrasetext
Phrase text
Options
In some cases it might be necessary to enhance/adapt the phrase mapping manually.

Customer specific phrases
The phrase mapping table has to be enhanced if a customer uses additional customer specific
phrases.
To suppress the warning message these phrases have to be added manually to the phrase
mapping table.
Tip
We recommend to insert these phrases using the following pattern:
Internal_Id: <Catalog name>-<Phrase key> , e.g. CUST-N09.00101280
External_Id: <Catalog name>-<Phrase key> , e.g. CUST-N09.00101280
To consider these enhancements for updates of the standard mapping you should label
these manual settings in the database e.g. in the Version column.
Customer specific phrase catalogue
The first part of the phrase key (column: External_Id) always signifies the active phrase catalogue in EHS.
The default phrase mapping is based on the CED Phrase Catalogue.
The default value for the active phrase catalogue is CUST.
If the active phrase catalogue in the EHS system is named differently then the mapping has
to be changed (using the replace function in MS Access).
5.2.8. Cache
OCC makes use of a caching functionally to improve the performance of the data load. After
the initial implementation and after each change of the XML database, the cache needs to
be created. The cache will be created automatically by OCC whenever the XML substance
database is changed:
Start OCC for Product Safety for any list substance after you have installed your XML substance database. The first load after the installation will analyze the database and will store
this information locally in your mapping database (cache).
This process may take from less than a minute to several minutes, depending on your network
speed to the XML substance database and your front-end computer (memory). Only the first
88
SAP AG

load will take this long, after the cache has been rebuild, load times should be down to only
a few seconds again.
We recommend that the first load is done by somebody with a fast connection to the XML
substance database, e.g. a user working at the same site as the XML substance database
installation.
Note
Do not cancel OCC if it looks like the program has locked up. This process may require
several minutes and in rare cases up to an hour.
Ensure that you have a fast network connection to the OCC mapping database and
the XML substance database. A WAN connection is insufficient for accessing a large
MDB file with the cache.
Make sure that caching of header data is activated, as described in Note 965586 (activated automatically as of Support Package 14).
5.2.9. Review New Filter Settings

At the first start of OCC, you will get a pop-up window informing you about new regulatory lists
added. In the next step you will see the OCC filter settings.
During the initial load, you need to review the filter settings in OCC and adapt them to your
business processes. For each regulatory list, a decision should be made if this list is required
by your business process or not. After reviewing the filter settings, you can define these as the
new standard by clicking the "Default" button in OCC.
The content reports for SAP EHS Regulatory Content - substance lists and reference data
will help you make this decision in case that you are not familiar with some of the content.
Content reports include a short description of the regulatory background and purpose of each
list, information about the SAP EHS property used to load this data and an example data set.
Note
As a general rule, load only lists that are used in your business processes. Data that
is loaded but not used will still create additional work in the update process when you
have to review updated data.
5.2.9.1. Adapt Dangerous Goods Filter Settings

During the initial load, you need to review the filter settings in OCC loading tool. For each
dangerous goods regulation, a decision should be made if this list is required by your business
process or not.
Split by mode of transport for CFR / TDG:
No changes to filter settings are required.
No Split by mode of transport for CFR / TDG:
Deselect the following regulations - both under identifiers and regulations - if you want to load
Dangerous Goods data without split by mode of transport:
89
SAP AG
CFR_AIR_C
CFR_AIR_P
CFR_INWTR
CFR_RAIL_C
CFR_RAIL_P
TDG_INWT_C
TDG_INWT_P
TDG_RAIL_C
TDG_RAIL_P
TDG_ROAD_P
After reviewing the filter settings, you can define these as the new standard by clicking the
"Default" button.

The following steps describe how to check the implementation of SAP EHS Regulatory Content.
5.3.1. Check List Product Safety

Please use the following check list as guidance through the substance lists and reference data
implementation and as check list after the implementation.
Status
Where to do
What to do
General
O
Technical Part
O
Frontend
Install Open Content Connector
SAP EHS (sm59)
Setup & check RFC connection
SAP EHS (cg3z)
Upload customizing transports

Upload phrases
SAP EHS (stms)
Import customizing transports
SAP EHS ()
Install hit list functionality
SAP EHS (cg31)
Import substance lists and reference data phrase library
SAP EHS (cg12)
Merge phrases to active catalogue
SAP EHS (cg31)
Import phrase sets
td_cleo.mdb
Install XML substance database

Setup mapping database
(optional) adjust mapping
customizing (spro)
Manual changes to OCC and user exit

(optional) Install spreadsheet template for data analysis
Regulatory Part / Data Load

O
Review regulatory lists in release notes and content reports
90
SAP AG

O
Create cache
Review new filter settings
5.3.2. Check List Dangerous Goods Packaging Data

Please use the following check list as guidance through the substance lists and reference data
for dangerous goods data implementation and as check list after the implementation.
Status
Where to do
What to do
General
O
Technical Part
O
Frontend
Install Open Content Connector
SAP EHS (sm59)
Setup & check RFC connection
SAP EHS (cg3z)
Upload customizing transports

Upload phrases
SAP EHS (stms)
Import customizing transports (BC Set)
SAP EHS (cg31)
Import Import substance lists and reference data phrase

library for dangerous goods
SAP EHS (cg12)
Merge phrases to active catalogue
SAP EHS (cg31)
Import phrase sets
TD_CLEO_DG.mdb
Install XML substance database

Setup mapping database
(optional) adjust mapping
customizing (spro)
Manual changes to OCC and user exit

O
Review regulatory lists in changes database
Create cache
Review new filter settings
91
SAP AG

Content - expert rules for substance
and mixture classification
SAP provides Expert Rule Sets for the determination of secondary data according to regulations in different jurisdictions, with a focus on the European Union, the Americas and Asia/
Pacific regions. The rule sets require the installation of EHS Expert on a separate server, connected to an EHS system. Delivery is in the form of compiled ruc files and mapping databases
which have to be implemented on the EHS Expert Server.

This section describes the prerequisites for the implementation of Expert Rules, gives an
overview of the delivery process and details which components are delivered upon licensing
of Expert Rules.
This chapter describes the prerequisites for using EHS Expert rule sets for secondary data
determination.
All Expert Rules require additional customizing activities such as the creation of separate user-exits and data origins for each rule set.
In addition some Expert Rules require further customizing activities, e.g. additional value assignment ratings or user-defined free text categories.
These customizing entries are described for each rule set in the appendices.
It is recommended to perform the customizing activities before setting up the Expert Rules on
the Expert Server.
6.1.2. Content of Expert Rule set packages

Each Expert Rule set package consists of the following parts:
Documentation: functional descriptions which describe the general functionalities of the rule
set and release notes which describe the changes compared to the previous versions.
Expert rule set files and content database(s)
For a complete overview of all files included in this delivery of Expert Rules, please see the
list of Expert rule files.
6.2. Implementation
The following chapters describe how to implement Expert Rules.
6.2.1. EHS Expert

EHS Expert has to be installed on a separate PC and has to be configured in EHS. We recommend setting up separate Expert Server PCs for the test and productive systems. This enables
92
SAP AG
SAP EHS Regulatory Content - expert rules

for substance and mixture classification
you to test new versions of rule sets on the test EHS Expert Server independently from your
productive system. The following chapters describe the required installation steps.
6.2.1.1. Install EHS Expert

6.2.1.1.1. What is EHS Expert
EHS Expert is an independent Windows PC program. This program communicates via RFC
with the EHS database using a standardized BAPI interface.
EHS Expert is called from within EHS. The call is passed on to the Expert server which runs
on a PC. This server reads the EHS specification data via a BAPI interface.
Input facts , which are defined within the rule set and denoted with (IN), are filled with specification data via the BAPI interface. Rules define the calculations to be made using these facts
and thus new data for other facts is derived. After all the rules have been processed the output
facts, which are denoted with (OUT), are outputted to the specification database via the BAPI
interface.
The definitions for the facts and rules used by EHS Expert are stored in a rule file. The rule file
is a text file that is automatically created when rules are defined using the rule editor. However
they can be created and edited using any text editor.
The assignment of facts and other parts of the rule set (i.e. records, compositions, internal
phrases) to the specification database elements (e.g. characteristics, value assignment types,
phrase keys etc.) is made via the mapping tables.
6.2.1.1.2. Where to get EHS Expert
The installation program for EHS Expert is available on the current SAP Server Components
CD.
The current EHS Expert Version and respective patches are available on the SAP Support
Portal on the SAP Service Marketplace. You can find the patches for EHS Expert on the SAP
Service Marketplace under 'Support Packages & Patches' (http://service.sap.com/patches).
Detailed information on how to obtain the latest version of EHS Expert can be found in SAP
Note 568302.
6.2.1.1.3. How to install Expert
Section A.38, How to install EHS Expert
6.2.1.2. Setup RFC connection

6.2.1.2.1. Why do you need a RFC connection
The EHS Administration Server and EHS Expert are independent Windows PC programs.
These programs communicate via RFC with the EHS database using a standardized BAPI
interface.
6.2.1.2.2. How to setup a RFC connection
93
SAP AG

2.
3.
4.
5.
RFC destination: We recommend you structure the name as follows:

Connection type: T
On the Technical Settings tab page in the Activation Type screen area, set the flag to Registered Server Program.
In the Registered Server Program screen area, enter the PROGID entry from your installation (see How to install EHS Expert or entry in the file SAPRFC.ini) in the program ID field.
Save your entries

94
SAP AG

settings easily.
Connection type: T
service.
95
SAP AG

Connection type: T
96
SAP AG

6.2.1.2.3. How to test the RFC connection

97
SAP AG

6.2.1.3. Configure EHS Expert

You can configure EHS Expert servers as Microsoft Windows services or as console programs.
The advantage that the windows service has over the console program is that it does not
require that a user be logged on in order to execute the service. Thus a service can be started
automatically as a background process when the system is started up. It is recommend that
the EHS Expert Microsoft Windows service be used and that it be configured using the EHS
Service Administration.
6.2.1.3.1. using Service Administration
Within the EHS service administration, the EHS management server has the following functions:
Installation and deinstallation of services
Control of services (starting, stopping, restarting)
Display and change of service configurations (SAPRFC.INI, EHS Expert parameters and
EHS Expert rule sets)
File transfer (File transfer server PC <--> front-end PC (only access to directories used by
EHS Expert and WWI)
You will find a detailed description of the EHS service administration in the SAP help (EHS -> Basic Data and Tools --> Tools --> EHS Service Administration)
6.2.1.3.1.1. How to configure EHS Expert Server using EHS Service Administration
To call EHS service administration choose in the SAP menu --> Logistics--> Environment,
Health and Safety --> Basic Data and Tools --> Tools WWI and EHS Expert Server Administration or use transaction cgsadm.
98
SAP AG

The system searches dynamically for all EHS management servers that are logged on to the
system and displays the PC names as the search results in the navigation tree.
Double-click a PC name. The EHS management server is called and a list of all WWI and
EHS Expert servers installed in the system is displayed.
Choose in the menu Service --> Create --> EHS Expert Server
Choose a destination by using F4-help and enter a name a description for the EHS Expert
(in the example: EHS_EXPERT)
The system enters the following data:
The values for the selected destination in the RFC Parameters group box (Program ID,
Gateway host and Service)
A generated service key (<destination/system/sequential number) and an editable service
name with description in the General group box
99
SAP AG

The SAPRFC.ini file will be updated automatically on the Expert Server PC using the Program ID "EHS_EXPERT_TEST" as PROGID and the Service "EHS_EXPERT_TDG_01"
as DEST .
Accept your entries.
The Expert Server will then immediately be started on the PC.
6.2.1.3.1.2. How to configure Expert service administration
Section 6.2.1.3.1.1, How to configure EHS Expert Server using EHS Service Administration
6.2.1.3.2. Without using Service Administration
You can configure EHS Expert servers as Microsoft Windows services or as console programs.
The advantage that the windows service has over the console program is that it does not
require that a user be logged on in order to execute the service. Thus a service can be started
automatically as a background process when the system is started up.
The first step is the configuration of the file SAPRFC.ini. This step is the same regardless of
whether Expert is to be used as a Windows Service or as a console program. After this step
has been completed then EHS Expert can be configured (as either a Windows Service or as
a console program) and started.
6.2.1.3.2.1. How to configure SAPRFC.INI
1. From the EH&S Expert installation directory (e.g. C:\Program Files\EHS\Expert), open the
subdirectory BIN and open the SAPRFC.INI file.
2. Add the following lines to the SAPRFC.INI file:
Sample entry
Meaning
; Expert Server
Comment line
DEST=EHS_EXPERT_TDG_01
Name of destination (the parameter with

which you call the program EHSEXPER.EXE
or EHSEXPSV.EXE
100
SAP AG

PROGID=EHS_EXPERT_TEST
Name of program ID (as used as program id

in the RFC connection)
TYPE=R
R = Registration in R/3
GWHOST=pntd01
Router string + application server
GWSERV=sapgw00
Gateway service
RFC_TRACE=0
RFC trace initialization (0= no trace file, 1=

trace file). The trace file is normally not needed.
Note
You can use the SAPGUI entry to find the details for GWHOST and GWSERV:
GWHOST contains the SAP router string including the application server. GWSERV
contains the string sapgw and the system number
3. Save these entries.
6.2.1.3.2.2. How to configure EHS Expert Server as a Windows Service
Requirements
Your PC runs on the Windows NT or Windows 2000 operating system.
You have installed the EHS Expert server on your PC.
You have configured the EHS Expert server for a certain destination. (In the following, the
destination EHS_EXPERT_TDG_01 is used as an example).
Standard settings
The EHS Expert server as a Windows service consists of the file EHSEXPSV.EXE that is
automatically copied to the corresponding bin directory for Expert installation (for example, c:
\program files\EHS\Expert\bin). The bin directory should also contain the following three files:
The administration program SVCADMIN.EXE, which can be used to install, configure, and
check services
The program library WIN32SVC.DLL
The EHSSTART.EXE file to automatically start and monitor the WWI generation server or
EHS Expert server as a Windows service
Activities
1. Log on as local administrator to the PC
2. Start the MS-DOS prompt and change to the bin directory for EHS Expert installation
3. Install the service by calling the EHSEXPSV file together with command line parameters as
follows: EHSEXPSV.EXE -I -N<name> -D<destination>.
Example:
EHSEXPSV.EXE -I -NTest -DEHS_EXPERT_TDG_01 installs the Windows service EHS
Expert Server (Test). The destination EHS_EXPERT_TDG_01 is used.
4. Make the settings that are specific to the application for the EHS Expert server as a Windows
NT service.
During the installation, for each service, a key is created with the name
EhsExpertSvc(<name>) under the main key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
101
SAP AG

Start REGEDIT.EXE via Start\Run\regedit.exe
Choose the key EhsExpertSvc(<name>)\Parameter.
Change the parameters if required.
Destination: name of logical SAP R/3 destination
Idle Time: (default value = 1000 ms)
InitialServerCount: Number of EHS Expert server threads that are created directly after
the service is started. (Default value = 1)
MaximumServerCount: Maximum number of EHS Expert server threads. As soon as
the maximum is reached, a warning is logged. The service main thread then only functions as a database server. (Default value = 20)
LogDirOptions: (Default value = 1 /F /P /E /L=clean.log)
Syntax: n [/F] [/P] [/E /L=<filename>]
The number n deletes all files whose creation date or change date is more than n
days ago (with 1 <= n <= 365)
/F If the parameter is set, the reference point for deleting is the creation date. If the
parameter is not set, the reference point for deleting is the date of the last access
or last change.
/P If the parameter is set, subdirectory structures are retained and only files are deleted. If the parameter is not set, everything below the current directory is deleted.
/E Logs the names of all files and directories that cannot be deleted owing to restricted
access rights. /L=<filename> Name of log file if parameter /E is set.
Examples:
1 /F /P /E /L=clean.log deletes all files whose creation date is more than a day ago
and log messages are created in the CLEAN.LOG file in the EHS Expert directory.
1 /P deletes all files whose change date is more than a day ago.
5. Configure the application log for Windows NT or Windows 2000.
Start the Windows event viewer (EVENTVWR.EXE).
Change the setting for the application log via Log -> Log settings to the option Overwrite
Events as Needed to prevent an overflow in the event viewer.
6. Test the service.
Start and stop the EHS Expert Server (Test) service using the SVCADMIN.EXE program
from the bin directory of the Expert installation or the Services control in Windows.
Call the EHS Expert Server (Test) from the SAP System.
Use the event viewer to check whether the respective commands in the application log file
have been logged and whether the language-dependent texts for the events are displayed
in the detail view.
Check whether the service was started automatically on system startup by rebooting the
PC and calling the EHS Expert Server (Test) from the SAP System.
7. To remove an installed service, proceed as follows:
Log on to the PC with administrator rights.
Start the service administration program SVCADMIN.EXE from the bin directory for the
Expert installation.
If necessary, close the current service using the Control and configure services function.
Remove the service using the Uninstall services function.
102
SAP AG
6.2.1.3.2.3. How to configure EHS Expert Server as a console program

To start the EHS Expert as a console program, you call the program EHSEXPER.EXE with
the parameter -D <Name of destination>.
For example: EHSEXPER.EXE -DEHS_EXPERT_TDG_01
If you copied the icons to your desktop when you installed the EHS Expert, change the parameter -D accordingly to the entry in your file SAPRFC.INI.
Alternatively, you can call the program on your front end using the menu command Start > Programs -> EHS Expert. The default parameter -D is here set to EHS_EXPERT. Therefore you have to change the parameter if you have defined another destination in your file
SAPRFC.INI (EHS_EXPERT_TDG_01 in the example)
6.2.2. SAP EHS Customizing

6.2.2.1. User Exit
Each EHS Expert rule set has to be configured in a SAP system and on the Expert Server PC.
This chapter describes the configuration in a SAP system.
For each rule set a user exit has to be created in the SAP system. A user exit can be created
or changed via the customizing settings EHS -> Basic Data and Tools -> Basic Settings >
Manage User Exits. The type of user exits for EHS Expert rule sets is SUB_SEDACA.
Please find the proposed user exit settings for the Expert rule sets.
6.2.2.1.1. How to extend entry in secondary data determination
Activities
103
SAP AG

EXPERT_COMMIT_MODE
Note
Expert.
EXPERT_DESTINATION
EHS_EXPERT).
to the EHS Expert.
104
SAP AG

Examples
the USA.
EXPERT_RULE_SET
EXPERT_COMMIT_FLG
to inactive.
Expert.
105
SAP AG

Warning
determination.
EXPERT_WRITE_OWNER
digits.
106
SAP AG

Note
EX.
EXPERT_ADD_PARAM_1
EXPERT_ADD_PARAM_2
EXPERT_ADD_PARAM_3
EXPERT_TAB_FIELD_1
EXPERT_TAB_FIELD_2
EXPERT_TAB_FIELD_3
EXPERT_TAB_FIELD_4
107
SAP AG

Sample value
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
SAP_EHS_0101_002
EX
EXPERT_READ_RATING
PUBLIC
REG_WORLD
EXPERT_RULE_SET
ZEXP_GHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHS
REG_WORLD

Sample Value
EXPERT_ADD_PARAM_1
headerurl=<path
to
CLEO
PS
DB>\PS_DB
\header.xml
EXPERT_ADD_PARAM_2
usernameurl=x
EXPERT_ADD_PARAM_3
passwordurl=x
EXPERT_CALL_ONCE
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_OCC
108
SAP AG

EXPERT_READ_RATING
EXPERT_RULE_SET
CLEO_PS
EXPERT_TAB_FIELD_1
<subid>
EXPERT_TAB_FIELD_2
EXPERT_TAB_FIELD_3
EXPERT_TAB_FIELD_4
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
TECHNIDATA
REG_WORLD
6.2.2.2. Multi Rule Call

This CSM Solution Package delivers Expert Multi Rule Call functionality. This enables the user
to define a list of rule sets which EHS Expert executes in one step as an automatic sequence .
For example, it is possible to set up a Expert Multi Rule Call which runs all the rule sets required
to create the data for a Material Safety Data Sheet.
6.2.2.2.1. What is a Multi Rule Call
Standard EHS functionality allows the execution of only one rule set at a time. As such, if it
is necessary to apply more than one rule set to a specification, this can be done either by
several manual calls or by using the Expert Multi Rule Call. The Expert Multi Rule Call supports
background and dialog processing.
Example (using standard SAP rule sets):
After changing the product composition of a preparation the standard composition has to be
recalculated (run the Composition rule set).
This change of the standard composition may have an impact on all classification data of
the product, so it is necessary to recalculate the EU classification (run the rule set: DAPEC).
The hazardous ingredients for the EU MSDS have to be determined as well (run the rule
set HazardComp_EU).
Instead of starting three rule sets manually and one at a time, Expert Multi Rule Call would
trigger the execution of the required rule sets in a predefined order.
6.2.2.2.2. Where to get Multi Rule Call
The Expert Multi Rule Call functionality is available as a CSM Solution Package (CSM-PSEXPMRC).
For enquiries please contact your SAP Account Manager.
6.2.2.3. Data Origin

The data origins used within the EHS systems connect the user-exits with the Expert Administration instances.
109
SAP AG

Each rule set has its own data origin, which is used when data instances are written to the
EHS database. As such a user is able to tell when a data instance orginates from a rule set.
The user-exits and data origins should have a descriptive comment indicating, at a minimum,
the purpose, rule set name and version. These comments should be created and kept up to
date in all relevant interface languages if possible.
Please find the proposed settings for the data origin(s) .
6.2.2.3.1. How to add data origins

Save your settings
6.2.2.4. Literature Source

The Literature Source specifies the actual source from which the data are taken.
The following entries can be made for sources: Source description, Author, Source note,
Source category, Date of publication, Order number
Please find the proposed settings for the literature source.
6.2.2.4.1. How to add literature sources
110
SAP AG


6.2.2.5. User Defined Text Type

User-defined text types are rquired when using the EHS Expert explanation components.
Please find the proposed settings for the User Defined Text Type.
6.2.2.5.1. How to add user defined text types

Save your settings
6.2.2.6. Regulatory Lists

Regulatory lists are required for assigning identifiers. They can be used for specifying the regulatory list to which a particular identifier belongs, or the regulatory list from which an identifier
was taken. An identifier can belong to several regulatory lists.
There are special cases, where one specification can occur under several different identifiers
in the same regulatory list e.g. there are specifications that are entered several times in the
CAS library under different CAS numbers.
A standard EHS system contains several different commonly used regulatory lists.
Activities:
1. Check if you want to use the predefined regulatory lists already available in the EHS system.
111
SAP AG

2. Delete the entries you do not require and create new ones if appropriate.
3. Assign a specification category to each newly created regulatory list.
Entries for regulatory lists that have already been used for data maintenance in a productive
system may not be deleted.
Regulatory lists can be entered in the Product Safety screen under Tools -> Current settings.
Please find the proposed settings for the regulatory lists.
6.2.2.6.1. How to add regulatory lists

Save your settings
6.2.2.7. User-Defined Dangerous Goods Texts

Using user-defined dangerous goods texts, additional data can be transferred into the dangerous goods master via the dangerous goods master data filling process. This information may
consist of additional text items, relevant for other processes and not otherwise given in the
EHS specification database, e.g. "Do not store together with acids".
The Expert Rule DangGoods determines special provisions (e.g. SP640) which are written as
phrases into the EHS standard property "Dangerous Goods User-Defined Texts". This rule
112
SAP AG

also derives special notes for small packaging sizes, (e.g. "If package size is more than 30 l,
packaging group II.") which are also outputted to this property.
Please find the proposed settings for the user defined dangerous goods texts.
6.2.2.7.1. How to add user-defined DG texts
User-defined dangerous goods texts are regulation-dependant and may be assigned to specific dangerous goods user-defined text profiles. The dangerous goods user-defined free texts
themselves are phrases, whereas those phrases written by the standard expert rule DangGoods are CED standard phrases delivered with the CED phrase library. If further dangerous
goods user-defined texts are required, additional phrases need to be created.
To specify dangerous goods user-defined text profiles, use transaction SPRO, choose SAP
Reference IMG and navigate through the activities tree to Environment, Health and Safety Dangerous Goods Management - Basic Data and Master Data - Common Settings - Specify
Profiles for User-Defined Dangerous Goods Texts:
Press F5 or select "New Entries"
Enter the respective DG regulation, a unique number for the profile and a description for
the profile
Specify the value assignment type the profile shall be used with (standard is
SAP_EHS_1022_042 provided with the EHS standard property tree)
(optional)
Select
the
function
module
used
for
output
conditions
(DG50_PRICOND_USRDEFTXT is delivered with the standard)
Save your settings
6.2.2.8. Value Assignment Rating

This rating, along with the validity area, make up the value assignment usage.
It is recommend that you enter as few ratings as possible. This minimizes the report generation
variant maintenance activities, as it is required that a rating be assigned to these variants
otherwise data cannot be outputted in the reports.
The following ratings are available:
INTERNAL - only for internal use

PUBLIC - for the public
OFFICIAL - for authorities
CUSTOMER - for customers
Activities :
1. Analyze your organizational structure in order to define the authorizations required to access
specification data.
2. Analyze the external addresses for specification data.
3. Make the required settings.
During filling of the dangerous goods master records, the system evaluates the rating of the
respective value assignments using a specific scheme.
Please find the proposed settings for the value assignment rating.
113
SAP AG

6.2.2.8.1. How to add a value assignment rating
By assigning a rating to a value assignment, you specify who can access the data or on which
documents the data can be printed. Once a rating has been used in a productive system you
cannot delete it.
To add value assignment rating, go into the customizing using transaction SPRO and navigate
to Environment, Health and Safety -> Basic Data and Tools -> Additional Information for Value
Assignment -> Usage ->Specify Ratings.
Then press F5 or "New Entry" and enter the new ratings as well as the description and save
your entries.
6.2.3. SAP EHS Regulatory Content - expert rules for substance and mixture classification
Each EHS Expert rule set has to be configured in a SAP system and on the Expert Server PC.
This chapter describes configuration on the Expert Server PC. The rule set can be configured
directly on the PC or within the SAP system using the EHS Service Administration.
6.2.3.1. Install Expert Rule Sets

The Expert rule sets have to be loaded and registered on the Expert Server PC.
Please find the proposed settings for the instances on the Expert Admin Server.
6.2.3.1.1. How to load rule sets onto the Expert server
Each rule set consists at least of two files
the rule set itself = file with the extension .ruc
the mapping database = file with the extension .mdb
114
SAP AG

Some rule sets are delivered with an additional files containing the external tables (file with the
extension .mdb) or additional rules in files with extension .ruc
All the files need to be copied on the Expert Server PC.
You can copy the files by using EHS Service Administration or by connecting to the Expert
Server PC directly.
EHS Service Administration
In transaction cgsadm choose the Expert Server PC and transfer the files as described in the
following steps
1. Choose in the menu Utilities --> Transfer File to Server
2. Choose all files to be transferred
3. Choose the path on the Expert Server PC
NOTE:
The path can only be chosen by a click on the icon
Then choose the icon next to view the directory structure
You will get the following screen and you can choose the path Rules for the files to be
transferred.
4. Press save and the files will be copied to the Expert Server PC
Direct copy
Connect to the Expert Server PC and copy all files in the RULES subdirectory of the Expert
installation.
115
SAP AG

6.2.3.1.2. How to register rule sets
All Expert rule sets have to be registered on the Expert Server PC. You can do this in the SAP
system using EHS Service Administration or directly on the Expert Server PC with the help of
the Expert Admin Tool. Some rule sets uses additional settings, e.g. IgnoreWarnings. These
additional settings could not be set using EHS Service Administration.
using EHS Service Administration
In transaction cgsadm go to the Expert Server PC and select the Expert Server. The Expert
Server has to be started and can then be edited
1.
2.
3.
4.
Go in Edit mode (Menu Service Change <-> Display or correspondent icon

Choose the tab page Application Parameters
Click on icon new page (Append row)
Insert the name of the rule set (as given in descriptions of the rule set) and Set of Rules
File and the Mapping File.
For example for the rule set GHS:
Set of Rules Name = ZEXP_GHS, Set of Rules File = C:\Programme\EHSExpert\Rules

\GHS_V1-6.ruc, Mapping File = C:\Programme\EHSExpert\Rules\GHS_V1-6.mdb
5. Save your entries (Menu Service --> Save)
using Expert Admin Tool

Logon the Expert Server PC and Start the program Expert Admin (via Start --> Programs -->
EHS or by calling the program ExpertAdmin.exe in the bin directory of the Expert installation.
1. Add a new instance by pressing
2. Choose the name of the rule set
Name = ZEXP_GHS, Rule File = GHS_V1-6.ruc, Mapping Database = GHS_V1-6.mdb
3. Save you settings by Apply
116
SAP AG

6.2.3.2. Run Expert Rule Sets

6.2.3.2.1. How to execute rules
Section A.47, How to execute rules
6.2.3.2.2. How to display the explanation component
Section A.48, How to display the Explanation Component
6.2.3.2.3. How to generate log files
Section A.49, How to generate Log Files
6.2.3.3. Adjust Expert Rule Sets

6.2.3.3.1. How to adjust external table values
In addition to the files for the rule sets (ruc files and the mapping data base) some rule sets
provide a separate MS-Access data base
The purpose of it is to allow the user to modify the preconfigured data according to the needs
of the customers.
These external parameters are interpreted by the rule set as IN facts.
It is recommended to install this data base in the same directory on the Expert server as the
rule files.
117
SAP AG

If this external data base is installed somewhere else, the linkage between the rule set and the
external data base must be maintained by defining the file path in the mapping tables.
The
below
mentioned
mapping
information
refers
to
the
OSHA_Hazard_Determination_externvalues.mdb but the approach to adjust the mapping is
the same for all rule sets.
Example: Record-Mapping Installation of the external data base in the same directory as the
rule set.
Internal_id
External_id
ext_target_organ T:Target_Organ/OSHA_Hazard_Determination_externvalues.mdb
Example: Record-Mapping Full declaration of the path for the external data
Internal_id
External_id
ext_target_organ T:Target_Organ/C:\Program Files\EHS\Expert\Rules

\OSHA_Hazard_Determination_externvalues.mdb
Example: Fact-Mapping Installation of the external data base in the same directory as the
rule set.
Internal_id
External_id
i_switch_harmful T:harmful_check;Switches/
OSHA_Hazard_Determination_externvalues.mdb
Example: Fact-Mapping Full declaration of the path for the external data
Internal_id
External_id
i_switch_harmful T:harmful_check;Switches/C:\Program Files\EHS\Expert\Rules

A documentation of the adjustable parameters could be obtained from the respective functional
descriptions of the rule sets.
6.2.3.3.2. How to adjust the Fact Mapping
Table Field
Meaning
Internal_Id
Record
Group
External_Id
Descriptions
Options
118
SAP AG

Table Field
IsPhrase
Meaning
6.2.3.3.3. How to adjust the Record Mapping
Table Field
Meaning
Internal_Id
Group
External_Id
Descriptions
Options
6.2.3.3.4. How to adjust the Group Mapping
The composition mapping table contains the regulations for mapping compositions in the set
of rules to value assignment types of the category composition in EHS.
Table Fields in the Composition Mapping Table (ExpGroupMap)
Table Field
Meaning
Internal_Id
Name of the composition in the set of rules. This field uniquely identifies
the composition in the set of rules.
External_Id
Name of the assigned value assignment type of the category composition

in EHS
Descriptions
Description text for the composition
Options
6.2.3.3.5. How to adjust the Phrase Mapping

Note
119
SAP AG

Table Field
Meaning
Internal_Id
External_Id
Phrase key in EHS
Phrasetext
Phrase text
Options

phrases.
mapping table.
Tip
6.2.3.3.6. How to write the Last Run Date
The EHS Expert is able to write the current date when running an Expert rule, to allow looking
up when a rule was called for the last time on a given substance. For that purpose, the property
"EHS Expert Explanations" was extended by another characteristic "Last Run Date" allowing
to store a date.
To activate writing the last run date, the following user-exit parameters have to be set:
120
SAP AG

EXPERT_WRITE_RUN_DATE = X (invokes writing the date)
EXPERT_EXPLANATION_ESTCAT = SAP_EHS_0101_002 (property the explanation is
stored at)
EXPERT_EXPLANATION_RULE_PROP = SAP_EHS_0101_002_RULESET (characteristic within the property given above to save the user-exit name)
EXPERT_EXPLANATION_DATE_PROP = SAP_EHS_0101_002_RUN_DATE (characteristic where the date of the last run shall be stored)

The following steps describe how the implementation of Expert Rules can be checked .
6.3.1. Check List

The following table can be used as guide to the Expert Rules implementation steps and as a
check list after the implementation has been completed.
Status
Where to do it
What to do
General
O
Technical Part
O
Frontend
Install EHS Expert
SAP EHS (sm59)
Setup RFC connection
Expert Server or SAP EHS Configure EHS Expert Server

(cgsadm)
Customizing (spro)
Create user exit(s)

(optional) Create user exit(s) for Multi Rule Call
Create data origin
Create literature source
Create user defined text type
Create regulatory lists
Create user defined dangerous goods texts
Create value assignment rating
Expert Server or SAP EHS Upload rule set files

(cgsadm)
Create admin instance(s)
Mapping.mdbs
(optional) Adjust mapping.mdbs

O
121
SAP AG

Content - material safety data sheet
(MSDS) templates
The following rules and design features apply to all sections of the template, unless otherwise
noted.
The template uses a table structure to format the data displayed. It consists of three columns:
Column 1 contains a header/label text, describing the information to be displayed.
Column 2 holds a delimiter to separate columns 1 and 3, usually the colon sign :
Column 3 contains the actual substance data.
If the key data fields of column 3 do not contain any data, the whole table line is not displayed.
This chapter describes the prerequisites which are necessary to use Report Templates.
The material safety data sheet (MSDS) templates require additional customizing activities,
especially creating identification listings and generation variants.
These customizing entries are described in the respective report templates' area in this
documentation's appendix.
It is recommended to perform these steps before implementing the material safety data sheet
(MSDS) templates.
Starting with the 2010-1 Release, the material safety data sheet (MSDS) templates will use
function modules located in the /TDAG/-namespace instead of utilizing the Z-namespace
( ZISI...).
Therefore it is necessary to create the /TDAG/-namespace on a customer system, before importing the workbench transport with the actual function modules in the /TDAG/-namespace.
Please see section "file overview" to find details on the namespace transport.
7.1.2. Content of material safety data sheet (MSDS) template packages

The material safety data sheet (MSDS) template packages contain WWI template layouts according to regional legislation requirements and come with necessary customizing and expansion methods as well as Property Tree layouts (adapted to each template).
Each template also comes with a DataMapping-Document that gives detailed overview on the
printed properties.
122
SAP AG
SAP EHS Regulatory Content - material safety data sheet (MSDS) templates
Please find the contained files of the delivery.
7.2. Implementation
The following steps describe how to implement material safety data sheet (MSDS) templates.
7.2.1. Import transports

This chapter describes in detail the import of transports.
7.2.1.1. How to import transports (customizing or workbench)

123
SAP AG
value.)
be : SH2K102002
Setting filters :
124
SAP AG
7.2.2. Setup identification listings

This chapter describes in detail the setup of identification listings.
7.2.2.1. How to setup identification listings

Setting up identification listings is an IMG activity.
Please choose transaction SPRO , then choose SAP Reference-IMG (F5).
Go to: Environment, Health and Safety - Basic Data and Tools - Specification Management Specification Master - Check Identification Listings
Add the required Identification Listings via "New Entry" including a header, add the required
identifiers to the definition and save.
7.2.3. Upload files

This chapter describes which files have to be uploaded and how this upload has to be performed.
7.2.3.1. How to upload files

application server.
For example :
125
SAP AG
screen shot below.
7.2.4. Import report template

This chapter describes in detail the import of report templates.
You use this function to import report templates (or cover sheet templates and acknowledgement of receipt templates) to the SAP System.
In conjunction with report template export, you can exchange report templates between different SAP Systems.
7.2.4.1. How to import report templates

First upload the files dat-files (for example SDS_EU_2010_1.dat ) and doc-files on the application server using transfer format BIN (=>transaction CG3Z).
If a UNIX system is used, choose corresponding dat file with ending _unix.dat and rename it
to SDS_x_y.dat.
Then import the dat-file using transaction CG34 "Import Report Templates" or go to Logistics > Environment, Health and Safety -> Basic Data and Tools -> Tools -> Data Transfer -> Import
Report Template
The following settings need to be used:
File with path: <path on application server and file with ending .dat>
Character standard: MS-NT
126
SAP AG
Choose function "Check file". The SAP System checks if the data can be transferred correctly
from the transfer file and matches up the symbols.
Check Symbol Matchup to make sure all symbols are available on system in the correct way.
All entries in the system column must have symbol names. If they do not, check if symbol
generation was carried out on your system.
"Transfer/Start Time" will transfer (import) your file.
WWI will automaticly open the new template document. Check the template by clicking on the
check-button and save it.
7.2.5. Create generation variant

This chapter describes how to create generation variant.
The generation variant makes it possible for only permitted specification data to be output on
a report because it links the report template with a leading validity area and one or more value
assignment ratings.
7.2.5.1. How to create generation variant

Using transaction CG2B you can maintain generation variants for every template.
Or you go to Logistics -> Environment, Health and Safety -> Basic Data and Tools -> Report
Definition -> Edit Generation Variants
In the generation variant the main validity area is defined under "Validity Area"; the area from
which the template will draw its data.
The option "Usage check" is utilized to control the way in which the usages are compared.
There are four options to select: 0, 1, 2 and 3.
If you do not specify a value, the SAP System uses the value 0 as default.
Value 0: The usage is appropriate if - with the same rating used - the generation variant validity
area that is expanded to its countries and regions is the same as or is a subset of the expanded
validity area of the usage with which it is to be compared.
127
SAP AG
Example: Generation variant: DE Value assignment usage: REG_EU If a safety data sheet is
created for Germany, value assignment instances are also taken into account that are valid
for the validity area REG_EU.
Please see the SAP Help function for all the details on the option.
Under "Rating/Validity", additional validity/language combinations can be maintained:
These validity areas or languages must be addressed directly by the WWI coding in the
template (G-Repeating-Group) to be effective. By the use of these Rating/Validity options, it
is for example possible to give out special phrases in English on a template in Chinese or
Spanish.

The following steps describe how to check the implementation of material safety data sheet
(MSDS) templates.

Please use the following check list as guidance through the material safety data sheet (MSDS)
templates implementation and as check list after the implementation.
Status
Where to do
What to do
General
O
Administration Manual, Review documentation

ReadMe
Technical Part
O
SAP EHS (cg3z)
Upload files
SAP EHS (stms)
Check if necessary workbench transport is already imported (the workbench transports are the same transports as in
2010-2 release)
SAP EHS (stms)
Import customizing transports
Customizing (spro)
Setup identification listings
SAP EHS (cg34)
Import templates
SAP EHS (cg2b)
Create generation variants
128
SAP AG
Appendix A. How To ...

A.1. How to upload property tree transports files
The upload process consists of three steps:
In the following, the three steps are described:
You may ask your SAP system manager or proceed as follows:
Run transaction AL11.
The first part of the directory path is listed after the entry DIR_TRANS, for example "F:
\usr\sap\trans".
Within this directory two sub-directories exist:
The sub-directory "cofiles" where the co-files are stored.
The sub-directory "data" where the data files are stored.
Start transaction CG3Z.
Enter in the field "Source file on front end" the transport file name including the complete
path on your computer or file server, for example "d:\transfer\K102047.SH2" for a co-file
or "d:\transfer\R102047.SH2" for a data file.
Enter in the field "Target file on application server" the same file name and the complete
path on the SAP Application Server which you found out in Step 1, for example "F:\usr
\sap\trans\cofiles\K102047.SH2" for a co-file or "F:\usr\sap\trans\data\R102047.SH2" for
a data file. Make sure to enter "BIN" in the field "Transfer format for data".
Start the upload process with the push button "Upload". When the upload process has
been successful a message appears.
Navigate to the SAP Transport Management System (transaction STMS).
Choose push button "Import Overview (F5)".
Navigate to the transport domain of your SAP system: Position the cursor on the transport
domain and choose the push button "Display Import Queue" or choose "Double click".
Choose in the menu "Extras" -> "Other requests" -> "Add".
Enter in the field "Transp. Request" the name of the transport request, e.g.
"SH2K102047". The field "Import Queue" is already filled with the selected import queue.
Start the process with the push button "Continue". The transport request is added to the
bottom of the import queue with the highest number.
Please note that the listed "Owner" is the SAP user who created the transport request not
the login-user who started the upload process!
A.2. How to upload files

application server.
129
SAP AG
How To ...
For example :
screen shot below.
A.3. How to import transports (customizing or

workbench)
130
SAP AG
How To ...
131
SAP AG
How To ...
value.)
be : SH2K102002
Setting filters :
A.4. How to import BC sets

If BC Sets have been uploaded (cg3z) you must activate them.
Activation
Choose Tools - Customizing - Business Configuration Sets - Activation in the SAP menu, or
enter the transaction code SCPR20 in the command field.
Enter the name of the BC Set which you want to activate.
Choose Bus.Conf.Set - Activate or the Activate pushbutton.
Enter the transport request number when asked for a Customizing transport request and
choose Continue.
A warning that original tables are overwritten by activation of BC Sets appears. Choose one
of the following three options
132
SAP AG
How To ...
To proceed with the activation, choose Activation.
If several BC Sets are being activated, only those which have not yet sent an error message
are activated.
Simulation
To simulate activation, choose Simulation.
Simulation tests part of the activation procedure and creates an activation log. The log tells
the user whether the simulated activation reached a certain point. A successful simulation
does not guarantee the success of a subsequent activation. The errors in a simulation would
occur during activation.
Simulations write no data in customizing tables or transports.
The system checks for key conflicts in the BC Set.
Key conflicts occur if there are two data records in a hierarchical BC Set with the same key
but different values. In this case it is not clear which of the values is to be put in the original
tables. The activation is cancelled if key conflicts occur.
Result
The result of activation or simulation can be:
Activation successful
Program Response is a status message and all data are written.
Activation ended with warning
Program Response is a status message and most data are written.
Choose Compare with Customizing Tables and read activation log.
Activation ended with error
Activation log displayed automatically, data are not, or only partially, written.
Choose Compare with Customizing Tables and read activation log.
Compare with system tables

Double-click on the BC Set to be compared with the system tables.
Choose Utilities - Compare - With System Tables or the Compare with System Tables icon.
You can display all entries with the Display All pushbutton, or the differences only with the
Only Display Differences pushbutton.
Result of comparison of BC Set and Customizing tables
133
SAP AG
How To ...
In this example, the BC Set values (in the 1st row) and the values in the table named at the
right (in the 2nd row) are identical.
A.5. How to allocate phrase sets

There are two ways to generate phrase sets:
Run transaction CGCZ "Match Up Master Data" with flag "Match Up ValAss Type and
Char." only. This function determines all characteristics to which phrases can be assigned
- that are characteristics of type CHAR 30. These characteristics are transferred to the
table Phrase set - Attribute assignment (transaction CGAB).
Choose transaction CG1B "Edit phrase sets" and create manually phrase sets for all
characteristics which are described in the file "Changes....pdf" as "new, CHAR 30, multiple phrases" or new, CHAR 30, single phrase. Enter the characteristic key as the new
phrase set key. Add appropriate phrases to the new phrase sets. Exceptions are characteristics such as "Accuracy" or "GLP". For these characteristics, phrase sets already
exist (SAP_EHS_XXXX_XXX_PREC, SAP_EHS_XXXX_XXX_GLP) and can directly be
assigned.
Customers of SAP EHS Regulatory Content - multilanguage phrase library for hazard
communication receive the allocation of phrases to phrase sets of new characteristics
with the corresponding update.
Choose transaction CGAB "Edit phrase set-attribute assignment". Assign all new phrase
sets to the appropriate characteristics.
Run transaction CGCZ "Match up master data" with flag "Activate Phrasing of Characteristics." only. This function assigns the function module
134
SAP AG
How To ...
C14K_PHRASECHARACT_CHECK to all phrase-related characteristics. This enables
the system to call an assigned phrase set in the specification data base.

If an EHS system is set up initially the customizing activity "Generate Standard Phrase
Sets" is used in general to create and allocate phrase sets to all characteristics of type
CHAR 30.
Navigate to the activity "Generate Standard Phrase Sets" in the SAP customizing (IMDG)
(path within EHS 3.2 and higher releases: Environment, Health & Safety -> Basic Data and
Tools -> Specification Management -> Specification Data Base Structure -> Settings for
Value Assignment). A complete overview about this activity is given in the corresponding
IMDG activity documentation.
Start the activity.
Phrase sets are generated and allocated to all characteristics of type CHAR 30. Phrases
are not allocated to the new phrase sets. Assignments of phrase sets to characteristics
that already exist are not overwritten by the system.
Some characteristics defined as CHAR 30 are not meant to be assigned to phrase sets,
for example "Value in Non-Standard Unit". These characteristics shall be used to store a
numerical value and a unit but were unfortunately defined as a free text fields of CHAR
30. In this case, the assigned phrase set has to be deleted in the table "Edit phrase
set-attribute assignment" (transaction CGAB) after the standard phrase sets have been
created.
Run transaction CGCZ "Match up master data" with flag "Activate Phrasing of Characteristics" only. This function assigns the function module
C14K_PHRASECHARACT_CHECK to all phrase-related characteristics. This enables the system to call an assigned phrase set in the specification data base.
If the phrase set was deleted in the table "Edit phrase set-attribute assignment" (transaction CGAB) before carrying out this transaction, then the function module
C14K_PHRASECHARACT_CHECK is deleted in the corresponding CHAR 30-characteristic and this characteristic can be filled as a free text field.
135
SAP AG
How To ...
A.6. How to create WWI report symbols

Run transaction CGCZ "Match up master data" with flag "Generate Symbols" only. This will
generate the necessary new WWI symbols for the new characteristics.
Additional information:
In a standard R/3 System symbols are generated with descriptions in the logon language. The
flag "Regenerate Symbol Descriptions" within transaction CGCZ can be used to generate the
symbol descriptions in another language different from the logon language.
If the transaction CGCZ is run with the flag "Match Up Symbols-Phrase-Enabled Characteristics" the symbol definitions for the characteristic symbols that have been changed from phraserelated to non-phrase-related (or vice versa) will be updated..
136
SAP AG
How To ...
A.7. How to set up the Table-based Value Assignment

There are two ways to set up the Table-based Value Assignment:
137
SAP AG
How To ...
1.4. Enter a property key of a new property or a series of property keys in the field "Value
assgmt type" and start the process (pushbutton "Execute").
A general example for a property key is SAP_EHS_1023_043 (for property "GHS Classification"). Select the property keys of the new properties within a specific property tree
package from the file "Changes_.....pdf". The file name for a specific property tree package can be found in the Appendix.
Please avoid to execute this process with the same property key multiple times because
this would create multiple entries in the customizing table!
138
SAP AG
How To ...
1.6. Choose the entry "Set Up Table-Based Value Assignment". The complete customizing table opens. Check all entries for the configured property/properties:
1.8. Repeat the steps 1.2 to 1.7 to create the necessary entries for all new properties.
For EHS 3.2 and higher releases you have to change the configuration of existing properties where new characteristics were added and which were already configured for the Table-Based Value Assignment. The recommended procedure is to delete all entries for existing properties with new characteristics in the customizing table and to create the entries
for these properties again (see the following steps 2.1 to 2.14).
If the configuration of the Table-Based Value Assignment for properties with new characteristics was already changed, then these changes should be documented before deleting the
entries. In this case, an alternative could be not to delete all entries for a changed property
but to update the Table-Based Value Assignment for the existing property only (follow steps
1.1 to 1.8). Then, the new characteristics would be appended to the already existing entries
for this property. The correct order of the characteristics would have to be set up manually.
Please note, that the Table-based Value Assignment customizing table can only be changed
in SAP systems where the direct customizing is enabled. If the direct customizing is disabled
(for example in a production system), then the Table-based Value Assignment should be set
up in a system where the direct customizing is enabled (for example a development system).
The correct entries can be then transported to the system with the disabled customizing
(customizing transport).
139
SAP AG
How To ...
2.3. Choose the entry "Set Up Table-Based Value Assignment". The complete customizing table opens.
2.4. Choose the push button "Position", enter a property key of an existing property with
new characteristics and navigate to this property. Select the property key from the file
"Changes_.....pdf". The specific file name for a certain property tree package can be found
in the Appendix.
2.5. Select all entries for this property.
2.6. Delete the selected entries (push button "Delete").
140
SAP AG
How To ...
2.9. Enter the property key of the property, which entries you deleted in the previous step,
in the field "Value assgmt type":
2.10. Start the process (pushbutton "Execute").
2.12. Choose the entry "Set Up Table-Based Value Assignment" again. The customizing
table opens. Check all entries for the configured property:
2.14. Repeat the steps 2.2 to 2.13 to create the necessary entries for all existing properties
with new characteristics.
A.8. How to create passive phrase catalogues

141
SAP AG
How To ...
Requirements : You have already defined the number

ranges for the phrase key.
Note

Phrase library
CED
Label
CED for EHS
Note
optional
Active library
remains empty
Distributor
Publication Date
Version
library version
Phr. ChkRtn
Object name
ESN_PHRID
Int. no. range
0I
Ext. no. range
0E
A.9. How to setup number ranges

Here the interval limits of the internal (0I) and the external number range (0E) must be entered.
The internal number range is assigned by the system itself while the automatic key definition
whereas the external number range must contain all phrase keys which are not produced
automatically but entered manually or by phrase import.
EH&S 2.5B and newer: Implementation Guide for R/3 Customizing (IMG) / Environment, Health
& Safety / Product Safety / Phrase Management / Specify Number Ranges for Phrases
EH&S 3.2 and newer: Implementation Guide for R/3 Customizing (IMG) / Environment, Health
& Safety / Basic Data and Tools / Phrase Management / Specify Number Ranges for Phrases
To import the CED phrases the external number range 0E must have the alphanumeric interval
from A to ZZZZZZZZZZZZZZZ.
We recommend to designate the internal number range 0I for numeric values only (interval
100000000000000 to 899999999999999).
142
SAP AG
How To ...
A.10. How to import phrases

Check the file (F5)
Save
Note
Caution
passive library!
143
SAP AG
How To ...
A.11. How to merge phrases

with :
144
SAP AG
How To ...
and select merge.

145
SAP AG
How To ...
Note
Note
A.12. How to import phrase set assignments

into SAP EHS.
Check the file (F5)
146
SAP AG
How To ...
147
SAP AG
How To ...
contact us.
A.13. How to combine/retire phrases

A.13.1. Combining Duplicate Phrases
Previous versions of retired phrases lists will be delivered on demand. With those the following
should be done.
All phrases in column A will no longer be maintained and should be combined with the phrases
listed in column D .
Combining a phrase adds all phrase set assignments from the no longer used phrase (replaced
phrase) to the phrase that's still in use (combined phrase). Additionally all substance value
assignments will be checked and the no longer used phrase key will be replaced by the combined phrase key.
Please see also the SAP EHS documentation for further information on combining phrases.
(example on next page)
Create a hit list of two or more phrases you want to combine
Check that both phrase texts are identical
Do a check if these phrases are used: -> Extras -> Where-used list
Choose -> Extras -> Combine
Mark the phrase that you want to keep
Choose Execute or Execute in background
Important Notes:
When combining phrases, the phrase positions will not be changed, e.g. missing translations
in one phrase will not be filled with the existing translation of the other phrase nor will changes
to the phrase text or code be made.
If a phrase is used directly on a report template, the symbol for this phrase has to be replaced
manually with the phrase key of the combined phrase. Use the "where-used list" functionality
to check if a phrase is used on a report template.
If a phrase is used, execute the combine as a background job as it might take some time to
update all value assignments with the new phrase key.
Please note that combining phrases may have an influence on e.g. Expert rule sets or data
loads. It may become necessary to change mapping tables accordingly.
For combining phrases when using ALE distribution please take notice of SAP NOTE 727174
Example:
Phrase to be replaced by another phrase
148
SAP AG
How To ...
Example of hit list of duplicate phrases
The marked phrase N15.00208960 will still be in use after combining, N02.00900510 will be
combined (replaced) and is no longer available after combining.
A.13.2. Retired Phrases

Due to regulatory changes or the addition/revision of phrases some of the older phrases of the
CED phrase library may become obsolete. We publish a list of so called "retired phrases" as
a spreadsheet (e.g. CED_2009_1_RetiredPhrases.xls) which is included in the delivery. For
past updates these files can be delivered on demand.
Please review the retired phrases list and inform us if there are phrases that you still need.
After that, please delete any phrases that you no longer need from your active phrase library:
Create a hit list of these phrases
Do a check if these phrases are used: -> Extras -> Where-used list
149
SAP AG
How To ...
If not used, choose -> Edit -> Delete
Phrases deleted from the SAP system are stored in the backup phrase library unless an active
phrase that originated in a passive phrase library is deleted.
A.14. How to create phrase variants

In the phrase library there are several phrases including.? in the phrase text, e.g. .?C. If you
wish to use such a phrases with a specified temperature e.g. 10C, please create a variant
of this phrase.
To do so, create a hit list with the original phrase, mark the phrase and create a copy
(Phrase_CopyTemplate). Then choose a new phrase key starting with P (for permutation) and
safe the new phrase.
Replace the ? in each language of the new P phrase with the chosen number or customer
specific information, in this case 10, and safe again.
Please do not alter the original CED phrase as your changes might be overwritten in one of
the following updates.
It is also possible to replace the qualifier .? automatically by using special user exits at the
phrase. Please see SAP Note 1373615 for more information.
In addition there is a standard functionality for special qualifiers available, that may insert phrases like target organs into another phrase.
Example:
"Causes damage to organs (/$/*_ORG_SING_ORAL/$/) if swallowed." The functionality
would replace the placeholder with the values stored in *_ORG_SING_ORAL (e.g. in
SAP_EHS_1023_044 GHS Target Organs for single exposure, oral). Please note that this
functionality might not work correctly in all languages, because the value used might have an
impact on the wording of the phrase in some languages. It usually works in most Western
and Eastern European languages. Until now, this functionality is able to manage phrases only.
Other values as e.g. numerical ones are not yet covered.
Please see SAP Note 146663 Placeholder phrases for EH&S reports for details on how to
implement the placeholder functionality and how to use it in phrases and WWI templates.
A.15. How to install EHS OCC

On each front-end computer that is used for loads of SAP EHS Regulatory Content - substance
lists and reference data, SAP EHS Open Content Connector (OCC) needs to be installed.
OCC in the latest version is part of the SAP EHS Expert installation package. If your current
OCC version is lower than Service Pack 20, we highly recommend that you upgrade all OCC
installations to this version. See the SAP EHS Regulatory Content Release Notes document
for new features of this OCC version.
Note
For installation local administrator rights might be required. Registry settings will be
added under the following paths:
150
SAP AG
How To ...
SAP EHS OCC Service Pack 20 and below:

HKEY_LOCAL_MACHINE\SOFTWARE\TechniData\EHS-AddOns\Systems
HKEY_LOCAL_MACHINE\SOFTWARE\TechniData\EHS-AddOns\Instances
SAP EHS OCC Service Pack 21 and higher:

HKEY_CURRENT_USER\Software\EHS-AddOns\Systems
HKEY_CURRENT_USER\Software\EHS-AddOns\Instances
HKEY_CURRENT_USER\Software\EHS-AddOns\Open Content Connector
A.15.1. Initial Installation/Upgrading of older OCC versions

Prerequisites.
OCC for details.
3. Run Expert/OCC Setup
4. Choose Option "Open Content Connector". If Expert rule sets are used on this computer,
additional setup options may be required.
A.16. How to setup a RFC connection


RFC destination: We recommend you structure the name as follows:
Connection type: T
151
SAP AG
How To ...
4. In the Registered Server Program screen area, enter the PROGID entry from your installation (see How to install EHS Expert or entry in the file SAPRFC.ini) in the program ID field.

settings easily.
Connection type: T
service.
152
SAP AG
How To ...

Connection type: T
153
SAP AG
How To ...
A.17. How to test the RFC connection

154
SAP AG
How To ...
A.18. How to extend entry in secondary data determination

Activities
155
SAP AG
How To ...

EXPERT_COMMIT_MODE
Note
Expert.
EXPERT_DESTINATION
156
SAP AG
How To ...
EHS_EXPERT).
to the EHS Expert.
Examples
the USA.
EXPERT_RULE_SET
EXPERT_COMMIT_FLG
157
SAP AG
How To ...
to inactive.
Expert.
Warning
determination.
EXPERT_WRITE_OWNER
digits.
158
SAP AG
How To ...
Note
EX.
EXPERT_ADD_PARAM_1
EXPERT_ADD_PARAM_2
159
SAP AG
How To ...
EXPERT_ADD_PARAM_3
EXPERT_TAB_FIELD_1
EXPERT_TAB_FIELD_2
EXPERT_TAB_FIELD_3
EXPERT_TAB_FIELD_4

Sample value
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
SAP_EHS_0101_002
EX
EXPERT_READ_RATING
PUBLIC
REG_WORLD
EXPERT_RULE_SET
ZEXP_GHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHS
160
SAP AG
How To ...
REG_WORLD

Sample Value
EXPERT_ADD_PARAM_1
headerurl=<path
to
CLEO
PS
DB>\PS_DB
\header.xml
EXPERT_ADD_PARAM_2
usernameurl=x
EXPERT_ADD_PARAM_3
passwordurl=x
EXPERT_CALL_ONCE
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_OCC
EXPERT_READ_RATING
EXPERT_RULE_SET
CLEO_PS
EXPERT_TAB_FIELD_1
<subid>
EXPERT_TAB_FIELD_2
EXPERT_TAB_FIELD_3
EXPERT_TAB_FIELD_4
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
TECHNIDATA
REG_WORLD
A.19. How to manage user exits

In this IMG activity, you can define function modules for the user exits of the SAP component
Environment, Health and Safety for the following areas: Type SUB_SEDACA Secondary Data
Determination
Standard environment parameters with default values are delivered with some reference function modules.
Tip
If you want to define your own function modules, display the documentation for the
corresponding reference function module (SE37). Write the new function module analogous to the reference function module and its interface.
161
SAP AG
How To ...
Activities
1. Call the IMG activity.
2. Check if the default settings are correct.
3. You can assign a specification category to a user exit so that this user exit is displayed
depending on the specification category (for example, for user exits on secondary data
determination).
The assignment is relevant only for user exits that relate to specifications.
A.20. How to add user defined text types


Save your settings
A.21. How to add data origins


Save your settings
A.22. How to add regulatory lists

162
SAP AG
How To ...

Save your settings
A.23. How to add literature sources


163
SAP AG
How To ...
A.24. How to add identifier types

Start transaction "spro" navigate to Environment, Health and Safety -> Basic Data and Tools
-> Specification Management -> Specification Master -> Check Identification Types.
Enter the Identification category (NAM, NUM FRM....) as work area.
With F5 or "New Entries" you can enter a new identification type and additional settings.
You may only enter values within the "Z"- namespace. Others are possible but are not recommended - if really necessary - ignore warnings and safe.
Go to the navigation sidebar and double click on the "Specification Category" entry and enter
a new entry e.g. "SUBSTANCE"
save your Setting.
164
SAP AG
How To ...
A.25. How to add dangerous goods master data

SAP EHS offers wide customizing options regarding dangerous goods master data. Maintenance of these customizing settings is done in transaction SPRO at Environment, Health and
Safety - Dangerous Goods Management - Basic Data and Master Data. Here there are three
further sub-nodes, Common Settings, Basic Data, and Master Data, each consisting of multiple customizing items. In the following those customizing activities that may be relevant are
described in detail.
A.25.1. Dangerous Goods Classes and Classification Codes

Management - Basic Data and Master Data - Common Settings - Specify Dangerous Goods
Classes and Classification Codes:
165
SAP AG
How To ...

Enter the DG regulation the class and letter are relevant for
Enter the DG class and give a description
Switch to the navigation side bar on the left side and double click "Classification Code"
Enter the classification code together with a description
Save your settings
A.25.2. Risk Potentials

Management - Basic Data and Master Data - Basic Data - Specify Risk Potential:

Enter the DG regulation and class the risk potential is relevant for
Enter the risk potential (and classification code if applicable)
Enter a description for the new risk potential
Save your settings
A.25.3. Hazard Identification Numbers

Management - Basic Data and Master Data - Common Settings - Specify Hazard Identification
Numbers:

Enter the DG regulation the new hazard identification number shall be relevant for
Enter the new hazard identification number together with a description
Save your settings
A.25.4. Danger Labels

Management - Basic Data and Master Data - Common Settings - Specify Danger Labels:

Enter the DG regulation (and class if applicable) the new danger label shall be relevant for
Enter the danger label together with a description
Save your settings
A.25.5. Packing Instruction Numbers

Management - Basic Data and Master Data - Common Settings - Specify Packing Instruction
Numbers: (these entries are just used in RiscClssification for creation of transport documents)

Enter the DG regulation the packing instruction number shall be relevant for
Enter the packing instruction number and a description
Save your settings
166
SAP AG
How To ...
A.25.6. Categories of Instructions for Enclosure and Instructions for Enclosure

Management - Basic Data and Master Data - Common Settings - Specify Categories for Enclosure: (these entries of packing instructions are used in PackingRequirements)
Choose Categorie or enter a new one if necessary
Switch to the navigation side bar on the left side and double click "Specify Instructions for
Enclosure"
Enter Instruction for Enclosure and regulation the new instruction shall be relevant for
Save your settings
A.25.7. Packing Codes

Management - Basic Data and Master Data - Common Settings - Specify Packing Codes:
(these entries of packing codes are used in PackingRequirements, do not use Packing Codes
(old))
Enter Packing code with description and regulation the new code shall be relevant for
Save your settings
A.26. How to add validity areas

The validity area determines in which jurisdictions values assigned to specifications apply. You
specify validity areas depending on the validity area categories. You can use the validity area
categories to define plants, business areas or regions, for example, as validity areas. You can
assign individual jurisdictions or organizational units at a lower level to each validity area, for
example:
You can assign countries and regions from the country table as validity areas for validity areas
of the category REGION. You can assign other organizational units for validity areas of another
category.
The definition of validity areas is closely linked to the requirements for reports. The validity
areas for this IMG activity are also used in the R/3 component Dangerous Goods Management.
Caution
Be aware, that the validity area "REG_WOLRLD" is "empty" and
has the default behaviour to recognize all countries.
Once you have used a validity area in a productive system, it can
no longer be deleted.
Newly created validity areas are not evaluated correctly by the
Expert before restarting the Expert Server.
Go to the IMG customizing ("spro"):
Navigate to Environment, Health and Safety -> Basic Data and Tools -> Additional Information for Value Assignment -> Usage ->Specify Validity Areas.
167
SAP AG
How To ...
Press F5 or "New Entry" and enter the Validity area category (e.g. REGION) and the new
area as well as the description. Mark the entry and switch to the navigation sidebar
Double clicking the "Assign Validity Area/Country" entry the list of countries belonging to
this area opens (- empty). There you can assign all countries that shall belong to this new
validity area.
A.27. How to create extended search user exit
168
SAP AG
How To ...
A new entry for an extended search user exit can be added in SAP EHS customizing.
Activities
2. Create a new user exit of user exit type SUB_QUERY with the following values:
User Exit Type
SUB_QUERY
User Exit Name
SUB_FILE
Specific. categ.
SUBSTANCE
EN: List substance with new data...

DE: Listenstoff mit neuen Daten ...

C1H0_SUB_FIND_BY_VALU
3. Parameters and Values are not required for a search user exit and you can leave them
empty.
A.28. How to setup/update XML substance

database for substance lists and reference data
Note
This step is not required if substance lists and reference data is loaded from the SAP
EHS Regulatory Content webserver, only if a local copy of the database is used.
No database server is needed, any file server with a fast connection and sufficient
storage space is suitable.
Your data implementation or update package contains a setup file e.g. cleo_2009-2_region.exe
which includes all required database XML files. Please execute this file and choose the correct
path to your SAP EHS Regulatory Content - substance lists and reference data (Product Safety
or Dangerous Goods) database installation. The path must match the entry of the secondary
data determination User Exit for data load, see chapter How to configure the User Exit.
Note
If you are updating an existing database, the setup program will suggest a path for
the installation based on the storage path of the last installation from this computer.
Please carefully check this installation path to avoid mixing up e.g. productive and test
databases.
In your XML substance database folder, a text file called version.txt is stored which
will have information about the currently installed database. Please check the version
file before updating the database to avoid overwriting your database with the same or
older files.
Each installation of the substance lists and reference data XML substance database takes
approximately 1,5 GB for Product Safety and 1,1 GB for Dangerous Goods database.
After installation of the XML files, the structure of the database should look like:
169
SAP AG
How To ...
Product Safety:

(header.xml and version.txt)
<path to XML substance database>\CLEO\1 subfolder with all CAS numbers starting with 1
<path to XML substance database>\CLEO\... subfolders for other CAS numbers starting
with 2 to 9
<path to XML substance database>\CLEO\G subfolder with all substance groups
<path to XML substance database>\CLEO\N subfolder with all non-substances data, e.g.
mixtures and data with no CAS number
Dangerous Goods and Dangerous Goods with Packaging

Data:

(head.xml and version.txt)
<path to XML substance database>\CLEO subfolder with all data for DG regulation
\ADN
ADN(R)
<path to XML substance database>\CLEO\... subfolders for other DG regulations
<path to XML substance database>\CLEO subfolder with all available UN numbers
\UN
Alternatively extract the files and burn a DVD if no network folder should be used (performance
loss!). The network path for database must be accessible for all users (read access). For
security reasons, access should be limited to persons allowed to load SAP EHS Regulatory
Content - substance lists and reference data. Please note the path to the database in the
installation protocol.
It is possible to have separate databases for Test, Development and Productive systems. This
allows testing of data updates without impact on the productive data load. If you want to do this,
copy the whole database including all subfolders to a different storage location. In addition,
changes to the mapping database and user exit are required to support multiple databases
(see also chapters How to configure the User Exit, How to configure EHS OCC and How to
setup Mapping Database).
Note
Please make sure that you have a fast network connection between your OCC frontend computer, SAP application server and the storage location of the XML substance
database. WAN connections are usually unsuitable for OCC as large amounts of data
have to be transferred. See also SAP note 1235663 for further hints to improve the
OCC performance.
A.29. How to setup/update mapping database for

SAP EHS Regulatory Content - substance lists
and reference data
170
SAP AG
How To ...
The mapping database file is included in folder 5-Mapping-Database of your SAP EHS Regulatory Content -substance lists and reference data package. The mapping file is named
td_cleo.mdb for product safety and td_cleo_dg.mdb for dangerous goods.
Initial setup of mapping database

This mapping database can either be installed locally for each user or used as a central network-database for all users.
Advantages of a local database:
Fast access during data load
Cache during the first data load is created much faster
No access conflicts if several person are loading data at the same time
Disadvantages of a local database:
During updates, each database needs to be changed/replaced.
Users can have different mapping for phrases, properties and other values, potentially creating inconsistencies in SAP EHS.
Advantages of a central database:
Only one database needs to be maintained/updated
All users have the same mapping settings
Disadvantages of a central database:
If network access is slow or bandwidth is limited, response time during data load might be
longer. Especially creating the cache will be much slower.
In rare cases conflicts in opening the database if several persons are loading substance lists
and reference data at the same time
Note
Please make sure that you have a fast network connection between your OCC frontend computer and the storage location of the mapping database. WAN connections
are usually unsuitable for OCC as large amounts of data have to be transferred. As the
mapping database is used to store cached data for improved performance, this file can
get quite big (over 100 MB). See also SAP note 1235663 for further hints to improve
the OCC performance.
If you are copying the mapping database from a CD/DVD to your local drive/network,
please remove the write protection of the file td_cleo.mdb after copying to your local
drive.
If the active phrase library is different than CUST, changes to the mapping database are required:
1. Open td_cleo.mdb / td_cleo_dg.mdb in MS Access
2. Open table ExpPhraseMap
3. Choose column External_id and replace CUST:
Search for: CUSTReplace with:????- (name of active phrase library)
171
SAP AG
How To ...
Search in: External_id
Compare: Beginning of field
Replace all
Note
If several installations were done for the database (test/dev/prod), we recommend a
separate mapping database for each of the installations.
The OCC mapping database follows the same structure as SAP EHS Expert mapping databases. There are separate mapping tables for properties, phrases and other values:
Updating the mapping database

We recommend replacing the mapping database with the new version included in your update package as additional phrases and regulatory lists are added in the phrase mapping
table. If you have already made your own changes to the mapping database, e.g. renamed
identifiers or phrase mapping changes, please contact us and we will support you in updating
your database. If your active phrase library is different than CUST, changes to the mapping
database as specified above are required.
You can find the path of your mapping database in the ExpertAdmin tool installed on your front
end computer. On the instances tab there should be entries for e.g. CLEO_PS or CLEO_DG
which specify the path to the current mapping database. Please see Section 5.2.7.1.1, How
to configure EHS OCC for details.
Repeat the above steps for all installations of the SAP EHS Regulatory content - substance
lists and reference data mapping database if you are using more than one mapping database
or if each user has a local copy of the mapping database.
Note
We recommend to create a backup copy of your existing mapping database before
overwriting it with the new version of the mapping database.
Tables of the mapping database
ExpRecordMap: Property Mapping

ExpFactMap: Characteristics, Identifiers, Free Text, ... and display order
ExpPhraseMap: Phrases and other values
ExpGroupMap: Not used for OCC
ExpSubstanceMap: Individual filter settings for each substance based on the last load for
this substance
History: Version information and change log
CacheHeaderInfo: Cached information about the index file. Only available after the first data
load.
CacheHeaderAvailableSubstances: Cached data about all available substances in the
database. Only available after the first data load.
CacheHeaderGroup: Cached data about all group assignments in the database. Only available after the first data load.
172
SAP AG
How To ...
In all tables, Internal_id means the key/value in the database and External_id the corresponding key/value in SAP EHS.
A.30. How to install the Update Analysis Tool for

Excel
The Simulation Tool for SAP EHS Regulatory Content - substance lists and reference data
is included in folder 6-UpdateTools and can be installed on front-end computers with a few
simple steps:
Copy either cleo_simulation.xlt (MS Excel 97 - 2003) or cleo_simulation.xltm (MS Excel 2007) to your Excel template folder, usually ...\Documents\<user>\Application Data\Microsoft\Templates
As an alternative, open cleo_simulation.xlt in Microsoft Excel 97-2003 and choose "Save
as...". Use the option for Excel templates *.xlt and the correct path to the template folder should be preset. Save as xlt-file to this folder. For MS Excel 2007, open choose
cleo_simulation.xltm and save as "Excel Template with macros" *.xltm
Note
You need to activate the macros in cleo_simulation.xlt / cleo_simulation.xltm or you
will not have access to any of the functionalities of the tool. If you have installed previous versions of the Simulation Tool for Excel you may want to make a copy before
overwriting with the new version. If you do not want to activate macros, we recommend
using the previous version of the tool which was not making use of any macros but
has limited functionality.
Note
In MS Excel 2007, you need to save this Excel file in a trusted directory or you cannot
activate the macros.
A.31. How to configure EHS OCC

The following settings in OCC must be created to support the data load of SAP EHS Regulatory
Content - substance lists and reference data.
Note
Please note that everything described in this chapter is only valid for SAP EHS Open
Content Connector (OCC) Service Pack 21 (November 2009) or higher. Please update
OCC to this version or contact us for the settings in older OCC versions.
Note
If multiple installations of the database exist for test, development and productive systems, the below steps must be repeated for all of them. Assign the name of the instances as specified in the user exit parameter EXPERT_RULE_SET and assign the
appropriate mapping database.
Product Safety
A new instance entry has to be configured for Product Safety data:
173
SAP AG
How To ...
Choose Add
Name: CLEO_PS
System: EHSOCC
Mapping: Path to your mapping database TD_CLEO.mdb which was part of the installation
in step "How to setup Mapping Database"
Dangerous Goods / Packaging Data

A new system entry has to be configured for Dangerous Goods/Packaging Data:
Choose: Options -> Preferences ...
Switch to the Systems tab
Choose Add
Name: EHSOCCDG
Options: All settings should have been automatically copied when the EHSOCCDG key was
created. No changes necessary.
Choose Apply
174
SAP AG
How To ...
A new instance entry has to be configured for Dangerous Goods/Packaging Data:

Choose Add
Name: CLEO_DG
System: EHSOCCDG
Mapping: Path to your mapping database TD_CLEO_DG.mdb which was part of the installation in step "How to setup Mapping Database"
175
SAP AG
How To ...
A.32. How to configure the User Exit for SAP EHS

Regulatory Content - substance lists and reference data
The user exit for secondary data determination substance lists and reference data needs to
be adapted to the installation path of the XML substance database for Product Safety or the
XML substance database for Dangerous Goods. EXPERT_ADD_PARAM_1 of the User Exit
has to be changed to reflect the path of the database index file of either the productive or the
test database.
Environment, Health & Safety -> Product Safety -> Basic Settings -> Manage User Exits
User Exit Category
SUB_SEDACA
User Exit Name
CLEO_PS or CLEO_DG
EXPERT_ADD_PARAM_1
headerurl=<path
to
176
XML
substance
SAP AG
How To ...
If multiple installations of the database exist for test, development and productive systems,
copy the UserExit for each separate installation of the database. Change the following two
parameters:
EXPERT_ADD_PARAM_1
PS: headerurl=<path to XML substance

DG: headerurl=<path to XML substance
database>\head.xml
EXPERT_RULE_SET
Instance name given to the database in

step How to configure EHS OCC, usually
CLEO_PS or CLEO_DG
177
SAP AG
How To ...
Example A.1. Example:

An additional database for the test system was created at F:\CLEO-TEST:
Additional registry-key needed for instance CLEO-TEST
Path to mapping database for new instance in registry changed to F:\CLEO-TEST
\td_cleo.mdb
Existing User Exit, e.g. CLEO_PS copied to new key, e.g. CLEO_TEST
In new User Exit, change EXPERT_ADD_PARAM_1 to: headerurl= F:\CLEO-TEST
\header.xml
In new User Exit, change EXPERT_RULE_SET to: CLEO-TEST
A.33. How to adjust the Fact Mapping

Table Field
Meaning
Internal_Id
Record
Group
External_Id
Descriptions
Options
IsPhrase
A.34. How to adjust the Record Mapping

Table Field
Meaning
Internal_Id
Group
External_Id
Descriptions
Options
178
SAP AG
How To ...
A.35. How to adjust the Phrase Mapping

Note
Table Field
Meaning
Internal_Id
External_Id
Phrase key in EHS
Phrasetext
Phrase text
Options

phrases.
mapping table.
Tip

179
SAP AG
How To ...
A.36. How to write the Last Run Date

The EHS Expert is able to write the current date when running an Expert rule, to allow looking
up when a rule was called for the last time on a given substance. For that purpose, the property
"EHS Expert Explanations" was extended by another characteristic "Last Run Date" allowing
to store a date.
To activate writing the last run date, the following user-exit parameters have to be set:
EXPERT_WRITE_RUN_DATE = X (invokes writing the date)
stored at)
EXPERT_EXPLANATION_DATE_PROP = SAP_EHS_0101_002_RUN_DATE (characteristic where the date of the last run shall be stored)
A.37. SAP EHS Regulatory Content - substance

lists and reference data (Product Safety) Update
Data Load
A.37.1. Review Regulatory Changes
SAP EHS Regulatory Content Release Notes include a brief overview of the new, deleted
and modified regulations in this version. Details about each regulatory list, e.g. list purpose or
mapping to SAP EHS can be found in the content reports which are part of this update.
All documents are available in folder 0-Documentation. This information should be reviewed
prior to continuing the update process.
A.37.2. Update Cached Data

Start OCC for SAP EHS Regulatory Content - substance lists and reference data (Product
Safety) for any list substance after you have updated your database. The first load after the
update will analyze the database for new and changed substance and will store this information
locally in your mapping database (cache).
This process may take from less than a minute to several minutes, depending on your network
speed to the database and your front-end computer (memory). Minimum requirements are 512
MB memory, we recommend 1 GB for the initial load.
Only the first load will take this long, after the cache has been rebuild, load times should be
down to only a few seconds again.
We recommend that the first load is done by somebody with a fast connection to the database,
e.g. someone working at the same site as the database installation.
180
SAP AG
How To ...
A.37.3. Review New Filter Settings

For the new lists added with this release, please check the filter settings and change the standard filter settings if required. The default is that new lists will be added to your standard filter
settings as to be loaded.
After reviewing the filter settings, you can define these as the new standard by clicking the
"Default" button.
A.37.4. Hit List of List Substances

SAP EHS Regulatory Content - substance lists and reference data comes with a functionality
to search for list substances with new or changed data available. We recommend using this
functionality to create a selection of your list substances that should be checked for new data.
Note
With the SAP EHS Regulatory Content 2009-1 update we have provided enhanced
functionality for the list substance search which performs much faster than older version
of the program. Please check the technical details of this update and make sure that
the new version of the program is installed to avoid long run times or time-out issues.
1. Choose Extended Search: List Substance with new content ...
181
SAP AG
How To ...
2. Specify the path to the file cleo_update_2010-1.txt which can be found in folder 6-UpdateTools.
3. Combine with any other search option, e.g. SUBID or identifiers and execute the search.
4. A hit list of all list substances will be created that potentially have new or updated regulatory
data available.
182
SAP AG
How To ...
5. We recommend saving the created hit list so you have it available in the future without rerunning the query.
Note
Starting with update 2010-1, we also provide a file cleo_new_group_assignments.txt.
This file can be used in the same way as described above, however it generates a list
of substances with new group assignments compared to the last release.
Note
For performance reasons, we are only checking the changes on a per substance level
not on single data sets. As a result you may have substances on your hit list for which
you do not get any new or changed data when you try to load them. This is the case if
You have not licensed all regional packages for SAP EHS Regulatory Content - substance lists and reference data and the changes are in an area you have not licensed.
You have switched off certain lists/regions in your filter settings; changed data therefore will not be displayed.
You have decided not to load certain data and/or groups in the past for this substance, if the change is in one of these data sets, it will not be displayed.
A.37.5. Simulate Data Load

Based on the generated hit list we recommend to simulate the data load first, before you start
loading updates. The simulated update will be exported to a spreadsheet which you can then
use to analyze the changed data for potential impact.
1. Create a hit list of substances either manually or as described in the last chapter of this
guide.
2. Select (all) substances
3. Start the secondary data determination and choose CLEO Product Safety (or a comparable
entry available in your system)
->Utilities -> Secondary Data -> Determination -> CLEO Product Safety
4. Select a substance and press "Set Filters"
5. Set data options "Load Changes Only" and optionally "Use Substance Groups"
183
SAP AG
How To ...
6. Select "Apply to All Substances"

7. Back on the OCC substance list, choose the spreadsheet symbol to simulate the update
data load
8. A suitable program assigned to handle CSV data will be opened, usually this is Microsoft
Excel. Save the spreadsheet that was created with the new and revised list substance data
for further use.
A.37.6. Analyze Changed Data

SAP offers a template for Microsoft Excel which allows a first analysis of the new and changed
list substance data. If the template is not installed on your computer, please follow the steps
described in the SAP EHS Regulatory Content Administration manual or contact us for further
information.
1. Open Excel and create a new spreadsheet using the installed cleo_simulation.xlt as a template:
2.
3.
4.
5.
6.
-> File -> New -> New from template -> General Templates -> cleo_simulation.xlt
When prompted, enable macros
Open the spreadsheet with the new and revised list substance data you created during the
data load simulation if it is no longer open
Click the button Import OCC Data. The tool will check for any open OCC simulation file
and ask for your confirmation to import the data. If no spreadsheet with OCC data is found,
please either copy the data manually or open the correct file (starting with occSimu_*.csv)
Click the button Start Analysis to analyze the imported OCC data.
Save the new spreadsheet
The Simulation spreadsheet offers some functionality for a first analysis of new and changed
data:
Two lines per dataset, the first one (white background) is the new SAP EHS Regulatory
Content data. The second line (grey background) is existing data in SAP EH&S
Pairs of related data are assigned a unique record number in column A, e.g. 1_CLEO and
1_EHS
184
SAP AG
How To ...
In column "Mode" each record is marked as either new, changed or inactivated

Filter options for all fields, e.g. by property or regulatory list
New records are highlighted bold red (complete line)
In changed records, only important changes are highlighted bold red
Inactivated records are highlighted in italics (complete line)
In the top right corner a summary is given (number of substances and records)
Explanation of some fields:

Column A: Unique record number for pairs of related data, e.g. 1_CLEO and 1_EHS
Column B: Substance ID of SAP EH&S (SubID)
Column C: Group ID of SAP CLEO => Data is from a generic group, not for the substance
itself
Column E: Mode - "New" , "Change" or "Inactivated"
Column F: Property - this is the property or identifier with the new/changed data
Column H: CAS number or identifier type
Column I: Name of the substance
Example A.2. Examples

Example 1: Select all substances that have a changed EU Classification
Switch filter of column Mode to "change"
Switch filter of column Property to "CLASSIFICATION"
Example 2: Select all records that have a new entry for notification status
Switch filter of column Mode to "new"
Switch filter of column Property to "NOTIFICATIONSTATUS"
Example 3: Select all substances with a new synonym name identifier:
Switch filter of column Mode to "new"
Switch filter of column Property to "__IDENTIFIERS__"
Switch filter of column CAS/ID Type to "SYN"
Example 4: Select all records with new or changed data for New Zealand:
Switch filter of column Lit. Source to "Custom..."
Define criteria "contains" and "NZ_"
A.37.7. Load Changes to SAP EH&S

There are two different options to load new and changed data into your existing list substances
in SAP EH&S.
If only a few substances need to be updated or if you want to exclude some data from being
updated, the manual process is the best choice.
If the data analysis in the previous chapters has not shown any critical changes and a lot of
substances have new data available, the autoload functionality should be used.
A.37.7.1. Manual update load

A manual update load is almost identical to an initial data load, except for two differences:
The option " Load Changes Only " is set and you can compare the new data with the already
existing data in SAP EH&S directly in OCC.
185
SAP AG
How To ...
1. Create a hit list of substances either manually or as described in Section A.37.4, Hit List
of List Substances
4. If you have selected more than one substance, select a substance from the following screen
and press "Set Filters"
5. Set data options "Load Changes Only" and optionally "Use Substance Groups"
6. Select "Apply to All Substances"
7. Back on the OCC substance list, select the " Ok / Show Regulatory Data" button
8. Compare new and changed data to existing data in SAP EH&S
9. Make your choices on load/no load/etc.
10.Save data to EH&S
A.37.7.2. Mass Load / Autoload

The autoload functionality is different from a standard load as no user interactivity is possible
after a choice of options and filters/regulatory lists was made. All changed and new data will
be automatically loaded into the existing list substances in SAP EH&S.
1. Create a hit list of substances either manually or as described in Section A.37.4, Hit List
of List Substances
4.
5.
6.
7.
Select a substance from the following screen and press "Set Filters"
Set data options "Load Changes Only" and optionally "Use Substance Groups"
Select "Apply to All Substances"
Select the "Autoload" button
Note
If a new group was assigned to a substance, the group information will not be loaded
using the autoload functionality combined with the "load changes only" option. This
is the intended behaviour to avoid unintentional group assignments which were not
reviewed by your regulatory experts.
If new or changed data becomes available within an existing group, your choices in the
past decide if the data will be loaded:
If a group was loaded in the past, all new and changed data will be loaded as well.
If a group was set to "no load" in the past, new and changed data will be ignored
and not loaded.
A.38. How to install EHS Expert

186
SAP AG
How To ...
Tip
We recommend to set up separate Expert Server PCs for your test and for your productive system.
A.38.1. Initial Installation of Expert

Prerequisites.
Expert for details.
3. Run Expert/OCC Setup as local administrator
4. Choose Option "User Defined" as setup type and choose from the following components
for your installation.
EHS Expert Management Service: needed, when you want to use the Service Administration in EHS (transaction cgsadm); available since SAP Enterprise PLM Extension 2.0.
The EHS management server is installed as a Microsoft Windows service and manages
the generation servers for the Windows Wordprocessor Integration (WWI) program and
the EHS Expert servers for the SAP EHS component by Remote Function Call (RFC)
from the SAP system.
Expert NT Service: Expert as Windows service:
EHS Expert Server: Expert as console program
EHS Expert Rule Editor: Rule Editor is needed, if you want to create your own rule files
Demo Rules: example rule files
EHS Open Content Connector: needs only to be installed if you want to use OCC and
Expert on this PC
Open Content Connector Samples
Recommended components (without OCC installation on this PC) are shown in the following
screenshot:

6. During the setup you can immediately maintain the entry for the EHS Management Server in
the configuration file SAPRFC.ini (see following screenshot). We recommend you structure
the name as follows: EHS_MGMT_<computer name of server>
187
SAP AG
How To ...
.
Sample entry from screenshot
Meaning
DEST=EHS_MGMT_XYZ
Name of destination of the Administration

Service. We recommend you structure the
name as follows: EHS_MGMT_<computer
name of server>
PROGID=EHS_MGMT_XYZ
Name of program ID (see how to setup a

RFC connection)
TYPE=R
R = Registration in R/3 (R presents registered RFC connection. This means that the
EHS Management Service logs itself onto
the system)
GWHOST=sma85
GWSERV=sapgw00
Gateway service: contains the string sapgw

and the system number
MANAGED=1
defines that this destination is an EHS-Management-Service
When you have installed EHS Expert successfully, a directory is created on your PC with the
name that you specified during installation (default name: C:\Program Files\EHS\Expert). This
directory contains all the relevant subdirectories and files.
The subdirectory RULES is the default directory for your sets of rules and already contains
sample sets of rules.
The subdirectory LOG is used to store log files for EHS Expert if log creation is activated.
The subdirectory BIN contains executable programs
A.38.2. Upgrading of older Expert versions

Expert for details.
2. Stop EHS Services on Expert Server
3. Run Expert/OCC Setup as local administrator
4. Choose Option "User Defined" as setup type and choose the appropriate components for
your installation.
5. Start EHS Services on Expert Server
188
SAP AG
How To ...
A.38.3. Implement Expert patches

1. Upgrade to latest EHS Expert
2. Stop EHS Services on Expert Server
3. Extract attached zip-file in subdirectory BIN
4. Start EHS Services on Expert Server
A.39. How to configure SAPRFC.INI

1. From the EH&S Expert installation directory (e.g. C:\Program Files\EHS\Expert), open the
subdirectory BIN and open the SAPRFC.INI file.
2. Add the following lines to the SAPRFC.INI file:
Sample entry
Meaning
; Expert Server
Comment line
DEST=EHS_EXPERT_TDG_01
Name of destination (the parameter with

which you call the program EHSEXPER.EXE
or EHSEXPSV.EXE
PROGID=EHS_EXPERT_TEST
Name of program ID (as used as program id

in the RFC connection)
TYPE=R
R = Registration in R/3
GWHOST=pntd01
GWSERV=sapgw00
Gateway service
RFC_TRACE=0
RFC trace initialization (0= no trace file, 1=

trace file). The trace file is normally not needed.
Note
You can use the SAPGUI entry to find the details for GWHOST and GWSERV:
GWHOST contains the SAP router string including the application server. GWSERV
contains the string sapgw and the system number
3. Save these entries.
A.40. How to configure EHS Expert Server using

To call EHS service administration choose in the SAP menu --> Logistics--> Environment,
Health and Safety --> Basic Data and Tools --> Tools WWI and EHS Expert Server Administration or use transaction cgsadm.
The system searches dynamically for all EHS management servers that are logged on to the
system and displays the PC names as the search results in the navigation tree.
Double-click a PC name. The EHS management server is called and a list of all WWI and
EHS Expert servers installed in the system is displayed.
189
SAP AG
How To ...
Choose in the menu Service --> Create --> EHS Expert Server
Choose a destination by using F4-help and enter a name a description for the EHS Expert
(in the example: EHS_EXPERT)
The system enters the following data:
The values for the selected destination in the RFC Parameters group box (Program ID,
Gateway host and Service)
A generated service key (<destination/system/sequential number) and an editable service
name with description in the General group box
190
SAP AG
How To ...
The SAPRFC.ini file will be updated automatically on the Expert Server PC using the Program ID "EHS_EXPERT_TEST" as PROGID and the Service "EHS_EXPERT_TDG_01"
as DEST .
Accept your entries.
The Expert Server will then immediately be started on the PC.
A.41. How to configure EHS Expert Server as a

Windows Service
Requirements
Your PC runs on the Windows NT or Windows 2000 operating system.
You have installed the EHS Expert server on your PC.
You have configured the EHS Expert server for a certain destination. (In the following, the
destination EHS_EXPERT_TDG_01 is used as an example).
Standard settings
The EHS Expert server as a Windows service consists of the file EHSEXPSV.EXE that is
automatically copied to the corresponding bin directory for Expert installation (for example, c:
\program files\EHS\Expert\bin). The bin directory should also contain the following three files:
The administration program SVCADMIN.EXE, which can be used to install, configure, and
check services
The program library WIN32SVC.DLL
The EHSSTART.EXE file to automatically start and monitor the WWI generation server or
EHS Expert server as a Windows service
Activities
1. Log on as local administrator to the PC
191
SAP AG
How To ...
2. Start the MS-DOS prompt and change to the bin directory for EHS Expert installation
3. Install the service by calling the EHSEXPSV file together with command line parameters as
follows: EHSEXPSV.EXE -I -N<name> -D<destination>.
Example:
EHSEXPSV.EXE -I -NTest -DEHS_EXPERT_TDG_01 installs the Windows service EHS
Expert Server (Test). The destination EHS_EXPERT_TDG_01 is used.
4. Make the settings that are specific to the application for the EHS Expert server as a Windows
NT service.
During the installation, for each service, a key is created with the name
EhsExpertSvc(<name>) under the main key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
Start REGEDIT.EXE via Start\Run\regedit.exe
Choose the key EhsExpertSvc(<name>)\Parameter.
Change the parameters if required.
Destination: name of logical SAP R/3 destination
Idle Time: (default value = 1000 ms)
InitialServerCount: Number of EHS Expert server threads that are created directly after
the service is started. (Default value = 1)
LogDirOptions: (Default value = 1 /F /P /E /L=clean.log)
Syntax: n [/F] [/P] [/E /L=<filename>]
The number n deletes all files whose creation date or change date is more than n
days ago (with 1 <= n <= 365)
/F If the parameter is set, the reference point for deleting is the creation date. If the
parameter is not set, the reference point for deleting is the date of the last access
or last change.
/P If the parameter is set, subdirectory structures are retained and only files are deleted. If the parameter is not set, everything below the current directory is deleted.
/E Logs the names of all files and directories that cannot be deleted owing to restricted
access rights. /L=<filename> Name of log file if parameter /E is set.
Examples:
1 /F /P /E /L=clean.log deletes all files whose creation date is more than a day ago
and log messages are created in the CLEAN.LOG file in the EHS Expert directory.
1 /P deletes all files whose change date is more than a day ago.
5. Configure the application log for Windows NT or Windows 2000.
Start the Windows event viewer (EVENTVWR.EXE).
Change the setting for the application log via Log -> Log settings to the option Overwrite
Events as Needed to prevent an overflow in the event viewer.
6. Test the service.
Start and stop the EHS Expert Server (Test) service using the SVCADMIN.EXE program
from the bin directory of the Expert installation or the Services control in Windows.
Call the EHS Expert Server (Test) from the SAP System.
192
SAP AG
How To ...
Use the event viewer to check whether the respective commands in the application log file
have been logged and whether the language-dependent texts for the events are displayed
in the detail view.
Check whether the service was started automatically on system startup by rebooting the
PC and calling the EHS Expert Server (Test) from the SAP System.
7. To remove an installed service, proceed as follows:
Log on to the PC with administrator rights.
Start the service administration program SVCADMIN.EXE from the bin directory for the
Expert installation.
If necessary, close the current service using the Control and configure services function.
Remove the service using the Uninstall services function.
A.42. How to configure EHS Expert Server as a

console program
To start the EHS Expert as a console program, you call the program EHSEXPER.EXE with
the parameter -D <Name of destination>.
For example: EHSEXPER.EXE -DEHS_EXPERT_TDG_01
If you copied the icons to your desktop when you installed the EHS Expert, change the parameter -D accordingly to the entry in your file SAPRFC.INI.
Alternatively, you can call the program on your front end using the menu command Start > Programs -> EHS Expert. The default parameter -D is here set to EHS_EXPERT. Therefore you have to change the parameter if you have defined another destination in your file
SAPRFC.INI (EHS_EXPERT_TDG_01 in the example)
A.43. How to add user-defined DG texts

User-defined dangerous goods texts are regulation-dependant and may be assigned to specific dangerous goods user-defined text profiles. The dangerous goods user-defined free texts
themselves are phrases, whereas those phrases written by the standard expert rule DangGoods are CED standard phrases delivered with the CED phrase library. If further dangerous
goods user-defined texts are required, additional phrases need to be created.
To specify dangerous goods user-defined text profiles, use transaction SPRO, choose SAP
Reference IMG and navigate through the activities tree to Environment, Health and Safety Dangerous Goods Management - Basic Data and Master Data - Common Settings - Specify
Profiles for User-Defined Dangerous Goods Texts:
Press F5 or select "New Entries"
Enter the respective DG regulation, a unique number for the profile and a description for
the profile
Specify the value assignment type the profile shall be used with (standard is
SAP_EHS_1022_042 provided with the EHS standard property tree)
(optional)
Select
the
function
module
used
for
output
conditions
(DG50_PRICOND_USRDEFTXT is delivered with the standard)
Save your settings
A.44. How to add a value assignment rating

193
SAP AG
How To ...
By assigning a rating to a value assignment, you specify who can access the data or on which
documents the data can be printed. Once a rating has been used in a productive system you
cannot delete it.
To add value assignment rating, go into the customizing using transaction SPRO and navigate
to Environment, Health and Safety -> Basic Data and Tools -> Additional Information for Value
Assignment -> Usage ->Specify Ratings.
Then press F5 or "New Entry" and enter the new ratings as well as the description and save
your entries.
A.45. How to load rule sets onto the Expert server

Each rule set consists at least of two files
the rule set itself = file with the extension .ruc
the mapping database = file with the extension .mdb
Some rule sets are delivered with an additional files containing the external tables (file with the
extension .mdb) or additional rules in files with extension .ruc
All the files need to be copied on the Expert Server PC.
You can copy the files by using EHS Service Administration or by connecting to the Expert
Server PC directly.

In transaction cgsadm choose the Expert Server PC and transfer the files as described in the
following steps
194
SAP AG
How To ...
1. Choose in the menu Utilities --> Transfer File to Server
2. Choose all files to be transferred
3. Choose the path on the Expert Server PC
NOTE:
You will get the following screen and you can choose the path Rules for the files to be
transferred.
4. Press save and the files will be copied to the Expert Server PC
Direct copy
Connect to the Expert Server PC and copy all files in the RULES subdirectory of the Expert
installation.
A.46. How to register rule sets

All Expert rule sets have to be registered on the Expert Server PC. You can do this in the SAP
system using EHS Service Administration or directly on the Expert Server PC with the help of
the Expert Admin Tool. Some rule sets uses additional settings, e.g. IgnoreWarnings. These
additional settings could not be set using EHS Service Administration.
using EHS Service Administration

In transaction cgsadm go to the Expert Server PC and select the Expert Server. The Expert
Server has to be started and can then be edited
195
SAP AG
How To ...
1. Go in Edit mode (Menu Service Change <-> Display or correspondent icon
2. Choose the tab page Application Parameters
3. Click on icon new page (Append row)
4. Insert the name of the rule set (as given in descriptions of the rule set) and Set of Rules
File and the Mapping File.
Set of Rules Name = ZEXP_GHS, Set of Rules File = C:\Programme\EHSExpert\Rules
\GHS_V1-6.ruc, Mapping File = C:\Programme\EHSExpert\Rules\GHS_V1-6.mdb
5. Save your entries (Menu Service --> Save)
using Expert Admin Tool

Logon the Expert Server PC and Start the program Expert Admin (via Start --> Programs -->
EHS or by calling the program ExpertAdmin.exe in the bin directory of the Expert installation.
1. Add a new instance by pressing
2. Choose the name of the rule set
Name = ZEXP_GHS, Rule File = GHS_V1-6.ruc, Mapping Database = GHS_V1-6.mdb
3. Save you settings by Apply
196
SAP AG
How To ...
A.47. How to execute rules

Procedure
1. In the SAP system, execute one of the following procedures to determine specifications for
which you want to determine secondary data
searching manually for specifications
executing queries
loading sets of hits
A set of specifications appears in the form of a hit list.
2. In the hit list, select the specifications you require and choose Utilities -> Secondary Data
-> Determination.
The Determine secondary data dialog box appears.
3. Choose the EHS Expert user exit by double-clicking.
If you have set the parameter EXPERT_PARAMETER_CHANGE_MODE to S for the
EHS Expert user exit in Customizing for Basic Data and Tools, the SAP system displays
the Determine secondary data dialog box in display mode when secondary data determination is started.
If you have set the parameter EXPERT_PARAMETER_CHANGE_MODE to E for the
EHS Expert user exit in Customizing for Basic Data and Tools, you can edit the environment parameters in the Determine secondary data dialog box when secondary data determination is started. The environment parameters set in Customizing are displayed as
default values. Enter or change the environment parameters as required.
197
SAP AG
How To ...
If you have set the parameter EXPERT_PARAMETER_CHANGE_MODE to H for the
EHS Expert user exit in Customizing for Basic Data and Tools, the SAP system does not
display the Determine secondary data dialog box when secondary data determination is
started.
Result
Using the rules in the set of rules, the EHS Expert determines data for the selected specifications and writes it to the database. When writing the data, the EHS Expert uses the data
you specified in the IMG activity Manage User Exits under the corresponding parameters for
the EHS Expert user exit for rating, validity area, data provider, and data origin, or the data
changed manually in the Expert: Parameter Entry for Data Determination dialog box.
The save mode specified in Customizing or in this dialog box determines whether existing data
records are overwritten, or whether new data records are just added. If the newly determined
data is identical to the data determined at an earlier stage, the system does not delete or create
data if save mode I is not set.
You can use and edit the data that was written to the database by the EHS Expert in the same
way as data entered manually.
Note
Here you should note that if during subsequent manual processing the data origin and
data provider differ from the corresponding parameters of the EHS Expert run, a new
value assignment instance is created in a new EHS Expert run even if the values
then match.
A.48. How to display the Explanation Component

Some of the SAP EHS Regulatory Content - expert rules for substance and mixture classification are delivered with explanations showing intermediate results to be able to trace how the
results determined by the rule were dedicated.
To activate the explanatory tool for an Expert rule, the following steps have to be performed:
Additional user-exit parameters have to be set according to the Expert rule's functional description. The default settings are:
EXPERT_EXPLANATION_SAVE = X (invokes the explanation)
stored at)
EXPERT_EXPLANATION_TEXTCAT = EX (defines the user-defined free text category
to be used for the XML stream)
(optional) EXPERT_EXPLANATION_DISPLAY = X (has the explanation displayed automatically after the rule set run)
Create the user-defined free text category defined above (EX in the default case).
Make sure that the characteristic defined above (default: SAP_EHS_0101_002_RULESET)
is not with phrases and remove the phrase set assignment if necessary. Please note that the
phrase set assignment may be made automatically with standard property tree upgrades;
in this case this has to be undone manually!
198
SAP AG
How To ...
If you want to have the current date written with the explanation each time you run the Expert
rule, the following parameters are required in addition:
(optional) EXPERT_WRITE_RUN_DATE = X (invoking saving the date)
(optional)
=
SAP_EHS_0101_002_RUN_DATE (characteristic where the date is stored)
To display an explanation, create a hit-list of the substance(s) whose explanation shall be
shown and choose in the menu Utilities -> Secondary Data -> Log.
Open the tree structure with a mouse click.
If you are using an EHS 2.7B system with the downgrade for the explanation choose the menu
item specified with the downgrade's installation.
Some of the standard expert rules use the sub rule GS_IDENT, which has an external table
GS_ident_externvalues.mdb where some parameters for the explanation can be customized
individually. For details on these parameters please refer to the rule set's functional description.
A.49. How to generate Log Files

The Expert logging can be activated directly on the Expert server with the help of the Expert
Admin tool or, if the Expert server is configured accordingly, with the EHS Administration Service (transaction cgsadm).
For each rule set instance that shall be logged the logging needs to be activated separately;
this is especially important when sub rules are used, i.e. for DangGoods and NotStat.
To find out which instance is called for a given rule set, please check the user-exit parameter
EXPERT_RULE_SET, or refer to the documentation for the sub rules used.
Using EHS Service administration

1. Start EHS Service administration (transaction cgsadm), click on the Expert Server PC and
choose the Expert Server
2. Change to edit mode (via Menu Service --> Change <-> Display)
3. Activate logging
To activate the logging please go to the Application Parameters tab page and tick the "Logging" flag at the rule set instance to enable the RFC logging, and set the log level to 5 to
set the so-called Exp logging to an appropriate level of detail.
199
SAP AG
How To ...
Caution
Please do not forget to deactivate the logging afterwards, since an activated log level
has a negative impact on the Expert's performance.
4. Run the rule set in EHS
5. Download the files EXP*.log and RFC*.log from the logging directory within the EHS Service
Administration
You can download the files via the menu: Utilities --> File from Server
Choose the logging directory on the Expert Server PC; default is the directory LOG in the
Expert installation directory
NOTE:
Mark the files to be transferred and choose the storage path on you computer afterwards
Using ExpertAdmin Tool

1. Logon the Expert Server PC
2. Activate logging
To activate the logging please tick the "Log Data Exchange" flag at the rule set instance to
enable the RFC logging, and set the log level to 5 to set the so-called Exp logging to an
appropriate level of detail. (see screenshot)
3. Run the rule set in EHS
200
SAP AG
How To ...
4. Download the files EXP*.log and RFC*.log from the logging directory (the logging directory
can be specified, default is the directory LOG in the Expert installation directory.)
Caution
Please do not forget to deactivate the logging afterwards, since an activated log level
has a negative impact on the Expert's performance.
A.50. How to adjust external table values

In addition to the files for the rule sets (ruc files and the mapping data base) some rule sets
provide a separate MS-Access data base
The purpose of it is to allow the user to modify the preconfigured data according to the needs
of the customers.
These external parameters are interpreted by the rule set as IN facts.
It is recommended to install this data base in the same directory on the Expert server as the
rule files.
If this external data base is installed somewhere else, the linkage between the rule set and the
external data base must be maintained by defining the file path in the mapping tables.
The
below
mentioned
mapping
information
refers
to
the
OSHA_Hazard_Determination_externvalues.mdb but the approach to adjust the mapping is
the same for all rule sets.
201
SAP AG
How To ...
Example: Record-Mapping Installation of the external data base in the same directory as the
rule set.
Internal_id
External_id
ext_target_organ T:Target_Organ/OSHA_Hazard_Determination_externvalues.mdb
Example: Record-Mapping Full declaration of the path for the external data
Internal_id
External_id
ext_target_organ T:Target_Organ/C:\Program Files\EHS\Expert\Rules

Example: Fact-Mapping Installation of the external data base in the same directory as the
rule set.
Internal_id
External_id
i_switch_harmful T:harmful_check;Switches/
OSHA_Hazard_Determination_externvalues.mdb
Example: Fact-Mapping Full declaration of the path for the external data
Internal_id
External_id
i_switch_harmful T:harmful_check;Switches/C:\Program Files\EHS\Expert\Rules

A documentation of the adjustable parameters could be obtained from the respective functional
descriptions of the rule sets.
A.51. How to adjust the Group Mapping

The composition mapping table contains the regulations for mapping compositions in the set
of rules to value assignment types of the category composition in EHS.
Table Fields in the Composition Mapping Table (ExpGroupMap)
Table Field
Meaning
Internal_Id
Name of the composition in the set of rules. This field uniquely identifies
the composition in the set of rules.
External_Id
Name of the assigned value assignment type of the category composition

in EHS
Descriptions
Description text for the composition
Options
A.52. How to setup identification listings

Setting up identification listings is an IMG activity.
Please choose transaction SPRO , then choose SAP Reference-IMG (F5).
Go to: Environment, Health and Safety - Basic Data and Tools - Specification Management Specification Master - Check Identification Listings
202
SAP AG
How To ...
Add the required Identification Listings via "New Entry" including a header, add the required
identifiers to the definition and save.
A.53. How to import report templates

First upload the files dat-files (for example SDS_EU_2010_1.dat ) and doc-files on the application server using transfer format BIN (=>transaction CG3Z).
If a UNIX system is used, choose corresponding dat file with ending _unix.dat and rename it
to SDS_x_y.dat.
Then import the dat-file using transaction CG34 "Import Report Templates" or go to Logistics > Environment, Health and Safety -> Basic Data and Tools -> Tools -> Data Transfer -> Import
Report Template
The following settings need to be used:
File with path: <path on application server and file with ending .dat>
Character standard: MS-NT
Choose function "Check file". The SAP System checks if the data can be transferred correctly
from the transfer file and matches up the symbols.
Check Symbol Matchup to make sure all symbols are available on system in the correct way.
All entries in the system column must have symbol names. If they do not, check if symbol
generation was carried out on your system.
"Transfer/Start Time" will transfer (import) your file.

WWI will automaticly open the new template document. Check the template by clicking on the
check-button and save it.
A.54. How to create generation variant

Using transaction CG2B you can maintain generation variants for every template.
Or you go to Logistics -> Environment, Health and Safety -> Basic Data and Tools -> Report
Definition -> Edit Generation Variants
203
SAP AG
How To ...
In the generation variant the main validity area is defined under "Validity Area"; the area from
which the template will draw its data.
The option "Usage check" is utilized to control the way in which the usages are compared.
There are four options to select: 0, 1, 2 and 3.
If you do not specify a value, the SAP System uses the value 0 as default.
Value 0: The usage is appropriate if - with the same rating used - the generation variant validity
area that is expanded to its countries and regions is the same as or is a subset of the expanded
validity area of the usage with which it is to be compared.
Example: Generation variant: DE Value assignment usage: REG_EU If a safety data sheet is
created for Germany, value assignment instances are also taken into account that are valid
for the validity area REG_EU.
Please see the SAP Help function for all the details on the option.
Under "Rating/Validity", additional validity/language combinations can be maintained:
These validity areas or languages must be addressed directly by the WWI coding in the
template (G-Repeating-Group) to be effective. By the use of these Rating/Validity options, it
is for example possible to give out special phrases in English on a template in Chinese or
Spanish.
204
SAP AG
Appendix B. Technical Settings

Property Tree Packages
In general, this Appendix contains all relevant information to implement the last property tree
package delivered with the last SAP EHS Regulatory Content Update.
The last SAP EHS Regulatory Content Update is 2011-1. No enhancements to existing properties or no new properties were defined for this update. Therefore, no property tree package
2011-1 was created.
In order to make use of the latest Expert Rules, Substance Lists and Reference Data (delivered with update 2011-1) the contents of the already existing property tree packages such
as 2010-2 Product Safety, 2010-1 Product Safety etc have to have been implemented before
implementing the update 2011-1. This should have already happened with the last SAP EHS
Regulatory Content Updates. If the property tree STANDARD is up to date, no property tree
package has to be installed in the 2011-1 update process.
The existing property tree packages which were delivered in the past are summarized in Chapter 2.
B.1. Settings to implement the last SAP EHS Management Property Tree Package Product Safety
No property tree package is delivered with the 2011-1 update. Therefore, no transports have
to be installed if the property tree STANDARD is up to date, that is if ERP 6.0 EHP6 or all
packages up to 2010-2 were installed.
B.2. Overview about existing property tree packages delivered in the past
The existing property tree packages, which were delivered in the past, are summarized in the
following tables:
General Information
Order Property tree package
number
Update from EHS Release -> to

EHS Release
SAP EHS Property Tree Package 2.7B/3.2
EHS 2.7B -> EHS 3.2
SAP EHS Property Tree Package 3.2/2004
EHS 3.2 -> ERP 5.0 (= ERP 2004)
SAP EHS Property Tree Package 2004/2005 ERP 5.0 (= ERP 2004) -> ERP 6.0 (=
ERP 2005)
SAP EHS Property Tree Package ERP 6.0

EnhP 3 Product Safety
ERP 6.0 (= ERP 2005) -> ERP 6.0

EhP3
SAP EHS Property Tree Package 2007-2

Product Safety
ERP 6.0 EhP3 -> ERP 6.0 EhP5 (first

part)
205
SAP AG
Technical Settings Property Tree Packages

Product Safety
ERP 6.0 EhP3 -> ERP 6.0 EhP5

(second part)
does
not
exist

Product Safety
No changes were made for 2008-2
SAP EHS Property Tree Package 2009-1 ERP 6.0 EhP3 -> ERP 6.0 EhP5
Product Safety
(third part)
SAP EHS Property Tree Package 2009-2 ERP 6.0 EhP3 -> ERP 6.0 EhP5
Product Safety
(fourth part)
SAP EHS Property Tree Package 2010-1 with ERP 6.0 EhP5 -> ERP 6.0 EhP6 (first
2010-1A Product Safety
part)
10
SAP EHS Property Tree Package 2010-2 ERP 6.0 EhP5 _> ERP 6.0 EhP6
Product Safety
(second part)
does
not
exist
SAP EHS Property Tree Package 2011-1 No changes were made for 2011-1
Product Safety
SAP EHS Property Tree Package 2.7B/3.2

Order File name
of import
Description
NewEHS32Props.zip
Package with descriptors in English

and German
PropTree_27B_Extended_Characteristics_
VALUES_NS_UNIT.zip
Additional package with 8 extended

characteristics
French_Descriptors_for_package_
NewEHS32Props_20060518.zip
French descriptors
2.7B/3.2
for
package
SAP EHS Property Tree Package 3.2/2004

Order File name
of import
Description
Changes_Property_Trees_EHS_32_2004
_041115.zip

and German
French_Descriptors_for_package_
EHS_32_2004_20060530.zip
French descriptors for package EHS

3.2/2004
SAP EHS Property Tree Package 2004/2005

Order File name
of import
1
Description
_041115.zip

and German
206
SAP AG
SAP EHS Property Tree Package ERP 6.0 EnhP 3 Product

Safety
Order File name
of import
1
Description
_Product_Safety_20070601b.zip

and German
SAP EHS Property Tree Package 2007-2 Product Safety

Order File name
of import
1
Description
Changes_EHS_Property_Trees_2007-2_
Complete_20080224.zip

and German

Order File name
of import
1
Description
Changes_EHS_Property_Trees_2008-1_
20081001.zip

and German

Order File name
of import
1
Description
EHS_Property_Tree_Package_2009-1_
20091108.zip

and German

Order File name
of import
1
Description
20091108.zip

and German
SAP EHS Property Tree Package 2010-1 and 2010-1A Product Safety
Order File name
of import
Description
207
SAP AG
PS_V1_20100616.zip
Packages with descriptors in English

and German
1A_PS_V1_20100827.zip

Order File name
of import
1
Description
PS_V1_20101116.zip
208

and German
SAP AG
Appendix C. Technical Settings

Multilanguage Phrase Library 2011-1
This annex contains all relevant information to implement the SAP EHS Regulatory Content multilanguage phrase library for hazard communication.
The settings are divided into the several packages.
C.1. Settings to implement the Multilanguage

Phrase Library (Standard)
C.1.1. File Overview
The following files are included in the delivery (additional set of files for Unix application servers
containing appendix "_unix" in the filename also included; files for special language codes
instead of Z8 and Z9 not included but available on request). We recommend to use the Unicode
files when possible to avoid character conversion errors with the non-Unicode files.
Standard
File name
Description
01_documents
CED_ReleaseNote_2011-1.pdf
Release Note for current version
CED_Changes_2011-1.xls
Excel file with complete scope of EN phrases in previous and current version for a quick information what has
changed in the latest release; table 2 contains obsolete
pset assignments that should be deleted
Phrase_Services_Proposals.xls
Proposal template for customer suggestions
02_phrases_windows / 03_phrases_unix
ced_2011-1_standard_unicode_
complete.dat
Phrase import file including all phrases in all standard

languages except Mexican Spanish, US English (Z8),
and Brazilian Portuguese (Z9) for fast processing in Unicode systems
ced_2011-1_standard_unicode_
update.dat
Phrase import file including revised and new phrases

in all standard languages except Mexican Spanish, US
English (Z8), and Brazilian Portuguese (Z9) for fast processing in Unicode systems
ced_2011-1_brazilian_Z9_
complete.dat
Phrase import file with all phrases in Brazilian Portuguese via Z9 customer correspondence language
ced_2011-1_brazilian_Z9_
update.dat
Phrase import file including revised and new phrases in

Brazilian Z9
ced_2011-1_mexican_unicode_
complete.dat
Phrase import file with all phrases in Mexican Spanish
ced_2011-1_mexican_unicode_
update.dat

Mexican Spanish
209
SAP AG
Technical Settings Multilanguage Phrase Library 2011-1

ced_2011-1_usenglish_Z8_
complete.dat
Phrase import file with all phrases in US English via Z8

customer correspondence language
ced_2011-1_usenglish_Z8_
update.dat

US English Z8
Non-Unicode files with separate files per codepage. These files are not needed if you
use the Unicode files
ced_2011-1_west_complete.dat
Phrase import file with phrases in Western European

languages: English, French, German, Spanish, Italian,
Portuguese, Dutch, Danish, Swedish, Finnish, Norwegian
ced_2011-1_central_complete.dat
Phrase import file with phrases in Central-European languages: Croatian, Czech, Hungarian, Polish, Romanian, Serbian (SH), Slovenian, Slovakian
ced_2011-1_baltic_complete.dat
Phrase import file with phrases in Baltic languages: Estonian, Latvian, Lithuanian
ced_2011-1_cyrill_complete.dat
Phrase import file with phrases in Russian, Bulgarian

and Ukrainian language
ced_2011-1_greek_complete.dat
Phrase import file with phrases in Greek language
ced_2011-1_turkish_complete.dat
Phrase import file with phrases in Turkish language
04_psets_windows / 05_psets_unix
ced_2011-1_pset_new.dat
New phrase set assignments for ERP6.0 EhP4 properties tree
ced_2011-1_pset_complete.dat
Complete phrase set assignments for ERP6.0 EhP4

properties tree (all assignments to prior properties tree
packages are included in this file as well); this part includes all assignments from previous releases and the
new release
C.2. Settings to implement the Multilanguage

Phrase Library (APA)
C.2.1. File Overview
The following files are included in the delivery (additional set of files for Unix application servers
containing appendix "_unix" in the filename also included). We recommend to use the Unicode
files when possible to avoid character conversion errors with the non-Unicode files.
Asia Pacific
File name
Description
01_documents
CED_ReleaseNote_2011-1.pdf
Release Note for current version
CED_Changes_2011-1.xls
Excel file with complete scope of EN phrases in previous and current version for a quick information what has
changed in the latest release; table 2 contains obsolete
pset assignments that should be deleted
210
SAP AG

Phrase_Services_Proposals.xls
Proposal template for customer suggestions
02_phrases_windows / 03_phrases_unix
ced_2011-1_ap_unicode_complete.dat
Phrase
import file including all phrases in all AP languages for fast processing in Unicode systems
ced_2011-1_ap_unicode_update.dat

all AP languages for fast processing in Unicode systems
Non-Unicode files with separate files per codepage. These files are not needed if you
use the Unicode files. For technical reasons Hindi, Vietnamese and Tagalog are only
available as Unicode file.
ced_2011-1_ap_latin_complete.dat
Phrase import file for Latin languages including English,

Indonesian and Malay
ced_2011-1_ap_tchin_complete.dat
Non Unicode version of the import file for Traditional

Chinese. This may include characters that are not printed correctly within SAP EHS.
ced_2011-1_ap_schin_complete.dat
Phrase import file including Simplified Chinese phrases
ced_2011-1_ap_japanese_complete.dat
Phrase
import file including Japanese phrases
ced_2011-1_ap_korean_complete.datPhrase
import file including Korean phrases
ced_2011-1_ap_thai_complete.dat
Phrase import file including Thai phrases
04_psets_windows / 05_psets_unix
ced_2011-1_pset_new.dat
New phrase set assignments for ERP6.0 EhP4 properties tree
ced_2011-1_pset_complete.dat
Complete phrase set assignments for ERP6.0 EhP4

properties tree (all assignments to prior properties tree
packages are included in this file as well); this part includes all assignments from previous releases and the
new release
C.3. General Settings

C.3.1. Phrase Groups
The phrases of the CED Phrase Library are divided into the following phrase groups analogous
to the chapters of an European safety data sheet in the version before REACh 2007. Change
of the sections 2 and 3 did not result in change of the phrase groups in the CED library as this
would have caused changes of phrase keys as well and therefore was not acceptable.
Phrase group
Description
00.00
REF.
01.00
IDENTIFICATION OF THE SUBSTANCE OR

PREPARATION
02.00
COMPOSITION / INFORMATION ON INGREDIENTS
03.00
HAZARDS IDENTIFICATION
04.00
FIRST-AID MEASURES
05.00
FIRE-FIGHTING MEASURES
211
SAP AG

06.00
ACCIDENTAL RELEASE MEASURES
07.00
HANDLING AND STORAGE
08.00
EXPOSURE CONTROLS /PERSONAL PROTECTION
09.00
PHYSICAL AND CHEMICAL PROPERTIES
10.00
STABILITY AND REACTIVITY
11.00
TOXICOLOGICAL INFORMATION
12.00
ECOLOGICAL INFORMATION
13.00
DISPOSAL CONSIDERATIONS
14.00
TRANSPORT INFORMATION
15.00
REGULATORY INFORMATION
16.00
OTHER INFORMATION
17.00
FURTHER MSDS - INFORMATION
18.00
CEFIC Phrases
19.00
RESERVE
20.00
MSDS - HEADER
US_ANSI
SDS Phrases North America
C.3.2. Name spaces

C.3.2.1. Phrase keys
The assignment of phrase keys is based on a content dependent systematic.
Example: N05.00314600 In the event of fire, cool tanks with water spray.
Systematic meaning of the phrase key:
N05.00314600
N Normal phrase for substance evaluation
05.00 Hint on phrase group 05.00: "Fire-fighting measures
3 Sub group 3 : "Special information for fire fighters
14600 unique ending of the phrase key
C.3.2.1.1. Name spaces concerning substance evaluation phrases (-> allocated to
phrase sets)
N* MLL-CED-Phrases for substance evaluation
Z* EHS-CED phrases for substance evaluation
U* SDS phrases North America
* Structure for the phrase key
Phrase Group
01.00
Sub Group
Meaning
Identification
212
SAP AG

1xxxx
Product name related
2xxxx
Company name related
3xxxx
Emergency contact related
4xxxx
5xxxx
Descriptor categories (SU, ERC, PC) for exposure scenarios
6xxxx
Process descriptors (PROC) for exposure scenarios
7xxxx
Article categories (AC) for exposure scenarios
0xxxx
Industry specific categories for exposure scenarios
02.00
Composition / information on Ingredients

0xxxx
Product type, substance, preparation, intermediate
2xxxx
Chemical nature
9xxxx
Preparation description and product uses
03.00
Hazards Identification
7xxxx
R phrases
0xxxx
04.00
First aid measures

1xxxx
Inhalation
2xxxx
Skin
3xxxx
Eye
4xxxx
Ingestion
5xxxx
Physician
6xxxx
Protection of first aides
0xxxx
General phrases
05.00
Fire fighting measures

1xxxx
Suitable / unsuitable extinguishing media
2xxxx
Specific Hazards from burning
3xxxx
Special information for fire fighters
0xxxx
Further information
06.00
Accidental release measures

1xxxx
Personal precautions
2xxxx
Environmental precautions
3xxxx
Methods for clean up
0xxxx
Further information
07.00
Handling and storage

1xxxx
Handling - Technical measures / precautions
2xxxx
Handling - Save handling advice
3xxxx
Storage-technical measures / storage precautions
213
SAP AG

4xxxx
Storage - incompatible materials
5xxxx
Storage - packing material
0xxxx
Further information
08.00
Exposure control / personal protection

1xxxx
Engineering methods to reduce exposure
2xxxx
Control parameters
3xxxx
Personal protection - respiratory
4xxxx
Personal protection - Hand
5xxxx
Personal protection - Eye
6xxxx
Personal protection - Skin / Body
7xxxx
Hygiene measures
0xxxx
Further information
09.00
Physical and chemical properties

1xxxx
Form
2xxxx
Colour
3xxxx
Odour
4xxxx
Other physical chemical properties
5xxxx
pH
6xxxx
Changes in state
7xxxx
Decomposition
8xxxx
Flash point
9xxxx
Solubility
0xxxx
Further information
10.00
Stability and reactivity

1xxxx
Conditions to avoid
2xxxx
Materials to avoid
3xxxx
Hazardous decomposition products
0xxxx
Further information
11.00
Toxicology information
1xxxx
Acute toxicity
2xxxx
Local effects
3xxxx
Chronic / long term effects
4xxxx
Specific effects e. g. mutagenicity
5xxxx
Symptoms / organs / useful expressions
0xxxx
Further information
12.00
Ecological information
1xxxx
Possible effects, environmental fate etc.
2xxxx
Ecotoxicity
214
SAP AG

0xxxx
13.00
Further information
Disposal considerations
1xxxx
Waste from residues / unused products
2xxxx
Contaminated packaging
0xxxx
Further information
14.00
Transport information
1xxxx
2xxxx
Proper Shipping names English only (unnecessary

with the EHS2.2-tree)
0xxxx
Labels IMO / IATA

Further information
15.00
Regulatory information
1xxxx
International regulatory sentences
2xxxx
Symbols
3xxxx
R phrases EC
4xxxx
R phrases others
5xxxx
S phrases EC
6xxxx
S phrases other
0xxxx
Further information
16.00
Other information
1xxxx
Recommended use
2xxxx
Recommended restrictions
0xxxx
Further information
18.00
CEFIC Phrases
20.00
SDS Annex Phrases
C.3.2.1.2. Name conventions concerning header-phrases (-> non - allocated phrases)

These phrases are headers and sub headers of the MSDS chapters and names of properties
and characteristics.
H* MLL-CED-Header
E* EHS-CED-Header
C.3.2.1.3. Name conventions for customer specific phrases
P* customer specific permutation of CED phrases
X* and Y* customer specific newly added phrases
=> these phrases may then be allocated to phrase sets provided that they are part of the active
library
C.3.3. Language/Codepages
215
SAP AG

Language
group
Language
ISO-Norm
character
set
SAP
R/3 MiMiFont
(MiStancrosoft-Code-crosoft-Code-crosoft)
in
dard-Code- page
page
in which phraspage (based
SAP R/3
es are supon
ISOplied by CED
Norm)
Western
European
English
ISO 8859-1 1100
1252 (iden- 110

tical
with
R/3 Codepage 1100)
ARIAL.TTF
ISO 8859-7 1700
1253
1704
ARIAL
GREEK.TTF
ISO 8859-2 1401
1250
1404
ARIAL
CE.TTF
ISO 8859-5 1500
1251
1504
ARIAL
CYR.TTF
Danish
Dutch
Finnish
French
German
Italian
Norwegian
Portuguese
Spanish
Swedish
Brazilian
US English
Greek
Greek
Central Eu- Croatian

ropean
Czech
Hungarian
Polish
Romanian
Slovakian
Slovenian
Serbian
Cyrillic
Russian
Bulgarian
Ukrainian
216
SAP AG

Turkish
Turkish
ISO 8859-9 1610
1254
1614
ARIAL
TUR.TTF
Baltic
Estonian
ISO 8859-4 1900
1257
1904
ARIAL
BALTIC.TTF
ISO 8859-1 110
1252
1100
ARIAL.TTF
Latvian
Lithuanian
AP-Latin
English
Indonesian
Malay
AP-TChin
Traditional
Chinese not all characters supported!
8300
950 (BIG 5) 8300
mingliu.ttc
AP-SChin
Simplified
Chinese
8400
936
(GB 8400
2312)
Simsun.ttc
APJapanese
Japanese
8000
932
8000
msmincho.ttc
AP-Korean Korean
8500
949
8500
batang.ttc
AP-Thai
Thai
8600
874
8600
tahoma.ttc
Unicode
Canadian
French
4103
ARIAL MS
Unicode
French
Mexican
Spanish
Hindi (AP)
Vietnamese
(AP)
Traditional
Chinese
(AP)
Philippine
(Tagalog)
C.3.4. Language keys

Language keys of Western European phrase translations
Phrase language
Language keys for phrase im- Language key presentation in

port
phrase administration
English
EN
217
SAP AG

Danish
DA
Dutch
NL
Finnish
FI
French
FR
German
DE
Greek
EL
Italian
IT
Norwegian
NO
Portuguese
PT
Spanish
ES
Swedish
SV
Language keys of other phrase translations

Phrase language

port
Bulgarian
BG
Croatian
HR
Czech
CS
Estonian
ET
Hungarian
HU
Latvian
LV
Lithuanian
LT
Polish
PL
Romanian
RO
Russian
RU
Slovakian
SK
Slovenian
SL
Turkish
TR
Ukrainian
UK
Brazilian Portuguese
&
Z9
Canadian French
US English
3F
;
Z8
Mexican Spanish
Serbian
1X
d
SH
Language keys of Asia Pacific translations

Phrase language

port
Indonesian
ID
218
SAP AG

Malay
MS
Simplified Chinese
ZH
Traditional Chinese
ZF
Japanese
JA
Korean
KO
Thai
TH
Hindi
HI
Philippine (Tagalog)
P1
Vietnamese
VI
219
SAP AG
Appendix D. Technical Settings

Substance Lists and Reference Data
2011-1
This annex contains all relevant information to implement the SAP EHS Regulatory Content
- substance lists and reference data.
The settings are divided into separate chapters for the different regulatory data packages.
D.1. Settings to implement the Substance Lists

and Reference Data (Product Safety)
D.1.1. File Overview
The Substance Lists and Reference Data installation package for Product Safety includes the
following files:
Files
File Description
0-Documentation
PS_Data_ReleaseNote _2011-1.pdf
Latest Substance Lists and Reference Data Release

Note for Product Safety
CLEO_ContentReport_AP.pdf
Content Report Asia-Pacific Data
CLEO_ContentReport_EU.pdf
Content Report European Data
CLEO_ContentReport_Americas.pdf
Content Report American Data
CLEO_ContentReport_
Inventories.pdf
Content Report Inventories Data
CLEO_PS_Training_EN.ppt
SAP EHS Regulatory Content Training Workshop Presentation
1-OCC
Info file on how to obtain OCC
readme.txt
2-Customizing (Only for initial implementation - see Update Guide for changes to
customizing)
R900552.TD8
and K900552.TD8
Substance Lists and Reference Data - Product Safety Customizing transport (User Exit, Data Origin, Free Text
Types, passive Phrase Library, identifier types, regulatory lists and literature sources) (Unicode)
R900554.TD8
and K900554.TD8
Substance Lists and Reference Data - Product Safety Customizing transport Validity Areas (Unicode)
R902764.TD4
and K902764.TD4
Substance Lists and Reference Data - Product Safety Customizing transport (User Exit, Data Origin, Free Text
Types, passive Phrase Library, identifier types, regulatory lists and literature sources) (Non-Unicode)
R902766.TD4
and K902766.TD4
Substance Lists and Reference Data - Product Safety Validity Areas Customizing transport (Non-Unicode)
220
SAP AG
Technical Settings Substance

Lists and Reference Data 2011-1
Files
File Description
2A-Hitlist
R900343.TD8
and K900343.TD8
Workbench transport of improved extended search

functionality
3-Phrases\Unicode_Unix / 3-Phrases\Unicode_Win
cleo_2011-1_unicode.dat
Unicode phrase import file (all languages)
cleo_2011-1_pset_unicode.dat
Unicode phrase set assignment import file
cleo_2011-1_canadianfrench_
unicode.dat
Unicode Phrase import file Canadian French
cleo_2011-1_usenglish_
unicode.dat
Unicode Phrase import file US English
cleo_2011-1_mexican_spanish_
unicode.dat
Unicode Phrase import file Mexican Spanish
cleo_2011-1_brazilian_unicode.datUnicode
Phrase import file Brazilian Portuguese
3-Phrases\MS-NT_Unix / 3-Phrases\MS-NT_Win
cleo_2011-1_west.dat
Phrase import file Western European languages
cleo_2011-1_central.dat
Phrase import file Central European languages
cleo_2011-1_cyrillic.dat
Phrase import file Cyrillic European languages
cleo_2011-1_baltic.dat
Phrase import file Baltic European languages
cleo_2011-1_brazilian.dat
Phrase import file Brazilian Portuguese
cleo_2011-1_greek.dat
Phrase import file Greek
cleo_2011-1_japanese.dat
Phrase import file Japanese
cleo_2011-1_korean.dat
Phrase import file Korean
cleo_2011-1_simplchinese.dat
Phrase import file Simplified Chinese
cleo_2011-1_tradchinese.dat
Phrase import file Traditional Chinese
cleo_2011-1_thai.dat
Phrase import file Thai
cleo_2011-1_turkish.dat
Phrase import file Turkish
cleo_2011-1_usenglish.dat
Phrase import file US English
cleo_2011-1_pset.dat
Phrase set assignment import file
4-CLEO Database
CLEO_PS_region_2011-1.exe
Substance Lists and Reference Data - Product Safety Database setup/update program
5-Mapping
td_cleo.mdb
Substance Lists and Reference Data - Product Safety

- Mapping Database
6-UpdateTools
cleo_update_2011-1.txt
Update file to create hit list of changed list substances
cleo_new_group_assignments
_2011-1.txt
Update file to create hit list substances with new group

assignments
cleo_simulation.xltm
Template for simulation (MS Excel 2007)
cleo_simulation.xlt
Template for simulation (MS Excel 97- 2003)
221
SAP AG

D.1.2. User Exit Settings

The following settings are proposed for the user exit:
Standard Value
EXPERT_ADD_PARAM_1
headerurl=<path
to
CLEO
PS
DB>\PS_DB
\header.xml
EXPERT_ADD_PARAM_2
usernameurl=x
EXPERT_ADD_PARAM_3
passwordurl=x
EXPERT_CALL_ONCE
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_OCC
EXPERT_READ_RATING
EXPERT_RULE_SET
CLEO_PS
EXPERT_TAB_FIELD_1
<subid>
EXPERT_TAB_FIELD_2
EXPERT_TAB_FIELD_3
EXPERT_TAB_FIELD_4
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
TECHNIDATA
REG_WORLD
D.1.3. Other Settings

The following customizing settings are necessary:
Customizing Setting
Value
Data Origin
TECHNIDATA
Phrase Library
TDCLE
User defined text type
OCCUNQID (OCC unique record ID)
NOL (name on list)
D.2. Settings to implement the Substance Lists

and Reference Data for Dangerous Goods
222
SAP AG

D.2.1. File Overview

The Substance Lists and Reference Data installation package for Dangerous Goods includes
the following files:
Files
File Description
0-Documentation
CLEO_DG_2011-1.pdf
Latest Substance Lists and Reference Data Release

Note for Dangerous Goods
TD_CLEO_DG_Training_EN.ppt
SAP EHS Regulatory Content Training Workshop

Slides
cleo_dg_changes_2011-1.mdb
Database with list of all changes compared to previous

release.
1-Customizing
R900081.TD8 and K900081.TD8
Basic Customizing transport (UserExit, RegList,

Source, Identifiers) with split by mode of transport of NA
regulations
R900434.TD8 and K900434.TD8
Basic Customizing transport (UserExit, RegList,

Source, Identifiers) without split by mode of transport of
NA regulations
R900456.TD8 and K900456.TD8
Master Data customizing transport for regulation ADG
R904117.TDG and K904117.TDG
Master Data customizing transport for regulation ADN

with pack data
Master Data customizing transport for regulation ADN

without pack data
Master Data customizing transport for regulation ADR

with pack data
Master Data customizing transport for regulation ADR

without pack data
Master Data customizing transport for regulation

CFR49 without split by mode of transport of NA regulations, including pack data

CFR49 without split by mode of transport of NA regulations, without pack data
R901931.TDF and K901931.TDF

CFR49 with split by mode of transport of NA regulations,
including pack data

CFR49 with split by mode of transport of NA regulations,
without pack data
Master Data customizing transport for regulation IATA

with pack data
Master Data customizing transport for regulation IATA

without pack data
223
SAP AG

Files
File Description
Master Data customizing transport for regulation IMDG

with pack data
Master Data customizing transport for regulation IMDG

without pack data
Master Data customizing transport for regulation RID

with pack data
Master Data customizing transport for regulation RID

without pack data
Master Data customizing transport for regulation TDG

Canada without split by mode of transport of NA regulations, including pack data

Canada without split by mode of transport of NA regulations, without pack data

Canada with split by mode of transport of NA regulations, including pack data

Canada with split by mode of transport of NA regulations, without pack data
R900398.TD8 and K900398.TD8
Master Data customizing transport for DG regulations

China, Mexico, MERCOSUR, Korea
R900494.TD8 and K900494.TD8
Master Data customizing transport for DG regulation

New Zealand
2-Phrases
cleo_dg_2011-1.dat
Import file for phrases
cleo_dg_pset_2011-1.dat
Import file for phrase set assignments
3-CLEO Database
CLEO_DG_2011-1.zip
Substance Lists and Reference Data - Dangerous

Goods - Database setup/update program
4-Mapping
TD_CLEO_DG.mdb
Standard mapping database without split of North

American regulations and with additional pack data, for
use in systems from ERP 6.0 on.
TD_CLEO_DG_without_pack.mdb
Mapping database without split of North American regulations and without additional pack data, for use in systems older than ERP 6.0.
TD_CLEO_DG_with_split.mdb
Mapping database with split of North American regulations into separate instances for different carrier types
and with additional pack data, for use in systems from
ERP 6.0 on.
TD_CLEO_DG_with_split_without_
pack.mdb
Mapping database with split of North American regulations into separate instances for different carrier types
224
SAP AG

Files
File Description
and without additional pack data, for use in systems older than ERP 6.0.
Caution
For system releases older than ERP 6.0 use transports and mapping database without
pack data only because structures for those additional data are not available in your
system.
You might use the correct mapping database and rename this one in TD_Cleo.mdb.
D.2.2. User Exit Settings

EXPERT_ADD_PARAM_1
Standard Value
headerurl=<path
to
CLEO
DG
DB>\DG_DB
\head.xml
EXPERT_ADD_PARAM_2
usernameurl=x
EXPERT_ADD_PARAM_3
passwordurl=x
EXPERT_CALL_ONCE
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_OCC
EXPERT_READ_RATING
EXPERT_RULE_SET
CLEO_DG
EXPERT_TAB_FIELD_1
<subid>
EXPERT_TAB_FIELD_2
<identifier>[NUM,UN]
EXPERT_TAB_FIELD_3
<identifier>[NAM,DG]
EXPERT_TAB_FIELD_4
<identifier>[NAM,DG]
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
TECHNIDATA
REG_WORLD
D.2.3. Other Settings

225
SAP AG

Customizing Setting
Value
Data Origin
TECHNIDATA
Phrase Library
TDCLE
OCCUNQID (OCC unique record ID)
NOL (name on list)
226
SAP AG
Appendix E. Technical Settings

Expert Rules 2011-1
This annex contains all relevant information to implement the SAP EHS Regulatory Content expert rules for substance and mixture classification.
The settings are grouped according to the respective rule set packages.
E.1. Settings to implement the basis rule set

package
E.1.1. File Overview
The following files are included in the delivery:
comp
File name
Description
comp_V1-21.ruc
Rule File
comp_V1-21.mdb
Mapping Database
Comp_V1-21.pdf
Functional Description
M Factor
File name
Description
M_Factor_V1-0.ruc
Rule File
M_Factor_V1-0.mdb
Mapping Database
M_Factor_V1-0.pdf
E.1.2. Settings in Admin Tool

The above listed settings have to be maintained via the Expert Admin Tool or within the transaction CGSADM
The settings for the rule sets and sub rule sets are:
Comp
Value of the parameter
Name
ZEXP_COMP
Mapping Database
comp_V1-21.mdb
Rule File
comp_V1-21.ruc
Additional Settings
Name
IgnoreWarnings
Value
355
227
SAP AG
Technical Settings Expert Rules 2011-1
M Factor
Name
ZEXP_MFACT
Mapping Database
M_Factor_V1-0.mdb
Rule File
M_Factor_V1-0.ruc
E.1.3. User Exit Settings

comp
User exit name
ZEXP_COMP
EHS-Expert: composition
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_WORLD
EXPERT_RULE_SET
ZEXP_COMP
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_COMP
REG_WORLD
M Factor
User exit name
ZEXP_MFACT
EHS-Expert: M Factor
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
228
SAP AG
EXPERT_READ_RATING
PUBLIC
EXPERT_RULE_SET
ZEXP_MFACT
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_MFACT
REG_WORLD
E.1.4. Other Settings

Source
affected rule sets
EHS-Expert
all
Data Origin
affected rule sets
ZEXP_COMP
Composition
ZEXP_MFACT
M Factor
E.2. Settings to implement the rule set package

for GHS
EU to GHS
File name
Description
EU_to_GHS_V1-51.ruc
Rule File
EU_to_GHS_Annex_VII_externvalues.mdb
External Database according to Annex VII of

the consolidated GHS EU proposal
EU_to_GHS_V1-51.mdb
Mapping
Database
with
reference
to
the
external
database
EU_to_GHS_EU_Annex_VII_externvalues.mdb
(Annex VII of the consolidated GHS EU proposal)
GS_physchem_V1-21.ruc
sub rule set which has to be installed once as

a separate instance on the Expert-Server-PC
229
SAP AG
GHS_label_V1-0.ruc

EU_to_GHS__HISTORY.mdb
database for the documentation of the

changes in the mapping database and the external database
ReleaseNote_EU_to_GHS_V1-51.pdf
Release Note
EU_to_GHS_V1-51.pdf
GHS
File name
Description
GHS_V2-3.ruc
Rule File
GHS_V2-3.mdb
Mapping Database
GHS_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-1.ruc
sub rule set which must be installed once as a

separate instance on the Expert-Server-PC
GS_ident_V1-0.ruc


GHS_sub_pb2009_V1-3.ruc

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GHS__HISTORY.mdb

ReleaseNote_GHS_V2-3.pdf
Release Note
GHS_V2-3.pdf
Hazcomp GHS
File name
Description
Hazcomp_GHS_V1-52.ruc
Rule File
Hazcomp_GHS_V1-52.mdb
Mapping Database
Hazcomp_GHS_externvalues.mdb
External Database
GS_base_V1-1.ruc

230
SAP AG
Hazcomp_GHS__HISTORY.mdb

ReleaseNote_Hazcomp_GHS_V1-52.pdf
Release Note
HazardComp_GHS_V1-52.pdf

The settings for the rule sets are:
EU to GHS
Name
ZEXP_RTGHS
Mapping Database
EU_TO_GHS_V1-51.mdb
Rule File
EU_to_GHS_V1-51.ruc
GHS
Name
ZEXP_GHS
Mapping Database
GHS_V2-3.mdb
Rule File
GHS_V2-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Hazcomp GHS
Name
ZEXP_HCGHS
Mapping Database
Hazcomp_GHS_V1-52.mdb
Rule File
Hazcomp_GHS_V1-52.ruc
E.2.3. Settings in Admin Tool - Sub Rules

The settings for the sub rule sets are:
GS_BASE_1_1
231
SAP AG
Name
GS_BASE_1_1
Rule File
GS_base_V1-1.ruc
GS_PHYSCHEM_1_2
Name
GS_PHYSCHEM_1_2
Rule File
GS_IDENT
Name
GS_IDENT
Rule File
GS_ident_V1-0.ruc
GHS_SUB_PB2009_1_3
Name
GHS_SUB_PB2009_1_1
Rule File
GHS_EXPL_1_5
Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc
GHS_LABEL_1_0
Name
GHS_LABEL_1_0
Rule File
GHS_label_V1-0.ruc
GHS_LABEL_1_1
Name
GHS_LABEL_1_1
Rule File
GHS_label_V1-1.ruc
GHS_PURE_1_1
Name
GHS_PURE_1_1
Rule File
GHS_pure_V1-1.ruc
232
SAP AG

EU to GHS
User exit name
ZEXP_RTGHS
EHS-Expert: EU to GHS
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_EU
EXPERT_RULE_SET
ZEXP_RTGHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_RTGHS
REG_WORLD
GHS
User exit name
ZEXP_GHS
EHS-Expert: GHS
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_WORLD
EXPERT_RULE_SET
ZEXP_GHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
233
SAP AG
ZEXP_GHS
REG_WORLD
SAP_EHS_0101_002
EX
Hazcomp GHS
User exit name
ZEXP_HCGHS
EHS-Expert: Hazardous Ingredients GHS
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
EXPERT_RULE_SET
ZEXP_HCGHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HCGHS
REG_WORLD

Source
affected rule sets
EHS-Expert
all
Data Origin
affected rule sets
ZEXP_RTGHS
EU to GHS
ZEXP_GHS
GHS
ZEXP_HCGHS
Hazardous ingredients GHS
234
SAP AG
User Defined Text Type

affected rule sets
EX
all rule sets with an explanation component
Validity Area
affected rule sets
REG_GHSUN
GHS: this region REG_GHSUN should contain all countries for which the GHS UN rule set
will be called. It is needed for the output in the
properties which are used by all GHS rule sets
like "Labeling for special preparations (GHS).
With this region it is possible to differentiate
the output of all GHS rule sets.
Regulatory List
affected rule sets
GHS
GHS
Identifier NAM
affected rule sets
RTGHS
EU to GHS

for APJ
DP AU
File name
Description
DP_AU_V2-34.ruc
Rule File
DP_AU_V2-34.mdb
Mapping Database
DP_AU_externvalues.mdb
External Database
GS_base_V1_1.ruc

DP_AU__HISTORY.mdb

ReleaseNote_APA_2011-1.pdf
Release Note
DP_AU_V2-34.pdf
235
SAP AG
HazardComp AU
File name
Description
HazardComp_AU_V2-51.ruc
Rule File
HazardComp_AU_V2-51.mdb
Mapping Database
HazardComp_AU_externvalues.mdb
External Database
GS_base_V1-1.ruc

HazardComp_AU__HISTORY.mdb

Release Note
HazardComp_AU_V2-51.pdf
Classification CN
File name
Description
Classification_CN_V2-51.ruc
Rule File
Classification_CN_V2-51.mdb
Mapping Database
Classification_CN_externvalues.mdb
External Database
GS_base_V1-1.ruc

Classification_CN__HISTORY.mdb

Release Note
Classification_CN_V2-51.pdf
HazardComp CN
File name
Description
HazardComp_CN_V2-5.ruc
Rule File
HazardComp_CN_V2-5.mdb
Mapping Database
HazardComp_CN_externvalues.mdb
External Database
GS_base_V1-1.ruc

HazardComp_CN__HISTORY.mdb

Release Note
HazardComp_CN_V2-5.pdf
GHS CN
File name
Description
236
SAP AG
GHS_CN_V1-3.ruc
Rule File
GHS_CN_V1-3.mdb
Mapping Database
GHS_CN_externvalues.mdb
External Database
the
external
database

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc

GS_ident_V1-0.ruc


GHS_CN__HISTORY.mdb

Release Note
GHS_CN_V1-3.pdf
Classification JP
File name
Description
Classification_JP_V2-62.ruc
Rule File
Classification_JP_V2-62.mdb
Mapping Database
Classification_JP_externvalues.mdb
External Database
GS_base_V1-1.ruc


Classification_JP__HISTORY.mdb

Release Note
Classification_JP_V2-62.pdf
Fire Service JP
File name
Description
237
SAP AG
Fire_Service_JP_V2-9.ruc
Rule File
Fire_Service_JP_V2-9.mdb
Mapping Database
Fire_Service_JP_externvalues.mdb
External Database
GS_base_V1-1.ruc


Fire_Service_JP__HISTORY.mdb

Release Note
Fire_Service_JP_V2-9.pdf
HazardComp JP
File name
Description
HazardComp_JP_V2-81.ruc
Rule File
HazardComp_JP_V2-81.mdb
Mapping Database
HazardComp_JP_externvalues.mdb
External Database
GS_base_V1-1.ruc

HazardComp_JP__HISTORY.mdb

Release Note
HazardComp_JP_V2-81.pdf
GHS JP
File name
Description
GHS_JP_V1-3.ruc
Rule File
GHS_JP_V1-3.mdb
Mapping Database
GHS_JP_externvalues.mdb
External Database
the
external
database

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

238
SAP AG
GS_base_V1-1.ruc

GS_ident_V1-0.ruc


GHS_JP__HISTORY.mdb

Release Note
GHS_JP_V1-3.pdf
GHS KR
File name
Description
GHS_KR_V1-7.ruc
Rule File
GHS_KR_V1-7.mdb
Mapping Database
GHS_KR_externvalues.mdb
External Database
the
external
database

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc

GS_ident_V1-0.ruc


GHS_KR__HISTORY.mdb

Release Note
GHS_KR_V1-7.pdf
DSSMA KR
File name
Description
DSSMA_KR_V1-7.ruc
Rule File
239
SAP AG
DSSMA_KR_V1-7.mdb
Mapping Database
DSSMA_KR_externvalues.mdb
External Database
GS_base_V1-1.ruc


DSSMA_KR__HISTORY.mdb

Release Note
DSSMA_KR_V1-7.pdf
HazardComp KR
File name
Description
HazardComp_KR_V2-52.ruc
Rule File
HazardComp_KR_V2-52.mdb
Mapping Database
HazardComp_KR_externvalues.mdb
External Database
GS_base_V1-1.ruc


HazardComp_KR__HISTORY.mdb

Release Note
HazardComp_KR_V2-52.pdf
GHS NZ
File name
Description
GHS_NZ_V1-6.ruc
Rule File
GHS_NZ_V1-6.mdb
Mapping Database
GHS_NZ_externvalues.mdb
External Database
the
external
database

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GS_base_V1-1.ruc

240
SAP AG
GS_ident_V1-0.ruc


GHS_NZ__HISTORY.mdb

Release Note
GHS_NZ_V1-6.pdf
HazardComp NZ
File name
Description
HazardComp_NZ_V1-3.ruc
Rule File
HazardComp_NZ_V1-3.mdb
Mapping Database
HazardComp_NZ_externvalues.mdb
External Database
GS_base_V1-1.ruc

HazardComp_NZ__HISTORY.mdb

Release Note
HazardComp_NZ_V1-3.pdf
GHS SG
File name
Description
GHS_SG_V1-3.ruc
Rule File
GHS_SG_V1-3.mdb
Mapping Database
GHS_SG_externvalues.mdb
External Database
the
external
database

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc

GS_ident_V1-0.ruc

241
SAP AG

GHS_SG__HISTORY.mdb

Release Note
GHS_SG_V1-3.pdf
HazardComp SG
File name
Description
HazardComp_SG_V1-1.ruc
Rule File
HazardComp_SG_V1-1.mdb
Mapping Database
HazardComp_SG_externvalues.mdb
External Database
GS_base_V1-1.ruc

HazardComp_SG__HISTORY.mdb

Release Note
HazardComp_SG_V1-1.pdf
Classification TW
File name
Description
Classification_TW_V2-42.ruc
Rule File
Classification_TW_V2-42.mdb
Mapping Database
Classification_TW_externvalues.mdb
External Database
GS_base_V1-1.ruc

Classification_TW__HISTORY.mdb

Release Note
Classification_TW_V2-42.pdf
HazardComp TW
File name
Description
HazardComp_TW_V2-51.ruc
Rule File
HazardComp_TW_V2-51.mdb
Mapping Database
HazardComp_TW_externvalues.mdb
External Database
GS_base_V1-1.ruc

242
SAP AG
HazardComp_TW__HISTORY.mdb

Release Note
HazardComp_TW_V2-51.pdf
GHS TW
File name
Description
GHS_TW_V1-3.ruc
Rule File
GHS_TW_V1-3.mdb
Mapping Database
GHS_TW_externvalues.mdb
External Database
the
external
database

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc

GS_ident_V1-0.ruc


GHS_TW__HISTORY.mdb

Release Note
GHS_TW_V1-3.pdf

DP AU
Name
ZEXP_DP_AU
243
SAP AG
Mapping Database
DP_AU_V2-34.mdb
Rule File
DP_AU_V2-34.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp AU
Name
ZEXP_HC_AU
Mapping Database
HazardComp_AU_V2-51.mdb
Rule File
HazardComp_AU_V2-51.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Classification CN
Name
ZEXP_CN_CN
Mapping Database
Classification_CN_V2-51.mdb
Rule File
Classification_CN_V2-51.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp CN
Name
ZEXP_HC_CN
Mapping Database
HazardComp_CN_V2-5.mdb
Rule File
HazardComp_CN_V2-5.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS CN
Name
ZEXP_GHSCN
Mapping Database
GHS_CN_V1-3.mdb
Rule File
GHS_CN_V1-3.ruc
244
SAP AG
Additional Settings
Name
IgnoreWarnings
Value
322
Classification JP
Name
ZEXP_CN_JP
Mapping Database
Classification_JP_V2-62.mdb
Rule File
Classification_JP_V2-62.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Fire Service JP
Name
ZEXP_FS_JP
Mapping Database
Fire_Service_JP_V2-9.mdb
Rule File
Fire_Service_JP_V2-9.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp JP
Name
ZEXP_HC_JP
Mapping Database
HazardComp_JP_V2-81.mdb
Rule File
HazardComp_JP_V2-81.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS JP
Name
ZEXP_GHSJP
Mapping Database
GHS_JP_V1-3.mdb
Rule File
GHS_JP_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
245
SAP AG
GHS KR
Name
ZEXP_GHSKR
Mapping Database
GHS_KR_V1-7.mdb
Rule File
GHS_KR_V1-7.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
DSSMA KR
Name
ZEXP_DS_KR
Mapping Database
DSSMA_KR_V1-7.mdb
Rule File
DSSMA_KR_V1-7.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp KR
Name
ZEXP_HC_KR
Mapping Database
HazardComp_KR_V2-52.mdb
Rule File
HazardComp_KR_V2-52.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS NZ
Name
ZEXP_GHSNZ
Mapping Database
GHS_NZ_V1-6.mdb
Rule File
GHS_NZ_V1-6.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp NZ
246
SAP AG
Name
ZEXP_HCNZ
Mapping Database
HazardComp_NZ_V1-3.mdb
Rule File
HazardComp_NZ_V1-3.ruc
GHS SG
Name
ZEXP_GHSSG
Mapping Database
GHS_SG_V1-3.mdb
Rule File
GHS_SG_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp SG
Name
ZEXP_HC_SG
Mapping Database
HazardComp_SG_V1-1.mdb
Rule File
HazardComp_SG_V1-1.ruc
Classification TW
Name
ZEXP_CN_TW
Mapping Database
Classification_TW_V2-42.mdb
Rule File
Classification_TW_V2-42.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp TW
Name
ZEXP_HC_TW
Mapping Database
HazardComp_TW_V2-51.mdb
Rule File
HazardComp_TW_V2-51.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS TW
247
SAP AG
Name
ZEXP_GHSTW
Mapping Database
GHS_TW_V1-3.mdb
Rule File
GHS_TW_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322

GS_BASE_1_1
Name
GS_BASE_1_1
Rule File
GS_base_V1-1.ruc
GS_PHYSCHEM_1_2
Name
GS_PHYSCHEM_1_2
Rule File
GS_IDENT
Name
GS_IDENT
Rule File
GS_ident_V1-0.ruc
GHS_SUB_PB2007_1_4
Name
GHS_SUB_PB2007_1_4
Rule File
GHS_EXPL_1_5
Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc
GHS_LABEL_1_1
248
SAP AG
Name
GHS_LABEL_1_1
Rule File
GHS_label_V1-1.ruc
GHS_PURE_1_1
Name
GHS_PURE_1_1
Rule File
GHS_pure_V1-1.ruc

DP AU
User exit name
ZEXP_DP_AU
EHS-Expert: DP_AU
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
AU
EXPERT_RULE_SET
ZEXP_DP_AU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_DP_AU
AU
HazardComp AU
User exit name
ZEXP_HC_AU
EHS-Expert: Hazardous Ingr. Australia
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
249
SAP AG
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
AU
EXPERT_RULE_SET
ZEXP_HC_AU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HC_AU
AU
Classification CN
User exit name
ZEXP_CN_CN
EHS-Expert: Classification_CN
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
CN
EXPERT_RULE_SET
ZEXP_CN_CN
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_CN_CN
CN
HazardComp CN
User exit name
ZEXP_HC_CN
EHS-Expert: Hazardous Ingr. China
EXPERT_COMMIT_FLG
250
SAP AG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
CN
EXPERT_RULE_SET
ZEXP_HC_CN
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HC_CN
CN
GHS CN
User exit name
ZEXP_GHSCN
EHS-Expert: GHS China
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
CN
EXPERT_RULE_SET
ZEXP_GHSCN
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHSCN
CN
SAP_EHS_0101_002
EX
Classification JP
User exit name
ZEXP_CN_JP
251
SAP AG
EHS-Expert: Classification_JP
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
JP
EXPERT_RULE_SET
ZEXP_CN_JP
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_CN_JP
JP
Fire Service JP
User exit name
ZEXP_FS_JP
EHS-Expert: Fire Service Law Japan
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
JP
EXPERT_RULE_SET
ZEXP_FS_JP
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_FS_JP
JP
HazardComp JP
User exit name
ZEXP_HC_JP
252
SAP AG
EHS-Expert: Hazardous Ingr. Japan
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
JP
EXPERT_RULE_SET
ZEXP_HC_JP
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HC_JP
JP
GHS JP
User exit name
ZEXP_GHSJP
EHS-Expert: GHS Japan
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
JP
EXPERT_RULE_SET
ZEXP_GHSJP
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHSJP
JP
SAP_EHS_0101_002
253
SAP AG
EX
GHS KR
User exit name
ZEXP_GHSKR
EHS-Expert: GHS Korea
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
KR
EXPERT_RULE_SET
ZEXP_GHSKR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHSKR
KR
SAP_EHS_0101_002
EX
DSSMA KR
User exit name
ZEXP_DS_KR
EHS-Expert: DSSMA Korea
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
KR
254
SAP AG
EXPERT_RULE_SET
ZEXP_DS_KR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_DS_KR
KR
HazardComp KR
User exit name
ZEXP_HC_KR
EHS-Expert: Hazardous Ingr. Korea
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
KR
EXPERT_RULE_SET
ZEXP_HC_KR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HC_KR
KR
GHS NZ
User exit name
ZEXP_GHSNZ
EHS-Expert: GHS New Zealand
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
255
SAP AG
NZ
EXPERT_RULE_SET
ZEXP_GHSNZ
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHSNZ
NZ
HazardComp NZ
User exit name
ZEXP_HC_NZ
EHS-Expert: Hazardous Ingr. New Zealand
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
NZ
EXPERT_RULE_SET
ZEXP_HC_NZ
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HC_NZ
NZ
GHS SG
User exit name
ZEXP_GHSSG
EHS-Expert: GHS Singapore
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
256
SAP AG
EXPERT_READ_RATING
PUBLIC
SG
EXPERT_RULE_SET
ZEXP_GHSSG
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHSSG
SG
SAP_EHS_0101_002
EX
HazardComp SG
User exit name
ZEXP_HC_SG
EHS-Expert: Hazardous Ingr. Singapore
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
SG
EXPERT_RULE_SET
ZEXP_HC_SG
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HC_SG
SG
Classification TW
User exit name
ZEXP_CN_TW
EHS-Expert: Classification_TW
EXPERT_COMMIT_FLG
257
SAP AG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
TW
EXPERT_RULE_SET
ZEXP_CN_TW
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_CN_TW
TW
HazardComp TW
User exit name
ZEXP_HC_TW
EHS-Expert: Hazardous Ingr. Taiwan
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
TW
EXPERT_RULE_SET
ZEXP_HC_TW
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HC_TW
TW
GHS TW
User exit name
ZEXP_GHSTW
EHS-Expert: GHS Taiwan
EXPERT_COMMIT_FLG
258
SAP AG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
TW
EXPERT_RULE_SET
ZEXP_GHSTW
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHSTW
TW
SAP_EHS_0101_002
EX

Source
affected rule sets
EHS-Expert
all
Data Origin
affected rule sets
ZEXP_DP_AU
DP AU
ZEXP_HC_AU
HazardComp AU
ZEXP_CN_CN
Classification CN
ZEXP_HC_CN
HazardComp CN
ZEXP_GHSCN
GHS CN
ZEXP_CN_JP
Classification JP
ZEXP_FS_JP
Fire Service JP
ZEXP_HC_JP
HazardComp JP
ZEXP_GHSJP
GHS JP
ZEXP_GHSKR
GHS KR
ZEXP_DS_KR
DSSMA KR
ZEXP_HC_KR
HazardComp KR
259
SAP AG
ZEXP_GHSNZ
GHS New Zealand
ZEXP_HC_NZ
Hazardous ingredients New Zealand
ZEXP_GHSSG
GHS SG
ZEXP_HC_SG
Hazardous ingredients Singapore
ZEXP_CN_TW
Classification TW
ZEXP_HC_TW
HazardComp TW
ZEXP_GHSTW
GHS TW
Rating
affected rule sets
LABEL_S
GHS_TW (needed for reduced label - needed

if output of label for packages < 100 ml has to
be written with its own usage)
Regulatory List
affected rule sets
GHS_CN
GHS CN
JP AVL
Fire Service JP
JP ECL
Fire Service JP
JP HPGL
Fire Service JP
JP VSL
Fire Service JP
GHS_JP
GHS JP
GHS_KR
GHS KR
ZKR_ISH166
HazardComp KR
GHS_NZ
GHS NZ
GHS_SG
GHS SG
GHS_TW
GHS TW

Europe
Dapec
File name
Description
DAPEC_V3-1.ruc
Rule File
DAPEC_V3-1.mdb
Mapping Database
DAPEC_externvalues.mdb
External Database
260
SAP AG
the
external
database
GS_base_V1-1.ruc

GS_ident_V1-0.ruc


comp_LEC50_V1-01.ruc

DAPEC__HISTORY.mdb

ReleaseNote_DAPEC_V3-1.pdf
Release Note
DAPEC_V3-1.pdf
GHS EU
File name
Description
GHS_EU_V1-6.ruc
Rule File
GHS_EU_V1-6.mdb
Mapping Database
GHS_EU_externvalues.mdb
External Database

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc


GHS_EU__HISTORY.mdb

ReleaseNote_GHS_EU_V1-6.pdf
Release Note
GHS_EU_V1-6.pdf
EU to GHS
File name
Description
EU_to_GHS_V1-51.ruc
Rule File
261
SAP AG
EU_to_GHS_Annex_VII_externvalues.mdb
External Database according to Annex VII of

the consolidated GHS EU proposal
EU_to_GHS_V1-51.mdb
Mapping
Database
with
reference
to
the
external
database
EU_to_GHS_EU_Annex_VII_externvalues.mdb
(Annex VII of the consolidated GHS EU proposal)

GHS_label_V1-0.ruc

EU_to_GHS__HISTORY.mdb

ReleaseNote_EU_to_GHS_V1-51.pdf
Release Note
EU_to_GHS_V1-51.pdf
HazardComp EU
File name
Description
HazardComp_EU_V3-0.ruc
Rule File
HazardComp_EU_V3-0.mdb
Mapping Database
HazardComp_EU_externvalues.mdb
External Database
GS_base_V1-1.ruc



HazardComp_EU__HISTORY.mdb

ReleaseNote_HC_EU_V3-0.pdf
Release Note
HazardComp_EU_V3-0.pdf
CLNOT
File name
Description
CL_for_notification_V1-2.ruc
Rule File
CL_for_notification_V1-2.mdb
Mapping Database - this file has to be in the

same folder as GHS_EU_externvalues.mdb
GHS_EU_externvalues.mdb
External Database - the rule set uses

the same external tables as the rule
set GHS EU. If GHS EU is already installed and changes had be done in
the external tables, this delivered file
262
SAP AG

GHS_EU_externvalues.mdb should not be
used.


ReleaseNote_CL_for_notification_V1-2.pdf
Release Note
CL_for_notification_V1-2.pdf

DAPEC
Name
ZEXP_DAPEC
Mapping Database
DAPEC_V3-1.mdb
Rule File
DAPEC_V3-1.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS EU
Name
ZEXP_GHSEU
Mapping Database
GHS_EU_V1-6.mdb
Rule File
GHS_EU_V1-6.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
EU to GHS
Name
ZEXP_RTGHS
Mapping Database
EU_TO_GHS_V1-51.mdb
Rule File
EU_to_GHS_V1-51.ruc
HazardComp EU
263
SAP AG
Name
ZEXP_HC_EU
Mapping Database
HazardComp_EU_V3-0.mdb
Rule File
HazardComp_EU_V3-0.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
CLNOT
Name
ZEXP_CLNOT
Mapping Database
CL_for_notification_V1-2.mdb
Rule File
CL_for_notification_V1-2.ruc

GS_BASE_1_1
Name
GS_BASE_1_1
Rule File
GS_base_V1-1.ruc
GS_PHYSCHEM_1_2
Name
GS_PHYSCHEM_1_2
Rule File
GS_IDENT
Name
GS_IDENT
Rule File
GS_ident_V1-0.ruc
COMP_LEC50
Name
COMP_LEC50
Rule File
264
SAP AG
GHS_SUB_PB2007_1_4
Name
GHS_SUB_PB2007_1_4
Rule File
GHS_EXPL_1_5
Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc
GHS_LABEL_1_0
Name
GHS_LABEL_1_0
Rule File
GHS_label_V1-0.ruc
GHS_PURE_1_1
Name
GHS_PURE_1_1
Rule File
GHS_pure_V1-1.ruc

Dapec
User exit name
ZEXP_DAPEC
EHS-Expert: DAPEC
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_EU
EXPERT_RULE_SET
ZEXP_DAPEC
265
SAP AG
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_DAPEC
REG_EU
SAP_EHS_0101_002
EX
GHS EU
User exit name
ZEXP_GHSEU
EHS-Expert: GHS EU
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_EU
EXPERT_RULE_SET
ZEXP_GHSEU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHSEU
REG_EU
SAP_EHS_0101_002
EX
EU to GHS
User exit name
ZEXP_RTGHS
EHS-Expert: EU to GHS
EXPERT_COMMIT_FLG
266
SAP AG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_EU
EXPERT_RULE_SET
ZEXP_RTGHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_RTGHS
REG_WORLD
HazardComp EU
User exit name
ZEXP_HC_EU
EHS-Expert: HazardComp_EU
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
EXPERT_RULE_SET
ZEXP_HC_EU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HC_EU
REG_EU
CLNOT
User exit name
ZEXP_CLNOT
EHS-Expert: CL for notification
EXPERT_COMMIT_FLG
267
SAP AG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_EU
EXPERT_RULE_SET
ZEXP_CLNOT
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_CLNOT
REG_EU

Source
affected rule sets
EHS-Expert
all
Data Origin
affected rule sets
ZEXP_DAPEC
DAPEC
ZEXP_GHSEU
GHS EU
ZEXP_RTGHS
EU to GHS
ZEXP_HC_EU
HazardComp EU
ZEXP_CLNOT
CL for notification
Validity Area
affected rule sets
REG_EU
GHS EU

affected rule sets
EX
Rating
affected rule sets
268
SAP AG
LABEL_S
DAPEC (needed if output of label for packages

< 125 ml has to be written with its own usage)
LABEL_S
GHS_EU (needed for reduced label - if output

of label for packages < 125 ml has to be written
with its own usage)
Regulatory List
affected rule sets
GHS_EU
GHS_EU
GHS
EU to GHS
Identifier NAM
affected rule sets
EINECS
DAPEC

for National Regulations EU
CMR EU
File name
Description
CMR_EU_V1-02.ruc
Rule File
CMR_EU_V1-02.mdb
Mapping Database
CMR_EU_externvalues.mdb
External Database
GS_base_V1-1.ruc

CMR_EU__HISTORY.mdb

ReleaseNote_EU_2011-1.pdf
Release Note
CMR_EU_V1-02.pdf
Detergents
File name
Description
Detergents_V1-0.ruc
Rule File
Detergents_V1-0.mdb
Mapping Database
Detergents_externvalues.mdb
External Database
GS_base_V1-1.ruc

269
SAP AG
Detergents_V1-0.pdf
ICPE
File name
Description
ICPE_V1-11.ruc
Rule File
ICPE_V1-11.mdb
Mapping Database
ICPE_V1-11.pdf
Release Note
ICPE__HISTORY.mdb

Maladies Professionelles
File name
Description
MaladiesProfessionnelles_V1-41.ruc
Rule File
MaladiesProfessionnelles_V1-41.mdb
Mapping Database
MaladiesProfessionnelles_externvalues.mdb External
Database
MaladiesProfessionnelles__HISTORY.mdb

Release Note
MaladiesProfessionnelles_V1-41.pdf
MAL Code
File name
Description
MAL_Code_V1-3.ruc
Rule File
MAL_Code_V1-3.mdb
Mapping Database
GS_base_V1-1.ruc

MAL_Code__HISTORY.mdb

Release Note
MAL-Code_V1-3.pdf
Seveso II
File name
Description
Seveso-II_V1-41.ruc
Rule File
Seveso-II_V1-41.mdb
Mapping Database
Seveso-II_externvalues.mdb
External Database
270
SAP AG
GS_base_V1-1.ruc


Seveso-II__HISTORY.mdb

Release Note
Seveso-II_V1-41.pdf
TA Luft
File name
Description
TAluft_V4-21.ruc
Rule File
TAluft_V4-21.mdb
Mapping Database
TAluft_externvalues.mdb
External Database
GS_base_V1-1.ruc


TAluft__HISTORY.mdb

Release Note
TALuft_V4-21.pdf
TRGS510
File name
Description
TRGS510_V1-0.ruc
Rule File
TRGS510_V1-0.mdb
Mapping Database
TRGS510_externvalues.mdb
External Database
GS_base_V1-1.ruc


TRGS510_V1-0.pdf
TRGS900
File name
Description
TRGS_900_V1-22.ruc
Rule File
TRGS_900_V1-22.mdb
Mapping Database
TRGS_900_externvalues.mdb
External Database
271
SAP AG
GS_base_V1-1.ruc

TRGS_900__HISTORY.mdb

Release Note
TRGS_900_V1-22.pdf
VbF AT
File name
Description
VbF_AT_V1-31.ruc
Rule File
VbF_AT_V1-31.mdb
Mapping Database

VbF_AT__HISTORY.mdb

Release Note
VbF_AT_V1-31.pdf
VOC CH
File name
Description
VOC_CH_V1-31.ruc
Rule File
VOC_CH_V1-31.mdb
Mapping Database
VOC_CH_externvalues.mdb
External Database
GS_base_V1-1.ruc

VOC_CH__HISTORY.mdb

Release Note
VOC_CH_V1-31.pdf
VOC EU
File name
Description
VOC_EU_V1-33.ruc
Rule File
VOC_EU_V1-33.mdb
Mapping Database
VOC_EU_externvalues.mdb
External Database
GS_base_V1-1.ruc


272
SAP AG
VOC_EU__HISTORY.mdb

Release Note
VOC_EU_V1-33.pdf
VOC PaintCoat
File name
Description
VOC_PaintCoat_V1-4.ruc
Rule File
VOC_PaintCoat_V1-4.mdb
Mapping Database
VOC_PaintCoat_externvalues.mdb
External Database
GS_base_V1-1.ruc


VOC_PaintCoat__HISTORY.mdb

Release Note
VOC_PaintCoat_V1-4.pdf
WGK
File name
Description
WGK_V1-81.ruc
Rule File
WGK_V1-81.mdb
Mapping Database
WGK_externvalues.mdb
External Database
the
external
database
GS_base_V1-1.ruc

GS_ident_V1-0.ruc

WGK__HISTORY.mdb

Release Note
WGK_V1-81.pdf

273
SAP AG

CMR EU
Name
ZEXP_CMREU
Mapping Database
CMR_EU_V1-02.mdb
Rule File
CMR_EU_V1-02.ruc
Detergents
Name
ZEXP_DETR
Mapping Database
Detergents_V1-0.mdb
Rule File
Detergents_V1-0.ruc
ICPE
Name
ZEXP_ICPE
Mapping Database
ICPE_V1-11.mdb
Rule File
ICPE_V1-11.ruc
MAL Code
Name
ZEXP_MAL
Mapping Database
MAL_Code_V1-3.mdb
Rule File
MAL_Code_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Maladies Professionnelles
Name
ZEXP_F_MP
Mapping Database
MaladiesProfessionnelles_V1-41.mdb
Rule File
MaladiesProfessionnelles_V1-41.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Seveso II
274
SAP AG
Name
ZEXP_SEVE
Mapping Database
Seveso-II_V1-41.mdb
Rule File
Seveso-II_V1-41.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
TA Luft
Name
ZEXP_TAL
Mapping Database
TAluft_V4-21.mdb
Rule File
TAluft_V4-21.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
TRGS510
Name
ZEXP_TR510
Mapping Database
TRGS510_V1-0.mdb
Rule File
TRGS510_V1-0.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
TRGS900
Name
ZEXP_TR90
Mapping Database
TRGS_900_V1-22.mdb
Rule File
TRGS_900_V1-22.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
VbF AT
Name
ZEXP_VBFAT
Mapping Database
VbF_AT_V1-31.mdb
275
SAP AG
Rule File
VbF_AT_V1-31.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
VOC CH
Name
ZEXP_VOC
Mapping Database
VOC_CH_V1-31.mdb
Rule File
VOC_CH_V1-31.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
VOC EU
Name
ZEXP_VOCEU
Mapping Database
VOC_EU_V1-33.mdb
Rule File
VOC_EU_V1-33.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
VOC PaintCoat
Name
ZEXP_VOCPC
Mapping Database
VOC_PaintCoat_V1-4.mdb
Rule File
VOC_PaintCoat_V1-4.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
WGK
Name
ZEXP_WGK
Mapping Database
WGK_V1-81.mdb
Rule File
WGK_V1-81.ruc
Additional Settings
276
SAP AG
Name
IgnoreWarnings
Value
322

The settings for sub rule sets are:
GS_BASE_1_1
Name
GS_BASE_1_1
Rule File
GS_base_V1-1.ruc
GS_PHYSCHEM_1_2
Name
GS_PHYSCHEM_1_2
Rule File
GS_IDENT
Name
GS_IDENT
Rule File
GS_ident_V1-0.ruc

CMR EU
User exit name
ZEXP_CMREU
EHS-Expert: CMR (EU)
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
277
SAP AG
EXPERT_RULE_SET
ZEXP_CMREU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_CMREU
REG_EU
ICPE
User exit name
ZEXP_ICPE
EHS-Expert: ICPE (FR)
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
FR
EXPERT_RULE_SET
ZEXP_ICPE
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_ICPE
FR
TRGS510
User exit name
ZEXP_TR510
EHS-Expert: TRGS510
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
278
SAP AG
EXPERT_READ_RATING
PUBLIC
DE
EXPERT_RULE_SET
ZEXP_TR510
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_LGK
DE
MAL Code
User exit name
ZEXP_MAL
EHS-Expert: Mal Code (DK)
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
DK
EXPERT_RULE_SET
ZEXP_MAL
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_MAL
DK
Maladies Professionnelles
User exit name
ZEXP_F_MP
EHS-Expert: Maladies Professionnelles
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
279
SAP AG
EXPERT_READ_RATING
PUBLIC
FR
EXPERT_RULE_SET
ZEXP_F_MP
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_F_MP
FR
Seveso II
User exit name
ZEXP_SEVE
EHS-Expert: Seveso II (EU)
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_EU
EXPERT_RULE_SET
ZEXP_SEVE
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_SEVE
REG_EU
SAP_EHS_0101_002
EX
TA Luft
User exit name
ZEXP_TAL
EHS-Expert: TI-Air Quality (TA Luft /DE)
EXPERT_COMMIT_FLG
280
SAP AG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
DE
EXPERT_RULE_SET
ZEXP_TAL
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_TAL
DE
SAP_EHS_0101_002
EX
TRGS 900
User exit name
ZEXP_TR90
EHS-Expert: TRGS 900 (DE)
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
DE
EXPERT_RULE_SET
ZEXP_TR90
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_TR90
DE
VbF AT
User exit name
ZEXP_VBFAT
281
SAP AG
EHS-Expert: VBF (AT)
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
AT
EXPERT_RULE_SET
ZEXP_VBFAT
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_VBFAT
AT
VOC CH
User exit name
ZEXP_VOC
EHS-Expert: VOC (CH)
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
CH
EXPERT_RULE_SET
ZEXP_VOC
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_VOC
CH
VOC EU
User exit name
ZEXP_VOCEU
282
SAP AG
EHS-Expert: VOC (EU)
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_EU
EXPERT_RULE_SET
ZEXP_VOCEU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_VOCEU
REG_EU
VOC PaintCoat
User exit name
ZEXP_VOCPC
EHS-Expert: VOC PaintCoat
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_EU
EXPERT_RULE_SET
ZEXP_VOCPC
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_VOCPC
REG_EU
WGK
User exit name
ZEXP_WGK
283
SAP AG
EHS-Expert: WGK (DE)
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
DE
EXPERT_RULE_SET
ZEXP_WGK
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_WGK
DE
SAP_EHS_0101_002
EX

Source
affected rule sets
EHS-Expert
all
Data Origin
affected rule sets
ZEXP_CMREU
CMR (EU)
ZEXP_DETR
Detergents
ZEXP_ICPE
ICPE (FR)
ZEXP_LGK
TRGS 510
ZEXP_MAL
MAL Code (DK)
ZEXP_F_MP
Maladies Professionnelles (FR)
ZEXP_SEVE
Seveso II (EU)
ZEXP_TAL
TA Luft (DE)
284
SAP AG
ZEXP_TR90
TRGS 900
ZEXP_VBFAT
VBF (AT)
ZEXP_VOC
VOC CH
ZEXP_VOCEU
VOC EU
ZEXP_VOCPC
VOC PaintCoat
ZEXP_WGK
WGK

affected rule sets
EX
Regulatory List
affected rule sets
96/82/EC
Seveso II
04/42/EC
VOC PaintCoat

for the Americas
Clean Air Act

File name
Description
CAA_V1-21.ruc
Rule File
CAA_V1-21.mdb
Mapping Database
GS_base_V1-1.ruc

CAA__HISTORY.mdb

ReleaseNote_NA_2011-1.pdf
Release Note
CAA_V1-21.pdf
Clean Water Act

File name
Description
CWA_V1-01.ruc
Rule File
CWA_V1-01.mdb
Mapping Database
285
SAP AG
GS_base_V1-1.ruc

CWA__HISTORY.mdb

Release Note
CWA_V1-01.pdf
EU to OSHA
File name
Description
EU_to_OSHA_V1-1.ruc
Rule File
EU_to_OSHA_V1-1.mdb
Mapping Database
EU_to_OSHA_externvalues.mdb
External Database
EU_to_OSHA__HISTORY.mdb

Release Note
EU_to_OSHA_V1-1.pdf
HazardComp US
File name
Description
HazardComp_US_V2-71.ruc
Rule File
HazardComp_US_V2-71.mdb
Mapping Database
HazardComp_US_externvalues.mdb
External Database
GS_base_V1-1.ruc

HazardComp_US__HISTORY.mdb

Release Note
HazardComp_US_V2-71.pdf
HMIS
File name
Description
HMIS_V2-5.ruc
Rule File
HMIS_V2-5.mdb
Mapping Database
HMIS_externvalues.mdb
External Database
the
external
database
GS_base_V1-1.ruc

286
SAP AG
GS_ident_V1-0.ruc


HMIS__HISTORY.mdb

Release Note
HMIS_V2-5.pdf
Maine Chemicals High Concern

File name
Description
MCHC_V1-0.ruc
Rule File
MCHC_V1-0.mdb
Mapping Database
GS_base_V1-1.ruc

Release Note
MCHC_V1-0.pdf
NFPA
File name
Description
NFPA_V1-7.ruc
Rule File
NFPA_V1-7.mdb
Mapping Database
NFPA_externvalues.mdb
External Database
the
external
database
GS_base_V1-1.ruc

GS_ident_V1-0.ruc


NFPA__HISTORY.mdb

Release Note
NFPA_V1-7.pdf
OSHA/SARA Hazard Determination

File name
Description
OSHA_Hazard_Determination_V2-71.ruc
Rule File
287
SAP AG
OSHA_Hazard_Determination_V2-71.mdb
Mapping Database
OSHA_Hazard_Determination_
externvalues.mdb
External Database
the
external
database
GS_base_V1-1.ruc

GS_ident_V1-0.ruc


OSHA_Hazard_Determination__HISTORY.mdb

Release Note
OSHA_SARA_Hazard_Determination_V2-71.pdf
SaraComp
File name
Description
SaraComp_V2-11.ruc
Rule File
SaraComp_V2-11.mdb
Mapping Database
SaraComp_externvalues.mdb
External Database
GS_base_V1-1.ruc

SaraComp__HISTORY.mdb

Release Note
SaraComp_V2-11.pdf
SpillReport
File name
Description
SpillReport_V2-01.ruc
Rule File
SpillReport_V2-01.mdb
Mapping Database
SpillReport_externvalues.mdb
External Database
GS_base_V1-1.ruc

SpillReport__HISTORY.mdb

Release Note
SpillReport_V2-01.pdf
288
SAP AG
US State RTK
File name
Description
US_State_RTK_V1-74.ruc
Rule File
US_State_RTK_V1-74.mdb
Mapping Database
US_State_RTK_externvalues.mdb
External Database
GS_base_V1-1.ruc

US_State_RTK__HISTORY.mdb

Release Note
US_State_RTK_V1-74.pdf
CA PBT
File name
Description
CAPBT_V1-01.ruc
Rule File
CAPBT_V1-01.mdb
Mapping Database
GS_base_V1-1.ruc

CAPBT__HISTORY.mdb

Release Note
CAPBT_V1-01.pdf
WHMISClassification
File name
Description
WHMISCLASS_V2-62.ruc
Rule File
WHMISCLASS_V2-62.mdb
Mapping Database
WHMISCLASS_externvalues.mdb
External Database
the
external
database
GS_base_V1-1.ruc

GS_ident_V1-0.ruc


WHMISCLASS__HISTORY.mdb

289
SAP AG
Release Note
WHMISClassification_V2-62.pdf
WHMISComposition
File name
Description
WHMISComposition_V1-73.ruc
Rule File
WHMISComposition_V1-73.mdb
Mapping Database
WHMISComposition_externvalues.mdb
External Database
GS_base_V1-1.ruc

WHMISComposition__HISTORY.mdb

Release Note
WHMISComposition_V1-73.pdf
GHS BR
File name
Description
GHS_BR_V1-2.ruc
Rule File
GHS_BR_V1-2.mdb
Mapping Database
GHS_BR_externvalues.mdb
External Database

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc


GHS_BR__HISTORY.mdb

Release Note
GHS_BR_V1-2.pdf
HazardComp BR
File name
Description
HazardComp_BR_V1-1.ruc
Rule File
290
SAP AG
HazardComp_BR_V1-1.mdb
Mapping Database
HazardComp_BR_externvalues.mdb
External Database
GS_base_V1-1.ruc

HazardComp_BR__HISTORY.mdb

HazardComp_BR_V1-1.pdf

Clean Air Act

Name
ZEXP_CAA
Mapping Database
CAA_V1-21.mdb
Rule File
CAA_V1-21.ruc
Clean Water Act

Name
ZEXP_CWA
Mapping Database
CWA_V1-01.mdb
Rule File
CWA_V1-01.ruc
EU to OSHA
Name
ZEXP_RTOSH
Mapping Database
EU_to_OSHA_V1-1.mdb
Rule File
EU_to_OSHA_V1-1.ruc
HazardComp US
Name
ZEXP_HAZCO
Mapping Database
HazardComp_US_V2-71.mdb
Rule File
HazardComp_US_V2-71.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
291
SAP AG
HMIS
Name
ZEXP_HMIS
Mapping Database
HMIS_V2-5.mdb
Rule File
HMIS_V2-5.ruc
...
Name
ZEXP_MCHC
Mapping Database
MCHC_V1-0.mdb
Rule File
MCHC_V1-0.ruc
NFPA
Name
ZEXP_NFPA
Mapping Database
NFPA_V1-7.mdb
Rule File
NFPA_V1-7.ruc

Name
ZEXP_OSHA
Mapping Database
OSHA_Hazard_Determination_V2-71.mdb
Rule File
OSHA_Hazard_Determination_V2-71.ruc
SaraComp
Name
ZEXP_SAC
Mapping Database
SaraComp_V2-11.mdb
Rule File
SaraComp_V2-11.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
SpillReport
Name
ZEXP_SPRQ
Mapping Database
SpillReport_V2-01.mdb
Rule File
SpillReport_V2-01.ruc
292
SAP AG
Additional Settings
Name
IgnoreWarnings
Value
322
US State RTK
Name
ZEXP_RTK
Mapping Database
US_State_RTK_V1-74.mdb
Rule File
US_State_RTK_V1-74.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
CA PBT
Name
ZEXP_CAPBT
Mapping Database
CAPBT_V1-01.mdb
Rule File
CAPBT_V1-01.ruc
WHMISClassification
Name
ZEXP_WHMIS
Mapping Database
WHMISCLASS_V2-62.mdb
Rule File
WHMISCLASS_V2-62.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
WHMISComposition
Name
ZEXP_HC_CA
Mapping Database
WHMISComposition_V1-73.mdb
Rule File
WHMISComposition_V1-73.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS BR
293
SAP AG
Name
ZEXP_GHSBR
Mapping Database
GHS_BR_V1-2.mdb
Rule File
GHS_BR_V1-2.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp BR
Name
ZEXP_HC_BR
Mapping Database
HazardComp_BR_V1-1.mdb
Rule File
HazardComp_BR_V1-1.ruc
Additional Settings
Name
IgnoreWarnings
Value
322

GS_BASE_1_1
Name
GS_BASE_1_1
Rule File
GS_base_V1-1.ruc
GS_PHYSCHEM_1_2
Name
GS_PHYSCHEM_1_2
Rule File
GS_IDENT
Name
GS_IDENT
Rule File
GS_ident_V1-0.ruc
GHS_SUB_PB2007_1_4
Name
GHS_SUB_PB2007_1_4
294
SAP AG
Rule File
GHS_EXPL_1_5
Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc
GHS_LABEL_1_1
Name
GHS_LABEL_1_1
Rule File
GHS_label_V1-1.ruc
GHS_PURE_1_1
Name
GHS_PURE_1_1
Rule File
GHS_pure_V1-1.ruc

Clean Air Act

User exit name
ZEXP_CAA
EHS-Expert: Clean Air Act
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_CAA
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_CAA
US
295
SAP AG
Clean Water Act

User exit name
ZEXP_CWA
EHS-Expert: Clean Water Act
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_CWA
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_CWA
US
EU to OSHA
User exit name
ZEXP_RTOSH
EHS-Expert: EU to OSHA
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_EU
EXPERT_RULE_SET
ZEXP_RTOSH
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_RTOSH
US
296
SAP AG
HazardComp US
User exit name
ZEXP_HAZCO
EHS-Expert: Hazardous ingredients US
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_HAZCO
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HAZCO
US
HMIS
User exit name
ZEXP_HMIS
EHS-Expert: HMIS
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_HMIS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HMIS
US
297
SAP AG
SAP_EHS_0101_002
EX
....
User exit name
ZEXP_MCHC
EHS-Expert: ...
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_MCHC
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_MCHC
US
NFPA
User exit name
ZEXP_NFPA
EHS-Expert: NFPA
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_NFPA
298
SAP AG
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_NFPA
US
SAP_EHS_0101_002
EX

User exit name
ZEXP_OSHA
EHS-Expert: OSHA/SARA Classification
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_OSHA
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_OSHA
US
SAP_EHS_0101_002
EX
SaraComp
User exit name
ZEXP_SAC
EHS-Expert: SARA Components
EXPERT_COMMIT_FLG
299
SAP AG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_SAC
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_SAC
US
SpillReport
User exit name
ZEXP_SPRQ
EHS-Expert: Spill Reporting
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_SPRQ
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_SPRQ
US
US State RTK
User exit name
ZEXP_RTK
EHS-Expert: US Right to Know
EXPERT_COMMIT_FLG
300
SAP AG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_RTK
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_RTK
US
CA PBT
User exit name
ZEXP_CAPBT
EHS-Expert: CA PBT
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
CA
EXPERT_RULE_SET
ZEXP_CAPBT
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_CAPBT
CA
WHMISClassification
User exit name
ZEXP_WHMIS
EHS-Expert: WHMIS Classification (CA)
EXPERT_COMMIT_FLG
301
SAP AG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
CA
EXPERT_RULE_SET
ZEXP_WHMIS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_WHMIS
CA
SAP_EHS_0101_002
EX
WHMISComposition
User exit name
ZEXP_HC_CA
EHS-Expert: WHMIS Composition (CA)
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
CA
EXPERT_RULE_SET
ZEXP_HC_CA
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HC_CA
CA
GHS BR
User exit name
ZEXP_GHSBR
302
SAP AG
EHS-Expert: GHS Brazil
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
BR
EXPERT_RULE_SET
ZEXP_GHSBR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHSBR
BR
SAP_EHS_0101_002
EX
HazardComp BR
User exit name
ZEXP_HC_BR
EHS-Expert: Hazardous ingredients BR
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
BR
EXPERT_RULE_SET
ZEXP_HC_BR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_HC_BR
303
SAP AG
BR

Source
affected rule sets
EHS-Expert
all
Data Origin
affected rule sets
ZEXP_CAA
Clean Air Act
ZEXP_CWA
Clean Water Act
ZEXP_RTOSH
EU to OSHA
ZEXP_HAZCO
Hazardous Ingredients US
ZEXP_HMIS
HMIS
ZEXP_MCHC
Maine Chemicals of High Concern
ZEXP_NFPA
NFPA
ZEXP_OSHA
ZEXP_SAC
Sara Components
ZEXP_SPRQ
Spill Reporting
ZEXP_RTK
US State RTK
ZEXP_CAPBT
PBT List (CA)
ZEXP_WHMIS
WHMIS Classification (CA)
ZEXP_HC_CA
WHMIS Composition (CA)
ZEXP_GHSBR
GHS BR
ZEXP_HC_BR
HazardComp BR

affected rule sets
EX
Regulatory List
affected rule sets
GHS_BR
GHS_BR
Rating
affected rule sets
LABEL
WHMISClassification
304
SAP AG
E.7. Settings to implement the RegStat rule set

package
Please note: for NotStat, there are two different variants delivered, ProdComp and StandComp.
Depending on the variant chosen for the installation, the respective files need to be selected.
NotStat
File name
Description
NotStat_frame_master_V3-3.ruc
Rule File
NotStat_frame_master_ProdComp_V3-3.mdb
Mapping Database (ProdComp variant)
NotStat_frame_master_StandComp_V3-3.mdb
Mapping Database (StandComp variant)
NotStat_externvalues.mdb
External Database
NotStat_V3-3.ruc
sub rule (core logic)
NotStat_sub_TSCA12b_V3-3.ruc
sub rule (TSCA 12b)
NotStat_sub_expl_V3-3.ruc
sub rule (Explanation Component)
the
external
database
GS_base_V1-1.ruc

GS_ident_V1-0.ruc

NotStat_frame_master__HISTORY.mdb

ReleaseNote_NotStat_V3-3.pdf
Release Note
Notstat_V3-3.pdf
RestrictionStatus
File name
Description
RestrictionStatus_V1-71.ruc
Rule File
RestrictionStatus_V1-71.mdb
Mapping Database
RestrictionStatus_externvalues.mdb
External Database
GS_base_V1-1.ruc

RestrictionStatus__HISTORY.mdb

ReleaseNote_RestrictionStatus_V1-71.pdf
Release Note
305
SAP AG
RestrictionStatus_V1-71.pdf

The above listed settings have to be maintained via the Expert Admin Tool or within the transaction CGSADM.
Please note: for NotStat, there are two different variants delivered, ProdComp and StandComp.
Depending on the variant chosen for the installation, the respective files need to be selected.
NotStat
Name
ZEXP_NOTS
Mapping Database (ProdComp variant)
NotStat_frame_master_ProdComp_V3-3.mdb
(ProdComp variant)
Mapping Database (StandComp variant)
NotStat_frame_master_StandComp_V3-3.mdb
(StandComp variant)
Rule File
NotStat_frame_master_V3-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322,330,332,355
RestrictionStatus
Name
ZEXP_RESST
Mapping Database
RestrictionStatus_V1-71.mdb
Rule File
RestrictionStatus_V1-71.ruc

GS_BASE_1_1
Name
GS_BASE_1_1
Rule File
GS_base_V1-1.ruc
GS_IDENT
306
SAP AG
Name
GS_IDENT
Rule File
GS_ident_V1-0.ruc
NOTSTAT_SUB
Name
NOTSTAT_SUB
Rule File
NotStat_V3-3.ruc
NOTSTAT_SUB_TSCA12B
Name
NOTSTAT_SUB_TSCA12B
Rule File
NotStat_sub_TSCA12b_V3-3.ruc
NOTSTAT_SUB_EXPL
Name
NOTSTAT_SUB_EXPL
Rule File
NotStat_sub_expl_V3-3.ruc

NotStat
User exit name
ZEXP_NOTS
EHS-Expert: Notstat
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
EXPERT_RULE_SET
ZEXP_NOTS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_NOTS
REG_WORLD
307
SAP AG
SAP_EHS_0101_002
EX
RestrictionStatus
User exit name
ZEXP_RESST
EHS-Expert: RestrictionStatus
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
EXPERT_RULE_SET
ZEXP_RESST
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_RESST
REG_WORLD

Source
affected rule sets
EHS-Expert
all
Data Origin
affected rule sets
ZEXP_NOTS
NotStat
ZEXP_RESST
RestrictionStatus

affected rule sets
EX
308
SAP AG
E.8. Settings to implement the DangGoods rule

set package
Please note: there are two different variants of the DangGoods rule set available: global and
local. Depending on your license you may receive different files for the main rule DangGoods,
which are both indicated below separated by slashes. In such cases the delivered files have
to be chosen respectively.
DangGoods
File name
Description
DangGoods_master_global_V4-0.ruc
DangGoods_master_V4-0.ruc
Rule File (global/local version)
DangGoods_master_global_V4-0.mdb
DangGoods_master_V4-0.mdb
Mapping Database (global/local version)
DangGoods_externvalues.mdb
External Database
DangGoods_V4-0.ruc
sub rule set (central part for classification process for solids/liquids)
sub rule set (GHS classification via component data)
DangGoods_gas_V4-0.ruc
sub rule set (classification for gaseous mixtures and hazard inducer determination)
DangGoods_sub_binary_V4-0.ruc
sub rule set (evaluation of binary mixtures as

special gaseous mixtures)
DangGoods_report_quant_V4-0.ruc
sub rule set (determination of reportable quantities) (only global version!)
the
external
database
GS_base_V1-1.ruc

GS_ident_V1-0.ruc


DangGoods_master__HISTORY.mdb

ReleaseNote_DangGoods_V4-0.pdf
Release Note
DangGoods_V4-0.pdf
309
SAP AG

Please note: there are two different variants of the DangGoods rule set available: global and
local. Depending on your license you may receive different files for the main rule DangGoods,
which are both indicated below separated by slashes. In such cases the delivered files have
to be chosen respectively.
DangGoods
Name
ZEXP_DG
Mapping Database
DangGoods_master_global_V4-0.mdb
DangGoods_master_V4-0.mdb
Rule File
DangGoods_master_global_V4-0.ruc
DangGoods_master_V4-0.ruc

GS_BASE_1_1
Name
GS_BASE_1_1
Rule File
GS_base_V1-1.ruc
GS_PHYSCHEM_1_2
Name
GS_PHYSCHEM_1_2
Rule File
GS_IDENT
Name
GS_IDENT
Rule File
GS_ident_V1-0.ruc
DG_SUB_4_0
Name
DG_SUB_4_0
Rule File
DangGoods_V4-0.ruc
310
SAP AG
GHS_SUB_PB2009_1_1
Name
GHS_SUB_PB2009_1_1
Rule File
DG_SUB_GAS_4_0
Name
DG_SUB_GAS_4_0
Rule File
DangGoods_gas_V4-0.ruc
DG_GAS_BINARY
Name
DG_GAS_BINARY
Rule File
DangGoods_sub_binary_V4-0.ruc
DG_RQ_4_0
Name
DG_RQ_4_0
Rule File
DangGoods_report_quant_V4-0.ruc

DangGoods
User exit name
ZEXP_DG
EHS-Expert: DangGoods
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
EXPERT_RULE_SET
ZEXP_DG
EXPERT_WRITE_OWNER
311
SAP AG
EXPERT_WRITE_RATING
PUBLIC
ZEXP_DG
REG_WORLD
SAP_EHS_0101_002
EX

Source
affected rule sets
EHS-Expert
all
Data Origin
affected rule sets
ZEXP_DG
DangGoods

affected rule sets
EX
Identifier NAM
affected rule sets
DG-CLASS
DangGoods
E.9. Settings to implement the MSDSMaker rule

set package
MSDSMaker
File name
Description
MSDSRule_V3-7.ruc
Rule File
MSDSRule_V3-7.mdb
Mapping Database (depending on variant

used / subfolders in delivery)
312
SAP AG
MSDSMaker.mdb
External Database (depending on variant

MSDSRule_sub_V3-7.ruc
sub rule set
GS_base_V1-1.ruc

separate instance on the Expert Server PC

separate instance on the Expert Server PC
ReleaseNote_MSDSMaker_V3-7.pdf
Release Note
MSDSMaker_V3-7.pdf

MSDSMaker
Name
ZEXP_SDS
Mapping Database
MSDSRule_V3-7.mdb (depending on variant

Rule File
MSDSRule_V3-7.ruc

GS_BASE_1_1
Name
GS_BASE_1_1
Rule File
GS_base_V1-1.ruc
GS_PHYSCHEM_1_2
Name
GS_PHYSCHEM_1_2
Rule File
MSDSRULE_SUB
313
SAP AG
Name
MSDSRULE_SUB
Rule File
MSDSRule_sub_V3-7.ruc

MSDSMaker
User exit name
ZEXP_SDS
EHS-Expert: MSDSMaker
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
EXPERT_RULE_SET
ZEXP_SDS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_SDS
REG_WORLD

Source
affected rule sets
EHS-Expert
all
Data Origin
affected rule sets
ZEXP_SDS
MSDSMaker
E.10. Settings to implement the DPDplus rule set

package
314
SAP AG

DPDplus_lead
File name
Description
DPDplus_lead_V1-11.ruc
Rule File
DPDplus_lead_V1-11.mdb
Mapping Database
DPDplus_lead_externvalues.mdb
External Database
the
external
database
GS_base_V1-1.ruc


GS_ident_V1-0.ruc

DPDplus_lead__HISTORY.mdb

ReleaseNote_DPDplus_lead_V1-11.pdf
Release Note
DPDplus_lead_V1-11.pdf

DPDplus_lead
Name
ZEXP_DPDL
Mapping Database
DPDplus_lead_V1-11.mdb
Rule File
DPDplus_lead_V1-11.ruc
Additional Settings
Name
IgnoreWarnings
Value
322

315
SAP AG

GS_BASE_1_1
Name
GS_BASE_1_1
Rule File
GS_base_V1-1.ruc
GS_PHYSCHEM_1_2
Name
GS_PHYSCHEM_1_2
Rule File
GS_IDENT
Name
GS_IDENT
Rule File
GS_ident_V1-0.ruc

DPDplus_lead
User exit name
ZEXP_DPDL
EHS-Expert: DPDplus_lead
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
REG_EU
EXPERT_RULE_SET
ZEXP_DPDL
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_DPDL
REG_EU
316
SAP AG
SAP_EHS_0101_002
EX

Source
affected rule sets
EHS-Expert
all
Data Origin
affected rule sets
ZEXP_DPDL
DPDplus_lead
Regulatory List
affected rule sets
REACH
DPDplus_lead
Identifier NUM
affected rule sets
REACH_REG
DPDplus_lead
317
SAP AG
Appendix F. Technical Settings MSDS

Templates 2011-1
This annex contains all relevant information to implement the SAP EHS Regulatory Content material safety data sheet (MSDS) templates.
The settings are divided into the several packages.
F.1. Settings to implement the MSDS Templates

for APJ
F.1.1. File Overview
APJ
File name
Description
K901326.TDP and R901326.TDP
APA customizing transport TDPK901326 unicode
K902773.TD4 and R902773.TD4
APA customizing transport TD4K902773 nonunicode
workbench transport TDPK901097
K900243.TD5 and R900243.TD5
transport with definition of the namespace

TDAG
K909498.TD6 and R909498.TD6
workbench transport TD6K909498 non-unicode
SDS_AP_AU_2011_1.dat
Template Import-file
SDS_AP_CN_2011_1.dat
SDS_AP_JP_2011_1.dat
SDS_AP_KR_2011_1.dat
SDS_AP_TW_2011_1.dat
SDS_AP_NZ_2011_1.dat
SDS_AP_SG_2011_1.dat
SDS_AP_AU_2011_1_unix.dat
Template Import-file for unix systems
SDS_AP_CN_2011_1_unix.dat
SDS_AP_JP_2011_1_unix.dat
SDS_AP_KR_2011_1_unix.dat
SDS_AP_TW_2011_1_unix.dat
SDS_AP_NZ_2011_1_unix.dat
SDS_AP_SG_2011_1_unix.dat
SDS_AP_AU_2011_1.doc
Template document-file
SDS_AP_CN_2011_1.doc
318
SAP AG
Technical Settings MSDS Templates 2011-1
SDS_AP_JP_2011_1.doc
SDS_AP_KR_2011_1.doc
SDS_AP_TW_2011_1.doc
SDS_AP_NZ_2011_1.doc
SDS_AP_SG_2011_1.doc
SDS_AP_AU_2011_1_Datamapping.pdf
DataMapping - Document for SDS AU (Australia)
SDS_AP_CN_2011_1_Datamapping.pdf
DataMapping - Document for SDS CN (China)
SDS_AP_CN_2011_1_changes_marked_
yellow.doc
SDS WWI Layout with updated parts highlighted
SDS_AP_CN_2011_1_Datamapping_highlighted.pdf
DataMapping
- Document with updated parts
highlighted
SDS_AP_JP_2011_1_Datamapping.pdf
DataMapping - Document for SDS JP (Japan)
SDS_AP_JP_2011_1_changes_marked_
yellow.doc
SDS_AP_JP_2011_1_Datamapping_highlighted.pdf
DataMapping
highlighted
SDS_AP_KR_2011_1_Datamapping.pdf
DataMapping - Document for SDS KR (Korea)
SDS_AP_KR_2011_1_changes_marked_
yellow.doc
SDS_AP_KR_2011_1_Datamapping_highlighted.pdf
DataMapping
highlighted
SDS_AP_TW_2011_1_Datamapping.pdf
DataMapping - Document for SDS TW (Taiwan)
SDS_AP_TW_2011_1_changes_marked_
yellow.doc
SDS_AP_TW_2011_1_Datamapping_highlighted.pdf
DataMapping
highlighted
SDS_AP_NZ_2011_1_Datamapping.pdf
DataMapping - Document for SDS NZ (New

Zealand)
SDS_AP_NZ_2011_1_changes_marked_
yellow.doc
SDS_AP_NZ_2011_1_Datamapping_highlighted.pdf
DataMapping
highlighted
SDS_AP_SG_2011_1_Datamapping.pdf
DataMapping - Document for SDS SG (Singapore)
SDS_AP_SG_2011_1_Datamapping_highlighted.pdf
DataMapping
highlighted
SDS_AP_SG_2011_1_changes_marked_
yellow.doc
F.1.2. Other Settings

319
SAP AG

Please maintain following ID Listings: ZISIEU1020, ZISINA1080,D_VALPOS, ZTS_IDLID
We suggest to maintain them as follows:
IDListing
IDList
ZISIEU1020
SDS EU Identifiers
IDListPos
IDListPrio
NAM
NAM
NAM
NAM
ANNEXI
TRIV
EINECS
SYN
IDCategory
IDType
IDListing
IDList
ZISINA1080
SDS NA Identifiers
IDListPos
IDListPrio
IDCategory
NAM
NAM
NAM
NAM
IDType
SYN
CAS
ANNEX1
EINECS
IDListing
IDList
D_VALPOS
Identifier in Component overview
IDListPos
IDListPrio
IDCategory
NAM
NAM
NAM
NUM
IDType
SYN
CAS
EINECS
CAS
IDListing
IDList
IDListPos
IDListPrio
IDCategory
IDType
ZTS_IDLID
Trade Secret Listing
NAM
ZTRADESEC
F.1.3. Generation variant

We suggest to use following settings (example for Australian safety data sheet; other countries to be maintained accordingly):
Generation Variant for Australia Header
Validity Area
AU
Usage Check
0(Subset)
Generate manual requests automatically
set flag
Change Marks
320
SAP AG
Initial Release Status
RE (released)
Version requirement
set flag
Set historical automatically
set flag
Date format
MM/DD/YYYY
Decimal Display
Period
Maintain the Rating as follows:

MSDS Safety Data Sheet
PUBLIC Released w/o restrictions
Maintain the necessary validity areas as shown in following table:
Important
Each validity area must be maintained in English and in Report language!
1 Region REG_WORLD World
EN English
Report language
3 Region AU
Australia
Report language
4 Region AU
Australia
EN English
F.2. Settings to implement the MSDS Template for

EMEA
EMEA
File name
Description
customizing transport TDPK901322 unicode
K902777.TD4 and R902777.TD4
customizing transport TD4K902777 non-unicode
K900243.TD5 and R900243.TD5

TDAG
K909498.TD6 and R909498.TD6
SDS_EU_2011_1.dat
Import-file Template
SDS_EU_2011_1.doc
Template-file
SDS_EU_2011_1_unix.dat
Import-file Template for unix systems
SDS_EU_2011_1_Datamapping.pdf
DataMapping - Document
SDS_EU_2011_1_changes_marked_yellow.doc
321
SAP AG
SDS_EU_2011_1_Datamapping_highlighted.pdf DataMapping
highlighted

Please maintain following ID Listings: ZISIEU1020, ZISIEU1021, ZISIEU1080, ZISIEU1710,
ZISIEU1050 and ZISIEU1051
IDListing
ZISIEU1020
IDList
SDS EU Identifiers
IDListPos
IDListPrio
NAM
NAM
NAM
NAM
ANNEXI
TRIV
EINECS
SYN
IDCategory
IDType
IDListing
ZISIEU1021
IDList
SDS EU Identifiers
IDListPos
IDListPrio
NUM
NUM
EINECS
EC
IDCategory
IDType
IDListing
ZISIEU1080
IDList
SDS EU Identifiers
IDListPos
IDListPrio
IDCategory
NAM
NAM
NAM
NAM
IDType
SYN
EINECS
HIS
TRIV
IDListing
ZISIEU1710
IDList
SDS EU Identifiers
IDListPos
IDListPrio
NAM
NAM
NAM
NAM
ANNEXI
PROD
EINECS
SYN
IDCategory
IDType
IDListing
IDList
ZISIEU1050
SDS EU Identifiers
IDListPos
IDListPrio
322
SAP AG
IDCategory NAM
IDType
RCS
NAM
NAM
NAM
NAM
ANNEXI
IUPAC
CAS
SYN
IDListing
ZISIEU1051
IDList
SDS EU Identifiers
IDListPos
IDListPrio
NUM
NUM
NUM
INDEX
EINECS
CAS
IDCategory
IDType

We suggest to use following settings (example for German safety data sheet; other countries
to be maintained accordingly):
Generation Variant for Germany Header
Validity Area
DE
Usage Check
0(Subset)
set flag
Change Marks
RE (released)
Version requirement
set flag
set flag
Date format
DD.MM.YYYY
Decimal Display
Comma

Important
1 Region REG_EU
European Community
EN English
2 Region REG_EU
European Community
Report language
3 Region DE
Germany
Report language
4 Region DE
Germany
EN English
F.3. Settings to implement the MSDS Template for

GHS
323
SAP AG

GHS
File name
Description
K902515.TD4
and R902515.TD4
K900243.TD5 and R900243.TD5
transport with definition of the TDAG namespace
K909498.TD6 and R909498.TD6
SDS_GHS_2010_1.dat
SDS_GHS_2010_1.doc
Template-file
SDS_GHS_2010_1_unix.dat
SDS_GHS_2010_1_Datamapping.pdf

Please maintain following ID Listings: ZISIEU1020, ZISIEU1021, ZISIEU1080 and
ZISIEU1150
IDListing
IDList
ZISIEU1020
SDS EU Identifiers
IDListPos
IDListPrio
NAM
NAM
NAM
NAM
ANNEXI
TRIV
EINECS
SYN
IDCategory
IDType
IDListing
IDList
ZISIEU1021
SDS EU Identifiers
IDListPos
IDListPrio
NUM
NUM
EINECS
EC
IDCategory
IDType
IDListing
IDList
IDListPos
ZISIEU1080
SDS EU Identifiers
1
324
SAP AG
IDListPrio
IDCategory
NAM
NAM
NAM
NAM
IDType
SYN
EINECS
HIS
TRIV
IDListing
ZISIEU1150
IDList
SDS EU Identifiers
IDListPos
IDListPrio
NAM
NAM
PROD
TRIV
IDCategory
IDType

We suggest to maintain the following generation variants:
Generation Variant for GHS Countries Header
Validity Area
REG GHS
Usage Check
1 (Intersection)
set flag
Change Marks
RE (released)
Version requirement
set flag
set flag
Date format
MM/DD/YYYY
Decimal Display
Period

Important
3 Region GHS
GHS-Countries
4 Region GHS
GHS-Countries
EN English
Report language
EN English
Report language
F.4. Settings to implement the MSDS Templates

for the Americas
325
SAP AG

Americas
File name
Description
K902775.TD4 and R902775.TD4
K900243.TD5 and R900243.TD5
K909498.TD6 and R909498.TD6
SDS_NA_2011_1.dat
SDS_NA_2011_1.doc
Template-file
SDS_NA_2011_1_unix.dat
SDS_NA_2011_1_Datamapping.pdf
SDS_NA_2011_1_changes_marked_ yellow.doc
SDS_NA_2011_1_Datamapping_highlighted.pdf DataMapping
highlighted
SDS_BR_2011_1.dat
SDS_BR_2011_1.doc
Template-file
SDS_BR_2011_1_unix.dat
SDS_BR_2011_1_Datamapping.pdf
SDS_BR_2011_1_changes_marked_ yellow.doc
SDS_BR_2011_1_Datamapping_highlighted.pdf DataMapping
highlighted

Please maintain following ID Listings: ZISINA1080, D_VALPOS, ZTS_IDLID
IDListing
IDList
ZISINA1080
SDS NA Identifiers
IDListPos
IDListPrio
IDCategory
NAM
NAM
NAM
NAM
IDType
SYN
CAS
ANNEX1
EINECS
326
SAP AG
IDListing
D_VALPOS
IDList
Identifier in Component overview
IDListPos
IDListPrio
IDCategory
NAM
NAM
NAM
NUM
IDType
SYN
CAS
EINECS
CAS
IDListing
ZTS_IDLID
IDList
IDListPos
IDListPrio
IDCategory
IDType
Trade Secret Listing
NAM
ZTRADESEC

We suggest to maintain the following generation variants:
Generation Variant for North America Header
Validity Area
REG NA
Usage Check
1 (Intersection)
set flag
Change Marks
RE (released)
Version requirement
set flag
set flag
Date format
MM/DD/YYYY
Decimal Display
Period

Important
Report language
3 Region US
USA
Report language
4 Region CA
Canada
Report language
5 Region MX
Mexico
Report language
327
EN English
SAP AG
6 Region US
USA
EN English
7 Region MX
Canada
EN English
8 Region CA
Mexico
EN English
9 Region REG_NA
North America
EN English
10 Region REG_NA
North America
Report language
Generation Variant for REG US Header

Validity Area
US
Usage Check
0(Subset)
set flag
Change Marks
RE (released)
Version requirement
set flag
set flag
Date format
MM/DD/YYYY
Decimal Display
Comma
Maintain the Rating as above.

Maintain the necessary validity areas as above for REG WORLD, REG NA and US.
BRAZIL:
Generation Variant for Brazil
Validity Area
BR
Usage Check
0(Subset)
set flag
Change Marks
RE (released)
Version requirement
set flag
set flag
Date format
MM/DD/YYYY
Decimal Display
Comma

3 Region BR
Brazil
328
EN English
Report language
EN English
SAP AG
4 Region BR
Brazil
329
Report language
SAP AG
Index
A
Analysis Tool for Excel, 80
B
BC sets
Import, 132
C
Cache, OCC, Mapping Database, 88
check list, 121
Checklist, 121
Console program, 102, 193
(see also Expert Server)
Customizing, 103
D
Dangerous Goods Master Data, 63, 165
Substance lists and reference data, 60
Data Origin, 52, 109, 110, 162
OCC, 52
Database, XML files, 76, 76, 76, 169
E
Expert Rule sets, 114
Execution, 117
Installation, 114
Prerequisites, 92
Expert Rules, 92
Americas, 285
Customizing, 304
Expert admin settings, 291
File overview, 285
User exit settings, 295
Asia Pacific, 235
Customizing, 259
File overview, 235
Basis, 227
Customizing, 229
File overview, 227
DangGoods, 309
Customizing, 312
File overview, 309
DPDplus
Customizing, 317
File overview, 314, 315
Europe, 260
Customizing, 268, 284
Expert admin settings, 263, 273
User exit settings, 265, 277
File overview, 92
General Information, 92
GHS, 229
Customizing, 234
File overview, 229
Implementation, 92
MSDSMaker, 312
Customizing, 314
File overview, 312
National Regulations Europe, 269
Registration, 116, 195
RegStat
Customizing, 308
Expert Server, 92
Configuration, 98
CGSADM, 98
EHS Service Administration, 98, 189
Microsoft Windows services, 100
Installation, 93
Expert Sub Rules
Americas
Asia Pacific
DangGoods
DPDplus
Europe
Expert admin settings, 264, 277
GHS
MSDSMaker
RegStat
330
SAP AG
Index
Explanation component, 120, 180, 198
External table
Adjustment, 117, 201
Mapping
Facts, 86, 118, 178
Groups, 119, 202
Phrases, 87, 119, 179
Records, 87, 119, 178
F
Files
Upload, 27, 70, 125
G
Generation Variants
Creation, 127, 127, 203
H
Hit List
Update functionality, 68
EMEA
File overview, 321
Europe, 321
Customizing, 322
Generation variant, 323
GHS, 323
Customizing, 324
File overview, 324
Implementation, 123, 128
Checklist, 128
Import, 126
Prerequisites, 122
Multi Rule Call, 109
N
Number ranges, 54, 142
Identification listings
Setup, 125, 125, 202
Identifier types, 58, 164
Import, 123
Merge, 30, 72, 144
Phrases, cg31, 28, 71, 143
Report templates, 126, 203
Transport, stms, 10, 123, 130
OCC, 39, 39
Download, 40
Filter, Regulatory List, 89
Installation, 40, 150
Open Content Connector, 40
Registry instance, 81, 173
RFC connection, 41
SAP Note, 38
Schematic Diagram, 38
User Exit, 84, 176
Literature source, 57, 110, 163

Expert Rules, 110
Log files, Exp-log, RFC-log, 199
Phrase catalogue, 26, 54, 141

CED, 26
Phrase sets, 13
Allocation, 13, 134
Phrase set assignment, 32, 74, 146
Phrase Variants
Creation, 34, 150
Phrases, 23
Appendix, 209
Asia Pacific, 210
File overview, 210
Check Implementation, 35
Checklist, 35
Combine/Retire, 148
File overview, 26
General Settings, 211
Language keys, 217
Language/Codepages, 215
M
Mapping database
Cache, 78, 170
MS Access, 77
Setup, 77
MSDS Report Template, 122, 122
Americas, 325
Customizing, 326
File overview, 326
APJ
File overview, 318
Asia Pacific, 318
Customizing, 319
331
SAP AG
Index
Name spaces, 212
Phrase groups, 211
Implementation, 26
Import, 28, 71
Individual changes, 34
Language/Codepage/Font, 24
Prerequisites, 23
Proposal, 26
Standard, 209
File overview, 209
Structure, 23
Property Tree, 7
Checklist, 22
File Overview, 8
File overview, 205
Implementation, 8
Package overview, 205
Prerequisites, 7
R
Regulatory Data, 37
Checklist, 90, 91
Dangerous Goods, 222
Customizing, 225
File overview, 223
File overview, 39
Implementation, 39
Product Safety, 220
Customizing, 222
File overview, 220
Regulatory lists, 56, 112, 162
Expert Rules, 111
RFC connection, 41, 41, 93, 93, 151
Expert Rules, 93
Test, 44, 97, 154
User exit, 84
Update, simulation, hit list, 180
T
Table Based Value Assignment, 16, 17, 137
Transports (see Import)
U
Upload files
Expert rules, EHS Expert server, 114, 194
Phrases, 27, 70, 125, 129
Property tree, 9, 129
User Defined Dangerous Goods Texts, 113,
193
Expert Rules, 112
User Defined Text Types, 55, 111, 111, 162
OCCUNQID, NOL, Free text, 54
User Exit, 45, 161
Expert Rules, 103
Explanation component, 46, 103, 155
Search functionality, 69, 69, 168
V
Validity area, 65, 66, 167
Value Assignment Rating, 113, 114, 193
W
Windows Service, EHS Expert Server, 101,
191
WWI Symbol, 16
Generation, 16, 136
S
SAPRFC.INI, 100, 189
Secondary data, 197
Setup, EHS Expert, 186
Simulation Tool, 80, 173
Substance lists and reference data
Adjustment, 81
Mapping, 86
OCC, 81
332
SAP AG

SAP EHS Regulatory Content Administration Manual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP EHS Regulatory Content Administration Manual

Uploaded by

Copyright:

Available Formats

SAP EHS Regulatory Content