SAP EHS Regulatory Content Update Guide

SAP EHS Regulatory
Content Update Guide

SAP EHS Regulatory Content Update Guide
Version 1901
Publication date January 2019

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

1. Introduction ....................................................................................................................... 1
1.1. Objective ................................................................................................................ 1
1.2. How to use this guidance document ..................................................................... 1
1.2.1. Structure of this manual .............................................................................. 1
1.3. Security/Authorization ............................................................................................. 2
1.4. Support ................................................................................................................... 2
2. Update ............................................................................................................................... 3
2.1. Update Prerequisites .............................................................................................. 3
2.2. Update overall procedure ....................................................................................... 4
3. Property Tree .................................................................................................................... 6
3.1. Property Tree Update ............................................................................................ 6
3.1.1. Update Procedure ....................................................................................... 6
3.1.2. Contents of Latest SAP ERC Property Tree Package ................................. 7
3.1.2.1. File overview property tree package Product Safety ........................ 7
3.1.2.2. File overview corrections to previous property tree package ............ 8
4. SAP EHS Regulatory Content - multilanguage phrase library for hazard communica-
tion ......................................................................................................................................... 9
4.1. Check Update ........................................................................................................ 9
4.1.1. Checking Procedure .................................................................................... 9
4.1.2. Settings to implement the Multilanguage Phrase Library (Standard) ........... 9
4.1.2.1. File Overview .................................................................................... 9
4.1.3. General Settings ........................................................................................ 10
4.1.3.1. Language keys ............................................................................... 10
5. SAP EHS Regulatory Content - substance lists and reference data ............................... 11
5.1. Check Update ...................................................................................................... 11
5.1.1. Check List Update Product Safety ............................................................ 11
5.1.2. Settings to update the Substance Lists and Reference Data (Product
Safety) ................................................................................................................. 12
5.1.2.1. File Overview .................................................................................. 12
5.1.2.2. Other Settings ................................................................................. 13
5.1.3. Check List Update Dangerous Goods for SAP EHS ................................. 14
5.1.4. Settings to update the regulatory data (Dangerous Goods for SAP
EHS) .................................................................................................................... 15
5.1.4.1. File Overview .................................................................................. 15
5.1.4.2. Other Settings ................................................................................. 16
5.1.5. Check List Update Dangerous Goods for SAP Transportation Manage-
ment ..................................................................................................................... 16
5.1.6. Settings to update the regulatory data (Dangerous Goods for SAP
Transportation Management) ............................................................................... 15
5.1.6.1. File Overview .................................................................................. 16
6. SAP EHS Regulatory Content - expert rules for substance and mixture classification
.............................................................................................................................................. 17
6.1. Check Update ...................................................................................................... 17
6.1.1. Check List ................................................................................................. 17
6.1.2. Settings to update the licenced rule set package(s) .................................. 18
6.1.2.1. File Overview .................................................................................. 18
6.1.2.2. File Overview .................................................................................. 19
6.1.2.3. File Overview .................................................................................. 20
6.1.2.4. File Overview .................................................................................. 38
6.1.2.5. File Overview .................................................................................. 39
6.1.2.6. File Overview .................................................................................. 40
6.1.2.7. Settings in Admin Tool .................................................................... 40
INTERNAL: SAP CUSTOMER iii © SAP SE

6.1.2.8. Settings in Admin Tool - Sub Rules ................................................ 53

6.1.2.9. User Exit Settings ........................................................................... 55
6.1.2.10. Other Settings ............................................................................... 55
7. MSDS Templates ............................................................................................................ 56
7.1. Check Update ...................................................................................................... 56
7.1.1. Checking Procedure .................................................................................. 56
7.1.2. Settings to update the MSDS Template for EMEA .................................... 56
7.1.2.1. File Overview .................................................................................. 56
7.1.2.2. Other Settings ................................................................................. 62
A. How To ... ....................................................................................................................... 64
A.1. How to upload property tree transports files ....................................................... 64
A.2. How to upload files .............................................................................................. 65
A.3. How to import transport requests ........................................................................ 65
A.4. How to allocate phrase sets ................................................................................ 67
A.5. How to create WWI report symbols ..................................................................... 69
A.6. How to set up the Table-based Value Assignment .............................................. 70
A.7. How to check and extend copy/inheritance templates ......................................... 76
A.8. How to import phrases ........................................................................................ 76
A.9. How to merge phrases ........................................................................................ 78
A.10. How to import phrase set assignments ............................................................. 80
A.11. How to combine/retire phrases .......................................................................... 82
A.11.1. Combining Duplicate Phrases ................................................................. 82
A.11.2. Retired Phrases ...................................................................................... 83
A.12. How to install EHS OCC ................................................................................... 84
A.12.1. Initial Installation/Upgrading of older OCC versions ................................ 84
A.13. How to extend entry in secondary data determination ....................................... 84
A.14. How to manage user exits ................................................................................ 90
A.15. How to add user defined text types ................................................................... 91
A.16. How to add data origins .................................................................................... 91
A.17. How to add regulatory lists ................................................................................ 92
A.18. How to add literature sources ........................................................................... 92
A.19. How to add identifier types ................................................................................ 93
A.20. How to add dangerous goods master data ....................................................... 95
A.20.1. Dangerous Goods Classes and Classification Codes ............................. 95
A.20.2. Risk Potentials ........................................................................................ 95
A.20.3. Hazard Identification Numbers ................................................................ 96
A.20.4. Danger Labels ......................................................................................... 96
A.20.5. Packing Instruction Numbers .................................................................. 96
A.20.6. Categories of Instructions for Enclosure and Instructions for Enclosure
.............................................................................................................................. 96
A.20.7. Packing Codes ........................................................................................ 96
A.21. How to add validity areas .................................................................................. 97
A.22. How to setup/update XML substance database for substance lists and refer-
ence data ..................................................................................................................... 98
A.23. How to setup/update mapping database for SAP EHS Regulatory Content -
substance lists and reference data ........................................................................... 100
A.24. How to configure EHS OCC ............................................................................ 102
A.25. How to adjust the Fact Mapping ...................................................................... 105
A.25.1. Adjusting Fact Mapping to Load a CAS Number .................................. 106
A.26. How to adjust the Record Mapping ................................................................. 106
A.27. How to adjust the Phrase Mapping ................................................................. 106
INTERNAL: SAP CUSTOMER iv © SAP SE

A.28. SAP EHS Regulatory Content - substance lists and reference data (Product
Safety) Update Data Load ........................................................................................ 107
A.28.1. Review Regulatory Changes ................................................................ 107
A.28.2. Update Cached Data ............................................................................ 108
A.28.3. Review New Filter Settings ................................................................... 108
A.28.4. Hit List of List Substances .................................................................... 108
A.28.4.1. Simulate Data Load ................................................................... 110
A.28.4.2. Analyze Changed Data .............................................................. 111
A.28.4.3. Load Changes to SAP EH&S .................................................... 112
A.29. SAP EHS Regulatory Content - substance lists and reference data (Danger-
ous Goods) Update Data Load ................................................................................. 114
A.29.1. Review Regulatory Changes ................................................................ 114
A.29.2. Update Cached Data ............................................................................ 114
A.29.3. Review New Filter Settings ................................................................... 114
A.29.4. Analyze Changed Data ......................................................................... 114
A.29.5. Load Changes to SAP EH&S ............................................................... 115
A.29.5.1. Manual update load ................................................................... 115
A.29.5.2. Mass Load / Autoload ................................................................ 116
A.30. How to add user-defined DG texts .................................................................. 116
A.31. How to add a value assignment rating ............................................................ 117
A.32. SAP Setup for SAP EHS Regulatory Content Expert Rule Sets ...................... 117
A.32.1. Overview ............................................................................................... 117
A.32.2. Installation on the Test or QA Expert Server ......................................... 122
A.32.3. Installation on the Productive Expert Server ......................................... 123
A.33. How to load rule sets onto the Expert server .................................................. 123
A.34. How to register rule sets ................................................................................. 124
A.35. How to adjust external table values ................................................................ 126
A.36. How to adjust the Group Mapping ................................................................... 127
A.37. How to use the History.mdb ............................................................................ 127
A.38. How to setup identification listings .................................................................. 128
A.39. How to import report templates ....................................................................... 129
A.40. How to create generation variant .................................................................... 129
A.41. How to disclose component names ................................................................. 130
INTERNAL: SAP CUSTOMER v © SAP SE

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 send an e-mail to <Regulatory.Content@sap.com>.
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 Ad-
ministration manual as a step by step documentation of how to implement SAP EHS Regula-
tory 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 infor-
mation 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 infor-
mation related to current version of regulatory data.
INTERNAL: SAP CUSTOMER 1 © SAP SE

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.
The SAP Security Guides provide you with a collection of our guidelines and recommendations
pertaining to SAP system and SAP software security. These documents offer general guide-
lines for securing your SAP systems. Do keep in mind that additional factors are also very
important when securing your overall landscape, such as the usage of a variety of software
packages (SAP and non-SAP). Therefore, we highly recommend you analyze your own risks
and needs and establish your own security policy (or policies). These guides are intended to
assist you in this process, but cannot replace the need for your own customer-specific policies.
For the latest information on security updates see SAP Security Notes.
We strongly recommend to store the SAP EHS Regulatory Content in a restricted environment,
accessible only by authorized persons involved in content implementation or updates. For
further details regarding user authorization in your file system please see the user manual of
your operating system.
In SAP EHS access rights to SAP EHS Regulatory Content can be administrated via autho-
rization profiles. For further details we refer to “User and Role Administration of AS ABAP” and
“Roles for Environment, Health and Safety (EH&S)” in the SAP Library (http://help.sap.com).
1.4. Support
Issues with SAP EHS and SAP EHS Regulatory Content can be reported using the SAP One
Support Lauchpad https://launchpad.support.sap.com/.
Please select one of the following components to ensure fast assignment to the appropriate
subject matter expert.
• EHS-ERC for all incidents related to regulatory list data, phrases, Expert rules and WWI
templates
• EHS-BD-RDF-WWI for incidents related to WWI functionality (other than WWI templates)
• EHS-BD-TLS-OCC for incidents related to OCC functionality (other than regulatory data)
• EHS-BD-TLS-EXP for incidents related to EHS Expert functionality (other than ERC Expert
rules)

Chapter 2. Update
This chapter describes the prerequisites which are necessary to update your SAP EHS Reg-
ulatory Content.
2.1. Update Prerequisites

This chapter describes the overall prerequisites in order to update SAP EHS Regulatory Con-
tent. 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
568302).
• Please check if SAP note 1409995 is implemented to improve handling of identifiers in dif-
ferent languages
EHS WWI
• Current version of WWI
We recommend that you always apply the most recent patch for WWI, regardless of the
Support Package and EH&S version you are using.
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 addi-
tional system requirements.
1061242 EH&S: Availability and performance of WWI and Expert servers
1409995 EHS OCC: Using the ISO language code for Unicode data
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

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
1576098 EH&S standard WWI processing methods
1689850 Output of tunnel code for reports
820516 EH&S WWI: Include Template; Conditional Output
1381072 Phrase warning: Missing code/graphic as of ERP 6.0 EhP 3
1367148 needed if "no calculation" functionality of rule sets is used
1381072 Phrase warning: Missing code/graphic
1658925 EH&S WWI: Report bodies contain errors
1540754 Instance control for extended safety data sheets
1392418 Phrase collector: Output of collected phrases
1697543 EH&S WWI: Corrections in WWI SP28
2004802 Comp rule: Composition tree: Average value of ingredients
This list is not exhaustive but contains some general notes as well as important notes of the
last few months. Please check if the appropriate note is available for your EHS release.
2.2. 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

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

Chapter 3. Property Tree
3.1. Property Tree Update
The following steps describe how to Implement the newest property tree package and check
the implemented objects.
3.1.1. Update Procedure

Please use the following check list as guidance through the property tree update procedure.
Please find the information about delivered files and transports included in the latest property
tree package 1810 Product Safety below in the next section.
In order to make use of the latest Expert Rules, Substance Lists and Regulatory Data the
contents of the latest property tree package 1810 Product Safety and of the other existing
property tree packages have to have been implemented before implementing other content
of the ERC update 1810.
Property tree packages contain everything needed to set up and use the new and enhanced
characteristics and classes/properties added to SAP EH&S in an existing ERP 6.0 EHP3, ERP
6.0 EHP4, ERP 6.0 EHP5, ERP 6.0 EHP6, ERP 6.0 EHP7, or ERP 6.0 EHP8 system. More
details about the delivery of property tree enhancements can be found in SAP Note 1761696.
Please read the ReadMe document included in each property tree package carefully BEFORE
starting the implementation of any property tree package!
Status Where to do What to do

General
O Review documentation, especially ReadMe document
Technical Part
O SAP system (Transaction Upload files
CG3Z)
O SAP Transport Manage- Import transports
ment System (Transaction
STMS)
O SAP EH&S (Transaction Create phrase sets
CG1B)
O SAP EH&S (Transaction Match up master data
CGCZ with option "Match
up ValAss type and char.")
O SAP EH&S (Transaction Assign phrase sets to characteristics
CGAB)
O SAP EH&S (Transaction Activate phrase set assignment to characteristic
CGCZ with option "Acti-
vate Phrasing of Charac-
teristics")

Property Tree
O SAP EH&S (Transaction Create WWI symbols

CGCZ with option "Gener-
ate symbols")
O SAP EH&S Customiz- Update table based value assignment
ing (Transaction SPRO,
navigation: Environment,
Health & Safety -> Ba-
sic Data and Tools ->
Specification Management
-> Specification Database
Structure -> Settings for
Value Assignment -> Set
Up Table-Based Value As-
signment)
O SAP EH&S Specification Test properties and characteristics in the property tree
Data Base (Transaction STANDARD in the EH&S specification data base.
CG02)
O SAP EH&S (Transaction Check, if new properties need to be included in inheri-
CG02 Specification -> In- tance templates
heritance -> Edit Tem-
plates)
Detailed information on how to execute the single steps are provided in How-To-documents:
• Section A.1, “How to upload property tree transports files”

• Section A.3, “How to import transport requests”
• 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”
• Section A.7, “How to check and extend copy/inheritance templates”
3.1.2. Contents of Latest SAP ERC Property Tree Package

The contents of the delivery of property tree enhancements and corrections with ERC Update
1810 are described in the following sections. They are delivered on SAP Market Place in the
Folder "Update" where also the text document ReadMe_ERC_Property_Tree_Update.pdf with
more details about the update can be found.
3.1.2.1. File overview property tree package Product Safety

The following files are included in the delivery, that is in the zip-file EHS_Property_Tree_Pack-
age_1810_PS_V1-0.zip:
General Information
File name Description

ReadMe_EHS_Property_Tree_Package_1810_ Summary of installation steps (text docu-
PS.pdf ment)
Changes_EHS_Property_Tree_Package_1810_ Summary of new and enhanced properties
PS.pdf and characteristics included in this package
(text document)

Property Tree

Help_Texts_EN_EHS_Property_Tree_Package_ Summary of help texts in English (text docu-
1810_PS.pdf ment)
Help_Texts_DE_EHS_Property_Tree_Package_ Summary of help texts in German (text docu-
1810_PS.pdf ment)
Transports
Please note that for each transport two files are delivered: Files with names starting with a "K"
are the co-files, files with names starting with a "R" are the data files.
Order of Transport File names Description

import name
1 EBJK448579 K448579.EBJ, New and enhanced characteristics, classes,
R448579.EBJ value assignment types, and assignments to
the property tree STANDARD with German
descriptions. New and enhanced German
help texts.
2 NE5K902963 K902963.NE5, English descriptions for new and enhanced
R902963.NE5 characteristics, classes, and value assign-
ment types. New and enhanced English help
texts.
3.1.2.2. File overview corrections to previous property tree package

No corrections to the property tree package 1805 Version 1-0 are delivered.

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 - mul-
tilanguage phrase library for hazard communication.
4.1.1. Checking Procedure

Please use the following check list as guidance through the phrase library update procedure.

General
O Review documentation
Technical Part
O Customizing (SPRO) & Add user exit for automatic replacement of storage tem-
Phrase Management perature placeholder. Please see the ERC administra-
(CG12) tion manual in chapter Placeholder Phrases for details.
This is an optional step.
O SAP EHS (cg3z) Upload phrases
Upload phrase set assignments
O SAP EHS (cg31) Import phrases
O SAP EHS (cg31) Import phrase corrections
O SAP EHS (cg12) Merge phrases
O SAP EHS (cg31) Import phrase set assignments
Detailed information on how to execute the single steps will be provided in this How-To-doc-
uments:
• Section A.2, “How to upload files”

• Section A.8, “How to import phrases”
• Section A.9, “How to merge phrases”
• Section A.10, “How to import phrase set assignments”
• Section A.11, “How to combine/retire phrases”
4.1.2. Settings to implement the Multilanguage Phrase Li-

brary (Standard)
4.1.2.1. File Overview
The following files are included in the delivery. We recommend to use the Unicode files when
possible to avoid character conversion errors with the non-Unicode files. Non-Unicode files
will no longer be included. If you cannot use the Unicode files provided, please contact our
helpdesk.

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

01_documents
CED_Changes_1810.xlsx Excel file with an overview of new, changed and retired
phrases
CED_ReleaseNote_1810.pdf Release Note for current version
Phrase_Services_Proposals.xls Proposal template for customer suggestions
02_phrases
1_ced_1810_standard_complete.dat Phrase import file including all phrases in all standard
languages except US English (Z8) and Brazilian Por-
tuguese (Z9) for Unicode systems
1_ced_1810_standard_update.dat Phrase import file including revised and new phrases in
all standard languages
2_ced_1810_usenglish_Z8_ Phrase import file including all phrases in US English
complete.dat via Z8 customer correspondence language
2_ced_1810_usenglish_Z8_ Phrase import file including revised and new phrases in
update.dat US English (Z8)
3_ced_1810_brazilian_Z9_ Phrase import file including all phrases in Brazilian Por-
complete.dat tuguese via Z9 customer correspondence language
3_ced_1810_brazilian_Z9_ Phrase import file including revised and new phrases in
update.dat Brazilian Portuguese (Z9)
4_ced_1810_arabic_hebrew_ Phrase import file including all phrases Unicode Phrase
complete.dat import file Arabic and Hebrew
4_ced_1810_arabic_hebrew_ Phrase import file including revised and new phrases in
update.dat Arabic and Hebrew
03_psets
ced_1810_pset_complete.dat Complete phrase set assignments based on the latest
property tree; this file includes all assignments from pre-
vious releases and the new release
ced_1810_pset_new.dat New phrase set assignments based on the latest prop-
erty tree
4.1.3. General Settings

New functionality has been introduced to support the automatic replacement of the placeholder
for storage temperature. Please see the ERC administration manual in chapter Placeholder
Phrases for details. This is an optional step and is not required if you choose not to use the
automatic replacement functionality.
4.1.3.1. Language keys

No new language has been added with this update.
Based on feedback from our customers that there is no regulatory requirement for SDS in
Filipino, we have decided to stop the support of the Filipino (Tagalog) language. We will no
longer provide new translations into this language as part of our updates nor will we update
the existing translations in the future.

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.

General
O Documentation Review documentation
Technical Part
O Frontend Upgrade installation of Open Content Connector
O SAP EHS (cg3z) Upload customizing transports
Upload phrases
O SAP EHS (stms) Import customizing transports
O SAP EHS (cg31) Import substance lists and reference data phrase library
O SAP EHS (cg12) Merge phrases to active catalogue
O SAP EHS (cg31) Import phrase sets
O XML File storage (local, Update database XML files using the database setup
network drive) file
O 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
O SAP EHS / OCC Update cached data
O SAP EHS / OCC Review new filter settings
O SAP EHS (cg02) Generate hit list of changed list substances
O SAP EHS (cg02) Generate hit list of list substances with new group as-
signments
O SAP EHS / OCC Simulate data load
O MS Excel Analyze new & changed data
O SAP EHS / OCC Load changes to SAP EHS

SAP EHS Regulatory Content - sub-
stance lists and reference data
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.12, “How to install EHS OCC”

• Section A.13, “How to extend entry in secondary data determination”
• Section A.22, “How to setup/update XML substance database for substance lists and refer-
ence data”
• Section A.23, “How to setup/update mapping database for SAP EHS Regulatory Content -
substance lists and reference data”
• Section A.25, “How to adjust the Fact Mapping”
• Section A.26, “How to adjust the Record Mapping”
• Section A.27, “How to adjust the Phrase Mapping”
• Section A.28, “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:
ProductSafety

0-Documentation
ERC_1901_changed_phrases.xlsx Overview of new and revised phrases
Availability of the content reports depends on the li-
censed ERC package:
ERC_ContentReport _ Content Report Inventories Data
Inventories.pdf
ERC_ContentReport_Americas.pdf Content Report American Data
ERC_ContentReport_APJ.pdf Content Report Asia-Pacific Data
ERC_ContentReport_EMEA.pdf Content Report Europe, Middle-East & Africa Data
ERC_ContentReport_SDS- Content Report SDS Authoring Package
Authoring.pdf
ERC_ContentReport_ Content Report Marketability Package
Marketability.pdf
ERC_PS_Data_ReleaseNote_1901.pdf Latest Substance Lists and Reference Data Release
Note for Product Safety
ERC_PS_Training_EN.pdf SAP EHS Regulatory Content Training Workshop Pre-
sentation

ERC_ListOverview_1901.xlsx Overview of lists by region and country and assignment

to properties
TLV_Stmt_of_Position.pdf ACGIH® Statement of Position Regarding the TLVs®
and BEIs®
JSOH_Characteristics_of_OELs _ Japan Society of Occupational Health - Additional infor-
and_Instructions_for_Users.pdf mation regarding OEL values
1-OCC
readme.txt Info file on how to obtain OCC
2-Customizing\Update
Note: If you have already implemented the customizing
transports from ERC 1810, the following transports are
not needed as they do not include any additional cus-
tomizing.
customizing_overview.txt Overview of customizing transports
K902915.NE5 Customizing transport with additional regulatory lists,
sources and identifier types (Unicode)
R902915.NE5 Customizing transport with additional regulatory lists,
sources and identifier types (Unicode)
3-Phrases
1_erc_1901_unicode.DAT Unicode phrase import file (all languages)
2_erc_1901_usenglish _ Unicode Phrase import file US English (only import if
unicode.DAT you use Z8 for US English)
3_erc_1901_brazilian _ Unicode Phrase import file Brazilian Portuguese (only
unicode.DAT import if you use Z9 for Brazilian Portuguese)
4_erc_1901_pset_unicode.DAT Unicode phrase set assignment import file
4-Database
ERC_PS_<Region>_1901.exe Substance Lists and Reference Data - Product Safety -
Database setup/update program
5-Mapping
td_cleo.mdb Substance Lists and Reference Data - Product Safety -
Mapping Database
6-UpdateTools
erc_new_group_assignments _ Update file to create hit list substances with new group
1901.txt assignments
ERC_simulation.xlt Template for simulation (MS Excel 97- 2003)
ERC_simulation.xltm Template for simulation (MS Excel 2007)
erc_update_1901.txt Update file to create hit list of changed list substances
5.1.2.2. Other Settings
No additional settings are needed for this release.

Note
No actions required for update from version 1810 to 1901.
5.1.3. Check List Update Dangerous Goods for SAP EHS

Please use the following check list as guidance through the update procedure of substance
lists and reference data for dangerous goods.
Dangerous Goods
All steps to import and merge phrases and phrase sets are just necessary if you use packaging
data.

General
O Documentation Review documentation
Technical Part
O Frontend Upgrade installation of Open Content Connector
O SAP EHS (cg3z) Upload phrases and customizing transports
O SAP EHS (stms) Import customizing transports
O SAP EHS (cg31) Import substance lists and reference data phrase library
for dangerous goods
O SAP EHS (cg12) Merge phrases to active catalogue
O SAP EHS (cg31) Import phrase sets
O XML File storage (local, Update database XML files using the database setup
network drive) file
O TD_CLEO_DG.MDB Update mapping database
Identify and consider customer made changes for the
updated mapping database
O Documentation Review release notes
O SAP EHS / OCC Update cached data
O MS Access Analyze new & changed 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.12, “How to install EHS OCC”



• Section A.22, “How to setup/update XML substance database for substance lists and refer-
ence data”
• Section A.23, “How to setup/update mapping database for SAP EHS Regulatory Content -
substance lists and reference data”
• Section A.29, “SAP EHS Regulatory Content - substance lists and reference data (Danger-
ous Goods) Update Data Load”
5.1.4. Settings to update the regulatory data (Dangerous

Goods for SAP EHS)
Updating your DG data please use the following files:
Files File Description

0-Documentation
ERC_DG_Data_ReleaseNote_1901.pdf Latest Substance Lists and Reference Data Release
Note for Dangerous Goods
ERC_DG_Regulations_Status_ SAP EHS Regulatory Content status of regulatory lists
1901.pdf overview
ERC_DG_Changes_1901.mdb Database with list of all changes and tool to analyze im-
pact on used UN No
ERC_DG_Data_Training.pdf Training overview on how to use DG data and OCC.
1-Customizing - Update
R903037.NE5 and K903037.NE5 ADN with pack data, update pack provisions
R903049.NE5 and K903049.NE5 ADN update classification code
R903055.NE5 and K903055.NE5 ADN update risk potential
R903039.NE5 and K903039.NE5 ADR with pack data, update pack provisions
R903051.NE5 and K903051.NE5 ADR update classification code
R903057.NE5 and K903057.NE5 ADR update risk potentia
R903041.NE5 and K903041.NE5 RID with pack data, update pack provisions
R903053.NE5 and K903053.NE5 RID update classification code
R903059.NE5 and K903059.NE5 RID update risk potential
2-Phrases
erc_dg_1901.dat phrase import file
erc_dg_pset_1901.dat phrase set assignment import file
3-Database
ERC_DG_1901.exe 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 pack-
ing data, without split by mode of transport for NA reg-
ulations
TD_CLEO_DG_with_split_without_ Dangerous Goods - Mapping Database, without pack-
pack.mdb ing data, with split by mode of transport for NA regula-
tions

The following customizing settings have to be enhanced/changed for this update:
Note
Please choose only one single MDB depending on your application
5.1.5. Check List Update Dangerous Goods for SAP Trans-

portation Management
Note
This chapter describes the Dangerous Goods solution for SAP Transportation Man-
agement. Users of SAP EHS Dangerous Goods can skip this chapter.
In the downloaded Package you can find a compressed ZIP file containing the content for
usage in SAP Transport Management. This file can be uploaded in the Content Import tool of
SAP Transportation Management without any processing steps from your side, e.g. unpacking
in your local file system.
5.1.6. Settings to update the regulatory data (Dangerous

Goods for SAP Transportation Management)
Updating your DG data please use the following files:

1-Customizing - Update
K903067.NE5 and R903067.NE5 Update of customizing entries used for new TM DG data
2-Database
TM_DG_1901.zip Archive with data files to be used by loading tool

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.

General
O Review documentation
Retired Rule Sets
Expert Server SAPSetup will remove retired rule sets from the expert
server. Before starting SAPSetup, check for which rule
sets the data shall be written as inactive. For these rule
sets follow the following procedure: backup the rule
sets, adapt the mapping to write the data as inactive
and reinstall the rule sets after the update of the expert
server with SAPSetup. Further details on retired rule
sets can be found below. If the data of these rule sets
will be deleted manually no action on the setup is re-
quired.
Technical Part
O Customizing (Transaction Create data origin
spro)
Create user exit(s)
Create regulatory list
O Mapping.mdbs If you have adapted the mapping databases of the pre-
vious version to your needs , identify changes in the
new mapping.mdbs and consider these for the update
of your mapping databases (see HISTORY.mdbs)
O Externvalues.mdbs If you have adapted the external values databas-
es 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)
O Expert Server or SAP EHS Use SAP Setup on the Ex-
(Transaction cgsadm) pert Server (SetupERC_<package>.exe (e.g.
SetupERC_GLOBAL.exe)) for installing the rule
set on the Expert Server. For more details see
Readme_SAPSetup_RuleSets

SAP EHS Regulatory Content - expert rules
for substance and mixture classification
OR alternatively the following three steps can be

done
...1) Upload rule set files
...2) Create new admin instance(s)
...3) Update existing admin instance(s)
O
Detailed information on how to execute the single steps will be provided in these How-To-
documents:
• Section A.16, “How to add data origins”

• Section A.13, “How to extend entry in secondary data determination”
• Section A.37, “How to use the History.mdb”
• Section A.35, “How to adjust external table values”
• Section A.36, “How to adjust the Group Mapping”
• Section A.32, “SAP Setup for SAP EHS Regulatory Content Expert Rule Sets”
• Section A.33, “How to load rule sets onto the Expert server”
• Section A.34, “How to register rule sets”
6.1.2. Settings to update the licenced rule set package(s)

The following files are included in the delivery:
comp

comp_1810.ruc Rule File
comp_1810.mdb Mapping Database
ReleaseNote_Basis_1810.pdf Release Note
Comp_1810.pdf Functional Description
GWPO

GWP_1810.ruc Rule File
GWP_1810.mdb Mapping Database
GWP_externvalues.mdb External Database
GWP__HISTORY.mdb database for the documentation of the
changes in the mapping database and the ex-
ternal database
GWP_1810.pdf Functional Description

HDCOMP

HazardDecomp_1810.ruc Rule File
HazardDecomp_1810.mdb Mapping Database
HazardDecomp_externvalues.mdb External Database
GS_base_V1-11.ruc sub rule set which must be installed once as a
separate instance on the Expert-Server-PC
HazardDecomp__HISTORY.mdb database for the documentation of the
ternal database
HazardDecomp_1810.pdf Functional Description
HHAZ

HealthHaz_1810.ruc Rule File
HealthHaz_1810.mdb Mapping Database
HealthHaz_externvalues.mdb External Database
HealthHaz__HISTORY.mdb database for the documentation of the
ternal database
HealthHaz_1810.pdf Functional Description
RespiratoryProtection

RespiratoryProtection_1810.ruc Rule File
RespiratoryProtection_1810.mdb Mapping Database
RespiratoryProtection_externvalues.mdb External Database
RespiratoryProtection__HISTORY.mdb database for the documentation of the
ternal database
RespiratoryProtection_1810.pdf Functional Description

GHS

GHS_1810.ruc Rule File
GHS_1810.mdb Mapping Database

GHS_externvalues.mdb External Database

GHS__global_externvalues.mdb External Database used by all GHS rule sets
GS_ident_externvalues.mdb the external database
GS_ident_externvalues.mdb must be located
in the same directory
GS_ident_V1-0.ruc sub rule set which must be installed once as a
GS_physchem_V1-22.ruc sub rule set which must be installed once as a
GHS_sub_pb2017_V1-0.ruc sub rule set which must be installed once as a
GHS_label_V2-02.ruc sub rule set which must be installed once as a
GHS_pure_V1-42.ruc sub rule set which must be installed once as a
GHS_expl_V2-4.ruc sub rule set which must be installed once as a
GHS__HISTORY.mdb database for the documentation of the
ternal database
GHS__global_externvalues__HISTORY.mdb database for the documentation of the
changes in the global external database (used
by all GHS rule sets)
ReleaseNote_GHS_1810.pdf Release Note
GHS_1810.pdf Functional Description
Hazcomp GHS

Hazcomp_GHS_1810.ruc Rule File
Hazcomp_GHS_1810.mdb Mapping Database
Hazcomp_GHS_externvalues.mdb External Database
Hazcomp_GHS__HISTORY.mdb database for the documentation of the
ternal database
ReleaseNote_GHS_1810.pdf Release Note
HazardComp_GHS_1810.pdf Functional Description

Dapec

DAPEC_1810.ruc Rule File
DAPEC_1810.mdb Mapping Database
DAPEC_externvalues.mdb External Database
comp_LEC50_V1-01.ruc sub rule set which must be installed once as a
DAPEC__HISTORY.mdb database for the documentation of the
ternal database
ReleaseNote_EMEA_1810.pdf Release Note
DAPEC_1810.pdf Functional Description
GHS EU

GHS_EU_1810.ruc Rule File
GHS_EU_1810.mdb Mapping Database
GHS_EU_externvalues.mdb External Database


GHS_EU__HISTORY.mdb database for the documentation of the
ternal database
GHS_EU_1810.pdf Functional Description
GHS RU

GHS_RU_1810.ruc Rule File
GHS_RU_1810.mdb Mapping Database
GHS_RU_externvalues.mdb External Database
GHS_RU__HISTORY.mdb database for the documentation of the
ternal database
GHS_RU_1810.pdf Functional Description
GHS TR

GHS_TR_1810.ruc Rule File

GHS_TR_1810.mdb Mapping Database

GHS_TR_externvalues.mdb External Database
GHS_TR__HISTORY.mdb database for the documentation of the
ternal database
GHS_TR_1810.pdf Functional Description
EU to GHS

EU_TO_GHS_1810.ruc Rule File
EU_TO_GHS_Annex_VII_externvalues.mdb External Database according to Annex VII of
the consolidated GHS EU proposal
EU_TO_GHS_1810.mdb Mapping Database with refer-
ence to the external database
EU_to_GHS_EU_Annex_VII_externvalues.mdb
(Annex VII of the consolidated GHS EU pro-
posal)
GS_physchem_V1-22.ruc sub rule set which has to be installed once as
a separate instance on the Expert-Server-PC
GHS_label_V2-02.ruc sub rule set which has to be installed once as
a separate instance on the Expert-Server-PC
EU_TO_GHS__HISTORY.mdb database for the documentation of the
ternal database

EU_to_GHS_1810.pdf Functional Description
HazardComp EU

HazardComp_EU_1810.ruc Rule File
HazardComp_EU_1810.mdb Mapping Database
HazardComp_EU_externvalues.mdb External Database
HazardComp_EU__HISTORY.mdb database for the documentation of the
ternal database
HazardComp_EU_1810.pdf Functional Description
KKDIK Annex XVII Warnings

KKDIK_Annex_XVII_Warnings_1810.ruc Rule File
KKDIK_Annex_XVII_Warnings_1810.mdb Mapping Database
KKDIK_Annex_XVII_Warnings__HISTORY.mdb database for the documentation of the
ternal database
KKDIK_Annex_XVII_Warnings_1810.pdf Functional Description
KKDIK Annex XVII Status

KKDIK_Annex_XVII_Status_1810.ruc Rule File
KKDIK_Annex_XVII_Status_1810.mdb Mapping Database
KKDIK_Annex_XVII_Status_externvalues.mdb External Database
KKDIK_Annex_XVII_Status__HISTORY.mdb database for the documentation of the
ternal database


KKDIK_Annex_XVII_Status_1810.pdf Functional Description
REACH Annex XVII Warnings

REACH_Annex_XVII_Warnings_1810.ruc Rule File
REACH_Annex_XVII_Warnings_1810.mdb Mapping Database
REACH_Annex_XVII_Warnings__HISTORY.mdb database for the documentation of the
ternal database
REACH_Annex_XVII_Warnings_1810.pdf Functional Description
REACH Annex XVII Status

REACH_Annex_XVII_Status_1810.ruc Rule File
REACH_Annex_XVII_Status_1810.mdb Mapping Database
REACH_Annex_XVII_Status_externvalues.mdb External Database
REACH_Annex_XVII_Status__HISTORY.mdb database for the documentation of the
ternal database
REACH_Annex_XVII_Status_1810.pdf Functional Description
RS RestSub

RS_RestSub_1810.ruc Rule File
RS_RestSub_1810.mdb Mapping Database
RS_RestSub_externvalues.mdb External Database

RS_RestSub__HISTORY.mdb database for the documentation of the

ternal database
RS_RestSub_1810.pdf Functional Description
HazardComp EMEA

HazardComp_EMEA_1810.ruc Rule File
HazardComp_EMEA_1810.mdb Mapping Database
HazardComp_EMEA_externvalues.mdb External Database
comp_LEC50_V1-01.ruc sub rule set which must be installed once as a
HazardComp_EMEA__HISTORY.mdb database for the documentation of the
ternal database
HazardComp_EMEA_1810.pdf Functional Description
HazardComp CIS

HazardComp_CIS_1810.ruc Rule File
HazardComp_CIS_1810.mdb Mapping Database
HazardComp_CIS_externvalues.mdb External Database
HazardComp_CIS__HISTORY.mdb database for the documentation of the
ternal database
HazardComp_CIS_1810.pdf Functional Description
HazardComp TR

HazardComp_TR_1810.ruc Rule File
HazardComp_TR_1810.mdb Mapping Database

HazardComp_TR_externvalues.mdb External Database

HazardComp_TR__HISTORY.mdb database for the documentation of the
ternal database
HazardComp_TR_1810.pdf Functional Description
CLNOT

CL_for_notification_1810.ruc Rule File
CL_for_notification_1810.mdb Mapping Database - this file has to be in the
same folder as GHS_EU_externvalues.mdb
GHS_EU_externvalues.mdb External Database - the rule set uses
the same external tables as the rule
set GHS EU. If GHS EU is already in-
stalled and changes had be done in
the external tables, this delivered file
GHS_EU_externvalues.mdb should not be
used.
CL_for_notification__HISTORY.mdb database for the documentation of the
ternal database
CL_for_notification_1810.pdf Functional Description
CMR EU

CMR_EU_1810.ruc Rule File
CMR_EU_1810.mdb Mapping Database
CMR_EU_externvalues.mdb External Database
CMR_EU__HISTORY.mdb database for the documentation of the
ternal database

CMR_EU_1810.pdf Functional Description
Detergents

Detergents_1810.ruc Rule File
Detergents_1810.mdb Mapping Database
Detergents_externvalues.mdb External Database
Detergents__HISTORY.mdb database for the documentation of the
ternal database
Detergents_1810.pdf Functional Description
ICPE

ICPE_1810.ruc Rule File
ICPE_1810.mdb Mapping Database
ICPE_externvalues.mdb External Database
ICPE__HISTORY.mdb database for the documentation of the
ternal database
ICPE_1810.pdf Functional Description
Maladies Professionelles

MaladiesProfessionnelles_1810.ruc Rule File
MaladiesProfessionnelles_1810.mdb Mapping Database
MaladiesProfessionnelles_ External Database
externvalues.mdb
MaladiesProfessionnelles__HISTORY.mdb database for the documentation of the
ternal database
MaladiesProfessionnelles_1810.pdf Functional Description
MAL Code

MAL_Code_1810.ruc Rule File

MAL_Code_1810.mdb Mapping Database

MAL_Code_externvalues.mdb External Database
MAL_Code__HISTORY.mdb database for the documentation of the
ternal database
MAL_Code_1810.pdf Functional Description
Medical Surveillance

Medsurv_1810.ruc Rule File
Medsurv_1810.mdb Mapping Database
Medsurv__HISTORY.mdb database for the documentation of the
ternal database
Medsurv_1810.pdf Functional Description
NL GAM

NL_GAM_1810.ruc Rule File
NL_GAM_1810.mdb Mapping Database
NL_GAM__HISTORY.mdb database for the documentation of the
ternal database
NL_GAM_1810.pdf Functional Description
PIC EU

PIC_EU_1810.ruc Rule File
PIC_EU_1810.mdb Mapping Database
GHS__global_externvalues.mdb the external database
GHS_EU_externvalues.mdb the external database


PIC_EU__HISTORY.mdb database for the documentation of the
ternal database
PIC_EU_1810.pdf Functional Description
RegInfo AL

RegInfo_AL_1810.ruc Rule File
RegInfo_AL_1810.mdb Mapping Database
RegInfo_AL__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_AL_1810.pdf Functional Description
RegInfo CH

RegInfo_CH_1810.ruc Rule File
RegInfo_CH_1810.mdb Mapping Database
RegInfo_CH__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_CH_1810.pdf Functional Description
RegInfo CZ

RegInfo_CZ_1810.ruc Rule File
RegInfo_CZ_1810.mdb Mapping Database
RegInfo_CZ__HISTORY.mdb database for the documentation of the
ternal database

RegInfo_CZ_1810.pdf Functional Description
RegInfo DE

RegInfo_DE_1810.ruc Rule File
RegInfo_DE_1810.mdb Mapping Database
RegInfo_DE__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_DE_1810.pdf Functional Description
RegInfo DK

RegInfo_DK_1810.ruc Rule File
RegInfo_DK_1810.mdb Mapping Database
RegInfo_DK__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_DK_1810.pdf Functional Description
RegInfo HU

RegInfo_HU_1810.ruc Rule File
RegInfo_HU_1810.mdb Mapping Database
RegInfo_HU__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_HU_1810.pdf Functional Description
RegInfo IT

RegInfo_IT_1810.ruc Rule File
RegInfo_IT_1810.mdb Mapping Database
RegInfo_IT__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_IT_1810.pdf Functional Description

RegInfo LV

RegInfo_LV_1810.ruc Rule File
RegInfo_LV_1810.mdb Mapping Database
RegInfo_LV__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_LV_1810.pdf Functional Description
RegInfo NL

RegInfo_NL_1810.ruc Rule File
RegInfo_NL_1810.mdb Mapping Database
RegInfo_NL_externvalues.mdb External Database
RegInfo_NL__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_NL_1810.pdf Functional Description
RegInfo PL

RegInfo_PL_1810.ruc Rule File
RegInfo_PL_1810.mdb Mapping Database
RegInfo_PL__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_PL_1810.pdf Functional Description
RegInfo RO

RegInfo_RO_1810.ruc Rule File
RegInfo_RO_1810.mdb Mapping Database
RegInfo_RO__HISTORY.mdb database for the documentation of the
ternal database

RegInfo_RO_1810.pdf Functional Description
RegInfo RS

RegInfo_RS_1810.ruc Rule File
RegInfo_RS_1810.mdb Mapping Database
RegInfo_RS__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_RS_1810.pdf Functional Description
RegInfo SE

RegInfo_SE_1810.ruc Rule File
RegInfo_SE_1810.mdb Mapping Database
RegInfo_SE_externvalues.mdb External Database
RegInfo_SE__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_SE_1810.pdf Functional Description
RegInfo SI

RegInfo_SI_1810.ruc Rule File
RegInfo_SI_1810.mdb Mapping Database
RegInfo_SI__HISTORY.mdb database for the documentation of the
ternal database
RegInfo_SI_1810.pdf Functional Description
RegInfo TR

RegInfo_TR_1810.ruc Rule File
RegInfo_TR_1810.mdb Mapping Database
RegInfo_TR__HISTORY.mdb database for the documentation of the
ternal database


RegInfo_TR_1810.pdf Functional Description
Seveso III

Seveso-III_1810.ruc Rule File
Seveso-III_1810.mdb Mapping Database
Seveso-III_externvalues.mdb External Database
Seveso-III__HISTORY.mdb database for the documentation of the
ternal database
Seveso-III_1810.pdf Functional Description
StFV

StFV_1810.ruc Rule File
StFV_1810.mdb Mapping Database
StFV__HISTORY.mdb database for the documentation of the
ternal database
StFV_1810.pdf Functional Description
TA Luft

TAluft_1810.ruc Rule File
TAluft_1810.mdb Mapping Database
TAluft_externvalues.mdb External Database
TAluft__HISTORY.mdb database for the documentation of the
ternal database


TALuft_1810.pdf Functional Description
TRGS510

TRGS510_1810.ruc Rule File
TRGS510_1810.mdb Mapping Database
TRGS510_externvalues.mdb External Database
TRGS510__HISTORY.mdb database for the documentation of the
ternal database
TRGS510_1810.pdf Functional Description
TRGS900

TRGS_900_1810.ruc Rule File
TRGS_900_1810.mdb Mapping Database
TRGS_900_externvalues.mdb External Database
TRGS_900__HISTORY.mdb database for the documentation of the
ternal database
TRGS_900_1810.pdf Functional Description
VbF AT

VbF_AT_1810.ruc Rule File
VbF_AT_1810.mdb Mapping Database
VbF_AT__HISTORY.mdb database for the documentation of the
ternal database
VbF_AT_1810.pdf Functional Description

VOC CH

VOC_CH_1810.ruc Rule File
VOC_CH_1810.mdb Mapping Database
VOC_CH_externvalues.mdb External Database
VOC_CH__HISTORY.mdb database for the documentation of the
ternal database
VOC_CH_1810.pdf Functional Description
VOC EU

VOC_EU_1810.ruc Rule File
VOC_EU_1810.mdb Mapping Database
VOC_EU_externvalues.mdb External Database
VOC_EU__HISTORY.mdb database for the documentation of the
ternal database
VOC_EU_1810.pdf Functional Description
VOC PaintCoat

VOC_PaintCoat_1810.ruc Rule File
VOC_PaintCoat_1810.mdb Mapping Database
VOC_PaintCoat_externvalues.mdb External Database
VOC_PaintCoat__HISTORY.mdb database for the documentation of the
ternal database
VOC_PaintCoat_1810.pdf Functional Description

WGK (AwSV Annex 1 (5)

WGK_1810.ruc Rule File
WGK_1810.mdb Mapping Database
WGK_externvalues.mdb External Database
WGK__HISTORY.mdb database for the documentation of the
ternal database
WGK_1810.pdf Functional Description
Youth&Mothers

YoMo_1810.ruc Rule File
YoMo_1810.mdb Mapping Database
YoMo_externvalues.mdb External Database
YoMo__HISTORY.mdb database for the documentation of the
ternal database
YoMo_1810.pdf Functional Description

LCID_1810.ruc Rule File
LCID_1810.mdb Mapping Database
GHS__global_externvalues.mdb the external database
GHS_EU_externvalues.mdb the external database


LCID__HISTORY.mdb database for the documentation of the
ternal database
LCID_1810.pdf Functional Description

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

NotStat_frame_master_1810.ruc Rule File
NotStat_frame_master_ProdComp_1810.mdb Mapping Database (ProdComp variant)
NotStat_frame_master_StandComp_1810.mdb Mapping Database (StandComp variant)
NotStat_externvalues.mdb External Database
NotStat_1810.ruc sub rule (core logic)
NotStat_sub_TSCA12b_1810.ruc sub rule (TSCA 12b)
NotStat_sub_expl_1810.ruc sub rule (Explanation Component)
NotStat_frame_master__HISTORY.mdb database for the documentation of the
ternal database
ReleaseNote_RegStatus_1810.pdf Release Note
Notstat_1810.pdf Functional Description
RestrictionStatus

RestrictionStatus_1810.ruc Rule File

RestrictionStatus_1810.mdb Mapping Database

RestrictionStatus_externvalues.mdb External Database
RestrictionStatus__HISTORY.mdb database for the documentation of the
ternal database
ReleaseNote_RegStatus_1810.pdf Release Note
RestrictionStatus_1810.pdf Functional Description

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

DangGoods_master_global_1810.ruc Rule File (global)
DangGoods_master_1810.ruc Rule File (local version)
DangGoods_master_global_1810.mdb Mapping Database
DangGoods_externvalues.mdb External Database
DangGoods_1810.ruc sub rule set (central part for classification pro-
cess for solids/liquids)
GHS_sub_pb2017_V1-0.ruc sub rule set (GHS classification via compo-
nent data)
DangGoods_gas_1810.ruc sub rule set (classification for gaseous mix-
tures and hazard inducer determination)
DangGoods_report_quant_1810.ruc sub rule set (determination of reportable quan-
tities) (only global version!)
DangGoods_master__HISTORY.mdb database for the documentation of the
ternal database

ReleaseNote_DangGoods_1810.pdf Release Note

DangGoods_1810.pdf Functional Description

MSDSMaker

setup.exe Installation procedure for front-end program
MSDSMAKER.CAB Archive with files for extraction by the installer
setup.lst Installation configuration file
MSDSRule_1810.ruc Rule File
MSDSRule_1810.mdb Mapping Database
MSDSMaker.mdb External Database
MSDSRule_sub_V4-1.ruc sub rule set
separate instance on the Expert Server PC
separate instance on the Expert Server PC
ReleaseNote_MSDSMaker_1810.pdf Release Note
MSDSMaker_1810.pdf Functional Description
6.1.2.7. Settings in Admin Tool
Note
The settings on the Expert Server can now be done by using SAP Setup for ERC
Rule Sets. For more details see Readme_SAPSetup_RuleSets.
Alternatively it is possible to maintain the settings manually via the Expert Admin Tool or within
the transaction CGSADM. The settings for unchanged instances are documented in the SAP
EHS Regulatory Content Administration Manual which is also included in the delivery.
The changed settings for the rule sets are:
CMR EU [update instance]
Environment parameter Value of the parameter

Name ZEXP_CMREU
Mapping Database CMR_EU_1810.mdb
Rule File CMR_EU_1810.ruc
Detergents [update instance]

Name ZEXP_DETR
Mapping Database Detergents_1810.mdb
Rule File Detergents_1810.ruc
ICPE [update instance]

Name ZEXP_ICPE
Mapping Database ICPE_1810.mdb
Rule File ICPE_1810.ruc
MAL Code [update instance]

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

Name ZEXP_F_MP
Mapping Database MaladiesProfessionnelles_1810.mdb
Rule File MaladiesProfessionnelles_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
Medical Surveillance [update instance]

Name ZEXP_MEDS
Mapping Database Medsurv_1810.mdb
Rule File Medsurv_1810.ruc
PIC EU [update instance]

Name ZEXP_PICEU
Mapping Database PIC_EU_1810.mdb
Rule File PIC_EU_1810.ruc

Additional Settings
Name IgnoreWarnings
Value 322
RegInfo AL [update instance]

Name ZEXP_RI_AL
Mapping Database RegInfo_AL_1810.mdb
Rule File RegInfo_AL_1810.ruc
RegInfo CH [update instance]

Name ZEXP_RI_CH
Mapping Database RegInfo_CH_1810.mdb
Rule File RegInfo_CH_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
RegInfo CZ [update instance]

Name ZEXP_RI_CZ
Mapping Database RegInfo_CZ_1810.mdb
Rule File RegInfo_CZ_1810.ruc
RegInfo DE [update instance]

Name ZEXP_RI_DE
Mapping Database RegInfo_DE_1810.mdb
Rule File RegInfo_DE_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
RegInfo DK [update instance]

Name ZEXP_RI_DK
Mapping Database RegInfo_DK_1810.mdb
Rule File RegInfo_DK_1810.ruc

Additional Settings
Name IgnoreWarnings
Value 322
RegInfo HU [update instance]

Name ZEXP_RI_HU
Mapping Database RegInfo_HU_1810.mdb
Rule File RegInfo_HU_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
RegInfo IT [update instance]

Name ZEXP_RI_IT
Mapping Database RegInfo_IT_1810.mdb
Rule File RegInfo_IT_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
RegInfo LV [update instance]

Name ZEXP_RI_LV
Mapping Database RegInfo_LV_1810.mdb
Rule File RegInfo_LV_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
RegInfo NL [update instance]

Name ZEXP_RI_NL
Mapping Database RegInfo_NL_1810.mdb
Rule File RegInfo_NL_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

RegInfo PL [update instance]

Name ZEXP_RI_PL
Mapping Database RegInfo_PL_1810.mdb
Rule File RegInfo_PL_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
RegInfo RO [update instance]

Name ZEXP_RI_RO
Mapping Database RegInfo_RO_1810.mdb
Rule File RegInfo_RO_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
RegInfo RS [update instance]

Name ZEXP_RI_RS
Mapping Database RegInfo_RS_1810.mdb
Rule File RegInfo_RS_1810.ruc
RegInfo SE [update instance]

Name ZEXP_RI_SE
Mapping Database RegInfo_SE_1810.mdb
Rule File RegInfo_SE_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
RegInfo SI [update instance]

Name ZEXP_RI_SI
Mapping Database RegInfo_SI_1810.mdb
Rule File RegInfo_SI_1810.ruc
Additional Settings

Name IgnoreWarnings
Value 322
RegInfo TR [update instance]

Name ZEXP_RI_TR
Mapping Database RegInfo_TR_1810.mdb
Rule File RegInfo_TR_1810.ruc
Seveso III [update instance]

Name ZEXP_SEVE3
Mapping Database Seveso-III_1810.mdb
Rule File Seveso-III_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
StFV [update instance]

Name ZEXP_STFV
Mapping Database StFV_1810.mdb
Rule File StFV_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
TA Luft [update instance]

Name ZEXP_TAL
Mapping Database TAluft_1810.mdb
Rule File TAluft_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
TRGS510 [update instance]

Name ZEXP_TR510
Mapping Database TRGS510_1810.mdb

Rule File TRGS510_1810.ruc

Additional Settings
Name IgnoreWarnings
Value 322
TRGS900 [update instance]

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

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

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

Name ZEXP_VOCEU
Mapping Database VOC_EU_1810.mdb
Rule File VOC_EU_1810.ruc
Additional Settings
Name IgnoreWarnings

Value 322
VOC PaintCoat [update instance]

Name ZEXP_VOCPC
Mapping Database VOC_PaintCoat_1810.mdb
Rule File VOC_PaintCoat_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
WGK (AwSV Annex 1 (5) [update instance]

Name ZEXP_WGK
Mapping Database WGK_1810.mdb
Rule File WGK_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
Youth & Mothers [update instance]

Name ZEXP_YOMO
Mapping Database YoMo_1810.mdb
Rule File YoMo_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
GHS [update instance]

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

Name ZEXP_HCGHS
Mapping Database Hazcomp_GHS_1810.mdb
Rule File Hazcomp_GHS_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
comp [update instance]

Name ZEXP_COMP
Mapping Database comp_1810.mdb
Rule File comp_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 355
HDCOMP [update instance]

Name ZEXP_HDCMP
Mapping Database HazardDecomp_1810.mdb
Rule File HazardDecomp_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
HHAZ [update instance]

Name ZEXP_HHAZ
Mapping Database HealthHaz_1810.mdb
Rule File HealthHaz_1810.ruc
Global Warming Potential [update instance]

Name ZEXP_GWPO
Mapping Database GWP_1810.mdb
Rule File GWP_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322

RespirationProtection [update instance]

Name ZEXP_RESPR
Mapping Database RespiratoryProtection_1810.mdb
Rule File RespiratoryProtection_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
DAPEC [update instance]

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

Name ZEXP_GHSEU
Mapping Database GHS_EU_1810.mdb
Rule File GHS_EU_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
GHS RU [update instance]

Name ZEXP_GHSRU
Mapping Database GHS_RU_1810.mdb
Rule File GHS_RU_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
GHS TR [update instance]

Name ZEXP_GHSTR

Mapping Database GHS_TR_1810.mdb

Rule File GHS_TR_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
EU to GHS [update instance]

Name ZEXP_RTGHS
Mapping Database EU_TO_GHS_1810.mdb
Rule File EU_to_GHS_1810.ruc
HazardComp EMEA [update instance]

Name ZEXP_HC_EM
Mapping Database HazardComp_EMEA_1810.mdb
Rule File HazardComp_EMEA_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
HazardComp EU [update instance]

Name ZEXP_HC_EU
Mapping Database HazardComp_EU_1810.mdb
Rule File HazardComp_EU_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
NLGAM [update instance]

Name ZEXP_NLGAM
Mapping Database NL_GAM_1810.mdb
Rule File NL_GAM_1810.ruc
KKDIK Annex XVII Warnings [update instance]

Name ZEXP_KK17
Mapping Database KKDIK_Annex_XVII_Warnings_1810.mdb

Rule File KKDIK_Annex_XVII_Warnings_1810.ruc

Additional Settings
Name IgnoreWarnings
Value 322
KKDIK Annex XVII Status [update instance]

Name ZEXP_KK17S
Mapping Database KKDIK_Annex_XVII_Status_1810.mdb
Rule File KKDIK_Annex_XVII_Status_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
REACH Annex XVII Warnings [update instance]

Name ZEXP_RA17
Mapping Database REACH_Annex_XVII_Warnings_1810.mdb
Rule File REACH_Annex_XVII_Warnings_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
RS RestSub [update instance]

Name ZEXP_RSRST
Mapping Database RS_RestSub_1810.mdb
Rule File RS_RestSub_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
REACH Annex XVII Status [update instance]

Name ZEXP_RA17S
Mapping Database REACH_Annex_XVII_Status_1810.mdb
Rule File REACH_Annex_XVII_Status_1810.ruc
Additional Settings
Name IgnoreWarnings

Value 322
HazardComp CIS [update instance]

Name ZEXP_HCCIS
Mapping Database HazardComp_CIS_1810.mdb
Rule File HazardComp_CIS_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
HazardComp TR [update instance]

Name ZEXP_HC_TR
Mapping Database HazardComp_TR_1810.mdb
Rule File HazardComp_TR_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
CLNOT [update instance]

Name ZEXP_CLNOT
Mapping Database CL_for_notification_1810.mdb
Rule File CL_for_notification_1810.ruc
Technical prerequisites Expert SP23 or higher; OSS note 1450276
has to be installed
DangGoods [update instance]

Name ZEXP_DG
Mapping Database DangGoods_master_global_1810.mdb
Rule File DangGoods_master_global_1810.ruc / Dang-
Goods_master_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
MSDSMaker [update instance]

Name ZEXP_SDS
Mapping Database MSDSRule_1810.mdb
Rule File MSDSRule_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
NotStat [update instance]

Name ZEXP_NOTS
Mapping Database (ProdComp variant) NotStat_frame_master_ProdComp_1810.mdb
(ProdComp variant)
Mapping Database (StandComp variant) NotStat_frame_master_StandComp_1810.mdb
(StandComp variant)
Rule File NotStat_frame_master_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322,330,331,332,355
RestrictionStatus [update instance]

Name ZEXP_RESST
Mapping Database RestrictionStatus_1810.mdb
Rule File RestrictionStatus_1810.ruc
LCID [update instance]

Name ZEXP_LCID
Mapping Database LCID_1810.mdb
Rule File LCID_1810.ruc
Additional Settings
Name IgnoreWarnings
Value 322
6.1.2.8. Settings in Admin Tool - Sub Rules
Note
The settings for the sub rule set are automatically installed when using SAP Setup
for ERC Rule sets.

In case SAPSetup is not used the below listed settings have to be maintained via the Expert Ad-
min 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 sub rule sets are:
GHS_PURE_1_4 [update instance]

Name GHS_PURE_1_4
Rule File GHS_pure_V1-42.ruc
GHS_LABEL_2_0 [update instance]

Name GHS_LABEL_2_0
Rule File GHS_label_V2-02.ruc
DG_SUB_1810 [create new instance]

Name DG_SUB_1810
Rule File DangGoods_1810.ruc
DG_SUB_GAS_1810 [create new instance]

Name DG_SUB_GAS_1810
Rule File DangGoods_gas_1810.ruc
DG_RQ_1810 [create new instance]

Name DG_RQ_1810
Rule File DangGoods_report_quant_1810.ruc
NOTSTAT_SUB_1810 [create new instance]

Name NOTSTAT_SUB_1810
Rule File NotStat_1810.ruc
NOTSTAT_SUB_TSCA12B_1810 [create new instance]

Name NOTSTAT_SUB_TSCA12B_1810
Rule File NotStat_sub_TSCA12b_1810.ruc

NOTSTAT_SUB_EXPL_1810 [create new instance]

Name NOTSTAT_SUB_EXPL_1810
Rule File NotStat_sub_expl_1810.ruc
6.1.2.9. User Exit Settings

The following user exit settings have to be enhanced/changed for this update:
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:

The following customizing settings have to be enhanced/changed for this update:
Data Origin [create new]

Chapter 7. MSDS Templates
7.1. Check Update
The following steps describe how to check the update of Material safety data sheet (MSDS)
templates.
7.1.1. Checking Procedure

Please use the following check list as guidance through the Material safety data sheet (MSDS)
templates update procedure.
Sta- Where to do What to do

tus
General
O Administration Manual, Review documentation
Release Notes
Technical Part
O SAP Notes Check if SAP Notes listed below are available in target sys-
tem
O SAP EHS (cg3z) Upload files
O SAP EHS (stms) Import transports
O Customizing (spro) Setup identification listings
O SAP EHS (cg34) Import templates
O SAP EHS (cg2b) Create generation variants
O Templates Identify changes in templates and consider these for the up-
dated templates
Detailed information on how to execute the single steps will be provided in this How-To-doc-
uments:

• Section A.38, “How to setup identification listings”
• Section A.39, “How to import report templates”
• Section A.40, “How to create generation variant”
• Section A.41, “How to disclose component names”
With ERC1810, the following SAP Note have become a prerequisite for the SDS templates.
• SAP Note 2620940 - Conversion of IATA_P to IATA
7.1.2. Settings to update the MSDS Template for EMEA


MSDS Templates
EU / EU_EXT / EMEA / CIS

customizing transport
R902923.NE5 SDS customizing transport NE5K902923 for the ERC
SDS template update 1810
K902923.NE5 SDS customizing transport NE5K902923 for the ERC
SDS template update 1810
documents
SDS_1810_EU_Specification.pdf Specification - Document for EU
SDS_1810_EU_Specification_ Specification - Document for EU showing differences to
changes_marked.pdf previous version
SDS_1810_CIS_Specification.pdf Specification - Document for CIS
SDS_1810_CIS_Specification_ Specification - Document for CIS showing differences
changes_marked.pdf to previous version
SDS_1810_EMEA_Specification.pdf Specification - Document for EMEA
SDS_1810_EMEA_Specification_ Specification - Document for EMEA showing differences
SDS_1810_GHS_Specification.pdf Specification - Document for GHS (purple book)
SDS_1810_GHS_Specification_ Specification - Document for GHS showing differences
SDS_1810_RTL_GHS_based_ Specification - Document for RTL SDS template based
Specification.pdf on GHS
SDS_1810_RTL_EU_EXT_based_ Specification - Document for RTL SDS template based
Specification.pdf on EU_EXT
SDS_1810_RTL_EMEA_based_ Specification - Document for RTL SDS template based
Specification.pdf on EMEA
SDS_1810_RTL_GHS_based_ Specification - Document for RTL SDS template based
Specification_changes_marked.pdf on GHS showing differences to previous version
SDS_1810_RTL_EU_EXT_based_ Specification - Document for RTL SDS template based
Specification_changes_marked.pdf on EU_EXT showing differences to previous version
SDS_1810_RTL_EMEA_based_ Specification - Document for RTL SDS template based
Specification_changes_marked.pdf on EMEA showing differences to previous version
Overview_SDS_Templates_used_ Overview on templates and used includes
Includes_1810.xlsx
ReleaseNote_SDS_Templates_ ReleaseNote for the ERC SDS template 1810
1810.pdf
RGV_1810_Configuration.pdf Overview on the generationvariants and how to main-
tain them
SDS_Template_Changes_ERC_ Overview on the SDS template changes, updates and
1810.xlsx corrections in ERC update 1810
SDS-layouts
SDS_1810_BASIC_01.dat Basic SDS template Import-file, Section 1
SDS_1810_BASIC_01.doc Basic SDS template document-file, section 1

MSDS Templates
SDS_1810_BASIC_02.dat Basic SDS template Import-file, section 2

SDS_1810_BASIC_02_EMEA.dat Template Import-file for SDS EMEA, Section 2
SDS_1810_BASIC_02_EMEA.doc Template document-file for SDS EMEA, Section 2
SDS_1810_CIS_01.dat Template Import-file for SDS CIS, Section 1
SDS_1810_CIS_01.doc Template document-file for SDS CIS Section 1

MSDS Templates
SDS_1810_CIS_12.doc Template document-file for SDS CIS, additional part of

section 12
SDS_1810_CIS_12.dat Template Import-file for SDS CIS, additional part of sec-
tion 12
SDS_1810_CIS_MAIN.dat Template Import-file for SDS CIS
SDS_1810_CIS_MAIN.doc Template document-file for SDS CIS
SDS_1810_EU_01.dat Template Import-file for SDS EU, Section 1
SDS_1810_EU_01.doc Template document-file for SDS EU, Section 1

MSDS Templates

SDS_1810_EU_ANNEX.dat Template Import-file for SDS EU, ANNEX
SDS_1810_EU_ANNEX.doc Template document-file for SDS EU, ANNEX
SDS_1810_EU_MAIN.dat Template Import-file for SDS EU
SDS_1810_EU_MAIN.doc Template document-file for SDS EU
SDS_1810_EU_EXT_MAIN.dat Template Import-file for SDS EU_EXT
SDS_1810_EU_EXT_MAIN.doc Template document-file for SDS EU_EXT
SDS_1810_EU_EXT_02_TR.dat Template Import-file for SDS EU_EXT, Section 2 for TR
SDS_1810_EU_EXT_02_TR.doc Template document-file for SDS EU_EXT, Section 2 for
TR
SDS_1810_EU_EXT_02.dat Template Import-file for SDS EU_EXT, Section 2
SDS_1810_EU_EXT_02.doc Template document-file for SDS EU_EXT, Section 2
SDS_1810_EMEA_MAIN.dat Template Import-file for SDS EMEA
SDS_1810_EMEA_MAIN.doc Template document-file for SDS EMEA
SDS_1810_EU_RTL_01.dat Template Import-file for SDS EU, Section 1
SDS_1810_EU_RTL_01.doc Template document-file for SDS EU, Section 1
SDS_1810_EU_EXT_RTL_02.dat Template Import-file for SDS EU, Section 2
SDS_1810_EU_EXT_RTL_02.doc Template document-file for SDS EU, Section 2

MSDS Templates

SDS_1810_EUEXT_RTL_MAIN.dat Template Import-file for SDS EU_EXT
SDS_1810_EUEXT_RTL_MAIN.doc Template document-file for SDS EU_EXT
SDS_1810_EMEA_RTL_MAIN.dat Template Import-file for SDS EMEA
SDS_1810_EMEA_RTL_MAIN.doc Template document-file for SDS EMEA
SDS_1810_EMEA_RTL_02.dat Template Import-file for SDS EMEA RTL, Section 2
SDS_1810_EMEA_RTL_02.doc Template document-file for SDS EMEA RTL, Section 2
SDS_1810_GHS_02.dat Template Import-file for SDS GHS, Section 2
SDS_1810_GHS_02.doc Template document-file for SDS GHS, Section 2

MSDS Templates
SDS_1810_GHS_MAIN.dat Template Import-file for SDS GHS

SDS_1810_GHS_MAIN.doc Template document-file for SDS GHS
SDS_1810_RTL_01.dat Template Import-file for SDS RTL, Section 1
SDS_1810_RTL_01.doc Template document-file for SDS RTL, Section 1
SDS_1810_RTL_MAIN.dat Template Import-file for SDS GHS RTL
SDS_1810_RTL_MAIN.doc Template document-file for SDS GHS RTL

MSDS Templates
Recommendations for the Setup of Report Generation Variants
The recommendations for the setup of Report Generation Variants in comparison to the pre-
vious delivery have been changed for:
SDS_RS: An additional validity area has been added, Sort. 9, ValAreaCat REGION, Val.Area
RS, U. 2, LA EN.
For details please refer to the Report Generation Variant recommendation list RGV_1810_
Configuration.pdf.
Additional settings
Different then for earlier releases, it is recommended to set the two environment param-
eters E_ES_STAT1_COMPARE and E_ES_STAT2_COMPARE to default values of CUST-
H02.00100034 and CUST-H01.00400017, respectively. For earlier releases we recommend-
ed the default setting to leave those parameters empty. The new setting avoids warning mes-
sages during report generation for system configurations that allow detailed error analysis, e.g.
when the environment parameter REPORT_GENERATION_PROTOCOL is set to "X". Details
on the functionality around the two aforementioned environment parameters can be found in
the SDS Template Documentation.

Appendix A. How To ...
A.1. How to upload property tree transports files
The upload process consists of three steps:
1. Find out the directory name and path of the import queue for the SAP Transport Manage-
ment System.
2. Load the transport files into the import directory using the transaction CG3Z.
3. Attach the transport request to the import queue
In the following, the three steps are described:
1. Find out the directory name and path of the import queue for the SAP Transport Manage-
ment System.
1.1. You may ask your SAP system manager or proceed as follows:
1.2. Run transaction AL11.
1.3. The first part of the directory path is listed after the entry DIR_TRANS, for example
"F:\usr\sap\trans".
1.4. Within this directory two sub-directories exist:
• The sub-directory "cofiles" where the co-files are stored.
• The sub-directory "data" where the data files are stored.
5. Load the transport files into the import directory using the transaction CG3Z.
5.1. Start transaction CG3Z.

5.2. Enter in the field "Source file on front end" the transport file name including the com-
plete path on your computer or file server, for example "d:\transfer\K102047.SH2" for
a co-file or "d:\transfer\R102047.SH2" for a data file.
5.3. Enter in the field "Target file on application server" the same file name and the complete
path on the SAP Application Server which you found out in Step 1, for example "F:\usr
\sap\trans\cofiles\K102047.SH2" for a co-file or "F:\usr\sap\trans\data\R102047.SH2"
for a data file. Make sure to enter "BIN" in the field "Transfer format for data".
5.4. Start the upload process with the push button "Upload". When the upload process has
been successful a message appears.
5. Attach the transport request to the import queue
5.1. Navigate to the SAP Transport Management System (transaction STMS).

5.2. Choose push button "Import Overview (F5)".
5.3. Navigate to the transport domain of your SAP system: Position the cursor on the trans-
port domain and choose the push button "Display Import Queue" or choose "Double
click".
5.4. Choose in the menu "Extras" -> "Other requests" -> "Add".
5.5. Enter in the field "Transp. Request" the name of the transport request, e.g.
"SH2K102047". The field "Import Queue" is already filled with the selected import
queue.
5.6. Start the process with the push button "Continue". The transport request is added to
the bottom of the import queue with the highest number.
Please note that the listed "Owner" is the SAP user who created the transport request not the
login-user who started the upload process!

How To ...
A.2. How to upload files

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

The import process consists of several steps which are identical for customizing and work-
bench transport requests:
1. Check user in import client.

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

How To ...
Please note that property tree transport requests are client dependent and shall be available
after the import only in the selected client.
6. Check the import by displaying the transport log.
In the following, the steps listed above are described in more detail:
1. Check user in import client.

1.a. Make sure, that no other user besides the SAP administrator (who is doing the import)
is working in the EH&S specification data base or in the EH&S customizing on the SAP
client where the import of property tree transports takes place. Otherwise, property
tree objects might be logged and might not be updated during the import.
2. Navigate to the SAP Transport Management System.
2.a. Start transaction STMS.
2.b. Choose pushbutton "Import Overview (F5)" or press F5.
2.c. The import overview open with a list of transport requests which are available for im-
port.
3. Select the transport domain for your SAP system.
3.a. Position the cursor on the transport domain.
3.b. Choose the push button "Display Import Queue" or "Double click" on the transport
domain name.
4. Search and select the transport request which shall be imported.
The files which need to be imported depend on the property tree package and are listed
in the Appendix.
4.a. In order to find a transport request more easily in the import queue, a filter can be set.
Choose a column, "Request" for example, by clicking on the column title.
Then choose the pushbutton "Filters (Ctrl + F10)" or press "Ctrl + F10".
Enter the filter criterion in the following window, "SH2*" or "EEI*" for example.
Select the filter criterion with the pushbutton "Copy (Enter)".

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

How To ...
6. Check the import by displaying the transport log.

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

There are two ways to generate phrase sets:
1. Manual generation and allocation of phrase sets

2. During an initial setup or with ERP 6.0 EHP7 and higher EHPs: Run customizing activity
"Generate Standard Phrase Sets"
In the following, both ways are described:
1. Manual generation and allocation of phrase sets

1.a. Ensure that no one is working with the affected property tree or is using the affected
properties and characteristics in the EH&S specification workbench.
1.b. Run transaction CGCZ "Match Up Master Data" with flag "Match Up ValAss Type and
Char." only. This function determines all characteristics to which phrases can be as-
signed - that are all characteristics of type CHAR 30. These characteristics are trans-
ferred to the table “Phrase set - Attribute assignment” (transaction CGAB).
1.c. Choose transaction CG1B "Edit phrase sets" and create manually phrase sets for all
characteristics which are described in the file "Changes....pdf" as "new, CHAR 30,
multiple phrases" or “new, CHAR 30, single phrase”. Enter the characteristic key as
the new phrase set key. Enter the English characteristic description as the phrase set
name in English. Save.
It is recommended to add a German phrase set name as well when you work also
work with a German user interface.

How To ...
Add appropriate phrases to the new phrase sets.
Exceptions are characteristics which keys end with "_GLP",

"_PREC", or "_TEST_SUB". For these characteristics, phrase sets al-
ready exist (SAP_EHS_XXXX_XXX_PREC, SAP_EHS_XXXX_XXX_GLP, and
SAP_EHS_XXXX_XXX_TEST_SUB) and shall directly be assigned.
1.d. Choose transaction CGAB "Edit phrase set-attribute assignment". Assign all new
phrase sets to the appropriate characteristics.
1.e. Run transaction CGCZ "Match up master data" with flag "Activate Phras-
ing of Characteristics" only. This function assigns the function module
C14K_PHRASECHARACT_CHECK to all phrase-related characteristics. This en-
ables the system to call an assigned phrase set in the specification data base.
2. During an initial setup: Run customizing activity "Generate Standard Phrase Sets"
2.a. Ensure that no one is working with the affected property tree or is using the affected
properties and characteristics in the EH&S specification workbench.
2.b. If an EH&S system is set up initially the customizing activity "Generate Standard
Phrase Sets" is used in general to create and allocate phrase sets to all characteris-
tics of type CHAR 30. Please note that with ERP 6.0 EHP7 and higher EHPs, this
customizing activity was extended by a list of characteristics which shall be excluded
from phrase set assignment. This list is delivered with the SAP standard deliver and
ensure that CHAR 30 which are not meant to be assigned to phrase sets are excluded
from the generation and assignment of standard phrase sets.
2.c. Navigate to the activity "Generate Standard Phrase Sets" in the SAP customizing
(IMDG) (path within EH&S 3.2 and higher releases: Environment, Health & Safety ->
Basic Data and Tools -> Specification Management -> Specification Data Base Struc-
ture -> Settings for Value Assignment -> Generate Standard Phrase Sets). A complete
overview about this activity is given in the corresponding IMDG activity documentation.
2.d. Start the activity.
2.e. Phrase sets are generated and allocated to all characteristics of type CHAR 30. With
ERP 6.0 EHP7 and higher EPs phrase sets are not generated and allocated to char-
acteristics which are on the exclusion list. Phrases are not allocated to the new phrase
sets. Assignments of phrase sets to characteristics that already exist are not overwrit-
ten by the system.
2.f. Some characteristics defined as CHAR 30 are not meant to be assigned to phrase
sets, for example "Value in Non-Standard Unit". These characteristics shall be used to

How To ...
store a numerical value and a unit but were unfortunately defined as a free text fields
of CHAR 30. In this case, the assigned phrase set has to be deleted in the table "Edit
phrase set-attribute assignment" (transaction CGAB) after the standard phrase sets
have been created.
If the explanation component shall be used and the phrase sets were generated
by the automatic customizing functionality "Create Standard Phrase Sets", it is neces-
sary to remove the phrase set assignment manually at least from the characteristic
SAP_EHS_0101_002_RULESET. Otherwise the explanation cannot be stored in the
specification database for later use.
2.g. Run transaction CGCZ "Match up master data" with flag "Activate Phras-
ing of Characteristics" only. This function assigns the function module
C14K_PHRASECHARACT_CHECK to all characteristics where phrase sets have
been assigned (see transaction CGAB). This enables the system to call an assigned
phrase set in the specification data base. If the phrase set was deleted in the table "Edit
phrase set-attribute assignment" (transaction CGAB) before carrying out this transac-
tion, then the function module C14K_PHRASECHARACT_CHECK is deleted in the
corresponding CHAR 30-characteristic and this characteristic can be filled as a free
text field.
A.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.

How To ...
Additional information:
In a standard R/3 System automatically created symbols using the transaction CGCZ are gen-
erated with descriptions which are copies of the characteristics descriptions in the logon lan-
guage. The flag "Regenerate Symbol Descriptions" within transaction CGCZ can be used to
generate the symbol descriptions in another language different from the logon language. En-
glish or German are possible symbol descriptions languages when property tree packages are
installed where the characteristics descriptions are delivered in English and German.
If the transaction CGCZ is run with the flag "Match Up Symbols-Phrase-Enabled Characteris-
tics" the symbol definitions for the characteristic symbols that have been changed from phrase-
related to non-phrase-related (or vice versa) will be updated..
A.6. How to set up the Table-based Value Assign-

ment
There are two ways to set up the Table-based Value Assignment:
1. Set up Table-based Value Assignment for new properties

2. Set up Table-based Value Assignment for existing properties with new characteristics
In the following, both ways are described:
1. Set up Table-based Value Assignment for new properties
1.1. Navigate to the activity "Set Up Table-Based Value Assignment" in the SAP customiz-
ing (IMG) (path: Environment, Health & Safety -> Basic Data and Tools -> Specification
Management -> Specification Data Base Structure -> Settings for Value Assignment
-> Set Up Table-Based Value Assignment). A complete overview about this activity is
given in the corresponding IMG activity documentation.
1.2. Start the activity. The following screen appears:

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

How To ...
1.4. Enter a property key of a new property or a series of property keys in the field "Value
assgmt type" and start the process (pushbutton "Execute"). A general example for a
property key is SAP_EHS_1023_043 (for property "GHS Classification (List Data").
Select the property keys of the new properties within a specific property tree package
from the file "Changes_.....pdf". The file name for a specific property tree package can
be found in the Appendix.
Please avoid to execute this process with the same property key multiple times be-
cause this would create multiple entries in the customizing table!
1.5. Return to the previous window (push button "Back"):

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
You have to change the configuration of existing properties where new characteristics were
added and which were already configured for the Table-Based Value Assignment. The rec-
ommended procedure is to delete all entries for existing properties with new characteristics
in the customizing table and to create the entries for these properties anew (see the follow-
ing steps 2.1 to 2.14).
If the configuration of the Table-Based Value Assignment for properties with new character-
istics was already changed, then these changes should be documented before deleting the
entries. In this case, an alternative could be not to delete all entries for a changed property
but to update the Table-Based Value Assignment for the existing property only (follow steps
1.1 to 1.8). Then, the new characteristics would be appended to the already existing entries
for this property. The correct order of the characteristics would have to be set up manually.
Please note, that the Table-based Value Assignment customizing table can only be changed
in SAP systems where the direct customizing is enabled. If the direct customizing is disabled
(for example in a production system), then the Table-based Value Assignment should be set
up in a system where the direct customizing is enabled (for example a development system).
The correct entries can be then transported to the system with the disabled customizing
(customizing transport request).
2.1. Navigate to the activity "Set Up Table-Based Value Assignment" in the SAP customiz-
ing (IMG) (path: Environment, Health & Safety -> Basic Data and Tools -> Specification
Management -> Specification Data Base Structure -> Settings for Value Assignment
-> Set Up Table-Based Value Assignment). A complete overview about this activity is
given in the corresponding IMG activity documentation.
2.2. Start the activity. The following screen appears:

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:

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.

How To ...
A.7. How to check and extend copy/inheritance

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

Choose Data Transfer - > Phrases (Transaction CG31) ; please see screen shot below.
• "File with path" - Enter the path and file name (same as target file section upload files )
• For all files choose UTF-8 as character standard.
• You can leave all other options blank
• Optional: You can limit the import to certain languages if you want (Button "Language se-
lection" )
• Check the file (F5)
• Carefully check the displayed information before importing the phrases. Make sure you im-
port to the passive CED or TDCLE library, the versions are correct and no errors are dis-
played.
• If necessary approve the message "Date of phr. lib. to be imported is identical to date of
current library", this is just for your information.
• However if the file you want to import is older than the library in your system, you can not
import it. Please make sure you have chosen the correct import file. In section upload files
you can also find information on how to change the header data of your import files.
• Choose "Transfer/start time" (F6)
•INTERNAL:
Choose "Immediate" or specify a time
SAP CUSTOMER 76 © SAP SE
• Save
How To ...
Note
Phrase import files for CED and TDCLE libraries include all phrases of the library,
not only those that are new or updated. Please be aware that all manual changes
made in your CED or TDCLE phrases will be overwritten.
Caution
Please do not set the flag for full import as this will delete your
passive library!

How To ...
A.9. 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:

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.

How To ...
Note
It is not recommended to press the "Determine target phrase" - button as this may
select phrases as target phrases that are not appropriate or may not have e.g. all
language translations.
Note
The merging process normally does not perform well when processing several thou-
sand phrases at one time. Therefore, we strongly recommend that only a part of the
phrase library is merged at one time (e.g. filtered by phrase groups or phrase keys).
A.10. 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)

How To ...
Sometimes none or only a few assignments are imported. If you encounter this error, the first
step would be to run this import several times until no more phrases are assigned to phrase
sets. If this does not help an easy work-around is to change the name of the phrase library in
the import file to the name of your active library. Upload and import this modified file. In section
upload files you can also find information on how to change the header data of your import files.
As the phrase set assignment files are based on the latest SAP EHS standard property tree
there will be warnings in the logfile of the import if your system is not updated with the latest
standard property tree. These warnings can usually be ignored. Customers with valid mainte-

How To ...
nance contracts for SAP EHS Regulatory Content - expert rules for substance and mixture
classification or - substance lists and reference data receive the latest tree as part of their reg-
ular maintenance. Should you need any additional info on this topic please feel free to contact
us.
A.11. How to combine/retire phrases

A.11.1. Combining Duplicate Phrases
Previous versions of retired phrases lists will be delivered on demand. With those the following
should be done.
All phrases in column A will no longer be maintained and should be combined with the phrases
listed in column D .
Combining a phrase adds all phrase set assignments from the no longer used phrase (replaced
phrase) to the phrase that's still in use (combined phrase). Additionally all substance value
assignments will be checked and the no longer used phrase key will be replaced by the com-
bined phrase key.
Please see also the SAP EHS documentation for further information on combining phrases.
(example on next page)
• Create a hit list of two or more phrases you want to combine

• Check that both phrase texts are identical
• Do a check if these phrases are used: -> Extras -> Where-used list
• Choose -> Extras -> Combine
• Mark the phrase that you want to keep
• Choose Execute or Execute in background
Important Notes:
• When combining phrases, the phrase positions will not be changed, e.g. missing translations
in one phrase will not be filled with the existing translation of the other phrase nor will changes
to the phrase text or code be made.
• If a phrase is used directly on a report template, the symbol for this phrase has to be replaced
manually with the phrase key of the combined phrase. Use the "where-used list" functionality
to check if a phrase is used on a report template.
• If a phrase is used, execute the combine as a background job as it might take some time to
update all value assignments with the new phrase key.
• Please note that combining phrases may have an influence on e.g. Expert rule sets or data
loads. It may become necessary to change mapping tables accordingly.
• For combining phrases when using ALE distribution please take notice of SAP NOTE 727174
Example:
Phrase to be replaced by another phrase

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

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.12. How to install EHS OCC

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

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

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

termination
In the example at the bottom you can see the typically used entries for secondary data deter-
mination with Expert rule sets and OCC data loads. The required entries for the specific rule
sets are explicitly given in the functional description of the rule set and in the appendix for SAP
EHS Regulatory Content - substance lists and reference data.

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 de-
activated can be derived from the parameter EXPERT_NUM_OF_DEACT_VALUATION.
The data records that were newly determined by the EHS Expert are also created. If the
EXPERT_RES_BY_SRSID_OWNID_FLG parameter is set, then only those data records
are deleted that were determined during previous runs of the EHS Expert. This helps

How To ...
you prevent data records being deleted inadvertently. The SAP system uses the da-
ta origin (parameter EXPERT_WRITE_SOURCE_ID) and the data provider (parameter
EXPERT_WRITE_OWNER) to recognize which data was determined previously by the EHS
Expert.
• EXPERT_DESTINATION
Corresponds with the name of the RFC destination that is entered under Tools -> Adminis-
tration -> Administration -> Network -> RFC Destinations (transaction SM59) (for example
EHS_EXPERT).
• EXPERT_READ_RATING and EXPERT_READ_VALIDITY_AREA
Determine the rating and validity area for which the data is transferred from the SAP system
to the EHS Expert.
• EXPERT_WRITE_RATING and EXPERT_WRITE_VALIDITY_AREA
Determine the rating and validity area with which the data determined is stored in the SAP
system. In the EHS Expert set of rules you can also specifically define a different rating and
validity area that are used when storing data in the system.
• EXPERT_READ_USAGE_1...n and EXPERT_WRITE_USAGE_1...n
These parameters can be used in addition to the two previous parameter pairs. You can
specify any number of usages in the format VACLID/RVLID/EXCLFLG (rating/validity/ex-
clude indicator). The parameter numbering has to start with 1 and has to be consecutive.
Examples
EXPERT_READ_USAGE_1:PUBLIC/REG_EU EXPERT_READ_USAGE_2:PUBLIC/DE/X
In this example, the system reads all data records that are valid in the EU but not in Germany.
EXPERT_WRITE_USAGE_1:PUBLIC/REG_EU
EXPERT_WRITE_USAGE_2:PUBLIC/US
In this example, the system writes all data records that are valid both for the EU and for
the USA.
• EXPERT_WRITE_SOURCE_ID
Data origin that must be created in the IMG activity Specify Data Origin.
If no data origin is created, the system issues an error.

• EXPERT_RULE_SET
Name of the rule set
The following environment parameters can be set up for the reference module
C1E5_SUB_EXPERT_EVALUATE (not all possible parameters are described here):
• EXPERT_COMMIT_FLG
If you set this indicator to X, the system calls the update function specified in the parameter
EXPERT_COMMIT_FUNCTION after the calculation is finished on the Expert server.
If you do not set this indicator, the EHS Expert server directly calls the update function. In
a productive system, we recommend that you set the indicator so that the Expert server is

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.
• EXPERT_PARAMETER_CHANGE_MODE
If you enter the value S (default), the SAP system displays the Determine Secondary Da-
ta dialog box in display mode when starting secondary data determination using the EHS
Expert.
If you enter the value E you can revise the environment parameters in the Determine Sec-
ondary Data dialog box when starting secondary data determination using the EHS Expert.
The environment parameters you specified in Customizing are displayed as default values.
If you enter the value H the SAP system does not display the Determine Secondary Data
dialog box when starting secondary data determination using the EHS Expert.
• EXPERT_RES_BY_SRSID_OWNID_FLG
Set this indicator if in backup modes C or D only data is to be deleted by the EHS Expert
that was determined during previous runs of the EHS Expert.
Warning
If you do not set this indicator, data that has also been entered manually or imported
can be deleted in backup mode C or D by the EHS Expert during secondary data
determination.
• EXPERT_WRITE_OWNER
Data provider that you must have created in the SAP component Product Safety under Tools
-> Addresses -> Edit Data Providers. The data provider must always be entered with 10
digits.
If you do not specify a data provider, the SAP system uses the authorization group for the
specification to determine the respective data provider (see IMG activity Specify Authoriza-
tion Groups). If the SAP system does not find any data providers there, it creates the data
without a data provider.
• EXPERT_HIDDEN_PROCESSING_MODE
You can choose between two operating modes.
ONLINE (default): The EHS Expert run starts immediately after you choose Execute.
BACKGROUND: The EHS Expert runs as a background job. The indicator for the parameter
EXPERT_ASK_FOR_STARTTIME must be set for the start time prompt.
• EXPERT_ASK_FOR_STARTTIME
If you set this indicator, you will be prompted in a dialog box when the EHS Expert is to start
as a background job.
• EXPERT_ADD_PARAM_1...n
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 parame-
ters EXPERT_EXPLANATION_ESTCAT, EXPERT_EXPLANATION_RULE_PROP, and
EXPERT_EXPLANATION_DATE_PROP as described below. Please note that this option
requires the implementation of OSS note no. 1450276!
You set up the explanation component (optional) of the EHS Expert using the following pa-
rameters:
• EXPERT_EXPLANATION_DISPLAY
If you set this parameter to X and allow the set of rules to run in the foreground, the system
displays the explanation immediately after the set of rules run. For sets of rules that run in
the background, the system does not display the explanation automatically.
• EXPERT_EXPLANATION_SAVE
Set this parameter to X if you want to save the explanation for the set of rules run in the
specification. If you set the parameter to X, you must also edit the following parameters:
• EXPERT_EXPLANATION_ESTCAT
In this parameter you specify the value assignment type in which the explanation is to be
saved as a user-defined text. The standard version of the demo sets of rules contains the
entry SAP_EHS_0101_002. This value assignment type is not in a property tree because
the explanation is not displayed as a user-defined text but in the menu.
• EXPERT_EXPLANATION_RULE_PROP
In this parameter you specify the characteristic in which the name of the set of rules is
saved to allow its assignment when displayed at a later stage. The characteristic must be in
the same value assignment type as the user-defined text for the explanation. The standard
version of the demo sets of rules contains the entry SAP_EHS_0101_002_RULESET.
Note
If you run a master data match up, the system automatically appends a phrase set
and a check module to the characteristic. You must remove this check module again.
• EXPERT_EXPLANATION_DATE_PROP
In this parameter you specify the characteristic in which the current date is written with each
rule run. The characteristic must be in the same value assignment type as specified in the
parameter EXPERT_EXPLANATION_ESTCAT. The standard version of the demo sets of
rules contains the entry SAP_EHS_0101_002_RUN_DATE. The last run date is only written
when triggered separately with the parameter EXPERT_WRITE_RUN_DATE. Please note
that this option requires the implementation of OSS note no. 1450276!
• EXPERT_EXPLANATION_TEXTCAT
In this parameter you specify the user-defined text type with which the explanation is to be
saved in the specification. The standard version of the demo sets of rules contains the entry
EX.

How To ...
• EXPERT_ADD_PARAM_1
In this parameter you specify the path and name of the index / header file of your SAP EHS
Regulatory Content database.
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.
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.
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.
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.
In this parameter you can specify a second identifier that OCC should use when look-
ing for substance data. This is identifier is only used when the identifier specified in
EXPERT_TAB_FIELD_2 does not give a search result. The main purpose is for loading data
that is not assigned to CAS numbers.
In this parameter you can specify a third identifier that OCC should use when look-
ing for substance data. This is identifier is only used when the identifiers specified in
EXPERT_TAB_FIELD_2 and EXPERT_TAB_FIELD_4 do not give a search result. The main
purpose is for loading data that is not assigned to CAS numbers, e.g. by using PMN numbers.
Typical Example Expert Rule set:
Environment parameter Sample value

EXPERT_COMMIT_FLG X
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE D
EXPERT_DESTINATION EHS_EXPERT
EXPERT_EXPLANATION_DISPLAY
EXPERT_EXPLANATION_ESTCAT SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE X
EXPERT_EXPLANATION_TEXTCAT EX

How To ...
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE S
EXPERT_READ_RATING PUBLIC
EXPERT_READ_VALIDITY_AREA REG_WORLD
EXPERT_RES_BY_SRSID_OWNID_FLG X
EXPERT_RULE_SET ZEXP_GHS
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID ZEXP_GHS
EXPERT_WRITE_VALIDITY_AREA REG_WORLD
Typical Example OCC data load:
Environment parameter Sample Value

EXPERT_ADD_PARAM_1 headerurl=<path to ERC PS DB>\PS_DB
\header.xml
EXPERT_ADD_PARAM_2 usernameurl=x
EXPERT_ADD_PARAM_3 passwordurl=x
EXPERT_CALL_ONCE X
EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE I
EXPERT_DESTINATION EHS_OCC
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE H
EXPERT_READ_RATING
EXPERT_READ_VALIDITY_AREA
EXPERT_RES_BY_SRSID_OWNID_FLG
EXPERT_RULE_SET CLEO_PS
EXPERT_TAB_FIELD_1 <subid>
EXPERT_TAB_FIELD_2 <identifier>[NUM,CAS]
EXPERT_TAB_FIELD_3 <identifier>[NAM,SYN]
EXPERT_TAB_FIELD_4 <identifier>[NAM,TRIV]
EXPERT_TAB_FIELD_5 <identifier>[NUM,PMN]
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING PUBLIC
EXPERT_WRITE_SOURCE_ID TECHNIDATA
EXPERT_WRITE_VALIDITY_AREA REG_WORLD
A.14. How to manage user exits

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

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

• Enter the user defined text types (limited to 10 characters)
• Give a note / description
• Assign a specification category
• Save your settings
A.16. How to add data origins

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

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

How To ...
A.17. How to add regulatory lists

Start transaction "spro" and navigate to: Environment, Health and Safety -> Basic Data and
Tools -> Specification Management -> Specification Master -> Specify Regulatory Lists
• Press F5 or " New Entries"

• Enter the short form of the regulatory list (limited to 10 characters)
• Give a description and other additional information
• switch to the navigation side bar on the left side and double click "Specification Category"
• Enter new Entries e.g "SUBSTANCE" for which the List will be valid.
A.18. How to add literature sources

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

• 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".
A.19. How to add identifier types

Start transaction "spro" navigate to Environment, Health and Safety -> Basic Data and Tools
-> Specification Management -> Specification Master -> Check Identification Types.
• Enter the Identification category (NAM, NUM FRM....) as work area.

• With F5 or "New Entries" you can enter a new identification type and additional settings.
• You may only enter values within the "Z"- namespace. Others are possible but are not rec-
ommended - if really necessary - ignore warnings and safe.
• Go to the navigation sidebar and double click on the "Specification Category" entry and enter
a new entry e.g. "SUBSTANCE"
• save your Setting.

How To ...

How To ...
A.20. How to add dangerous goods master data

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

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

• Enter the DG regulation the class and letter are relevant for
• Enter the DG class and give a description
• Switch to the navigation side bar on the left side and double click "Classification Code"
• Enter the classification code together with a description
A.20.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

How To ...
A.20.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
A.20.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
A.20.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
A.20.6. Categories of Instructions for Enclosure and In-

structions for Enclosure
Management - Basic Data and Master Data - Common Settings - Specify Categories for En-
closure: (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
A.20.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))

How To ...

• Enter Packing code with description and regulation the new code shall be relevant for
A.21. How to add validity areas

The validity area determines in which jurisdictions values assigned to specifications apply. You
specify validity areas depending on the validity area categories. You can use the validity area
categories to define plants, business areas or regions, for example, as validity areas. You can
assign individual jurisdictions or organizational units at a lower level to each validity area, for
example:
You can assign countries and regions from the country table as validity areas for validity areas
of the category REGION. You can assign other organizational units for validity areas of another
category.
The definition of validity areas is closely linked to the requirements for reports. The validity
areas for this IMG activity are also used in the R/3 component Dangerous Goods Management.
Caution
• Be aware, that the validity area "REG_WORLD" is "empty" and
has the default behaviour to recognize all countries.
• Once you have used a validity area in a productive system, it can
no longer be deleted.
• Newly created validity areas are not evaluated correctly by the
Expert before restarting the Expert Server.
• Please see also SAP Note 603152 - Country Codes for Serbia
and Montenegro
• Go to the IMG customizing ("spro"):

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

How To ...
• Press F5 or "New Entry" and enter the Validity area category (e.g. REGION) and the new
area as well as the description. Mark the entry and switch to the navigation sidebar
• Double clicking the "Assign Validity Area/Country" entry the list of countries belonging to
this area opens (- empty). There you can assign all countries that shall belong to this new
validity area.
A.22. How to setup/update XML substance

database for substance lists and reference data
Note
No database server is needed, any file server with a fast connection and sufficient
storage space is suitable.
Your data implementation or update package contains a setup file e.g. ERC_PS_Region_
2015-2.exe which includes all required database XML files. Please execute this file and choose
the correct path to your SAP EHS Regulatory Content - substance lists and reference data
(Product Safety or Dangerous Goods) database installation. The path must match the entry of
the secondary data determination User Exit for data load, see chapter How to configure the
User Exit.
Note
Please carefully check the installation path if you are updating an existing database to
avoid mixing up e.g. productive and test databases.

How To ...
In your XML substance database folder, a text file called version.txt is stored which
will have information about the currently installed database. Please check the version
file before updating the database to avoid overwriting your database with the same or
older files.
Note
Customers who have licensed both the SAP EHS Regulatory Content SDS Authoring
and Marketability packages have the possibility to load regulatory lists data from both
packages with one data load.
In case you have licensed both, SDS-Authoring and Marketability, and you load both
packages with one data load, please do not install the SDS-Authoring package for list
data. Instead, please use the Marketability installation file and follow the instructions
there to install the combined content for both packages.
Each installation of the substance lists and reference data XML substance database takes
approximately 1,5 GB for Product Safety and 1,1 GB for Dangerous Goods database.
After installation of the XML files, the structure of the database should look like:
Product Safety:
<path to XML substance database>\ERC-PS\ main folder with index file and version info
(header.xml and version.txt)
<path to XML substance database>\ERC-PS subfolder with all CAS numbers starting with 1
\1
<path to XML substance database>\ERC-PS subfolders for other CAS numbers starting
\... with 2 to 9
<path to XML substance database>\ERC-PS subfolder with all substance groups
\G
<path to XML substance database>\ERC-PS subfolder with all non-substances data, e.g.
\N mixtures and data with no CAS number
Dangerous Goods and Dangerous Goods with Packaging

Data:
<path to XML substance database>\ERC-DG\ main folder with index file and version info
(head.xml and version.txt)
<path to XML substance database>\ERC-DG subfolder with all data for DG regulation
\ADN ADN(R)
<path to XML substance database>\ERC-DG subfolders for other DG regulations
\...
<path to XML substance database>\ERC-DG subfolder with all available UN numbers
\UN
Alternatively extract the files and burn a DVD if no network folder should be used (performance
loss!). The network path for database must be accessible for all users (read access). For
security reasons, access should be limited to persons allowed to load SAP EHS Regulatory

How To ...
Content - substance lists and reference data. Please note the path to the database in the
installation protocol.
It is possible to have separate databases for Test, Development and Productive systems. This
allows testing of data updates without impact on the productive data load. If you want to do this,
copy the whole database including all subfolders to a different storage location. In addition,
changes to the mapping database and user exit are required to support multiple databases
(see also chapters How to configure the User Exit, How to configure EHS OCC and How to
setup Mapping Database).
Note
Please make sure that you have a fast network connection between your OCC front-
end computer, SAP application server and the storage location of the XML substance
database. WAN connections are usually unsuitable for OCC as large amounts of data
have to be transferred. See also SAP note 1235663 for further hints to improve the
OCC performance.
A.23. How to setup/update mapping database for

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

This mapping database can either be installed locally for each user or used as a central net-
work-database for all users.
Advantages of a local database:
• Fast access during data load

• Cache during the first data load is created much faster
• No access conflicts if several person are loading data at the same time
Disadvantages of a local database:
• During updates, each database needs to be changed/replaced.

• Users can have different mapping for phrases, properties and other values, potentially cre-
ating inconsistencies in SAP EHS.
Advantages of a central database:
• Only one database needs to be maintained/updated

• All users have the same mapping settings
Disadvantages of a central database:
• If network access is slow or bandwidth is limited, response time during data load might be
longer. Especially creating the cache will be much slower.

How To ...
• In rare cases conflicts in opening the database if several persons are loading substance lists
and reference data at the same time
Note
Please make sure that you have a fast network connection between your OCC front-
end computer and the storage location of the mapping database. WAN connections
are usually unsuitable for OCC as large amounts of data have to be transferred. As the
mapping database is used to store cached data for improved performance, this file can
get quite big (over 100 MB). See also SAP note 1235663 for further hints to improve
the OCC performance.
If you are copying the mapping database from a CD/DVD to your local drive/network,
please remove the write protection of the file td_cleo.mdb after copying to your local
drive.
If the active phrase library is different than CUST, changes to the mapping database are re-
quired:
1. Open td_cleo.mdb / td_cleo_dg.mdb in MS Access

2. Open table ExpPhraseMap
3. Choose column External_id and replace CUST:
Search for: CUST-
Replace with:????- (name of active phrase library)
Search in: External_id
Compare: Beginning of field
Replace all
Note
If several installations were done for the database (test/dev/prod), we recommend a
separate mapping database for each of the installations.
The OCC mapping database follows the same structure as SAP EHS Expert mapping databas-
es. There are separate mapping tables for properties, phrases and other values:
Updating the mapping database

We recommend replacing the mapping database with the new version included in your update
package as additional phrases and regulatory lists are added in the phrase mapping table.
If you have made your own changes to the mapping database, e.g. renamed identifiers or
phrase mapping changes, please take care to implement your changes also in the new map-
ping database. If your active phrase library is different than CUST, changes to the mapping
database as specified above are required.
You can find the path of your mapping database in the ExpertAdmin tool installed on your front
end computer. On the instances tab there should be entries for e.g. CLEO_PS or CLEO_DG
which specify the path to the current mapping database. Please see Section A.24, “How to
configure EHS OCC” for details.

How To ...
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 avail-
able after the first data load.
In all tables, Internal_id means the key/value in the database and External_id the correspond-
ing key/value in SAP EHS.
A.24. How to configure EHS OCC

The following settings in OCC must be created to support the data load of SAP EHS Regulatory
Content - substance lists and reference data.
Note
Please note that everything described in this chapter is only valid for SAP EHS Open
Content Connector (OCC) Service Pack 21 (November 2009) or higher. Please update
OCC to the latest version or contact us for the settings in older OCC versions.
Note
If multiple installations of the database exist for test, development and productive sys-
tems, the below steps must be repeated for all of them. Assign the name of the in-
stances as specified in the user exit parameter EXPERT_RULE_SET and assign the
appropriate mapping database.
Product Safety
A new instance entry has to be configured for Product Safety data:

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

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"

How To ...
A.25. 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.

How To ...
The first three fields together form a unique identifier for the fact in the set of rules.
A.25.1. Adjusting Fact Mapping to Load a CAS Number

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

Record
DispOrder 96
Internal_Id NUM_CAS
Group
External_Id I:NUM,CAS;DUMMY,UPDDAT,LANGU,IDENT,SUBLIST
Language EN
Description CAS Number
IsPhrase yes
Options /DISP=1/MAP=SUBLIST/SEP="|"
A.26. 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
The first two fields together identify the record uniquely in the set of rules.
A.27. How to adjust the Phrase Mapping

The phrase mapping table contains the regulations for mapping phrase codes used in the set
of rules or OCC XML files to phrase keys in EHS.
Note
Phrase mapping allows an assignment to be made between an internal and an external
value for any fact value. The phrase does not have to be an EHS phrase. The corre-
sponding conversion takes place if the IsPhrase indicator is set in fact mapping.
Expert generates a warning message if the rule set or OCC reads phrases which are
not contained in the Mapping table.
Table Fields in the Phrase Mapping Table (ExpPhraseMap)

How To ...
Table Field Meaning

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

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

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

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

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

For the new lists added with this release, please check the filter settings and change the stan-
dard filter settings if required. The default is that new lists will be added to your standard filter
settings as to be loaded.
After reviewing the filter settings, you can define these as the new standard by clicking the
"Default" button.
A.28.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 ...“

How To ...
2. Specify the path to the file erc_update_<version>.txt which can be found in folder 6-Up-
dateTools.
3. Combine with any other search option, e.g. SUBID or identifiers and execute the search.
4. A hit list of all list substances will be created that potentially have new or updated regulatory
data available.

How To ...
5. We recommend saving the created hit list so you have it available in the future without re-
running the query.
Note
We also provide a file erc_new_group_assignments_<version>.txt. This file can be
used in the same way as described above, however it generates a list of substances
with new group assignments compared to the last release.
Note
For performance reasons, we are only checking the changes on a per substance level
not on single data sets. As a result you may have substances on your hit list for which
you do not get any new or changed data when you try to load them. This is the case if
• You have not licensed all regional packages for SAP EHS Regulatory Content - sub-
stance lists and reference data and the changes are in an area you have not licensed.
• You have switched off certain lists/regions in your filter settings; changed data there-
fore will not be displayed.
• You have decided not to load certain data and/or groups in the past for this substance,
if the change is in one of these data sets, it will not be displayed.
A.28.4.1. Simulate Data Load

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

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.28.4.2. Analyze Changed Data

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

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 ERC => Data is from a generic group, not for the substance itself
• Column E: Mode - "New" , "Change" or "Inactivated"
• Column F: Property - this is the property or identifier with the new/changed data
• Column H: CAS number or identifier type
• Column I: Name of the substance
Example A.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.28.4.3. Load Changes to SAP EH&S
There are two different options to load new and changed data into your existing list substances
in SAP EH&S.
If only a few substances need to be updated or if you want to exclude some data from being
updated, the manual process is the best choice.

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.28.4.3.1. Manual update load
A manual update load is almost identical to an initial data load, except for two differences:
The option " Load Changes Only " is set and you can compare the new data with the already
existing data in SAP EH&S directly in OCC.
1. Create a hit list of substances either manually or as described in Section A.28.4, “Hit List
of List Substances”
3. Start the secondary data determination and choose SAP ERC Product Safety Data (or a
comparable entry available in your system)
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.28.4.3.2. Mass Load / Autoload
The autoload functionality is different from a standard load as no user interactivity is possible
after a choice of options and filters/regulatory lists was made. All changed and new data will
be automatically loaded into the existing list substances in SAP EH&S.
1. Create a hit list of substances either manually or as described in Section A.28.4, “Hit List
of List Substances”
3. Start the secondary data determination and choose CLEO Product Safety (or a comparable
entry available in your system)
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.

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.29. SAP EHS Regulatory Content - substance

lists and reference data (Dangerous Goods) Up-
date Data Load
A.29.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.29.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.29.3. Review New Filter Settings

In all cases please review your filter settings for OCC respecting changes done in our content
since last release.
A.29.4. Analyze Changed Data

We provide an Microsoft Access database with a summary of all changes made in the last
update. The database 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

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.29.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 specifica-
tion do not show two instances of the same regulation.
A.29.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 compa-
rable 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.

How To ...
10.Save data to EH&S
A.29.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 compa-
rable 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.30. How to add user-defined DG texts

User-defined dangerous goods texts are regulation-dependant and may be assigned to spe-
cific dangerous goods user-defined text profiles. The dangerous goods user-defined free texts
themselves are phrases, whereas those phrases written by the standard expert rule Dang-
Goods are CED standard phrases delivered with the CED phrase library. If further dangerous
goods user-defined texts are required, additional phrases need to be created.
To specify dangerous goods user-defined text profiles, use transaction SPRO, choose SAP
Reference IMG and navigate through the activities tree to Environment, Health and Safety -
Dangerous Goods Management - Basic Data and Master Data - Common Settings - Specify
Profiles for User-Defined Dangerous Goods Texts:
• Press F5 or select "New Entries"

• Enter the respective DG regulation, a unique number for the profile and a description for
the profile

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)
A.31. 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.32. SAP Setup for SAP EHS Regulatory Content

Expert Rule Sets
SAP Front End installation (SAP Setup)
A.32.1. Overview
The SAP EHS Regulatory Content Expert Rule Sets can now be installed with the help of SAP
Setup on the Expert-Server.

How To ...
Note
SAP ERC Rule Sets can be installed and updated on the Expert Server either
with the help of SAP Setup or manually. However for an individual rule set It is not
recommended to use both methods. Therefore if SAP Setup has been used for a
particular rule set, future updates should also be performed using SAP Setup.
For initial installations of SAP ERC Rule Sets the SAP Setup can be used as
detailed below.
However for an update of rule sets using SAP Setup the following additional steps
are required:
1) Backup of existing rule sets - make a copy of the <EXPERT>\Rules directory
2) Start the setup for rule sets and install new versions (existing rule instances
will be overwritten)
3) Make customer specific changes in the mapping databases and external value
databases
In case of intermediate corrections of ruc-files, the instance in the registry needs
to be changed manually (by using ExpertAdmin or transaction cgsadm).
For the next regular update SAPSetup can then again be used, but the intermedi-
ate version of the ruc-file will not be deleted by SAPSetup. This has no impact on
the functionality. The intermediate version of the ruc-file can be deleted manually.
The Setup offers two possibilities
• Installation: Copy rule set files into the specified Rules Directory on the Expert Server PC
and create registry settings for all needed instances.
• Registration: Create registry settings for all needed instances. The rule set files need to be
transferred manually.
Our recommended procedure is the following:
1. Use SAP Setup to install all needed Expert Rule Sets on a test or QA Expert Server
2. Perform all tests and make necessary adjustments to the mapping mdbs or external tables
on the test or QA Expert server
3. Use SAP Setup’s registration option to create all registry settings needed on any Production
Expert Servers.
4. Transfer Rule Set files from the test or QA Expert Server to the Production Expert Server(s)
This procedure will ensure necessary registry entries are created for all rules, while also en-
suring consistency between QA and Production environments. Detailed steps for this proce-
dure follow below.

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

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

How To ...
You can select all rule files in one click by choosing "Select all".
When updating from one SAP ERC release to the next SAP ERC release (e.g. from ERC1605
to ERC1611) it is important to choose "Select all" that all rule sets are updated and new rule
sets are installed on the Expert Server PC.

How To ...
A.32.2. Installation on the Test or QA Expert Server

Prerequisites
• Access to the Test or QA Expert Server PC

• The user logged on to the PC must have local administrator privileges.
Procedure
• Create a backup of the .mdb files before installation, as the files get overwritten during the
installation process.
• Start SetupERC_<package>.exe (e.g. SetupERC_GLOBAL.exe)
• The installation starts and a progress screen is displayed.
• Choose next
• The list of EHS Regulatory Content rule sets is displayed.
• Choose the rule sets from "Installation"
• Select the rule sets that you want to install or deselect the ones you want to remove.
A yellow dot indicates a change in the selection list. A green plus sign next to a rule set
package or rule set name indicates that this rule set will be installed.
that this rule set package or rule set will be uninstalled.

How To ...
• Choose next
The installation starts and a progress screen is displayed.
Once the installation is complete, a confirmation screen is displayed. The rule sets are now
successfully installed.
• Verify the mapping databases and the settings in the external tables and adapt them if nec-
essary.
A.32.3. Installation on the Productive Expert Server

Prerequisites
• Access to the Productive Expert Server PC

• The user logged on to the PC must have local administrator privileges.
Procedure
• Create a backup of the .mdb files before installation (just as a precaution, the files are not
overwritten during the registration process)
• Start SetupERC_<package>.exe (e.g. SetupERC_GLOBAL.exe)
• The installation starts and a progress screen is displayed.
• Choose next
The list of EHS Regulatory Content rule sets is displayed.

• Choose the rule sets from "Registration"
• Select the rule sets that you want to register or deselect the ones you want to remove.
A yellow dot indicates a change in the selection list. A green plus sign next to a rule set
package or rule set name indicates that this rule set will be registered.
that this rule set package or rule set will be uninstalled.
• Choose next
The installation starts and a progress screen is displayed.
Once the registration is complete, a confirmation screen is displayed. The rule sets are now
successfully registered.
• Copy the rule set files form the Test or QA Expert Server to the Productive Expert Server.
A.33. 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

How To ...
All the files need to be copied on the Expert Server PC.
You can copy the files by using EHS Service Administration or by connecting to the Expert
Server PC directly.
EHS Service Administration

In transaction cgsadm choose the Expert Server PC and transfer the files as described in the
following steps
1. Choose in the menu Utilities --> Transfer File to Server

2. Choose all files to be transferred
3. Choose the path on the Expert Server PC
NOTE:
The path can only be chosen by a click on the icon
Then choose the icon next to view the directory structure
You will get the following screen and you can choose the path Rules for the files to be
transferred.
4. Press save and the files will be copied to the Expert Server PC
Direct copy
Connect to the Expert Server PC and copy all files in the RULES subdirectory of the Expert
installation.
A.34. How to register rule sets

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

How To ...
A.35. How to adjust external table values

In addition to the files for the rule sets (ruc files and the mapping data base) some rule sets
provide a separate MS-Access data base
The purpose of it is to allow the user to modify the preconfigured data according to the needs
of the customers.
These external parameters are interpreted by the rule set as IN facts.
It is recommended to install this data base in the same directory on the Expert server as the
rule files.
If this external data base is installed somewhere else, the linkage between the rule set and the
external data base must be maintained by defining the file path in the mapping tables.
The below mentioned mapping information refers to the HazardComp_US_externvalues.mdb

but the approach to adjust the mapping is the same for all rule sets.
Example: Record-Mapping –Installation of the external data base in the same directory as the
rule set.
Internal_id External_id
EXT_RANGES T:Ranges/HazardComp_US_externvalues.mdb
Example: Record-Mapping – Full declaration of the path for the external data

How To ...
EXT_RANGES T:Ranges/C:\Program Files\EHS\Expert\Rules
\HazardComp_US_externvalues.mdb
Example: Fact-Mapping –Installation of the external data base in the same directory as the
rule set.
i_limit_oel T:Threshold;OEL/HazardComp_US_externvalues.mdb
Example: Fact-Mapping –Full declaration of the path for the external data
i_limit_oel T:Threshold;OEL/C:\Program Files\EHS\Expert\Rules
\HazardComp_US_externvalues.mdb
A documentation of the adjustable parameters could be obtained from the respective functional
descriptions of the rule sets.
A.36. 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
A.37. How to use the History.mdb

The History database gives the user information and overview on changes applied to the map-
ping database of a rule set. All changes that have been applied to the mapping of a rule set
since the last release are documented in the History database. This includes the four standard
categories
• CHANGES_in_mapping_table_____ExpFactMap
• CHANGES_in_mapping_table_____ExpPhraseMap
• CHANGES_in_mapping_table_____ExpRecordMap
• CHANGES_in_mapping_table_____ExpGroupMap
Changes which have been made concerning the externvalues database are also documented
here, e.g.
• Changes_in_external_table____GHS_table

How To ...
• Table_Changes_in_external_table_not_P_Statements
There are three different cases of mapping changes: new entries, changed entries, and deleted
entries.
Every changed, new, or deleted entry is added to the HISTORY.mdb as a new line.
If there is a change, it is additionally checked if the given entry already exists in the
HISTORY.mdb (i.e. if it has already been changed in a former version); if this is the case, the
matching entry is updated and the old version information is preserved as described below.
The additional columns Version and Remark are maintained as follows:
Version:
• the version number without a preceding "V", e.g. "1.5"
• if a line is updated, the old Version entry is replaced by the new one
Remark: dependant on the type of change:

• new entry: "Vn-m: New"
• change: "Vn-m Changed (further description of change)"
• change after preliminary change: Vn-m: "Changed (...); V(n-i)-(m-j): New/Changed (...)/
Deleted"
• deleted entry: "Vn-m: Deleted"
With the help of the History database the key-user can easily adopt the Mapping to a newly
delivered version, if the company has fitted the mapping to their needs by adding , deleting or
changing phrases from the standard mapping database delivered by SAP.
A.38. 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.

How To ...
A.39. How to import report templates

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

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

How To ...
The option "Usage check" is utilized to control the way in which the usages are compared.
There are four options to select: 0, 1, 2 and 3.
If you do not specify a value, the SAP System uses the value 0 as default.
Value 0: The usage is appropriate if - with the same rating used - the generation variant validity
area that is expanded to its countries and regions is the same as or is a subset of the expanded
validity area of the usage with which it is to be compared.
Example: Generation variant: DE Value assignment usage: REG_EU If a safety data sheet is
created for Germany, value assignment instances are also taken into account that are valid
for the validity area REG_EU.
Please see the SAP Help function for all the details on the option.
Under "Rating/Validity", additional validity/language combinations can be maintained:
These validity areas or languages must be addressed directly by the WWI coding in the
template (G-Repeating-Group) to be effective. By the use of these Rating/Validity options, it
is for example possible to give out special phrases in English on a template in Chinese or
Spanish.
A complete overview on the parameters of all generation variants can be found in the document
RGV_XXXX_Configuration.pdf (where XXXX stands for the current release).
A.41. How to disclose component names

This section describes the Component Name Disclosure in SDSs including trade secret re-
quirements.
Requirements
• Standard name

How To ...
Usually components in SDSs are listed by name that allows to identify the component with
a commonly used name. The name should be given in the language of the SDS. Often
regulations or best practices require a specific name that is used in some regulations or for
registration purposes (e.g. name from REACH registration in EU SDS section 3)
• trade secret name
Some regulations allow that a name of a component can be discarded (e.g. standard name
replaced by the words “trade secret” or replaced by a more generic name). This name is an
alternative name to the standard name
Required data maintenance

The above requirements create a need for at least two names for components – one used as
standard name and another one used as trade secret name. For other reasons potentially oth-
er names of components might be relevant (e.g. name of substance to be used in dangerous
goods shipping documents). Names are maintained as identifier. That means that for names
two identifiers are relevant. The standard name (e.g. NAM PROD) and the trade secret name
(e.g. NAM TRADESEC). As the identifiers are not called directly in the WWI template, but by
means of identification listings, it can be controlled by customization settings which identifiers
should be used for which scenario (standard or trade secret). So, other identifiers types as in
the above examples can be used, if customizing setting are adjusted accordingly. All names
need to be available in all relevant SDS languages. This can be achieved either by mainte-
nance of all relevant translations or by use of a technically language independent name that
can be used as a default, if no translated name is available. In this case the language inde-
pendent name usually holds the English translation. As there is no source generally available
for fully translated names, there are two approaches to maintain the standard name:
• Collect all names at a dedicated identifier (e.g. NAM PROD) by manually or logic-based
copying them from all potential sources (e.g. NAM ANNEXI, NAM EINECS, NAM ENCS, …).
Translation gaps can be either closed by translation or by use of a language independent
entry.
• Create an identification listing in customization, that holds all potential sources (e.g. NAM
ANNEXI, NAM EINECS, NAM ENCS, …) in a prioritized sort sequence. As translation gaps
will occur (e.g. NAM ANNEXI not available for all substances and only in selected lan-
guages), a language independent identifier should be given (e.g. NAM SYN) as fallback at
the lowest priority in the listing.
The trade secret name has to be included in a separate ID listing which is then used for the
disclosure of trade secret names.
Technical implementation in template

The WWI template is coded by using WWI functions to disclose different ID listings (instead of
direct identifier output). The relevant ID listings can be maintained as environment parameter
in customizing. These functions handle the output of a second ID listing for trade secret names.
This is controlled by the component type of the relevant composition. If the component type
is considered to be trade secret relevant (customization, e.g. TRADESEC) then instead of
the identifiers from the standard ID listing the identifiers from the trade secret ID listing are
considered for output. The ID listings are not only used to disclose component names but also
component numbers, e.g. CAS-no. Therefore the ID-listings need to contain all the names
assigned according to their priorities to position 1, all numbers assigned according to their
priorities to position 2. Exemption: if the CAS-no. should be discarded with a name if trade

How To ...
secret applies (e.g. “proprietary ingredient” this needs to be maintained as separate identifier,
(e.g. NAM TRADESEC2) and is entered on position 2 of the listing.
Technical limitations
• No component type available
As the component type in the composition tab controls the output of trade secret identifiers,
this trigger cannot be provided in value assignment types with specification listing (instead
of composition) only. In this case always the standard identifier will be disclosed.
• More than one identifier per type
If more than one relevant identifier is found by the WWI functions (e.g. NAM PROD DE
is maintained twice), it can occur that the first found identifier is disclosed in the column
for component names, while the second found identifier is disclosed in the column for com-
ponent numbers instead of e.g. the CAS-number. This can be avoided by consistent data
maintenance. It can be avoided technically, if all name identifiers in the ID listing are listed
for position 1 and all number identifiers are listed for position 2.
Required system settings

• Environment parameters for ID listing assignment
• REP_TS_COMPCAT1 -> Standard Component Type, e.g. ACT_AGENT
• REP_TS_IDLID1 -> Standard ID Listing for Standard Component Type assigned to
REP_TS_COMPCAT1, e.g. D_NTSIDLID
• REP_TS_COMPCAT2 ->Trade secret Component Type, e.g. TRADESEC
• REP_TS_IDLID2 -> Standard ID Listing for Trade secret Component Type assigned to
REP_TS_COMPCAT2, e.g. D_TSIDLID
Further component type/ID listing combinations can be maintained. For all component types
that are not maintained at an environment parameter the ID listing D_VALPOS is used as
default. If no entries are given in the environment parameters the ID listing D_VALPOS is
used for standard name output and trade secret name output as well.
• Further environment parameters influencing the identifier output

• REP_TS_IDENT_NOUSAGECHECK -> No usage check for Trade Secret. If this param-
eter has an value “x” the usage of an identifier is not considered for output (setting not
recommended)
• REP_TS_NOTRADESEC_IDLID -> If the component type is not specified within one
of the REP_TS_COMPCAT# parameters, the identification listing specified in environ-
ment parameter REP_TS_NOTRADESEC_IDLID is used. The environment parameters
REP_TS_NOTRADESEC_IDLID is not provided in the standard system.
• REP_TS_OUTPUT_PER_POS -> If you want to use the function module
C14N_SYM_TS_START to determine identifiers using "Trade Secret" listings in such a
way that they are output to the report on a position-by-position basis during report gener-
ation, you must create the following environment parameter in the "Specify Environment
Parameters" Customizing activity: REP_TS_OUTPUT_PER_POS Identifier Output Per
Position (TS) To enable determination to be made on a position-by-position basis, set the
parameter to "X". If this environment parameter is not available or is not set, the identifiers
are determined using the standard process for listings. That is, the identifiers are deter-
mined based on the sequence of the position and priority. In this case, the system takes
into account only identifiers that are not blank under consideration of the Customizing
settings for the defined listing. (SAP Note 2094891, 2172087)
How To ...
• REP_TS_SUPPORT -> Option to generate time-specific change marking (SAP Note

2164505)
• Identifier listings
All identifier listings assigned to component types as environment parameter need to be

created with all relevant names and numbers.
Example:
• Simple ID listing for standard identifier output D_NTSIDLID
IDListPos IDListPrio IDCategory IDType MaxNoID

1 1 NAM PROD 1
2 1 NUM CAS 1
For this setup the NAM PROD needs to be maintained with all translations (or if missing
translations should be allowed all available translations plus one language independent
entry for NAM PROD)
• Complex ID listing for standard identifier output D_NTSIDLID

1 1 NAM ANNEXI 1
1 2 NAM EINECS 1
1 3 NAM IUPAC 1
1 4 NAM SYN 1
1 5 NAM ENCS 1
1 6 NAM PROD 1
2 1 NUM CAS 1
2 2 NUM EINECS 1
2 3 NUM ELINCS 1
For this setup the NAM PROD (and only this one) should have a language independent
entry to make sure that always an output is found.
• ID listing for trade secret identifier output D_TSIDLID

1 1 NAM TRADESEC 1
2 1 NAM TRADESEC2 1
This setup support to discard the CAS-No. with a name identifier (e.g. Proprietary Ingre-
dient)
• Simple ID listing for trade secret identifier output D_TSIDLID

1 1 NAM TRADESEC 1
This setup results in disclosure of a trade secret name instead of a standard name. No
numbers are printed, so the CAS-number can be discarded for trade secret components.
How To ...
Special Trade Secret Functionality for US and Canada

For US and Canada, the regulatory requirement regarding trade secrets can be broken down
to the following cases:
1. Masking the component identity, while the component identity is being claimed as a trade
secret.
2. Masking the component concentration, while the component concentration is being claimed
as a trade secret.
3. Masking both the component identity and concentration.
Case 1 is handled by the standard trade secret functionality as described above.
Cases 2 and 3 are handled by additional component types.
Mock-up for Canada
Note: The US section 3 would be identical, with the exception of the HMIRA phrase, which
would be missing.
Masking component concentration (Case 2):
This is achieved by using the component type ZTRADECONC. When the relevant component
in the product Standard composition is maintained with this component type, the template
outputs “Trade Secret (HazardComp range)" instead of just the HazardComp range (see case
2 in mock-up above).
Note: This HazardComp range can be achieved by either of two means:
1. If "ignore Expert rule range" is not maintained, then the HazardComp ranges will be generic
ranges. This means that all ranges for all disclosed components will be generic ranges.
2. If "ignore Expert rule range" is maintained, then the HazardComp ranges will be copied
directly from the Standard composition. This is the case where at least some of the disclosed
components are not trade secrets, and thus have their true concentrations/ranges (from the
Standard composition) disclosed in section 3.

How To ...
Masking component identity and concentration (Case 3):
This is achieved by using the component type ZTRADESCON. When the relevant component
in the product Standard composition is maintained with this component type, the template
outputs NAM ZTRADESEC instead of NAM PROD for the chemical name. The CAS number
is replaced by NAM ZTRADESEC2. “Trade Secret (HazardComp range)” is output instead of
just the HazardComp range (see case 3 in mock-up above).
Note: The same considerations regarding the HazardComp range as above apply here.
Output of HMIRA phrase in section 3:
The HMIRA phrase is output in section 3 of the Canada SDS (see mock-up above) if one of
the based on the following logic: If the HazardComp contains a component with one of the
component types ZTRADESEC, ZTRADECONC or ZTRADESCON in a CA instance, then the
phrase is output.
Customizing for Component types ZTRADECONC or ZTRADESCON
All Component types ZTRADESEC, ZTRADECONC and ZTRADESCON must be specified

in the customizing in “Specify Component Types for Compositions” and “Specify Environment
Parameters”.
Example for setting Component Types ZTRADESEC, ZTRADECONC and ZTRADESCON
A complete list of all Environment parameters, including None-Trade-Secret ID Listings (see

section “Required system settings” above), would look like that:
Environment parameters Parameter Value

REP_TS_COMPCAT1 ACT_AGENT
REP_TS_COMPCAT2 ZTRADESEC
REP_TS_COMPCAT3 ZTRADESCON
REP_TS_COMPCAT4 ZTRADECONC*
REP_TS_IDLID1 D_NTSIDLID
REP_TS_IDLID2 D_TSIDLID
REP_TS_IDLID3 D_TSIDLID

How To ...
REP_TS_IDLID4 D_NTSIDLID*
*The component type ZTRADECONC for masking concentration (see Case 2 above) has the
D_NTSIDLID ID Listing as the masked Concentration is written by the HazComp rule.
The component types ZTRADECONC (Masking component concentration) and ZTRADE-

SCON (Masking component identity and concentration) trigger the output of the phrase “Trade
Secret” by the template in column “Concentration (% w/w)” (see mock-up above).
Special procedure to disclose the CAS No on Product level

for Substances which have only one component which is a
Trade Secret for Taiwan only
The Type of substance for the Product has to be "Substance".
The Component types of the components can be ZTRADESCON (masking component identity
and conc.) or TRADESEC (masking component identity only).
A specific Trade secret identifier (NAM / ZTRADESEC2) has to be maintained on product

level. The identifier NAM ZTRADESEC2 has to be maintained manually on component level
to overwrite the NUM CAS in section 3.
Therefore a new logic has been implemented on the SDS template:
1. Check if NAM ZTRADESEC2 is maintained. If available, print it.

2. Check if a NUM CAS is assigned. If available, print it, otherwise print “Not assigned”.

SAP EHS Regulatory Content Update Guide

Uploaded by

Document Information

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

Publication date January 2019

INTERNAL: SAP CUSTOMER

INTERNAL: SAP CUSTOMER iii © SAP SE

6.1.2.8. Settings in Admin Tool - Sub Rules ................................................ 53

INTERNAL: SAP CUSTOMER iv © SAP SE

INTERNAL: SAP CUSTOMER v © SAP SE

1.2. How to use this guidance document

1.2.1. Structure of this manual

INTERNAL: SAP CUSTOMER 1 © SAP SE

INTERNAL: SAP CUSTOMER 2 © SAP SE

2.1. Update Prerequisites

Front-end computer for data load

INTERNAL: SAP CUSTOMER 3 © SAP SE

1407091 Check function for EC numbers

2.2. Update overall procedure

The graph shows the sequence of the update.

• Check list: Property tree

INTERNAL: SAP CUSTOMER 4 © SAP SE

INTERNAL: SAP CUSTOMER 5 © SAP SE

3.1.1. Update Procedure

Status Where to do What to do

INTERNAL: SAP CUSTOMER 6 © SAP SE

O SAP EH&S (Transaction Create WWI symbols

• Section A.1, “How to upload property tree transports files”

3.1.2. Contents of Latest SAP ERC Property Tree Package

3.1.2.1. File overview property tree package Product Safety

File name Description

INTERNAL: SAP CUSTOMER 7 © SAP SE

File name Description

Order of Transport File names Description

3.1.2.2. File overview corrections to previous property tree package

INTERNAL: SAP CUSTOMER 8 © SAP SE

4.1.1. Checking Procedure

Status Where to do What to do

• Section A.2, “How to upload files”

4.1.2. Settings to implement the Multilanguage Phrase Li-

INTERNAL: SAP CUSTOMER 9 © SAP SE

File name Description

4.1.3. General Settings

4.1.3.1. Language keys

INTERNAL: SAP CUSTOMER 10 © SAP SE

5.1.1. Check List Update Product Safety

Status Where to do What to do

INTERNAL: SAP CUSTOMER 11 © SAP SE

• Section A.12, “How to install EHS OCC”

5.1.2. Settings to update the Substance Lists and Reference

File name Description

INTERNAL: SAP CUSTOMER 12 © SAP SE

ERC_ListOverview_1901.xlsx Overview of lists by region and country and assignment

5.1.2.2. Other Settings

No additional settings are needed for this release.

INTERNAL: SAP CUSTOMER 13 © SAP SE

5.1.3. Check List Update Dangerous Goods for SAP EHS

Status Where to do What to do

• Section A.12, “How to install EHS OCC”

INTERNAL: SAP CUSTOMER 14 © SAP SE

• Section A.3, “How to import transport requests”

5.1.4. Settings to update the regulatory data (Dangerous

Files File Description

INTERNAL: SAP CUSTOMER 15 © SAP SE

Files File Description