SAP EHS Regulatory Content Update Guide

SAP EHS Regulatory
Content Update Guide
SAP EHS Regulatory Content Update Guide

Version 2011-1
Published May 2011
Copyright 2011 SAP AG, Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany
The content of this document is the intellectual property of SAP AG. Any forwarding to third parties or publication even of parts
thereof requires express and written approval by SAP AG.
1. Introduction ....................................................................................................................... 1
1.1. Objective ................................................................................................................ 1
1.2. How to use this guidance document ..................................................................... 1
1.2.1. Structure of this manual .............................................................................. 1
1.3. Security/Authorization ............................................................................................ 2
1.4. Support options ..................................................................................................... 2
1.4.1. Customer Helpdesk .................................................................................... 2
2. Update .............................................................................................................................. 3
2.1. Update Prerequisites ............................................................................................. 3
2.2. Update overall procedure ...................................................................................... 4
3. Property Tree ................................................................................................................... 5
3.1. Check Update ........................................................................................................ 5
3.1.1. Checking Procedure ................................................................................... 5
3.1.2. Settings to implement the last SAP EHS Management Property Tree
Package Product Safety ....................................................................................... 5
4. SAP EHS Regulatory Content - multilanguage phrase library for hazard communication ........................................................................................................................................ 6
4.1. Check Update ........................................................................................................ 6
4.1.1. Checking Procedure ................................................................................... 6
4.1.2. Settings to implement the Multilanguage Phrase Library (Standard) ........... 6
4.1.2.1. File Overview ................................................................................... 6
4.1.3. Settings to implement the Multilanguage Phrase Library (APA) .................. 8
4.1.3.1. File Overview ................................................................................... 8
4.1.4. General Settings ......................................................................................... 9
4.1.4.1. Language/Codepages ...................................................................... 9
4.1.4.2. Language keys ................................................................................. 9
5. SAP EHS Regulatory Content - substance lists and reference data .............................. 10
5.1. Check Update ...................................................................................................... 10
5.1.1. Check List Update Product Safety ............................................................ 10
5.1.2. Settings to update the Substance Lists and Reference Data (Product
Safety) ................................................................................................................. 11
5.1.2.1. File Overview ................................................................................. 11
5.1.2.2. Other Settings ................................................................................ 12
5.1.3. Check List Update Dangerous Goods ...................................................... 16
5.1.4. Settings to update the CLEO regulatory data (Dangerous Goods) ............ 17
5.1.4.1. File Overview ................................................................................. 17
5.1.4.2. Other Settings ................................................................................ 18
6. SAP EHS Regulatory Content - expert rules for substance and mixture classification
.............................................................................................................................................. 20
6.1. Check Update ...................................................................................................... 20
6.1.1. Check List ................................................................................................. 20
6.1.2. Settings to update the licenced rule set package(s) ................................. 21
6.1.2.1. Settings in Admin Tool ................................................................... 21
6.1.2.2. Settings in Admin Tool - Sub Rules ............................................... 32
6.1.2.3. User Exit Settings .......................................................................... 34
6.1.2.4. Other Settings ................................................................................ 36
6.1.3. Settings to update the basis rule set package .......................................... 36
6.1.3.1. File Overview ................................................................................. 36
6.1.3.4. Other Settings ................................................................................ 37
6.1.4. Settings to update the rule set package for GHS ..................................... 37
iii
SAP AG

6.1.4.1. File Overview ................................................................................. 37
6.1.4.5. Other Settings ................................................................................ 40
6.1.5. Settings to update the rule set package for APA ...................................... 40
6.1.5.1. File Overview ................................................................................. 40
6.1.5.5. Other Settings ................................................................................ 52
6.1.6. Settings to update the rule set package Europe ....................................... 52
6.1.6.1. File Overview ................................................................................. 52
6.1.6.5. Other Settings ................................................................................ 56
6.1.7. Settings to update the rule set package DPDplus .................................... 56
6.1.7.1. File Overview ................................................................................. 56
6.1.7.5. Other Settings ................................................................................ 58
6.1.8. Settings to update the rule set package for National Regulations EU........ 58
6.1.8.1. File Overview ................................................................................. 58
6.1.8.5. Other Settings ................................................................................ 66
6.1.9. Settings to update the rule set package for NA ........................................ 66
6.1.9.1. File Overview ................................................................................. 66
6.1.9.5. Other Settings ................................................................................ 76
6.1.10. Settings to update the RegStat rule set package .................................... 76
6.1.10.1. File Overview ............................................................................... 76
6.1.10.2. Settings in Admin Tool ................................................................. 77
6.1.10.3. Settings in Admin Tool - Sub Rules ............................................. 77
6.1.10.4. User Exit Settings ........................................................................ 78
6.1.10.5. Other Settings .............................................................................. 78
6.1.11. Settings to update the DangGoods rule set package .............................. 78
6.1.11.1. File Overview ............................................................................... 78
6.1.11.5. Other Settings .............................................................................. 81
6.1.12. Settings to update the MSDSMaker rule set package ............................. 81
6.1.12.1. File Overview ............................................................................... 81
iv
SAP AG

6.1.12.5. Other Settings .............................................................................. 82
7. MSDS Templates ........................................................................................................... 83
7.1. Check Update ...................................................................................................... 83
7.1.1. Checking Procedure ................................................................................. 83
7.1.2. Settings to update the MSDS Templates for APJ ..................................... 83
7.1.2.1. File Overview ................................................................................. 83
7.1.2.2. Other Settings ................................................................................ 85
7.1.3. Settings to update the MSDS Template for EMEA ................................... 85
7.1.3.1. File Overview ................................................................................. 85
7.1.3.2. Other Settings ................................................................................ 86
7.1.4. Settings to update the MSDS Template for GHS ...................................... 86
7.1.4.1. File Overview ................................................................................. 86
7.1.4.2. Other Settings ................................................................................ 86
7.1.5. Settings to update the MSDS Templates for the Americas ....................... 86
7.1.5.1. File Overview ................................................................................. 86
7.1.5.2. Other Settings ................................................................................ 87
A. How To ... ....................................................................................................................... 88
A.1. How to upload property tree transports files ....................................................... 88
A.2. How to upload files ............................................................................................. 88
A.3. How to import transports (customizing or workbench) ........................................ 89
A.4. How to allocate phrase sets ................................................................................ 91
A.5. How to create WWI report symbols .................................................................... 93
A.6. How to set up the Table-based Value Assignment ............................................. 94
A.7. How to import phrases ........................................................................................ 99
A.8. How to merge phrases ...................................................................................... 101
A.9. How to import phrase set assignments ............................................................. 103
A.10. How to combine/retire phrases ....................................................................... 105
A.10.1. Combining Duplicate Phrases .............................................................. 105
A.10.2. Retired Phrases .................................................................................... 106
A.11. How to install EHS OCC ................................................................................. 107
A.11.1. Initial Installation/Upgrading of older OCC versions .............................. 107
A.12. How to extend entry in secondary data determination .................................... 107
A.13. How to manage user exits .............................................................................. 113
A.14. How to add user defined text types ................................................................ 114
A.15. How to add data origins .................................................................................. 114
A.16. How to add regulatory lists ............................................................................. 114
A.17. How to add literature sources ......................................................................... 115
A.18. How to add identifier types ............................................................................. 116
A.19. How to add dangerous goods master data ..................................................... 117
A.19.1. Dangerous Goods Classes and Classification Codes ........................... 117
A.19.2. Risk Potentials ...................................................................................... 118
A.19.3. Hazard Identification Numbers ............................................................. 118
A.19.4. Danger Labels ...................................................................................... 118
A.19.5. Packing Instruction Numbers ................................................................ 118
A.19.6. Categories of Instructions for Enclosure and Instructions for Enclosure
............................................................................................................................ 119
A.19.7. Packing Codes ..................................................................................... 119
A.20. How to add validity areas ................................................................................ 119
A.21. How to setup/update XML substance database for substance lists and reference data .................................................................................................................. 121
A.22. How to setup/update mapping database for SAP EHS Regulatory Content substance lists and reference data ........................................................................... 122
SAP AG

A.23. How to configure EHS OCC ...........................................................................
A.24. How to adjust the Fact Mapping .....................................................................
A.25. How to adjust the Record Mapping .................................................................
A.26. How to adjust the Phrase Mapping .................................................................
A.27. SAP EHS Regulatory Content - substance lists and reference data (Product
Safety) Update Data Load ........................................................................................
A.27.1. Review Regulatory Changes ................................................................
A.27.2. Update Cached Data ............................................................................
A.27.3. Review New Filter Settings ..................................................................
A.27.4. Hit List of List Substances ....................................................................
A.27.5. Simulate Data Load ..............................................................................
A.27.6. Analyze Changed Data .........................................................................
A.27.7. Load Changes to SAP EH&S ...............................................................
A.27.7.1. Manual update load ...................................................................
A.27.7.2. Mass Load / Autoload ................................................................
A.28. SAP EHS Regulatory Content - substance lists and reference data (Dangerous Goods) Update Data Load .................................................................................
A.28.1. Review Regulatory Changes ................................................................
A.28.2. Update Cached Data ............................................................................
A.28.3. Review New Filter Settings ..................................................................
A.28.4. Analyze Changed Data .........................................................................
A.28.5. Load Changes to SAP EH&S ...............................................................
A.28.5.1. Manual update load ...................................................................
A.28.5.2. Mass Load / Autoload ................................................................
A.29. How to add user-defined DG texts ..................................................................
A.30. How to add a value assignment rating ............................................................
A.31. How to load rule sets onto the Expert server ..................................................
A.32. How to register rule sets .................................................................................
A.33. How to adjust external table values ................................................................
A.34. How to adjust the Group Mapping ..................................................................
A.35. How to use the History.mdb ............................................................................
A.36. How to setup identification listings ..................................................................
A.37. How to import report templates .......................................................................
A.38. How to create generation variant ....................................................................
vi
124
127
128
128
129
129
129
130
130
132
133
134
135
135
136
136
136
136
136
137
137
138
138
139
139
140
142
143
143
144
145
145
SAP AG
Chapter 1. Introduction
1.1. Objective
This SAP EHS Regulatory Content Update Guide comprises all relevant steps and guidelines
for update of the SAP EHS Regulatory Content content products (phrases, regulatory data,
Expert rules, MSDS-templates) in SAP EHS. Appropriate related How Tos are included to
facilitate the update procedure. Information for all relevant update steps is provided.
This manual does not replace release notes or functional descriptions for the individual content
products. Release notes are provided for each new version of the individual product to give
an overview over new and changed features. Functional descriptions are provided for each
individual product as detailed documentation on all functions and settings.
This manual describes all available SAP EHS Regulatory Content products. These products
need to be licensed. The manual may describe products that are not licensed by your company
and thus not delivered to your company. If you would like to check your SAP EHS Regulatory
Content license status, please contact SAP.
1.2. How to use this guidance document

This guide is intended as a quick update for the experienced SAP EHS user to implement
a SAP EHS Regulatory Content update. It is not intended to replace the SAP Administration
Manual.
If you are not familiar with SAP EHS Regulatory Content we recommend to use the SAP Administration manual as a step by step documentation of how to implement SAP EHS Regulatory Content.
User of the printed version should refer to the table of contents to find the information they
need. The links which are embedded in the PDF file could be used if this document is viewed
on the computer.
The following chapter Structure of this manual gives an overview over the structure of this
manual.
1.2.1. Structure of this manual

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

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

Our customer helpdesk http://support.technidata.de allows you to ask your questions and report your problems 24 hours a day. This offers you an easy possibility to contact SAP if any
problems occur with SAP products. Your issues are forwarded automatically to the appropriate contact person. Automatic feedback e-mails inform you about the status of your issues or
alternatively you can actively follow the status yourself.
You can report different types of issues, such as bugs, questions or requests for new features
or improvements and address them to the CSM-CLEO Data, Rules and Services project.
The customer helpdesk also provides the opportunity to bring in suggestions and requests for
further development of SAP EHS Regulatory Content.
For
questions
about
online
access
or
available
services
please
address
to:
<OD_LoB_CaaS_Helpdesk@sap.com>.
SAP AG
Chapter 2. Update
This chapter describes the prerequisites which are necessary to update your SAP EHS Regulatory Content.
2.1. Update Prerequisites

This chapter describes the overall prerequisites in order to update 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
EHS Expert/OCC
Current version of EHS Open Content Connector (OCC) and EHS Expert (see SAP note
586302).
EHS WWI
Current version of WWI
Starting with the 2010-1 Release, the Material safety data sheet (MSDS) templates will use
function modules located in the /TDAG/-namespace instead of utilizing the Z-namespace
( ZISI...). Therefore it is necessary to create the /TDAG/-namespace on a customer system,
before importing the workbench transport with the actual function modules in the /TDAG/namespace.
Please see section "File overview" to find details on the namespace transport.
Customizing
SAP authorisation
Front-end computer for data load
SAP Notes
SAP Note
Remark
568302
See for information how to download the latest version of OCC and additional system requirements.
1061242
EH&S: Availability and performance of WWI and Expert servers
1408534
Import of phrases terminates with a runtime error
1418024
Incomplete long text when you merge phrases
1299868
EH&S Expert/EH&S OCC Unicode support
SAP AG
Update
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
1105036
Output of Tunnelcode on Reports
1146663
Placeholder-Functionality for Phrases
1279191
Missing DG Symbol for Marine Pollutant
1265493
Evaluation and Output of Environmentally Hazardous
1368217
Output of Environmentally Hazardous on Reports
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. Update overall procedure

This document provides information and instructions for the SAP EHS Regulatory Content
update procedure.
The graph shows the sequence of the update.
Detailed information which steps are necessary to update your 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 update procedure please review the enclosed documentation.
Caution
It might be necessary to upgrade your installation of OCC/Expert or to update your
EHS or to implement SAP notes.
Tip
Collect all transports contained in the update. If you upload all transports at once you
can skip the appropriate upload activities mentioned in the check lists.
SAP AG
Chapter 3. Property Tree

3.1. Check Update
The following steps describe how to check the update of Property Trees.
3.1.1. Checking Procedure

Please use the following check list as guidance through the property tree update procedure.
Status
Where to do
What to do
General
O
Review documentation
Technical Part
O
SAP EHS (cg3z)
Upload files
SAP EHS (stms)
Import transports
SAP EHS (cg1b)
Create phrase sets
SAP EHS (cgcz)
Match up master data
SAP EHS (cgab)
Assign phrase sets to characteristics
SAP EHS (cgcz)
Activate phrase set assignment to characteristic
SAP EHS (cgcz)
Create WWI symbols
Customizing (spro)
Update table based value assignment
Detailed information on how to execute the single steps will be provided in this How-To-documents:
Section A.1, How to upload property tree transports files

Section A.4, How to allocate phrase sets
Section A.5, How to create WWI report symbols
Section A.6, How to set up the Table-based Value Assignment
3.1.2. Settings to implement the last SAP EHS Management

Property Tree Package Product Safety
No property tree package is delivered with the 2011-1 update. Therefore, no transports have
to be installed if the property tree STANDARD is up to date, that is if ERP 6.0 EHP6 or all
packages up to 2010-2 were installed.
SAP AG
Chapter 4. SAP EHS Regulatory

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

Please use the following check list as guidance through the phrase library update procedure.
Status
Where to do
What to do
General
O
Technical Part
O
Customizing (spro)
Specify Language Selection
SAP EHS (cg3z)
Upload phrases
Upload phrase set assignments
SAP EHS (cg31)
Import phrases
SAP EHS (cg31)
Import phrase corrections
SAP EHS (cg12)
Merge phrases
SAP EHS (cg31)
Import phrase set assignments
Section A.2, How to upload files

Section A.7, How to import phrases
Section A.8, How to merge phrases
Section A.9, How to import phrase set assignments
Section A.10, How to combine/retire phrases
4.1.2. Settings to implement the Multilanguage Phrase Library (Standard)

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

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

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

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

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

customer correspondence language
ced_2011-1_usenglish_Z8_
update.dat

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

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

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

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

The following files are included in the delivery (additional set of files for Unix application servers
containing appendix "_unix" in the filename also included). We recommend to use the Unicode
files when possible to avoid character conversion errors with the non-Unicode files.
Asia Pacific
File name
Description
01_documents
CED_ReleaseNote_2011-1.pdf
Release Note for current version
CED_Changes_2011-1.xls
Excel file with complete scope of EN phrases in previous and current version for a quick information what has
changed in the latest release; table 2 contains obsolete
pset assignments that should be deleted
Phrase_Services_Proposals.xls
Proposal template for customer suggestions
02_phrases_windows / 03_phrases_unix
ced_2011-1_ap_unicode_complete.dat
Phrase
import file including all phrases in all AP languages for fast processing in Unicode systems
ced_2011-1_ap_unicode_update.dat

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

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

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

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

4.1.4.1. Language/Codepages
The following settings have to be enhanced/changed for this update:
No additional languages have been added with this release.
4.1.4.2. Language keys

The following settings have to be enhanced/changed for this update:
No additional languages have been added with this release.
SAP AG

Content - substance lists and
reference data
5.1. Check Update
The following steps describe how to check the update of substance and reference data and is
divided into subsections for Product Safety and Dangerous Goods.
5.1.1. Check List Update Product Safety

Please use the following check list as guidance through the update procedure of substance
lists and reference data.
Status
Where to do
What to do
Documentation
General
O
Technical Part
O
Frontend
Upgrade installation of Open Content Connector
SAP EHS (cg3z)
Upload customizing transports

Upload phrases
SAP EHS (cg3z)
Upload phrases
SAP EHS (stms)
Import customizing transports
SAP EHS (cg31)
Import substance lists and reference data phrase library
SAP EHS (cg12)
Merge phrases to active catalogue
SAP EHS (cg31)
Import phrase sets
XML File storage (local, Update database XML files using the database setup
network drive)
file
td_cleo.mdb
Update mapping database

Identify and consider customer made changes for the
updated mapping database
Regulatory Part / Data Load

O
Documentation
Review regulatory changes
SAP EHS / OCC
Update cached data
SAP EHS / OCC
Review new filter settings
SAP EHS (cg12)
Generate hit list of changed list substances
SAP EHS (cg12)
Generate hit list of list substances with new group assignments
SAP EHS / OCC
Simulate data load
MS Excel
Analyze new & changed data
10
SAP AG
SAP EHS Regulatory Content - substance lists and reference data

O
SAP EHS / OCC
Load changes to SAP EHS
Detailed information on how to execute the single steps will be provided by following the links
in the check list above or in the How-To-documents listed below:
Section A.11, How to install EHS OCC

Section A.3, How to import transports (customizing or workbench)
Section A.21, How to setup/update XML substance database for substance lists and reference data
Section A.22, How to setup/update mapping database for SAP EHS Regulatory Content substance lists and reference data
Section A.24, How to adjust the Fact Mapping
Section A.25, How to adjust the Record Mapping
Section A.26, How to adjust the Phrase Mapping
Section A.27, SAP EHS Regulatory Content - substance lists and reference data (Product
Safety) Update Data Load
5.1.2. Settings to update the Substance Lists and Reference

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

Note for Product Safety
CLEO_ContentReport_AP.pdf
Content Report Asia-Pacific Data
CLEO_ContentReport_EU.pdf
Content Report European Data
CLEO_ContentReport_Americas.pdf
Content Report American Data
CLEO_ContentReport_
Inventories.pdf
Content Report Inventories Data
CLEO_PS_Training_EN.ppt
SAP EHS Regulatory Content Training Workshop Presentation
1-OCC
Info file on how to obtain OCC
readme.txt
2-Customizing
R900542.TD8
and K900542.TD8
Customizing transport with additional regulatory lists

and sources (Unicode)
R902760.TD4
and K902760.TD4
Customizing transport with additional regulatory lists

and sources (Non-Unicode)
R900548.TD8
and K900548.TD8
Customizing transport with additional validity areas

(Unicode)
11
SAP AG

Files
R902762.TD4
and K902762.TD4
customizing_overview.txt
File Description
Customizing transport with additional validity areas
(Non-Unicode)
Overview of customizing entries
3-Phrases\Unicode_Unix / 3-Phrases\Unicode_Win
cleo_2011-1_unicode.dat
Unicode phrase import file (all languages, except those

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

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

group assignments
5.1.2.2. Other Settings
12
SAP AG

The following customizing settings have to be added or changed for this update:
Note
Create new Regulatory Lists
Create new Sources
Add new Validity Areas
Customizing Transport TD8K900542 (Unicode) for Reg. Lists and
Sources
Customizing Transport TD4K902760 (Non-Unicode) for Reg. Lists
and Sources
Customizing Transport TD8K900548 (Unicode) for Validity Areas
Customizing Transport TD4K902762 (Non-Unicode) for Validity Areas
This installation package includes customizing transports that can be imported to create all
necessary customizing entries.
Alternatively, all customizing entries can be done manually according to the tables below.
Additional Regulatory Lists
Value of the parameter
Description
ZAR_BEI
Argentina. Biological Exposure Indices
ZBE_BEI
Belgium. BEI values
ZBR_BEI
Brazil. NR7. Parameters for Biological Control

of Occupational Exposure to Some Chemical
Agents
ZCH_BAT
Switzerland. List of BAT-values.
ZDK_BEI
Denmark. Biological limit values
ZES_BEI
Spain. Biological Exposure Values
ZFI_BEI
Finland. Biological limit values
ZGB_BMGV
UK. Biological monitoring guidance values
ZHU_BEI
Hungary. Permissible limit values of biological

exposure (effect) indices
ZIT_BEI
Italy. Biological Exposure Limits
ZLU_BEI
Luxembourg. Biological Exposures
ZLV_BEI
Latvia. Biological Exposure Indices
ZMT_BEI
Malta. Biological Exposure Limits
ZNZ_BEI
New Zealand. Biological Exposure Indices
ZRO_BEI
Romania. Biological limit values
ZRS_BEI
Serbia. Binding Biological Limit Values and

Health Surveillance Measures
13
SAP AG

ZSG_BEI
Singapore. Biological Threshold Limit Values
ZSI_BAT
Slovenia. BAT-values
ZSK_BEI
Slovakia. Biological Limit Values
ZTR_BEI
Turkey. Binding biological limit values and

health surveillance measures
ZCN_HW
China. National Catalogue of Hazardous

Wastes
ZKR_GHSMOE
Korean GHS based classification (MOE)
ZIN_OEL
India. Permissible levels of certain chemical

substances in work environment.
ZCY_OEL
Cyprus. Occupational Exposure Limits
ZIS_OEL
Iceland. Regulation on occupational exposure

limits.
ZMK_OEL
Macedonia. Occupational Exposure Limits
ZMT_OEL
Malta. Occupational Exposure Limits
ZRS_OEL
Serbia. Occupational Exposure Limits
ZPH_PCL
Philippines. Priority Chemical List.
-> Environment, Health &Safety -> Basic Data and Tools -> Specification Management
-> Specification Master -> Specify Regulatory Lists
OR transaction: S_SH8_72000974 - Specify Regulatory Lists
Section A.16, How to add regulatory lists
Additional Sources
Description
ZAR_BEI
Argentina. Biological Exposure Indices
ZBE_BEI
Belgium. BEI values
ZBR_BEI
Brazil. NR7. Parameters for Biological Control

of Occupational Exposure to Some Chemical
Agents
ZCH_BAT
Switzerland. List of BAT-values.
ZDK_BEI
Denmark. Biological limit values
ZES_BEI
Spain. Biological Exposure Values
ZFI_BEI
Finland. Biological limit values
ZGB_BMGV
UK. Biological monitoring guidance values
ZHU_BEI
Hungary. Permissible limit values of biological

exposure (effect) indices
ZIT_BEI
Italy. Biological Exposure Limits
ZLU_BEI
Luxembourg. Biological Exposures
ZLV_BEI
Latvia. Biological Exposure Indices
ZMT_BEI
Malta. Biological Exposure Limits
14
SAP AG

ZNZ_BEI
New Zealand. Biological Exposure Indices
ZRO_BEI
Romania. Biological limit values
ZRS_BEI
Serbia. Binding Biological Limit Values and

Health Surveillance Measures
ZSG_BEI
Singapore. Biological Threshold Limit Values
ZSI_BAT
Slovenia. BAT-values
ZSK_BEI
Slovakia. Biological Limit Values
ZTR_BEI
Turkey. Binding biological limit values and

health surveillance measures
ZCN_HW
China. National Catalogue of Hazardous

Wastes
ZKR_GHSMOE
Korean GHS based classification (MOE)
ZIN_OEL
India. Permissible levels of certain chemical

substances in work environment.
ZCY_OEL
Cyprus. Occupational Exposure Limits
ZIS_OEL
Iceland. Regulation on occupational exposure

limits.
ZMK_OEL
Macedonia. Occupational Exposure Limits
ZMT_OEL
Malta. Occupational Exposure Limits
ZRS_OEL
Serbia. Occupational Exposure Limits
ZPH_PCL
Philippines. Priority Chemical List.
-> Environment, Health &Safety -> Basic Data and Tools -> Specification Management > Additional Information for Value Assignment -> Specify Sources
OR transaction: S_SH8_72000953 - Specify Sources
Section A.17, How to add literature sources
Additional Validity Areas
Note
Please see also SAP Note 603152 - Country Codes for Serbia and
Montenegro
VAreaCat
Val. area
Descr. for validity area
REGION
CY
Cyprus
REGION
IN
India
REGION
MK
Macedonia
REGION
RS
Serbia
REGION
VE
Venezuela
-> Environment, Health and Safety -> Basic Data and Tools -> Additional Information for
Value Assignment -> Usage -> Specify Validity Areas
15
SAP AG

Section A.20, How to add validity areas
5.1.3. Check List Update Dangerous Goods

Please use the following check list as guidance through the update procedure of substance
lists and reference data for dangerous goods.
Dangerous Goods with Packaging Data

Status
Where to do
What to do
Documentation
General
O
Technical Part
O
Frontend
Upgrade installation of Open Content Connector
SAP EHS (cg3z)
Upload phrases
SAP EHS (cg31)
Import substance lists and reference data phrase library

for dangerous goods
SAP EHS (cg12)
Merge phrases to active catalogue
SAP EHS (cg31)
Import phrase sets
XML File storage (local, Update database XML files using the database setup
network drive)
file
td_cleo.mdb
Update mapping database

Identify and consider customer made changes for the
updated mapping database

O
Documentation
Review release notes
SAP EHS / OCC
Update cached data
MS Access
Analyze new & changed data
SAP EHS / OCC
Load changes to SAP EHS
Detailed information on how to execute the single steps will be provided by following the links
in the check list above or in the How-To-documents listed below:
Section A.11, How to install EHS OCC
Section A.21, How to setup/update XML substance database for substance lists and reference data
Section A.22, How to setup/update mapping database for SAP EHS Regulatory Content substance lists and reference data
16
SAP AG

Section A.28, SAP EHS Regulatory Content - substance lists and reference data (Dangerous Goods) Update Data Load
5.1.4. Settings to update the CLEO regulatory data (Dangerous Goods)

The CLEO DG installation package includes the following files:
Files
File Description
0-Documentation
DG_Data_ReleaseNotes_ 2011-1.pdf
Latest Substance Lists and Reference Data Release

Note for Dangerous Goods
cleo_dg_changes 2011-1.mdb
Database with list of all changes and tool to analyze

impact on used UN No
TD_CLEO_DG_Training_EN.pdf
Training overview on how to use DG data and OCC.
1-Customizing
R904130.TDG / K904130.TDG
customizing transport updating ADR and RID, without

packing data
R904126.TDG / K904126.TDG
customizing transport updating ADR and RID, with

packing data
R904159.TDG / K904159.TDG
customizing transport for regulation ADN, without packing data
R904117.TDG / K904117.TDG
customizing transport for regulation ADN, with packing

data
2-Phrases
cleo_dg_2011-1.dat
phrase import file
cleo_dg_pset_2011-1.dat
phrase set assignment import file
3-CLEO Database
CLEO_DG_2011-1.zip
Substance Lists and Reference Data - Dangerous

Goods -archive
4-Mapping
TD_CLEO_DG.mdb
Dangerous Goods - Mapping Database, standard, with

packing data, without split by mode of transport for NA
regulations
TD_CLEO_DG_with_Split.mdb
Dangerous Goods - Mapping Database, with packing

data, with split by mode of transport for NA regulations
TD_CLEO_DG_without_pack.mdb
Dangerous Goods - Mapping Database, without packing data, without split by mode of transport for NA regulations
17
SAP AG

Files
File Description
TD_CLEO_DG_with_split_without_
pack.mdb
Dangerous Goods - Mapping Database, without packing data, with split by mode of transport for NA regulations

The following customizing settings have to be enhanced/changed for this update:
Note
This release contains a transport with all changed customizing entries of the regulations ADR, IMDG and RID.
These transports enable you to update your system with all new
entries for these regulations in 2011 amendment.
Note
With this release we implement a new regulation ADN for inland
waterway transport in Europe.
Currently ADNR is set up within the systems as the relevant Inland
Waterway regulation for various Countries in Europe. In order to
ensure a seamless switch to ADN data the following process steps
need to be performed:
1. Create the DG Regulation ADN within customizing Specify Dangerous Goods Regulations initially must not contain the Mode of
Transport Category Inland Waterway, for this is still assigned
to ADNR. Otherwise there will be Countries with more than one
DG regulation valid to Inland Waterway, which will lead to errors
in Logistics. Instead a Dummy Mode of Transport Category like
Pipeline needs to be used initially for the time being. This holds
ADNR still active and deactivates ADN.
2. Implement ADN DG Customizing transport with all the other entries necessary.
3. Load LS_UN_SUB data for ADN. The OCC will create a new instance for this regulation in your specification but will remember
the settings of your last load with ADNR.
4. Amend DG_CL_SUB > Transport Classification with ADN data.
5. Amend all other DG related properties with ADN data, e. g.
Additional data for Transport, Hazard Inducers and Dangerous
Goods User defined Texts
6. Prepare WWI documents (MSDS) for ADN. Our MSDS template
is already prepared for this regulation.
7. Set ADN active by changing the Mode of Transport Category
from the dummy entry to Inland Waterway.
8. Set ADNR inactive by changing the Mode of Transport Category
from Inland Waterway to the dummy entry. In this case you
have to delete this regulation and create it new with new settings.
9. Refill DG Master.
10.Remove all ADNR data from Specification database.
18
SAP AG

11.Remove all ADNR DG customizing.
This updae package includes customizing transports that can be
imported to create all necessary customizing entries.
Note
We harmonized the unique IDs of the regulations ADR, RID and
ADN with this release. So it might happen that OCC is not able
to recognize an already existing RID instance in a specification.
In this cases you should delete the old RID instance so that this
specification do not show two RID instances.
This installation package includes customizing transports that can be imported to create all
necessary customizing entries.
The transports contains new entries for following tables:
TCG46 Sources
TCG91 Validity Areas
THM009 Dangerous goods classes
THM071 Risk potentials
THM017 Danger labels
THM003 Transport types
THM031Hazard identification numbers
CCUNC 115 Instructions for enclosure
CCUNC121 Packing codes
Alternatively, all customizing entries can be done manually, please contact us for a detailed
description.
19
SAP AG

Content - expert rules for substance
and mixture classification
6.1. Check Update
The following steps describe how to check the update of Expert Rules.
6.1.1. Check List

Please use the following check list as guidance through the Expert Rules update procedure.
Status
Where to do
What to do
General
O
Technical Part
O
Customizing (Transaction Create data origin

spro)
Create user exit(s)
Create regulatory list
Mapping.mdbs
If you have adapted the mapping databases of the previous version to your needs , identify changes in the
new mapping.mdbs and consider these for the update
of your mapping databases (see HISTORY.mdbs)
Externvalues.mdbs
If you have adapted the external values databases of the previous version to your needs , identify
changes in the new externvalues.mdbs and consider
these for the update of your mapping databases (see
HISTORY.mdbs)
Expert Server or SAP EHS Upload rule set files

(Transaction cgsadm)
Create new admin instance(s)
Update existing admin instance(s)

O
Detailed information on how to execute the single steps will be provided in these How-Todocuments:
Section A.15, How to add data origins

Section A.12, How to extend entry in secondary data determination
Section A.35, How to use the History.mdb
Section A.33, How to adjust external table values
20
SAP AG
SAP EHS Regulatory Content - expert rules

for substance and mixture classification
Section A.34, How to adjust the Group Mapping

Section A.31, How to load rule sets onto the Expert server
Section A.32, How to register rule sets
6.1.2. Settings to update the licenced rule set package(s)

6.1.2.1. Settings in Admin Tool
The below listed settings have to be maintained via the Expert Admin Tool or within the transaction CGSADM for the current release.
The settings for unchanged instances are documented in the SAP EHS Regulatory Content
Administration Manual which is also included in the delivery.
The settings for the rule sets are:
DP AU [update instance]
Environment parameter
Name
ZEXP_DP_AU
Mapping Database
DP_AU_V2-34.mdb
Rule File
DP_AU_V2-34.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Classification CN [update instance]

Name
ZEXP_CN_CN
Mapping Database
Classification_CN_V2-51.mdb
Rule File
Classification_CN_V2-51.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS CN [update instance]

Name
ZEXP_GHSCN
Mapping Database
GHS_CN_V1-3.mdb
Rule File
GHS_CN_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
21
SAP AG

Classification JP [update instance]
Name
ZEXP_CN_JP
Mapping Database
Classification_JP_V2-62.mdb
Rule File
Classification_JP_V2-62.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Fire Service JP [update instance]

Name
ZEXP_FS_JP
Mapping Database
Fire_Service_JP_V2-9.mdb
Rule File
Fire_Service_JP_V2-9.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp JP [update instance]

Name
ZEXP_HC_JP
Mapping Database
HazardComp_JP_V2-81.mdb
Rule File
HazardComp_JP_V2-81.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS JP [update instance]

Name
ZEXP_GHSJP
Mapping Database
GHS_JP_V1-3.mdb
Rule File
GHS_JP_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS KR [update instance]

22
SAP AG

Name
ZEXP_GHSKR
Mapping Database
GHS_KR_V1-7.mdb
Rule File
GHS_KR_V1-7.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
DSSMA KR [update instance]

Name
ZEXP_DS_KR
Mapping Database
DSSMA_KR_V1-7.mdb
Rule File
DSSMA_KR_V1-7.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp KR [update instance]

Name
ZEXP_HC_KR
Mapping Database
HazardComp_KR_V2-52.mdb
Rule File
HazardComp_KR_V2-52.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS NZ [update instance]

Name
ZEXP_GHSNZ
Mapping Database
GHS_NZ_V1-6.mdb
Rule File
GHS_NZ_V1-6.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp NZ [update instance]

GHS SG [update instance]
Name
ZEXP_GHSSG
23
SAP AG

Mapping Database
GHS_SG_V1-3.mdb
Rule File
GHS_SG_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp SG [update instance]

Name
ZEXP_HC_SG
Mapping Database
HazardComp_SG_V1-1.mdb
Rule File
HazardComp_SG_V1-1.ruc
GHS TW [update instance]

Name
ZEXP_GHSTW
Mapping Database
GHS_TW_V1-3.mdb
Rule File
GHS_TW_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
CMR EU [update instance]

Name
ZEXP_CMREU
Mapping Database
CMR_EU_V1-02.mdb
Rule File
CMR_EU_V1-02.ruc
Detergents [create new instance]

Name
ZEXP_DETR
Mapping Database
Detergents_V1-0.mdb
Rule File
Detergents_V1-0.ruc
ICPE [update instance]

Name
ZEXP_ICPE
Mapping Database
ICPE_V1-11.mdb
Rule File
ICPE_V1-11.ruc
24
SAP AG

Maladies Professionelles [update instance]
Name
ZEXP_F_MP
Mapping Database
MaladiesProfessionnelles_V1-41.mdb
Rule File
MaladiesProfessionnelles_V1-41.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
MAL Code [update instance]

Name
ZEXP_MAL
Mapping Database
MAL_Code_V1-3.mdb
Rule File
MAL_Code_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Seveso II [update instance]

Name
ZEXP_SEVE
Mapping Database
Seveso-II_V1-41.mdb
Rule File
Seveso-II_V1-41.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
TA Luft [update instance]

Name
ZEXP_TAL
Mapping Database
TAluft_V4-21.mdb
Rule File
TAluft_V4-21.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
TRGS510 [create new instance]

Name
ZEXP_TR510
25
SAP AG

Mapping Database
TRGS510_V1-0.mdb
Rule File
TRGS510_V1-0.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
TRGS900 [update instance]

Name
ZEXP_TR90
Mapping Database
TRGS_900_V1-22.mdb
Rule File
TRGS_900_V1-22.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
VbF AT [update instance]

Name
ZEXP_VBFAT
Mapping Database
VbF_AT_V1-31.mdb
Rule File
VbF_AT_V1-31.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
VOC CH [update instance]

Name
ZEXP_VOC
Mapping Database
VOC_CH_V1-31.mdb
Rule File
VOC_CH_V1-31.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
VOC EU [update instance]

Name
ZEXP_VOCEU
Mapping Database
VOC_EU_V1-33.mdb
Rule File
VOC_EU_V1-33.ruc
Additional Settings
26
SAP AG

Name
IgnoreWarnings
Value
322
VOC PaintCoat [update instance]

Name
ZEXP_VOCPC
Mapping Database
VOC_PaintCoat_V1-4.mdb
Rule File
VOC_PaintCoat_V1-4.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
WGK [update instance]

Name
ZEXP_WGK
Mapping Database
WGK_V1-81.mdb
Rule File
WGK_V1-81.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
EU to GHS [update instance]

Name
ZEXP_RTGHS
Mapping Database
EU_TO_GHS_V1-51.mdb
Rule File
EU_to_GHS_V1-51.ruc
GHS [update instance]

Name
ZEXP_GHS
Mapping Database
GHS_V2-3.mdb
Rule File
GHS_V2-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Hazcomp GHS [update instance]

Name
ZEXP_HCGHS
27
SAP AG

Mapping Database
Hazcomp_GHS_V1-52.mdb
Rule File
Hazcomp_GHS_V1-52.ruc
Clean Water Act [update instance]

Name
ZEXP_CWA
Mapping Database
CWA_V1-01.mdb
Rule File
CWA_V1-01.ruc
HazardComp US [update instance]

Name
ZEXP_HAZCO
Mapping Database
HazardComp_US_V2-71.mdb
Rule File
HazardComp_US_V2-71.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HMIS [update instance]

Name
ZEXP_HMIS
Mapping Database
HMIS_V2-5.mdb
Rule File
HMIS_V2-5.ruc
MCHC [create new instance]

Name
ZEXP_MCHC
Mapping Database
MCHC_V1-0.mdb
Rule File
MCHC_V1-0.ruc
NFPA [update instance]

Name
ZEXP_NFPA
Mapping Database
NFPA_V1-7.mdb
Rule File
NFPA_V1-7.ruc
OSHA/SARA Hazard Determination [update instance]

Name
ZEXP_OSHA
28
SAP AG

Mapping Database
OSHA_Hazard_Determination_V2-71.mdb
Rule File
OSHA_Hazard_Determination_V2-71.ruc
SpillReport [update instance]

Name
ZEXP_SPRQ
Mapping Database
SpillReport_V2-01.mdb
Rule File
SpillReport_V2-01.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
US State RTK [update instance]

Name
ZEXP_RTK
Mapping Database
US_State_RTK_V1-74.mdb
Rule File
US_State_RTK_V1-74.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
CA PBT [update instance]

Name
ZEXP_CAPBT
Mapping Database
CAPBT_V1-01.mdb
Rule File
CAPBT_V1-01.ruc
WHMISClassification [update instance]

Name
ZEXP_WHMIS
Mapping Database
WHMISCLASS_V2-62.mdb
Rule File
WHMISCLASS_V2-62.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
WHMISComposition [update instance]

Name
ZEXP_HC_CA
29
SAP AG

Mapping Database
WHMISComposition_V1-73.mdb
Rule File
WHMISComposition_V1-73.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS BR [update instance]

Name
ZEXP_GHSBR
Mapping Database
GHS_BR_V1-2.mdb
Rule File
GHS_BR_V1-2.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp BR [update instance]

Name
ZEXP_HC_BR
Mapping Database
HazardComp_BR_V1-1.mdb
Rule File
HazardComp_BR_V1-1.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
comp [update instance/set additional settings]

Name
ZEXP_COMP
Mapping Database
comp_V1-21.mdb
Rule File
comp_V1-21.ruc
Additional Settings
Name
IgnoreWarnings
Value
355
Dapec [update instance]

Name
ZEXP_DAPEC
Mapping Database
DAPEC_V3-1.mdb
Rule File
DAPEC_V3-1.ruc
Additional Settings
30
SAP AG

Name
IgnoreWarnings
Value
322
GHS EU [update instance]

Name
ZEXP_GHSEU
Mapping Database
GHS_EU_V1-6.mdb
Rule File
GHS_EU_V1-6.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp EU [update instance]

Name
ZEXP_HC_EU
Mapping Database
HazardComp_EU_V3-0.mdb
Rule File
HazardComp_EU_V3-0.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
CLNOT [update instance]

Name
ZEXP_CLNOT
Mapping Database
CL_for_notification_V1-2.mdb
Rule File
CL_for_notification_V1-2.ruc
DangGoods [update instance]

Name
ZEXP_DG
Mapping Database
DangGoods_master_global_V4-0.mdb
DangGoods_master_V4-0.mdb
Rule File
DangGoods_master_global_V4-0.ruc
DangGoods_master_V4-0.ruc
MSDSMaker [update instance]

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

used / subfolders in delivery)
31
SAP AG

Rule File
MSDSRule_V3-7.ruc
NotStat [update instance]

Name
ZEXP_NOTS
Mapping Database (ProdComp variant)
NotStat_frame_master_ProdComp_V3-3.mdb
(ProdComp variant)
Mapping Database (StandComp variant)
NotStat_frame_master_StandComp_V3-3.mdb
(StandComp variant)
Rule File
NotStat_frame_master_V3-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322,330,332,355
RestrictionStatus [update instance]

Name
ZEXP_RESST
Mapping Database
RestrictionStatus_V1-71.mdb
Rule File
RestrictionStatus_V1-71.ruc
DPD_plus_lead [update instance]

Name
ZEXP_DPDL
Mapping Database
DPDplus_lead_V1-11.mdb
Rule File
DPDplus_lead_V1-11.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
6.1.2.2. Settings in Admin Tool - Sub Rules

The settings for the sub rule sets are:
DG_SUB [delete instance]
DG_SUB_4_0 [create new instance]
Name
DG_SUB_4_0
32
SAP AG

Rule File
DangGoods_V4-0.ruc
DG_COMPARE [delete instance]

DG_HI [delete instance]
DG_SUB_GAS [delete instance]
DG_SUB_GAS_4_0 [create new instance]
Name
DG_SUB_GAS_4_0
Rule File
DangGoods_gas_V4-0.ruc
DG_GAS_BINARY [update instance]

Name
DG_GAS_BINARY
Rule File
DangGoods_sub_binary_V4-0.ruc
DG_RQ [delete instance]

DG_RQ_4_0 [create new instance]
Name
DG_RQ_4_0
Rule File
DangGoods_report_quant_V4-0.ruc
GHS_SUB_PB2009_1_1 [create new instance]

Name
GHS_SUB_PB2009_1_1
Rule File
GHS_sub_pb2009_V1-1.ruc

Name
GHS_SUB_PB2007_1_4
Rule File

Name
GHS_SUB_PB2009_1_3
Rule File
GHS_EXPL_1_5 [create new instance]

33
SAP AG

Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc
GHS_LABEL_1_1 [create new instance]

Name
GHS_LABEL_1_1
Rule File
GHS_label_V1-1.ruc
MSDSRULE_SUB [update instance]

Name
MSDSRULE_SUB
Rule File
MSDSRule_sub_V3-7.ruc
NOTSTAT_SUB [update instance]

Name
NOTSTAT_SUB
Rule File
NotStat_V3-3.ruc
NOTSTAT_SUB_TSCA12B [update instance]

Name
NOTSTAT_SUB_TSCA12B
Rule File
NotStat_sub_TSCA12b_V3-3.ruc
NOTSTAT_SUB_EXPL [update instance]

Name
NOTSTAT_SUB_EXPL
Rule File
NotStat_sub_expl_V3-3.ruc
6.1.2.3. User Exit Settings

The following user exit settings have to be enhanced/changed for this update:
Detergents [create new user exit]
User exit name
ZEXP_DETR
User exit description
EHS-Expert: Detergents
34
SAP AG

EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION
C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE
EXPERT_READ_RATING
PUBLIC
EXPERT_READ_VALIDITY_AREA
REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG
EXPERT_RULE_SET
ZEXP_DETR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
EXPERT_WRITE_SOURCE_ID
ZEXP_DETR
EXPERT_WRITE_VALIDITY_AREA
REG_EU
TRGS510 [create new user exit]

User exit name
ZEXP_TR510
EHS-Expert: TRGS510
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
DE
EXPERT_RULE_SET
ZEXP_TR510
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_LGK
DE
Maine Chemicals High Concern [create new user exit]

User exit name
ZEXP_MCHC
EHS-Expert: ...
35
SAP AG

EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_MCHC
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
ZEXP_MCHC
US

Data Origin [create new]
affected rule sets
ZEXP_DETR
Detergents
affected rule sets
ZEXP_MCHC
Maine Chemicals of High Concern
6.1.3. Settings to update the basis rule set package

The following files are included in the delivery:
comp
File name
Description
comp_V1-21.ruc
Rule File
comp_V1-21.mdb
Mapping Database
Comp_V1-21.pdf
Functional Description
M Factor
File name
Description
M_Factor_V1-0.ruc
Rule File
M_Factor_V1-0.mdb
Mapping Database
36
SAP AG

M_Factor_V1-0.pdf

Comp [update instance/set additional settings]
Name
ZEXP_COMP
Mapping Database
comp_V1-21.mdb
Rule File
comp_V1-21.ruc
Additional Settings
Name
IgnoreWarnings
Value
355


6.1.4. Settings to update the rule set package for GHS

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

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

a separate instance on the Expert-Server-PC
37
SAP AG

GHS_label_V1-0.ruc

EU_to_GHS__HISTORY.mdb
database for the documentation of the

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

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



GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GHS__HISTORY.mdb

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

38
SAP AG

Hazcomp_GHS__HISTORY.mdb

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

Name
ZEXP_RTGHS
Mapping Database
EU_TO_GHS_V1-51.mdb
Rule File
EU_to_GHS_V1-51.ruc
GHS [update instance]

Name
ZEXP_GHS
Mapping Database
GHS_V2-3.mdb
Rule File
GHS_V2-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Hazcomp GHS [update instance]

Name
ZEXP_HCGHS
Mapping Database
Rule File

39
SAP AG

Name
GHS_SUB_PB2009_1_3
Rule File

Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc

Name
GHS_LABEL_1_1
Rule File
GHS_label_V1-1.ruc


6.1.5. Settings to update the rule set package for APA

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

DP_AU__HISTORY.mdb

ReleaseNote_APA_2011-1.pdf
Release Note
DP_AU_V2-34.pdf
40
SAP AG

HazardComp AU
File name
Description
HazardComp_AU_V2-51.ruc
Rule File
HazardComp_AU_V2-51.mdb
Mapping Database
HazardComp_AU_externvalues.mdb
External Database
GS_base_V1-1.ruc

HazardComp_AU__HISTORY.mdb

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

Classification_CN__HISTORY.mdb

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

HazardComp_CN__HISTORY.mdb

Release Note
HazardComp_CN_V2-5.pdf
GHS CN
File name
Description
GHS_CN_V1-3.ruc
Rule File
41
SAP AG

GHS_CN_V1-3.mdb
Mapping Database
GHS_CN_externvalues.mdb
External Database
the
external
database

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc

GS_ident_V1-0.ruc


GHS_CN__HISTORY.mdb

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


Classification_JP__HISTORY.mdb

Release Note
Classification_JP_V2-62.pdf
Fire Service JP
File name
Description
Rule File
42
SAP AG

Mapping Database
Fire_Service_JP_externvalues.mdb
External Database
GS_base_V1-1.ruc


Fire_Service_JP__HISTORY.mdb

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

HazardComp_JP__HISTORY.mdb

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

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc

43
SAP AG

GS_ident_V1-0.ruc


GHS_JP__HISTORY.mdb

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

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc

GS_ident_V1-0.ruc


GHS_KR__HISTORY.mdb

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

GS_base_V1-1.ruc


DSSMA_KR__HISTORY.mdb

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


HazardComp_KR__HISTORY.mdb

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

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GS_base_V1-1.ruc

GS_ident_V1-0.ruc

45
SAP AG


GHS_NZ__HISTORY.mdb

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

HazardComp_NZ__HISTORY.mdb

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

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc

GS_ident_V1-0.ruc


46
SAP AG

GHS_SG__HISTORY.mdb

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

HazardComp_SG__HISTORY.mdb

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

Classification_TW__HISTORY.mdb

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

HazardComp_TW__HISTORY.mdb

47
SAP AG

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

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc

GS_ident_V1-0.ruc


GHS_TW__HISTORY.mdb

Release Note
GHS_TW_V1-3.pdf

DP AU [update instance]
Name
ZEXP_DP_AU
Mapping Database
DP_AU_V2-34.mdb
48
SAP AG

Rule File
DP_AU_V2-34.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Classification CN [update instance]

Name
ZEXP_CN_CN
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
GHS CN [update instance]

Name
ZEXP_GHSCN
Mapping Database
GHS_CN_V1-3.mdb
Rule File
GHS_CN_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Classification JP [update instance]

Name
ZEXP_CN_JP
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
Fire Service JP [update instance]

Name
ZEXP_FS_JP
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
49
SAP AG

HazardComp JP [update instance]
Name
ZEXP_HC_JP
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
GHS JP [update instance]

Name
ZEXP_GHSJP
Mapping Database
GHS_JP_V1-3.mdb
Rule File
GHS_JP_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS KR [update instance]

Name
ZEXP_GHSKR
Mapping Database
GHS_KR_V1-7.mdb
Rule File
GHS_KR_V1-7.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
DSSMA KR [update instance]

Name
ZEXP_DS_KR
Mapping Database
DSSMA_KR_V1-7.mdb
Rule File
DSSMA_KR_V1-7.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp KR [update instance]

Name
ZEXP_HC_KR
50
SAP AG

Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
GHS NZ [update instance]

Name
ZEXP_GHSNZ
Mapping Database
GHS_NZ_V1-6.mdb
Rule File
GHS_NZ_V1-6.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS SG [update instance]

Name
ZEXP_GHSSG
Mapping Database
GHS_SG_V1-3.mdb
Rule File
GHS_SG_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp SG [update instance]

Name
ZEXP_HC_SG
Mapping Database
Rule File
GHS TW [update instance]

Name
ZEXP_GHSTW
Mapping Database
GHS_TW_V1-3.mdb
Rule File
GHS_TW_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
51
SAP AG

Name
GHS_SUB_PB2007_1_4
Rule File

Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc

Name
GHS_LABEL_1_1
Rule File
GHS_label_V1-1.ruc


Rating [create new]
affected rule sets
LABEL_S
GHS_TW (needed for reduced label - needed

if output of label for packages < 100 ml has to
be written with its own usage)
6.1.6. Settings to update the rule set package Europe

Dapec
File name
Description
DAPEC_V3-1.ruc
Rule File
DAPEC_V3-1.mdb
Mapping Database
52
SAP AG

DAPEC_externvalues.mdb
External Database
the
external
database
GS_base_V1-1.ruc

GS_ident_V1-0.ruc


comp_LEC50_V1-01.ruc

DAPEC__HISTORY.mdb

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

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc


GHS_EU__HISTORY.mdb

ReleaseNote_GHS_EU_V1-6.pdf
Release Note
GHS_EU_V1-6.pdf
EU to GHS
File name
Description
53
SAP AG

EU_to_GHS_V1-51.ruc
Rule File
EU_to_GHS_Annex_VII_externvalues.mdb
External Database according to Annex VII of

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

GHS_label_V1-0.ruc

EU_to_GHS__HISTORY.mdb

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


comp_LEC50_V1-01.ruc

HazardComp_EU__HISTORY.mdb

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

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

the same external tables as the rule
set GHS EU. If GHS EU is already installed and changes had be done in
54
SAP AG

the external tables, this delivered file
GHS_EU_externvalues.mdb should not be
used.


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

DAPEC [update instance]
Name
ZEXP_DAPEC
Mapping Database
DAPEC_V3-1.mdb
Rule File
DAPEC_V3-1.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
GHS EU [update instance]

Name
ZEXP_GHSEU
Mapping Database
GHS_EU_V1-6.mdb
Rule File
GHS_EU_V1-6.ruc
Additional Settings
Name
IgnoreWarnings
Value
322

Name
ZEXP_RTGHS
Mapping Database
EU_TO_GHS_V1-51.mdb
Rule File
EU_to_GHS_V1-51.ruc
55
SAP AG

HazardComp EU [update instance]
Name
ZEXP_HC_EU
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
CLNOT [update instance]

Name
ZEXP_CLNOT
Mapping Database
Rule File

Name
GHS_SUB_PB2007_1_4
Rule File

Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc

6.1.7. Settings to update the rule set package DPDplus

56
SAP AG

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


GS_ident_V1-0.ruc

DPDplus_lead__HISTORY.mdb

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

DPDL [update instance]
Name
ZEXP_DPDL
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322

57
SAP AG



Regulatory List [create new]
affected rule sets
REACH
DPDplus_lead
Identifier NUM [create new]

affected rule sets
REACH_REG
DPDplus_lead
6.1.8. Settings to update the rule set package for National

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

CMR_EU__HISTORY.mdb

ReleaseNote_EU_2011-1.pdf
Release Note
CMR_EU_V1-02.pdf
Detergents
File name
Description
Detergents_V1-0.ruc
Rule File
Detergents_V1-0.mdb
Mapping Database
58
SAP AG

Detergents_externvalues.mdb
External Database
GS_base_V1-1.ruc

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

Maladies Professionelles
File name
Description
Rule File
Mapping Database
MaladiesProfessionnelles_externvalues.mdb External
Database
MaladiesProfessionnelles__HISTORY.mdb

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

MAL_Code__HISTORY.mdb

Release Note
MAL-Code_V1-3.pdf
Seveso II
File name
Description
Seveso-II_V1-41.ruc
Rule File
Seveso-II_V1-41.mdb
Mapping Database
59
SAP AG

Seveso-II_externvalues.mdb
External Database
GS_base_V1-1.ruc


Seveso-II__HISTORY.mdb

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


TAluft__HISTORY.mdb

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


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

GS_base_V1-1.ruc

TRGS_900__HISTORY.mdb

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

VbF_AT__HISTORY.mdb

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

VOC_CH__HISTORY.mdb

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


61
SAP AG

VOC_EU__HISTORY.mdb

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


VOC_PaintCoat__HISTORY.mdb

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

GS_ident_V1-0.ruc

WGK__HISTORY.mdb

Release Note
WGK_V1-81.pdf

62
SAP AG

CMR EU [update instance]
Name
ZEXP_CMREU
Mapping Database
CMR_EU_V1-02.mdb
Rule File
CMR_EU_V1-02.ruc
Detergents [create new instance]

Name
ZEXP_DETR
Mapping Database
Detergents_V1-0.mdb
Rule File
Detergents_V1-0.ruc
ICPE [update instance]

Name
ZEXP_ICPE
Mapping Database
ICPE_V1-11.mdb
Rule File
ICPE_V1-11.ruc
MAL Code [update instance]

Name
ZEXP_MAL
Mapping Database
MAL_Code_V1-3.mdb
Rule File
MAL_Code_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Maladies Professionnelles [update instance]

Name
ZEXP_F_MP
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
63
SAP AG

Seveso II [update instance]
Name
ZEXP_SEVE
Mapping Database
Seveso-II_V1-41.mdb
Rule File
Seveso-II_V1-41.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
TA Luft [update instance]

Name
ZEXP_TAL
Mapping Database
TAluft_V4-21.mdb
Rule File
TAluft_V4-21.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
TRGS510 [create new instance]

Name
ZEXP_TR510
Mapping Database
TRGS510_V1-0.mdb
Rule File
TRGS510_V1-0.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
TRGS900 [update instance]

Name
ZEXP_TR90
Mapping Database
TRGS_900_V1-22.mdb
Rule File
TRGS_900_V1-22.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
VbF AT [update instance]

Name
ZEXP_VBFAT
64
SAP AG

Mapping Database
VbF_AT_V1-31.mdb
Rule File
VbF_AT_V1-31.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
VOC CH [update instance]

Name
ZEXP_VOC
Mapping Database
VOC_CH_V1-31.mdb
Rule File
VOC_CH_V1-31.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
VOC EU [update instance]

Name
ZEXP_VOCEU
Mapping Database
VOC_EU_V1-33.mdb
Rule File
VOC_EU_V1-33.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
VOC PaintCoat [update instance]

Name
ZEXP_VOCPC
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
WGK [update instance]

Name
ZEXP_WGK
Mapping Database
WGK_V1-81.mdb
Rule File
WGK_V1-81.ruc
Additional Settings
65
SAP AG

Name
IgnoreWarnings
Value
322



affected rule sets
ZEXP_DETR
Detergents
6.1.9. Settings to update the rule set package for NA

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

CAA__HISTORY.mdb

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

File name
Description
CWA_V1-01.ruc
Rule File
CWA_V1-01.mdb
Mapping Database
66
SAP AG

GS_base_V1-1.ruc

CWA__HISTORY.mdb

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

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

HazardComp_US__HISTORY.mdb

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

67
SAP AG

GS_ident_V1-0.ruc


HMIS__HISTORY.mdb

Release Note
HMIS_V2-5.pdf
Maine Chemicals High Concern

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

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

GS_ident_V1-0.ruc


NFPA__HISTORY.mdb

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

File name
Description
Rule File
68
SAP AG

Mapping Database
OSHA_Hazard_Determination_
externvalues.mdb
External Database
the
external
database
GS_base_V1-1.ruc

GS_ident_V1-0.ruc


OSHA_Hazard_Determination__HISTORY.mdb

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

SaraComp__HISTORY.mdb

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

SpillReport__HISTORY.mdb

Release Note
SpillReport_V2-01.pdf
69
SAP AG

US State RTK
File name
Description
Rule File
Mapping Database
US_State_RTK_externvalues.mdb
External Database
GS_base_V1-1.ruc

US_State_RTK__HISTORY.mdb

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

CAPBT__HISTORY.mdb

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

GS_ident_V1-0.ruc


WHMISCLASS__HISTORY.mdb

70
SAP AG

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

WHMISComposition__HISTORY.mdb

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

GHS_label_V1-1.ruc

GHS_pure_V1-1.ruc

GHS_expl_V1-5.ruc

GS_base_V1-1.ruc


GHS_BR__HISTORY.mdb

Release Note
GHS_BR_V1-2.pdf
HazardComp BR
File name
Description
Rule File
71
SAP AG

Mapping Database
HazardComp_BR_externvalues.mdb
External Database
GS_base_V1-1.ruc

HazardComp_BR__HISTORY.mdb

HazardComp_BR_V1-1.pdf

Clean Water Act [update instance]
Name
ZEXP_CWA
Mapping Database
CWA_V1-01.mdb
Rule File
CWA_V1-01.ruc
HazardComp US [update instance]

Name
ZEXP_HAZCO
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
HMIS [update instance]

Name
ZEXP_HMIS
Mapping Database
HMIS_V2-5.mdb
Rule File
HMIS_V2-5.ruc
Maine Chemicals High Concern [create new instance]

72
SAP AG

Name
ZEXP_MCHC
Mapping Database
MCHC_V1-0.mdb
Rule File
MCHC_V1-0.ruc
NFPA [update instance]

Name
ZEXP_NFPA
Mapping Database
NFPA_V1-7.mdb
Rule File
NFPA_V1-7.ruc
OSHA/SARA Hazard Determination [update instance]

Name
ZEXP_OSHA
Mapping Database
Rule File
SpillReport [update instance]

Name
ZEXP_SPRQ
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
US State RTK [update instance]

Name
ZEXP_RTK
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
CA PBT [update instance]

Name
ZEXP_CAPBT
Mapping Database
CAPBT_V1-01.mdb
Rule File
CAPBT_V1-01.ruc
73
SAP AG

WHMISClassification [update instance]
Name
ZEXP_WHMIS
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
WHMISComposition [update instance]

Name
ZEXP_HC_CA
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322
GHS BR [update instance]

Name
ZEXP_GHSBR
Mapping Database
GHS_BR_V1-2.mdb
Rule File
GHS_BR_V1-2.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
HazardComp BR [update instance]

Name
ZEXP_HC_BR
Mapping Database
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322

74
SAP AG

Name
GHS_SUB_PB2007_1_4
Rule File

Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc

Name
GHS_LABEL_1_1
Rule File
GHS_label_V1-1.ruc

Maine Chemicals High Concern [create new user exit]
User exit name
ZEXP_MCHC
EHS-Expert: Maine Chemicals High Concern
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_READ_RATING
PUBLIC
US
EXPERT_RULE_SET
ZEXP_MCHC
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
75
SAP AG

ZEXP_MCHC
US

affected rule sets
ZEXP_MCHC
Maine Chemicals of High Concern
6.1.10. Settings to update the RegStat rule set package

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

GS_ident_V1-0.ruc

NotStat_frame_master__HISTORY.mdb

ReleaseNote_NotStat_V3-3.pdf
Release Note
Notstat_V3-3.pdf
RestrictionStatus
File name
Description
76
SAP AG

Rule File
Mapping Database
RestrictionStatus_externvalues.mdb
External Database
GS_base_V1-1.ruc

RestrictionStatus__HISTORY.mdb

ReleaseNote_RestrictionStatus_V1-71.pdf
Release Note
RestrictionStatus_V1-71.pdf

Please note: for NotStat, there are two different variants delivered, ProdComp and StandComp.
Depending on the variant chosen for the installation, the respective files need to be selected.
NotStat [update instance]
Name
ZEXP_NOTS
(ProdComp variant)
(StandComp variant)
Rule File
Additional Settings
Name
IgnoreWarnings
Value
322,330,332,355
RestrictionStatus [update instance]

Name
ZEXP_RESST
Mapping Database
Rule File

77
SAP AG

NOTSTAT_SUB [update instance]
Name
NOTSTAT_SUB
Rule File
NotStat_V3-3.ruc
NOTSTAT_SUB_TSCA12B [update instance]

Name
NOTSTAT_SUB_TSCA12B
Rule File
NOTSTAT_SUB_EXPL [update instance]

Name
NOTSTAT_SUB_EXPL
Rule File


6.1.11. Settings to update the DangGoods rule set package

Please note: there are two different variants of the DangGoods rule set available: global and
local. Depending on your license you may receive different files for the main rule DangGoods,
which are both indicated below separated by slashes. In such cases the delivered files have
to be chosen respectively.
DangGoods
File name
Description
Rule File (global/local version)
Mapping Database (global/local version)
DangGoods_externvalues.mdb
External Database
78
SAP AG

DangGoods_V4-0.ruc
sub rule set (central part for classification process for solids/liquids)
sub rule set (GHS classification via component data)
sub rule set (classification for gaseous mixtures and hazard inducer determination)
sub rule set (evaluation of binary mixtures as

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

GS_ident_V1-0.ruc


DangGoods_master__HISTORY.mdb

ReleaseNote_DangGoods_V4-0.pdf
Release Note
DangGoods_V4-0.pdf

Please note: there are two different variants of the DangGoods rule set available: global and
local. Depending on your license you may receive different files for the main rule DangGoods,
which are both indicated below separated by slashes. In such cases the delivered files have
to be chosen respectively.
DangGoods [update instance]
Name
ZEXP_DG
Mapping Database
Rule File
79
SAP AG


DG_SUB [delete instance]
DG_SUB_4_0 [create new instance]
Name
DG_SUB_4_0
Rule File
DangGoods_V4-0.ruc
DG_COMPARE [delete instance]

DG_HI [delete instance]
DG_SUB_GAS [delete instance]
DG_SUB_GAS_4_0 [create new instance]
Name
DG_SUB_GAS_4_0
Rule File
DG_GAS_BINARY [update instance]

Name
DG_GAS_BINARY
Rule File
DG_RQ [delete instance]

DG_RQ_4_0 [create new instance]
Name
DG_RQ_4_0
Rule File

Name
GHS_SUB_PB2009_1_1
Rule File
80
SAP AG



6.1.12. Settings to update the MSDSMaker rule set package

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

MSDSMaker.mdb
External Database (depending on variant

sub rule set
GS_base_V1-1.ruc

separate instance on the Expert Server PC

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

MSDSMaker [update instance]
Name
ZEXP_SDS
Mapping Database
MSDSRule_V3-7.mdb (depending on variant

Rule File
MSDSRule_V3-7.ruc
81
SAP AG

MSDSRULE_SUB [update instance]
Name
MSDSRULE_SUB
Rule File

Please note: If multiple content variants of the MSDSMaker shall be used in parallel, additional
user-exits are required. For details please refer to the functional description delivered with the
MSDSMaker.

82
SAP AG
Chapter 7. MSDS Templates

7.1. Check Update
The following steps describe how to check the update of Material safety data sheet (MSDS)
templates.

Please use the following check list as guidance through the Material safety data sheet (MSDS)
templates update procedure.
Status
Where to do
What to do
General
O
Technical Part
O
SAP EHS (cg3z)
Upload files
SAP EHS (stms)
Import transports
Customizing (spro)
Setup identification listings
SAP EHS (cg34)
Import templates
SAP EHS (cg2b)
Create generation variants
Templates
Identify changes in templates and consider these for the updated templates

Section A.36, How to setup identification listings
Section A.38, How to create generation variant
Section A.37, How to import report templates
7.1.2. Settings to update the MSDS Templates for APJ

APJ
File name
Description
K901326.TDP and R901326.TDP
APA customizing transport TDPK901326 unicode
K902773.TD4 and R902773.TD4
APA customizing transport TD4K902773 nonunicode
workbench transport TDPK901097
83
SAP AG
MSDS Templates
K900243.TD5 and R900243.TD5
transport with definition of the namespace

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

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

There are no further manual settings to be maintained manually with this update.
7.1.3. Settings to update the MSDS Template for EMEA

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

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

For correct printing of the ADR tunnel restriction code in section 14 it is necessary to implement following SAP notes: 1105036 (Mapping the tunnel regulation from the ADR 2007) and
1316952 (Displaying the transport type (description) in EHS reports)
7.1.4. Settings to update the MSDS Template for GHS

GHS
File name
Description
ReleaseNote_SDS_GHS_2011_1.pdf
ReleaseNote

There are no special new settings to be maintained for this GHS SDS update.
7.1.5. Settings to update the MSDS Templates for the Americas

Americas
File name
Description
customizing transport TDPK901324 unicode
K902775.TD4 and R902775.TD4
customizing transport TD4K902775 non-unicode
K900243.TD5 and R900243.TD5
K909498.TD6 and R909498.TD6
SDS_NA_2011_1.dat
SDS_NA_2011_1.doc
Template-file
SDS_NA_2011_1_unix.dat
SDS_NA_2011_1_Datamapping.pdf
86
SAP AG
MSDS Templates
SDS_NA_2011_1_changes_marked_ yellow.doc
SDS_NA_2011_1_Datamapping_highlighted.pdf DataMapping
highlighted
SDS_BR_2011_1.dat
SDS_BR_2011_1.doc
Template-file
SDS_BR_2011_1_unix.dat
SDS_BR_2011_1_Datamapping.pdf
SDS_BR_2011_1_changes_marked_ yellow.doc
SDS_BR_2011_1_Datamapping_highlighted.pdf DataMapping
highlighted

Placeholder-Phrases, like" Manufactured with /$/, a substance which harms public health and
environment by destroying ozone in the upper atmosphere." are included in our delivery of
CED phrases.
These phrases are used to pull NOL of components into the phrasetext printed on the SDS.
It is also important to make sure that the SAP Note 967807 is correctly implemented before
importing the template and using the above mentioned NOL functionality.
87
SAP AG
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 Management System.
2. Load the transport files into the import directory using the transaction CG3Z.
3. Attach the transport request to the import queue
In the following, the three steps are described:
1. Find out the directory name and path of the import queue for the SAP Transport Management System.
You may ask your SAP system manager or proceed as follows:
Run transaction AL11.
The first part of the directory path is listed after the entry DIR_TRANS, for example "F:
\usr\sap\trans".
Within this directory two sub-directories exist:
The sub-directory "cofiles" where the co-files are stored.
The sub-directory "data" where the data files are stored.
2. Load the transport files into the import directory using the transaction CG3Z.
Start transaction CG3Z.
Enter in the field "Source file on front end" the transport file name including the complete
path on your computer or file server, for example "d:\transfer\K102047.SH2" for a co-file
or "d:\transfer\R102047.SH2" for a data file.
Enter in the field "Target file on application server" the same file name and the complete
path on the SAP Application Server which you found out in Step 1, for example "F:\usr
\sap\trans\cofiles\K102047.SH2" for a co-file or "F:\usr\sap\trans\data\R102047.SH2" for
a data file. Make sure to enter "BIN" in the field "Transfer format for data".
Start the upload process with the push button "Upload". When the upload process has
been successful a message appears.
3. Attach the transport request to the import queue
Navigate to the SAP Transport Management System (transaction STMS).
Choose push button "Import Overview (F5)".
Navigate to the transport domain of your SAP system: Position the cursor on the transport
domain and choose the push button "Display Import Queue" or choose "Double click".
Choose in the menu "Extras" -> "Other requests" -> "Add".
Enter in the field "Transp. Request" the name of the transport request, e.g.
"SH2K102047". The field "Import Queue" is already filled with the selected import queue.
Start the process with the push button "Continue". The transport request is added to the
bottom of the import queue with the highest number.
Please note that the listed "Owner" is the SAP user who created the transport request not
the login-user who started the upload process!
A.2. How to upload files

Upload all phrase import files and the phrase set assignment file from your local drive to the
application server.
88
SAP AG
How To ...
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. The update delivery includes import files formatted for MS Windows and UNIX. You
can get info about the OS in R/3 at -> System -> Status. Under the "Host data" header you can
see the operating system used by the R/3 server. You may also have to consider if Unicode
or Non Unicode system.
The upload of import files onto the application server and the import into EHS are completely
independent from any language specific settings on the front-end PC, i.e. phrases can be
uploaded and imported with every regional default setting.
A.3. How to import transports (customizing or

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

There are two ways to generate phrase sets:
1. Manual generation and allocation of phrase sets
2. During an initial setup: Customizing activity "Generate Standard Phrase Sets"
In the following, both ways are described:
1. Manual generation and allocation of phrase sets
Ensure that no one is working with the affected property tree or is using the affected the
properties and characteristics in the EHS specification workbench.
Run transaction CGCZ "Match Up Master Data" with flag "Match Up ValAss Type and
Char." only. This function determines all characteristics to which phrases can be assigned
- that are characteristics of type CHAR 30. These characteristics are transferred to the
table Phrase set - Attribute assignment (transaction CGAB).
91
SAP AG
How To ...
Choose transaction CG1B "Edit phrase sets" and create manually phrase sets for all
characteristics which are described in the file "Changes....pdf" as "new, CHAR 30, multiple phrases" or new, CHAR 30, single phrase. Enter the characteristic key as the new
phrase set key. Add appropriate phrases to the new phrase sets. Exceptions are characteristics such as "Accuracy" or "GLP". For these characteristics, phrase sets already
exist (SAP_EHS_XXXX_XXX_PREC, SAP_EHS_XXXX_XXX_GLP) and can directly be
assigned.
Customers of SAP EHS Regulatory Content - multilanguage phrase library for hazard
communication receive the allocation of phrases to phrase sets of new characteristics
with the corresponding update.
Choose transaction CGAB "Edit phrase set-attribute assignment". Assign all new phrase
sets to the appropriate characteristics.
Run transaction CGCZ "Match up master data" with flag "Activate Phrasing of Characteristics." only. This function assigns the function module
C14K_PHRASECHARACT_CHECK to all phrase-related characteristics. This enables
the system to call an assigned phrase set in the specification data base.
92
SAP AG
How To ...
2. During an initial setup: Customizing activity "Generate Standard Phrase Sets"
Ensure that no one is working with the affected property tree or is using the affected the
properties and characteristics in the EHS specification workbench.
If an EHS system is set up initially the customizing activity "Generate Standard Phrase
Sets" is used in general to create and allocate phrase sets to all characteristics of type
CHAR 30.
Navigate to the activity "Generate Standard Phrase Sets" in the SAP customizing (IMDG)
(path within EHS 3.2 and higher releases: Environment, Health & Safety -> Basic Data and
Tools -> Specification Management -> Specification Data Base Structure -> Settings for
Value Assignment). A complete overview about this activity is given in the corresponding
IMDG activity documentation.
Start the activity.
Phrase sets are generated and allocated to all characteristics of type CHAR 30. Phrases
are not allocated to the new phrase sets. Assignments of phrase sets to characteristics
that already exist are not overwritten by the system.
Some characteristics defined as CHAR 30 are not meant to be assigned to phrase sets,
for example "Value in Non-Standard Unit". These characteristics shall be used to store a
numerical value and a unit but were unfortunately defined as a free text fields of CHAR
30. In this case, the assigned phrase set has to be deleted in the table "Edit phrase
set-attribute assignment" (transaction CGAB) after the standard phrase sets have been
created.
Run transaction CGCZ "Match up master data" with flag "Activate Phrasing of Characteristics" only. This function assigns the function module
C14K_PHRASECHARACT_CHECK to all phrase-related characteristics. This enables the system to call an assigned phrase set in the specification data base.
If the phrase set was deleted in the table "Edit phrase set-attribute assignment" (transaction CGAB) before carrying out this transaction, then the function module
C14K_PHRASECHARACT_CHECK is deleted in the corresponding CHAR 30-characteristic and this characteristic can be filled as a free text field.
A.5. 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.
93
SAP AG
How To ...
Additional information:
In a standard R/3 System symbols are generated with descriptions in the logon language. The
flag "Regenerate Symbol Descriptions" within transaction CGCZ can be used to generate the
symbol descriptions in another language different from the logon language.
If the transaction CGCZ is run with the flag "Match Up Symbols-Phrase-Enabled Characteristics" the symbol definitions for the characteristic symbols that have been changed from phraserelated to non-phrase-related (or vice versa) will be updated..
A.6. 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
1.1. Navigate to the activity "Set Up Table-Based Value Assignment" in the SAP customizing (IMG) (path within EHS 3.2 and higher releases: Environment, Health & Safety ->
Basic Data and Tools -> Specification Management -> Specification Data Base Structure
-> Settings for Value Assignment -> Set Up Table-Based Value Assignment). A complete
overview about this activity is given in the corresponding IMG activity documentation.
1.2. Start the activity. The following screen appears:
94
SAP AG
How To ...
1.3. Choose the entry "Create Entries for the Value Assignments". The window "Filling
Customizing Table for Table-based Value Assignment" appears:
95
SAP AG
How To ...
1.4. Enter a property key of a new property or a series of property keys in the field "Value
assgmt type" and start the process (pushbutton "Execute").
A general example for a property key is SAP_EHS_1023_043 (for property "GHS Classification"). Select the property keys of the new properties within a specific property tree
package from the file "Changes_.....pdf". The file name for a specific property tree package can be found in the Appendix.
Please avoid to execute this process with the same property key multiple times because
this would create multiple entries in the customizing table!
1.5. Return to the previous window (push button "Back"):
96
SAP AG
How To ...
1.6. Choose the entry "Set Up Table-Based Value Assignment". The complete customizing table opens. Check all entries for the configured property/properties:
1.8. Repeat the steps 1.2 to 1.7 to create the necessary entries for all new properties.
2. Set up Table-based Value Assignment for existing properties with new characteristics
For EHS 3.2 and higher releases you have to change the configuration of existing properties where new characteristics were added and which were already configured for the Table-Based Value Assignment. The recommended procedure is to delete all entries for existing properties with new characteristics in the customizing table and to create the entries
for these properties again (see the following steps 2.1 to 2.14).
If the configuration of the Table-Based Value Assignment for properties with new characteristics was already changed, then these changes should be documented before deleting the
entries. In this case, an alternative could be not to delete all entries for a changed property
but to update the Table-Based Value Assignment for the existing property only (follow steps
1.1 to 1.8). Then, the new characteristics would be appended to the already existing entries
for this property. The correct order of the characteristics would have to be set up manually.
Please note, that the Table-based Value Assignment customizing table can only be changed
in SAP systems where the direct customizing is enabled. If the direct customizing is disabled
(for example in a production system), then the Table-based Value Assignment should be set
up in a system where the direct customizing is enabled (for example a development system).
The correct entries can be then transported to the system with the disabled customizing
(customizing transport).
2.1. Navigate to the activity "Set Up Table-Based Value Assignment" in the SAP customizing (IMG) (path within EHS 3.2 and higher releases: Environment, Health & Safety ->
Basic Data and Tools -> Specification Management -> Specification Data Base Structure
-> Settings for Value Assignment -> Set Up Table-Based Value Assignment). A complete
overview about this activity is given in the corresponding IMG activity documentation.
2.2. Start the activity. The following screen appears:
97
SAP AG
How To ...
2.3. Choose the entry "Set Up Table-Based Value Assignment". The complete customizing table opens.
2.4. Choose the push button "Position", enter a property key of an existing property with
new characteristics and navigate to this property. Select the property key from the file
"Changes_.....pdf". The specific file name for a certain property tree package can be found
in the Appendix.
2.5. Select all entries for this property.
2.6. Delete the selected entries (push button "Delete").
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:
98
SAP AG
How To ...
2.9. Enter the property key of the property, which entries you deleted in the previous step,
in the field "Value assgmt type":
2.10. Start the process (pushbutton "Execute").
2.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.14. Repeat the steps 2.2 to 2.13 to create the necessary entries for all existing properties
with new characteristics.
A.7. How to import phrases

99
SAP AG
How To ...
Choose Data Transfer - > Phrases (Transaction CG31) ; please see screen shot below.
"File with path" - Enter the path and file name (same as target file section upload files )
"Character standard" - Choose MS-NT for all files that have no _unicode.dat ending in their
filename; this applies also to unicode systems!
For files with unicode only languages ( with _unicode.dat ending in their filename) choose
UTF-8 as character standard.
You can leave all other options blank
Optional: You can limit the import to certain languages if you want (Button "Language selection" )
Check the file (F5)
Carefully check the displayed information before importing the phrases. Make sure you import to the passive CED or TDCLE library, the versions are correct and no errors are displayed.
If necessary approve the message "Date of phr. lib. to be imported is identical to date of
current library", this is just for your information.
However if the file you want to import is older than the library in your system, you can not
import it. Please make sure you have chosen the correct import file. In section upload files
you can also find information on how to change the header data of your import files.
Choose "Transfer/start time" (F6)
Choose "Immediate" or specify a time
Save
Note
For the TDCLE phrase library you have the choice to import either a single unicode
file including all languages, except for American English and Canadian French, or
separate import files based on the language group.
Due to the size of the phrase library and technical limitations with the phrase import
functionality, the option of a single import file for all languages is currently not available for the CED library.
Phrase import files for CED and TDCLE libraries include all phrases of the library,
not only those that are new or updated. Please be aware that all manual changes
made in your CED or TDCLE phrases will be overwritten.
Caution
Please do not set the flag for full import as this will delete your
passive library!
100
SAP AG
How To ...
A.8. 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:
101
SAP AG
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.
102
SAP AG
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 thousand phrases at one time. Therefore, we strongly recommend that only a part of the
phrase library is merged at one time (e.g. filtered by phrase groups or phrase keys).
A.9. 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)
103
SAP AG
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 maintenance contracts for SAP EHS Regulatory Content - expert rules for substance and mixture
classification or - substance lists and reference data receive the latest tree as part of their
104
SAP AG
How To ...
regular maintenance. Should you need any additional info on this topic please feel free to
contact us.
A.10. How to combine/retire phrases

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

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

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

HKEY_CURRENT_USER\Software\EHS-AddOns\Systems
HKEY_CURRENT_USER\Software\EHS-AddOns\Instances
HKEY_CURRENT_USER\Software\EHS-AddOns\Open Content Connector
A.11.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.12. How to extend entry in secondary data determination

In the example at the bottom you can see the typically used entries for secondary data determination with Expert rule sets and OCC data loads. The required entries for the specific rule
sets are explicitly given in the functional description of the rule set and in the appendix for SAP
EHS Regulatory Content - substance lists and reference data.
107
SAP AG
How To ...
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.

The following environment parameters must be set up for the reference modules
C1E5_SUB_EXPERT_EVALUATE:
EXPERT_COMMIT_MODE
Specifies the backup mode for secondary data determination by the EHS Expert.
If you enter the value I, the SAP system creates the new data records that were determined
by the EHS Expert without changing other data records.
If you enter the value D, the SAP system deletes all the existing data records and creates
the newly determined data. If the EXPERT_RES_BY_SRSID_OWNID_FLG parameter is
set, then only those data records are deleted that were determined during previous runs of
the EHS Expert. Using the data origin (parameter EXPERT_WRITE_SOURCE_ID) and the
data provider (parameter EXPERT_WRITE_OWNER) the SAP system recognizes which
data was determined previously by the EHS Expert.
Note
You can determine the address number of the data provider in Customizing for Basic
Data and Tools in the IMG activity Specify Authorization Groups. To do this, call the
input help for the Data prov. field in the IMG activity. You will find the value you require
in the Addr. no. field. The address number is not displayed in address management
in the Product Safety component.
If you enter the value C the SAP system resets the active indicator for the newest of the
data records and deletes all other existing ones. The number of data records to be deactivated can be derived from the parameter EXPERT_NUM_OF_DEACT_VALUATION.
The data records that were newly determined by the EHS Expert are also created. If the
EXPERT_RES_BY_SRSID_OWNID_FLG parameter is set, then only those data records
are deleted that were determined during previous runs of the EHS Expert. This helps
108
SAP AG
How To ...
you prevent data records being deleted inadvertently. The SAP system uses the data origin (parameter EXPERT_WRITE_SOURCE_ID) and the data provider (parameter
EXPERT_WRITE_OWNER) to recognize which data was determined previously by the EHS
Expert.
EXPERT_DESTINATION
Corresponds with the name of the RFC destination that is entered under Tools -> Administration -> Administration -> Network -> RFC Destinations (transaction SM59) (for example
EHS_EXPERT).
EXPERT_READ_RATING and EXPERT_READ_VALIDITY_AREA
Determine the rating and validity area for which the data is transferred from the SAP system
to the EHS Expert.
EXPERT_WRITE_RATING and EXPERT_WRITE_VALIDITY_AREA
Determine the rating and validity area with which the data determined is stored in the SAP
system. In the EHS Expert set of rules you can also specifically define a different rating and
validity area that are used when storing data in the system.
EXPERT_READ_USAGE_1...n and EXPERT_WRITE_USAGE_1...n
These parameters can be used in addition to the two previous parameter pairs. You can
specify any number of usages in the format VACLID/RVLID/EXCLFLG (rating/validity/exclude indicator). The parameter numbering has to start with 1 and has to be consecutive.
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.
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
109
SAP AG
How To ...
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.
If you enter the value S (default), the SAP system displays the Determine Secondary Data dialog box in display mode when starting secondary data determination using the EHS
Expert.
If you enter the value E you can revise the environment parameters in the Determine Secondary Data dialog box when starting secondary data determination using the EHS Expert.
The environment parameters you specified in Customizing are displayed as default values.
If you enter the value H the SAP system does not display the Determine Secondary Data
dialog box when starting secondary data determination using the EHS Expert.
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 Authorization Groups). If the SAP system does not find any data providers there, it creates the data
without a data provider.
EXPERT_HIDDEN_PROCESSING_MODE
You can choose between two operating modes.
ONLINE (default): The EHS Expert run starts immediately after you choose Execute.
BACKGROUND: The EHS Expert runs as a background job. The indicator for the parameter
EXPERT_ASK_FOR_STARTTIME must be set for the start time prompt.
EXPERT_ASK_FOR_STARTTIME
If you set this indicator, you will be prompted in a dialog box when the EHS Expert is to start
as a background job.
EXPERT_ADD_PARAM_1...n
110
SAP AG
How To ...
You can pass any number of parameters to the set of rules. This means you can make sets
of rules configurable. In the set of rules you must create a fact for this purpose that is mapped
to the external ID P:I_TAB_PARAM in fact mapping.
EXPERT_WRITE_RUN_DATE
With this parameter, the Expert will write the current date with each run of
the given Expert rule: Enter the value X here, and set the further parameters EXPERT_EXPLANATION_ESTCAT, EXPERT_EXPLANATION_RULE_PROP, and
EXPERT_EXPLANATION_DATE_PROP as described below.
You set up the explanation component (optional) of the EHS Expert using the following parameters:
EXPERT_EXPLANATION_DISPLAY
If you set this parameter to X and allow the set of rules to run in the foreground, the system
displays the explanation immediately after the set of rules run. For sets of rules that run in
the background, the system does not display the explanation automatically.
EXPERT_EXPLANATION_SAVE
Set this parameter to X if you want to save the explanation for the set of rules run in the
specification. If you set the parameter to X, you must also edit the following parameters:
EXPERT_EXPLANATION_ESTCAT
In this parameter you specify the value assignment type in which the explanation is to be
saved as a user-defined text. The standard version of the demo sets of rules contains the
entry SAP_EHS_0101_002. This value assignment type is not in a property tree because
the explanation is not displayed as a user-defined text but in the menu.
EXPERT_EXPLANATION_RULE_PROP
In this parameter you specify the characteristic in which the name of the set of rules is
saved to allow its assignment when displayed at a later stage. The characteristic must be in
the same value assignment type as the user-defined text for the explanation. The standard
version of the demo sets of rules contains the entry SAP_EHS_0101_002_RULESET.
Note
If you run a master data match up, the system automatically appends a phrase set
and a check module to the characteristic. You must remove this check module again.
EXPERT_EXPLANATION_DATE_PROP
In this parameter you specify the characteristic in which the current date is written with each
rule run. The characteristic must be in the same value assignment type as specified in the
parameter EXPERT_EXPLANATION_ESTCAT. The standard version of the demo sets of
rules contains the entry SAP_EHS_0101_002_RUN_DATE. The last run date is only written
when triggered separately with the parameter EXPERT_WRITE_RUN_DATE.
EXPERT_EXPLANATION_TEXTCAT
In this parameter you specify the user-defined text type with which the explanation is to be
saved in the specification. The standard version of the demo sets of rules contains the entry
EX.
EXPERT_ADD_PARAM_1
111
SAP AG
How To ...
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
In this parameter you can specify a second identifier that OCC should use when looking for substance data. This is identifier is only used when the identifier specified in
EXPERT_TAB_FIELD_2 does not give a search result. The main purpose is for loading data
that is not assigned to CAS numbers.
Typical Example Expert Rule set:

Sample value
EXPERT_COMMIT_FLG
EXPERT_COMMIT_MODE
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
EXPERT_EXPLANATION_TEXTCAT
EX
EXPERT_READ_RATING
PUBLIC
REG_WORLD
EXPERT_RULE_SET
ZEXP_GHS
EXPERT_WRITE_OWNER
112
SAP AG
How To ...
EXPERT_WRITE_RATING
PUBLIC
ZEXP_GHS
REG_WORLD
Typical Example OCC data load:

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

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

To add new data origins use transaction "spro" for the IMG customizing. Navigate to Environment, Health & Safety ->Basic Data and Tools -> Specification Management -> Additional Information for Value Assignment -> Specify User-Defined Text Types.
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.15. How to add data origins

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

Enter the Data Origin (limited to 10 characters)
Optionally you may assign an Exchange Profile
Give a note / description
Save your settings
A.16. How to add regulatory lists

114
SAP AG
How To ...
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.17. How to add literature sources

Enter the sources and assign a specification category to each source. You can assign the
source key as required.
You can create new sources at any time, even in a productive system, from the EHS menu by
choosing Basic Data and Tools -> Tools -> Current Settings -> Specify Sources.
Or : Start IMG customizing with transaction "spro".
Navigate to Environment Health and Safety -> Basic Data and Tools ->Specification Management -> Additional Information for Value Assignment -> Specify Sources.

Enter the new source ID (limited to 10 characters) and additional information
Switch to the left navigation sidebar and double click on the "Specification Category" entry.
Pressing F5 or "New Entries" you can enter the Specification category like "SUBSTANCE".
115
SAP AG
How To ...
A.18. How to add identifier types

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

SAP EHS offers wide customizing options regarding dangerous goods master data. Maintenance of these customizing settings is done in transaction SPRO at Environment, Health and
Safety - Dangerous Goods Management - Basic Data and Master Data. Here there are three
further sub-nodes, Common Settings, Basic Data, and Master Data, each consisting of multiple customizing items. In the following those customizing activities that may be relevant are
described in detail.
A.19.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:
117
SAP AG
How To ...

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

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

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

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

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

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

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

Management - Basic Data and Master Data - Common Settings - Specify Packing Instruction
Numbers: (these entries are just used in RiscClssification for creation of transport documents)
Enter the DG regulation the packing instruction number shall be relevant for
Enter the packing instruction number and a description
118
SAP AG
How To ...
Save your settings
A.19.6. Categories of Instructions for Enclosure and Instructions for Enclosure

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

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

The validity area determines in which jurisdictions values assigned to specifications apply. You
specify validity areas depending on the validity area categories. You can use the validity area
categories to define plants, business areas or regions, for example, as validity areas. You can
assign individual jurisdictions or organizational units at a lower level to each validity area, for
example:
You can assign countries and regions from the country table as validity areas for validity areas
of the category REGION. You can assign other organizational units for validity areas of another
category.
The definition of validity areas is closely linked to the requirements for reports. The validity
areas for this IMG activity are also used in the R/3 component Dangerous Goods Management.
Caution
Be aware, that the validity area "REG_WOLRLD" is "empty" and
has the default behaviour to recognize all countries.
Once you have used a validity area in a productive system, it can
no longer be deleted.
Newly created validity areas are not evaluated correctly by the
Expert before restarting the Expert Server.
119
SAP AG
How To ...
Go to the IMG customizing ("spro"):
Navigate to Environment, Health and Safety -> Basic Data and Tools -> Additional Information for Value Assignment -> Usage ->Specify Validity Areas.
Press F5 or "New Entry" and enter the Validity area category (e.g. REGION) and the new
area as well as the description. Mark the entry and switch to the navigation sidebar
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.
120
SAP AG
How To ...
A.21. How to setup/update XML substance

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

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

Data:
<path to XML substance database>\CLEO\
main folder with index file and version info

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

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

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

We recommend replacing the mapping database with the new version included in your update package as additional phrases and regulatory lists are added in the phrase mapping
table. If you have already made your own changes to the mapping database, e.g. renamed
identifiers or phrase mapping changes, please contact us and we will support you in updating
your database. If your active phrase library is different than CUST, changes to the mapping
database as specified above are required.
123
SAP AG
How To ...
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 A.23, How to
configure EHS OCC for details.
Repeat the above steps for all installations of the SAP EHS Regulatory content - substance
lists and reference data mapping database if you are using more than one mapping database
or if each user has a local copy of the mapping database.
Note
We recommend to create a backup copy of your existing mapping database before
overwriting it with the new version of the mapping database.
Tables of the mapping database
ExpRecordMap: Property Mapping

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

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

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

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"
126
SAP AG
How To ...
A.24. 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.
127
SAP AG
How To ...
The first three fields together form a unique identifier for the fact in the set of rules.
A.25. How to adjust the Record Mapping

The record mapping table contains the settings for mapping records in the set of rules or OCC
to value assignment types in EHS.
Table Fields in the Record Mapping Table (ExpRecordMap)
Table Field
Meaning
Internal_Id
Name of the record in the set of rules / OCC XML file
Group
Optional assignment of the record to a composition in the set of rules
External_Id
Name of the assigned value assignment type in EHS
Descriptions
Description text for the record
Options
The first two fields together identify the record uniquely in the set of rules.
A.26. How to adjust the Phrase Mapping

The phrase mapping table contains the regulations for mapping phrase codes used in the set
of rules or OCC XML files to phrase keys in EHS.
Note
Phrase mapping allows an assignment to be made between an internal and an external
value for any fact value. The phrase does not have to be an EHS phrase. The corresponding conversion takes place if the IsPhrase indicator is set in fact mapping.
Expert generates a warning message if the rule set or OCC reads phrases which are
not contained in the Mapping table.
Table Fields in the Phrase Mapping Table (ExpPhraseMap)
Table Field
Meaning
Internal_Id
Phrase code in the set of rules. The rule editor uses a special syntax for
phrase codes to distinguish them from normal texts. For this purpose the
phrase codes are enclosed in square brackets and number signs, for example [#R20#] .
External_Id
Phrase key in EHS
Phrasetext
Phrase text
Options
In some cases it might be necessary to enhance/adapt the phrase mapping manually.
Customer specific phrases

The phrase mapping table has to be enhanced if a customer uses additional customer specific
phrases.
To suppress the warning message these phrases have to be added manually to the phrase
mapping table.
128
SAP AG
How To ...
Tip
We recommend to insert these phrases using the following pattern:
Internal_Id: <Catalog name>-<Phrase key> , e.g. CUST-N09.00101280
External_Id: <Catalog name>-<Phrase key> , e.g. CUST-N09.00101280
To consider these enhancements for updates of the standard mapping you should label
these manual settings in the database e.g. in the Version column.
Customer specific phrase catalogue

The first part of the phrase key (column: External_Id) always signifies the active phrase catalogue in EHS.
The default phrase mapping is based on the CED Phrase Catalogue.
The default value for the active phrase catalogue is CUST.
If the active phrase catalogue in the EHS system is named differently then the mapping has
to be changed (using the replace function in MS Access).
A.27. SAP EHS Regulatory Content - substance

lists and reference data (Product Safety) Update
Data Load
A.27.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.27.2. Update Cached Data

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

For the new lists added with this release, please check the filter settings and change the standard filter settings if required. The default is that new lists will be added to your standard filter
settings as to be loaded.
After reviewing the filter settings, you can define these as the new standard by clicking the
"Default" button.
A.27.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 ...
130
SAP AG
How To ...
2. Specify the path to the file cleo_update_2010-1.txt which can be found in folder 6-UpdateTools.
3. Combine with any other search option, e.g. SUBID or identifiers and execute the search.
4. A hit list of all list substances will be created that potentially have new or updated regulatory
data available.
131
SAP AG
How To ...
5. We recommend saving the created hit list so you have it available in the future without rerunning the query.
Note
Starting with update 2010-1, we also provide a file cleo_new_group_assignments.txt.
This file can be used in the same way as described above, however it generates a list
of substances with new group assignments compared to the last release.
Note
For performance reasons, we are only checking the changes on a per substance level
not on single data sets. As a result you may have substances on your hit list for which
you do not get any new or changed data when you try to load them. This is the case if
You have not licensed all regional packages for SAP EHS Regulatory Content - substance lists and reference data and the changes are in an area you have not licensed.
You have switched off certain lists/regions in your filter settings; changed data therefore will not be displayed.
You have decided not to load certain data and/or groups in the past for this substance, if the change is in one of these data sets, it will not be displayed.
A.27.5. Simulate Data Load

Based on the generated hit list we recommend to simulate the data load first, before you start
loading updates. The simulated update will be exported to a spreadsheet which you can then
use to analyze the changed data for potential impact.
1. Create a hit list of substances either manually or as described in the last chapter of this
guide.
2. Select (all) substances
3. Start the secondary data determination and choose CLEO Product Safety (or a comparable
entry available in your system)
->Utilities -> Secondary Data -> Determination -> CLEO Product Safety
4. Select a substance and press "Set Filters"
132
SAP AG
How To ...
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, 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.27.6. Analyze Changed Data

SAP offers a template for Microsoft Excel which allows a first analysis of the new and changed
list substance data. If the template is not installed on your computer, please follow the steps
described in the SAP EHS Regulatory Content Administration manual or contact us for further
information.
1. Open Excel and create a new spreadsheet using the installed cleo_simulation.xlt as a template:
2.
3.
4.
5.
6.
-> File -> New -> New from template -> General Templates -> cleo_simulation.xlt
When prompted, enable macros
Open the spreadsheet with the new and revised list substance data you created during the
data load simulation if it is no longer open
Click the button Import OCC Data. The tool will check for any open OCC simulation file
and ask for your confirmation to import the data. If no spreadsheet with OCC data is found,
please either copy the data manually or open the correct file (starting with occSimu_*.csv)
Click the button Start Analysis to analyze the imported OCC data.
Save the new spreadsheet
The Simulation spreadsheet offers some functionality for a first analysis of new and changed
data:
Two lines per dataset, the first one (white background) is the new SAP EHS Regulatory
Content data. The second line (grey background) is existing data in SAP EH&S
133
SAP AG
How To ...
Pairs of related data are assigned a unique record number in column A, e.g. 1_CLEO and
1_EHS
In column "Mode" each record is marked as either new, changed or inactivated
Filter options for all fields, e.g. by property or regulatory list
New records are highlighted bold red (complete line)
In changed records, only important changes are highlighted bold red
Inactivated records are highlighted in italics (complete line)
In the top right corner a summary is given (number of substances and records)
Explanation of some fields:
Column A: Unique record number for pairs of related data, e.g. 1_CLEO and 1_EHS
Column B: Substance ID of SAP EH&S (SubID)
Column C: Group ID of SAP CLEO => Data is from a generic group, not for the substance
itself
Column E: Mode - "New" , "Change" or "Inactivated"
Column F: Property - this is the property or identifier with the new/changed data
Column H: CAS number or identifier type
Column I: Name of the substance
Example A.1. 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.27.7. Load Changes to SAP EH&S

There are two different options to load new and changed data into your existing list substances
in SAP EH&S.
If only a few substances need to be updated or if you want to exclude some data from being
updated, the manual process is the best choice.
134
SAP AG
How To ...
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.27.7.1. Manual update load

A manual update load is almost identical to an initial data load, except for two differences:
The option " Load Changes Only " is set and you can compare the new data with the already
existing data in SAP EH&S directly in OCC.
1. Create a hit list of substances either manually or as described in Section A.27.4, Hit List
of List Substances
4. If you have selected more than one substance, select a substance from the following screen
and press "Set Filters"
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.27.7.2. Mass Load / Autoload

The autoload functionality is different from a standard load as no user interactivity is possible
after a choice of options and filters/regulatory lists was made. All changed and new data will
be automatically loaded into the existing list substances in SAP EH&S.
1. Create a hit list of substances either manually or as described in Section A.27.4, Hit List
of List Substances
4. Select a substance from the following screen and press "Set Filters"
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.
135
SAP AG
How To ...
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.28. SAP EHS Regulatory Content - substance

lists and reference data (Dangerous Goods) Update Data Load
A.28.1. Review Regulatory Changes
The Release Notes for SAP EHS Regulatory Content - substance lists and reference data for
Dangerous Goods include a brief overview of the new and modified regulations in this version.
All documents are available in folder 0-Documentation. This information should be reviewed
prior to continuing the update process.
A.28.2. Update Cached Data

Start OCC for SAP EHS Regulatory Content - substance lists and reference data (Dangerous
Goods) for any UN listed 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.28.3. Review New Filter Settings

We added the DG regulations ADN and deleted ADNR with this release please review your
filter settings for OCC.
A.28.4. Analyze Changed Data

We provide an Microsoft Access database with a summary of all changes made in the last
update. The database cleo_dg_changes_2011-1.mdb can be found in folder 0-Documentation.
Check for changed UN numbers

Table Changes gives a summary of all updated UN numbers and a comparison of all
changes made
136
SAP AG
How To ...
Table Customer UN Numbers allows you to maintain a list of UN numbers you are using
Query Impact Analysis gives you an overview which of the UN numbers currently in use are
affected by the changes if the table Customer UN Numbers is maintained
Check for deleted variants

A number of classification versions are omitted in the updated regulations and now we deleted
all the variants in our database. In all the cases you are using these deleted variants it is
necessary to replace the listed substance now.
You can search Table Changes or the result of the impact analysis for all deleted variants.
A.28.5. 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.
With this release we added the new regulation ADN and removed ADNR. So please revise all
your specifications affected. Load a new ADN instance and delete the ADNR instance.
We harmonized the unique IDs of RID and ADN instances with ADR in this release. It might
happen that OCC during load do not recognize the present RID instance and a new one is
loaded additionally. In this cases you should delete the old RID instance, so that the specification do not show two instances of the same regulation.
A.28.5.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.
1. Create a hit list of substances
3. Start the secondary data determination and choose CLEO Dangerous Goods (or a comparable entry available in your system)
->Utilities -> Secondary Data -> Determination -> CLEO Dangerous Goods
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 "Use Substance Groups"
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.
137
SAP AG
How To ...
10.Save data to EH&S
A.28.5.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
3. Start the secondary data determination and choose CLEO Dangerous Goods (or a comparable entry available in your system)
->Utilities -> Secondary Data -> Determination -> CLEO Dangerous Goods
4. Select a substance from the following screen and press "Set Filters"
5. Set data options "Load Changes Only" and "Use Substance Groups"
7. Select the "Autoload" button
Note
If a new variant or regulation was assigned to a UN number, the new data 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 expert.
If new or changed data becomes available within an existing group/DG variant, your
choices in the past decide if the data will be loaded::
If a group/variant was loaded in the past, all new and changed data will be loaded
as well.
If a group/variant was set to "no load" in the past, new and changed data will be
ignored and not loaded.
A.29. How to add user-defined DG texts

User-defined dangerous goods texts are regulation-dependant and may be assigned to specific dangerous goods user-defined text profiles. The dangerous goods user-defined free texts
themselves are phrases, whereas those phrases written by the standard expert rule DangGoods are CED standard phrases delivered with the CED phrase library. If further dangerous
goods user-defined texts are required, additional phrases need to be created.
To specify dangerous goods user-defined text profiles, use transaction SPRO, choose SAP
Reference IMG and navigate through the activities tree to Environment, Health and Safety Dangerous Goods Management - Basic Data and Master Data - Common Settings - Specify
Profiles for User-Defined Dangerous Goods Texts:
Press F5 or select "New Entries"
Enter the respective DG regulation, a unique number for the profile and a description for
the profile
138
SAP AG
How To ...
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.30. 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.
A.31. 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.
139
SAP AG
How To ...
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.
A.32. How to register rule sets

140
SAP AG
How To ...
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
3. Save you settings by Apply
141
SAP AG
How To ...
A.33. How to adjust external table values

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

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

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

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

in EHS
Descriptions
Description text for the composition
Options
A.35. How to use the History.mdb

The History database gives the user information and overview on changes applied to the mapping 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.
143
SAP AG
How To ...
Changes_in_external_table____GHS_table
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.36. 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.
144
SAP AG
How To ...
A.37. How to import report templates

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

WWI will automaticly open the new template document. Check the template by clicking on the
check-button and save it.
A.38. 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.
145
SAP AG
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.
146
SAP AG

SAP EHS Regulatory Content Update Guide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP EHS Regulatory Content Update Guide

Uploaded by

Copyright:

Available Formats

SAP EHS Regulatory

Content Update Guide