SAP EHS Regulatory Content

Administration Manual
SAP EHS Regulatory Content Administration Manual
Version 1901

Publication date January 2019

Copyright © 2019 SAP SE, Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany
The content of this document is the intellectual property of SAP SE. Any forwarding to third parties or publication even of parts
thereof requires express and written approval by SAP SE.

INTERNAL: SAP CUSTOMER

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 ................................................................................................................... 2
1.5. Glossary ................................................................................................................. 3
2. Installation ......................................................................................................................... 6
2.1. Prerequisites .......................................................................................................... 6
2.2. Implementation overall procedure .......................................................................... 7
3. Property Tree .................................................................................................................... 9
3.1. General Information ............................................................................................... 9
3.1.1. Prerequisites ................................................................................................ 9
3.1.2. Content of Property Tree packages .......................................................... 10
3.2. Implementation ..................................................................................................... 10
3.2.1. Upload property tree transport files ........................................................... 10
3.2.1.1. How to upload property tree transports files ................................... 11
3.2.1.2. Settings ........................................................................................... 12
3.2.2. Import transport requests .......................................................................... 12
3.2.2.1. How to import transport requests ................................................... 12
3.2.2.2. Execute Programs .......................................................................... 13
3.2.2.3. Settings ........................................................................................... 14
3.2.3. Allocate phrase sets .................................................................................. 14
3.2.3.1. How to allocate phrase sets ........................................................... 14
3.2.3.2. Settings ........................................................................................... 17
3.2.4. Generate WWI symbols for reports ........................................................... 17
3.2.4.1. How to create WWI report symbols ................................................ 17
3.2.5. Set up Table-based Value Assignment ..................................................... 18
3.2.5.1. How to set up the Table-based Value Assignment ......................... 18
3.2.6. Check and extend copy/inheritance templates .......................................... 23
3.2.6.1. How to check and extend copy/inheritance templates .................... 24
3.3. Check Implementation ......................................................................................... 24
3.3.1. Checking Procedure .................................................................................. 24
4. SAP EHS Regulatory Content - multilanguage phrase library for hazard communica-
tion ....................................................................................................................................... 26
4.1. General Information ............................................................................................. 26
4.1.1. Prerequisites .............................................................................................. 26
4.1.2. Structure of CED phrase catalogue for EHS ............................................. 26
4.1.2.1. Phrase groups ................................................................................ 26
4.1.2.2. Phrase keys .................................................................................... 26
4.1.2.3. Allocation of bitmaps to phrases .................................................... 26
4.1.2.4. Phrase sets (PSET/PAWM) ............................................................ 27
4.1.3. Language/Codepage/Font ......................................................................... 27
4.1.3.1. Prerequisites / important notes ....................................................... 27
4.1.3.2. Phrase Languages in Unicode / Non-Unicode ................................ 28
4.1.3.3. Setup of language keys for phrase items within the phrase ad-
ministration ................................................................................................... 28
4.1.4. Proposals ................................................................................................... 28
4.1.4.1. Proposals for changes, corrections or expansions ......................... 28
4.1.4.2. Correction of mistakes .................................................................... 29
4.1.5. Content of Phrases packages ................................................................... 29
4.2. Implementation ..................................................................................................... 29

INTERNAL: SAP CUSTOMER iii © SAP SE

 SAP EHS Regulatory Content Administration Manual

4.2.1. Create passive phrase catalogue CED ..................................................... 29

4.2.1.1. How to create passive phrase catalogues ...................................... 29
4.2.2. Upload files ............................................................................................... 30
4.2.2.1. How to upload files ......................................................................... 30
4.2.2.2. Load of import files into EHS ......................................................... 31
4.2.3. Import phrases .......................................................................................... 31
4.2.3.1. How to import phrases ................................................................... 31
4.2.3.2. How to merge phrases ................................................................... 32
4.2.3.3. How to import phrase set assignments .......................................... 34
4.2.4. Placeholder Phrases ................................................................................. 36
4.2.4.1. Adding CED Permutations .............................................................. 36
4.2.4.2. Automatic Replacement .................................................................. 36
4.2.4.3. Replacing Placeholders Through a Phrase User Exit ..................... 36
4.2.5. Individual changes on CED phrases ......................................................... 37
4.2.5.1. Adding of customer specific phrase groups .................................... 37
4.2.5.2. Customer specific changes / extensions of phrases ....................... 37
4.3. Check Implementation ......................................................................................... 37
4.3.1. Checking Procedure .................................................................................. 37
5. SAP EHS Regulatory Content - substance lists and reference data ............................... 39
5.1. General Information ............................................................................................. 39
5.1.1. Prerequisites .............................................................................................. 40
5.1.2. Schematic Diagram Open Content Connector .......................................... 40
5.1.3. Content of substance lists and reference data packages .......................... 41
5.2. Implementation ..................................................................................................... 41
5.2.1. EHS OCC .................................................................................................. 41
5.2.1.1. Install EHS OCC ............................................................................ 41
5.2.1.2. RFC connection .............................................................................. 43
5.2.2. SAP EHS Customizing .............................................................................. 47
5.2.2.1. Secondary Data Determination User Exit ....................................... 47
5.2.2.2. Data Origin ..................................................................................... 54
5.2.2.3. Phrase Catalogue ........................................................................... 55
5.2.2.4. User defined text types .................................................................. 57
5.2.2.5. Regulatory Lists .............................................................................. 58
5.2.2.6. Literature Source ............................................................................ 59
5.2.2.7. Identifier Types ............................................................................... 60
5.2.2.8. Dangerous Goods Master Data ...................................................... 62
5.2.2.9. Validity Area .................................................................................... 67
5.2.2.10. Update Hit List Functionality ......................................................... 72
5.2.3. Phrases ..................................................................................................... 73
5.2.3.1. Upload files ..................................................................................... 73
5.2.3.2. Import phrases ................................................................................ 74
5.2.4. XML substance database .......................................................................... 80
5.2.4.1. Install XML substance database .................................................... 80
5.2.5. Mapping Database .................................................................................... 81
5.2.5.1. Setup Mapping Database ............................................................... 82
5.2.6. Analysis Tool for Excel .............................................................................. 84
5.2.6.1. Install Analysis Tool for Excel ......................................................... 84
5.2.7. Adjustments ............................................................................................... 85
5.2.7.1. Configure EHS OCC ...................................................................... 85
5.2.7.2. Configure User Exit ........................................................................ 88
5.2.7.3. Adjust Mapping ............................................................................... 90
5.2.8. Cache ........................................................................................................ 93

INTERNAL: SAP CUSTOMER iv © SAP SE

 SAP EHS Regulatory Content Administration Manual

5.2.9. Review New Filter Settings ....................................................................... 94

5.2.9.1. Adapt Dangerous Goods Filter Settings ......................................... 94
5.3. Check Implementation ......................................................................................... 95
5.3.1. Check List Product Safety ......................................................................... 95
5.3.2. Check List Dangerous Goods for SAP EHS ............................................. 96
5.3.3. Check List Dangerous Goods for SAP Transportation Management ......... 96
6. SAP EHS Regulatory Content - expert rules for substance and mixture classification
.............................................................................................................................................. 98
6.1. General Information ............................................................................................. 98
6.1.1. Prerequisites .............................................................................................. 98
6.1.2. Content of Expert Rule set packages ....................................................... 98
6.2. Implementation ..................................................................................................... 98
6.2.1. EHS Expert ............................................................................................... 98
6.2.1.1. Install EHS Expert .......................................................................... 99
6.2.1.2. Setup RFC connection ................................................................... 99
6.2.1.3. Configure EHS Expert .................................................................. 104
6.2.2. SAP EHS Customizing ............................................................................ 109
6.2.2.1. User Exit ....................................................................................... 109
6.2.2.2. Multi Rule Call .............................................................................. 115
6.2.2.3. Data Origin ................................................................................... 116
6.2.2.4. Literature Source .......................................................................... 116
6.2.2.5. User Defined Text Type ................................................................ 117
6.2.2.6. Regulatory Lists ............................................................................ 117
6.2.2.7. User-Defined Dangerous Goods Texts ......................................... 119
6.2.2.8. Value Assignment Rating ............................................................. 119
6.2.3. SAP EHS Regulatory Content - expert rules for substance and mixture
classification ....................................................................................................... 120
6.2.3.1. Install Expert Rule Sets using SAP Setup .................................... 120
6.2.3.2. Install Expert Rule Sets ................................................................ 121
6.2.3.3. Run Expert Rule Sets ................................................................... 124
6.2.3.4. Adjust Expert Rule Sets ............................................................... 124
6.3. Check Implementation ....................................................................................... 128
6.3.1. Check List ............................................................................................... 128
7. SAP EHS Regulatory Content - safety data sheet (SDS) templates ............................. 130
7.1. General Information ........................................................................................... 130
7.1.1. Prerequisites ............................................................................................ 130
7.1.2. Content of safety data sheet (SDS) template packages .......................... 131
7.1.3. Identifier for Component Names ............................................................. 132
7.2. Implementation ................................................................................................... 132
7.2.1. Import transports ..................................................................................... 132
7.2.1.1. How to import transport requests ................................................. 132
7.2.2. Setup identification listings ...................................................................... 133
7.2.2.1. How to setup identification listings ............................................... 133
7.2.3. Upload files ............................................................................................. 134
7.2.3.1. How to upload files ....................................................................... 134
7.2.4. Import report template ............................................................................. 135
7.2.4.1. How to import report templates .................................................... 135
7.2.5. Create generation variant ........................................................................ 135
7.2.5.1. How to create generation variant ................................................. 136
7.3. Check Implementation ....................................................................................... 137
7.3.1. Checking Procedure ................................................................................ 137
A. How To ... ..................................................................................................................... 138

INTERNAL: SAP CUSTOMER v © SAP SE

 SAP EHS Regulatory Content Administration Manual

A.1. How to upload property tree transports files ...................................................... 138

A.2. How to upload files ............................................................................................ 139
A.3. How to import transport requests ...................................................................... 139
A.4. How to import BC sets ...................................................................................... 141
A.5. How to allocate phrase sets .............................................................................. 142
A.6. How to create WWI report symbols ................................................................... 145
A.7. How to set up the Table-based Value Assignment ............................................ 146
A.8. How to check and extend copy/inheritance templates ....................................... 152
A.9. How to create passive phrase catalogues ......................................................... 152
A.10. How to setup number ranges .......................................................................... 153
A.11. How to implement correct language keys for English and Portuguese vari-
ants (EN/6N/Z8, PT1/1P/Z9) ..................................................................................... 153
A.12. How to import phrases .................................................................................... 154
A.13. How to merge phrases .................................................................................... 156
A.14. How to import phrase set assignments ........................................................... 158
A.15. How to combine/retire phrases ........................................................................ 160
A.15.1. Combining Duplicate Phrases ............................................................... 160
A.15.2. Retired Phrases .................................................................................... 161
A.16. How to create phrase variants ........................................................................ 162
A.17. How to install EHS OCC ................................................................................. 162
A.17.1. Initial Installation/Upgrading of older OCC versions .............................. 163
A.18. How to setup a RFC connection ..................................................................... 163
A.19. How to test the RFC connection ..................................................................... 166
A.20. How to extend entry in secondary data determination ..................................... 167
A.21. How to manage user exits ............................................................................... 173
A.22. How to add user defined text types ................................................................. 174
A.23. How to add data origins .................................................................................. 174
A.24. How to add regulatory lists .............................................................................. 175
A.25. How to add literature sources ......................................................................... 175
A.26. How to add identifier types .............................................................................. 176
A.27. How to add dangerous goods master data ..................................................... 177
A.27.1. Dangerous Goods Classes and Classification Codes ........................... 177
A.27.2. Risk Potentials ...................................................................................... 178
A.27.3. Hazard Identification Numbers .............................................................. 178
A.27.4. Danger Labels ....................................................................................... 178
A.27.5. Packing Instruction Numbers ................................................................ 178
A.27.6. Categories of Instructions for Enclosure and Instructions for Enclosure
............................................................................................................................ 179
A.27.7. Packing Codes ...................................................................................... 179
A.28. How to add validity areas ................................................................................ 179
A.29. How to create extended search user exit ........................................................ 181
A.30. How to setup/update XML substance database for substance lists and refer-
ence data ................................................................................................................... 181
A.31. How to setup/update mapping database for SAP EHS Regulatory Content -
substance lists and reference data ........................................................................... 183
A.32. How to install the Update Analysis Tool for Excel ........................................... 185
A.33. How to configure EHS OCC ............................................................................ 186
A.34. How to configure the User Exit for SAP EHS Regulatory Content - substance
lists and reference data ............................................................................................ 189
A.35. How to adjust the Fact Mapping ...................................................................... 191
A.35.1. Adjusting Fact Mapping to Load a CAS Number .................................. 191
A.36. How to adjust the Record Mapping ................................................................. 192

INTERNAL: SAP CUSTOMER vi © SAP SE

 SAP EHS Regulatory Content Administration Manual

A.37. How to adjust the Phrase Mapping ................................................................. 192

A.38. How to write the Last Run Date ...................................................................... 193
A.39. SAP EHS Regulatory Content - substance lists and reference data (Product
Safety) Update Data Load ........................................................................................ 193
A.39.1. Review Regulatory Changes ................................................................ 194
A.39.2. Update Cached Data ............................................................................ 194
A.39.3. Review New Filter Settings ................................................................... 194
A.39.4. Hit List of List Substances .................................................................... 194
A.39.4.1. Simulate Data Load ................................................................... 196
A.39.4.2. Analyze Changed Data .............................................................. 197
A.39.4.3. Load Changes to SAP EH&S .................................................... 198
A.40. How to install EHS Expert ............................................................................... 199
A.40.1. Initial Installation of Expert .................................................................... 200
A.40.2. Upgrading of older Expert versions ...................................................... 201
A.40.3. Implement Expert patches .................................................................... 202
A.41. How to configure SAPRFC.INI ........................................................................ 202
A.42. How to configure EHS Expert Server using EHS Service Administration ......... 202
A.43. How to configure EHS Expert Server as a Windows Service .......................... 204
A.44. How to configure EHS Expert Server as a console program ........................... 206
A.45. How to add user-defined DG texts .................................................................. 206
A.46. How to add a value assignment rating ............................................................ 206
A.47. SAP Setup for SAP EHS Regulatory Content Expert Rule Sets ...................... 207
A.47.1. Overview ............................................................................................... 207
A.47.2. Installation on the Test or QA Expert Server ......................................... 212
A.47.3. Installation on the Productive Expert Server ......................................... 213
A.48. How to load rule sets onto the Expert server .................................................. 213
A.49. How to register rule sets ................................................................................. 215
A.50. How to execute rules ....................................................................................... 216
A.51. How to display the Explanation Component .................................................... 217
A.52. How to use the UPO functionality ................................................................... 218
A.53. How to generate Log Files .............................................................................. 220
A.54. How to adjust external table values ................................................................ 223
A.55. How to adjust the Group Mapping ................................................................... 224
A.56. How to use the History.mdb ............................................................................ 224
A.57. How to setup identification listings .................................................................. 225
A.58. How to import report templates ....................................................................... 226
A.59. How to create generation variant .................................................................... 226
A.60. How to disclose component names ................................................................. 227
B. Technical Settings Property Tree Packages ................................................................. 234
B.1. Contents of Latest SAP ERC Property Tree Package ....................................... 234
B.1.1. File overview property tree package Product Safety ............................... 234
B.1.2. File overview corrections to previous property tree package .................. 235
B.2. Overview about existing property tree packages ............................................... 235
C. Technical Settings Multilanguage Phrase Library ......................................................... 239
C.1. Settings to implement the Multilanguage Phrase Library (Standard) ................. 239
C.1.1. File Overview .......................................................................................... 239
C.2. General Settings ................................................................................................ 240
C.2.1. Phrase Groups ........................................................................................ 240
C.2.2. Name spaces .......................................................................................... 241
C.2.2.1. Phrase keys ................................................................................. 241
C.2.3. Language/Codepages ............................................................................. 244
C.2.4. Language keys ....................................................................................... 246

INTERNAL: SAP CUSTOMER vii © SAP SE

 SAP EHS Regulatory Content Administration Manual

D. Technical Settings Substance Lists and Reference Data ............................................. 249

D.1. Settings to implement the Substance Lists and Reference Data (Product Safe-
ty) ............................................................................................................................... 249
D.1.1. File Overview .......................................................................................... 249
D.1.2. User Exit Settings ................................................................................... 250
D.1.3. Other Settings ......................................................................................... 251
D.2. Settings to implement the Substance Lists and Reference Data for Dangerous
Goods (SAP EHS) ..................................................................................................... 251
D.2.1. File Overview .......................................................................................... 251
D.2.2. User Exit Settings ................................................................................... 254
D.2.3. Other Settings ......................................................................................... 255
D.3. Settings to implement the Substance Lists and Reference Data for Dangerous
Goods (SAP Transportation Management) ............................................................... 251
D.3.1. File Overview .......................................................................................... 255
E. Technical Settings Expert Rules ................................................................................... 256
E.1. Settings to implement the basis rule set package ............................................. 256
E.1.1. File Overview .......................................................................................... 256
E.1.2. Settings in Admin Tool ............................................................................ 257
E.1.3. Settings in Admin Tool - Sub Rules ........................................................ 258
E.1.4. User Exit Settings ................................................................................... 259
E.1.5. Other Settings ......................................................................................... 261
E.2. Settings to implement the rule set package for GHS ......................................... 262
E.2.1. File Overview .......................................................................................... 262
E.2.2. Settings in Admin Tool ............................................................................ 263
E.2.3. Settings in Admin Tool - Sub Rules ........................................................ 264
E.2.4. User Exit Settings ................................................................................... 265
E.2.5. Other Settings ......................................................................................... 266
E.3. Settings to implement the rule set package Europe .......................................... 268
E.3.1. File Overview .......................................................................................... 268
E.3.2. Settings in Admin Tool ............................................................................ 286
E.3.3. Settings in Admin Tool - Sub Rules ........................................................ 297
E.3.4. User Exit Settings ................................................................................... 298
E.3.5. Other Settings ......................................................................................... 324
E.4. Settings to implement the RegStat rule set package ......................................... 326
E.4.1. File Overview .......................................................................................... 326
E.4.2. Settings in Admin Tool ............................................................................ 327
E.4.3. Settings in Admin Tool - Sub Rules ........................................................ 328
E.4.4. User Exit Settings ................................................................................... 329
E.4.5. Other Settings ......................................................................................... 330
E.5. Settings to implement the DangGoods rule set package ................................... 331
E.5.1. File Overview .......................................................................................... 331
E.5.2. Settings in Admin Tool ............................................................................ 331
E.5.3. Settings in Admin Tool - Sub Rules ........................................................ 332
E.5.4. User Exit Settings ................................................................................... 333
E.5.5. Other Settings ......................................................................................... 334
E.6. Settings to implement the MSDSMaker rule set package ................................. 334
E.6.1. File Overview .......................................................................................... 334
E.6.2. Settings in Admin Tool ............................................................................ 335
E.6.3. Settings in Admin Tool - Sub Rules ........................................................ 335
E.6.4. User Exit Settings ................................................................................... 336
E.6.5. Other Settings ......................................................................................... 336
F. Technical Settings MSDS Templates ............................................................................ 337

INTERNAL: SAP CUSTOMER viii © SAP SE

 SAP EHS Regulatory Content Administration Manual

F.1. Settings to implement the MSDS Template for EMEA ....................................... 337
F.1.1. File Overview ........................................................................................... 337
F.1.2. Other Settings .......................................................................................... 343
F.1.3. Generation variant ................................................................................... 345
Index .................................................................................................................................. 346

INTERNAL: SAP CUSTOMER ix © SAP SE

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 (phras-
es, 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 send an e-mail to <Regulatory.Content@sap.com>.

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 - Ap-
pendix. 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 infor-
mation 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.
• Installation: This chapter provides information about the general prerequisites for the imple-
mentation of SAP EHS Regulatory Content as well as an overall implementation procedure.

INTERNAL: SAP CUSTOMER 1 © SAP SE

 Introduction

• 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 infor-
mation 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 pro-
vides 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.

The SAP Security Guides provide you with a collection of our guidelines and recommendations
pertaining to SAP system and SAP software security. These documents offer general guide-
lines for securing your SAP systems. Do keep in mind that additional factors are also very
important when securing your overall landscape, such as the usage of a variety of software
packages (SAP and non-SAP). Therefore, we highly recommend you analyze your own risks
and needs and establish your own security policy (or policies). These guides are intended to
assist you in this process, but cannot replace the need for your own customer-specific policies.
For the latest information on security updates see SAP Security Notes.

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 autho-
rization 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
Issues with SAP EHS and SAP EHS Regulatory Content can be reported using the SAP One
Support Lauchpad https://launchpad.support.sap.com/.

INTERNAL: SAP CUSTOMER 2 © SAP SE

 Introduction

Please select one of the following components to ensure fast assignment to the appropriate
subject matter expert.

• EHS-ERC for all incidents related to regulatory list data, phrases, Expert rules and WWI
templates
• EHS-BD-RDF-WWI for incidents related to WWI functionality (other than WWI templates)
• EHS-BD-TLS-OCC for incidents related to OCC functionality (other than regulatory data)
• EHS-BD-TLS-EXP for incidents related to EHS Expert functionality (other than ERC Expert
rules)

1.5. Glossary
EH&S Expert

With EHS Expert you can

• define rule sets and create and maintain the corresponding mapping tables
• calculate secondary data based on the rule sets and mapping table for EHS
specification data

As an example it is possible to calculate GHS hazard statements based on

other data of the specification.

Open Content Connector (OCC)

Open Content Connector 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 offers functionality for manual single substance data loads, automatic
mass loads, as well as update and simulation functionality.

Windows Wordprocessor Integration (WWI)

A modified version of Microsoft Word that is called from the SAP system to edit
a document template.

Phrase

A standard text.

Phrases can be used for:

• Value assignment of characteristic fields in the property tree

• Value assignment of certain input fields in screens and dialog boxes
• Reports
• Phrases are managed in libraries. A phrase can group the same text in sev-
eral languages.

Phrase Library

A collection of phrases used as a value assignment.

Apart from the active company library, other libraries can be kept for information
purposes.

INTERNAL: SAP CUSTOMER 3 © SAP SE

 Introduction

Rule Set (Rules)

Rule sets are used to calculate secondary data based on information stored in
EHS specifications.

Template

A template defines the format of a report in the SAP Environment, Health and
Safety component and specifies where data from specification management
and other SAP applications is placed in the document.

When the report is generated, the symbols are replaced with data and the text
is formatted using the features in a word-processing program such as text type,
font size, and color.

Property

The details on a specification in the form of numeric values including the appro-
priate unit of measure, or in the form of textual information.

The details can be linked with information on the source of the data or on the
method of analysis.

Properties can be grouped as follows:

• Physical
• Chemical
• Toxicological
• Ecological
• First aid measures
• Safety measures
• Hazard classes

Customizing

Overall implementation procedure to set up one or more SAP systems at a

customer site. The procedure aims to:

Adjust the company-neutral and industry-specific delivered functions to your

company's business requirements

Enhance SAP functions in the company

Implement SAP functions in your company quickly, safely and cost effectively

Value Assignment

The values set for a value assignment type.

Example:

Values assigned to the value assignment type "density" include:

Accuracy: approx.

Value: 2 g/cm3

INTERNAL: SAP CUSTOMER 4 © SAP SE

 Introduction

Specification

A description that uses identifiers and value assignments such as physical and
chemical properties, medical notes, and details on transport and storage.

Specifications can be managed for different categories, such as:

• Substances
• Agents
• Packaging
• Waste codes
• Dangerous goods classifications

Characteristic

A part of a value assignment type.

A value assignment type can consist of a number of characteristics. The value

assignment type boiling point can consist of the following characteristics:

• Value
• Accuracy
• Ambient pressure
• Method

INTERNAL: SAP CUSTOMER 5 © SAP SE

Chapter 2. Installation
This chapter describes the prerequisites which are necessary to implement SAP EHS Regu-
latory 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 li-
censed.

EHS Expert/OCC
• Current version of EHS Open Content Connector (OCC) and EHS Expert (see SAP note
568302).

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.

INTERNAL: SAP CUSTOMER 6 © SAP SE

 Installation

SAP authorisation
• All Expert rules and OCC users need SAP authorization S_RFC authorization for RFC ac-
cess.
• 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 addi-
tional 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
1367148 needed if "no calculation" functionality of rule sets is used
1381072 Phrase warning: Missing code/graphic
1565029 NotStat rule: Exit functionality for interrupting component explosion
2004802 Comp rule: Composition tree: Average value of ingredients

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.

INTERNAL: SAP CUSTOMER 7 © SAP SE

 Installation

The graph shows the sequence of the implementation.

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 documenta-
tion.

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.

INTERNAL: SAP CUSTOMER 8 © SAP SE

Chapter 3. Property Tree
3.1. General Information
The SAP EH&S Standard Functionality includes the definition of properties in order to main-
tain data in the EH&S specification data base. These properties are delivered together with
the property tree STANDARD. The SAP EH&S property tree STANDARD is continuously im-
proved. Extensions to the SAP EH&S property tree STANDARD are delivered with the SAP
standard delivery (see also SAP Note 1761696).

SAP EHS Regulatory Content (abbreviated SAP ERC) expert rules for substance and mixture
classification, SAP ERC substance lists and reference data and SAP ERC safety data sheet
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 SAP ERC customers for older EH&S versions as well. These packages contain
everything needed to set up and use the new and enhanced characteristics and classes/prop-
erties added to SAP EH&S in an existing ERP 6.0 EHP3, ERP 6.0 EHP4, ERP 6.0 EHP5, ERP
6.0 EHP6, ERP 6.0 EHP7, or ERP 6.0 EHP8 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. Help texts are delivered in English and German for SAP Enterprise
Releases. As an additional service, the help texts are delivered also as text documents.

Please read the ReadMe document included in each property tree package carefully BEFORE
starting the implementation of any property tree package, but especially BEFORE starting
the implementation of the property tree package 2015-2 Product Safety (enhancements for
ESComXML Format Version 2-0) and the propert tree package 1711 Product Safety (set up of
new dimensions and new unit of measurements)!

3.1.1. Prerequisites
The EH&S property tree needs to be updated to the latest release status.

Customers must ensure that the earlier property tree packages have already been installed
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. New customers may profit from
the combination package in which several property tree packages are combined (see details
and example in Appendix).

An overview about the existing property tree packages and the order of installation is given
in the Appendix.

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 "Char-
Copy 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 in-
clude 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

INTERNAL: SAP CUSTOMER 9 © SAP SE

 Property Tree

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.

3.1.2. Content of Property Tree packages

Each EH&S property tree package consists of the following parts:

• List of enhanced and new properties and characteristics

• Files for the R/3 Transport Management System (TMS) for new and enhanced classes,
characteristics, value assignment types and positions in the property tree STANDARD (with
English and German descriptions)
• Files for the R/3 Transport Management System (TMS) for help texts (in English and Ger-
man).
• Text documents with help texts in English and German

A detailed list of transports and files delivered with the property tree package of the corre-
sponding SAP EH&S 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
Appendix. The steps "Allocate phrase sets", "Generate WWI symbols for reports", "Setup Ta-
ble-based Value assignments" and "Check and extend copy/inheritance templates" have to be
done after the import of the transports on each EH&S system. .

To support the SAP ESComXML/EH&S interface based on ESComXML Format Version 1.5,
new properties, new characteristics, changed existing characteristics, new specification types,
new property trees were delivered with property tree package 2014-2 Product Safety or were
set up manually. Details and links to the SAP Help Portal were described in the ReadMe doc-
ument which was delivered with this property tree package 2014-2.

With property tree package 2015-2 Product Safety, the REACH eSDS Annex properties were
changed to support the ESComXML Format Version 2.0 which was published on the Webpage
of the Eurpean Chemical Industry Association (Cefic). Several existing REACH eSDS Annex
properties newly added with 2008-1 PS, 2010-1 PS, or 2014--2 PS were shifted to the property
tree OBSOLETE and were replaced by new properties. Details can be found in the ReadMe
and Changes document included in property tree package 2015-2 PS.

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. In some packages, the customizing objects are included in the workbench
transport requests that only workbench transport requests have to be imported. However, the
import procedure for workbench and customizing transport request is the same.

Before property tree transport requests can be imported into an EH&S system, the correspond-
ing 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:

INTERNAL: SAP CUSTOMER 10 © SAP SE

 Property Tree

• 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 request
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 Manage-
ment 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:

1. Find out the directory name and path of the import queue for the SAP Transport Manage-
ment System.

1.1. You may ask your SAP system manager or proceed as follows:
1.2. Run transaction AL11.
1.3. The first part of the directory path is listed after the entry DIR_TRANS, for example
"F:\usr\sap\trans".
1.4. 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.

5. Load the transport files into the import directory using the transaction CG3Z.

5.1. Start transaction CG3Z.

5.2. Enter in the field "Source file on front end" the transport file name including the com-
plete 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.
5.3. 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".
5.4. Start the upload process with the push button "Upload". When the upload process has
been successful a message appears.

5. Attach the transport request to the import queue

5.1. Navigate to the SAP Transport Management System (transaction STMS).

5.2. Choose push button "Import Overview (F5)".
5.3. Navigate to the transport domain of your SAP system: Position the cursor on the trans-
port domain and choose the push button "Display Import Queue" or choose "Double
click".

INTERNAL: SAP CUSTOMER 11 © SAP SE

 Property Tree

5.4. Choose in the menu "Extras" -> "Other requests" -> "Add".
5.5. 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.
5.6. 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 transport requests

This chapter describes in detail the import of transport requests and reports.

3.2.2.1. How to import transport requests

The import process consists of several steps which are identical for customizing and work-
bench transport requests:

1. Check user in import client.

2. Navigate to the SAP Transport Management System.
3. Select the transport domain for your SAP system.
4. Search and select the transport request which shall be imported.
5. Start the import for the client where the property tree objects shall be used.

Please note that property tree transport requests are client dependent and shall be available
after the import only in the selected client.
6. Check the import by displaying the transport log.

In the following, the steps listed above are described in more detail:

1. Check user in import client.

1.a. Make sure, that no other user besides the SAP administrator (who is doing the import)
is working in the EH&S specification data base or in the EH&S customizing on the SAP
client where the import of property tree transports takes place. Otherwise, property
tree objects might be logged and might not be updated during the import.
2. Navigate to the SAP Transport Management System.
2.a. Start transaction STMS.
2.b. Choose pushbutton "Import Overview (F5)" or press F5.
2.c. The import overview open with a list of transport requests which are available for im-
port.
3. Select the transport domain for your SAP system.
3.a. Position the cursor on the transport domain.
3.b. Choose the push button "Display Import Queue" or "Double click" on the transport
domain name.
4. Search and select the transport request which shall be imported.

The files which need to be imported depend on the property tree package and are listed
in the Appendix.

INTERNAL: SAP CUSTOMER 12 © SAP SE

 Property Tree

4.a. In order to find a transport request more easily in the import queue, a filter can be set.
Choose a column, "Request" for example, by clicking on the column title.

Then choose the pushbutton "Filters (Ctrl + F10)" or press "Ctrl + F10".

Enter the filter criterion in the following window, "SH2*" or "EEI*" for example.

Select the filter criterion with the pushbutton "Copy (Enter)".

4.b. Position the cursor on the transport request and select it with the pushbutton "Se-
lect/Deselect Request (F9)" or press F9. The selected transport request will be high-
lighted.
5. Start the import for the client where the property tree objects shall be used.

Please note that property tree transport requests are client dependent and shall be available
after the import only in the selected client.
5.a. Start the import with the pushbutton "Import Request (Ctrl+F11) or press Ctrl+F11.
5.b. Fill in the "Target Client" in the next window.
5.c. On the tab page "Date", set the start date to "Immediate".
5.d. On the tab page "Options", select the option "Leave Transport Request in Queue for
Later Import" .
5.e. On the tab page "Options", select the option "Ignore Invalid Component Version" when
transports which were generated on an ERP 6.0 system are imported in a system with
a lower release (ERP 5.0 = ERP 2004 for example).
5.f. Choose the pushbutton "Continue" to start the import. The status of the transport re-
quest will change first to "Import running" and then to "Request is ready for import
again".

Use "Legend: Import Queue" to obtain more details about the status symbols.
6. Check the import by displaying the transport log.
6.a. After the import is completed, open the transport log for the imported transport request
using the push button "Logs (Ctrl+F4)" or press Ctrl+F4.
6.b. The transport log will be displayed. You may open additional sections by pressing the
"+" pushbutton.
6.c. In general, the status of the import will be "(0) Successfully Completed".
6.d. The status may be "(4) Ended with warning" when transports which were generated
on an ERP 6.0 system are imported in a system with a lower release (ERP 5.0 = ERP
2004 for example). Such warnings because of "different nametabs" can be ignored.
The property tree objects are imported correctly despite the warning.

3.2.2.2. Execute Programs

Some property tree packages contain a program which has to be executed normally after the
import of the transport requests. A detailed description is delivered with the program itself.

The general procedure to execute a program is described in the steps below:

1. Execute transaction SA38.

2. Enter the program name mentioned in the property tree package description (document
ReadMe....) or in the document accompanying the program.
3. Choose pushbutton "Excecute (F8)" or press 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.
INTERNAL: SAP CUSTOMER 13 © SAP SE
 Property Tree

3.2.2.3. Settings

The files which need to be imported depend on the property tree package and are listed in
the Appendix.

3.2.3. Allocate phrase sets

The prerequisite for the import of the allocation of phrases to phrase sets is that the standard
property tree has been set up in SAP EH&S and that the phrase sets have been generated and
assigned to all characteristics defined for phrases. The allocation of phrase sets to customer
specific properties has to be done manually.

Neither new phrases nor phrase sets nor allocations of phrase sets to standard 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 character-
istics. 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 or with ERP 6.0 EHP7 and higher EHPs: Run customizing activity
"Generate Standard Phrase Sets"

In the following, both ways are described:

1. Manual generation and allocation of phrase sets

1.a. Ensure that no one is working with the affected property tree or is using the affected
properties and characteristics in the EH&S specification workbench.
1.b. 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 as-
signed - that are all characteristics of type CHAR 30. These characteristics are trans-
ferred to the table “Phrase set - Attribute assignment” (transaction CGAB).

INTERNAL: SAP CUSTOMER 14 © SAP SE

 Property Tree

1.c. 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. Enter the English characteristic description as the phrase set
name in English. Save.

It is recommended to add a German phrase set name as well when you work also
work with a German user interface.

Add appropriate phrases to the new phrase sets.

Exceptions are characteristics which keys end with "_GLP",

"_PREC", or "_TEST_SUB". For these characteristics, phrase sets al-
ready exist (SAP_EHS_XXXX_XXX_PREC, SAP_EHS_XXXX_XXX_GLP, and
SAP_EHS_XXXX_XXX_TEST_SUB) and shall directly be assigned.
1.d. Choose transaction CGAB "Edit phrase set-attribute assignment". Assign all new
phrase sets to the appropriate characteristics.
1.e. Run transaction CGCZ "Match up master data" with flag "Activate Phras-
ing of Characteristics" only. This function assigns the function module
C14K_PHRASECHARACT_CHECK to all phrase-related characteristics. This en-
ables the system to call an assigned phrase set in the specification data base.

INTERNAL: SAP CUSTOMER 15 © SAP SE

 Property Tree

2. During an initial setup: Run customizing activity "Generate Standard Phrase Sets"
2.a. Ensure that no one is working with the affected property tree or is using the affected
properties and characteristics in the EH&S specification workbench.
2.b. If an EH&S system is set up initially the customizing activity "Generate Standard
Phrase Sets" is used in general to create and allocate phrase sets to all characteris-
tics of type CHAR 30. Please note that with ERP 6.0 EHP7 and higher EHPs, this
customizing activity was extended by a list of characteristics which shall be excluded
from phrase set assignment. This list is delivered with the SAP standard deliver and
ensure that CHAR 30 which are not meant to be assigned to phrase sets are excluded
from the generation and assignment of standard phrase sets.
2.c. Navigate to the activity "Generate Standard Phrase Sets" in the SAP customizing
(IMDG) (path within EH&S 3.2 and higher releases: Environment, Health & Safety ->
Basic Data and Tools -> Specification Management -> Specification Data Base Struc-
ture -> Settings for Value Assignment -> Generate Standard Phrase Sets). A complete
overview about this activity is given in the corresponding IMDG activity documentation.
2.d. Start the activity.
2.e. Phrase sets are generated and allocated to all characteristics of type CHAR 30. With
ERP 6.0 EHP7 and higher EPs phrase sets are not generated and allocated to char-
acteristics which are on the exclusion list. Phrases are not allocated to the new phrase
sets. Assignments of phrase sets to characteristics that already exist are not overwrit-
ten by the system.
2.f. 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.

If the explanation component shall be used and the phrase sets were generated
by the automatic customizing functionality "Create Standard Phrase Sets", it is neces-
sary 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.
2.g. Run transaction CGCZ "Match up master data" with flag "Activate Phras-
ing of Characteristics" only. This function assigns the function module
INTERNAL: SAP CUSTOMER 16 © SAP SE
 Property Tree

C14K_PHRASECHARACT_CHECK to all characteristics where phrase sets have

been assigned (see transaction CGAB). 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 transac-
tion, 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
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, WWI symbols have to
be created for all new characteristics, which shall 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.

INTERNAL: SAP CUSTOMER 17 © SAP SE

 Property Tree

Additional information:

In a standard R/3 System automatically created symbols using the transaction CGCZ are gen-
erated with descriptions which are copies of the characteristics descriptions in the logon lan-
guage. The flag "Regenerate Symbol Descriptions" within transaction CGCZ can be used to
generate the symbol descriptions in another language different from the logon language. En-
glish or German are possible symbol descriptions languages when property tree packages are
installed where the characteristics descriptions are delivered in English and German.

If the transaction CGCZ is run with the flag "Match Up Symbols-Phrase-Enabled Characteris-
tics" the symbol definitions for the characteristic symbols that have been changed from phrase-
related to non-phrase-related (or vice versa) will be updated..

3.2.5. Set up Table-based Value Assignment

Specification data are entered in the specification data base in a table on the "Value assign-
ments" tab page. The characteristics 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".

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
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

In the following, both ways are described:

1. Set up Table-based Value Assignment for new properties

INTERNAL: SAP CUSTOMER 18 © SAP SE

 Property Tree

1.1. Navigate to the activity "Set Up Table-Based Value Assignment" in the SAP customiz-
ing (IMG) (path: 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:

INTERNAL: SAP CUSTOMER 19 © SAP SE

 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 (List Data").

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 be-
cause this would create multiple entries in the customizing table!
1.5. Return to the previous window (push button "Back"):

INTERNAL: SAP CUSTOMER 20 © SAP SE

 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.7. Return to the previous window (push button "Back"):
1.8. Repeat the steps 1.2 to 1.7 to create the necessary entries for all new properties.
2. Set up Table-based Value Assignment for existing properties with new characteristics

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 rec-
ommended procedure is to delete all entries for existing properties with new characteristics
in the customizing table and to create the entries for these properties anew (see the follow-
ing steps 2.1 to 2.14).

If the configuration of the Table-Based Value Assignment for properties with new character-
istics 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 request).

2.1. Navigate to the activity "Set Up Table-Based Value Assignment" in the SAP customiz-
ing (IMG) (path: 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.
2.2. Start the activity. The following screen appears:

INTERNAL: SAP CUSTOMER 21 © SAP SE

 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:
2.8. Choose the entry "Create Entries for the Value Assignments". The window "Filling
Customizing Table for Table-based Value Assignment" appears:

INTERNAL: SAP CUSTOMER 22 © SAP SE

 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.11. Return to the previous window:
2.12. Choose the entry "Set Up Table-Based Value Assignment" again. The customizing
table opens. Check all entries for the configured property:
2.13. Return to the previous window (push button "Back"):
2.14. Repeat the steps 2.2 to 2.13 to create the necessary entries for all existing properties
with new characteristics.

3.2.6. Check and extend copy/inheritance templates

INTERNAL: SAP CUSTOMER 23 © SAP SE

 Property Tree

In order to copy or inherit information within EH&S, templates are used where the properties
are specified which shall be copied or inherited. Normally, these templates stay unchanged
for some time. However, when new properties are added to the standard property tree these
templates have to be checked and extended, if necessary.

3.2.6.1. How to check and extend copy/inheritance templates

The following steps are necessary to check and extend copy/inheritance templates:

1. Check copy/inheritance templates and assign one of the new properties to an existing tem-
plate, if necessary.
2. It is recommended to proceed as follows:
2.a. Navigate to the substance workbench or run transaction CG02.
2.b. Select "Find Substance" (double-click) on the initial screen. It is not necessary to start
a search and create a hit list.
2.c. Make sure that you are working in the "Edit" mode and not the "Display" mode. You
may change from "Display" to "Edit" mode using the pushbutton "Display <-> Edit (Ctrl
+F1)".
2.d. Navigate in the menu to "Specification" -> "Inheritance" -> "Edit Templates".
2.e. A selection screen opens where you select the template you want to edit. Choose the
pushbutton "Inheritance Templates Detail View". A detail window opens.
2.f. Choose the option "Value assignment type selection" where you can add new proper-
ties to the copy/inheritance template.
2.g. Select a new property. Choose the pushbutton "Transfer (Enter)".
2.h. A new window opens. Choose one of the pushbuttons "Replace" or "Supplement".
2.i. Choose the pushbutton "Transfer (F8)" on the next screen.
2.j. Complete this process by choosing the pushbutton "Save (Ctrl+S)" on the following
selection screen.
2.k. Choose the pushbutton "Transfer (Enter)" to return to the hit list.

3.3. Check Implementation

In the table below the implementation steps for property tree packages are listed which shall
be performed and checked.

3.3.1. Checking Procedure

Please use the following check list as a guidance through the property tree implementation
and checking procedure.

Status Where to do What to do

General
O Review documentation
Technical Part
O SAP system (Transaction Upload files
CG3Z)
O SAP Transport Manage- Import transports
ment System (Transaction
STMS)
O SAP EH&S (Transaction Create phrase sets
CG1B)

INTERNAL: SAP CUSTOMER 24 © SAP SE

 Property Tree

O SAP EH&S (Transaction Match up master data

CGCZ with option "Match
up ValAss type and char.")
O SAP EH&S (Transaction Assign phrase sets to characteristics
CGAB)
O SAP EH&S (Transaction Activate phrase set assignment to characteristic
CGCZ with option "Acti-
vate Phrasing of Charac-
teristics")
O SAP EH&S (Transaction Create WWI symbols
CGCZ with option "Gener-
ate symbols")
O SAP EH&S Customiz- Update table based value assignment
ing (Transaction SPRO,
navigation: Environment,
Health & Safety -> Ba-
sic Data and Tools ->
Specification Management
-> Specification Database
Structure -> Settings for
Value Assignment -> Set
Up Table-Based Value As-
signment)
O SAP EH&S Specification Test properties and characteristics in the property tree
Data Base (Transaction STANDARD in the EH&S specification data base.
CG02)
O SAP EH&S (Transaction Check, if new properties need to be included in inheri-
CG02 Specification -> In- tance templates
heritance -> Edit Tem-
plates)

INTERNAL: SAP CUSTOMER 25 © SAP SE

Chapter 4. SAP EHS Regulatory
Content - multilanguage phrase
library for hazard communication
4.1. General Information
SAP provides Multilanguage Phrase Libraries, previously known as CED (Chemical Exchange
Directory) Catalogue. This is a collection of more than10.000 phrases for product safety issues
in currently 45 languages, 35 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.

4.1.1. Prerequisites
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 Regu-
latory 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 corre-
spondent phrases.

If a customer has maintained own graphics by allocation of bitmaps to phrases these alloca-
tions will be overwritten by an update. The same applies for the fields phrase code and phrase
remark at the phrase item level!

INTERNAL: SAP CUSTOMER 26 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage phrase library for hazard communication

4.1.2.4. Phrase sets (PSET/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
system. 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.

Please note that there are different import files required depending on the language key defi-
nition in your system -details can be found in How To Implement Language Keys.

If you are working in an SAP S/4HANA system environment language key EN is defined to be
US English, while 6N is defined to be Britisch English. PT is defined to be Brazilian Portuguese,
while 1P is defined to be European Portuguese. In this case use the phrase import files for
SAP S/4HANA.

If you are working in an R/3 environment having EN defined as British English and PT as
European Portuguese please use the CED Standard phrase import files after implementation
of the correspondence languages Z8 and Z9.

• 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 and Hindi 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.

INTERNAL: SAP CUSTOMER 27 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage phrase library for hazard communication

• In Windows XP please check "Install files for complex script and right-to-left languages (in-
cluding Thai)" and "Install files for East Asia languages".

4.1.3.2. Phrase Languages in Unicode / Non-Unicode

All phrase import files are provided as Unicode files within SAP EHS Regulatory Content with
character standard UTF-8.

For customers still on Non-Unicode systems, we can provide non-Unicode phrase import files
only for languages available on ISO norm character set ISO 8859-1 (often referred to as “ISO
Latin 1”). Please request these languages through our helpdesk. We highly recommend the
use of Unicode files as some special characters cannot be converted for non-Unicode systems.

An overview of available languages can be found in the appendix (Languages/Codepages.

Serbian using the Central European code page is provided with language key d as proposed
by SAP; a Serbocroatain version using language key 0 is available on request for customers.
Normally 0 should be used for the Cyrillic version of Serbian. A Cyrillic version of Serbian is
not within the scope of ERC languages.

Please see appendix (Languages/Codepages) for further information on code pages and nec-
essary fonts.

4.1.3.3. Setup of language keys for phrase items within the phrase ad-
ministration

All different language keys within the R/3 system are delivered by SAP as standard settings
which the customer should 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.

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. Therefore single character
language keys are still applied in the import file.

4.1.3.3.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.

4.1.3.3.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

INTERNAL: SAP CUSTOMER 28 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage phrase library for hazard communication

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 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.

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 SAP SE

INTERNAL: SAP CUSTOMER 29 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage phrase library for hazard communication

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 per-
formed.

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.

Please check that you upload the correct files for the operating system of your application
server. You may also have to consider if Unicode or Non Unicode system. For non-unicode
files, 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.

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.

INTERNAL: SAP CUSTOMER 30 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage phrase library for hazard communication

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.

Apart from changes to header data (e.g. library date) no changes must be made within the
import file! The library key may contain characters from the English alphabet only (no special
characters).

Note
Be careful when opening and editing Unicode phrase import files. Many text editors are
not suitable for Unicode files any may corrupt the import files.

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 )
• For all files choose UTF-8 as character standard.
• You can leave all other options blank
• Optional: You can limit the import to certain languages if you want (Button "Language se-
lection" )
• Check the file (F5)
• Carefully check the displayed information before importing the phrases. Make sure you im-
port to the passive CED or TDCLE library, the versions are correct and no errors are dis-
played.
• 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
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.

INTERNAL: SAP CUSTOMER 31 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage phrase library for hazard communication

Caution
Please do not set the flag for full import as this will delete your
passive library!

4.2.3.2. How to merge phrases

To merge phrases from a passive catalogue into the active, use transaction cg12 and start with :

INTERNAL: SAP CUSTOMER 32 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage phrase library for hazard communication

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:

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.

INTERNAL: SAP CUSTOMER 33 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage phrase library for hazard communication

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 thou-
sand 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)

• "File with path" - Enter the path and file name (same as target file section upload files )

• Check the "Phrase Set Assignmt" option as shown in the screenshot below

• Check the file (F5)

INTERNAL: SAP CUSTOMER 34 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage phrase library for hazard communication

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 mainte-

INTERNAL: SAP CUSTOMER 35 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage phrase library for hazard communication

nance 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 reg-
ular maintenance. Should you need any additional info on this topic please feel free to contact
us.

4.2.4. Placeholder Phrases

The CED phrase library contains several phrases with a placeholder. The following chapters
describe several methods how to use these phrases.

4.2.4.1. Adding CED Permutations

The CED-library contains 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 25°C“.

• P15.00511321 "Keep at temperature not exceeding 30°C“.

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.

Possibilities for automatic replacement of the placeholder are described in the next chapters.

4.2.4.2. Automatic Replacement

Standard functionality is available to insert phrases like target organs into another phrase by
specifying the characteristic from which the phrase should be taken.

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 values are not yet covered.

Please see SAP Note 1146663 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.3. Replacing Placeholders Through a Phrase User Exit

There are two precautionary statements P411 and P411+P235 that include a placeholder for
a storage temperature. If specified or determined by GHS rule sets using the default settings,
these statements currently are displayed as follows:

• P411 Store at temperatures not exceeding .? °C/ .? °F. (N15.00950860)

• P411+P235 Store at temperatures not exceeding .? °C/ .? °F. Keep cool. (N15.00950865).

INTERNAL: SAP CUSTOMER 36 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage phrase library for hazard communication

Starting with our release ERC 1705, a new functionality can be used in order to automatically
fill the storage temperature values instead of the placeholders. As a prerequisite some settings
are required in the system:

• Environmental parameters need to be maintained manually in the EH&S system

(according the details given in the SAP Note 2345518). Two parameters should
be added: PHR_REPLACE_TEMPERATURE_VA with value SAP_EHS_1021_001 and
PHR_REPLACE_TEMPERATURE_CHARAC with value SAP_EHS_1021_001_TEMP
• A storage temperature needs to be available (SAP_EHS_1021_001_TEMP)
• User exit MSDS_STEMP need to be set manually in the header data of the phrases in the
active library (according to details given in the SAP Note 2345518).
• In Phrase Management (transaction CG12), the user exit MSDS_STEMP must be entered
in the affected phrases N15.00950860 and N15.00950865 (dialog "Edit Phrase: Header").

Other placeholders can also be replaced automatically by developing specific user exits, but
we do not provide standard functionality for them. Please see SAP Note 1373615 for more
information.

4.2.5. Individual changes on CED phrases

4.2.5.1. 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.5.2. 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.

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.3. Check Implementation

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

4.3.1. Checking Procedure

INTERNAL: SAP CUSTOMER 37 © SAP SE

 SAP EHS Regulatory Content - multilan-
guage 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 Review documentation
Technical Part
O Customizing (spro) Create passive phrase catalogue
O SAP EHS (cg3z) Upload phrases
Upload phrase set assignments
O SAP EHS (cg31) Import phrases
O SAP EHS (cg12) Merge phrases
O SAP EHS (cg31) Import phrase set assignments
O MS Excel / SAP EHS Review the list of retired phrases in the overview of
(cg31) changes spreadsheet. Make a decision if these phrases
should be deleted or removed from phrase sets.

INTERNAL: SAP CUSTOMER 38 © SAP SE

Chapter 5. SAP EHS Regulatory
Content - substance lists and
reference data
5.1. General Information
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

• ADN - European Carriage of Dangerous Goods by Inland Waterways
• ADR - European Carriage of Dangerous Goods by Road
• ANTT - Regulation for inland transport of dangerous goods in Brazil
• ASIA_ROAD - Road transport of dangerous goods in Asia
• 49CFR - USA Code of Federal Regulations 49 - Transportation
• CL_DG - Chile Standard on transport of dangerous goods
• CN_DG - Road Transportation of Dangerous Goods in China
• ICAO/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)
• ZA_DG . South Africa Standard on transport of dangerous goods

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

INTERNAL: SAP CUSTOMER 39 © SAP SE

 SAP EHS Regulatory Content - sub-
stance 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.

5.1.1. Prerequisites
The substance lists and reference data require additional customizing activities. These cus-
tomizing 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

INTERNAL: SAP CUSTOMER 40 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

5.1.3. Content of substance lists and reference data pack-

ages
Each substance lists and reference data implementation package consists of the following
parts:

• Documentation including user manual, release notes, content reports and training presen-
tations.
• 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

INTERNAL: SAP CUSTOMER 41 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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.

We recommend that you upgrade all OCC installations to the latest service pack.

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 Sup-
port 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 the latest 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

INTERNAL: SAP CUSTOMER 42 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

• HKEY_CURRENT_USER\Software\EHS-AddOns\Open Content Connector

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 Destina-
tion 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 structure the name as follows:

EHS_MGMT_<computer name of server>

INTERNAL: SAP CUSTOMER 43 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

• Connection type: T
• 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.
2. Confirm your entries.
3. On the Technical Settings tab page in the Activation Type screen area, set the flag to Reg-
istered Server Program.
4. In the Registered Server Program screen area, enter the PROGID entry from your installa-
tion (see How to install EHS Expert or entry in the file SAPRFC.ini) in the program ID field.
5. Save your entries

RFC Destination for EHS Expert

1. Choose Edit -> Create.

The RFC Destination screen appears. Enter the following data:

• 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
• Description: Enter a text to describe the RFC destination.
2. Confirm your entries.
3. On the Technical Settings tab page in the Activation Type screen area, set the flag to Reg-
istered 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.

INTERNAL: SAP CUSTOMER 44 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

5. If the SAP system comprises a number of application servers, you must specify under Gate-
way 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

1. Choose Edit -> Create.

The RFC Destination screen appears. Enter the following data:

• RFC destination: Name of your RFC destination, for example EHS_OCC

This entry corresponds to the entry for the EXPERT_DESTINATION parameter for the
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

INTERNAL: SAP CUSTOMER 45 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

• Description: Enter a text to describe the RFC destination: EHS Open Content Connector
2. Confirm your entries.
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. Save your entries

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).

INTERNAL: SAP CUSTOMER 46 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

• In the RFC Destinations tree, choose TCP/IP connections -> <name of your RFC destina-
tion> 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 determina-
tion user exit must be created in SAP EHS customizing. Product Safety and Dangerous Goods
content package require two separate user exits.

INTERNAL: SAP CUSTOMER 47 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 Sec-
tion 3.2.2.1, “How to import transport requests”

Import BC-Sets

Please find detailed information about this customizing activity within this document Sec-
tion 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 deter-
mination 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.

INTERNAL: SAP CUSTOMER 48 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 de-
activated 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 da-
ta 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 -> Adminis-
tration -> 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/ex-
clude indicator). The parameter numbering has to start with 1 and has to be consecutive.

INTERNAL: SAP CUSTOMER 49 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 Da-
ta 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 Sec-
ondary 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.

INTERNAL: SAP CUSTOMER 50 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 Authoriza-
tion 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 parame-
ters EXPERT_EXPLANATION_ESTCAT, EXPERT_EXPLANATION_RULE_PROP, and
EXPERT_EXPLANATION_DATE_PROP as described below. Please note that this option
requires the implementation of OSS note no. 1450276!

You set up the explanation component (optional) of the EHS Expert using the following pa-
rameters:

• 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:

INTERNAL: SAP CUSTOMER 51 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

• EXPERT_EXPLANATION_ESTCAT

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. Please note
that this option requires the implementation of OSS note no. 1450276!
• 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
database if it is stored in a password protected storage location or web server.
• 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.
INTERNAL: SAP CUSTOMER 52 © SAP SE
 SAP EHS Regulatory Content - sub-
stance lists and reference data

• EXPERT_TAB_FIELD_4

In this parameter you can specify a second identifier that OCC should use when look-
ing 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.
• EXPERT_TAB_FIELD_5

In this parameter you can specify a third identifier that OCC should use when look-
ing for substance data. This is identifier is only used when the identifiers specified in
EXPERT_TAB_FIELD_2 and EXPERT_TAB_FIELD_4 do not give a search result. The main
purpose is for loading data that is not assigned to CAS numbers, e.g. by using PMN numbers.

Typical Example Expert Rule set:

Environment parameter Sample value

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_DISPLAY
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_WORLD
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_GHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_GHS
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

Typical Example OCC data load:

Environment parameter Sample Value

EXPERT_ADD_PARAM_1 headerurl=<path to ERC PS DB>\PS_DB
\header.xml
EXPERT_ADD_PARAM_2 usernameurl=x
EXPERT_ADD_PARAM_3 passwordurl=x
EXPERT_CALL_ONCE X

INTERNAL: SAP CUSTOMER 53 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE I
EXPERT_DESTINATION EHS_OCC
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE H
EXPERT_READ_RATING
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG
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_TAB_FIELD_5 <identifier>[NUM,PMN]
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID TECHNIDATA
EXPERT_WRITE_VALIDITY_AREA 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 specifica-
tion database, which must be created in SAP EHS customizing. Product Safety and Danger-
ous 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.

5.2.2.2.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 Sec-
tion 3.2.2.1, “How to import transport requests”

INTERNAL: SAP CUSTOMER 54 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

5.2.2.2.2. via manual customizing

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 Environ-
ment, Health & Safety ->Basic Data and Tools -> Tools -> Import ans Export -> Basic Settings
for Import and Export -> Specify Data Origins.

• Press F5 or "New Entries"

• 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 Prod-
uct Safety and extended Dangerous Goods with packaging data make use of phrases.

5.2.2.3.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”

INTERNAL: SAP CUSTOMER 55 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

Import transports

Please find detailed information about this customizing activity within this document Sec-
tion 3.2.2.1, “How to import transport requests”

5.2.2.3.2. via manual customizing

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 .

5.2.2.3.2.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.

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 SAP SE
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.

INTERNAL: SAP CUSTOMER 56 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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

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 Cus-
tomizing 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.

5.2.2.4.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 Sec-
tion 3.2.2.1, “How to import transport requests”

5.2.2.4.2. via manual customizing

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 Environ-
ment, Health & Safety ->Basic Data and Tools -> Specification Management -> Additional In-
formation for Value Assignment -> Specify User-Defined Text Types.

• Press F5 or "New Entries"

• Enter the user defined text types (limited to 10 characters)
• Give a note / description
• Assign a specification category

INTERNAL: SAP CUSTOMER 57 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

• 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 Customiz-
ing of each content package for substance lists and reference data. As an alternative, you can
create the regulatory lists manually with the description below.

5.2.2.5.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 Sec-
tion 3.2.2.1, “How to import transport requests”

5.2.2.5.2. via manual customizing

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

INTERNAL: SAP CUSTOMER 58 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 Cus-
tomizing of each content package for substance lists and reference data. As an alternative,
you can create the literature sources manually with the description below.

5.2.2.6.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 Sec-
tion 3.2.2.1, “How to import transport requests”

5.2.2.6.2. via manual customizing

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 Manage-
ment -> Additional Information for Value Assignment -> Specify Sources.

INTERNAL: SAP CUSTOMER 59 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

• Press F5 or "New Entries"

• 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

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 alterna-
tive, you can create the identifier types manually with the description below.

5.2.2.7.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 Sec-
tion 3.2.2.1, “How to import transport requests”

5.2.2.7.2. via manual customizing

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

INTERNAL: SAP CUSTOMER 60 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 rec-
ommended - 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.

INTERNAL: SAP CUSTOMER 61 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 releas-
es 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.

INTERNAL: SAP CUSTOMER 62 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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

1 Road 1
2 Rail 2
3 Inland waterway 3
4 Sea 4
5 Air cargo 5
6 Air passenger 6
7 Road passenger 1
8 Rail passenger 2
9 Inland waterway passenger 3
20 Pipeline 20
97 Road and Rail 7
98 Road, rail, inland waterway 7
99 All mode of transport cate- 7
gories

INTERNAL: SAP CUSTOMER 63 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 3
ADR ADR 1
ANTT BR 1
ASIA_ROAD ASR 1
CFR_AIR_C US 5
CFR_AIR_P US 6
CFR_INWTR US 3
CFR_RAIL_C US 2
CFR_RAIL_P US 8
CFR_ROAD US 1
CL_DG CL 97
CN_DG CN 1
IATA_C REG_WORLD 5
IATA_P REG_WORLD 6
IMDG REG_WORLD 4
KR_DG KR 1
MERCOSUR MERCOSUR 1
MX_DG MX 1
NZ_DG NZ 97
RID RID 2
TDG_INWT_C CA 3
TDG_INWT_P CA 9
TDG_RAIL_C CA 2
TDG_RAIL_P CA 8
TDG_ROAD_C CA 1
TDG_ROAD_P CA 7
UN_DG REG_UN_DG 98
ZA_DG ZA 97

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:

INTERNAL: SAP CUSTOMER 64 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

Regulation Validity Area MTrCat.

CFR US 99
TDG CA 99

5.2.2.8.3. 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 Sec-
tion 3.2.2.1, “How to import transport requests”

5.2.2.8.4. via manual customizing

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. Mainte-
nance 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 multi-
ple 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:

• Press F5 or " New Entries"

• 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

Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Basic Data - Specify Risk Potential:

• Press F5 or " New Entries"

• Enter the DG regulation and class the risk potential is relevant for
• Enter the risk potential (and classification code if applicable)

INTERNAL: SAP CUSTOMER 65 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

• Enter a description for the new risk potential

• Save your settings

5.2.2.8.4.1.3. Hazard Identification Numbers

Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Common Settings - Specify Hazard Identification
Numbers:

• Press F5 or " New Entries"

• 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

Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Common Settings - Specify Danger Labels:

• Press F5 or " New Entries"

• 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

Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Common Settings - Specify Packing Instruction
Numbers: (these entries are just used in RiscClssification for creation of transport documents)

• Press F5 or " New Entries"

• 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

Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Common Settings - Specify Categories for En-
closure: (these entries of packing instructions are used in PackingRequirements)

• Press F5 or " New Entries"

• 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

Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Common Settings - Specify Packing Codes:

INTERNAL: SAP CUSTOMER 66 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

(these entries of packing codes are used in PackingRequirements, do not use Packing Codes
(old))

• Press F5 or " New Entries"

• 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 avail-
able 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 Customiz-
ing of each content package for substance lists and reference data. As an alternative, you can
create the validity areas 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 HU Hungary
BE Belgium IE Ireland
BG Bulgaria IT Italy
CY Cyprus LT Lithuania
CZ Czech Republic LU Luxembourg
DE Germany LV Latvia
DK Denmark MT Malta
EE Estonia NL Netherlands
ES Spain PL Poland
FI Finland PT Portugal
FR France RO Romania
GB United Kingdom SE Sweden
GR Greece SI Slovenia
HR Croatia SK Slovakia

INTERNAL: SAP CUSTOMER 67 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

5.2.2.9.1. Validity Areas for SAP EHS Regulatory Content - substance lists and refer-
ence 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 ASR Region of regulation
ASIA_ROAD
REGION BR Brazil
REGION CA Canada
REGION CL Chile
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 ZA South Africa
REGION REG_UN_DG Val. Area for UN model regula-
tions
REGION REG_WORLD World

Table 5.1. Special validity areas for dangerous goods

Country Code ADN ADR ASR MER- RID

COSUR
Albania AL X X
Algeria DZ X
Andorra AD X
Armenia AM X
Argentina AR X
Austria AT X X X
Azerbaijan AZ X
Belarus BY X
Belgium BE X X X
Bolivia BO X

INTERNAL: SAP CUSTOMER 68 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

Country Code ADN ADR ASR MER- RID

COSUR
Bosnia BA X X
Herzegov-
ina
Bulgaria BG X X X
Chile CL
Colombia CO X
Croatia HR X X X
Cyprus CY X
Czech Re- CZ X X X
public
Denmark DK X X
Ecuador EC X
Estonia EE X X
Finland FI X X
France FR X X X
Georgia GE X X
Germany DE X X X
Greece GR X X
Hungary HU X X X
Iceland IS X
Indonesia ID X
Iraq IQ X
Iran IR X
Ireland IE X X
Italy IT X X X
Jordan JO X
Kazakhstan KZ X
Latvia LV X X
Lebanon LB X
Liechten- LI X X
stein
Lithuania LT X X
Luxem- LU X X X
bourg
Macedonia MK X X
Malaysia MY X
Malta MT X
Moldova MD X X

INTERNAL: SAP CUSTOMER 69 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

Country Code ADN ADR ASR MER- RID

COSUR
Monaco MC X
Morocco MA X X
Montene- ME X X
gro
Nether- NL X X X
lands
Norway NO X X
Paraguay PY X
Peru PE X
Poland PL X X X
Portugal PT X X
Romania RO X X X
Russian RU X X X
Federation
Serbia RS X X X
Singapore SG X
Slovakia SK X X X
Slovenia SI X X
Spain ES X X
Sweden SE X X
Switzerland CH X X X
Syria SY X
Taiwan TW
Tajikistan TJ X
Thailand TH X
Tunisia TN X X
Turkey TR X X
Ukraine UA X X X
United GB X X
Kingdom
Uruguay UY X
Venezuela VE X

5.2.2.9.2. 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”

INTERNAL: SAP CUSTOMER 70 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

Import transports

Please find detailed information about this customizing activity within this document Sec-
tion 3.2.2.1, “How to import transport requests”

5.2.2.9.3. via manual customizing

Please ask us for details if you want to manually customize validity areas for SAP EHS Reg-
ulatory 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:

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_WORLD" 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.
• Please see also SAP Note 603152 - Country Codes for Serbia
and Montenegro

• Go to the IMG customizing ("spro"):

• Navigate to Environment, Health and Safety -> Basic Data and Tools -> Additional Informa-
tion for Value Assignment -> Usage ->Specify Validity Areas.

INTERNAL: SAP CUSTOMER 71 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

• 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.

5.2.2.10. Update Hit List Functionality

INTERNAL: SAP CUSTOMER 72 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

Through the extended substance search functionality, you will be able to search for list sub-
stances that have new and/or changed data available from SAP EHS Regulatory Content -
substance lists and reference data. The result will be given as a hit list directly in SAP EHS.

Note
This functionality has been integrated as a standard functionality into SAP EHS. Please
do not use the program that was included in previous releases of SAP ERC and use
the standard functionality described below.

Please check in your specification workbench if the extended search functionality "New Data
Available for Substance.." is available: Note 1563938 - No extended search function to search
for updated substances

• Open the initial screen for the substance search

• Under "Extended search functions", the search function "New Data Available for Sub-
stance..." should be available

If this is not the case, please follow the instructions in SAP Note 1563938 - No extended search
function to search for updated substances.

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
• 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.

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.

INTERNAL: SAP CUSTOMER 73 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

5.2.3.1.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.

Please check that you upload the correct files for the operating system of your application
server. You may also have to consider if Unicode or Non Unicode system. For non-unicode
files, 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.

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.

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

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 )
• For all files choose UTF-8 as character standard.
• You can leave all other options blank

INTERNAL: SAP CUSTOMER 74 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

• Optional: You can limit the import to certain languages if you want (Button "Language se-
lection" )
• Check the file (F5)
• Carefully check the displayed information before importing the phrases. Make sure you im-
port to the passive CED or TDCLE library, the versions are correct and no errors are dis-
played.
• 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
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!

INTERNAL: SAP CUSTOMER 75 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

5.2.3.2.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:

INTERNAL: SAP CUSTOMER 76 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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.

INTERNAL: SAP CUSTOMER 77 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 thou-
sand 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).

5.2.3.2.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)

• "File with path" - Enter the path and file name (same as target file section upload files )

• Check the "Phrase Set Assignmt" option as shown in the screenshot below

• Check the file (F5)

INTERNAL: SAP CUSTOMER 78 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 mainte-

INTERNAL: SAP CUSTOMER 79 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

nance 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 reg-
ular maintenance. Should you need any additional info on this topic please feel free to 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 refer-
ence data

Note
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. ERC_PS_Region_
2015-2.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
Please carefully check the installation path if you are updating an existing database 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.

Note
Customers who have licensed both the SAP EHS Regulatory Content SDS Authoring
and Marketability packages have the possibility to load regulatory lists data from both
packages with one data load.

In case you have licensed both, SDS-Authoring and Marketability, and you load both
packages with one data load, please do not install the SDS-Authoring package for list
data. Instead, please use the Marketability installation file and follow the instructions
there to install the combined content for both packages.

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.

INTERNAL: SAP CUSTOMER 80 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

After installation of the XML files, the structure of the database should look like:

Product Safety:

<path to XML substance database>\ERC-PS\ main folder with index file and version info
(header.xml and version.txt)
<path to XML substance database>\ERC-PS subfolder with all CAS numbers starting with 1
\1
<path to XML substance database>\ERC-PS subfolders for other CAS numbers starting
\... with 2 to 9
<path to XML substance database>\ERC-PS subfolder with all substance groups
\G
<path to XML substance database>\ERC-PS subfolder with all non-substances data, e.g.
\N mixtures and data with no CAS number

Dangerous Goods and Dangerous Goods with Packaging Data:

<path to XML substance database>\ERC-DG\ main folder with index file and version info
(head.xml and version.txt)
<path to XML substance database>\ERC-DG subfolder with all data for DG regulation
\ADN ADN(R)
<path to XML substance database>\ERC-DG subfolders for other DG regulations
\...
<path to XML substance database>\ERC-DG 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 front-
end 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, reg-
ulatory lists and literature sources.

INTERNAL: SAP CUSTOMER 81 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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
database. OCC mapping databases are Microsoft Access databases. If changes to the map-
ping 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 Reg-
ulatory 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 net-
work-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 cre-
ating 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 front-
end computer and the storage location of the mapping database. WAN connections

INTERNAL: SAP CUSTOMER 82 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 re-
quired:

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: CUST-

Replace 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 databas-
es. 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 made your own changes to the mapping database, e.g. renamed identifiers or
phrase mapping changes, please take care to implement your changes also in the new map-
ping 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.

INTERNAL: SAP CUSTOMER 83 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 avail-
able after the first data load.

In all tables, Internal_id means the key/value in the database and External_id the correspond-
ing 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 and newer) to your Excel template folder, usually ...\Documents\<user>\Application
Data\Microsoft\Templates

INTERNAL: SAP CUSTOMER 84 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

Note
In Excel 2013 the default personal templates location is sometimes empty. Please
check in your Excel Options under ->Save ->Default personal templates location
that a folder is specified. Make sure the simulation spreadsheet has been copied
to this folder. If no folder is specified, you can select your own folder to store Excel
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
• It is also possible to open the simulation Excel files directly, without specifying them as a
template.

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 the latest version or contact us for the settings in older OCC versions.

INTERNAL: SAP CUSTOMER 85 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

Note
If multiple installations of the database exist for test, development and productive sys-
tems, the below steps must be repeated for all of them. Assign the name of the in-
stances 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:

• 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:

INTERNAL: SAP CUSTOMER 86 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

• Execute OCC: ->Start -> Programs -> EHS -> Open Content Connector
• 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

A new instance entry has to be configured for Dangerous Goods/Packaging Data:

• Execute OCC: ->Start -> Programs -> EHS -> Open Content Connector
• Choose: Options -> Instance Configuration ...
• 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"

INTERNAL: SAP CUSTOMER 87 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

5.2.7.2. Configure User Exit

Changes to the secondary data determination user exit are necessary to configure the con-
nection 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 ERC_PS or ERC_DG
EXPERT_ADD_PARAM_1 headerurl=<path to XML substance
database>\header.xml

INTERNAL: SAP CUSTOMER 88 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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

database>\header.xml
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

INTERNAL: SAP CUSTOMER 89 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

Example 5.1. Additional Test System Database

An additional database for the test system was created at F:\ERC-TEST:

• Additional registry-key needed for instance ERC-TEST

• Path to mapping database for new instance in registry changed to F:\ERC-TEST\td_
cleo.mdb
• Existing User Exit, e.g. ERC_PS copied to new key, e.g. ERC_TEST
• In new User Exit, change EXPERT_ADD_PARAM_1 to: headerurl= F:\ERC-TEST
\header.xml
• In new User Exit, change EXPERT_RULE_SET to: ERC-TEST

5.2.7.2.2. Adding Alternative Search Identifier Types

Open Content Connector supports the use of up to 2 alternative search identifier types. For our
product safety data we support the use of a generic key to load substance groups or generic
dust / PNOS information and PMN numbers from TSCA as alternatives for a load by CAS
number.

These alternative searches will only be used if no CAS number is maintained in the list sub-
stance.

Please note that this functionality requires SAP EHS OCC SP37 or higher versions.

If you want to make use of this alternative search, the secondary data determination user exit
has to be extended. Please add the following two parameters if they do not exist:

Environment parameter Sample Value

EXPERT_TAB_FIELD_4 <identifier>[NAM,TRIV]
EXPERT_TAB_FIELD_5 <identifier>[NUM,PMN]

This will allow you to use the NAM TRIV identifier type to load substances without a CAS
number by the technical key. You can replace NAM TRIV by any other identifier type that you
want to use for this purpose.

You can use the technical key of a substance group or generic entry for this search. For some
common generic entries, we have also created easy to use search keys:

• DUST: This search parameter can be used to load generic dust OEL values and other data
that is available for dust entries. You can also select from various dust sub-categories during
the data load, e.g. organic dust, inorganic dust.
• PNOS: This search parameter can be used to load data for particles/particulates not other-
wise specified.
• WOOD: This search parameter can be used to load data for many kinds of wood dust (hard-
wood, softwood, etc.)

The same functionality can be used to load our data by using the TSCA PMN number instead
of a CAS number.

Example: Maintaining NUM PMN "P-00-1122" in your list substance allows you to load the
same data as you could by maintaining NUM CAS 12032-75-6.

5.2.7.3. Adjust Mapping

INTERNAL: SAP CUSTOMER 90 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 trans-
port. You can use the TD_CLEO_DG.mdb as provided.

During next start of OCC de select the remaining carrier versions of CFR and TDG so that just
the two mapped entries remain. Store this setting as default and in future you will just see and
load a single regulation for each country in NA region (Canada, US).

If a split into modes of transport for CFR and TDG is required, please use mapping database
TD_CLEO_DG_with_split.mdb instead of the one mentioned above. All settings are already
adapted for split of carrier versions therein.

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
to suppress those additional data and avoid complications.

5.2.7.3.2. How to adjust the Fact Mapping

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

INTERNAL: SAP CUSTOMER 91 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

Table Field Meaning

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.2.1. Adjusting Fact Mapping to Load a CAS Number

Example how you can add a CAS number as identifier if you load your substance with a PMN
number:

Table Field Value

Record
DispOrder 96
Internal_Id NUM_CAS
Group
External_Id I:NUM,CAS;DUMMY,UPDDAT,LANGU,IDENT,SUBLIST
Language EN
Description CAS Number
IsPhrase yes
Options /DISP=1/MAP=SUBLIST/SEP="|"

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 Options that govern access to the data in EHS more closely

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.

INTERNAL: SAP CUSTOMER 92 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 corre-
sponding 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)

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 ex-
ample [#R20#] .
External_Id Phrase key in EHS
Phrasetext Phrase text
Options Options that govern access to the data in EHS more closely

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 cata-
logue 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

INTERNAL: SAP CUSTOMER 93 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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 sub-
stance 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
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 (ac-
tivated 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.

INTERNAL: SAP CUSTOMER 94 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

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:

• 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.

5.3. Check Implementation

The following steps describe how to check the implementation of SAP EHS Regulatory Con-
tent.

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 Review documentation
Technical Part
O Frontend Install Open Content Connector
O SAP EHS (sm59) Setup & check RFC connection
O SAP EHS (cg3z) Upload customizing transports
Upload phrases
O SAP EHS (stms) Import customizing transports
O SAP EHS () Install hit list functionality
O SAP EHS (cg31) Import substance lists and reference data phrase library
O SAP EHS (cg12) Merge phrases to active catalogue

INTERNAL: SAP CUSTOMER 95 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

O SAP EHS (cg31) Import phrase sets

O td_cleo.mdb Install XML substance database
Setup mapping database
(optional) adjust mapping
O customizing (spro) Manual changes to OCC and user exit
O (optional) Install spreadsheet template for data analysis
Regulatory Part / Data Load
O Review regulatory lists in release notes and content re-
ports
O Create cache
O Review new filter settings

5.3.2. Check List Dangerous Goods for SAP EHS

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 Review documentation
Technical Part
O Frontend Install Open Content Connector
O SAP EHS (sm59) Setup & check RFC connection
O SAP EHS (cg3z) Upload customizing transports
Upload phrases
O SAP EHS (stms) Import customizing transports (BC Set)
O SAP EHS (cg31) Import Import substance lists and reference data phrase
library for dangerous goods
O SAP EHS (cg12) Merge phrases to active catalogue
O SAP EHS (cg31) Import phrase sets
O TD_CLEO_DG.mdb Install XML substance database
Setup mapping database
(optional) adjust mapping
O customizing (spro) Manual changes to OCC and user exit
Regulatory Part / Data Load
O Review regulatory lists in changes database
O Create cache
O Review new filter settings

5.3.3. Check List Dangerous Goods for SAP Transportation

Management

INTERNAL: SAP CUSTOMER 96 © SAP SE

 SAP EHS Regulatory Content - sub-
stance lists and reference data

Note
This chapter describes the Dangerous Goods solution for SAP Transportation Man-
agement. Users of SAP EHS Dangerous Goods can skip this chapter.

In the downloaded Package you can find a compressed ZIP file containing the content for
usage in SAP Transport Management. This file can be uploaded in the Content Import tool of
SAP Transportation Management without any processing steps from your side, e.g. unpacking
in your local file system.

INTERNAL: SAP CUSTOMER 97 © SAP SE

Chapter 6. SAP EHS Regulatory
Content - expert rules for substance
and mixture classification
SAP provides Expert Rule Sets for the determination of secondary data according to regula-
tions 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, con-
nected 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.

6.1. General Information

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.

6.1.1. Prerequisites
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 us-
er-exits and data origins for each rule set.

In addition some Expert Rules require further customizing activities, e.g. additional value as-
signment 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 recom-
mend setting up separate Expert Server PCs for the test and productive systems. This enables

INTERNAL: SAP CUSTOMER 98 © SAP SE

 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 specifi-
cation 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.40, “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

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.

INTERNAL: SAP CUSTOMER 99 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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 Destina-
tion 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 structure the name as follows:

EHS_MGMT_<computer name of server>
• Connection type: T
• 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.
2. Confirm your entries.
3. On the Technical Settings tab page in the Activation Type screen area, set the flag to Reg-
istered Server Program.
4. In the Registered Server Program screen area, enter the PROGID entry from your installa-
tion (see How to install EHS Expert or entry in the file SAPRFC.ini) in the program ID field.
5. Save your entries

RFC Destination for EHS Expert

1. Choose Edit -> Create.

The RFC Destination screen appears. Enter the following data:

• RFC destination: Name of your RFC destination, for example EHS_EXPERT

INTERNAL: SAP CUSTOMER 100 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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
• Description: Enter a text to describe the RFC destination.
2. Confirm your entries.
3. On the Technical Settings tab page in the Activation Type screen area, set the flag to Reg-
istered 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.
5. If the SAP system comprises a number of application servers, you must specify under Gate-
way 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

INTERNAL: SAP CUSTOMER 101 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

RFC Destination for OCC

1. Choose Edit -> Create.

The RFC Destination screen appears. Enter the following data:

• RFC destination: Name of your RFC destination, for example EHS_OCC

This entry corresponds to the entry for the EXPERT_DESTINATION parameter for the
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
• Description: Enter a text to describe the RFC destination: EHS Open Content Connector
2. Confirm your entries.
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. Save your entries

INTERNAL: SAP CUSTOMER 102 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

6.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).
• In the RFC Destinations tree, choose TCP/IP connections -> <name of your RFC destina-
tion> and open the destination with a double-click.
• Choose Test connection.

INTERNAL: SAP CUSTOMER 103 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

The test is running successfully if transmission duration times are displayed in the SAP window.

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 func-
tions:

• 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 Adminis-
tration or use transaction cgsadm.

INTERNAL: SAP CUSTOMER 104 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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)
• Confirm your entries.
• 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

INTERNAL: SAP CUSTOMER 105 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

• The SAPRFC.ini file will be updated automatically on the Expert Server PC using the Pro-
gram 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

INTERNAL: SAP CUSTOMER 106 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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 need-
ed.

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\Current-
ControlSet\Services.

INTERNAL: SAP CUSTOMER 107 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

• 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 func-
tions as a database server. (Default value = 20)
• 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 func-
tions 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 delet-
ed. 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.
INTERNAL:
• RemoveSAP the CUSTOMER
service using the Uninstall 108
services function. © SAP SE

6.2.1.3.2.3. How to configure EHS Expert Server as a console program

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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 param-
eter -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

In the example at the bottom you can see the typically used entries for secondary data deter-
mination 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.

INTERNAL: SAP CUSTOMER 109 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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 de-
activated 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 da-
ta 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 -> Adminis-
tration -> 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/ex-
clude indicator). The parameter numbering has to start with 1 and has to be consecutive.

INTERNAL: SAP CUSTOMER 110 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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 Da-
ta 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 Sec-
ondary 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.

INTERNAL: SAP CUSTOMER 111 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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 Authoriza-
tion 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 parame-
ters EXPERT_EXPLANATION_ESTCAT, EXPERT_EXPLANATION_RULE_PROP, and
EXPERT_EXPLANATION_DATE_PROP as described below. Please note that this option
requires the implementation of OSS note no. 1450276!

You set up the explanation component (optional) of the EHS Expert using the following pa-
rameters:

• 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

INTERNAL: SAP CUSTOMER 112 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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. Please note
that this option requires the implementation of OSS note no. 1450276!
• 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
database if it is stored in a password protected storage location or web server.
• 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

INTERNAL: SAP CUSTOMER 113 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

In this parameter you can specify a second identifier that OCC should use when look-
ing 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.
• EXPERT_TAB_FIELD_5

In this parameter you can specify a third identifier that OCC should use when look-
ing for substance data. This is identifier is only used when the identifiers specified in
EXPERT_TAB_FIELD_2 and EXPERT_TAB_FIELD_4 do not give a search result. The main
purpose is for loading data that is not assigned to CAS numbers, e.g. by using PMN numbers.

Typical Example Expert Rule set:

Environment parameter Sample value

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_DISPLAY
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_WORLD
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_GHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_GHS
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

Typical Example OCC data load:

Environment parameter Sample Value

EXPERT_ADD_PARAM_1 headerurl=<path to ERC PS DB>\PS_DB
\header.xml
EXPERT_ADD_PARAM_2 usernameurl=x
EXPERT_ADD_PARAM_3 passwordurl=x
EXPERT_CALL_ONCE X
EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 114 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

EXPERT_COMMIT_MODE I
EXPERT_DESTINATION EHS_OCC
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE H
EXPERT_READ_RATING
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG
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_TAB_FIELD_5 <identifier>[NUM,PMN]
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID TECHNIDATA
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

6.2.2.2. Multi Rule Call

Expert Multi Rule Call functionality 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

Without this functionality EHS 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 with ERP 6.0 EHP7 or higher. For lower
versions corresponding consulting solution is offered.

INTERNAL: SAP CUSTOMER 115 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

For enquiries please contact your SAP Service contact.

6.2.2.3. Data Origin

The data origins used within the EHS systems connect the user-exits with the Expert Admin-
istration instances.

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

To add new data origins use transaction "spro" for the IMG customizing. Navigate to Environ-
ment, Health & Safety ->Basic Data and Tools -> Tools -> Import ans Export -> Basic Settings
for Import and Export -> Specify Data Origins.

• Press F5 or "New Entries"

• Enter the Data Origin (limited to 10 characters)
• Optionally you may assign an Exchange Profile
• Give a note / description
• 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

Enter the sources and assign a specification category to each source. You can assign the
source key as required.

INTERNAL: SAP CUSTOMER 116 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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 Manage-
ment -> Additional Information for Value Assignment -> Specify Sources.

• Press F5 or "New Entries"

• 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".

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

To add new data origins use transaction "spro" for the IMG customizing. Navigate to Environ-
ment, Health & Safety ->Basic Data and Tools -> Specification Management -> Additional In-
formation for Value Assignment -> Specify User-Defined Text Types.

• Press F5 or "New Entries"

• Enter the user defined text types (limited to 10 characters)
• Give a note / description
• Assign a specification category
• Save your settings

6.2.2.6. Regulatory Lists

Regulatory lists are required for assigning identifiers. They can be used for specifying the reg-
ulatory 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.

INTERNAL: SAP CUSTOMER 117 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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.
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

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

INTERNAL: SAP CUSTOMER 118 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

6.2.2.7. User-Defined Dangerous Goods Texts

Using user-defined dangerous goods texts, additional data can be transferred into the danger-
ous 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
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 spe-
cific 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 Dang-
Goods 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.

INTERNAL: SAP CUSTOMER 119 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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.

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 sub-

stance 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 the configuration on the Expert Server PC using SAPSetup or
manually. It is possible to configure the rule set within the SAP system using the EHS Service
Administration.

6.2.3.1. Install Expert Rule Sets using SAP Setup

INTERNAL: SAP CUSTOMER 120 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

SAP EHS Regulatory Rule Sets can be installed by using SAPSetup (new since 2013-1)

For more details see Readme_SAPSetup_RuleSets.

6.2.3.2. 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.2.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

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.

INTERNAL: SAP CUSTOMER 121 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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.

6.2.3.2.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.

INTERNAL: SAP CUSTOMER 122 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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. 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.

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

For example for the rule set GHS:

Name = ZEXP_GHS, Rule File = GHS_V1-6.ruc, Mapping Database = GHS_V1-6.mdb

3. Save you settings by Apply

INTERNAL: SAP CUSTOMER 123 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

6.2.3.3. Run Expert Rule Sets

6.2.3.3.1. How to execute rules

Section A.50, “How to execute rules”

6.2.3.3.2. How to display the explanation component

Section A.51, “How to display the Explanation Component”

6.2.3.3.3. How to generate log files

Section A.53, “How to generate Log Files”

6.2.3.4. Adjust Expert Rule Sets

6.2.3.4.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.

INTERNAL: SAP CUSTOMER 124 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

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 HazardComp_US_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_RANGES T:Ranges/HazardComp_US_externvalues.mdb

Example: Record-Mapping – Full declaration of the path for the external data

Internal_id External_id
EXT_RANGES T:Ranges/C:\Program Files\EHS\Expert\Rules
\HazardComp_US_externvalues.mdb

Example: Fact-Mapping –Installation of the external data base in the same directory as the
rule set.

Internal_id External_id
i_limit_oel T:Threshold;OEL/HazardComp_US_externvalues.mdb

Example: Fact-Mapping –Full declaration of the path for the external data

Internal_id External_id
i_limit_oel T:Threshold;OEL/C:\Program Files\EHS\Expert\Rules
\HazardComp_US_externvalues.mdb

A documentation of the adjustable parameters could be obtained from the respective functional
descriptions of the rule sets.

6.2.3.4.2. How to adjust the Fact Mapping

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

INTERNAL: SAP CUSTOMER 125 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

Table Field Meaning

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.

6.2.3.4.2.1. Adjusting Fact Mapping to Load a CAS Number

Example how you can add a CAS number as identifier if you load your substance with a PMN
number:

Table Field Value

Record
DispOrder 96
Internal_Id NUM_CAS
Group
External_Id I:NUM,CAS;DUMMY,UPDDAT,LANGU,IDENT,SUBLIST
Language EN
Description CAS Number
IsPhrase yes
Options /DISP=1/MAP=SUBLIST/SEP="|"

6.2.3.4.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 Options that govern access to the data in EHS more closely

The first two fields together identify the record uniquely in the set of rules.

6.2.3.4.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.

INTERNAL: SAP CUSTOMER 126 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

Table Field Meaning

External_Id Name of the assigned value assignment type of the category composition
in EHS
Descriptions Description text for the composition
Options Options that govern access to the data in EHS more closely

6.2.3.4.5. 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 corre-
sponding 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)

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 ex-
ample [#R20#] .
External_Id Phrase key in EHS
Phrasetext Phrase text
Options Options that govern access to the data in EHS more closely

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.

INTERNAL: SAP CUSTOMER 127 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

Customer specific phrase catalogue

The first part of the phrase key (column: External_Id) always signifies the active phrase cata-
logue 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).

6.2.3.4.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:

• 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 (characteris-
tic within the property given above to save the user-exit name)
• EXPERT_EXPLANATION_DATE_PROP = SAP_EHS_0101_002_RUN_DATE (character-
istic where the date of the last run shall be stored)

6.3. Check Implementation

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 Review documentation
Technical Part
O Frontend Install EHS Expert
O SAP EHS (sm59) Setup RFC connection
O Expert Server or SAP EHS Configure EHS Expert Server
(cgsadm)
O Customizing (spro) Create user exit(s)
(optional) Create user exit(s) for Multi Rule Call
Create data origin

INTERNAL: SAP CUSTOMER 128 © SAP SE

 SAP EHS Regulatory Content - expert rules
for substance and mixture classification

Create literature source

Create user defined text type
Create regulatory lists
Create user defined dangerous goods texts
Create value assignment rating
O Expert Server or SAP EHS Use SAP Setup on the Ex-
(cgsadm) pert Server (SetupERC_<package>.exe (e.g.
SetupERC_GLOBAL.exe)) for installing the rule
set on the Expert Server. For more details see
Readme_SAPSetup_RuleSets
OR alternatively the following two steps can man-
ually be done
...1) Upload rule set files
...2) Create admin instance(s)
O Mapping.mdbs (optional) Adjust mapping.mdbs
Regulatory Part / Data Load
O

INTERNAL: SAP CUSTOMER 129 © SAP SE

Chapter 7. SAP EHS Regulatory
Content - safety data sheet (SDS)
templates
7.1. General Information
ERC provides SDS templates for more than 100 countries. The SDS templates are grouped ac-
cording to regions and/or similar legislations. SAP ERC implemented different SDS main tem-
plates. Within each main template several sub-templates are included (“template includes”).
This is done to keep the number and size of each SDS template-include low. The SDS main
templates are:

• SDS_1810_APJ_MAIN
• SDS_1810_APJ_MAIN_MY
• SDS_1810_EU_MAIN
• SDS_1810_EU_EXT_MAIN
• SDS_1810_EMEA_MAIN
• SDS_1810_CIS_MAIN
• SDS_1810_GHS_MAIN
• SDS_1810_NA_MAIN
• SDS_1810_LA_MAIN
• SDS_1810_NA_GHS_MAIN
• SDS_1810_RTL_MAIN
• SDS_1810_EMEA_RTL_MAIN
• SDS_1810_EUEXT_RTL_MAIN

In this section general information is provided for installing SDS templates, region-specific and
further information can be found in the appendix.

7.1.1. Prerequisites
This chapter describes the prerequisites which are necessary to use Report Templates.

The safety data sheet (SDS) templates require additional customizing activities, especially
creating identification listings and generation variants.

Please also note that there can be additional customizing neccessary to do resulting from SAP
notes; this might depend on the question if the customer wants to use certain functionality or
not. Please also see the relevant SAP notes. For example for the Trade Secret function, please
add identifiers NAM ZTRADESEC and NAM ZTRADESEC2 and maintain them as desired.

These customizing entries are described in the respective report templates' area in this
documentation's appendix.

The User defined text type KRA has to get assigned to the Specification categorie SUB-
STANCE to be able to maintain it on a REAL_SUB Level.

Within safety data sheets several graphics are needed, such as the GHS pictograms or UN
model regulation labels. Graphic files are used in connection with phrases or methods that are

INTERNAL: SAP CUSTOMER 130 © SAP SE

 SAP EHS Regulatory Content -
safety data sheet (SDS) templates

resolving customizing entries. In order to be able to display these graphics using the SDS WWI
templates the graphic files that are delivered with the ERC package need to be copied to the
WWI installation sub-folder GRAPHICS of all WWI server(s) and relevant local WWI front ends.
The graphic files should be located directly in the GRAPHICS folder without any sub-folders.

It is recommended to perform these steps before implementing the safety data sheet (SDS)
templates.

The implementation of following SAP Notes are necessary in connection with the WWI SDS
templates.

• SAP Note 2620940 - Conversion of IATA_P to IATA

• SAP Note 2579021 - Output name of legal entity for registration number
• SAP Note 2468443 - Apply Expansion Methods in Report Templates - Enhancement of so-
lution packages
• SAP Note 2510771 - Trade secret in nested master groups
• SAP Note 2487733 - Incorrect sorting of texts
• SAP Note 2345518 - Apply Expansion Methods in Report Templates, new solution packages
• SAP Note 2162431 - Document description missing after import of report templates
• SAP Note 2052892 - Solution package: Output exposure scenarios on EU safety data sheets
• SAP Note 2216199 - Incorrect determination of dependent data during report generation
• SAP Note 2196966 - Output of the first report date without this internal version 1
• SAP Note 2043217 - provides new parameter symbols to standard EHS for date of first
version and date of previous version.
• SAP Note 2010955 - Reading the current language with a 2-character ISO code
• SAP Note 1608768 - FAQ: Layouting of EHS report templates with includes
• SAP Note 1566397 - EH&S standard WWI processing methods
• SAP Note 1689850 - Output of tunnel code for reports
• SAP Note 1608770 - EH&S WWI: Formatting of includes is not Transferred
• SAP Note 1576728 EH&S WWI: Formatting of includes is not transferred
• SAP Note 1576098 - EH&S standard WWI processing methods
• SAP Note 1689850 - Output of tunnel code for reports
• SAP Note 820516 - EH&S WWI: Include Template; Conditional Output
• SAP Note 863075 - Error in "Conditional Output" and "Include Template"
• SAP Note 821061 - Error for "Conditional output" and "Include template"
• SAP Note 1935001 - Report symbols for chapters 1 and 16 of the material safety data sheet;
not mandatory but may be used by customers
• SAP Note 1507738 - needed to create EH&S WWI reports in right to left languages (for
example, Arabic, Hebrew, Urdu, and so on).

The include functionality and the conditional output are available for systems of EH&S 2004
in ERP 2004 or higher.

7.1.2. Content of safety data sheet (SDS) template packages

The ERC safety data sheet (SDS) template packages contain WWI template layouts accord-
ing to regional legislation requirements and come with necessary customizing and expansion
methods as well as Property Tree views.

Each template also comes with a specification document (formerly known as DataMapping)
that gives detailed overview on the properties and characteristics printed on the SDS.

Please find the contained files of the delivery.

INTERNAL: SAP CUSTOMER 131 © SAP SE

 SAP EHS Regulatory Content -
safety data sheet (SDS) templates

7.1.3. Identifier for Component Names

The data maintenance of the component identifier is of high importance for the output on the
final SDS. Therefore every customer should create a concept on this issue. The ouput of iden-
tifiers on the SDS templates mainly follows priorisation rules defined in ID listings. The main-
tenance of these ID listings is up to every customer and SAP is only offering proposals on
the maintenance.

For more details see How to disclosure Component Names.

7.2. Implementation
The following steps describe how to implement safety data sheet (SDS) templates.

7.2.1. Import transports

This chapter describes in detail the import of transports.

7.2.1.1. How to import transport requests

The import process consists of several steps which are identical for customizing and work-
bench transport requests:

1. Check user in import client.

2. Navigate to the SAP Transport Management System.
3. Select the transport domain for your SAP system.
4. Search and select the transport request which shall be imported.
5. Start the import for the client where the property tree objects shall be used.

Please note that property tree transport requests are client dependent and shall be available
after the import only in the selected client.
6. Check the import by displaying the transport log.

In the following, the steps listed above are described in more detail:

1. Check user in import client.

1.a. Make sure, that no other user besides the SAP administrator (who is doing the import)
is working in the EH&S specification data base or in the EH&S customizing on the SAP
client where the import of property tree transports takes place. Otherwise, property
tree objects might be logged and might not be updated during the import.
2. Navigate to the SAP Transport Management System.
2.a. Start transaction STMS.
2.b. Choose pushbutton "Import Overview (F5)" or press F5.
2.c. The import overview open with a list of transport requests which are available for im-
port.
3. Select the transport domain for your SAP system.
3.a. Position the cursor on the transport domain.
3.b. Choose the push button "Display Import Queue" or "Double click" on the transport
domain name.
4. Search and select the transport request which shall be imported.

The files which need to be imported depend on the property tree package and are listed
in the Appendix.

INTERNAL: SAP CUSTOMER 132 © SAP SE

 SAP EHS Regulatory Content -
safety data sheet (SDS) templates

4.a. In order to find a transport request more easily in the import queue, a filter can be set.
Choose a column, "Request" for example, by clicking on the column title.

Then choose the pushbutton "Filters (Ctrl + F10)" or press "Ctrl + F10".

Enter the filter criterion in the following window, "SH2*" or "EEI*" for example.

Select the filter criterion with the pushbutton "Copy (Enter)".

4.b. Position the cursor on the transport request and select it with the pushbutton "Se-
lect/Deselect Request (F9)" or press F9. The selected transport request will be high-
lighted.
5. Start the import for the client where the property tree objects shall be used.

Please note that property tree transport requests are client dependent and shall be available
after the import only in the selected client.
5.a. Start the import with the pushbutton "Import Request (Ctrl+F11) or press Ctrl+F11.
5.b. Fill in the "Target Client" in the next window.
5.c. On the tab page "Date", set the start date to "Immediate".
5.d. On the tab page "Options", select the option "Leave Transport Request in Queue for
Later Import" .
5.e. On the tab page "Options", select the option "Ignore Invalid Component Version" when
transports which were generated on an ERP 6.0 system are imported in a system with
a lower release (ERP 5.0 = ERP 2004 for example).
5.f. Choose the pushbutton "Continue" to start the import. The status of the transport re-
quest will change first to "Import running" and then to "Request is ready for import
again".

Use "Legend: Import Queue" to obtain more details about the status symbols.
6. Check the import by displaying the transport log.
6.a. After the import is completed, open the transport log for the imported transport request
using the push button "Logs (Ctrl+F4)" or press Ctrl+F4.
6.b. The transport log will be displayed. You may open additional sections by pressing the
"+" pushbutton.
6.c. In general, the status of the import will be "(0) Successfully Completed".
6.d. The status may be "(4) Ended with warning" when transports which were generated
on an ERP 6.0 system are imported in a system with a lower release (ERP 5.0 = ERP
2004 for example). Such warnings because of "different nametabs" can be ignored.
The property tree objects are imported correctly despite the warning.

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.

INTERNAL: SAP CUSTOMER 133 © SAP SE

 SAP EHS Regulatory Content -
safety data sheet (SDS) templates

7.2.3. Upload files

This chapter describes which files have to be uploaded and how this upload has to be per-
formed.

7.2.3.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.

Please check that you upload the correct files for the operating system of your application
server. You may also have to consider if Unicode or Non Unicode system. For non-unicode
files, 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.

INTERNAL: SAP CUSTOMER 134 © SAP SE

 SAP EHS Regulatory Content -
safety data sheet (SDS) templates

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.

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 acknowledge-
ment of receipt templates) to the SAP System.

In conjunction with report template export, you can exchange report templates between differ-
ent SAP Systems.

7.2.4.1. How to import report templates

First upload the dat-files (for example SDS_2015_2_EU_MAIN.dat) and doc-files (for example
SDS_2015_2_EU_MAIN.doc) on the application server using transfer format BIN (=>transac-
tion CG3Z).

If a UNIX system is used, choose the corresponding import settings to import a windows file.

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>

(Note that each dat-file contains the information to automatically pull the corresponding doc-
file. The doc-file itself should NOT be specified for the import.)
• Character standard: UFT-8

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 automatically open the new template document. Check the template by clicking on
the check-button and save it. If you encounter error messages at this stage, you can directly
take the relevant actions(i.e. set up missing ID-listings, etc.), or you may save the template
anyway and resolve the messages later.

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.

INTERNAL: SAP CUSTOMER 135 © SAP SE

 SAP EHS Regulatory Content -
safety data sheet (SDS) templates

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.

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.

A complete overview on the parameters of all generation variants can be found in the document
RGV_XXXX_Configuration.pdf (where XXXX stands for the current release).

INTERNAL: SAP CUSTOMER 136 © SAP SE

 SAP EHS Regulatory Content -
safety data sheet (SDS) templates

7.3. Check Implementation

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

7.3.1. Checking Procedure

Please use the following check list as guidance through the material safety data sheet (MSDS)
templates implementation and as check list after the implementation.

Sta- Where to do What to do

tus
General
O Administration Manual, Review documentation
Release Notes
Technical Part
O Check if all prerequisites are fulfilled, e.g. SAP Notes, Graph-
ic files
O SAP EHS (cg3z) Upload files (files for the templates and files for the customiz-
ing transports)
O SAP EHS (stms) Import customizing transports
O Customizing (spro) Setup identification listings
O SAP EHS (cg34) Import templates. Check and save them
O SAP EHS (cg2b) Create generation variants

INTERNAL: SAP CUSTOMER 137 © SAP SE

Appendix A. How To ...
A.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 Manage-
ment 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:

1. Find out the directory name and path of the import queue for the SAP Transport Manage-
ment System.

1.1. You may ask your SAP system manager or proceed as follows:
1.2. Run transaction AL11.
1.3. The first part of the directory path is listed after the entry DIR_TRANS, for example
"F:\usr\sap\trans".
1.4. 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.

5. Load the transport files into the import directory using the transaction CG3Z.

5.1. Start transaction CG3Z.

5.2. Enter in the field "Source file on front end" the transport file name including the com-
plete 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.
5.3. 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".
5.4. Start the upload process with the push button "Upload". When the upload process has
been successful a message appears.

5. Attach the transport request to the import queue

5.1. Navigate to the SAP Transport Management System (transaction STMS).

5.2. Choose push button "Import Overview (F5)".
5.3. Navigate to the transport domain of your SAP system: Position the cursor on the trans-
port domain and choose the push button "Display Import Queue" or choose "Double
click".
5.4. Choose in the menu "Extras" -> "Other requests" -> "Add".
5.5. 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.
5.6. 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!

INTERNAL: SAP CUSTOMER 138 © SAP SE

 How To ...

A.2. 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.

Please check that you upload the correct files for the operating system of your application
server. You may also have to consider if Unicode or Non Unicode system. For non-unicode
files, 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.

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.

A.3. How to import transport requests

The import process consists of several steps which are identical for customizing and work-
bench transport requests:

1. Check user in import client.

2. Navigate to the SAP Transport Management System.
3. Select the transport domain for your SAP system.
4. Search and select the transport request which shall be imported.
5. Start the import for the client where the property tree objects shall be used.

INTERNAL: SAP CUSTOMER 139 © SAP SE

 How To ...

Please note that property tree transport requests are client dependent and shall be available
after the import only in the selected client.
6. Check the import by displaying the transport log.

In the following, the steps listed above are described in more detail:

1. Check user in import client.

1.a. Make sure, that no other user besides the SAP administrator (who is doing the import)
is working in the EH&S specification data base or in the EH&S customizing on the SAP
client where the import of property tree transports takes place. Otherwise, property
tree objects might be logged and might not be updated during the import.
2. Navigate to the SAP Transport Management System.
2.a. Start transaction STMS.
2.b. Choose pushbutton "Import Overview (F5)" or press F5.
2.c. The import overview open with a list of transport requests which are available for im-
port.
3. Select the transport domain for your SAP system.
3.a. Position the cursor on the transport domain.
3.b. Choose the push button "Display Import Queue" or "Double click" on the transport
domain name.
4. Search and select the transport request which shall be imported.

The files which need to be imported depend on the property tree package and are listed
in the Appendix.

4.a. In order to find a transport request more easily in the import queue, a filter can be set.
Choose a column, "Request" for example, by clicking on the column title.

Then choose the pushbutton "Filters (Ctrl + F10)" or press "Ctrl + F10".

Enter the filter criterion in the following window, "SH2*" or "EEI*" for example.

Select the filter criterion with the pushbutton "Copy (Enter)".

4.b. Position the cursor on the transport request and select it with the pushbutton "Se-
lect/Deselect Request (F9)" or press F9. The selected transport request will be high-
lighted.
5. Start the import for the client where the property tree objects shall be used.

Please note that property tree transport requests are client dependent and shall be available
after the import only in the selected client.
5.a. Start the import with the pushbutton "Import Request (Ctrl+F11) or press Ctrl+F11.
5.b. Fill in the "Target Client" in the next window.
5.c. On the tab page "Date", set the start date to "Immediate".
5.d. On the tab page "Options", select the option "Leave Transport Request in Queue for
Later Import" .
5.e. On the tab page "Options", select the option "Ignore Invalid Component Version" when
transports which were generated on an ERP 6.0 system are imported in a system with
a lower release (ERP 5.0 = ERP 2004 for example).
5.f. Choose the pushbutton "Continue" to start the import. The status of the transport re-
quest will change first to "Import running" and then to "Request is ready for import
again".

Use "Legend: Import Queue" to obtain more details about the status symbols.

INTERNAL: SAP CUSTOMER 140 © SAP SE

 How To ...

6. Check the import by displaying the transport log.

6.a. After the import is completed, open the transport log for the imported transport request
using the push button "Logs (Ctrl+F4)" or press Ctrl+F4.
6.b. The transport log will be displayed. You may open additional sections by pressing the
"+" pushbutton.
6.c. In general, the status of the import will be "(0) Successfully Completed".
6.d. The status may be "(4) Ended with warning" when transports which were generated
on an ERP 6.0 system are imported in a system with a lower release (ERP 5.0 = ERP
2004 for example). Such warnings because of "different nametabs" can be ignored.
The property tree objects are imported correctly despite the warning.

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
• 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
INTERNAL: SAP CUSTOMER 141 © SAP SE
 How To ...

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

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:

1. Manual generation and allocation of phrase sets

2. During an initial setup or with ERP 6.0 EHP7 and higher EHPs: Run customizing activity
"Generate Standard Phrase Sets"

In the following, both ways are described:

1. Manual generation and allocation of phrase sets

1.a. Ensure that no one is working with the affected property tree or is using the affected
properties and characteristics in the EH&S specification workbench.
1.b. 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 as-
signed - that are all characteristics of type CHAR 30. These characteristics are trans-
ferred to the table “Phrase set - Attribute assignment” (transaction CGAB).

INTERNAL: SAP CUSTOMER 142 © SAP SE

 How To ...

1.c. 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. Enter the English characteristic description as the phrase set
name in English. Save.

It is recommended to add a German phrase set name as well when you work also
work with a German user interface.

Add appropriate phrases to the new phrase sets.

Exceptions are characteristics which keys end with "_GLP",

"_PREC", or "_TEST_SUB". For these characteristics, phrase sets al-
ready exist (SAP_EHS_XXXX_XXX_PREC, SAP_EHS_XXXX_XXX_GLP, and
SAP_EHS_XXXX_XXX_TEST_SUB) and shall directly be assigned.
1.d. Choose transaction CGAB "Edit phrase set-attribute assignment". Assign all new
phrase sets to the appropriate characteristics.
1.e. Run transaction CGCZ "Match up master data" with flag "Activate Phras-
ing of Characteristics" only. This function assigns the function module
C14K_PHRASECHARACT_CHECK to all phrase-related characteristics. This en-
ables the system to call an assigned phrase set in the specification data base.

INTERNAL: SAP CUSTOMER 143 © SAP SE

 How To ...

2. During an initial setup: Run customizing activity "Generate Standard Phrase Sets"
2.a. Ensure that no one is working with the affected property tree or is using the affected
properties and characteristics in the EH&S specification workbench.
2.b. If an EH&S system is set up initially the customizing activity "Generate Standard
Phrase Sets" is used in general to create and allocate phrase sets to all characteris-
tics of type CHAR 30. Please note that with ERP 6.0 EHP7 and higher EHPs, this
customizing activity was extended by a list of characteristics which shall be excluded
from phrase set assignment. This list is delivered with the SAP standard deliver and
ensure that CHAR 30 which are not meant to be assigned to phrase sets are excluded
from the generation and assignment of standard phrase sets.
2.c. Navigate to the activity "Generate Standard Phrase Sets" in the SAP customizing
(IMDG) (path within EH&S 3.2 and higher releases: Environment, Health & Safety ->
Basic Data and Tools -> Specification Management -> Specification Data Base Struc-
ture -> Settings for Value Assignment -> Generate Standard Phrase Sets). A complete
overview about this activity is given in the corresponding IMDG activity documentation.
2.d. Start the activity.
2.e. Phrase sets are generated and allocated to all characteristics of type CHAR 30. With
ERP 6.0 EHP7 and higher EPs phrase sets are not generated and allocated to char-
acteristics which are on the exclusion list. Phrases are not allocated to the new phrase
sets. Assignments of phrase sets to characteristics that already exist are not overwrit-
ten by the system.
2.f. 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.

If the explanation component shall be used and the phrase sets were generated
by the automatic customizing functionality "Create Standard Phrase Sets", it is neces-
sary 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.
2.g. Run transaction CGCZ "Match up master data" with flag "Activate Phras-
ing of Characteristics" only. This function assigns the function module
INTERNAL: SAP CUSTOMER 144 © SAP SE
 How To ...

C14K_PHRASECHARACT_CHECK to all characteristics where phrase sets have

been assigned (see transaction CGAB). 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 transac-
tion, 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.

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 automatically created symbols using the transaction CGCZ are gen-
erated with descriptions which are copies of the characteristics descriptions in the logon lan-

INTERNAL: SAP CUSTOMER 145 © SAP SE

 How To ...

guage. The flag "Regenerate Symbol Descriptions" within transaction CGCZ can be used to
generate the symbol descriptions in another language different from the logon language. En-
glish or German are possible symbol descriptions languages when property tree packages are
installed where the characteristics descriptions are delivered in English and German.

If the transaction CGCZ is run with the flag "Match Up Symbols-Phrase-Enabled Characteris-
tics" the symbol definitions for the characteristic symbols that have been changed from phrase-
related to non-phrase-related (or vice versa) will be updated..

A.7. How to set up the Table-based Value Assign-

ment
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

In the following, both ways are described:

1. Set up Table-based Value Assignment for new properties

1.1. Navigate to the activity "Set Up Table-Based Value Assignment" in the SAP customiz-
ing (IMG) (path: 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:

INTERNAL: SAP CUSTOMER 146 © SAP SE

 How To ...

1.3. Choose the entry "Create Entries for the Value Assignments". The window "Filling
Customizing Table for Table-based Value Assignment" appears:

INTERNAL: SAP CUSTOMER 147 © SAP SE

 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 (List Data").

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 be-
cause this would create multiple entries in the customizing table!
1.5. Return to the previous window (push button "Back"):

INTERNAL: SAP CUSTOMER 148 © SAP SE

 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.7. Return to the previous window (push button "Back"):
1.8. Repeat the steps 1.2 to 1.7 to create the necessary entries for all new properties.
2. Set up Table-based Value Assignment for existing properties with new characteristics

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 rec-
ommended procedure is to delete all entries for existing properties with new characteristics
in the customizing table and to create the entries for these properties anew (see the follow-
ing steps 2.1 to 2.14).

If the configuration of the Table-Based Value Assignment for properties with new character-
istics 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 request).

2.1. Navigate to the activity "Set Up Table-Based Value Assignment" in the SAP customiz-
ing (IMG) (path: 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.
2.2. Start the activity. The following screen appears:

INTERNAL: SAP CUSTOMER 149 © SAP SE

 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").
2.7. Return to the previous window:
2.8. Choose the entry "Create Entries for the Value Assignments". The window "Filling
Customizing Table for Table-based Value Assignment" appears:

INTERNAL: SAP CUSTOMER 150 © SAP SE

 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.11. Return to the previous window:
2.12. Choose the entry "Set Up Table-Based Value Assignment" again. The customizing
table opens. Check all entries for the configured property:
2.13. Return to the previous window (push button "Back"):
2.14. Repeat the steps 2.2 to 2.13 to create the necessary entries for all existing properties
with new characteristics.

INTERNAL: SAP CUSTOMER 151 © SAP SE

 How To ...

A.8. How to check and extend copy/inheritance

templates
The following steps are necessary to check and extend copy/inheritance templates:

1. Check copy/inheritance templates and assign one of the new properties to an existing tem-
plate, if necessary.
2. It is recommended to proceed as follows:
2.a. Navigate to the substance workbench or run transaction CG02.
2.b. Select "Find Substance" (double-click) on the initial screen. It is not necessary to start
a search and create a hit list.
2.c. Make sure that you are working in the "Edit" mode and not the "Display" mode. You
may change from "Display" to "Edit" mode using the pushbutton "Display <-> Edit (Ctrl
+F1)".
2.d. Navigate in the menu to "Specification" -> "Inheritance" -> "Edit Templates".
2.e. A selection screen opens where you select the template you want to edit. Choose the
pushbutton "Inheritance Templates Detail View". A detail window opens.
2.f. Choose the option "Value assignment type selection" where you can add new proper-
ties to the copy/inheritance template.
2.g. Select a new property. Choose the pushbutton "Transfer (Enter)".
2.h. A new window opens. Choose one of the pushbuttons "Replace" or "Supplement".
2.i. Choose the pushbutton "Transfer (F8)" on the next screen.
2.j. Complete this process by choosing the pushbutton "Save (Ctrl+S)" on the following
selection screen.
2.k. Choose the pushbutton "Transfer (Enter)" to return to the hit list.

A.9. 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.

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
INTERNAL: SAP CUSTOMER 152 © SAP SE
 How To ...

Active library remains empty

Distributor SAP SE
Publication Date
Version library version
Phr. ChkRtn
Object name ESN_PHRID
Int. no. range 0I
Ext. no. range 0E

A.10. 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).

A.11. How to implement correct language keys

for English and Portuguese variants (EN/6N/Z8,
PT1/1P/Z9)
During the history SAP has made use of different language keys for UK English / US English
and for European and Brazilian language variants.

ERC supports both models. During the ERC implementation decisions are required based on
the language keys that have been defined in the system, in which ERC shall be implemented.

Major difference is that in previous systems (here references as R/3 systems) the use of so-
called corresponding languages Z8 and Z9 has been supported. This is not supported in SAP
S/4HANA systems, so that only the SAP standard language keys are available. Please note
that the language keys for EN and PT have different meanings in both concepts.

language key R/3 meaning

Z8 US English
EN British English

INTERNAL: SAP CUSTOMER 153 © SAP SE

 How To ...

PT European Portuguese
Z9 Brazil Portuguese

language key SAP S/4HANA meaning

EN US English
6N British English
1P European Portuguese
PT Brazil Portuguese

After decision for a model has been made, please take care about the following:

• ERC provides different phrase import files for both models.

Please make sure, that the correct phrase import file from delivery folder 02-Phrases is used.
In both cases the source language is EN

Location for phrase files supporting language key R/3: \\dwdf212\reg_content\CLEO

\ERC_####\11-Deliveries\02-Phrases\01-CED_Standard_####

Location for phrase files supporting language key SAP S/4HANA (only ERC3.0 contracts):
\\dwdf212\reg_content\CLEO\ERC_####\11-Deliveries\02-Phrases\03-CED_S4_####. In
Release 1805 there is only a initial version, later releases include also update files.

#### representing the release number

• There are no differences in customizing transports. They are always provided with language
key EN. All customizing transports can be used for both models.
• There are no differences in regulatory data (neither Product Safety, nor Dangerous Goods
data). The xml-files for regulatory data contain data (especially identifiers) with all variants
when applicable. During OCC data loads OCC identifies, if a language key is not present in
the target system and ignores elements with those language keys.

Please note: the phrase files provided with the regulatory data (library TDCLE) is not deliv-
ered with variants. These files contain all relevant languages in one import file. Thus, the im-
port files from folders \03-ContentData\ProductSafety\3-Phrases and \03-ContentData\Dan-
gerousGoods\EHS\2-Phrases can be used for both models.
• Expert rule sets are independent of the settings above.
• WWI templates are independent of the settings above.
• Report languages for safety data sheets need to be configured according to the settings
above. E.g. if the language keys according to R/3 are applied, then for the US SDS select
the report language Z8. Select EN, if the language keys according to an SAP S/4HANA
system are applied.

Please note: in both models maintain the settings for generation variants in tab Rat-
ing/Validity area under listing Validity Areas as EN as documented in the document
RGV_####_Configuration.pdf (supplied with each release, #### represents release num-
ber).

A.12. How to import phrases

Choose Data Transfer - > Phrases (Transaction CG31) ; please see screen shot below.

INTERNAL: SAP CUSTOMER 154 © SAP SE

 How To ...

• "File with path" - Enter the path and file name (same as target file section upload files )
• For all files choose UTF-8 as character standard.
• You can leave all other options blank
• Optional: You can limit the import to certain languages if you want (Button "Language se-
lection" )
• Check the file (F5)
• Carefully check the displayed information before importing the phrases. Make sure you im-
port to the passive CED or TDCLE library, the versions are correct and no errors are dis-
played.
• 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
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!

INTERNAL: SAP CUSTOMER 155 © SAP SE

 How To ...

A.13. 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:

INTERNAL: SAP CUSTOMER 156 © SAP SE

 How To ...

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.

INTERNAL: SAP CUSTOMER 157 © SAP SE

 How To ...

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 thou-
sand 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).

A.14. 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)

• "File with path" - Enter the path and file name (same as target file section upload files )

• Check the "Phrase Set Assignmt" option as shown in the screenshot below

• Check the file (F5)

INTERNAL: SAP CUSTOMER 158 © SAP SE

 How To ...

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 mainte-

INTERNAL: SAP CUSTOMER 159 © SAP SE

 How To ...

nance 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 reg-
ular maintenance. Should you need any additional info on this topic please feel free to contact
us.

A.15. How to combine/retire phrases

A.15.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 com-
bined 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

INTERNAL: SAP CUSTOMER 160 © SAP SE

 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.15.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

INTERNAL: SAP CUSTOMER 161 © SAP SE

 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.16. 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. 10°C, 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 phras-
es 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 1146663 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.17. 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 the latest version.

Note
For installation local administrator rights might be required. Registry settings will be
added under the following paths:

INTERNAL: SAP CUSTOMER 162 © SAP SE

 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.17.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.

A.18. 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 Destina-
tion 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 structure the name as follows:

EHS_MGMT_<computer name of server>
• Connection type: T
• 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.
2. Confirm your entries.
3. On the Technical Settings tab page in the Activation Type screen area, set the flag to Reg-
istered Server Program.

INTERNAL: SAP CUSTOMER 163 © SAP SE

 How To ...

4. In the Registered Server Program screen area, enter the PROGID entry from your installa-
tion (see How to install EHS Expert or entry in the file SAPRFC.ini) in the program ID field.
5. Save your entries

RFC Destination for EHS Expert

1. Choose Edit -> Create.

The RFC Destination screen appears. Enter the following data:

• 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
• Description: Enter a text to describe the RFC destination.
2. Confirm your entries.
3. On the Technical Settings tab page in the Activation Type screen area, set the flag to Reg-
istered 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.
5. If the SAP system comprises a number of application servers, you must specify under Gate-
way 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
INTERNAL: SAP CUSTOMER 164 © SAP SE
 How To ...

RFC Destination for OCC

1. Choose Edit -> Create.

The RFC Destination screen appears. Enter the following data:

• RFC destination: Name of your RFC destination, for example EHS_OCC

This entry corresponds to the entry for the EXPERT_DESTINATION parameter for the
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
• Description: Enter a text to describe the RFC destination: EHS Open Content Connector
2. Confirm your entries.
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

INTERNAL: SAP CUSTOMER 165 © SAP SE

 How To ...

5. Save your entries

A.19. 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).
• In the RFC Destinations tree, choose TCP/IP connections -> <name of your RFC destina-
tion> and open the destination with a double-click.
• Choose Test connection.

INTERNAL: SAP CUSTOMER 166 © SAP SE

 How To ...

The test is running successfully if transmission duration times are displayed in the SAP window.

A.20. How to extend entry in secondary data de-

termination
In the example at the bottom you can see the typically used entries for secondary data deter-
mination 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).

INTERNAL: SAP CUSTOMER 167 © SAP SE

 How To ...

3. Choose Parameters and Values.

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 de-
activated 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 da-
ta 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

INTERNAL: SAP CUSTOMER 168 © SAP SE

 How To ...

Corresponds with the name of the RFC destination that is entered under Tools -> Adminis-
tration -> 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/ex-
clude indicator). The parameter numbering has to start with 1 and has to be consecutive.

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

INTERNAL: SAP CUSTOMER 169 © SAP SE

 How To ...

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 Da-
ta 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 Sec-
ondary 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.

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 Authoriza-
tion 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

INTERNAL: SAP CUSTOMER 170 © SAP SE

 How To ...

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 parame-
ters EXPERT_EXPLANATION_ESTCAT, EXPERT_EXPLANATION_RULE_PROP, and
EXPERT_EXPLANATION_DATE_PROP as described below. Please note that this option
requires the implementation of OSS note no. 1450276!

You set up the explanation component (optional) of the EHS Expert using the following pa-
rameters:

• 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

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. Please note
that this option requires the implementation of OSS note no. 1450276!
• 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

INTERNAL: SAP CUSTOMER 171 © SAP SE

 How To ...

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
database if it is stored in a password protected storage location or web server.
• 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

In this parameter you can specify a second identifier that OCC should use when look-
ing 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.
• EXPERT_TAB_FIELD_5

In this parameter you can specify a third identifier that OCC should use when look-
ing for substance data. This is identifier is only used when the identifiers specified in
EXPERT_TAB_FIELD_2 and EXPERT_TAB_FIELD_4 do not give a search result. The main
purpose is for loading data that is not assigned to CAS numbers, e.g. by using PMN numbers.

Typical Example Expert Rule set:

Environment parameter Sample value
EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_DISPLAY
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_WORLD
EXPERT_RES_BY_SRSID_OWNID_FLG X

INTERNAL: SAP CUSTOMER 172 © SAP SE

 How To ...

EXPERT_RULE_SET ZEXP_GHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_GHS
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

Typical Example OCC data load:

Environment parameter Sample Value

EXPERT_ADD_PARAM_1 headerurl=<path to ERC PS DB>\PS_DB
\header.xml
EXPERT_ADD_PARAM_2 usernameurl=x
EXPERT_ADD_PARAM_3 passwordurl=x
EXPERT_CALL_ONCE X
EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE I
EXPERT_DESTINATION EHS_OCC
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE H
EXPERT_READ_RATING
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG
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_TAB_FIELD_5 <identifier>[NUM,PMN]
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID TECHNIDATA
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

A.21. 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 func-
tion modules.

INTERNAL: SAP CUSTOMER 173 © SAP SE

 How To ...

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 anal-
ogous to the reference function module and its interface.

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.22. How to add user defined text types

To add new data origins use transaction "spro" for the IMG customizing. Navigate to Environ-
ment, Health & Safety ->Basic Data and Tools -> Specification Management -> Additional In-
formation for Value Assignment -> Specify User-Defined Text Types.

• Press F5 or "New Entries"

• Enter the user defined text types (limited to 10 characters)
• Give a note / description
• Assign a specification category
• Save your settings

A.23. How to add data origins

To add new data origins use transaction "spro" for the IMG customizing. Navigate to Environ-
ment, Health & Safety ->Basic Data and Tools -> Tools -> Import ans Export -> Basic Settings
for Import and Export -> Specify Data Origins.

• Press F5 or "New Entries"

• Enter the Data Origin (limited to 10 characters)
• Optionally you may assign an Exchange Profile
• Give a note / description
• Save your settings

INTERNAL: SAP CUSTOMER 174 © SAP SE

 How To ...

A.24. 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

A.25. 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 Manage-
ment -> Additional Information for Value Assignment -> Specify Sources.

• Press F5 or "New Entries"

• 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.

INTERNAL: SAP CUSTOMER 175 © SAP SE

 How To ...

• Pressing F5 or "New Entries" you can enter the Specification category like "SUBSTANCE".

A.26. 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 rec-
ommended - 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.

INTERNAL: SAP CUSTOMER 176 © SAP SE

 How To ...

A.27. How to add dangerous goods master data

SAP EHS offers wide customizing options regarding dangerous goods master data. Mainte-
nance 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 multi-
ple customizing items. In the following those customizing activities that may be relevant are
described in detail.

A.27.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:

INTERNAL: SAP CUSTOMER 177 © SAP SE

 How To ...

• Press F5 or " New Entries"

• 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.27.2. Risk Potentials

Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Basic Data - Specify Risk Potential:

• Press F5 or " New Entries"

• 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.27.3. Hazard Identification Numbers

Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Common Settings - Specify Hazard Identification
Numbers:

• Press F5 or " New Entries"

• 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.27.4. Danger Labels

Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Common Settings - Specify Danger Labels:

• Press F5 or " New Entries"

• 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.27.5. Packing Instruction Numbers

Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Common Settings - Specify Packing Instruction
Numbers: (these entries are just used in RiscClssification for creation of transport documents)

• Press F5 or " New Entries"

• Enter the DG regulation the packing instruction number shall be relevant for
• Enter the packing instruction number and a description
• Save your settings

INTERNAL: SAP CUSTOMER 178 © SAP SE

 How To ...

A.27.6. Categories of Instructions for Enclosure and In-

structions for Enclosure
Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
Management - Basic Data and Master Data - Common Settings - Specify Categories for En-
closure: (these entries of packing instructions are used in PackingRequirements)

• Press F5 or " New Entries"

• 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.27.7. Packing Codes

Start transaction SPRO and navigate to Environment, Health and Safety - Dangerous Goods
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))

• Press F5 or " New Entries"

• Enter Packing code with description and regulation the new code shall be relevant for
• Save your settings

A.28. 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_WORLD" 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.
• Please see also SAP Note 603152 - Country Codes for Serbia
and Montenegro

INTERNAL: SAP CUSTOMER 179 © SAP SE

 How To ...

• Go to the IMG customizing ("spro"):

• Navigate to Environment, Health and Safety -> Basic Data and Tools -> Additional Informa-
tion 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

• 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.

INTERNAL: SAP CUSTOMER 180 © SAP SE

 How To ...

A.29. How to create extended search user exit

A new entry for an extended search user exit can be added in SAP EHS customizing.

Activities
1. In Customizing for Basic Data and Tools, call the IMG activity Manage User Exits.
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 C1H0_SUB_FIND_BY_PRO_FILE
User exit description EN: New Data Available for Substance...
DE: Für Stoff liegen neue Daten vor...
Function Module Name C1H0_SUB_FIND_BY_VALU
3. Parameters and Values are not required for a search user exit and you can leave them
empty.

A.30. How to setup/update XML substance

database for substance lists and reference data
Note
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. ERC_PS_Region_
2015-2.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
Please carefully check the installation path if you are updating an existing database 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.

Note
Customers who have licensed both the SAP EHS Regulatory Content SDS Authoring
and Marketability packages have the possibility to load regulatory lists data from both
packages with one data load.

INTERNAL: SAP CUSTOMER 181 © SAP SE

 How To ...

In case you have licensed both, SDS-Authoring and Marketability, and you load both
packages with one data load, please do not install the SDS-Authoring package for list
data. Instead, please use the Marketability installation file and follow the instructions
there to install the combined content for both packages.

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>\ERC-PS\ main folder with index file and version info
(header.xml and version.txt)
<path to XML substance database>\ERC-PS subfolder with all CAS numbers starting with 1
\1
<path to XML substance database>\ERC-PS subfolders for other CAS numbers starting
\... with 2 to 9
<path to XML substance database>\ERC-PS subfolder with all substance groups
\G
<path to XML substance database>\ERC-PS subfolder with all non-substances data, e.g.
\N mixtures and data with no CAS number

Dangerous Goods and Dangerous Goods with Packaging

Data:
<path to XML substance database>\ERC-DG\ main folder with index file and version info
(head.xml and version.txt)
<path to XML substance database>\ERC-DG subfolder with all data for DG regulation
\ADN ADN(R)
<path to XML substance database>\ERC-DG subfolders for other DG regulations
\...
<path to XML substance database>\ERC-DG 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 front-
end computer, SAP application server and the storage location of the XML substance

INTERNAL: SAP CUSTOMER 182 © SAP SE

 How To ...

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.31. 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 Reg-
ulatory 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 net-
work-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 cre-
ating 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 front-
end 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.

INTERNAL: SAP CUSTOMER 183 © SAP SE

 How To ...

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 re-
quired:

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: CUST-

Replace 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 databas-
es. 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 made your own changes to the mapping database, e.g. renamed identifiers or
phrase mapping changes, please take care to implement your changes also in the new map-
ping 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

INTERNAL: SAP CUSTOMER 184 © SAP SE

 How To ...

• 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 avail-
able after the first data load.

In all tables, Internal_id means the key/value in the database and External_id the correspond-
ing key/value in SAP EHS.

A.32. 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 and newer) to your Excel template folder, usually ...\Documents\<user>\Application
Data\Microsoft\Templates

Note
In Excel 2013 the default personal templates location is sometimes empty. Please
check in your Excel Options under ->Save ->Default personal templates location
that a folder is specified. Make sure the simulation spreadsheet has been copied
to this folder. If no folder is specified, you can select your own folder to store Excel
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
• It is also possible to open the simulation Excel files directly, without specifying them as a
template.

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.

INTERNAL: SAP CUSTOMER 185 © SAP SE

 How To ...

Note
In MS Excel 2007, you need to save this Excel file in a trusted directory or you cannot
activate the macros.

A.33. 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 the latest version or contact us for the settings in older OCC versions.

Note
If multiple installations of the database exist for test, development and productive sys-
tems, the below steps must be repeated for all of them. Assign the name of the in-
stances 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:

• 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"

INTERNAL: SAP CUSTOMER 186 © SAP SE

 How To ...

Dangerous Goods / Packaging Data

A new system entry has to be configured for Dangerous Goods/Packaging Data:

• Execute OCC: ->Start -> Programs -> EHS -> Open Content Connector
• 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

INTERNAL: SAP CUSTOMER 187 © SAP SE

 How To ...

A new instance entry has to be configured for Dangerous Goods/Packaging Data:

• Execute OCC: ->Start -> Programs -> EHS -> Open Content Connector
• Choose: Options -> Instance Configuration ...
• 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"

INTERNAL: SAP CUSTOMER 188 © SAP SE

 How To ...

A.34. How to configure the User Exit for SAP EHS

Regulatory Content - substance lists and refer-
ence 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 ERC_PS or ERC_DG
EXPERT_ADD_PARAM_1 headerurl=<path to XML substance
database>\header.xml

INTERNAL: SAP CUSTOMER 189 © SAP SE

 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

database>\header.xml
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

INTERNAL: SAP CUSTOMER 190 © SAP SE

 How To ...

Example A.1. Additional Test System Database

An additional database for the test system was created at F:\ERC-TEST:

• Additional registry-key needed for instance ERC-TEST

• Path to mapping database for new instance in registry changed to F:\ERC-TEST\td_
cleo.mdb
• Existing User Exit, e.g. ERC_PS copied to new key, e.g. ERC_TEST
• In new User Exit, change EXPERT_ADD_PARAM_1 to: headerurl= F:\ERC-TEST
\header.xml
• In new User Exit, change EXPERT_RULE_SET to: ERC-TEST

A.35. How to adjust the Fact Mapping

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.

A.35.1. Adjusting Fact Mapping to Load a CAS Number

Example how you can add a CAS number as identifier if you load your substance with a PMN
number:

Table Field Value

Record
DispOrder 96
Internal_Id NUM_CAS
Group
External_Id I:NUM,CAS;DUMMY,UPDDAT,LANGU,IDENT,SUBLIST
Language EN

INTERNAL: SAP CUSTOMER 191 © SAP SE

 How To ...

Table Field Value

Description CAS Number
IsPhrase yes
Options /DISP=1/MAP=SUBLIST/SEP="|"

A.36. 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 Options that govern access to the data in EHS more closely

The first two fields together identify the record uniquely in the set of rules.

A.37. 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 corre-
sponding 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)

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 ex-
ample [#R20#] .
External_Id Phrase key in EHS
Phrasetext Phrase text
Options Options that govern access to the data in EHS more closely

In some cases it might be necessary to enhance/adapt the phrase mapping manually.

INTERNAL: SAP CUSTOMER 192 © SAP SE

 How To ...

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 cata-
logue 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).

A.38. 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)

• EXPERT_EXPLANATION_ESTCAT = SAP_EHS_0101_002 (property the explanation is
stored at)
• EXPERT_EXPLANATION_RULE_PROP = SAP_EHS_0101_002_RULESET (characteris-
tic within the property given above to save the user-exit name)
• EXPERT_EXPLANATION_DATE_PROP = SAP_EHS_0101_002_RUN_DATE (character-
istic where the date of the last run shall be stored)

A.39. SAP EHS Regulatory Content - substance

lists and reference data (Product Safety) Update
Data Load

INTERNAL: SAP CUSTOMER 193 © SAP SE

 How To ...

A.39.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.39.2. Update Cached Data

Start a data load with 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.

A.39.3. Review New Filter Settings

For the new lists added with this release, please check the filter settings and change the stan-
dard 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.39.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 ...“

INTERNAL: SAP CUSTOMER 194 © SAP SE

 How To ...

2. Specify the path to the file erc_update_<version>.txt which can be found in folder 6-Up-
dateTools.

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.

INTERNAL: SAP CUSTOMER 195 © SAP SE

 How To ...

5. We recommend saving the created hit list so you have it available in the future without re-
running the query.

Note
We also provide a file erc_new_group_assignments_<version>.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 - sub-
stance 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 there-
fore 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.39.4.1. 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 SAP ERC Product Safety Data (or a
comparable entry available in your system)

->Utilities -> Secondary Data -> Determination -> SAP ERC Product Safety Data
4. Select a substance and press "Set Filters"

5. Set data options "Load Changes Only" and optionally "Use Substance Groups"

INTERNAL: SAP CUSTOMER 196 © SAP SE

 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.39.4.2. 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 ERC_simulation.xltm as a
template:

-> File -> New -> New from template -> General Templates -> ERC_simulation.xltm
2. When prompted, enable macros
3. Open the spreadsheet with the new and revised list substance data you created during the
data load simulation if it is no longer open
4. 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)
5. Click the button Start Analysis to analyze the imported OCC data.
6. 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

INTERNAL: SAP CUSTOMER 197 © SAP SE

 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 ERC => 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.39.4.3. 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.39.4.3.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.

INTERNAL: SAP CUSTOMER 198 © SAP SE

 How To ...

1. Create a hit list of substances either manually or as described in Section A.39.4, “Hit List
of List Substances”
2. Select (all) substances
3. Start the secondary data determination and choose SAP ERC Product Safety Data (or a
comparable entry available in your system)

->Utilities -> Secondary Data -> Determination -> SAP ERC Product Safety Data
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.39.4.3.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.39.4, “Hit List
of List Substances”
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 -> SAP ERC Product Safety Data
4. 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. 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.40. How to install EHS Expert

INTERNAL: SAP CUSTOMER 199 © SAP SE
 How To ...

Tip
We recommend to set up separate Expert Server PCs for your test and for your pro-
ductive system.

A.40.1. Initial Installation of Expert

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
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 Adminis-
tration 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:

5. ODBC-(Database) drivers to access mapping databases are installed automatically, if they

do not already exist.
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>

INTERNAL: SAP CUSTOMER 200 © SAP SE

 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 regis-
tered RFC connection. This means that the
EHS Management Service logs itself onto
the system)
GWHOST=sma85 Router string + application server
GWSERV=sapgw00 Gateway service: contains the string sapgw
and the system number
MANAGED=1 defines that this destination is an EHS-Man-
agement-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.40.2. Upgrading of older Expert versions

1. Download the latest SAP EHS Expert and OCC setup files. See chapter Where to get EHS
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

INTERNAL: SAP CUSTOMER 201 © SAP SE

 How To ...

A.40.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.41. 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 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 need-
ed.

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.42. 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 Adminis-
tration 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.

INTERNAL: SAP CUSTOMER 202 © SAP SE

 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)
• Confirm your entries.
• 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

INTERNAL: SAP CUSTOMER 203 © SAP SE

 How To ...

• The SAPRFC.ini file will be updated automatically on the Expert Server PC using the Pro-
gram 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.43. 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

INTERNAL: SAP CUSTOMER 204 © SAP SE

 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\Current-
ControlSet\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)
• 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 func-
tions as a database server. (Default value = 20)
• 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 func-
tions 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 delet-
ed. 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.

INTERNAL: SAP CUSTOMER 205 © SAP SE

 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.44. 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 param-
eter -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.45. How to add user-defined DG texts

User-defined dangerous goods texts are regulation-dependant and may be assigned to spe-
cific 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 Dang-
Goods 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.46. How to add a value assignment rating

INTERNAL: SAP CUSTOMER 206 © SAP SE
 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.47. SAP Setup for SAP EHS Regulatory Content

Expert Rule Sets
SAP Front End installation (SAP Setup)

A.47.1. Overview
The SAP EHS Regulatory Content Expert Rule Sets can now be installed with the help of SAP
Setup on the Expert-Server.

INTERNAL: SAP CUSTOMER 207 © SAP SE

 How To ...

Note

SAP ERC Rule Sets can be installed and updated on the Expert Server either
with the help of SAP Setup or manually. However for an individual rule set It is not
recommended to use both methods. Therefore if SAP Setup has been used for a
particular rule set, future updates should also be performed using SAP Setup.
For initial installations of SAP ERC Rule Sets the SAP Setup can be used as
detailed below.
However for an update of rule sets using SAP Setup the following additional steps
are required:
1) Backup of existing rule sets - make a copy of the <EXPERT>\Rules directory
2) Start the setup for rule sets and install new versions (existing rule instances
will be overwritten)
3) Make customer specific changes in the mapping databases and external value
databases
In case of intermediate corrections of ruc-files, the instance in the registry needs
to be changed manually (by using ExpertAdmin or transaction cgsadm).
For the next regular update SAPSetup can then again be used, but the intermedi-
ate version of the ruc-file will not be deleted by SAPSetup. This has no impact on
the functionality. The intermediate version of the ruc-file can be deleted manually.

The Setup offers two possibilities

• Installation: Copy rule set files into the specified Rules Directory on the Expert Server PC
and create registry settings for all needed instances.
• Registration: Create registry settings for all needed instances. The rule set files need to be
transferred manually.

Our recommended procedure is the following:

1. Use SAP Setup to install all needed Expert Rule Sets on a test or QA Expert Server
2. Perform all tests and make necessary adjustments to the mapping mdbs or external tables
on the test or QA Expert server
3. Use SAP Setup’s registration option to create all registry settings needed on any Production
Expert Servers.
4. Transfer Rule Set files from the test or QA Expert Server to the Production Expert Server(s)

This procedure will ensure necessary registry entries are created for all rules, while also en-
suring consistency between QA and Production environments. Detailed steps for this proce-
dure follow below.

INTERNAL: SAP CUSTOMER 208 © SAP SE

 How To ...

A yellow dot indicates a change in the selection list. A green plus sign next to a rule set package
or rule set name indicates that this rule set will be installed.

INTERNAL: SAP CUSTOMER 209 © SAP SE

 How To ...

If you deselect an installed SAP front end component in this list, a red minus sign indicates
that this rule set package or rule set will be deinstalled.

INTERNAL: SAP CUSTOMER 210 © SAP SE

 How To ...

You can select all rule files in one click by choosing "Select all".

When updating from one SAP ERC release to the next SAP ERC release (e.g. from ERC1605
to ERC1611) it is important to choose "Select all" that all rule sets are updated and new rule
sets are installed on the Expert Server PC.

INTERNAL: SAP CUSTOMER 211 © SAP SE

 How To ...

A.47.2. Installation on the Test or QA Expert Server

Prerequisites

• Access to the Test or QA Expert Server PC

• The user logged on to the PC must have local administrator privileges.

Procedure

• Create a backup of the .mdb files before installation, as the files get overwritten during the
installation process.
• Start SetupERC_<package>.exe (e.g. SetupERC_GLOBAL.exe)
• The installation starts and a progress screen is displayed.
• Choose next
• The list of EHS Regulatory Content rule sets is displayed.
• Choose the rule sets from "Installation"
• Select the rule sets that you want to install or deselect the ones you want to remove.

A yellow dot indicates a change in the selection list. A green plus sign next to a rule set
package or rule set name indicates that this rule set will be installed.

If you deselect an installed SAP front end component in this list, a red minus sign indicates
that this rule set package or rule set will be uninstalled.

INTERNAL: SAP CUSTOMER 212 © SAP SE

 How To ...

• Choose next

The installation starts and a progress screen is displayed.

Once the installation is complete, a confirmation screen is displayed. The rule sets are now
successfully installed.
• Verify the mapping databases and the settings in the external tables and adapt them if nec-
essary.

A.47.3. Installation on the Productive Expert Server

Prerequisites

• Access to the Productive Expert Server PC

• The user logged on to the PC must have local administrator privileges.

Procedure

• Create a backup of the .mdb files before installation (just as a precaution, the files are not
overwritten during the registration process)
• Start SetupERC_<package>.exe (e.g. SetupERC_GLOBAL.exe)
• The installation starts and a progress screen is displayed.
• Choose next

The list of EHS Regulatory Content rule sets is displayed.

• Choose the rule sets from "Registration"
• Select the rule sets that you want to register or deselect the ones you want to remove.

A yellow dot indicates a change in the selection list. A green plus sign next to a rule set
package or rule set name indicates that this rule set will be registered.

If you deselect an installed SAP front end component in this list, a red minus sign indicates
that this rule set package or rule set will be uninstalled.
• Choose next

The installation starts and a progress screen is displayed.

Once the registration is complete, a confirmation screen is displayed. The rule sets are now
successfully registered.
• Copy the rule set files form the Test or QA Expert Server to the Productive Expert Server.

A.48. 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
INTERNAL: SAP CUSTOMER 213 © SAP SE
 How To ...

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.

INTERNAL: SAP CUSTOMER 214 © SAP SE

 How To ...

A.49. 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. 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.

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

For example for the rule set GHS:

Name = ZEXP_GHS, Rule File = GHS_V1-6.ruc, Mapping Database = GHS_V1-6.mdb

INTERNAL: SAP CUSTOMER 215 © SAP SE

 How To ...

3. Save you settings by Apply

A.50. 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 determi-
nation 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 environ-
ment parameters in the Determine secondary data dialog box when secondary data de-
INTERNAL: SAP CUSTOMER 216 © SAP SE
 How To ...

termination is started. The environment parameters set in Customizing are displayed as

default values. Enter or change the environment parameters as required.
• 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 specifi-
cations 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.51. How to display the Explanation Component

Some of the SAP EHS Regulatory Content - expert rules for substance and mixture classifica-
tion 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 de-
scription. The default settings are:
• EXPERT_EXPLANATION_SAVE = X (invokes the explanation)
• EXPERT_EXPLANATION_ESTCAT = SAP_EHS_0101_002 (property the explanation is
stored at)
• EXPERT_EXPLANATION_RULE_PROP = SAP_EHS_0101_002_RULESET (character-
istic within the property given above to save the user-exit name)
• 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 auto-
matically 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

INTERNAL: SAP CUSTOMER 217 © SAP SE

 How To ...

phrase set assignment may be made automatically with standard property tree upgrades;
in this case this has to be undone manually!
• 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) EXPERT_EXPLANATION_DATE_PROP = 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.

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.52. How to use the UPO functionality

Expert rules sets are typically determining secondary data based on primary data. Primary and
secondary data are different. However, there are cases – especially when input data is partially
incomplete – the user might have information that is more precise than the result derived by the
rule, e.g. from communication with a vendor. In those cases the user is interested to provide
this data as rule input and expects that the rule is considering this as output instead of the
calculated result. In the calculation process that means that a user either needs to switch off the
rule execution completely and maintains the data always manually at least for this specification
or the rule is executed once, the information is overwritten by user and the rule calculation
is switched-off for future protection of the user maintained value. Both process options are
leading to inconvenience – especially, when partial output information is provided by a user and
partial information needs to be added by the rule (e.g. VOC value, while all other information
from the rule like remarks, regulatory basis etc. are OK). To support the automated process of
rules execution an additional coding principle has been introduced to some rules to achieve
that the expert rules are enabled to consider user provided output (UPO) as input. The data
that should be considered for output is maintained in the same fields as the usual rule output.
This input needs to be maintained in a way that it exclusively accessible to the expert rules
without any impact on other processes (e.g. SDS or ALE processes for data distribution).

This is accomplished by using a specific rating “UPO” for the user provided output information.

This user provided output (UPO) is merged into the rules output and has precedence over the
information derived by the rule logic. This UPO does not need to cover all rules output fields. If
partial information is given, the rule takes the UPO and adds its output as derived by the normal
calculation. The logic which UPO information can be provided and how the logic form merging
this UPO input into the rules output is rule-specific and will be documented in the functional
description of the individual rules. If no UPO is given, the rule derives its result as normal.

Example from WGK rule

Scenario: a mixture has a major component with an unknown water pollution class. The WGK
rule applies the worst case scenario that leads to a water pollution class 3:

INTERNAL: SAP CUSTOMER 218 © SAP SE

 How To ...

From the vendor safety data sheet for the mixture it is derived that the mixture has a water
pollution class 2, which is the classification that the user would like to get as output from the
rule. This information can be maintained with a rating UPO (user provided output) in the WGK
output property as follows:

This information is then merged into the result of the WGK rule in precedence over the usual
result leading to a WGK of 2 for the mixture:

INTERNAL: SAP CUSTOMER 219 © SAP SE

 How To ...

The UPO information regarding the water pollution class has been merged into the rules result.
Regulatory Basis, Reference and output usage are standard results, while the Water Pollution
Class is merged from the UPO rated instance. To indicate that UPO has been considered, the
source note is followed by the letters UPO

A.53. 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 Ser-
vice (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

INTERNAL: SAP CUSTOMER 220 © SAP SE

 How To ...

To activate the logging please go to the Application Parameters tab page and tick the "Log-
ging" 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.

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:

The path can only be chosen by a click on the icon

Then choose the icon next to view the directory structure

Mark the files to be transferred and choose the storage path on you computer afterwards

INTERNAL: SAP CUSTOMER 221 © SAP SE

 How To ...

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
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.

INTERNAL: SAP CUSTOMER 222 © SAP SE

 How To ...

A.54. 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 HazardComp_US_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_RANGES T:Ranges/HazardComp_US_externvalues.mdb

Example: Record-Mapping – Full declaration of the path for the external data

INTERNAL: SAP CUSTOMER 223 © SAP SE

 How To ...

Internal_id External_id
EXT_RANGES T:Ranges/C:\Program Files\EHS\Expert\Rules
\HazardComp_US_externvalues.mdb

Example: Fact-Mapping –Installation of the external data base in the same directory as the
rule set.

Internal_id External_id
i_limit_oel T:Threshold;OEL/HazardComp_US_externvalues.mdb

Example: Fact-Mapping –Full declaration of the path for the external data

Internal_id External_id
i_limit_oel T:Threshold;OEL/C:\Program Files\EHS\Expert\Rules
\HazardComp_US_externvalues.mdb

A documentation of the adjustable parameters could be obtained from the respective functional
descriptions of the rule sets.

A.55. 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 Options that govern access to the data in EHS more closely

A.56. How to use the History.mdb

The History database gives the user information and overview on changes applied to the map-
ping database of a rule set. All changes that have been applied to the mapping of a rule set
since the last release are documented in the History database. This includes the four standard
categories

• CHANGES_in_mapping_table_____ExpFactMap
• CHANGES_in_mapping_table_____ExpPhraseMap
• CHANGES_in_mapping_table_____ExpRecordMap
• CHANGES_in_mapping_table_____ExpGroupMap

Changes which have been made concerning the externvalues database are also documented
here, e.g.

• Changes_in_external_table____GHS_table

INTERNAL: SAP CUSTOMER 224 © SAP SE

 How To ...

• Table_Changes_in_external_table_not_P_Statements

There are three different cases of mapping changes: new entries, changed entries, and deleted
entries.

Every changed, new, or deleted entry is added to the HISTORY.mdb as a new line.

If there is a change, it is additionally checked if the given entry already exists in the
HISTORY.mdb (i.e. if it has already been changed in a former version); if this is the case, the
matching entry is updated and the old version information is preserved as described below.

The additional columns Version and Remark are maintained as follows:

Version:
• the version number without a preceding "V", e.g. "1.5"
• if a line is updated, the old Version entry is replaced by the new one

Remark: dependant on the type of change:

• new entry: "Vn-m: New"
• change: "Vn-m Changed (further description of change)"
• change after preliminary change: Vn-m: "Changed (...); V(n-i)-(m-j): New/Changed (...)/
Deleted"
• deleted entry: "Vn-m: Deleted"

With the help of the History database the key-user can easily adopt the Mapping to a newly
delivered version, if the company has fitted the mapping to their needs by adding , deleting or
changing phrases from the standard mapping database delivered by SAP.

A.57. 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.

INTERNAL: SAP CUSTOMER 225 © SAP SE

 How To ...

A.58. How to import report templates

First upload the dat-files (for example SDS_2015_2_EU_MAIN.dat) and doc-files (for example
SDS_2015_2_EU_MAIN.doc) on the application server using transfer format BIN (=>transac-
tion CG3Z).

If a UNIX system is used, choose the corresponding import settings to import a windows file.

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>

(Note that each dat-file contains the information to automatically pull the corresponding doc-
file. The doc-file itself should NOT be specified for the import.)
• Character standard: UFT-8

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 automatically open the new template document. Check the template by clicking on
the check-button and save it. If you encounter error messages at this stage, you can directly
take the relevant actions(i.e. set up missing ID-listings, etc.), or you may save the template
anyway and resolve the messages later.

A.59. 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.

INTERNAL: SAP CUSTOMER 226 © SAP SE

 How To ...

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.

A complete overview on the parameters of all generation variants can be found in the document
RGV_XXXX_Configuration.pdf (where XXXX stands for the current release).

A.60. How to disclose component names

This section describes the Component Name Disclosure in SDSs including trade secret re-
quirements.

Requirements
• Standard name

INTERNAL: SAP CUSTOMER 227 © SAP SE

 How To ...

Usually components in SDSs are listed by name that allows to identify the component with
a commonly used name. The name should be given in the language of the SDS. Often
regulations or best practices require a specific name that is used in some regulations or for
registration purposes (e.g. name from REACH registration in EU SDS section 3)
• trade secret name

Some regulations allow that a name of a component can be discarded (e.g. standard name
replaced by the words “trade secret” or replaced by a more generic name). This name is an
alternative name to the standard name

Required data maintenance

The above requirements create a need for at least two names for components – one used as
standard name and another one used as trade secret name. For other reasons potentially oth-
er names of components might be relevant (e.g. name of substance to be used in dangerous
goods shipping documents). Names are maintained as identifier. That means that for names
two identifiers are relevant. The standard name (e.g. NAM PROD) and the trade secret name
(e.g. NAM TRADESEC). As the identifiers are not called directly in the WWI template, but by
means of identification listings, it can be controlled by customization settings which identifiers
should be used for which scenario (standard or trade secret). So, other identifiers types as in
the above examples can be used, if customizing setting are adjusted accordingly. All names
need to be available in all relevant SDS languages. This can be achieved either by mainte-
nance of all relevant translations or by use of a technically language independent name that
can be used as a default, if no translated name is available. In this case the language inde-
pendent name usually holds the English translation. As there is no source generally available
for fully translated names, there are two approaches to maintain the standard name:

• Collect all names at a dedicated identifier (e.g. NAM PROD) by manually or logic-based
copying them from all potential sources (e.g. NAM ANNEXI, NAM EINECS, NAM ENCS, …).
Translation gaps can be either closed by translation or by use of a language independent
entry.
• Create an identification listing in customization, that holds all potential sources (e.g. NAM
ANNEXI, NAM EINECS, NAM ENCS, …) in a prioritized sort sequence. As translation gaps
will occur (e.g. NAM ANNEXI not available for all substances and only in selected lan-
guages), a language independent identifier should be given (e.g. NAM SYN) as fallback at
the lowest priority in the listing.

The trade secret name has to be included in a separate ID listing which is then used for the
disclosure of trade secret names.

Technical implementation in template

The WWI template is coded by using WWI functions to disclose different ID listings (instead of
direct identifier output). The relevant ID listings can be maintained as environment parameter
in customizing. These functions handle the output of a second ID listing for trade secret names.
This is controlled by the component type of the relevant composition. If the component type
is considered to be trade secret relevant (customization, e.g. TRADESEC) then instead of
the identifiers from the standard ID listing the identifiers from the trade secret ID listing are
considered for output. The ID listings are not only used to disclose component names but also
component numbers, e.g. CAS-no. Therefore the ID-listings need to contain all the names
assigned according to their priorities to position 1, all numbers assigned according to their
priorities to position 2. Exemption: if the CAS-no. should be discarded with a name if trade

INTERNAL: SAP CUSTOMER 228 © SAP SE

 How To ...

secret applies (e.g. “proprietary ingredient” this needs to be maintained as separate identifier,
(e.g. NAM TRADESEC2) and is entered on position 2 of the listing.

Technical limitations

• No component type available

As the component type in the composition tab controls the output of trade secret identifiers,
this trigger cannot be provided in value assignment types with specification listing (instead
of composition) only. In this case always the standard identifier will be disclosed.
• More than one identifier per type

If more than one relevant identifier is found by the WWI functions (e.g. NAM PROD DE
is maintained twice), it can occur that the first found identifier is disclosed in the column
for component names, while the second found identifier is disclosed in the column for com-
ponent numbers instead of e.g. the CAS-number. This can be avoided by consistent data
maintenance. It can be avoided technically, if all name identifiers in the ID listing are listed
for position 1 and all number identifiers are listed for position 2.

Required system settings

• Environment parameters for ID listing assignment
• REP_TS_COMPCAT1 -> Standard Component Type, e.g. ACT_AGENT
• REP_TS_IDLID1 -> Standard ID Listing for Standard Component Type assigned to
REP_TS_COMPCAT1, e.g. D_NTSIDLID
• REP_TS_COMPCAT2 ->Trade secret Component Type, e.g. TRADESEC
• REP_TS_IDLID2 -> Standard ID Listing for Trade secret Component Type assigned to
REP_TS_COMPCAT2, e.g. D_TSIDLID

Further component type/ID listing combinations can be maintained. For all component types
that are not maintained at an environment parameter the ID listing D_VALPOS is used as
default. If no entries are given in the environment parameters the ID listing D_VALPOS is
used for standard name output and trade secret name output as well.

• Further environment parameters influencing the identifier output

• REP_TS_IDENT_NOUSAGECHECK -> No usage check for Trade Secret. If this param-
eter has an value “x” the usage of an identifier is not considered for output (setting not
recommended)
• REP_TS_NOTRADESEC_IDLID -> If the component type is not specified within one
of the REP_TS_COMPCAT# parameters, the identification listing specified in environ-
ment parameter REP_TS_NOTRADESEC_IDLID is used. The environment parameters
REP_TS_NOTRADESEC_IDLID is not provided in the standard system.
• REP_TS_OUTPUT_PER_POS -> If you want to use the function module
C14N_SYM_TS_START to determine identifiers using "Trade Secret" listings in such a
way that they are output to the report on a position-by-position basis during report gener-
ation, you must create the following environment parameter in the "Specify Environment
Parameters" Customizing activity: REP_TS_OUTPUT_PER_POS Identifier Output Per
Position (TS) To enable determination to be made on a position-by-position basis, set the
parameter to "X". If this environment parameter is not available or is not set, the identifiers
are determined using the standard process for listings. That is, the identifiers are deter-
mined based on the sequence of the position and priority. In this case, the system takes
into account only identifiers that are not blank under consideration of the Customizing
settings for the defined listing. (SAP Note 2094891, 2172087)
INTERNAL: SAP CUSTOMER 229 © SAP SE
 How To ...

• REP_TS_SUPPORT -> Option to generate time-specific change marking (SAP Note

2164505)
• Identifier listings

All identifier listings assigned to component types as environment parameter need to be

created with all relevant names and numbers.

Example:

• Simple ID listing for standard identifier output D_NTSIDLID

IDListPos IDListPrio IDCategory IDType MaxNoID

1 1 NAM PROD 1
2 1 NUM CAS 1

For this setup the NAM PROD needs to be maintained with all translations (or if missing
translations should be allowed all available translations plus one language independent
entry for NAM PROD)
• Complex ID listing for standard identifier output D_NTSIDLID

IDListPos IDListPrio IDCategory IDType MaxNoID

1 1 NAM ANNEXI 1
1 2 NAM EINECS 1
1 3 NAM IUPAC 1
1 4 NAM SYN 1
1 5 NAM ENCS 1
1 6 NAM PROD 1
2 1 NUM CAS 1
2 2 NUM EINECS 1
2 3 NUM ELINCS 1

For this setup the NAM PROD (and only this one) should have a language independent
entry to make sure that always an output is found.
• ID listing for trade secret identifier output D_TSIDLID

IDListPos IDListPrio IDCategory IDType MaxNoID

1 1 NAM TRADESEC 1
2 1 NAM TRADESEC2 1

This setup support to discard the CAS-No. with a name identifier (e.g. Proprietary Ingre-
dient)
• Simple ID listing for trade secret identifier output D_TSIDLID

IDListPos IDListPrio IDCategory IDType MaxNoID

1 1 NAM TRADESEC 1

This setup results in disclosure of a trade secret name instead of a standard name. No
INTERNAL: SAP CUSTOMER 230 © SAP SE
numbers are printed, so the CAS-number can be discarded for trade secret components.
 How To ...

Special Trade Secret Functionality for US and Canada

For US and Canada, the regulatory requirement regarding trade secrets can be broken down
to the following cases:

1. Masking the component identity, while the component identity is being claimed as a trade
secret.
2. Masking the component concentration, while the component concentration is being claimed
as a trade secret.
3. Masking both the component identity and concentration.

Case 1 is handled by the standard trade secret functionality as described above.

Cases 2 and 3 are handled by additional component types.

Mock-up for Canada

Note: The US section 3 would be identical, with the exception of the HMIRA phrase, which
would be missing.

Masking component concentration (Case 2):

This is achieved by using the component type ZTRADECONC. When the relevant component
in the product Standard composition is maintained with this component type, the template
outputs “Trade Secret (HazardComp range)" instead of just the HazardComp range (see case
2 in mock-up above).

Note: This HazardComp range can be achieved by either of two means:

1. If "ignore Expert rule range" is not maintained, then the HazardComp ranges will be generic
ranges. This means that all ranges for all disclosed components will be generic ranges.
2. If "ignore Expert rule range" is maintained, then the HazardComp ranges will be copied
directly from the Standard composition. This is the case where at least some of the disclosed
components are not trade secrets, and thus have their true concentrations/ranges (from the
Standard composition) disclosed in section 3.

INTERNAL: SAP CUSTOMER 231 © SAP SE

 How To ...

Masking component identity and concentration (Case 3):

This is achieved by using the component type ZTRADESCON. When the relevant component
in the product Standard composition is maintained with this component type, the template
outputs NAM ZTRADESEC instead of NAM PROD for the chemical name. The CAS number
is replaced by NAM ZTRADESEC2. “Trade Secret (HazardComp range)” is output instead of
just the HazardComp range (see case 3 in mock-up above).

Note: The same considerations regarding the HazardComp range as above apply here.

Output of HMIRA phrase in section 3:

The HMIRA phrase is output in section 3 of the Canada SDS (see mock-up above) if one of
the based on the following logic: If the HazardComp contains a component with one of the
component types ZTRADESEC, ZTRADECONC or ZTRADESCON in a CA instance, then the
phrase is output.

Customizing for Component types ZTRADECONC or ZTRADESCON

All Component types ZTRADESEC, ZTRADECONC and ZTRADESCON must be specified

in the customizing in “Specify Component Types for Compositions” and “Specify Environment
Parameters”.

Example for setting Component Types ZTRADESEC, ZTRADECONC and ZTRADESCON

A complete list of all Environment parameters, including None-Trade-Secret ID Listings (see

section “Required system settings” above), would look like that:

Environment parameters Parameter Value

REP_TS_COMPCAT1 ACT_AGENT
REP_TS_COMPCAT2 ZTRADESEC
REP_TS_COMPCAT3 ZTRADESCON
REP_TS_COMPCAT4 ZTRADECONC*
REP_TS_IDLID1 D_NTSIDLID
REP_TS_IDLID2 D_TSIDLID
REP_TS_IDLID3 D_TSIDLID

INTERNAL: SAP CUSTOMER 232 © SAP SE

 How To ...

REP_TS_IDLID4 D_NTSIDLID*

*The component type ZTRADECONC for masking concentration (see Case 2 above) has the
D_NTSIDLID ID Listing as the masked Concentration is written by the HazComp rule.

The component types ZTRADECONC (Masking component concentration) and ZTRADE-

SCON (Masking component identity and concentration) trigger the output of the phrase “Trade
Secret” by the template in column “Concentration (% w/w)” (see mock-up above).

Special procedure to disclose the CAS No on Product level

for Substances which have only one component which is a
Trade Secret for Taiwan only
The Type of substance for the Product has to be "Substance".

The Component types of the components can be ZTRADESCON (masking component identity
and conc.) or TRADESEC (masking component identity only).

A specific Trade secret identifier (NAM / ZTRADESEC2) has to be maintained on product

level. The identifier NAM ZTRADESEC2 has to be maintained manually on component level
to overwrite the NUM CAS in section 3.

Therefore a new logic has been implemented on the SDS template:

1. Check if NAM ZTRADESEC2 is maintained. If available, print it.

2. Check if a NUM CAS is assigned. If available, print it, otherwise print “Not assigned”.

INTERNAL: SAP CUSTOMER 233 © SAP SE

Appendix B. Technical Settings
Property Tree Packages
In general, this Appendix contains all relevant information to implement the latest property tree
package delivered with the last SAP EHS Regulatory Content Update.

In order to make use of the latest ERC Phrase Library, ERC Substance Lists and Reference
Data, ERC Expert Rules, and ERC WWI Templates, the contents of the latest Property Tree
Package 1810 Product Safety and of the other existing property tree packages have to be
implemented before implementing the other parts of SAP ERC Update 1810. Please note that
changes to the EH&S property tree will be officially delivered with the SAP release ERP 6.0
EhP8 and lower EHPs with specific support packages. In addition, the EH&S property trees are
also available in SAP S/4 HANA on-premise 1511, SAP S/4 HANA on-premise 1610, and SAP
S/4 HANA on-premise 1709. More details about the delivery of property tree enhancements
can be found in SAP Note 1761696.

The property tree packages are delivered in two different folders:

• Folder "Update": In this folder the latest property tree package is included and corrections
to former property tree packages - if neccessary (see Chapter 1 below).

• Folder "Initial": New ERC customers with an ERC 3.0 licence may need to update their
EH&S property tree in order to make proper use of the other ERC products like phrases, rule
sets, regulatory data or WWI templates. Therefore, all necessary property tree packages are
summarized in this folder which are needed to update the EH&S standard property tree for
SAP systems with releases ranging from ERP 6.0 EhP3 up to ERP 6.0 EhP8 (see Chapter
2 below).

Please read the ReadMe document included in every property tree package carefully BEFORE
starting the implementation of any property tree package!

The existing property tree packages which were delivered in the past and are needed to bring
the EH&S property tree of a new ERC customer up-to-date are summarized in Chapter 2.

B.1. Contents of Latest SAP ERC Property Tree

Package
The contents of the delivery of property tree enhancements and corrections with ERC Update
1810 are described in the following sections. They are delivered on SAP Market Place in the
Folder "Update" where also the text document ReadMe_ERC_Property_Tree_Update.pdf with
more details about the update can be found.

B.1.1. File overview property tree package Product Safety

The following files are included in the delivery, that is in the zip-file EHS_Property_Tree_Pack-
age_1810_PS_V1-0.zip:

INTERNAL: SAP CUSTOMER 234 © SAP SE

 Technical Settings Property Tree Packages

General Information
File name Description
ReadMe_EHS_Property_Tree_Package_1810_ Summary of installation steps (text docu-
PS.pdf ment)
Changes_EHS_Property_Tree_Package_1810_ Summary of new and enhanced properties
PS.pdf and characteristics included in this package
(text document)
Help_Texts_EN_EHS_Property_Tree_Package_ Summary of help texts in English (text docu-
1810_PS.pdf ment)
Help_Texts_DE_EHS_Property_Tree_Package_ Summary of help texts in German (text docu-
1810_PS.pdf ment)

Transports
Please note that for each transport two files are delivered: Files with names starting with a "K"
are the co-files, files with names starting with a "R" are the data files.

Order of Transport File names Description

import name
1 EBJK448579 K448579.EBJ, New and enhanced characteristics, classes,
R448579.EBJ value assignment types, and assignments to
the property tree STANDARD with German
descriptions. New and enhanced German
help texts.
2 NE5K902963 K902963.NE5, English descriptions for new and enhanced
R902963.NE5 characteristics, classes, and value assign-
ment types. New and enhanced English help
texts.

B.1.2. File overview corrections to previous property tree

package
No corrections to the property tree package 1805 Version 1-0 are delivered.

B.2. Overview about existing property tree pack-

ages
The existing property tree packages are summarized in the following tables. In addition to
single packages, a combination package exists as well where several property tree packages
are combined into a single transport (see details below). They are delivered on SAP Market
Place in the Folder "Initial" where also the text document ReadMe_ERC_Property_Tree_Initial_
Set_Up.pdf with more details about the initial set up can be found.

Please note that the Folder "Initial" is available on the SAP Market Place for ERC 3.0
Customers only!

Example:

INTERNAL: SAP CUSTOMER 235 © SAP SE

 Technical Settings Property Tree Packages

• A customer with an ERP 6.0 EhP3 system should first check in SAP Note 1761696 whether
the Support Package implemented in the customer's SAP ERP 6.0 EhPx system includes
already the update up to 2015-1 (in delivery client 000), for example.
• If yes, the customer can take over the standard properties and property trees from the deliv-
ery client 000 to the working client XYZ (tools see SAP EH&S customizing) so that the prop-
erty tree in client XYZ is updated to 2015-1. After that, the property tree packages 2015-2
(number 18), 1605 (number 19), 1611 (number 20), 1705 (number 21), 1711 (number 22),
1805 (number 23), and 1810 (number 24) shall be implemented.
• If no, the customer shall implement the combination package Version 3-0 which updates
the property tree up to 2011-2. After that, the property tree packages 2012-1 (number 12) ,
2012-2 (number 13), 2013-2 (number 14), 2014-1 (number 15), 2014-2 (number 16), 2015-1
(number 17), 2015-2 (number 18), 1605 (number 19), 1611 (number 20), 1705 (number 21),
1711 (number 22), 1805 (number 23), and 1810 (number 24) shall be implemented.

Delivered Packages on SAP Market Place in Folder "Initial"

for ERC 3.0 Customers
Please note that in the current delivery on the SAP Market Place the following property tree
packages are present:

Order Property Tree Package Update from EHS Property Tree

Num- Release -> to EHS Property Tree
ber Release
Combi- SAP EH&S Combination Property Tree Pack- ERP 6.0 -> ERP 6.0 EhP7 (first part)
nation age Product Safety Version 3-1 (includes
Pack- property tree packages ERP 6.0 EnhP3 ,
age 2007-2, 2008-1, 2009-1, 2009-2, 2010-1,
V 3-1 2010-2, 2011-2 Product Safety)
12 SAP EH&S Property Tree Package 2012-1 ERP 6.0 EhP6 -> ERP 6.0 EhP7
Product Safety SP01 (second part)
13 SAP EH&S Property Tree Package 2012-2 ERP 6.0 EhP6 -> ERP 6.0 EhP7
Product Safety SP01 (third part)
14 SAP EH&S Property Tree Package 2013-2 ERP 6.0 EhP7 SP01 -> ERP 6.0
Product Safety (Please note that 2013-1 Prod- EhP7 2013-2
uct Safety does not exist.)
15 SAP EH&S Property Tree Package 2014-1 ERP 6.0 EhP7 2013-2 -> ERP 6.0
Product Safety 2014-1
16 SAP EH&S Property Tree Package 2014-2 ERP 6.0 2014-1 -> ERP 6.0 2014-2
Product Safety
17 SAP EH&S Property Tree Package 2015-1 ERP 6.0 2014-2 -> ERP 6.0 2015-1
Product Safety
18 SAP EH&S Property Tree Package 2015-2 ERP 6.0 2015-1 -> ERP 6.0 2015-2
Product Safety
19 SAP EH&S Property Tree Package 1605 ERP 6.0 2015-2 -> ERP 6.0 1605
Product Safety
20 SAP EH&S Property Tree Package 1611 ERP 6.0 1605 -> ERP 6.0 1611
Product Safety

INTERNAL: SAP CUSTOMER 236 © SAP SE

 Technical Settings Property Tree Packages

21 SAP EH&S Property Tree Package 1705 ERP 6.0 1611 -> ERP 6.0 1705
Product Safety
22 SAP EH&S Property Tree Package 1711 ERP 6.0 1705 -> ERP 6.0 1711
Product Safety
23 SAP EH&S Property Tree Package 1805 ERP 6.0 1711 -> ERP 6.0 1805
Product Safety
24 SAP EH&S Property Tree Package 1810 ERP 6.0 1805 -> ERP 6.0 1810
Product Safety

If a customer needs earlier property tree packages, please set up a ticket in the SAP Helpdesk
with component EHS-ERC.

Overview about existing Property Tree Packages

Order Property tree package Update from EHS Property Tree
number Release -> to EHS Property Tree
Release
4 SAP EH&S Property Tree Package ERP 6.0 ERP 6.0 (= ERP 2005) -> ERP 6.0
EnhP 3 Product Safety EhP3
5 SAP EH&S Property Tree Package 2007-2 ERP 6.0 EhP3 -> ERP 6.0 EhP5 (first
Product Safety part)
6 SAP EH&S Property Tree Package 2008-1 ERP 6.0 EhP5 (first part) -> ERP 6.0
Product Safety EhP5 (second part)
does SAP EH&S Property Tree Package 2008-2 No property tree enhancements
not Product Safety were delivered with SAP ERC
exist 2008-2.
7 SAP EH&S Property Tree Package 2009-1 ERP 6.0 EhP5 (second part) -> ERP
Product Safety 6.0 EhP5 (third part)
8 SAP EH&S Property Tree Package 2009-2 ERP 6.0 EhP5 (third part) -> ERP 6.0
Product Safety EhP5 (fourth part)
9 SAP EH&S Property Tree Package 2010-1 ERP 6.0 EhP5 (fourth part) -> ERP
Product Safety 6.0 EhP6 (first part)
10 SAP EH&S Property Tree Package 2010-2 ERP 6.0 EhP6 (first part) -> ERP 6.0
Product Safety EhP6 (second part)
does SAP EH&S Property Tree Package 2011-1 No property tree enhancements
not Product Safety were delivered with SAP ERC
exist 2011-1.
11 SAP EH&S Property Tree Package 2011-2 ERP 6.0 EhP6 (second part) -> ERP
Product Safety 6.0 EhP7 (first part)
12 SAP EH&S Property Tree Package 2012-1 ERP 6.0 EhP7 (first part) -> ERP 6.0
Product Safety EhP7 (second part)
13 SAP EH&S Property Tree Package 2012-2 ERP 6.0 EhP7 (second part) -> ERP
Product Safety 6.0 EhP7 (third part)
does SAP EH&S Property Tree Package 2013-1 No property tree enhancements
not Product Safety were delivered with SAP ERC
exist 2013-1.

INTERNAL: SAP CUSTOMER 237 © SAP SE

 Technical Settings Property Tree Packages

14 SAP EH&S Property Tree Package 2013-2 ERP 6.0 EhP7 (third part) -> ERP 6.0
Product Safety EhP7 2013-2
15 SAP EH&S Property Tree Package 2014-1 ERP 6.0 EhP7 2013-2 -> ERP 6.0
Product Safety 2014-1
16 SAP EH&S Property Tree Package 2014-2 ERP 6.0 2014-1 -> ERP 6.0 2014-2
Product Safety
17 SAP EH&S Property Tree Package 2015-1 ERP 6.0 2014-2 -> ERP 6.0 2015-1
Product Safety
18 SAP EH&S Property Tree Package 2015-2 ERP 6.0 2015-1 -> ERP 6.0 2015-2
Product Safety
19 SAP EH&S Property Tree Package 1605 ERP 6.0 2015-2 -> ERP 6.0 1605
Product Safety
20 SAP EH&S Property Tree Package 1611 ERP 6.0 1605 -> ERP 6.0 1611
Product Safety
21 SAP EH&S Property Tree Package 1705 ERP 6.0 1611-> ERP 6.0 1705
Product Safety
22 SAP EH&S Property Tree Package 1711 ERP 6.0 1705 -> ERP 6.0 1711
Product Safety
23 SAP EH&S Property Tree Package 1805 ERP 6.0 1711 -> ERP 6.0 1805
Product Safety
24 SAP EH&S Property Tree Package 1810 ERP 6.0 1805 -> ERP 6.0 1810
Product Safety

INTERNAL: SAP CUSTOMER 238 © SAP SE

Appendix C. Technical Settings
Multilanguage Phrase Library
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. We recommend to use the Unicode files when
possible to avoid character conversion errors with the non-Unicode files. Non-Unicode files
will no longer be included. If you cannot use the Unicode files provided, please contact our
helpdesk.

Standard
File name Description
01_documents
CED_Changes_1810.xlsx Excel file with an overview of new, changed and retired
phrases
CED_ReleaseNote_1810.pdf Release Note for current version
Phrase_Services_Proposals.xls Proposal template for customer suggestions
02_phrases
1_ced_1810_standard_complete.dat Phrase import file including all phrases in all standard
languages except US English (Z8) and Brazilian Por-
tuguese (Z9) for Unicode systems
1_ced_1810_standard_update.dat Phrase import file including revised and new phrases in
all standard languages
2_ced_1810_usenglish_Z8_ Phrase import file including all phrases in US English
complete.dat via Z8 customer correspondence language
2_ced_1810_usenglish_Z8_ Phrase import file including revised and new phrases in
update.dat US English (Z8)
3_ced_1810_brazilian_Z9_ Phrase import file including all phrases in Brazilian Por-
complete.dat tuguese via Z9 customer correspondence language
3_ced_1810_brazilian_Z9_ Phrase import file including revised and new phrases in
update.dat Brazilian Portuguese (Z9)
4_ced_1810_arabic_hebrew_ Phrase import file including all phrases Unicode Phrase
complete.dat import file Arabic and Hebrew
4_ced_1810_arabic_hebrew_ Phrase import file including revised and new phrases in
update.dat Arabic and Hebrew
03_psets

INTERNAL: SAP CUSTOMER 239 © SAP SE

 Technical Settings Multilanguage Phrase Library

ced_1810_pset_complete.dat Complete phrase set assignments based on the latest

property tree; this file includes all assignments from pre-
vious releases and the new release
ced_1810_pset_new.dat New phrase set assignments based on the latest prop-
erty tree

C.2. General Settings

C.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.

Phrase group Description

00.00 REF.
01.00 IDENTIFICATION OF THE SUBSTANCE OR
PREPARATION
02.00 COMPOSITION / INFORMATION ON INGRE-
DIENTS
03.00 HAZARDS IDENTIFICATION
04.00 FIRST-AID MEASURES
05.00 FIRE-FIGHTING MEASURES
06.00 ACCIDENTAL RELEASE MEASURES
07.00 HANDLING AND STORAGE
08.00 EXPOSURE CONTROLS /PERSONAL PRO-
TECTION
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 SDS Annex Phrases
ASIA_PAC SDS Phrases Asia Pacific
ESCOM ESCom XML Phrases
TD_RUL Control Phrases for SAP EHS Expert rule sets

INTERNAL: SAP CUSTOMER 240 © SAP SE

 Technical Settings Multilanguage Phrase Library

US_ANSI SDS Phrases North America

C.2.2. Name spaces

C.2.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.2.2.1.1. Name spaces concerning substance evaluation phrases (-> allocated to

phrase sets)

N* CED-Phrases for substance evaluation

Z* CED phrases for substance evaluation

ZESX* ESCom XML Phrases

U* SDS phrases North America

* Structure for the phrase key

Phrase Group Sub Group Meaning

01.00 Identification
1xxxx Product name related
2xxxx Company name related
3xxxx Emergency contact related
4xxxx Descriptor categories (SU, ERC, PC) for exposure sce-
5xxxx narios

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

INTERNAL: SAP CUSTOMER 241 © SAP SE

 Technical Settings Multilanguage Phrase Library

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
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

INTERNAL: SAP CUSTOMER 242 © SAP SE

 Technical Settings Multilanguage Phrase Library

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
0xxxx Further information
13.00 Disposal considerations
1xxxx Waste from residues / unused products
2xxxx Contaminated packaging
0xxxx Further information
14.00 Transport information
1xxxx Proper Shipping names English only (unnecessary
2xxxx 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

INTERNAL: SAP CUSTOMER 243 © SAP SE

 Technical Settings Multilanguage Phrase Library

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
ESCOM ZESXxxxxxxxxxxxESCom XML Phrases (ZESX prefix + official ESCom
XML phrase key)

C.2.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.2.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.2.3. Language/Codepages
Language Language ISO-Norm SAP R/3 Mi- Mi- Font (Mi-
group character Stan- crosoft-Code-crosoft-Code-crosoft) in
set dard-Code- page page in which phras-
page (based SAP R/3 es are sup-
on ISO- plied by CED
Norm)
Western English ISO 8859-1 1100 1252 (iden- 110 ARIAL.TTF
European tical with
Danish R/3 Code-
page 1100)
Dutch

Finnish

French

German

INTERNAL: SAP CUSTOMER 244 © SAP SE

 Technical Settings Multilanguage Phrase Library

Italian

Norwegian

Portuguese

Spanish

Swedish

Brazilian

US English
Greek Greek ISO 8859-7 1700 1253 1704 ARIAL
GREEK.TTF
Central Eu- Albanian ISO 8859-2 1401 1250 1404 ARIAL
ropean CE.TTF
Croatian

Czech

Hungarian

Polish

Romanian

Slovakian

Slovenian

Serbian
Cyrillic Russian ISO 8859-5 1500 1251 1504 ARIAL
CYR.TTF
Bulgarian

Macedo-
nian

Ukrainian
Turkish Turkish ISO 8859-9 1610 1254 1614 ARIAL
TUR.TTF
Baltic Estonian ISO 8859-4 1900 1257 1904 ARIAL
BALTIC.TTF
Latvian

Lithuanian
Nordic Icelandic ISO ARIAL MS
8859-10 Unicode
AP-Latin English ISO 8859-1 110 1252 1100 ARIAL.TTF

Indonesian

INTERNAL: SAP CUSTOMER 245 © SAP SE

 Technical Settings Multilanguage Phrase Library

Malay
AP-TChin Traditional 8300 950 (BIG 5) 8300 mingliu.ttc
Chinese -
not all char-
acters sup-
ported!
AP-SChin Simplified 8400 936 (GB 8400 Simsun.ttc
Chinese 2312)
AP- Japanese 8000 932 8000 msmincho.ttc
Japanese
AP-Korean Korean 8500 949 8500 batang.ttc
AP-Thai Thai 8600 874 8600 tahoma.ttc
Unicode Canadian 4103 ARIAL MS
French Unicode

French

Mexican
Spanish

Hindi (AP)

Vietnamese
(AP)

Traditional
Chinese
(AP)

C.2.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 E EN
English_GB 6N*

Danish K DA
Dutch N NL
Finnish U FI
French F FR
German D DE
Greek G EL
Italian I IT
Norwegian O NO
Portuguese P PT

INTERNAL: SAP CUSTOMER 246 © SAP SE

 Technical Settings Multilanguage Phrase Library

Portuguese_PT 1P*

Spanish S ES
Swedish V SV
1

Language keys of other phrase translations

Phrase language Language keys for phrase im- Language key presentation in
port phrase administration
Albanian SQ

Bulgarian W BG
Croatian 6 HR
Czech C CS
Estonian 9 ET
Hungarian H HU
Icelandic b IS
Latvian Y LV
Lithuanian X LT
Macedonian MK

Polish L PL
Romanian 4 RO
Russian R RU
Slovakian Q SK
Slovenian 5 SL
Turkish T TR
Ukrainian 8 UK
Brazilian Portuguese & Z9
Canadian French 3F

US English ; Z8
Mexican Spanish - Also used 1X
for all other Spanish speaking
countries in Latin America
Serbian d SH

Language keys of Asia Pacific translations

Phrase language Language keys for phrase im- Language key presentation in
port phrase administration

1
* for SAP S/4HANA systems

INTERNAL: SAP CUSTOMER 247 © SAP SE

 Technical Settings Multilanguage Phrase Library

Indonesian i ID
Malay 7 MS
Simplified Chinese 1 ZH
Traditional Chinese M ZF
Japanese J JA
Korean 3 KO
Thai 2 TH
Hindi HI

Vietnamese VI

Language keys of Right-To-Left languages

Phrase language Language keys for phrase im- Language key presentation in
port phrase administration
Arabic A AR
Hebrew B HE

INTERNAL: SAP CUSTOMER 248 © SAP SE

Appendix D. Technical Settings
Substance Lists and Reference Data
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:

ProductSafety
File name Description
0-Documentation
ERC_1901_changed_phrases.xlsx Overview of new and revised phrases
Availability of the content reports depends on the li-
censed ERC package:
ERC_ContentReport_ Content Report Inventories Data
Inventories.pdf
ERC_ContentReport_Americas.pdf Content Report American Data
ERC_ContentReport_APJ.pdf Content Report Asia-Pacific Data
ERC_ContentReport_EMEA.pdf Content Report Europe, Middle-East & Africa Data
ERC_ContentReport_SDS- Content Report SDS Authoring Package
Authoring.pdf
ERC_ContentReport_ Content Report Marketability Package
Marketability.pdf
ERC_PS_Data_ReleaseNote_1901.pdf Latest Substance Lists and Reference Data Release
Note for Product Safety
ERC_PS_Training_EN.pdf SAP EHS Regulatory Content Training Workshop Pre-
sentation
ERC_ListOverview_1901.xlsx Overview of lists by region and country and assignment
to properties
TLV_Stmt_of_Position.pdf ACGIH® Statement of Position Regarding the TLVs®
and BEIs®
JSOH_Characteristics_of_OELs_ Japan Society of Occupational Health - Additional infor-
and_Instructions_for_Users.pdf mation regarding OEL values
1-OCC
readme.txt Info file on how to obtain OCC

INTERNAL: SAP CUSTOMER 249 © SAP SE

 Technical Settings Substance Lists and Reference Data

2-Customizing\Initial
K900546.NE5 Substance Lists and Reference Data - Product Safe-
ty - Basic Customizing transport (User Exit, Data Ori-
gin, Free Text Types, passive Phrase Library, identifier
types) (Unicode)
K902701.NE5 Substance Lists and Reference Data - Product Safety -
Consolidated customizing transport Validity Areas (Uni-
code)
K902917.NE5 Substance Lists and Reference Data - Product Safety
- Consolidated customizing transport (Regulatory Lists
and Literature Sources) (Unicode)
R900546.NE5 Substance Lists and Reference Data - Product Safe-
ty - Basic Customizing transport (User Exit, Data Ori-
gin, Free Text Types, passive Phrase Library, identifier
types) (Unicode)
R902701.NE5 Substance Lists and Reference Data - Product Safety -
Consolidated customizing transport Validity Areas (Uni-
code)
R902917.NE5 Substance Lists and Reference Data - Product Safety
- Consolidated customizing transport (Regulatory Lists
and Literature Sources) (Unicode)
3-Phrases
1_erc_1901_unicode.DAT Unicode phrase import file (all languages)
2_erc_1901_usenglish_unicode.DAT Unicode Phrase import file US English (only import if
you use Z8 for US English)
3_erc_1901_brazilian_unicode.DAT Unicode Phrase import file Brazilian Portuguese (only
import if you use Z9 for Brazilian Portuguese)
4_erc_1901_pset_unicode.DAT Unicode phrase set assignment import file
4-Database
ERC_PS_<Region>_1901.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
erc_new_group_assignments_ Update file to create hit list substances with new group
1901.txt assignments
ERC_simulation.xlt Template for simulation (MS Excel 97- 2003)
ERC_simulation.xltm Template for simulation (MS Excel 2007)
erc_update_1901.txt Update file to create hit list of changed list substances

D.1.2. User Exit Settings

The following settings are proposed for the user exit:

Environment parameter Standard Value

INTERNAL: SAP CUSTOMER 250 © SAP SE

 Technical Settings Substance Lists and Reference Data

EXPERT_ADD_PARAM_1 headerurl=<path to ERC PS DB>\PS_DB

\header.xml
EXPERT_ADD_PARAM_2 usernameurl=x
EXPERT_ADD_PARAM_3 passwordurl=x
EXPERT_CALL_ONCE X
EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE I
EXPERT_DESTINATION EHS_OCC
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE H
EXPERT_READ_RATING
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG
EXPERT_RULE_SET ERC_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_TAB_FIELD_5 <identifier>[NUM,PMN]
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID TECHNIDATA
EXPERT_WRITE_VALIDITY_AREA 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)
User defined text type NOL (name on list)

D.2. Settings to implement the Substance Lists

and Reference Data for Dangerous Goods (SAP
EHS)
D.2.1. File Overview

INTERNAL: SAP CUSTOMER 251 © SAP SE

 Technical Settings Substance Lists and Reference Data

The Substance Lists and Reference Data installation package for Dangerous Goods includes
the following files:

Files File Description

0-Documentation
ERC_DG_Data_ReleaseNote_1901.pdf Latest Substance Lists and Reference Data Release
Note for Dangerous Goods
ERC_DG_Regulations_Status_ SAP EHS Regulatory Content status of regulatory lists
1901.pdf overview
ERC_DG_Data_Training.pdf SAP EHS Regulatory Content Training Workshop
Slides
ERC_DG_Changes_1901.mdb Database with list of all changes compared to previous
release.
1-Customizing - Initial
R900833.NE5 and K900833.NE5 Basic Customizing transport (UserExit, RegList,
Source, Identifiers)
R902593.NE5 and K902593.NE5 Master Data customizing transport for regulation ADG
R903061.NE5 and K903061.NE5 Master Data customizing transport for regulation ADN
with pack data
R902603.NE5 and K902603.NE5 Master Data customizing transport for regulation ADN
without pack data
R903063.NE5 and K903063.NE5 Master Data customizing transport for regulation ADR
with pack data
R902607.NE5 and K902607.NE5 Master Data customizing transport for regulation ADR
without pack data
R902285.NE5 and K902285.NE5 Master Data customizing transport for regulation ANTT
R902064.NE5 and K902064.NE5 Master Data customizing transport for regulation Asia
Road
R902233.NE5 and K902233.NE5 Master Data customizing transport for regulation
Chile_DG
R902755.NE5 and K902755.NE5 Master Data customizing transport for regulation
CFR49 without split by mode of transport of NA regula-
tions, including pack data
R902630.NE5 and K902630.NE5 Master Data customizing transport for regulation
CFR49 without split by mode of transport of NA regula-
tions, without pack data
R902757.NE5 and K902757.NE5 Master Data customizing transport for regulation
CFR49 with split by mode of transport of NA regulations,
including pack data
R902636.NE5 and K902636.NE5 Master Data customizing transport for regulation
CFR49 with split by mode of transport of NA regulations,
without pack data
R902753.NE5 and K902753.NE5 Master Data customizing transport for regulation IATA
with pack data

INTERNAL: SAP CUSTOMER 252 © SAP SE

 Technical Settings Substance Lists and Reference Data

Files File Description

R902196.NE5 and K902196.NE5 Master Data customizing transport for regulation IATA
without pack data
R902751.NE5 and K902751.NE5 Master Data customizing transport for regulation IMDG
with pack data
R902525.NE5 and K902525.NE5 Master Data customizing transport for regulation IMDG
without pack data
R903065.NE5 and K903065.NE5 Master Data customizing transport for regulation RID
with pack data
R902611.NE5 and K902611.NE5 Master Data customizing transport for regulation RID
without pack data
R902850.NE5 and K902850.NE5 Master Data customizing transport for regulation TDG
Canada without split by mode of transport of NA regu-
lations
R902852.NE5 and K902852.NE5 Master Data customizing transport for regulation TDG
Canada with split by mode of transport of NA regulations
R902595.NE5 and K902595.NE5 Master Data customizing transport for DG regulation
China
R901786.NE5 and K901786.NE5 Master Data customizing transport for DG regulation
Mexico
R902519.NE5 and K902519.NE5 Master Data customizing transport for DG regulation
MERCOSUR
R902068.NE5 and K902068.NE5 Master Data customizing transport for DG regulation
Korea
R902507.NE5 and K902507.NE5 Master Data customizing transport for UN model regu-
lations
R902597.NE5 and K902597.NE5 Master Data customizing transport for DG regulation
New Zealand
R901802.NE5 and K901802.NE5 Master Data customizing transport for DG regulation
South Africa
2-Phrases
erc_dg_1901.dat Import file phrases
erc_dg_pset_1901.dat Import file phrase set assignments
3-Database
ERC_DG_1901.exe 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 reg-
ulations and without additional pack data, for use in sys-
tems older than ERP 6.0.

INTERNAL: SAP CUSTOMER 253 © SAP SE

 Technical Settings Substance Lists and Reference Data

Files File Description

TD_CLEO_DG_with_split.mdb Mapping database with split of North American regula-
tions 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_ Mapping database with split of North American regula-
pack.mdb tions into separate instances for different carrier types
and without additional pack data, for use in systems old-
er 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.

SAP Note 1796257 - Enhancement of danger label usage should be implemented.

You might use the correct mapping database and rename this one in TD_CLEO_DG.mdb.

D.2.2. User Exit Settings

The following settings are proposed for the user exit:

Environment parameter Standard Value

EXPERT_ADD_PARAM_1 headerurl=<path to ERC DG DB>\DG_DB
\head.xml
EXPERT_ADD_PARAM_2 usernameurl=x
EXPERT_ADD_PARAM_3 passwordurl=x
EXPERT_CALL_ONCE X
EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE I
EXPERT_DESTINATION EHS_OCC
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE H
EXPERT_READ_RATING
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG
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

INTERNAL: SAP CUSTOMER 254 © SAP SE

 Technical Settings Substance Lists and Reference Data

Environment parameter Standard Value

EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID TECHNIDATA
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

D.2.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)
User defined text type NOL (name on list)

D.3. Settings to implement the Substance Lists

and Reference Data for Dangerous Goods (SAP
Transportation Management)
Note
This chapter describes the Dangerous Goods solution for SAP Transportation Man-
agement. Users of SAP EHS Dangerous Goods can skip this chapter.

D.3.1. File Overview

The Substance Lists and Reference Data installation package for Dangerous Goods includes
the following files:

Files File Description

1-Customizing - Initial
R903069.NE5 and K903069.NE5 Customizing transport with all entries used in DG data
2-Database
TM_DG_1901.zip Archive with data files to be used by loading tool

INTERNAL: SAP CUSTOMER 255 © SAP SE

Appendix E. Technical Settings
Expert Rules
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_1810.ruc Rule File
comp_1810.mdb Mapping Database
ReleaseNote_Basis_1810.pdf Release Note
Comp_1810.pdf Functional Description

GWPO

File name Description

GWP_1810.ruc Rule File
GWP_1810.mdb Mapping Database
GWP_externvalues.mdb External Database
GWP__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_Basis_1810.pdf Release Note
GWP_1810.pdf Functional Description

HDCOMP

File name Description

HazardDecomp_1810.ruc Rule File
HazardDecomp_1810.mdb Mapping Database
HazardDecomp_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC

INTERNAL: SAP CUSTOMER 256 © SAP SE

 Technical Settings Expert Rules

HazardDecomp__HISTORY.mdb database for the documentation of the

changes in the mapping database and the ex-
ternal database
ReleaseNote_Basis_1810.pdf Release Note
HazardDecomp_1810.pdf Functional Description

HHAZ

File name Description

HealthHaz_1810.ruc Rule File
HealthHaz_1810.mdb Mapping Database
HealthHaz_externvalues.mdb External Database
HealthHaz__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_Basis_1810.pdf Release Note
HealthHaz_1810.pdf Functional Description

RespiratoryProtection

File name Description

RespiratoryProtection_1810.ruc Rule File
RespiratoryProtection_1810.mdb Mapping Database
RespiratoryProtection_externvalues.mdb External Database
RespiratoryProtection__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_Basis_1810.pdf Release Note
RespiratoryProtection_1810.pdf Functional Description

E.1.2. Settings in Admin Tool

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM

The settings for the rule sets and sub rule sets are:

Comp

Environment parameter Value of the parameter

Name ZEXP_COMP
Mapping Database comp_1810.mdb
Rule File comp_1810.ruc
Additional Settings
Name IgnoreWarnings

INTERNAL: SAP CUSTOMER 257 © SAP SE

 Technical Settings Expert Rules

Value 355

GWPO

Environment parameter Value of the parameter

Name ZEXP_GWPO
Mapping Database GWP_1810.mdb
Rule File GWP_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

HDCOMP

Environment parameter Value of the parameter

Name ZEXP_HDCMP
Mapping Database HazardDecomp_1810.mdb
Rule File HazardDecomp_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

HHAZ

Environment parameter Value of the parameter

Name ZEXP_HHAZ
Mapping Database HealthHaz_1810.mdb
Rule File HealthHaz_1810.ruc

RespirationProtection

Environment parameter Value of the parameter

Name ZEXP_RESPR
Mapping Database RespiratoryProtection_1810.mdb
Rule File RespiratoryProtection_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

E.1.3. Settings in Admin Tool - Sub Rules

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM

INTERNAL: SAP CUSTOMER 258 © SAP SE

 Technical Settings Expert Rules

The settings for the sub rule sets are:

GS_BASE_1_1

Environment parameter Value of the parameter

Name GS_BASE_1_1
Rule File GS_base_V1-11.ruc

E.1.4. User Exit Settings

The following settings are proposed for the user exit:

comp

User exit name ZEXP_COMP

User exit description EHS-Expert: composition

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_WORLD
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_COMP
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_COMP
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

GWPO

User exit name ZEXP_GWPO

User exit description EHS-Expert: Global Warming Potential

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1

INTERNAL: SAP CUSTOMER 259 © SAP SE

 Technical Settings Expert Rules

EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_GWPO
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_GWPO
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

HDCOMP

User exit name ZEXP_HDCMP

User exit description EHS-Expert: Hazard Decomposition

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_WORLD
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_HDCMP
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_HDCMP
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

HHAZ

User exit name ZEXP_HHAZ

User exit description EHS-Expert: Health Hazard

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1

INTERNAL: SAP CUSTOMER 260 © SAP SE

 Technical Settings Expert Rules

EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_HHAZ
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_HHAZ
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

RespirationProtection

User exit name ZEXP_RESPR

User exit description EHS-Expert: Respiration Protection

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_WORLD
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RESPR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RESPR
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

E.1.5. Other Settings

The following customizing settings are necessary:

Source

Value of the parameter affected rule sets

EHS-Expert all

Data Origin

Value of the parameter affected rule sets

INTERNAL: SAP CUSTOMER 261 © SAP SE

 Technical Settings Expert Rules

ZEXP_COMP Composition
ZEXP_GWPO Global Warming Potential
ZEXP_HDCMP Hazardous Decomposition Products
ZEXP_HHAZ Health Hazard
ZEXP_RESPR Respiratory Protection

E.2. Settings to implement the rule set package

for GHS
E.2.1. File Overview
The following files are included in the delivery:

GHS

File name Description

GHS_1810.ruc Rule File
GHS_1810.mdb Mapping Database
GHS_externvalues.mdb External Database
GHS__global_externvalues.mdb External Database used by all GHS rule sets
GS_ident_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_ident_V1-0.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_sub_pb2017_V1-0.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_label_V2-02.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_pure_V1-42.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_expl_V2-4.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
GHS__global_externvalues__HISTORY.mdb database for the documentation of the
changes in the global external database (used
by all GHS rule sets)
ReleaseNote_GHS_1810.pdf Release Note

INTERNAL: SAP CUSTOMER 262 © SAP SE

 Technical Settings Expert Rules

GHS_1810.pdf Functional Description

Hazcomp GHS

File name Description

Hazcomp_GHS_1810.ruc Rule File
Hazcomp_GHS_1810.mdb Mapping Database
Hazcomp_GHS_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
Hazcomp_GHS__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_GHS_1810.pdf Release Note
HazardComp_GHS_1810.pdf Functional Description

E.2.2. Settings in Admin Tool

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM

The settings for the rule sets are:

GHS

Environment parameter Value of the parameter

Name ZEXP_GHS
Mapping Database GHS_1810.mdb
Rule File GHS_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

Hazcomp GHS

Environment parameter Value of the parameter

Name ZEXP_HCGHS
Mapping Database Hazcomp_GHS_1810.mdb
Rule File Hazcomp_GHS_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

INTERNAL: SAP CUSTOMER 263 © SAP SE

 Technical Settings Expert Rules

E.2.3. Settings in Admin Tool - Sub Rules

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM

The settings for the sub rule sets are:

GS_BASE_1_1

Environment parameter Value of the parameter

Name GS_BASE_1_1
Rule File GS_base_V1-11.ruc

GS_PHYSCHEM_1_2

Environment parameter Value of the parameter

Name GS_PHYSCHEM_1_2
Rule File GS_physchem_V1-22.ruc

GS_IDENT

Environment parameter Value of the parameter

Name GS_IDENT
Rule File GS_ident_V1-0.ruc

GHS_SUB_PB2009_2_7

Environment parameter Value of the parameter

Name GHS_SUB_PB2009_2_7
Rule File GHS_sub_pb2009_V2-7.ruc

GHS_SUB_PB2011_2_1

Environment parameter Value of the parameter

Name GHS_SUB_PB2011_2_1
Rule File GHS_sub_pb2011_V2-1.ruc

GHS_SUB_PB2013_1_8

Environment parameter Value of the parameter

Name GHS_SUB_PB2013_1_8
Rule File GHS_sub_pb2013_V1-8.ruc

GHS_SUB_PB2017_1_0

Environment parameter Value of the parameter

INTERNAL: SAP CUSTOMER 264 © SAP SE

 Technical Settings Expert Rules

Name GHS_SUB_PB2017_1_0
Rule File GHS_sub_pb2017_V1-0.ruc

GHS_EXPL_2_4

Environment parameter Value of the parameter

Name GHS_EXPL_2_4
Rule File GHS_expl_V2-4.ruc

GHS_LABEL_2_0

Environment parameter Value of the parameter

Name GHS_LABEL_2_0
Rule File GHS_label_V2-02.ruc

GHS_PURE_1_4

Environment parameter Value of the parameter

Name GHS_PURE_1_4
Rule File GHS_pure_V1-42.ruc

E.2.4. User Exit Settings

The following settings are proposed for the user exit:

GHS

User exit name ZEXP_GHS

User exit description EHS-Expert: GHS

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_GHSUN

INTERNAL: SAP CUSTOMER 265 © SAP SE

 Technical Settings Expert Rules

EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_GHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_GHS
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

Hazcomp GHS

User exit name ZEXP_HCGHS

User exit description EHS-Expert: Hazardous Ingredients GHS

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_HCGHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_HCGHS
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

E.2.5. Other Settings

The following customizing settings are necessary:

Source

Value of the parameter affected rule sets

EHS-Expert all

Data Origin

Value of the parameter affected rule sets

ZEXP_GHS GHS
ZEXP_HCGHS Hazardous ingredients GHS

INTERNAL: SAP CUSTOMER 266 © SAP SE

 Technical Settings Expert Rules

User Defined Text Type

Value of the parameter affected rule sets

EX all rule sets with an explanation component

Validity Area

Value of the parameter affected rule sets

REG_GHSUN GHS: this region REG_GHSUN should con-
tain 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.
AG HC_GHS - Antigua and Barbuda
BB HC_GHS - Barbados
BM HC_GHS - Bermuda
BO HC_GHS - Bolivia, Plurinational State of
CL HC_GHS - Chile
CO HC_GHS - Colombia
DM HC_GHS - Dominica
DO HC_GHS - Dominican Republic
EC HC_GHS - Ecuador
SV HC_GHS - El Salvador
GT HC_GHS - Guatemala
HN HC_GHS - Honduras
JM HC_GHS - Jamaica
NI HC_GHS - Nicaragua
PA HC_GHS - Panama
PY HC_GHS - Paraquay
PE HC_GHS - Peru
TT HC_GHS - Trinidad and Tobago
TC HC_GHS - Turks and Caicos Islands
VE HC_GHS - Venezuela, Bolivarian Republic of
BH HC_GHS - Bahrain
BD HC_GHS - Bangladesh
BN HC_GHS - Brunei Darussalam
IN HC_GHS - India
KW HC_GHS - Kuweit
NP HC_GHS - Nepal
OM HC_GHS - Oman

INTERNAL: SAP CUSTOMER 267 © SAP SE

 Technical Settings Expert Rules

PK HC_GHS - Pakistan
QA HC_GHS - Qatar
SA HC_GHS - Saudi Arabia
LK HC_GHS - Sri Lanka
AE HC_GHS - United Arab Emirates
UY HC_GHS - Uruguay
HK HC_GHS - Hong Kong
MO HC_GHS - Macao

Regulatory List

Value of the parameter affected rule sets

GHS GHS

E.3. Settings to implement the rule set package

Europe
E.3.1. File Overview
The following files are included in the delivery:

Dapec

File name Description

DAPEC_1810.ruc Rule File
DAPEC_1810.mdb Mapping Database
DAPEC_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-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_ident_V1-0.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
comp_LEC50_V1-01.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
DAPEC__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
DAPEC_1810.pdf Functional Description

INTERNAL: SAP CUSTOMER 268 © SAP SE

 Technical Settings Expert Rules

GHS EU
File name Description
GHS_EU_1810.ruc Rule File
GHS_EU_1810.mdb Mapping Database
GHS_EU_externvalues.mdb External Database
GHS__global_externvalues.mdb External Database used by all GHS rule sets
GS_ident_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GHS_sub_pb2013_V1-8.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_label_V2-02.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_pure_V1-42.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_expl_V2-4.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_EU__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
GHS__global_externvalues__HISTORY.mdb database for the documentation of the
changes in the global external database (used
by all GHS rule sets)
ReleaseNote_EMEA_1810.pdf Release Note
GHS_EU_1810.pdf Functional Description

GHS RU
File name Description
GHS_RU_1810.ruc Rule File
GHS_RU_1810.mdb Mapping Database
GHS_RU_externvalues.mdb External Database
GHS__global_externvalues.mdb External Database used by all GHS rule sets
GS_ident_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GHS_sub_pb2011_V2-1.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_label_V2-02.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC

INTERNAL: SAP CUSTOMER 269 © SAP SE

 Technical Settings Expert Rules

GHS_pure_V1-42.ruc sub rule set which must be installed once as a

separate instance on the Expert-Server-PC
GHS_expl_V2-4.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_RU__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
GHS__global_externvalues__HISTORY.mdb database for the documentation of the
changes in the global external database (used
by all GHS rule sets)
ReleaseNote_EMEA_1810.pdf Release Note
GHS_RU_1810.pdf Functional Description

GHS TR

File name Description

GHS_TR_1810.ruc Rule File
GHS_TR_1810.mdb Mapping Database
GHS_TR_externvalues.mdb External Database
GHS__global_externvalues.mdb External Database used by all GHS rule sets
GS_ident_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GHS_sub_pb2009_V2-7.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_label_V2-02.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_pure_V1-42.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_expl_V2-4.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_TR__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
GHS__global_externvalues__HISTORY.mdb database for the documentation of the
changes in the global external database (used
by all GHS rule sets)

INTERNAL: SAP CUSTOMER 270 © SAP SE

 Technical Settings Expert Rules

ReleaseNote_EMEA_1810.pdf Release Note

GHS_TR_1810.pdf Functional Description

EU to GHS

File name Description

EU_TO_GHS_1810.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_1810.mdb Mapping Database with refer-
ence to the external database
EU_to_GHS_EU_Annex_VII_externvalues.mdb
(Annex VII of the consolidated GHS EU pro-
posal)
GS_physchem_V1-22.ruc sub rule set which has to be installed once as
a separate instance on the Expert-Server-PC
GHS_label_V2-02.ruc sub rule set which has to be installed once as
a separate instance on the Expert-Server-PC
EU_TO_GHS__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
EU_to_GHS_1810.pdf Functional Description

HazardComp EU

File name Description

HazardComp_EU_1810.ruc Rule File
HazardComp_EU_1810.mdb Mapping Database
HazardComp_EU_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
HazardComp_EU__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
HazardComp_EU_1810.pdf Functional Description

KKDIK Annex XVII Warnings

File name Description

KKDIK_Annex_XVII_Warnings_1810.ruc Rule File
KKDIK_Annex_XVII_Warnings_1810.mdb Mapping Database

INTERNAL: SAP CUSTOMER 271 © SAP SE

 Technical Settings Expert Rules

GS_base_V1-11.ruc sub rule set which must be installed once as a

separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
KKDIK_Annex_XVII_Warnings__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
KKDIK_Annex_XVII_Warnings_1810.pdf Functional Description

KKDIK Annex XVII Status

File name Description

KKDIK_Annex_XVII_Status_1810.ruc Rule File
KKDIK_Annex_XVII_Status_1810.mdb Mapping Database
KKDIK_Annex_XVII_Status_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
KKDIK_Annex_XVII_Status__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
KKDIK_Annex_XVII_Status_1810.pdf Functional Description

REACH Annex XVII Warnings

File name Description

REACH_Annex_XVII_Warnings_1810.ruc Rule File
REACH_Annex_XVII_Warnings_1810.mdb Mapping Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
REACH_Annex_XVII_Warnings__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
REACH_Annex_XVII_Warnings_1810.pdf Functional Description

REACH Annex XVII Status

File name Description

REACH_Annex_XVII_Status_1810.ruc Rule File

INTERNAL: SAP CUSTOMER 272 © SAP SE

 Technical Settings Expert Rules

REACH_Annex_XVII_Status_1810.mdb Mapping Database

REACH_Annex_XVII_Status_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
REACH_Annex_XVII_Status__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
REACH_Annex_XVII_Status_1810.pdf Functional Description

RS RestSub

File name Description

RS_RestSub_1810.ruc Rule File
RS_RestSub_1810.mdb Mapping Database
RS_RestSub_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
RS_RestSub__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RS_RestSub_1810.pdf Functional Description

HazardComp EMEA

File name Description

HazardComp_EMEA_1810.ruc Rule File
HazardComp_EMEA_1810.mdb Mapping Database
HazardComp_EMEA_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
comp_LEC50_V1-01.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
HazardComp_EMEA__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note

INTERNAL: SAP CUSTOMER 273 © SAP SE

 Technical Settings Expert Rules

HazardComp_EMEA_1810.pdf Functional Description

HazardComp CIS

File name Description

HazardComp_CIS_1810.ruc Rule File
HazardComp_CIS_1810.mdb Mapping Database
HazardComp_CIS_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
HazardComp_CIS__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
HazardComp_CIS_1810.pdf Functional Description

HazardComp TR

File name Description

HazardComp_TR_1810.ruc Rule File
HazardComp_TR_1810.mdb Mapping Database
HazardComp_TR_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
HazardComp_TR__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
HazardComp_TR_1810.pdf Functional Description

CLNOT

File name Description

CL_for_notification_1810.ruc Rule File
CL_for_notification_1810.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 in-
stalled and changes had be done in
the external tables, this delivered file
GHS_EU_externvalues.mdb should not be
used.

INTERNAL: SAP CUSTOMER 274 © SAP SE

 Technical Settings Expert Rules

GS_physchem_V1-22.ruc sub rule set which must be installed once as a

separate instance on the Expert-Server-PC
GHS_sub_pb2013_V1-8.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
CL_for_notification__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
CL_for_notification_1810.pdf Functional Description

The following files are included in the delivery:

CMR EU

File name Description

CMR_EU_1810.ruc Rule File
CMR_EU_1810.mdb Mapping Database
CMR_EU_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
CMR_EU__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
CMR_EU_1810.pdf Functional Description

Detergents

File name Description

Detergents_1810.ruc Rule File
Detergents_1810.mdb Mapping Database
Detergents_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
Detergents__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
Detergents_1810.pdf Functional Description

ICPE

File name Description

ICPE_1810.ruc Rule File

INTERNAL: SAP CUSTOMER 275 © SAP SE

 Technical Settings Expert Rules

ICPE_1810.mdb Mapping Database

ICPE_externvalues.mdb External Database
ICPE__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
ICPE_1810.pdf Functional Description

Maladies Professionelles

File name Description

MaladiesProfessionnelles_1810.ruc Rule File
MaladiesProfessionnelles_1810.mdb Mapping Database
MaladiesProfessionnelles_ External Database
externvalues.mdb
MaladiesProfessionnelles__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
MaladiesProfessionnelles_1810.pdf Functional Description

MAL Code

File name Description

MAL_Code_1810.ruc Rule File
MAL_Code_1810.mdb Mapping Database
MAL_Code_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
MAL_Code__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
MAL_Code_1810.pdf Functional Description

Medical Surveillance

File name Description

Medsurv_1810.ruc Rule File
Medsurv_1810.mdb Mapping Database
Medsurv__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note

INTERNAL: SAP CUSTOMER 276 © SAP SE

 Technical Settings Expert Rules

Medsurv_1810.pdf Functional Description

NL GAM

File name Description

NL_GAM_1810.ruc Rule File
NL_GAM_1810.mdb Mapping Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
NL_GAM__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
NL_GAM_1810.pdf Functional Description

PIC EU

File name Description

PIC_EU_1810.ruc Rule File
PIC_EU_1810.mdb Mapping Database
GHS__global_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GHS_EU_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GS_ident_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_sub_pb2013_V1-8.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
PIC_EU__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
PIC_EU_1810.pdf Functional Description

RegInfo AL

File name Description

RegInfo_AL_1810.ruc Rule File

INTERNAL: SAP CUSTOMER 277 © SAP SE

 Technical Settings Expert Rules

RegInfo_AL_1810.mdb Mapping Database

RegInfo_AL__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_AL_1810.pdf Functional Description

RegInfo CH

File name Description

RegInfo_CH_1810.ruc Rule File
RegInfo_CH_1810.mdb Mapping Database
RegInfo_CH__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_CH_1810.pdf Functional Description

RegInfo CZ

File name Description

RegInfo_CZ_1810.ruc Rule File
RegInfo_CZ_1810.mdb Mapping Database
RegInfo_CZ__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_CZ_1810.pdf Functional Description

RegInfo DE

File name Description

RegInfo_DE_1810.ruc Rule File
RegInfo_DE_1810.mdb Mapping Database
RegInfo_DE__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_DE_1810.pdf Functional Description

RegInfo DK

File name Description

RegInfo_DK_1810.ruc Rule File

INTERNAL: SAP CUSTOMER 278 © SAP SE

 Technical Settings Expert Rules

RegInfo_DK_1810.mdb Mapping Database

RegInfo_DK__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_DK_1810.pdf Functional Description

RegInfo HU

File name Description

RegInfo_HU_1810.ruc Rule File
RegInfo_HU_1810.mdb Mapping Database
RegInfo_HU__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_HU_1810.pdf Functional Description

RegInfo IT

File name Description

RegInfo_IT_1810.ruc Rule File
RegInfo_IT_1810.mdb Mapping Database
RegInfo_IT__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_IT_1810.pdf Functional Description

RegInfo LV

File name Description

RegInfo_LV_1810.ruc Rule File
RegInfo_LV_1810.mdb Mapping Database
RegInfo_LV__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_LV_1810.pdf Functional Description

RegInfo NL

File name Description

RegInfo_NL_1810.ruc Rule File
RegInfo_NL_1810.mdb Mapping Database

INTERNAL: SAP CUSTOMER 279 © SAP SE

 Technical Settings Expert Rules

RegInfo_NL_externvalues.mdb External Database

GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
RegInfo_NL__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_NL_1810.pdf Functional Description

RegInfo PL

File name Description

RegInfo_PL_1810.ruc Rule File
RegInfo_PL_1810.mdb Mapping Database
RegInfo_PL__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_PL_1810.pdf Functional Description

RegInfo RO

File name Description

RegInfo_RO_1810.ruc Rule File
RegInfo_RO_1810.mdb Mapping Database
RegInfo_RO__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_RO_1810.pdf Functional Description

RegInfo RS

File name Description

RegInfo_RS_1810.ruc Rule File
RegInfo_RS_1810.mdb Mapping Database
RegInfo_RS__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_RS_1810.pdf Functional Description

RegInfo SE

File name Description

INTERNAL: SAP CUSTOMER 280 © SAP SE

 Technical Settings Expert Rules

RegInfo_SE_1810.ruc Rule File

RegInfo_SE_1810.mdb Mapping Database
RegInfo_SE_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
RegInfo_SE__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_SE_1810.pdf Functional Description

RegInfo SI

File name Description

RegInfo_SI_1810.ruc Rule File
RegInfo_SI_1810.mdb Mapping Database
RegInfo_SI__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_SI_1810.pdf Functional Description

RegInfo TR

File name Description

RegInfo_TR_1810.ruc Rule File
RegInfo_TR_1810.mdb Mapping Database
RegInfo_TR__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
RegInfo_TR_1810.pdf Functional Description

Seveso III

File name Description

Seveso-III_1810.ruc Rule File
Seveso-III_1810.mdb Mapping Database
Seveso-III_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC

INTERNAL: SAP CUSTOMER 281 © SAP SE

 Technical Settings Expert Rules

Seveso-III__HISTORY.mdb database for the documentation of the

changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
Seveso-III_1810.pdf Functional Description

StFV

File name Description

StFV_1810.ruc Rule File
StFV_1810.mdb Mapping Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
StFV__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
StFV_1810.pdf Functional Description

TA Luft

File name Description

TAluft_1810.ruc Rule File
TAluft_1810.mdb Mapping Database
TAluft_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
TAluft__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
TALuft_1810.pdf Functional Description

TRGS510

File name Description

TRGS510_1810.ruc Rule File
TRGS510_1810.mdb Mapping Database
TRGS510_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC

INTERNAL: SAP CUSTOMER 282 © SAP SE

 Technical Settings Expert Rules

TRGS510__HISTORY.mdb database for the documentation of the

changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
TRGS510_1810.pdf Functional Description

TRGS900

File name Description

TRGS_900_1810.ruc Rule File
TRGS_900_1810.mdb Mapping Database
TRGS_900_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
TRGS_900__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
TRGS_900_1810.pdf Functional Description

VbF AT

File name Description

VbF_AT_1810.ruc Rule File
VbF_AT_1810.mdb Mapping Database
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
VbF_AT__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
VbF_AT_1810.pdf Functional Description

VOC CH

File name Description

VOC_CH_1810.ruc Rule File
VOC_CH_1810.mdb Mapping Database
VOC_CH_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
VOC_CH__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note

INTERNAL: SAP CUSTOMER 283 © SAP SE

 Technical Settings Expert Rules

VOC_CH_1810.pdf Functional Description

VOC EU

File name Description

VOC_EU_1810.ruc Rule File
VOC_EU_1810.mdb Mapping Database
VOC_EU_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
VOC_EU__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
VOC_EU_1810.pdf Functional Description

VOC PaintCoat

File name Description

VOC_PaintCoat_1810.ruc Rule File
VOC_PaintCoat_1810.mdb Mapping Database
VOC_PaintCoat_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
VOC_PaintCoat__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
VOC_PaintCoat_1810.pdf Functional Description

WGK (AwSV Annex 1 (5)

File name Description

WGK_1810.ruc Rule File
WGK_1810.mdb Mapping Database
WGK_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-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC

INTERNAL: SAP CUSTOMER 284 © SAP SE

 Technical Settings Expert Rules

GS_ident_V1-0.ruc sub rule set which must be installed once as a

separate instance on the Expert-Server-PC
WGK__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
WGK_1810.pdf Functional Description

Youth&Mothers

File name Description

YoMo_1810.ruc Rule File
YoMo_1810.mdb Mapping Database
YoMo_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
YoMo__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
YoMo_1810.pdf Functional Description

File name Description

LCID_1810.ruc Rule File
LCID_1810.mdb Mapping Database
GHS__global_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GHS_EU_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GS_ident_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GHS_sub_pb2013_V1-8.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_ident_V1-0.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
LCID__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
LCID_1810.pdf Functional Description

INTERNAL: SAP CUSTOMER 285 © SAP SE

 Technical Settings Expert Rules

E.3.2. Settings in Admin Tool

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM

The settings for the rule sets are:

DAPEC

Environment parameter Value of the parameter

Name ZEXP_DAPEC
Mapping Database DAPEC_1810.mdb
Rule File DAPEC_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

GHS EU

Environment parameter Value of the parameter

Name ZEXP_GHSEU
Mapping Database GHS_EU_1810.mdb
Rule File GHS_EU_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

GHS RU

Environment parameter Value of the parameter

Name ZEXP_GHSRU
Mapping Database GHS_RU_1810.mdb
Rule File GHS_RU_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

GHS TR

Environment parameter Value of the parameter

Name ZEXP_GHSTR
Mapping Database GHS_TR_1810.mdb
Rule File GHS_TR_1810.ruc
Additional Settings

INTERNAL: SAP CUSTOMER 286 © SAP SE

 Technical Settings Expert Rules

Name IgnoreWarnings
Value 322

EU to GHS

Environment parameter Value of the parameter

Name ZEXP_RTGHS
Mapping Database EU_TO_GHS_1810.mdb
Rule File EU_to_GHS_1810.ruc

HazardComp EU

Environment parameter Value of the parameter

Name ZEXP_HC_EU
Mapping Database HazardComp_EU_1810.mdb
Rule File HazardComp_EU_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

KKDIK Annex XVII Warnings

Environment parameter Value of the parameter

Name ZEXP_KK17
Mapping Database KKDIK_Annex_XVII_Warnings_1810.mdb
Rule File KKDIK_Annex_XVII_Warnings_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

KKDIK Annex XVII Status

Environment parameter Value of the parameter

Name ZEXP_KK17S
Mapping Database KKDIK_Annex_XVII_Status_1810.mdb
Rule File KKDIK_Annex_XVII_Status_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

REACH Annex XVII Warnings

Environment parameter Value of the parameter

INTERNAL: SAP CUSTOMER 287 © SAP SE

 Technical Settings Expert Rules

Name ZEXP_RA17
Mapping Database REACH_Annex_XVII_Warnings_1810.mdb
Rule File REACH_Annex_XVII_Warnings_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

REACH Annex XVII Status

Environment parameter Value of the parameter

Name ZEXP_RA17S
Mapping Database REACH_Annex_XVII_Status_1810.mdb
Rule File REACH_Annex_XVII_Status_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

RS RestSub

Environment parameter Value of the parameter

Name ZEXP_RSRST
Mapping Database RS_RestSub_1810.mdb
Rule File RS_RestSub_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

HazardComp EMEA

Environment parameter Value of the parameter

Name ZEXP_HC_EM
Mapping Database HazardComp_EMEA_1810.mdb
Rule File HazardComp_EMEA_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

HazardComp CIS

Environment parameter Value of the parameter

Name ZEXP_HCCIS
Mapping Database HazardComp_CIS_1810.mdb

INTERNAL: SAP CUSTOMER 288 © SAP SE

 Technical Settings Expert Rules

Rule File HazardComp_CIS_1810.ruc

Additional Settings
Name IgnoreWarnings
Value 322

HazardComp TR

Environment parameter Value of the parameter

Name ZEXP_HC_TR
Mapping Database HazardComp_TR_1810.mdb
Rule File HazardComp_TR_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

CLNOT

Environment parameter Value of the parameter

Name ZEXP_CLNOT
Mapping Database CL_for_notification_1810.mdb
Rule File CL_for_notification_1810.ruc
Technical prerequisites Expert SP23 or higher; OSS note 1450276
has to be installed

CMR EU

Environment parameter Value of the parameter

Name ZEXP_CMREU
Mapping Database CMR_EU_1810.mdb
Rule File CMR_EU_1810.ruc

Detergents

Environment parameter Value of the parameter

Name ZEXP_DETR
Mapping Database Detergents_1810.mdb
Rule File Detergents_1810.ruc

ICPE

Environment parameter Value of the parameter

Name ZEXP_ICPE
Mapping Database ICPE_1810.mdb

INTERNAL: SAP CUSTOMER 289 © SAP SE

 Technical Settings Expert Rules

Rule File ICPE_1810.ruc

MAL Code

Environment parameter Value of the parameter

Name ZEXP_MAL
Mapping Database MAL_Code_1810.mdb
Rule File MAL_Code_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

Maladies Professionnelles

Environment parameter Value of the parameter

Name ZEXP_F_MP
Mapping Database MaladiesProfessionnelles_1810.mdb
Rule File MaladiesProfessionnelles_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

Medical Surveillance

Environment parameter Value of the parameter

Name ZEXP_MEDS
Mapping Database Medsurv_1810.mdb
Rule File Medsurv_1810.ruc

NL GAM

Environment parameter Value of the parameter

Name ZEXP_NLGAM
Mapping Database NL_GAM_1810.mdb
Rule File NL_GAM_1810.ruc

PIC EU

Environment parameter Value of the parameter

Name ZEXP_PICEU
Mapping Database PIC_EU_1810.mdb
Rule File PIC_EU_1810.ruc
Additional Settings

INTERNAL: SAP CUSTOMER 290 © SAP SE

 Technical Settings Expert Rules

Name IgnoreWarnings
Value 322

RegInfo AL

Environment parameter Value of the parameter

Name ZEXP_RI_AL
Mapping Database RegInfo_AL_1810.mdb
Rule File RegInfo_AL_1810.ruc

RegInfo CH

Environment parameter Value of the parameter

Name ZEXP_RI_CH
Mapping Database RegInfo_CH_1810.mdb
Rule File RegInfo_CH_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

RegInfo CZ

Environment parameter Value of the parameter

Name ZEXP_RI_CZ
Mapping Database RegInfo_CZ_1810.mdb
Rule File RegInfo_CZ_1810.ruc

RegInfo DE

Environment parameter Value of the parameter

Name ZEXP_RI_DE
Mapping Database RegInfo_DE_1810.mdb
Rule File RegInfo_DE_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

RegInfo DK

Environment parameter Value of the parameter

Name ZEXP_RI_DK
Mapping Database RegInfo_DK_1810.mdb
Rule File RegInfo_DK_1810.ruc

INTERNAL: SAP CUSTOMER 291 © SAP SE

 Technical Settings Expert Rules

Additional Settings
Name IgnoreWarnings
Value 322

RegInfo HU

Environment parameter Value of the parameter

Name ZEXP_RI_HU
Mapping Database RegInfo_HU_1810.mdb
Rule File RegInfo_HU_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

RegInfo IT

Environment parameter Value of the parameter

Name ZEXP_RI_IT
Mapping Database RegInfo_IT_1810.mdb
Rule File RegInfo_IT_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

RegInfo LV

Environment parameter Value of the parameter

Name ZEXP_RI_LV
Mapping Database RegInfo_LV_1810.mdb
Rule File RegInfo_LV_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

RegInfo NL

Environment parameter Value of the parameter

Name ZEXP_RI_NL
Mapping Database RegInfo_NL_1810.mdb
Rule File RegInfo_NL_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

INTERNAL: SAP CUSTOMER 292 © SAP SE

 Technical Settings Expert Rules

RegInfo PL

Environment parameter Value of the parameter

Name ZEXP_RI_PL
Mapping Database RegInfo_PL_1810.mdb
Rule File RegInfo_PL_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

RegInfo RO

Environment parameter Value of the parameter

Name ZEXP_RI_RO
Mapping Database RegInfo_RO_1810.mdb
Rule File RegInfo_RO_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

RegInfo RS

Environment parameter Value of the parameter

Name ZEXP_RI_RS
Mapping Database RegInfo_RS_1810.mdb
Rule File RegInfo_RS_1810.ruc

RegInfo SE

Environment parameter Value of the parameter

Name ZEXP_RI_SE
Mapping Database RegInfo_SE_1810.mdb
Rule File RegInfo_SE_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

RegInfo SI

Environment parameter Value of the parameter

Name ZEXP_RI_SI
Mapping Database RegInfo_SI_1810.mdb
Rule File RegInfo_SI_1810.ruc

INTERNAL: SAP CUSTOMER 293 © SAP SE

 Technical Settings Expert Rules

Additional Settings
Name IgnoreWarnings
Value 322

RegInfo TR

Environment parameter Value of the parameter

Name ZEXP_RI_TR
Mapping Database RegInfo_TR_1810.mdb
Rule File RegInfo_TR_1810.ruc

Seveso III

Environment parameter Value of the parameter

Name ZEXP_SEVE3
Mapping Database Seveso-III_1810.mdb
Rule File Seveso-III_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

StFV

Environment parameter Value of the parameter

Name ZEXP_STFV
Mapping Database StFV_1810.mdb
Rule File StFV_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

TA Luft

Environment parameter Value of the parameter

Name ZEXP_TAL
Mapping Database TAluft_1810.mdb
Rule File TAluft_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

TRGS510

Environment parameter Value of the parameter

INTERNAL: SAP CUSTOMER 294 © SAP SE

 Technical Settings Expert Rules

Name ZEXP_TR510
Mapping Database TRGS510_1810.mdb
Rule File TRGS510_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

TRGS900

Environment parameter Value of the parameter

Name ZEXP_TR90
Mapping Database TRGS_900_1810.mdb
Rule File TRGS_900_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

VbF AT

Environment parameter Value of the parameter

Name ZEXP_VBFAT
Mapping Database VbF_AT_1810.mdb
Rule File VbF_AT_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

VOC CH

Environment parameter Value of the parameter

Name ZEXP_VOC
Mapping Database VOC_CH_1810.mdb
Rule File VOC_CH_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

VOC EU

Environment parameter Value of the parameter

Name ZEXP_VOCEU
Mapping Database VOC_EU_1810.mdb
Rule File VOC_EU_1810.ruc

INTERNAL: SAP CUSTOMER 295 © SAP SE

 Technical Settings Expert Rules

Additional Settings
Name IgnoreWarnings
Value 322

VOC PaintCoat

Environment parameter Value of the parameter

Name ZEXP_VOCPC
Mapping Database VOC_PaintCoat_1810.mdb
Rule File VOC_PaintCoat_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

WGK (AwSV Annex 1 (5)

Environment parameter Value of the parameter

Name ZEXP_WGK
Mapping Database WGK_1810.mdb
Rule File WGK_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

Youth&Mothers

Environment parameter Value of the parameter

Name ZEXP_YOMO
Mapping Database YoMo_1810.mdb
Rule File YoMo_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

LCID

Environment parameter Value of the parameter

Name ZEXP_LCID
Mapping Database LCID_1810.mdb
Rule File LCID_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

INTERNAL: SAP CUSTOMER 296 © SAP SE

 Technical Settings Expert Rules

E.3.3. Settings in Admin Tool - Sub Rules

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM

The settings for the sub rule sets are:

GS_BASE_1_1

Environment parameter Value of the parameter

Name GS_BASE_1_1
Rule File GS_base_V1-11.ruc

GS_PHYSCHEM_1_2

Environment parameter Value of the parameter

Name GS_PHYSCHEM_1_2
Rule File GS_physchem_V1-22.ruc

GS_IDENT

Environment parameter Value of the parameter

Name GS_IDENT
Rule File GS_ident_V1-0.ruc

COMP_LEC50

Environment parameter Value of the parameter

Name COMP_LEC50
Rule File comp_LEC50_V1-01.ruc

GHS_SUB_PB2009_2_7

Environment parameter Value of the parameter

Name GHS_SUB_PB2009_2_7
Rule File GHS_sub_pb2009_V2-7.ruc

GHS_SUB_PB2013_1_8

Environment parameter Value of the parameter

Name GHS_SUB_PB2013_1_8
Rule File GHS_sub_pb2013_V1-8.ruc

GHS_EXPL_2_4

Environment parameter Value of the parameter

INTERNAL: SAP CUSTOMER 297 © SAP SE

 Technical Settings Expert Rules

Name GHS_EXPL_2_4
Rule File GHS_expl_V2-4.ruc

GHS_LABEL_2_0

Environment parameter Value of the parameter

Name GHS_LABEL_2_0
Rule File GHS_label_V2-02.ruc

GHS_PURE_1_4

Environment parameter Value of the parameter

Name GHS_PURE_1_4
Rule File GHS_pure_V1-42.ruc

E.3.4. User Exit Settings

The following settings are proposed for the user exit:

Dapec

User exit name ZEXP_DAPEC

User exit description EHS-Expert: DAPEC

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_DAPEC
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_DAPEC
EXPERT_WRITE_VALIDITY_AREA REG_EU

INTERNAL: SAP CUSTOMER 298 © SAP SE

 Technical Settings Expert Rules

GHS EU

User exit name ZEXP_GHSEU

User exit description EHS-Expert: GHS EU

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_GHSEU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_GHSEU
EXPERT_WRITE_VALIDITY_AREA REG_EU

GHS RU

User exit name ZEXP_GHSRU

User exit description EHS-Expert: GHS RU

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S

INTERNAL: SAP CUSTOMER 299 © SAP SE

 Technical Settings Expert Rules

EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA RU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_GHSRU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_GHSRU
EXPERT_WRITE_VALIDITY_AREA RU

GHS TR

User exit name ZEXP_GHSTR

User exit description EHS-Expert: GHS TR

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA TR
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_GHSTR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_GHSTR
EXPERT_WRITE_VALIDITY_AREA TR

EU to GHS

User exit name ZEXP_RTGHS

User exit description EHS-Expert: EU to GHS

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 300 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RTGHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RTGHS
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

HazardComp EU

User exit name ZEXP_HC_EU

User exit description EHS-Expert: HazardComp_EU

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_HC_EU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_HC_EU
EXPERT_WRITE_VALIDITY_AREA REG_EU

KKDIK Annex XVII Warnings

User exit name ZEXP_KK17

User exit description EHS-Expert: KKDIK Annex XVII Warnings

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 301 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA TR
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_KK17
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_KK17
EXPERT_WRITE_VALIDITY_AREA TR

KKDIK Annex XVII Status

User exit name ZEXP_KK17S

User exit description EHS-Expert: KKDIK Annex XVII Status

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA TR
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_KK17S
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_KK17S
EXPERT_WRITE_VALIDITY_AREA TR

REACH Annex XVII Warnings

User exit name ZEXP_RA17

User exit description EHS-Expert: REACH Annex XVII Warnings

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 302 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RA17
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RA17
EXPERT_WRITE_VALIDITY_AREA REG_EU

REACH Annex XVII Status

User exit name ZEXP_RA17S

User exit description EHS-Expert: REACH Annex XVII Status

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RA17S
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RA17S
EXPERT_WRITE_VALIDITY_AREA REG_EU

RS RestSub

User exit name ZEXP_RSRST

User exit description EHS-Expert: RS RestSub

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 303 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA RS
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RSRST
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RSRST
EXPERT_WRITE_VALIDITY_AREA RS

HazardComp EMEA

User exit name ZEXP_HC_EM

User exit description EHS-Expert: HazardComp_EMEA

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_HC_EM
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_HC_EM
EXPERT_WRITE_VALIDITY_AREA REG_EU

HazardComp CIS

User exit name ZEXP_HCCIS

User exit description EHS-Expert: HazardComp_CIS

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 304 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_HCCIS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_HC_RU
EXPERT_WRITE_VALIDITY_AREA RU

HazardComp TR

User exit name ZEXP_HC_TR

User exit description EHS-Expert: HazardComp_TR

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA TR
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_HC_TR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_HC_TR
EXPERT_WRITE_VALIDITY_AREA TR

CLNOT

User exit name ZEXP_CLNOT

User exit description EHS-Expert: CL for notification

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 305 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_CLNOT
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_CLNOT
EXPERT_WRITE_VALIDITY_AREA REG_EU

CMR EU

User exit name ZEXP_CMREU

User exit description EHS-Expert: CMR (EU)

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_CMREU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_CMREU
EXPERT_WRITE_VALIDITY_AREA REG_EU

Detergents

User exit name ZEXP_DETR

User exit description EHS-Expert: Detergents

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 306 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_DETR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_DETR
EXPERT_WRITE_VALIDITY_AREA REG_EU

ICPE

User exit name ZEXP_ICPE

User exit description EHS-Expert: ICPE (FR)

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA FR
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_ICPE
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_ICPE
EXPERT_WRITE_VALIDITY_AREA FR

TRGS510

User exit name ZEXP_TR510

User exit description EHS-Expert: TRGS510

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 307 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA DE
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_TR510
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_LGK
EXPERT_WRITE_VALIDITY_AREA DE

MAL Code

User exit name ZEXP_MAL

User exit description EHS-Expert: Mal Code (DK)

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA DK
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_MAL
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_MAL
EXPERT_WRITE_VALIDITY_AREA DK

Maladies Professionnelles

User exit name ZEXP_F_MP

User exit description EHS-Expert: Maladies Professionnelles

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 308 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA FR
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_F_MP
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_F_MP
EXPERT_WRITE_VALIDITY_AREA FR

Medical Surveillance

User exit name ZEXP_MEDS

User exit description EHS-Expert: Medical Surveillance

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA FR
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_MEDS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_MEDS
EXPERT_WRITE_VALIDITY_AREA FR

NL GAM

User exit name ZEXP_NLGAM

User exit description EHS-Expert: NL GAM

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 309 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA NL
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_NLGAM
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_NLGAM
EXPERT_WRITE_VALIDITY_AREA NL

PIC EU

User exit name ZEXP_PICEU

User exit description EHS-Expert: PIC EU

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_PICEU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_PICEU
EXPERT_WRITE_VALIDITY_AREA REG_EU

RegInfo AL

User exit name ZEXP_RI_AL

User exit description EHS-Expert: RegInfo AL

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 310 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA AL
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_AL
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_AL
EXPERT_WRITE_VALIDITY_AREA AL

RegInfo CH

User exit name ZEXP_RI_CH

User exit description EHS-Expert: RegInfo CH

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA CH
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_CH
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_CH
EXPERT_WRITE_VALIDITY_AREA CH

RegInfo CZ

User exit name ZEXP_RI_CZ

User exit description EHS-Expert: RegInfo CZ

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 311 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA CZ
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_CZ
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_CZ
EXPERT_WRITE_VALIDITY_AREA CZ

RegInfo DE

User exit name ZEXP_RI_DE

User exit description EHS-Expert: RegInfo DE

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA DE
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_DE
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_DE
EXPERT_WRITE_VALIDITY_AREA DE

RegInfo DK

User exit name ZEXP_RI_DK

User exit description EHS-Expert: RegInfo DK

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 312 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA DK
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_DK
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_DK
EXPERT_WRITE_VALIDITY_AREA DK

RegInfo HU

User exit name ZEXP_RI_HU

User exit description EHS-Expert: RegInfo HU

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA HU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_HU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_HU
EXPERT_WRITE_VALIDITY_AREA HU

RegInfo IT

User exit name ZEXP_RI_IT

User exit description EHS-Expert: RegInfo IT

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 313 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA IT
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_IT
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_IT
EXPERT_WRITE_VALIDITY_AREA IT

RegInfo LV

User exit name ZEXP_RI_LV

User exit description EHS-Expert: RegInfo LV

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA LV
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_LV
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_LV
EXPERT_WRITE_VALIDITY_AREA LV

RegInfo NL

User exit name ZEXP_RI_NL

User exit description EHS-Expert: RegInfo NL

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 314 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA NL
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_NL
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_NL
EXPERT_WRITE_VALIDITY_AREA NL

RegInfo PL

User exit name ZEXP_RI_PL

User exit description EHS-Expert: RegInfo PL

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA PL
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_PL
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_PL
EXPERT_WRITE_VALIDITY_AREA PL

RegInfo RO

User exit name ZEXP_RI_RO

User exit description EHS-Expert: RegInfo RO

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 315 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA RO
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_RO
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_RO
EXPERT_WRITE_VALIDITY_AREA RO

RegInfo RS

User exit name ZEXP_RI_RS

User exit description EHS-Expert: RegInfo RS

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA RS
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_RS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_RS
EXPERT_WRITE_VALIDITY_AREA RS

RegInfo SE

User exit name ZEXP_RI_SE

User exit description EHS-Expert: RegInfo SE

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 316 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA SE
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_SE
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_SE
EXPERT_WRITE_VALIDITY_AREA SE

RegInfo SI

User exit name ZEXP_RI_SI

User exit description EHS-Expert: RegInfo SI

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA SI
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_SI
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_SI
EXPERT_WRITE_VALIDITY_AREA SI

RegInfo TR

User exit name ZEXP_RI_TR

User exit description EHS-Expert: RegInfo TR

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE

INTERNAL: SAP CUSTOMER 317 © SAP SE

 Technical Settings Expert Rules

EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA TR
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RI_TR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RI_TR
EXPERT_WRITE_VALIDITY_AREA TR

Seveso III

User exit name ZEXP_SEVE3

User exit description EHS-Expert: Seveso III (EU)

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_SEVE3
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_SEVE3
EXPERT_WRITE_VALIDITY_AREA REG_EU

StFV

User exit name ZEXP_STFV

INTERNAL: SAP CUSTOMER 318 © SAP SE

 Technical Settings Expert Rules

User exit description EHS-Expert: StFV

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA CH
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_STFV
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_STFV
EXPERT_WRITE_VALIDITY_AREA CH

TA Luft

User exit name ZEXP_TAL

User exit description EHS-Expert: TI-Air Quality (TA Luft /DE)

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA DE
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_TAL
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_TAL

INTERNAL: SAP CUSTOMER 319 © SAP SE

 Technical Settings Expert Rules

EXPERT_WRITE_VALIDITY_AREA DE

TRGS 900

User exit name ZEXP_TR90

User exit description EHS-Expert: TRGS 900 (DE)

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA DE
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_TR90
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_TR90
EXPERT_WRITE_VALIDITY_AREA DE

VbF AT

User exit name ZEXP_VBFAT

User exit description EHS-Expert: VBF (AT)

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA AT
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_VBFAT
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_VBFAT

INTERNAL: SAP CUSTOMER 320 © SAP SE

 Technical Settings Expert Rules

EXPERT_WRITE_VALIDITY_AREA AT

VOC CH

User exit name ZEXP_VOC

User exit description EHS-Expert: VOC (CH)

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA CH
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_VOC
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_VOC
EXPERT_WRITE_VALIDITY_AREA CH

VOC EU

User exit name ZEXP_VOCEU

User exit description EHS-Expert: VOC (EU)

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_VOCEU
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_VOCEU

INTERNAL: SAP CUSTOMER 321 © SAP SE

 Technical Settings Expert Rules

EXPERT_WRITE_VALIDITY_AREA REG_EU

VOC PaintCoat

User exit name ZEXP_VOCPC

User exit description EHS-Expert: VOC PaintCoat

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_VOCPC
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_VOCPC
EXPERT_WRITE_VALIDITY_AREA REG_EU

WGK

User exit name ZEXP_WGK

User exit description EHS-Expert: WGK (DE)

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA DE
EXPERT_RES_BY_SRSID_OWNID_FLG X

INTERNAL: SAP CUSTOMER 322 © SAP SE

 Technical Settings Expert Rules

EXPERT_RULE_SET ZEXP_WGK
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_WGK
EXPERT_WRITE_VALIDITY_AREA DE
EXPERT_WRITE_USAGE_1 PUBLIC/AT

Youth&Mothers

User exit name ZEXP_YOMO

User exit description EHS-Expert: Youth&Mothers

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_YOMO
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_YOMO
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

LCID

User exit name ZEXP_LCID

User exit description EHS-Expert: LCID

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX

INTERNAL: SAP CUSTOMER 323 © SAP SE

 Technical Settings Expert Rules

EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_LCID
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_LCID
EXPERT_WRITE_VALIDITY_AREA REG_EU

E.3.5. Other Settings

The following customizing settings are necessary:

Source

Value of the parameter affected rule sets

EHS-Expert all

Data Origin

Value of the parameter affected rule sets

ZEXP_DAPEC DAPEC
ZEXP_GHSEU GHS EU
ZEXP_GHSRU GHS RU
ZEXP_GHSTR GHS TR
ZEXP_RTGHS EU to GHS
ZEXP_HC_EU HazardComp EU
ZEXP_KK17 KKDIK Annex XVII Warnings
ZEXP_KK17S KKDIK Annex XVII Status
ZEXP_RA17 REACH Annex XVII Warnings
ZEXP_RA17S REACH Annex XVII Status
ZEXP_RSRST RS RestSub
ZEXP_HC_EM HazardComp EMEA
ZEXP_HC_RU HazardComp CIS
ZEXP_HC_TR HazardComp TR
ZEXP_CLNOT CL for notification
ZEXP_CMREU CMR (EU)
ZEXP_DETR Detergents
ZEXP_ICPE ICPE (FR)
ZEXP_LGK TRGS 510

INTERNAL: SAP CUSTOMER 324 © SAP SE

 Technical Settings Expert Rules

ZEXP_MAL MAL Code (DK)

ZEXP_F_MP Maladies Professionnelles (FR)
ZEXP_MEDS Medical Surveillance (FR)
ZEXP_NLGAM NL GAM
ZEXP_PICEU PIC EU
ZEXP_RI_AL RegInfo AL
ZEXP_RI_CH RegInfo CH
ZEXP_RI_CZ RegInfo CZ
ZEXP_RI_DE RegInfo DE
ZEXP_RI_DK RegInfo DK
ZEXP_RI_HU RegInfo HU
ZEXP_RI_IT RegInfo IT
ZEXP_RI_LV RegInfo LV
ZEXP_RI_NL RegInfo NL
ZEXP_RI_PL RegInfo PL
ZEXP_RI_RO RegInfo RO
ZEXP_RI_RS RegInfo RS
ZEXP_RI_SE RegInfo SE
ZEXP_RI_SI RegInfo SI
ZEXP_RI_TR RegInfo TR
ZEXP_SEVE3 Seveso III (EU)
ZEXP_STFV StFV
ZEXP_TAL TA Luft (DE)
ZEXP_TR90 TRGS 900
ZEXP_VBFAT VBF (AT)
ZEXP_VOC VOC CH
ZEXP_VOCEU VOC EU
ZEXP_VOCPC VOC PaintCoat
ZEXP_WGK WGK
ZEXP_YOMO Youth & Mothers
ZEXP_LCID LCID

Validity Area

Value of the parameter affected rule sets

REG_EU GHS EU
CG HC_EMEA - Congo
IL HC_EMEA - Israel
KE HC_EMEA - Kenya
NG HC_EMEA - Nigeria

INTERNAL: SAP CUSTOMER 325 © SAP SE

 Technical Settings Expert Rules

ZA HC_EMEA - South Africa

TZ HC_EMEA - Tanzania, United Republic of
BY HC_CIS - Belarus
GE HC_CIS - Georgia
KG HC_CIS - Kyrgyzstan
KZ HC_CIS - Kazakhstan
UA HC_CIS- Ukraine

User Defined Text Type

Value of the parameter affected rule sets

EX all rule sets with an explanation component

Rating

Value of the parameter affected rule sets

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)
LABEL_S GHS_TR (needed for reduced label - if output
of label for packages < 125 ml has to be written
with its own usage)
UPO WGK, VOC PaintCoat

Regulatory List

Value of the parameter affected rule sets

GHS_EU GHS EU
GHS EU to GHS
GHS_RU GHS RU
GHS_TR GHS TR
04/42/EC VOC PaintCoat

Identifier NAM

Value of the parameter affected rule sets

EINECS DAPEC

E.4. Settings to implement the RegStat rule set

package
E.4.1. File Overview

INTERNAL: SAP CUSTOMER 326 © SAP SE

 Technical Settings Expert Rules

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.

The following files are included in the delivery:

NotStat
File name Description
NotStat_frame_master_1810.ruc Rule File
NotStat_frame_master_ProdComp_1810.mdb Mapping Database (ProdComp variant)
NotStat_frame_master_StandComp_1810.mdb Mapping Database (StandComp variant)
NotStat_externvalues.mdb External Database
NotStat_1810.ruc sub rule (core logic)
NotStat_sub_TSCA12b_1810.ruc sub rule (TSCA 12b)
NotStat_sub_expl_1810.ruc sub rule (Explanation Component)
GS_ident_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_ident_V1-0.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
NotStat_frame_master__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_RegStatus_1810.pdf Release Note
Notstat_1810.pdf Functional Description

RestrictionStatus
File name Description
RestrictionStatus_1810.ruc Rule File
RestrictionStatus_1810.mdb Mapping Database
RestrictionStatus_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
RestrictionStatus__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_RegStatus_1810.pdf Release Note
RestrictionStatus_1810.pdf Functional Description

E.4.2. Settings in Admin Tool

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM.

INTERNAL: SAP CUSTOMER 327 © SAP SE

 Technical Settings Expert Rules

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.

The settings for the rule sets are:

NotStat

Environment parameter Value of the parameter

Name ZEXP_NOTS
Mapping Database (ProdComp variant) NotStat_frame_master_ProdComp_1810.mdb
(ProdComp variant)
Mapping Database (StandComp variant) NotStat_frame_master_StandComp_1810.mdb
(StandComp variant)
Rule File NotStat_frame_master_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322,330,331,332,355

RestrictionStatus

Environment parameter Value of the parameter

Name ZEXP_RESST
Mapping Database RestrictionStatus_1810.mdb
Rule File RestrictionStatus_1810.ruc

E.4.3. Settings in Admin Tool - Sub Rules

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM.

The settings for the sub rule sets are:

GS_BASE_1_1

Environment parameter Value of the parameter

Name GS_BASE_1_1
Rule File GS_base_V1-11.ruc

GS_IDENT

Environment parameter Value of the parameter

Name GS_IDENT
Rule File GS_ident_V1-0.ruc

NOTSTAT_SUB_1810

Environment parameter Value of the parameter

INTERNAL: SAP CUSTOMER 328 © SAP SE

 Technical Settings Expert Rules

Name NOTSTAT_SUB_1810
Rule File NotStat_1810.ruc

NOTSTAT_SUB_TSCA12B_1810

Environment parameter Value of the parameter

Name NOTSTAT_SUB_TSCA12B_1810
Rule File NotStat_sub_TSCA12b_1810.ruc

NOTSTAT_SUB_EXPL_1810

Environment parameter Value of the parameter

Name NOTSTAT_SUB_EXPL_1810
Rule File NotStat_sub_expl_1810.ruc

E.4.4. User Exit Settings

The following settings are proposed for the user exit:

NotStat

User exit name ZEXP_NOTS

User exit description EHS-Expert: Notstat

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_NOTS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_NOTS
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

INTERNAL: SAP CUSTOMER 329 © SAP SE

 Technical Settings Expert Rules

RestrictionStatus

User exit name ZEXP_RESST

User exit description EHS-Expert: RestrictionStatus

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_RESST
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_RESST
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

E.4.5. Other Settings

The following customizing settings are necessary:

Source

Value of the parameter affected rule sets

EHS-Expert all

Data Origin

Value of the parameter affected rule sets

ZEXP_NOTS NotStat
ZEXP_RESST RestrictionStatus

Rating

Value of the parameter affected rule sets

REACH NotStat

User Defined Text Type

Value of the parameter affected rule sets

EX all rule sets with an explanation component

INTERNAL: SAP CUSTOMER 330 © SAP SE

 Technical Settings Expert Rules

E.5. Settings to implement the DangGoods rule

set package
E.5.1. File Overview
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.

The following files are included in the delivery:

DangGoods

File name Description

DangGoods_master_global_1810.ruc Rule File (global)
DangGoods_master_1810.ruc Rule File (local version)
DangGoods_master_global_1810.mdb Mapping Database
DangGoods_externvalues.mdb External Database
DangGoods_1810.ruc sub rule set (central part for classification pro-
cess for solids/liquids)
GHS_sub_pb2017_V1-0.ruc sub rule set (GHS classification via compo-
nent data)
DangGoods_gas_1810.ruc sub rule set (classification for gaseous mix-
tures and hazard inducer determination)
DangGoods_report_quant_1810.ruc sub rule set (determination of reportable quan-
tities) (only global version!)
GS_ident_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_ident_V1-0.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
DangGoods_master__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
ReleaseNote_DangGoods_1810.pdf Release Note
DangGoods_1810.pdf Functional Description

E.5.2. Settings in Admin Tool

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM.

INTERNAL: SAP CUSTOMER 331 © SAP SE

 Technical Settings Expert Rules

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.

The settings for the rule sets are:

DangGoods

Environment parameter Value of the parameter

Name ZEXP_DG
Mapping Database DangGoods_master_global_1810.mdb
Rule File DangGoods_master_global_1810.ruc / Dang-
Goods_master_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

E.5.3. Settings in Admin Tool - Sub Rules

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM.

The settings for the sub rule sets are:

GS_BASE_1_1

Environment parameter Value of the parameter

Name GS_BASE_1_1
Rule File GS_base_V1-11.ruc

GS_PHYSCHEM_1_2

Environment parameter Value of the parameter

Name GS_PHYSCHEM_1_2
Rule File GS_physchem_V1-22.ruc

GS_IDENT

Environment parameter Value of the parameter

Name GS_IDENT
Rule File GS_ident_V1-0.ruc

DG_SUB_1810

Environment parameter Value of the parameter

Name DG_SUB_1810

INTERNAL: SAP CUSTOMER 332 © SAP SE

 Technical Settings Expert Rules

Rule File DangGoods_1810.ruc

GHS_SUB_PB2017_1_0

Environment parameter Value of the parameter

Name GHS_SUB_PB2017_1_0
Rule File GHS_sub_pb2017_V1-0.ruc

DG_SUB_GAS_1810

Environment parameter Value of the parameter

Name DG_SUB_GAS_1810
Rule File DangGoods_gas_1810.ruc

DG_RQ_1810

Environment parameter Value of the parameter

Name DG_RQ_1810
Rule File DangGoods_report_quant_1810.ruc

E.5.4. User Exit Settings

The following settings are proposed for the user exit:

DangGoods

User exit name ZEXP_DG

User exit description EHS-Expert: DangGoods

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_DG

INTERNAL: SAP CUSTOMER 333 © SAP SE

 Technical Settings Expert Rules

EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_DG
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

E.5.5. Other Settings

The following customizing settings are necessary:

Source

Value of the parameter affected rule sets

EHS-Expert all

Data Origin

Value of the parameter affected rule sets

ZEXP_DG DangGoods

User Defined Text Type

Value of the parameter affected rule sets

EX all rule sets with an explanation component

Identifier NAM

Value of the parameter affected rule sets

DG-CLASS DangGoods

E.6. Settings to implement the MSDSMaker rule

set package

E.6.1. File Overview

The following files are included in the delivery:

MSDSMaker

File name Description

setup.exe Installation procedure for front-end program
MSDSMAKER.CAB Archive with files for extraction by the installer
setup.lst Installation configuration file
MSDSRule_1810.ruc Rule File
MSDSRule_1810.mdb Mapping Database
MSDSMaker.mdb External Database

INTERNAL: SAP CUSTOMER 334 © SAP SE

 Technical Settings Expert Rules

MSDSRule_sub_V4-1.ruc sub rule set

GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert Server PC
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
separate instance on the Expert Server PC
ReleaseNote_MSDSMaker_1810.pdf Release Note
MSDSMaker_1810.pdf Functional Description

E.6.2. Settings in Admin Tool

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM

The settings for the rule sets are:

MSDSMaker

Environment parameter Value of the parameter

Name ZEXP_SDS
Mapping Database MSDSRule_1810.mdb
Rule File MSDSRule_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

E.6.3. Settings in Admin Tool - Sub Rules

The above listed settings have to be maintained via the Expert Admin Tool or within the trans-
action CGSADM

The settings for the sub rule sets are:

GS_BASE_1_1

Environment parameter Value of the parameter

Name GS_BASE_1_1
Rule File GS_base_V1-11.ruc

GS_PHYSCHEM_1_2

Environment parameter Value of the parameter

Name GS_PHYSCHEM_1_2
Rule File GS_physchem_V1-22.ruc

MSDSRULE_SUB_4_1

Environment parameter Value of the parameter

INTERNAL: SAP CUSTOMER 335 © SAP SE

 Technical Settings Expert Rules

Name MSDSRULE_SUB_4_1
Rule File MSDSRule_sub_V4-1.ruc

E.6.4. User Exit Settings

The following settings are proposed for the user exit:

MSDSMaker

User exit name ZEXP_SDS

User exit description EHS-Expert: MSDSMaker

Environment parameter Value of the parameter

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_SDS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_SDS
EXPERT_WRITE_VALIDITY_AREA REG_WORLD

E.6.5. Other Settings

The following customizing settings are necessary:

Source

Value of the parameter affected rule sets

EHS-Expert all

Data Origin

Value of the parameter affected rule sets

ZEXP_SDS MSDSMaker

INTERNAL: SAP CUSTOMER 336 © SAP SE

Appendix F. Technical Settings MSDS
Templates
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 Template for

EMEA
F.1.1. File Overview
The following files are included in the delivery:

EU / EU_EXT / EMEA / CIS

File name Description
customizing transport
R902923.NE5 SDS customizing transport NE5K902923 for the ERC
SDS template update 1810
K902923.NE5 SDS customizing transport NE5K902923 for the ERC
SDS template update 1810
documents
SDS_1810_EU_Specification.pdf Specification - Document for EU
SDS_1810_EU_Specification_ Specification - Document for EU showing differences to
changes_marked.pdf previous version
SDS_1810_CIS_Specification.pdf Specification - Document for CIS
SDS_1810_CIS_Specification_ Specification - Document for CIS showing differences
changes_marked.pdf to previous version
SDS_1810_EMEA_Specification.pdf Specification - Document for EMEA
SDS_1810_EMEA_Specification_ Specification - Document for EMEA showing differences
changes_marked.pdf to previous version
SDS_1810_GHS_Specification.pdf Specification - Document for GHS (purple book)
SDS_1810_GHS_Specification_ Specification - Document for GHS showing differences
changes_marked.pdf to previous version
SDS_1810_RTL_GHS_based_ Specification - Document for RTL SDS template based
Specification.pdf on GHS
SDS_1810_RTL_EU_EXT_based_ Specification - Document for RTL SDS template based
Specification.pdf on EU_EXT
SDS_1810_RTL_EMEA_based_ Specification - Document for RTL SDS template based
Specification.pdf on EMEA
SDS_1810_RTL_GHS_based_ Specification - Document for RTL SDS template based
Specification_changes_marked.pdf on GHS showing differences to previous version

INTERNAL: SAP CUSTOMER 337 © SAP SE

 Technical Settings MSDS Templates

SDS_1810_RTL_EU_EXT_based_ Specification - Document for RTL SDS template based

Specification_changes_marked.pdf on EU_EXT showing differences to previous version
SDS_1810_RTL_EMEA_based_ Specification - Document for RTL SDS template based
Specification_changes_marked.pdf on EMEA showing differences to previous version
Overview_SDS_Templates_used_ Overview on templates and used includes
Includes_1810.xlsx
ReleaseNote_SDS_Templates_ ReleaseNote for the ERC SDS template 1810
1810.pdf
RGV_1810_Configuration.pdf Overview on the generationvariants and how to main-
tain them
SDS_Template_Changes_ERC_ Overview on the SDS template changes, updates and
1810.xlsx corrections in ERC update 1810
SDS-layouts
SDS_1810_BASIC_01.dat Basic SDS template Import-file, Section 1
SDS_1810_BASIC_01.doc Basic SDS template document-file, section 1
SDS_1810_BASIC_02.dat Basic SDS template Import-file, section 2
SDS_1810_BASIC_02.doc Basic SDS template document-file, section 2
SDS_1810_BASIC_02_EMEA.dat Template Import-file for SDS EMEA, Section 2
SDS_1810_BASIC_02_EMEA.doc Template document-file for SDS EMEA, Section 2
SDS_1810_BASIC_03.dat Basic SDS template Import-file, section 3
SDS_1810_BASIC_03.doc Basic SDS template document-file, section 3
SDS_1810_BASIC_04.dat Basic SDS template Import-file, section 4
SDS_1810_BASIC_04.doc Basic SDS template document-file, section 4
SDS_1810_BASIC_05.dat Basic SDS template Import-file, section 5
SDS_1810_BASIC_05.doc Basic SDS template document-file, section 5
SDS_1810_BASIC_06.dat Basic SDS template Import-file, section 6
SDS_1810_BASIC_06.doc Basic SDS template document-file, section 6
SDS_1810_BASIC_07.dat Basic SDS template Import-file, section 7
SDS_1810_BASIC_07.doc Basic SDS template document-file, section 7
SDS_1810_BASIC_08.dat Basic SDS template Import-file, section 8
SDS_1810_BASIC_08.doc Basic SDS template document-file, section 8
SDS_1810_BASIC_09.dat Basic SDS template Import-file, section 9
SDS_1810_BASIC_09.doc Basic SDS template document-file, section 9
SDS_1810_BASIC_10.dat Basic SDS template Import-file, section 10
SDS_1810_BASIC_10.doc Basic SDS template document-file, section 10
SDS_1810_BASIC_11.dat Basic SDS template Import-file, section 11
SDS_1810_BASIC_11.doc Basic SDS template document-file, section 11
SDS_1810_BASIC_12.dat Basic SDS template Import-file, section 12
SDS_1810_BASIC_12.doc Basic SDS template document-file, section 12
SDS_1810_BASIC_13.dat Basic SDS template Import-file, section 13

INTERNAL: SAP CUSTOMER 338 © SAP SE

 Technical Settings MSDS Templates

SDS_1810_BASIC_13.doc Basic SDS template document-file, section 13

SDS_1810_BASIC_14.dat Basic SDS template Import-file, section 14
SDS_1810_BASIC_14.doc Basic SDS template document-file, section 14
SDS_1810_BASIC_15.dat Basic SDS template Import-file, section 15
SDS_1810_BASIC_15.doc Basic SDS template document-file, section 15
SDS_1810_BASIC_16.dat Basic SDS template Import-file, section 16
SDS_1810_BASIC_16.doc Basic SDS template document-file, section 16
SDS_1810_CIS_01.dat Template Import-file for SDS CIS, Section 1
SDS_1810_CIS_01.doc Template document-file for SDS CIS Section 1
SDS_1810_CIS_02.dat Template Import-file for SDS CIS, Section 2
SDS_1810_CIS_02.doc Template document-file for SDS CIS Section 2
SDS_1810_CIS_03.dat Template Import-file for SDS CIS, Section 3
SDS_1810_CIS_03.doc Template document-file for SDS CIS Section 3
SDS_1810_CIS_12.doc Template document-file for SDS CIS, additional part of
section 12
SDS_1810_CIS_12.dat Template Import-file for SDS CIS, additional part of sec-
tion 12
SDS_1810_CIS_16.dat Template Import-file for SDS CIS, Section 16
SDS_1810_CIS_16.doc Template document-file for SDS CIS Section 16
SDS_1810_CIS_MAIN.dat Template Import-file for SDS CIS
SDS_1810_CIS_MAIN.doc Template document-file for SDS CIS
SDS_1810_EU_01.dat Template Import-file for SDS EU, Section 1
SDS_1810_EU_01.doc Template document-file for SDS EU, Section 1
SDS_1810_EU_02.dat Template Import-file for SDS EU, Section 2
SDS_1810_EU_02.doc Template document-file for SDS EU, Section 2
SDS_1810_EU_03.dat Template Import-file for SDS EU, Section 3
SDS_1810_EU_03.doc Template document-file for SDS EU, Section 3
SDS_1810_EU_04.dat Template Import-file for SDS EU, Section 4
SDS_1810_EU_04.doc Template document-file for SDS EU, Section 4
SDS_1810_EU_05.dat Template Import-file for SDS EU, Section 5
SDS_1810_EU_05.doc Template document-file for SDS EU, Section 5
SDS_1810_EU_06.dat Template Import-file for SDS EU, Section 6
SDS_1810_EU_06.doc Template document-file for SDS EU, Section 6
SDS_1810_EU_07.dat Template Import-file for SDS EU, Section 7
SDS_1810_EU_07.doc Template document-file for SDS EU, Section 7
SDS_1810_EU_08.dat Template Import-file for SDS EU, Section 8
SDS_1810_EU_08.doc Template document-file for SDS EU, Section 8
SDS_1810_EU_09.dat Template Import-file for SDS EU, Section 9
SDS_1810_EU_09.doc Template document-file for SDS EU, Section 9

INTERNAL: SAP CUSTOMER 339 © SAP SE

 Technical Settings MSDS Templates

SDS_1810_EU_10.dat Template Import-file for SDS EU, Section 10

SDS_1810_EU_10.doc Template document-file for SDS EU, Section 10
SDS_1810_EU_11.dat Template Import-file for SDS EU, Section 11
SDS_1810_EU_11.doc Template document-file for SDS EU, Section 11
SDS_1810_EU_12.dat Template Import-file for SDS EU, Section 12
SDS_1810_EU_12.doc Template document-file for SDS EU, Section 12
SDS_1810_EU_13.dat Template Import-file for SDS EU, Section 13
SDS_1810_EU_13.doc Template document-file for SDS EU, Section 13
SDS_1810_EU_14.dat Template Import-file for SDS EU, Section 14
SDS_1810_EU_14.doc Template document-file for SDS EU, Section 14
SDS_1810_EU_15.dat Template Import-file for SDS EU, Section 15
SDS_1810_EU_15.doc Template document-file for SDS EU, Section 15
SDS_1810_EU_16.dat Template Import-file for SDS EU, Section 16
SDS_1810_EU_16.doc Template document-file for SDS EU, Section 16
SDS_1810_EU_ANNEX.dat Template Import-file for SDS EU, ANNEX
SDS_1810_EU_ANNEX.doc Template document-file for SDS EU, ANNEX
SDS_1810_EU_MAIN.dat Template Import-file for SDS EU
SDS_1810_EU_MAIN.doc Template document-file for SDS EU
SDS_1810_EU_EXT_MAIN.dat Template Import-file for SDS EU_EXT
SDS_1810_EU_EXT_MAIN.doc Template document-file for SDS EU_EXT
SDS_1810_EU_EXT_02_TR.dat Template Import-file for SDS EU_EXT, Section 2 for TR
SDS_1810_EU_EXT_02_TR.doc Template document-file for SDS EU_EXT, Section 2 for
TR
SDS_1810_EU_EXT_02.dat Template Import-file for SDS EU_EXT, Section 2
SDS_1810_EU_EXT_02.doc Template document-file for SDS EU_EXT, Section 2
SDS_1810_EU_EXT_03.dat Template Import-file for SDS EU_EXT, Section 3
SDS_1810_EU_EXT_03.doc Template document-file for SDS EU_EXT, Section 3
SDS_1810_EU_EXT_08.dat Template Import-file for SDS EU_EXT, Section 8
SDS_1810_EU_EXT_08.doc Template document-file for SDS EU_EXT, Section 8
SDS_1810_EU_EXT_12.dat Template Import-file for SDS EU_EXT, Section 12
SDS_1810_EU_EXT_12.doc Template document-file for SDS EU_EXT, Section 12
SDS_1810_EU_EXT_16.dat Template Import-file for SDS EU_EXT, Section 16
SDS_1810_EU_EXT_16.doc Template document-file for SDS EU_EXT, Section 16
SDS_1810_EMEA_MAIN.dat Template Import-file for SDS EMEA
SDS_1810_EMEA_MAIN.doc Template document-file for SDS EMEA
SDS_1810_EU_RTL_01.dat Template Import-file for SDS EU, Section 1
SDS_1810_EU_RTL_01.doc Template document-file for SDS EU, Section 1
SDS_1810_EU_EXT_RTL_02.dat Template Import-file for SDS EU, Section 2
SDS_1810_EU_EXT_RTL_02.doc Template document-file for SDS EU, Section 2

INTERNAL: SAP CUSTOMER 340 © SAP SE

 Technical Settings MSDS Templates

SDS_1810_EU_EXT_RTL_03.dat Template Import-file for SDS EU, Section 3

SDS_1810_EU_EXT_RTL_03.doc Template document-file for SDS EU, Section 3
SDS_1810_EU_RTL_04.dat Template Import-file for SDS EU, Section 4
SDS_1810_EU_RTL_04.doc Template document-file for SDS EU, Section 4
SDS_1810_EU_RTL_05.dat Template Import-file for SDS EU, Section 5
SDS_1810_EU_RTL_05.doc Template document-file for SDS EU, Section 5
SDS_1810_EU_RTL_06.dat Template Import-file for SDS EU, Section 6
SDS_1810_EU_RTL_06.doc Template document-file for SDS EU, Section 6
SDS_1810_EU_RTL_07.dat Template Import-file for SDS EU, Section 7
SDS_1810_EU_RTL_07.doc Template document-file for SDS EU, Section 7
SDS_1810_EU_EXT_RTL_08.dat Template Import-file for SDS EU, Section 8
SDS_1810_EU_EXT_RTL_08.doc Template document-file for SDS EU, Section 8
SDS_1810_EU_RTL_09.dat Template Import-file for SDS EU, Section 9
SDS_1810_EU_RTL_09.doc Template document-file for SDS EU, Section 9
SDS_1810_EU_RTL_10.dat Template Import-file for SDS EU, Section 10
SDS_1810_EU_RTL_10.doc Template document-file for SDS EU, Section 10
SDS_1810_EU_RTL_11.dat Template Import-file for SDS EU, Section 11
SDS_1810_EU_RTL_11.doc Template document-file for SDS EU, Section 11
SDS_1810_EU_RTL_12.dat Template Import-file for SDS EU, Section 12
SDS_1810_EU_RTL_12.doc Template document-file for SDS EU, Section 12
SDS_1810_EU_RTL_13.dat Template Import-file for SDS EU, Section 13
SDS_1810_EU_RTL_13.doc Template document-file for SDS EU, Section 13
SDS_1810_EU_RTL_14.dat Template Import-file for SDS EU, Section 14
SDS_1810_EU_RTL_14.doc Template document-file for SDS EU, Section 14
SDS_1810_EU_RTL_15.dat Template Import-file for SDS EU, Section 15
SDS_1810_EU_RTL_15.doc Template document-file for SDS EU, Section 15
SDS_1810_EU_EXT_RTL_16.dat Template Import-file for SDS EU, Section 16
SDS_1810_EU_EXT_RTL_16.doc Template document-file for SDS EU, Section 16
SDS_1810_EUEXT_RTL_MAIN.dat Template Import-file for SDS EU_EXT
SDS_1810_EUEXT_RTL_MAIN.doc Template document-file for SDS EU_EXT
SDS_1810_EMEA_RTL_MAIN.dat Template Import-file for SDS EMEA
SDS_1810_EMEA_RTL_MAIN.doc Template document-file for SDS EMEA
SDS_1810_EMEA_RTL_02.dat Template Import-file for SDS EMEA RTL, Section 2
SDS_1810_EMEA_RTL_02.doc Template document-file for SDS EMEA RTL, Section 2
SDS_1810_EMEA_RTL_03.dat Template Import-file for SDS EMEA RTL, Section 3
SDS_1810_EMEA_RTL_03.doc Template document-file for SDS EMEA RTL, Section 3
SDS_1810_EMEA_RTL_08.dat Template Import-file for SDS EMEA RTL, Section 8
SDS_1810_EMEA_RTL_08.doc Template document-file for SDS EMEA RTL, Section 8
SDS_1810_EMEA_RTL_11.dat Template Import-file for SDS EMEA RTL, Section 11

INTERNAL: SAP CUSTOMER 341 © SAP SE

 Technical Settings MSDS Templates

SDS_1810_EMEA_RTL_11.doc Template document-file for SDS EMEA RTL, Section 11

SDS_1810_EMEA_RTL_12.dat Template Import-file for SDS EMEA RTL, Section 12
SDS_1810_EMEA_RTL_12.doc Template document-file for SDS EMEA RTL, Section 12
SDS_1810_GHS_02.dat Template Import-file for SDS GHS, Section 2
SDS_1810_GHS_02.doc Template document-file for SDS GHS, Section 2
SDS_1810_GHS_03.dat Template Import-file for SDS GHS, Section 3
SDS_1810_GHS_03.doc Template document-file for SDS GHS, Section 3
SDS_1810_GHS_08.dat Template Import-file for SDS GHS, Section 8
SDS_1810_GHS_08.doc Template document-file for SDS GHS, Section 8
SDS_1810_GHS_11.dat Template Import-file for SDS GHS, Section 11
SDS_1810_GHS_11.doc Template document-file for SDS GHS, Section 11
SDS_1810_GHS_12.dat Template Import-file for SDS GHS, Section 12
SDS_1810_GHS_12.doc Template document-file for SDS GHS, Section 12
SDS_1810_GHS_MAIN.dat Template Import-file for SDS GHS
SDS_1810_GHS_MAIN.doc Template document-file for SDS GHS
SDS_1810_RTL_01.dat Template Import-file for SDS RTL, Section 1
SDS_1810_RTL_01.doc Template document-file for SDS RTL, Section 1
SDS_1810_RTL_02.dat Template Import-file for SDS RTL, Section 2
SDS_1810_RTL_02.doc Template document-file for SDS RTL, Section 2
SDS_1810_RTL_03.dat Template Import-file for SDS RTL, Section 3
SDS_1810_RTL_03.doc Template document-file for SDS RTL, Section 3
SDS_1810_RTL_04.dat Template Import-file for SDS RTL, Section 4
SDS_1810_RTL_04.doc Template document-file for SDS RTL, Section 4
SDS_1810_RTL_05.dat Template Import-file for SDS RTL, Section 5
SDS_1810_RTL_05.doc Template document-file for SDS RTL, Section 5
SDS_1810_RTL_06.dat Template Import-file for SDS RTL, Section 6
SDS_1810_RTL_06.doc Template document-file for SDS RTL, Section 6
SDS_1810_RTL_07.dat Template Import-file for SDS RTL, Section 7
SDS_1810_RTL_07.doc Template document-file for SDS RTL, Section 7
SDS_1810_RTL_08.dat Template Import-file for SDS RTL, Section 8
SDS_1810_RTL_08.doc Template document-file for SDS RTL, Section 8
SDS_1810_RTL_09.dat Template Import-file for SDS RTL, Section 9
SDS_1810_RTL_09.doc Template document-file for SDS RTL, Section 9
SDS_1810_RTL_10.dat Template Import-file for SDS RTL, Section 10
SDS_1810_RTL_10.doc Template document-file for SDS RTL, Section 10
SDS_1810_RTL_11.dat Template Import-file for SDS RTL, Section 11
SDS_1810_RTL_11.doc Template document-file for SDS RTL, Section 11
SDS_1810_RTL_12.dat Template Import-file for SDS RTL, Section 12
SDS_1810_RTL_12.doc Template document-file for SDS RTL, Section 12

INTERNAL: SAP CUSTOMER 342 © SAP SE

 Technical Settings MSDS Templates

SDS_1810_RTL_13.dat Template Import-file for SDS RTL, Section 13

SDS_1810_RTL_13.doc Template document-file for SDS RTL, Section 13
SDS_1810_RTL_14.dat Template Import-file for SDS RTL, Section 14
SDS_1810_RTL_14.doc Template document-file for SDS RTL, Section 14
SDS_1810_RTL_15.dat Template Import-file for SDS RTL, Section 15
SDS_1810_RTL_15.doc Template document-file for SDS RTL, Section 15
SDS_1810_RTL_16.dat Template Import-file for SDS RTL, Section 16
SDS_1810_RTL_16.doc Template document-file for SDS RTL, Section 16
SDS_1810_RTL_MAIN.dat Template Import-file for SDS GHS RTL
SDS_1810_RTL_MAIN.doc Template document-file for SDS GHS RTL

F.1.2. Other Settings

Display of Component Names
For the display of component names, in particular in connection with the Trade Secret Func-
tionality, there is customizing necessary. An explanation including a default setup suggestion
for necessary ID listings D_TSIDLID and D_NTSIDLID is summarized in section A.60How to
disclose component names. For further details please see also SAP Note 1576098.

Additionally, please maintain following ID Listings: ZISIEU1050, ZISIEU1051, D_ESC_SUB,

D_ESC_EC

We suggest to maintain them as follows:

IDListing ZISIEU1050
IDList SDS EU Identifiers
IDListPos 1 1 1 1 1
IDListPrio 1 2 3 4 5
IDCategory NAM NAM NAM NAM NAM
IDType RCS ANNEXI IUPAC CAS SYN

IDListing ZISIEU1051
IDList SDS EU Identifiers
IDListPos 1
IDListPrio 1
IDCategory NUM
IDType CAS

IDListing D_ESC_SUB
IDList Substance Name for ESCom
IDListPos 1 1 1
IDListPrio 1 2 3
IDCategory NAM NAM NAM

INTERNAL: SAP CUSTOMER 343 © SAP SE

 Technical Settings MSDS Templates

IDType IUCLID SYN ANNEXI

IDListing D_ESC_EC
IDList EC Number for ESCom
IDListPos 1 1 1 1
IDListPrio 1 2 3 4
IDCategory NUM NUM NUM NUM
IDType EC EINECS ELINCS NLP

Annex to European eSDS (ESCom)

The WWI template for the annex to the European eSDS was completely remodeled with ERC
2015-2 in order to reflect the ESComXML Format V2.0 as published by CEFIC.

EHS properties and characteristics, phrases and phrase-sets as well as the template have
been adapted requiring a new data maintenance after ERC 2015-1 for a proper output of the
eSDS. Details can be found in the documentation (SDS_XXXX_EU_Specification.pdf, where
XXXX is the current release).

Note that the adaptation to the ESComXML Format V2.0 that is being introduced with ERC
2015-2 refers only to the content (ERC) and apart from the EHS standard properties not to
the EHS system itself, i.e. the import and export of xml-files to and from EHS as well as data
migration from old properties to the new properties and characteristics is not in scope for SAP
EHS Regulatory Content and therefore not covered by this document.

General information on the Exposure Scenario Management can be found in the SAP applica-
tion help (http://help.sap.com/) for Exposure Scenario Management (EHS-SAF-ESM). Partic-
ularly helpful in connection to the template will also be the “Structure of Exposure Scenarios”.

The use of the European WWI templates for the eSDS requires several prerequisites:

• SAP Note 2052892 - Solution package: Output exposure scenarios on EU safety data
sheets. An important prerequisite hereby is to assure that the user exits MIC_REG_ST,
ES_CS_INCL, and SUB_FOR_ES as well as the report symbols E_ES_STAT1,
E_ES_STAT2, E_ES_FILT, and the environment parameters E_ES_STAT1_COMPARE and
E_ES_STAT2_COMPARE are created/available on the EHS system as described in the SAP
Note.
• The identification types ES_UUID, ES_DT_STMP, and CS_UUID (Identification Cat. NUM)
are needed because they are used within the WWI template. Make sure these Identification
types are available in the EHS system. See also IMG activity Environment, Health and Safety
- -> Basic Data and Tools - -> Specification Management - -> Specification Master - -> Check
Identification Types. Within SAP ERP 6.0 EhP 7 these identification types are available by
default.
• The identification listings D_ESC_SUB and D_ESC_EC need to be available. For the default
settings please refer to the tables above.
• By default, it is recommended to set phrase keys for the two environment parameters
E_ES_STAT1_COMPARE and E_ES_STAT2_COMPARE, e.g. CUST-H02.00100034 and
CUST-H01.00400017, respectively. This avoids warning messages during report genera-
tion for system configurations that allow detailed error analysis, e.g. when the environment
parameter REPORT_GENERATION_PROTOCOL is set to "X". Details on the functionality
around the two aforementioned environment parameters can be found in the SDS Template
Documentation.

INTERNAL: SAP CUSTOMER 344 © SAP SE

 Technical Settings MSDS Templates

The data maintenance concept is explained in the SDS template documentation. Note that
the ESCom phrases are technically provided as a separate phrase group (ESCOM) based on
ESCom Phrase Catalogue V2.0 by CEFIC. Updates to this separate phrase group are sched-
uled in line with officially published new versions of the ESCom Phrase Catalogue. Desired
changes have therefore to be addressed directly to the ESCom phrases group.

F.1.3. Generation variant

Several parameters are necessary for the setup of Report Generation variants such as Tem-
plate Version, Validity Area, Date and Decimal Format. A recommendation of parameters for
supported countries is listed in the additional document RGV_1810 _Configuration.pdf.

INTERNAL: SAP CUSTOMER 345 © SAP SE

Index General Information, 98
GHS, 262
Customizing, 266
History.mdb, 224 Expert admin settings, 263
File overview, 262
A User exit settings, 265
Analysis Tool for Excel, 84 Implementation, 98
MSDSMaker, 334
B Customizing, 336
BC sets Expert admin settings, 335
Import, 141 File overview, 334
User exit settings, 336
Registration, 122, 215
C RegStat
Cache, OCC, Mapping Database, 93
Customizing, 330
check list, 128
Expert admin settings, 327
Checklist, 128
File overview, 326, 326
Component name
User exit settings, 329
Disclosure, 227
Expert Server, 98
Console program, 108, 206
Configuration, 104
(see also Expert Server)
CGSADM, 104
Customizing, 109
EHS Service Administration, 104, 202
Microsoft Windows services, 106
D Installation, 99
Dangerous Goods Master Data, 65, 177 Expert Sub Rules
Substance lists and reference data, 62 Basis
Data Origin, 55, 116, 116, 174 Expert admin settings, 258
OCC, 54 DangGoods
Database, XML files, 80, 80, 80, 181 Expert admin settings, 332
Europe
E Expert admin settings, 297
Expert Rule sets, 120 GHS
Execution, 124 Expert admin settings, 264
Installation, 121 MSDSMaker
Installation with SAP Setup, 120 Expert admin settings, 335
Prerequisites, 98 RegStat
Expert Rules, 98 Expert admin settings, 328
Basis, 256 Explanation component, 128, 193, 217
Customizing, 261 External table
Expert admin settings, 257 Adjustment, 124, 223
File overview, 256 Mapping
User exit settings, 259 Facts, 91, 125, 191
DangGoods, 331 Groups, 126, 224
Customizing, 334 Phrases, 92, 127, 192
Expert admin settings, 331 Records, 92, 126, 192
File overview, 331
User exit settings, 333 F
Europe, 268
Files
Customizing, 324
Upload, 30, 73, 134
Expert admin settings, 286
File overview, 268
User exit settings, 298 G
File overview, 98 Generation Variants

INTERNAL: SAP CUSTOMER 346 © SAP SE

 Index

Creation, 135, 136, 226 Registry instance, 85, 186

RFC connection, 43
H SAP Note, 40
Hit List Schematic Diagram, 40
Update functionality, 72 User Exit, 88, 189

I P
Identification listings Phrase catalogue, 29, 56, 152
Setup, 133, 133, 225 CED, 29
Identifier types, 60, 176 Substance lists and reference data, 55
Substance lists and reference data, 60 Phrase sets, 14
Import, 132 Allocation, 14, 142
Merge, 32, 76, 156 Phrase set assignment, 34, 78, 158
Phrases, cg31, 31, 74, 154 Phrase Variants
Report templates, 135, 226 Creation, 162
Transport, stms, 12, 132, 139 Phrases, 26
Appendix, 239
L Check Implementation, 37
Language keys Checklist, 37
Implementation, 153 Combine/Retire, 160
Literature source, 59, 116, 175 File overview, 29
Expert Rules, 116 General Information, 26
Substance lists and reference data, 59 General Settings, 240
Log files, Exp-log, RFC-log, 220 Language keys, 246
Language/Codepages, 244
M Name spaces, 241
Mapping database Phrase groups, 240
Cache, 82, 183 Implementation, 29
MS Access, 81 Import, 31, 74
Setup, 82 Individual changes, 36, 37
MSDS Report Template, 130, 131, 132 Language/Codepage/Font, 27
EU Prerequisites, 26
File Overview, 337 Proposal, 28
Europe, 337 Standard, 239
Customizing, 343 File Overview, 239
Generation variant, 345 Structure, 26
General Information, 130 Substance lists and reference data, 73
Implementation, 132, 137 Property Tree, 9
Checklist, 137 Check Implementation, 24
Import, 135 Checklist, 24
Prerequisites, 130 File Overview, 10
Multi Rule Call, 115 File overview, 234
General Information, 9
N Implementation, 10
Number ranges, 56, 153 Package overview, 235
Prerequisites, 9
O
OCC, 41, 41 R
Download, 42 Regulatory Data, 39
Filter, Regulatory List, 94 Check Implementation, 95
Installation, 42, 162 Checklist, 95, 96, 96
Open Content Connector, 42 Dangerous Goods, 251, 255

INTERNAL: SAP CUSTOMER 347 © SAP SE

 Index

Customizing, 255 V
File overview, 251, 255 Validity area, 67, 71, 179
User exit settings, 254 Value Assignment Rating, 119, 120, 206
File overview, 41
Implementation, 41 W
Product Safety, 249
Windows Service, EHS Expert Server, 107,
Customizing, 251
204
User exit settings, 250
WWI Symbol, 17
ProductSafety
Generation, 17, 145
File Overview, 249
Regulatory lists, 58, 118, 175
Expert Rules, 117
Substance lists and reference data, 58
RFC connection, 43, 43, 99, 99, 163
Expert Rules, 99
Test, 46, 103, 166

S
SAP Setup Tool, 207
SAPRFC.INI, 106, 202
Secondary data, 216
Setup, EHS Expert, 199
Simulation Tool, 84, 185
Substance lists and reference data
Adjustment, 85
Mapping, 90
OCC, 85
User exit, 88
General Information, 39
Update, simulation, hit list, 193

T
Table Based Value Assignment, 18, 18, 146
Templates, 23
Property tree, 24, 152
Transports (see Import)

U
Upload files
Expert rules, EHS Expert server, 121, 213
Phrases, 30, 74, 134, 139
Property tree, 11, 138
UPO, 218
User Defined Dangerous Goods Texts, 119,
206
Expert Rules, 119
User Defined Text Types, 57, 117, 117, 174
OCCUNQID, NOL, Free text, 57
User Exit, 47, 173
Expert Rules, 109
Explanation component, 48, 109, 167
Search functionality, 181

INTERNAL: SAP CUSTOMER 348 © SAP SE