Professional Documents
Culture Documents
SAP EHS Regulatory Content Update Guide
SAP EHS Regulatory Content Update Guide
1. Introduction ....................................................................................................................... 1
1.1. Objective ................................................................................................................ 1
1.2. How to use this guidance document ..................................................................... 1
1.2.1. Structure of this manual .............................................................................. 1
1.3. Security/Authorization ............................................................................................ 2
1.4. Support options ..................................................................................................... 2
1.4.1. Customer Helpdesk .................................................................................... 2
2. Update .............................................................................................................................. 3
2.1. Update Prerequisites ............................................................................................. 3
2.2. Update overall procedure ...................................................................................... 4
3. Property Tree ................................................................................................................... 5
3.1. Check Update ........................................................................................................ 5
3.1.1. Checking Procedure ................................................................................... 5
3.1.2. Settings to implement the last SAP EHS Management Property Tree
Package Product Safety ....................................................................................... 5
4. SAP EHS Regulatory Content - multilanguage phrase library for hazard communication ........................................................................................................................................ 6
4.1. Check Update ........................................................................................................ 6
4.1.1. Checking Procedure ................................................................................... 6
4.1.2. Settings to implement the Multilanguage Phrase Library (Standard) ........... 6
4.1.2.1. File Overview ................................................................................... 6
4.1.3. Settings to implement the Multilanguage Phrase Library (APA) .................. 8
4.1.3.1. File Overview ................................................................................... 8
4.1.4. General Settings ......................................................................................... 9
4.1.4.1. Language/Codepages ...................................................................... 9
4.1.4.2. Language keys ................................................................................. 9
5. SAP EHS Regulatory Content - substance lists and reference data .............................. 10
5.1. Check Update ...................................................................................................... 10
5.1.1. Check List Update Product Safety ............................................................ 10
5.1.2. Settings to update the Substance Lists and Reference Data (Product
Safety) ................................................................................................................. 11
5.1.2.1. File Overview ................................................................................. 11
5.1.2.2. Other Settings ................................................................................ 12
5.1.3. Check List Update Dangerous Goods ...................................................... 16
5.1.4. Settings to update the CLEO regulatory data (Dangerous Goods) ............ 17
5.1.4.1. File Overview ................................................................................. 17
5.1.4.2. Other Settings ................................................................................ 18
6. SAP EHS Regulatory Content - expert rules for substance and mixture classification
.............................................................................................................................................. 20
6.1. Check Update ...................................................................................................... 20
6.1.1. Check List ................................................................................................. 20
6.1.2. Settings to update the licenced rule set package(s) ................................. 21
6.1.2.1. Settings in Admin Tool ................................................................... 21
6.1.2.2. Settings in Admin Tool - Sub Rules ............................................... 32
6.1.2.3. User Exit Settings .......................................................................... 34
6.1.2.4. Other Settings ................................................................................ 36
6.1.3. Settings to update the basis rule set package .......................................... 36
6.1.3.1. File Overview ................................................................................. 36
6.1.3.2. Settings in Admin Tool ................................................................... 37
6.1.3.3. User Exit Settings .......................................................................... 37
6.1.3.4. Other Settings ................................................................................ 37
6.1.4. Settings to update the rule set package for GHS ..................................... 37
iii
SAP AG
iv
SAP AG
SAP AG
vi
124
127
128
128
129
129
129
130
130
132
133
134
135
135
136
136
136
136
136
137
137
138
138
139
139
140
142
143
143
144
145
145
SAP AG
Chapter 1. Introduction
1.1. Objective
This SAP EHS Regulatory Content Update Guide comprises all relevant steps and guidelines
for update of the SAP EHS Regulatory Content content products (phrases, regulatory data,
Expert rules, MSDS-templates) in SAP EHS. Appropriate related How Tos are included to
facilitate the update procedure. Information for all relevant update steps is provided.
This manual does not replace release notes or functional descriptions for the individual content
products. Release notes are provided for each new version of the individual product to give
an overview over new and changed features. Functional descriptions are provided for each
individual product as detailed documentation on all functions and settings.
This manual describes all available SAP EHS Regulatory Content products. These products
need to be licensed. The manual may describe products that are not licensed by your company
and thus not delivered to your company. If you would like to check your SAP EHS Regulatory
Content license status, please contact SAP.
SAP AG
Introduction
Expert rules for substance and mixture classification: This section covers all information
necessary for Expert rules. This section contains the release related information for the
Expert rules. The settings are structured according to the rule set packages they belong to
as well as a consolidated overview listing of all licensed packages.
Material safety data sheet (MSDS) templates: The aim of this part is to provide information
which is relevant to update MSDS Report Templates.
How To ...: The aim of this section is to provide fast and easy to use advice on how to perform
all necessary actions throughout the process of updating SAP EHS Regulatory Content.
1.3. Security/Authorization
Starting with the download of the SAP EHS Regulatory Content package, the customer is solely
responsible for the integrity of the content, e.g. to protect the content against manipulation.
We strongly recommend to store the SAP EHS Regulatory Content in a restricted environment,
accessible only by authorized persons involved in content implementation or updates. For
further details regarding user authorization in your file system please see the user manual of
your operating system.
In SAP EHS access rights to SAP EHS Regulatory Content can be administrated via authorization profiles. For further details we refer to User and Role Administration of AS ABAP and
Roles for Environment, Health and Safety (EH&S) in the SAP Library (http://help.sap.com).
questions
about
online
access
or
available
services
please
address
to:
SAP AG
Chapter 2. Update
This chapter describes the prerequisites which are necessary to update your SAP EHS Regulatory Content.
EHS - Release
EHS Expert/OCC
Current version of EHS Open Content Connector (OCC) and EHS Expert (see SAP note
586302).
EHS WWI
Current version of WWI
Starting with the 2010-1 Release, the Material safety data sheet (MSDS) templates will use
function modules located in the /TDAG/-namespace instead of utilizing the Z-namespace
( ZISI...). Therefore it is necessary to create the /TDAG/-namespace on a customer system,
before importing the workbench transport with the actual function modules in the /TDAG/namespace.
Please see section "File overview" to find details on the namespace transport.
Customizing
SAP authorisation
Front-end computer for data load
SAP Notes
SAP Note
Remark
568302
See for information how to download the latest version of OCC and additional system requirements.
1061242
1408534
1418024
1299868
SAP AG
Update
1407091
1424476
1371276
1434736
1454105
1466900
1105036
1146663
1279191
1265493
1368217
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.
Detailed information which steps are necessary to update your SAP EHS Regulatory Content
are collected in the content related check lists:
Important
Before starting the update procedure please review the enclosed documentation.
Caution
It might be necessary to upgrade your installation of OCC/Expert or to update your
EHS or to implement SAP notes.
Tip
Collect all transports contained in the update. If you upload all transports at once you
can skip the appropriate upload activities mentioned in the check lists.
SAP AG
Where to do
What to do
General
O
Review documentation
Technical Part
O
Upload files
Import transports
Customizing (spro)
Detailed information on how to execute the single steps will be provided in this How-To-documents:
SAP AG
Where to do
What to do
General
O
Review documentation
Technical Part
O
Customizing (spro)
Upload phrases
Upload phrase set assignments
Import phrases
Merge phrases
Detailed information on how to execute the single steps will be provided in this How-To-documents:
SAP AG
SAP EHS Regulatory Content - multilanguage phrase library for hazard communication
Standard
File name
Description
01_documents
CED_ReleaseNote_2011-1.pdf
CED_Changes_2011-1.xls
Excel file with complete scope of EN phrases in previous and current version for a quick information what has
changed in the latest release; table 2 contains obsolete
pset assignments that should be deleted
Phrase_Services_Proposals.xls
02_phrases_windows / 03_phrases_unix
ced_2011-1_standard_unicode_
complete.dat
ced_2011-1_standard_unicode_
update.dat
ced_2011-1_brazilian_Z9_
complete.dat
Phrase import file with all phrases in Brazilian Portuguese via Z9 customer correspondence language
ced_2011-1_brazilian_Z9_
update.dat
ced_2011-1_mexican_unicode_
complete.dat
ced_2011-1_mexican_unicode_
update.dat
ced_2011-1_usenglish_Z8_
complete.dat
ced_2011-1_usenglish_Z8_
update.dat
Non-Unicode files with separate files per codepage. These files are not needed if you
use the Unicode files
ced_2011-1_west_complete.dat
ced_2011-1_central_complete.dat
Phrase import file with phrases in Central-European languages: Croatian, Czech, Hungarian, Polish, Romanian, Serbian (SH), Slovenian, Slovakian
ced_2011-1_baltic_complete.dat
Phrase import file with phrases in Baltic languages: Estonian, Latvian, Lithuanian
ced_2011-1_cyrill_complete.dat
ced_2011-1_greek_complete.dat
ced_2011-1_turkish_complete.dat
SAP AG
SAP EHS Regulatory Content - multilanguage phrase library for hazard communication
04_psets_windows / 05_psets_unix
ced_2011-1_pset_new.dat
ced_2011-1_pset_complete.dat
Description
01_documents
CED_ReleaseNote_2011-1.pdf
CED_Changes_2011-1.xls
Excel file with complete scope of EN phrases in previous and current version for a quick information what has
changed in the latest release; table 2 contains obsolete
pset assignments that should be deleted
Phrase_Services_Proposals.xls
02_phrases_windows / 03_phrases_unix
ced_2011-1_ap_unicode_complete.dat
Phrase
import file including all phrases in all AP languages for fast processing in Unicode systems
ced_2011-1_ap_unicode_update.dat
Non-Unicode files with separate files per codepage. These files are not needed if you
use the Unicode files. For technical reasons Hindi, Vietnamese and Tagalog are only
available as Unicode file.
ced_2011-1_ap_latin_complete.dat
ced_2011-1_ap_tchin_complete.dat
ced_2011-1_ap_schin_complete.dat
ced_2011-1_ap_japanese_complete.dat
Phrase
ced_2011-1_ap_korean_complete.datPhrase
ced_2011-1_ap_thai_complete.dat
04_psets_windows / 05_psets_unix
SAP AG
SAP EHS Regulatory Content - multilanguage phrase library for hazard communication
ced_2011-1_pset_new.dat
ced_2011-1_pset_complete.dat
SAP AG
Where to do
What to do
Documentation
Review documentation
General
O
Technical Part
O
Frontend
Upload phrases
XML File storage (local, Update database XML files using the database setup
network drive)
file
td_cleo.mdb
Documentation
MS Excel
10
SAP AG
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:
File Description
0-Documentation
PS_Data_ReleaseNote _2011-1.pdf
CLEO_ContentReport_AP.pdf
CLEO_ContentReport_EU.pdf
CLEO_ContentReport_Americas.pdf
CLEO_ContentReport_
Inventories.pdf
CLEO_PS_Training_EN.ppt
1-OCC
Info file on how to obtain OCC
readme.txt
2-Customizing
R900542.TD8
and K900542.TD8
R902760.TD4
and K902760.TD4
R900548.TD8
and K900548.TD8
11
SAP AG
and K902762.TD4
customizing_overview.txt
File Description
Customizing transport with additional validity areas
(Non-Unicode)
Overview of customizing entries
3-Phrases\Unicode_Unix / 3-Phrases\Unicode_Win
cleo_2011-1_unicode.dat
cleo_2011-1_pset_unicode.dat
cleo_2011-1_canadianfrench_
unicode.dat
cleo_2011-1_usenglish_
unicode.dat
cleo_2011-1_mexican_spanish_
unicode.dat
cleo_2011-1_brazilian_unicode.datUnicode
3-Phrases\MS-NT_Unix / 3-Phrases\MS-NT_Win
cleo_2011-1_west.dat
cleo_2011-1_central.dat
cleo_2011-1_cyrillic.dat
cleo_2011-1_baltic.dat
cleo_2011-1_brazilian.dat
cleo_2011-1_greek.dat
cleo_2011-1_japanese.dat
cleo_2011-1_korean.dat
cleo_2011-1_simplchinese.dat
cleo_2011-1_tradchinese.dat
cleo_2011-1_thai.dat
cleo_2011-1_turkish.dat
cleo_2011-1_usenglish.dat
cleo_2011-1_pset.dat
4-CLEO Database
CLEO_PS_region_2011-1.exe
Substance Lists and Reference Data - Product Safety Database setup/update program
5-Mapping
td_cleo.mdb
6-UpdateTools
cleo_update_2011-1.txt
cleo_new_group_assignments
_2011-1.txt
12
SAP AG
Note
Create new Regulatory Lists
Create new Sources
Add new Validity Areas
Customizing Transport TD8K900542 (Unicode) for Reg. Lists and
Sources
Customizing Transport TD4K902760 (Non-Unicode) for Reg. Lists
and Sources
Customizing Transport TD8K900548 (Unicode) for Validity Areas
Customizing Transport TD4K902762 (Non-Unicode) for Validity Areas
This installation package includes customizing transports that can be imported to create all
necessary customizing entries.
Alternatively, all customizing entries can be done manually according to the tables below.
Additional Regulatory Lists
Value of the parameter
Description
ZAR_BEI
ZBE_BEI
ZBR_BEI
ZCH_BAT
ZDK_BEI
ZES_BEI
ZFI_BEI
ZGB_BMGV
ZHU_BEI
ZIT_BEI
ZLU_BEI
ZLV_BEI
ZMT_BEI
ZNZ_BEI
ZRO_BEI
ZRS_BEI
13
SAP AG
ZSI_BAT
Slovenia. BAT-values
ZSK_BEI
ZTR_BEI
ZCN_HW
ZKR_GHSMOE
ZIN_OEL
ZCY_OEL
ZIS_OEL
ZMK_OEL
ZMT_OEL
ZRS_OEL
ZPH_PCL
-> Environment, Health &Safety -> Basic Data and Tools -> Specification Management
-> Specification Master -> Specify Regulatory Lists
OR transaction: S_SH8_72000974 - Specify Regulatory Lists
Section A.16, How to add regulatory lists
Additional Sources
Value of the parameter
Description
ZAR_BEI
ZBE_BEI
ZBR_BEI
ZCH_BAT
ZDK_BEI
ZES_BEI
ZFI_BEI
ZGB_BMGV
ZHU_BEI
ZIT_BEI
ZLU_BEI
ZLV_BEI
ZMT_BEI
14
SAP AG
ZRO_BEI
ZRS_BEI
ZSG_BEI
ZSI_BAT
Slovenia. BAT-values
ZSK_BEI
ZTR_BEI
ZCN_HW
ZKR_GHSMOE
ZIN_OEL
ZCY_OEL
ZIS_OEL
ZMK_OEL
ZMT_OEL
ZRS_OEL
ZPH_PCL
-> Environment, Health &Safety -> Basic Data and Tools -> Specification Management > Additional Information for Value Assignment -> Specify Sources
OR transaction: S_SH8_72000953 - Specify Sources
Section A.17, How to add literature sources
Additional Validity Areas
Note
Please see also SAP Note 603152 - Country Codes for Serbia and
Montenegro
VAreaCat
Val. area
REGION
CY
Cyprus
REGION
IN
India
REGION
MK
Macedonia
REGION
RS
Serbia
REGION
VE
Venezuela
-> Environment, Health and Safety -> Basic Data and Tools -> Additional Information for
Value Assignment -> Usage -> Specify Validity Areas
15
SAP AG
Where to do
What to do
Documentation
Review documentation
General
O
Technical Part
O
Frontend
Upload phrases
XML File storage (local, Update database XML files using the database setup
network drive)
file
td_cleo.mdb
Documentation
MS Access
Detailed information on how to execute the single steps will be provided by following the links
in the check list above or in the How-To-documents listed below:
Section A.11, How to install EHS OCC
Section A.2, How to upload files
Section A.3, How to import transports (customizing or workbench)
Section A.7, How to import phrases
Section A.8, How to merge phrases
Section A.9, How to import phrase set assignments
Section A.21, How to setup/update XML substance database for substance lists and reference data
Section A.22, How to setup/update mapping database for SAP EHS Regulatory Content substance lists and reference data
16
SAP AG
File Description
0-Documentation
DG_Data_ReleaseNotes_ 2011-1.pdf
cleo_dg_changes 2011-1.mdb
TD_CLEO_DG_Training_EN.pdf
1-Customizing
R904130.TDG / K904130.TDG
R904126.TDG / K904126.TDG
R904159.TDG / K904159.TDG
R904117.TDG / K904117.TDG
2-Phrases
cleo_dg_2011-1.dat
cleo_dg_pset_2011-1.dat
3-CLEO Database
CLEO_DG_2011-1.zip
4-Mapping
TD_CLEO_DG.mdb
TD_CLEO_DG_with_Split.mdb
TD_CLEO_DG_without_pack.mdb
Dangerous Goods - Mapping Database, without packing data, without split by mode of transport for NA regulations
17
SAP AG
File Description
TD_CLEO_DG_with_split_without_
pack.mdb
Dangerous Goods - Mapping Database, without packing data, with split by mode of transport for NA regulations
Note
This release contains a transport with all changed customizing entries of the regulations ADR, IMDG and RID.
These transports enable you to update your system with all new
entries for these regulations in 2011 amendment.
Note
With this release we implement a new regulation ADN for inland
waterway transport in Europe.
Currently ADNR is set up within the systems as the relevant Inland
Waterway regulation for various Countries in Europe. In order to
ensure a seamless switch to ADN data the following process steps
need to be performed:
1. Create the DG Regulation ADN within customizing Specify Dangerous Goods Regulations initially must not contain the Mode of
Transport Category Inland Waterway, for this is still assigned
to ADNR. Otherwise there will be Countries with more than one
DG regulation valid to Inland Waterway, which will lead to errors
in Logistics. Instead a Dummy Mode of Transport Category like
Pipeline needs to be used initially for the time being. This holds
ADNR still active and deactivates ADN.
2. Implement ADN DG Customizing transport with all the other entries necessary.
3. Load LS_UN_SUB data for ADN. The OCC will create a new instance for this regulation in your specification but will remember
the settings of your last load with ADNR.
4. Amend DG_CL_SUB > Transport Classification with ADN data.
5. Amend all other DG related properties with ADN data, e. g.
Additional data for Transport, Hazard Inducers and Dangerous
Goods User defined Texts
6. Prepare WWI documents (MSDS) for ADN. Our MSDS template
is already prepared for this regulation.
7. Set ADN active by changing the Mode of Transport Category
from the dummy entry to Inland Waterway.
8. Set ADNR inactive by changing the Mode of Transport Category
from Inland Waterway to the dummy entry. In this case you
have to delete this regulation and create it new with new settings.
9. Refill DG Master.
10.Remove all ADNR data from Specification database.
18
SAP AG
Note
We harmonized the unique IDs of the regulations ADR, RID and
ADN with this release. So it might happen that OCC is not able
to recognize an already existing RID instance in a specification.
In this cases you should delete the old RID instance so that this
specification do not show two RID instances.
This installation package includes customizing transports that can be imported to create all
necessary customizing entries.
The transports contains new entries for following tables:
TCG46 Sources
TCG91 Validity Areas
THM009 Dangerous goods classes
THM071 Risk potentials
THM017 Danger labels
THM003 Transport types
THM031Hazard identification numbers
CCUNC 115 Instructions for enclosure
CCUNC121 Packing codes
Alternatively, all customizing entries can be done manually, please contact us for a detailed
description.
19
SAP AG
Where to do
What to do
General
O
Review documentation
Technical Part
O
Mapping.mdbs
If you have adapted the mapping databases of the previous version to your needs , identify changes in the
new mapping.mdbs and consider these for the update
of your mapping databases (see HISTORY.mdbs)
Externvalues.mdbs
If you have adapted the external values databases of the previous version to your needs , identify
changes in the new externvalues.mdbs and consider
these for the update of your mapping databases (see
HISTORY.mdbs)
20
SAP AG
Name
ZEXP_DP_AU
Mapping Database
DP_AU_V2-34.mdb
Rule File
DP_AU_V2-34.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_CN_CN
Mapping Database
Classification_CN_V2-51.mdb
Rule File
Classification_CN_V2-51.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSCN
Mapping Database
GHS_CN_V1-3.mdb
Rule File
GHS_CN_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
21
SAP AG
Name
ZEXP_CN_JP
Mapping Database
Classification_JP_V2-62.mdb
Rule File
Classification_JP_V2-62.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_FS_JP
Mapping Database
Fire_Service_JP_V2-9.mdb
Rule File
Fire_Service_JP_V2-9.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HC_JP
Mapping Database
HazardComp_JP_V2-81.mdb
Rule File
HazardComp_JP_V2-81.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSJP
Mapping Database
GHS_JP_V1-3.mdb
Rule File
GHS_JP_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
22
SAP AG
ZEXP_GHSKR
Mapping Database
GHS_KR_V1-7.mdb
Rule File
GHS_KR_V1-7.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_DS_KR
Mapping Database
DSSMA_KR_V1-7.mdb
Rule File
DSSMA_KR_V1-7.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HC_KR
Mapping Database
HazardComp_KR_V2-52.mdb
Rule File
HazardComp_KR_V2-52.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSNZ
Mapping Database
GHS_NZ_V1-6.mdb
Rule File
GHS_NZ_V1-6.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSSG
23
SAP AG
GHS_SG_V1-3.mdb
Rule File
GHS_SG_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HC_SG
Mapping Database
HazardComp_SG_V1-1.mdb
Rule File
HazardComp_SG_V1-1.ruc
Name
ZEXP_GHSTW
Mapping Database
GHS_TW_V1-3.mdb
Rule File
GHS_TW_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_CMREU
Mapping Database
CMR_EU_V1-02.mdb
Rule File
CMR_EU_V1-02.ruc
Name
ZEXP_DETR
Mapping Database
Detergents_V1-0.mdb
Rule File
Detergents_V1-0.ruc
Name
ZEXP_ICPE
Mapping Database
ICPE_V1-11.mdb
Rule File
ICPE_V1-11.ruc
24
SAP AG
Name
ZEXP_F_MP
Mapping Database
MaladiesProfessionnelles_V1-41.mdb
Rule File
MaladiesProfessionnelles_V1-41.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_MAL
Mapping Database
MAL_Code_V1-3.mdb
Rule File
MAL_Code_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_SEVE
Mapping Database
Seveso-II_V1-41.mdb
Rule File
Seveso-II_V1-41.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_TAL
Mapping Database
TAluft_V4-21.mdb
Rule File
TAluft_V4-21.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_TR510
25
SAP AG
TRGS510_V1-0.mdb
Rule File
TRGS510_V1-0.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_TR90
Mapping Database
TRGS_900_V1-22.mdb
Rule File
TRGS_900_V1-22.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_VBFAT
Mapping Database
VbF_AT_V1-31.mdb
Rule File
VbF_AT_V1-31.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_VOC
Mapping Database
VOC_CH_V1-31.mdb
Rule File
VOC_CH_V1-31.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_VOCEU
Mapping Database
VOC_EU_V1-33.mdb
Rule File
VOC_EU_V1-33.ruc
Additional Settings
26
SAP AG
IgnoreWarnings
Value
322
Name
ZEXP_VOCPC
Mapping Database
VOC_PaintCoat_V1-4.mdb
Rule File
VOC_PaintCoat_V1-4.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_WGK
Mapping Database
WGK_V1-81.mdb
Rule File
WGK_V1-81.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_RTGHS
Mapping Database
EU_TO_GHS_V1-51.mdb
Rule File
EU_to_GHS_V1-51.ruc
Name
ZEXP_GHS
Mapping Database
GHS_V2-3.mdb
Rule File
GHS_V2-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HCGHS
27
SAP AG
Hazcomp_GHS_V1-52.mdb
Rule File
Hazcomp_GHS_V1-52.ruc
Name
ZEXP_CWA
Mapping Database
CWA_V1-01.mdb
Rule File
CWA_V1-01.ruc
Name
ZEXP_HAZCO
Mapping Database
HazardComp_US_V2-71.mdb
Rule File
HazardComp_US_V2-71.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HMIS
Mapping Database
HMIS_V2-5.mdb
Rule File
HMIS_V2-5.ruc
Name
ZEXP_MCHC
Mapping Database
MCHC_V1-0.mdb
Rule File
MCHC_V1-0.ruc
Name
ZEXP_NFPA
Mapping Database
NFPA_V1-7.mdb
Rule File
NFPA_V1-7.ruc
Name
ZEXP_OSHA
28
SAP AG
OSHA_Hazard_Determination_V2-71.mdb
Rule File
OSHA_Hazard_Determination_V2-71.ruc
Name
ZEXP_SPRQ
Mapping Database
SpillReport_V2-01.mdb
Rule File
SpillReport_V2-01.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_RTK
Mapping Database
US_State_RTK_V1-74.mdb
Rule File
US_State_RTK_V1-74.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_CAPBT
Mapping Database
CAPBT_V1-01.mdb
Rule File
CAPBT_V1-01.ruc
Name
ZEXP_WHMIS
Mapping Database
WHMISCLASS_V2-62.mdb
Rule File
WHMISCLASS_V2-62.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HC_CA
29
SAP AG
WHMISComposition_V1-73.mdb
Rule File
WHMISComposition_V1-73.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSBR
Mapping Database
GHS_BR_V1-2.mdb
Rule File
GHS_BR_V1-2.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HC_BR
Mapping Database
HazardComp_BR_V1-1.mdb
Rule File
HazardComp_BR_V1-1.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_COMP
Mapping Database
comp_V1-21.mdb
Rule File
comp_V1-21.ruc
Additional Settings
Name
IgnoreWarnings
Value
355
Name
ZEXP_DAPEC
Mapping Database
DAPEC_V3-1.mdb
Rule File
DAPEC_V3-1.ruc
Additional Settings
30
SAP AG
IgnoreWarnings
Value
322
Name
ZEXP_GHSEU
Mapping Database
GHS_EU_V1-6.mdb
Rule File
GHS_EU_V1-6.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HC_EU
Mapping Database
HazardComp_EU_V3-0.mdb
Rule File
HazardComp_EU_V3-0.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_CLNOT
Mapping Database
CL_for_notification_V1-2.mdb
Rule File
CL_for_notification_V1-2.ruc
Name
ZEXP_DG
Mapping Database
DangGoods_master_global_V4-0.mdb
DangGoods_master_V4-0.mdb
Rule File
DangGoods_master_global_V4-0.ruc
DangGoods_master_V4-0.ruc
Name
ZEXP_SDS
Mapping Database
31
SAP AG
MSDSRule_V3-7.ruc
Name
ZEXP_NOTS
NotStat_frame_master_ProdComp_V3-3.mdb
(ProdComp variant)
NotStat_frame_master_StandComp_V3-3.mdb
(StandComp variant)
Rule File
NotStat_frame_master_V3-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322,330,332,355
Name
ZEXP_RESST
Mapping Database
RestrictionStatus_V1-71.mdb
Rule File
RestrictionStatus_V1-71.ruc
Name
ZEXP_DPDL
Mapping Database
DPDplus_lead_V1-11.mdb
Rule File
DPDplus_lead_V1-11.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
DG_SUB_4_0
32
SAP AG
DangGoods_V4-0.ruc
Name
DG_SUB_GAS_4_0
Rule File
DangGoods_gas_V4-0.ruc
Name
DG_GAS_BINARY
Rule File
DangGoods_sub_binary_V4-0.ruc
Name
DG_RQ_4_0
Rule File
DangGoods_report_quant_V4-0.ruc
Name
GHS_SUB_PB2009_1_1
Rule File
GHS_sub_pb2009_V1-1.ruc
Name
GHS_SUB_PB2007_1_4
Rule File
GHS_sub_pb2007_V1-4.ruc
Name
GHS_SUB_PB2009_1_3
Rule File
GHS_sub_pb2009_V1-3.ruc
33
SAP AG
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc
Name
GHS_LABEL_1_1
Rule File
GHS_label_V1-1.ruc
Name
MSDSRULE_SUB
Rule File
MSDSRule_sub_V3-7.ruc
Name
NOTSTAT_SUB
Rule File
NotStat_V3-3.ruc
Name
NOTSTAT_SUB_TSCA12B
Rule File
NotStat_sub_TSCA12b_V3-3.ruc
Name
NOTSTAT_SUB_EXPL
Rule File
NotStat_sub_expl_V3-3.ruc
ZEXP_DETR
EHS-Expert: Detergents
Environment parameter
34
SAP AG
EXPERT_COMMIT_FUNCTION
C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE
EXPERT_READ_RATING
PUBLIC
EXPERT_READ_VALIDITY_AREA
REG_EU
EXPERT_RES_BY_SRSID_OWNID_FLG
EXPERT_RULE_SET
ZEXP_DETR
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
EXPERT_WRITE_SOURCE_ID
ZEXP_DETR
EXPERT_WRITE_VALIDITY_AREA
REG_EU
ZEXP_TR510
EHS-Expert: TRGS510
Environment parameter
EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION
C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE
EXPERT_READ_RATING
PUBLIC
EXPERT_READ_VALIDITY_AREA
DE
EXPERT_RES_BY_SRSID_OWNID_FLG
EXPERT_RULE_SET
ZEXP_TR510
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
EXPERT_WRITE_SOURCE_ID
ZEXP_LGK
EXPERT_WRITE_VALIDITY_AREA
DE
ZEXP_MCHC
EHS-Expert: ...
Environment parameter
35
SAP AG
EXPERT_COMMIT_FUNCTION
C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE
EXPERT_READ_RATING
PUBLIC
EXPERT_READ_VALIDITY_AREA
US
EXPERT_RES_BY_SRSID_OWNID_FLG
EXPERT_RULE_SET
ZEXP_MCHC
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
EXPERT_WRITE_SOURCE_ID
ZEXP_MCHC
EXPERT_WRITE_VALIDITY_AREA
US
ZEXP_DETR
Detergents
ZEXP_MCHC
Description
comp_V1-21.ruc
Rule File
comp_V1-21.mdb
Mapping Database
Comp_V1-21.pdf
Functional Description
M Factor
File name
Description
M_Factor_V1-0.ruc
Rule File
M_Factor_V1-0.mdb
Mapping Database
36
SAP AG
M_Factor_V1-0.pdf
Name
ZEXP_COMP
Mapping Database
comp_V1-21.mdb
Rule File
comp_V1-21.ruc
Additional Settings
Name
IgnoreWarnings
Value
355
Description
EU_to_GHS_V1-51.ruc
Rule File
EU_to_GHS_Annex_VII_externvalues.mdb
EU_to_GHS_V1-51.mdb
Mapping
Database
with
reference
to
the
external
database
EU_to_GHS_EU_Annex_VII_externvalues.mdb
(Annex VII of the consolidated GHS EU proposal)
GS_physchem_V1-21.ruc
37
SAP AG
EU_to_GHS__HISTORY.mdb
ReleaseNote_EU_to_GHS_V1-51.pdf
Release Note
EU_to_GHS_V1-51.pdf
Functional Description
GHS
File name
Description
GHS_V2-3.ruc
Rule File
GHS_V2-3.mdb
Mapping Database
GHS_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
GS_physchem_V1-21.ruc
GHS_sub_pb2009_V1-3.ruc
GHS_label_V1-1.ruc
GHS_pure_V1-1.ruc
GHS_expl_V1-5.ruc
GHS__HISTORY.mdb
ReleaseNote_GHS_V2-3.pdf
Release Note
GHS_V2-3.pdf
Functional Description
Hazcomp GHS
File name
Description
Hazcomp_GHS_V1-52.ruc
Rule File
Hazcomp_GHS_V1-52.mdb
Mapping Database
Hazcomp_GHS_externvalues.mdb
External Database
GS_base_V1-1.ruc
38
SAP AG
ReleaseNote_Hazcomp_GHS_V1-52.pdf
Release Note
HazardComp_GHS_V1-52.pdf
Functional Description
Name
ZEXP_RTGHS
Mapping Database
EU_TO_GHS_V1-51.mdb
Rule File
EU_to_GHS_V1-51.ruc
Name
ZEXP_GHS
Mapping Database
GHS_V2-3.mdb
Rule File
GHS_V2-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HCGHS
Mapping Database
Hazcomp_GHS_V1-52.mdb
Rule File
Hazcomp_GHS_V1-52.ruc
39
SAP AG
Name
GHS_SUB_PB2009_1_3
Rule File
GHS_sub_pb2009_V1-3.ruc
Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc
Name
GHS_LABEL_1_1
Rule File
GHS_label_V1-1.ruc
Description
DP_AU_V2-34.ruc
Rule File
DP_AU_V2-34.mdb
Mapping Database
DP_AU_externvalues.mdb
External Database
GS_base_V1_1.ruc
DP_AU__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
DP_AU_V2-34.pdf
Functional Description
40
SAP AG
Description
HazardComp_AU_V2-51.ruc
Rule File
HazardComp_AU_V2-51.mdb
Mapping Database
HazardComp_AU_externvalues.mdb
External Database
GS_base_V1-1.ruc
HazardComp_AU__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
HazardComp_AU_V2-51.pdf
Functional Description
Classification CN
File name
Description
Classification_CN_V2-51.ruc
Rule File
Classification_CN_V2-51.mdb
Mapping Database
Classification_CN_externvalues.mdb
External Database
GS_base_V1-1.ruc
Classification_CN__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
Classification_CN_V2-51.pdf
Functional Description
HazardComp CN
File name
Description
HazardComp_CN_V2-5.ruc
Rule File
HazardComp_CN_V2-5.mdb
Mapping Database
HazardComp_CN_externvalues.mdb
External Database
GS_base_V1-1.ruc
HazardComp_CN__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
HazardComp_CN_V2-5.pdf
Functional Description
GHS CN
File name
Description
GHS_CN_V1-3.ruc
Rule File
41
SAP AG
Mapping Database
GHS_CN_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GHS_sub_pb2007_V1-4.ruc
GHS_label_V1-1.ruc
GHS_pure_V1-1.ruc
GHS_expl_V1-5.ruc
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
GS_physchem_V1-21.ruc
GHS_CN__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
GHS_CN_V1-3.pdf
Functional Description
Classification JP
File name
Description
Classification_JP_V2-62.ruc
Rule File
Classification_JP_V2-62.mdb
Mapping Database
Classification_JP_externvalues.mdb
External Database
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
Classification_JP__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
Classification_JP_V2-62.pdf
Functional Description
Fire Service JP
File name
Description
Fire_Service_JP_V2-9.ruc
Rule File
42
SAP AG
Mapping Database
Fire_Service_JP_externvalues.mdb
External Database
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
Fire_Service_JP__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
Fire_Service_JP_V2-9.pdf
Functional Description
HazardComp JP
File name
Description
HazardComp_JP_V2-81.ruc
Rule File
HazardComp_JP_V2-81.mdb
Mapping Database
HazardComp_JP_externvalues.mdb
External Database
GS_base_V1-1.ruc
HazardComp_JP__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
HazardComp_JP_V2-81.pdf
Functional Description
GHS JP
File name
Description
GHS_JP_V1-3.ruc
Rule File
GHS_JP_V1-3.mdb
Mapping Database
GHS_JP_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GHS_sub_pb2007_V1-4.ruc
GHS_label_V1-1.ruc
GHS_pure_V1-1.ruc
GHS_expl_V1-5.ruc
GS_base_V1-1.ruc
43
SAP AG
GS_physchem_V1-21.ruc
GHS_JP__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
GHS_JP_V1-3.pdf
Functional Description
GHS KR
File name
Description
GHS_KR_V1-7.ruc
Rule File
GHS_KR_V1-7.mdb
Mapping Database
GHS_KR_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GHS_sub_pb2007_V1-4.ruc
GHS_label_V1-1.ruc
GHS_pure_V1-1.ruc
GHS_expl_V1-5.ruc
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
GS_physchem_V1-21.ruc
GHS_KR__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
GHS_KR_V1-7.pdf
Functional Description
DSSMA KR
File name
Description
DSSMA_KR_V1-7.ruc
Rule File
DSSMA_KR_V1-7.mdb
Mapping Database
DSSMA_KR_externvalues.mdb
External Database
44
SAP AG
GS_physchem_V1-21.ruc
DSSMA_KR__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
DSSMA_KR_V1-7.pdf
Functional Description
HazardComp KR
File name
Description
HazardComp_KR_V2-52.ruc
Rule File
HazardComp_KR_V2-52.mdb
Mapping Database
HazardComp_KR_externvalues.mdb
External Database
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
HazardComp_KR__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
HazardComp_KR_V2-52.pdf
Functional Description
GHS NZ
File name
Description
GHS_NZ_V1-6.ruc
Rule File
GHS_NZ_V1-6.mdb
Mapping Database
GHS_NZ_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GHS_sub_pb2007_V1-4.ruc
GHS_label_V1-1.ruc
GHS_pure_V1-1.ruc
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
45
SAP AG
GHS_NZ__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
GHS_NZ_V1-6.pdf
Functional Description
HazardComp NZ
File name
Description
HazardComp_NZ_V1-3.ruc
Rule File
HazardComp_NZ_V1-3.mdb
Mapping Database
HazardComp_NZ_externvalues.mdb
External Database
GS_base_V1-1.ruc
HazardComp_NZ__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
HazardComp_NZ_V1-3.pdf
Functional Description
GHS SG
File name
Description
GHS_SG_V1-3.ruc
Rule File
GHS_SG_V1-3.mdb
Mapping Database
GHS_SG_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GHS_sub_pb2007_V1-4.ruc
GHS_label_V1-1.ruc
GHS_pure_V1-1.ruc
GHS_expl_V1-5.ruc
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
GS_physchem_V1-21.ruc
46
SAP AG
ReleaseNote_APA_2011-1.pdf
Release Note
GHS_SG_V1-3.pdf
Functional Description
HazardComp SG
File name
Description
HazardComp_SG_V1-1.ruc
Rule File
HazardComp_SG_V1-1.mdb
Mapping Database
HazardComp_SG_externvalues.mdb
External Database
GS_base_V1-1.ruc
HazardComp_SG__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
HazardComp_SG_V1-1.pdf
Functional Description
Classification TW
File name
Description
Classification_TW_V2-42.ruc
Rule File
Classification_TW_V2-42.mdb
Mapping Database
Classification_TW_externvalues.mdb
External Database
GS_base_V1-1.ruc
Classification_TW__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
Classification_TW_V2-42.pdf
Functional Description
HazardComp TW
File name
Description
HazardComp_TW_V2-51.ruc
Rule File
HazardComp_TW_V2-51.mdb
Mapping Database
HazardComp_TW_externvalues.mdb
External Database
GS_base_V1-1.ruc
HazardComp_TW__HISTORY.mdb
47
SAP AG
Release Note
HazardComp_TW_V2-51.pdf
Functional Description
GHS TW
File name
Description
GHS_TW_V1-3.ruc
Rule File
GHS_TW_V1-3.mdb
Mapping Database
GHS_TW_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GHS_sub_pb2007_V1-4.ruc
GHS_label_V1-1.ruc
GHS_pure_V1-1.ruc
GHS_expl_V1-5.ruc
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
GS_physchem_V1-21.ruc
GHS_TW__HISTORY.mdb
ReleaseNote_APA_2011-1.pdf
Release Note
GHS_TW_V1-3.pdf
Functional Description
Name
ZEXP_DP_AU
Mapping Database
DP_AU_V2-34.mdb
48
SAP AG
DP_AU_V2-34.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_CN_CN
Mapping Database
Classification_CN_V2-51.mdb
Rule File
Classification_CN_V2-51.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSCN
Mapping Database
GHS_CN_V1-3.mdb
Rule File
GHS_CN_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_CN_JP
Mapping Database
Classification_JP_V2-62.mdb
Rule File
Classification_JP_V2-62.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_FS_JP
Mapping Database
Fire_Service_JP_V2-9.mdb
Rule File
Fire_Service_JP_V2-9.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
49
SAP AG
Name
ZEXP_HC_JP
Mapping Database
HazardComp_JP_V2-81.mdb
Rule File
HazardComp_JP_V2-81.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSJP
Mapping Database
GHS_JP_V1-3.mdb
Rule File
GHS_JP_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSKR
Mapping Database
GHS_KR_V1-7.mdb
Rule File
GHS_KR_V1-7.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_DS_KR
Mapping Database
DSSMA_KR_V1-7.mdb
Rule File
DSSMA_KR_V1-7.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HC_KR
50
SAP AG
HazardComp_KR_V2-52.mdb
Rule File
HazardComp_KR_V2-52.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSNZ
Mapping Database
GHS_NZ_V1-6.mdb
Rule File
GHS_NZ_V1-6.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSSG
Mapping Database
GHS_SG_V1-3.mdb
Rule File
GHS_SG_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HC_SG
Mapping Database
HazardComp_SG_V1-1.mdb
Rule File
HazardComp_SG_V1-1.ruc
Name
ZEXP_GHSTW
Mapping Database
GHS_TW_V1-3.mdb
Rule File
GHS_TW_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
51
SAP AG
Name
GHS_SUB_PB2007_1_4
Rule File
GHS_sub_pb2007_V1-4.ruc
Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc
Name
GHS_LABEL_1_1
Rule File
GHS_label_V1-1.ruc
LABEL_S
Description
DAPEC_V3-1.ruc
Rule File
DAPEC_V3-1.mdb
Mapping Database
52
SAP AG
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
GS_physchem_V1-21.ruc
comp_LEC50_V1-01.ruc
DAPEC__HISTORY.mdb
ReleaseNote_DAPEC_V3-1.pdf
Release Note
DAPEC_V3-1.pdf
Functional Description
GHS EU
File name
Description
GHS_EU_V1-6.ruc
Rule File
GHS_EU_V1-6.mdb
Mapping Database
GHS_EU_externvalues.mdb
External Database
GHS_sub_pb2007_V1-4.ruc
GHS_label_V1-1.ruc
GHS_pure_V1-1.ruc
GHS_expl_V1-5.ruc
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
GHS_EU__HISTORY.mdb
ReleaseNote_GHS_EU_V1-6.pdf
Release Note
GHS_EU_V1-6.pdf
Functional Description
EU to GHS
File name
Description
53
SAP AG
Rule File
EU_to_GHS_Annex_VII_externvalues.mdb
EU_to_GHS_V1-51.mdb
Mapping
Database
with
reference
to
the
external
database
EU_to_GHS_EU_Annex_VII_externvalues.mdb
(Annex VII of the consolidated GHS EU proposal)
GS_physchem_V1-21.ruc
GHS_label_V1-0.ruc
EU_to_GHS__HISTORY.mdb
ReleaseNote_EU_to_GHS_V1-51.pdf
Release Note
EU_to_GHS_V1-51.pdf
Functional Description
HazardComp EU
File name
Description
HazardComp_EU_V3-0.ruc
Rule File
HazardComp_EU_V3-0.mdb
Mapping Database
HazardComp_EU_externvalues.mdb
External Database
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
comp_LEC50_V1-01.ruc
HazardComp_EU__HISTORY.mdb
ReleaseNote_HC_EU_V3-0.pdf
Release Note
HazardComp_EU_V3-0.pdf
Functional Description
CLNOT
File name
Description
CL_for_notification_V1-2.ruc
Rule File
CL_for_notification_V1-2.mdb
GHS_EU_externvalues.mdb
54
SAP AG
GHS_sub_pb2007_V1-4.ruc
ReleaseNote_CL_for_notification_V1-2.pdf
Release Note
CL_for_notification_V1-2.pdf
Functional Description
Name
ZEXP_DAPEC
Mapping Database
DAPEC_V3-1.mdb
Rule File
DAPEC_V3-1.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSEU
Mapping Database
GHS_EU_V1-6.mdb
Rule File
GHS_EU_V1-6.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_RTGHS
Mapping Database
EU_TO_GHS_V1-51.mdb
Rule File
EU_to_GHS_V1-51.ruc
55
SAP AG
Name
ZEXP_HC_EU
Mapping Database
HazardComp_EU_V3-0.mdb
Rule File
HazardComp_EU_V3-0.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_CLNOT
Mapping Database
CL_for_notification_V1-2.mdb
Rule File
CL_for_notification_V1-2.ruc
Name
GHS_SUB_PB2007_1_4
Rule File
GHS_sub_pb2007_V1-4.ruc
Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc
56
SAP AG
Description
DPDplus_lead_V1-11.ruc
Rule File
DPDplus_lead_V1-11.mdb
Mapping Database
DPDplus_lead_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
GS_ident_V1-0.ruc
DPDplus_lead__HISTORY.mdb
ReleaseNote_DPDplus_lead_V1-11.pdf
Release Note
DPDplus_lead_V1-11.pdf
Functional Description
Name
ZEXP_DPDL
Mapping Database
DPDplus_lead_V1-11.mdb
Rule File
DPDplus_lead_V1-11.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
57
SAP AG
REACH
DPDplus_lead
REACH_REG
DPDplus_lead
Description
CMR_EU_V1-02.ruc
Rule File
CMR_EU_V1-02.mdb
Mapping Database
CMR_EU_externvalues.mdb
External Database
GS_base_V1-1.ruc
CMR_EU__HISTORY.mdb
ReleaseNote_EU_2011-1.pdf
Release Note
CMR_EU_V1-02.pdf
Functional Description
Detergents
File name
Description
Detergents_V1-0.ruc
Rule File
Detergents_V1-0.mdb
Mapping Database
58
SAP AG
External Database
GS_base_V1-1.ruc
Detergents_V1-0.pdf
Functional Description
ICPE
File name
Description
ICPE_V1-11.ruc
Rule File
ICPE_V1-11.mdb
Mapping Database
ICPE_V1-11.pdf
Functional Description
ReleaseNote_EU_2011-1.pdf
Release Note
ICPE__HISTORY.mdb
Maladies Professionelles
File name
Description
MaladiesProfessionnelles_V1-41.ruc
Rule File
MaladiesProfessionnelles_V1-41.mdb
Mapping Database
MaladiesProfessionnelles_externvalues.mdb External
Database
MaladiesProfessionnelles__HISTORY.mdb
ReleaseNote_EU_2011-1.pdf
Release Note
MaladiesProfessionnelles_V1-41.pdf
Functional Description
MAL Code
File name
Description
MAL_Code_V1-3.ruc
Rule File
MAL_Code_V1-3.mdb
Mapping Database
GS_base_V1-1.ruc
MAL_Code__HISTORY.mdb
ReleaseNote_EU_2011-1.pdf
Release Note
MAL-Code_V1-3.pdf
Functional Description
Seveso II
File name
Description
Seveso-II_V1-41.ruc
Rule File
Seveso-II_V1-41.mdb
Mapping Database
59
SAP AG
External Database
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
Seveso-II__HISTORY.mdb
ReleaseNote_EU_2011-1.pdf
Release Note
Seveso-II_V1-41.pdf
Functional Description
TA Luft
File name
Description
TAluft_V4-21.ruc
Rule File
TAluft_V4-21.mdb
Mapping Database
TAluft_externvalues.mdb
External Database
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
TAluft__HISTORY.mdb
ReleaseNote_EU_2011-1.pdf
Release Note
TALuft_V4-21.pdf
Functional Description
TRGS510
File name
Description
TRGS510_V1-0.ruc
Rule File
TRGS510_V1-0.mdb
Mapping Database
TRGS510_externvalues.mdb
External Database
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
TRGS510_V1-0.pdf
Functional Description
TRGS900
File name
Description
TRGS_900_V1-22.ruc
Rule File
TRGS_900_V1-22.mdb
Mapping Database
TRGS_900_externvalues.mdb
External Database
60
SAP AG
TRGS_900__HISTORY.mdb
ReleaseNote_EU_2011-1.pdf
Release Note
TRGS_900_V1-22.pdf
Functional Description
VbF AT
File name
Description
VbF_AT_V1-31.ruc
Rule File
VbF_AT_V1-31.mdb
Mapping Database
GS_physchem_V1-21.ruc
VbF_AT__HISTORY.mdb
ReleaseNote_EU_2011-1.pdf
Release Note
VbF_AT_V1-31.pdf
Functional Description
VOC CH
File name
Description
VOC_CH_V1-31.ruc
Rule File
VOC_CH_V1-31.mdb
Mapping Database
VOC_CH_externvalues.mdb
External Database
GS_base_V1-1.ruc
VOC_CH__HISTORY.mdb
ReleaseNote_EU_2011-1.pdf
Release Note
VOC_CH_V1-31.pdf
Functional Description
VOC EU
File name
Description
VOC_EU_V1-33.ruc
Rule File
VOC_EU_V1-33.mdb
Mapping Database
VOC_EU_externvalues.mdb
External Database
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
61
SAP AG
ReleaseNote_EU_2011-1.pdf
Release Note
VOC_EU_V1-33.pdf
Functional Description
VOC PaintCoat
File name
Description
VOC_PaintCoat_V1-4.ruc
Rule File
VOC_PaintCoat_V1-4.mdb
Mapping Database
VOC_PaintCoat_externvalues.mdb
External Database
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
VOC_PaintCoat__HISTORY.mdb
ReleaseNote_EU_2011-1.pdf
Release Note
VOC_PaintCoat_V1-4.pdf
Functional Description
WGK
File name
Description
WGK_V1-81.ruc
Rule File
WGK_V1-81.mdb
Mapping Database
WGK_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
WGK__HISTORY.mdb
ReleaseNote_EU_2011-1.pdf
Release Note
WGK_V1-81.pdf
Functional Description
62
SAP AG
Name
ZEXP_CMREU
Mapping Database
CMR_EU_V1-02.mdb
Rule File
CMR_EU_V1-02.ruc
Name
ZEXP_DETR
Mapping Database
Detergents_V1-0.mdb
Rule File
Detergents_V1-0.ruc
Name
ZEXP_ICPE
Mapping Database
ICPE_V1-11.mdb
Rule File
ICPE_V1-11.ruc
Name
ZEXP_MAL
Mapping Database
MAL_Code_V1-3.mdb
Rule File
MAL_Code_V1-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_F_MP
Mapping Database
MaladiesProfessionnelles_V1-41.mdb
Rule File
MaladiesProfessionnelles_V1-41.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
63
SAP AG
Name
ZEXP_SEVE
Mapping Database
Seveso-II_V1-41.mdb
Rule File
Seveso-II_V1-41.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_TAL
Mapping Database
TAluft_V4-21.mdb
Rule File
TAluft_V4-21.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_TR510
Mapping Database
TRGS510_V1-0.mdb
Rule File
TRGS510_V1-0.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_TR90
Mapping Database
TRGS_900_V1-22.mdb
Rule File
TRGS_900_V1-22.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_VBFAT
64
SAP AG
VbF_AT_V1-31.mdb
Rule File
VbF_AT_V1-31.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_VOC
Mapping Database
VOC_CH_V1-31.mdb
Rule File
VOC_CH_V1-31.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_VOCEU
Mapping Database
VOC_EU_V1-33.mdb
Rule File
VOC_EU_V1-33.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_VOCPC
Mapping Database
VOC_PaintCoat_V1-4.mdb
Rule File
VOC_PaintCoat_V1-4.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_WGK
Mapping Database
WGK_V1-81.mdb
Rule File
WGK_V1-81.ruc
Additional Settings
65
SAP AG
IgnoreWarnings
Value
322
ZEXP_DETR
Detergents
Description
CAA_V1-21.ruc
Rule File
CAA_V1-21.mdb
Mapping Database
GS_base_V1-1.ruc
CAA__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
CAA_V1-21.pdf
Functional Description
Description
CWA_V1-01.ruc
Rule File
CWA_V1-01.mdb
Mapping Database
66
SAP AG
CWA__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
CWA_V1-01.pdf
Functional Description
EU to OSHA
File name
Description
EU_to_OSHA_V1-1.ruc
Rule File
EU_to_OSHA_V1-1.mdb
Mapping Database
EU_to_OSHA_externvalues.mdb
External Database
EU_to_OSHA__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
EU_to_OSHA_V1-1.pdf
Functional Description
HazardComp US
File name
Description
HazardComp_US_V2-71.ruc
Rule File
HazardComp_US_V2-71.mdb
Mapping Database
HazardComp_US_externvalues.mdb
External Database
GS_base_V1-1.ruc
HazardComp_US__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
HazardComp_US_V2-71.pdf
Functional Description
HMIS
File name
Description
HMIS_V2-5.ruc
Rule File
HMIS_V2-5.mdb
Mapping Database
HMIS_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-1.ruc
67
SAP AG
GS_physchem_V1-21.ruc
HMIS__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
HMIS_V2-5.pdf
Functional Description
Description
MCHC_V1-0.ruc
Rule File
MCHC_V1-0.mdb
Mapping Database
GS_base_V1-1.ruc
ReleaseNote_NA_2011-1.pdf
Release Note
MCHC_V1-0.pdf
Functional Description
NFPA
File name
Description
NFPA_V1-7.ruc
Rule File
NFPA_V1-7.mdb
Mapping Database
NFPA_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
GS_physchem_V1-21.ruc
NFPA__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
NFPA_V1-7.pdf
Functional Description
Description
OSHA_Hazard_Determination_V2-71.ruc
Rule File
68
SAP AG
Mapping Database
OSHA_Hazard_Determination_
externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
GS_physchem_V1-21.ruc
OSHA_Hazard_Determination__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
OSHA_SARA_Hazard_Determination_V2-71.pdf
Functional Description
SaraComp
File name
Description
SaraComp_V2-11.ruc
Rule File
SaraComp_V2-11.mdb
Mapping Database
SaraComp_externvalues.mdb
External Database
GS_base_V1-1.ruc
SaraComp__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
SaraComp_V2-11.pdf
Functional Description
SpillReport
File name
Description
SpillReport_V2-01.ruc
Rule File
SpillReport_V2-01.mdb
Mapping Database
SpillReport_externvalues.mdb
External Database
GS_base_V1-1.ruc
SpillReport__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
SpillReport_V2-01.pdf
Functional Description
69
SAP AG
Description
US_State_RTK_V1-74.ruc
Rule File
US_State_RTK_V1-74.mdb
Mapping Database
US_State_RTK_externvalues.mdb
External Database
GS_base_V1-1.ruc
US_State_RTK__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
US_State_RTK_V1-74.pdf
Functional Description
CA PBT
File name
Description
CAPBT_V1-01.ruc
Rule File
CAPBT_V1-01.mdb
Mapping Database
GS_base_V1-1.ruc
CAPBT__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
CAPBT_V1-01.pdf
Functional Description
WHMISClassification
File name
Description
WHMISCLASS_V2-62.ruc
Rule File
WHMISCLASS_V2-62.mdb
Mapping Database
WHMISCLASS_externvalues.mdb
External Database
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
GS_physchem_V1-21.ruc
WHMISCLASS__HISTORY.mdb
70
SAP AG
Release Note
WHMISClassification_V2-62.pdf
Functional Description
WHMISComposition
File name
Description
WHMISComposition_V1-73.ruc
Rule File
WHMISComposition_V1-73.mdb
Mapping Database
WHMISComposition_externvalues.mdb
External Database
GS_base_V1-1.ruc
WHMISComposition__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
WHMISComposition_V1-73.pdf
Functional Description
GHS BR
File name
Description
GHS_BR_V1-2.ruc
Rule File
GHS_BR_V1-2.mdb
Mapping Database
GHS_BR_externvalues.mdb
External Database
GHS_sub_pb2007_V1-4.ruc
GHS_label_V1-1.ruc
GHS_pure_V1-1.ruc
GHS_expl_V1-5.ruc
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
GHS_BR__HISTORY.mdb
ReleaseNote_NA_2011-1.pdf
Release Note
GHS_BR_V1-2.pdf
Functional Description
HazardComp BR
File name
Description
HazardComp_BR_V1-1.ruc
Rule File
71
SAP AG
Mapping Database
HazardComp_BR_externvalues.mdb
External Database
GS_base_V1-1.ruc
HazardComp_BR__HISTORY.mdb
HazardComp_BR_V1-1.pdf
Functional Description
Name
ZEXP_CWA
Mapping Database
CWA_V1-01.mdb
Rule File
CWA_V1-01.ruc
Name
ZEXP_HAZCO
Mapping Database
HazardComp_US_V2-71.mdb
Rule File
HazardComp_US_V2-71.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HMIS
Mapping Database
HMIS_V2-5.mdb
Rule File
HMIS_V2-5.ruc
72
SAP AG
ZEXP_MCHC
Mapping Database
MCHC_V1-0.mdb
Rule File
MCHC_V1-0.ruc
Name
ZEXP_NFPA
Mapping Database
NFPA_V1-7.mdb
Rule File
NFPA_V1-7.ruc
Name
ZEXP_OSHA
Mapping Database
OSHA_Hazard_Determination_V2-71.mdb
Rule File
OSHA_Hazard_Determination_V2-71.ruc
Name
ZEXP_SPRQ
Mapping Database
SpillReport_V2-01.mdb
Rule File
SpillReport_V2-01.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_RTK
Mapping Database
US_State_RTK_V1-74.mdb
Rule File
US_State_RTK_V1-74.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_CAPBT
Mapping Database
CAPBT_V1-01.mdb
Rule File
CAPBT_V1-01.ruc
73
SAP AG
Name
ZEXP_WHMIS
Mapping Database
WHMISCLASS_V2-62.mdb
Rule File
WHMISCLASS_V2-62.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HC_CA
Mapping Database
WHMISComposition_V1-73.mdb
Rule File
WHMISComposition_V1-73.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_GHSBR
Mapping Database
GHS_BR_V1-2.mdb
Rule File
GHS_BR_V1-2.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
Name
ZEXP_HC_BR
Mapping Database
HazardComp_BR_V1-1.mdb
Rule File
HazardComp_BR_V1-1.ruc
Additional Settings
Name
IgnoreWarnings
Value
322
74
SAP AG
Name
GHS_SUB_PB2007_1_4
Rule File
GHS_sub_pb2007_V1-4.ruc
Name
GHS_EXPL_1_5
Rule File
GHS_expl_V1-5.ruc
Name
GHS_LABEL_1_1
Rule File
GHS_label_V1-1.ruc
ZEXP_MCHC
Environment parameter
EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION
C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE
EXPERT_READ_RATING
PUBLIC
EXPERT_READ_VALIDITY_AREA
US
EXPERT_RES_BY_SRSID_OWNID_FLG
EXPERT_RULE_SET
ZEXP_MCHC
EXPERT_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
75
SAP AG
ZEXP_MCHC
EXPERT_WRITE_VALIDITY_AREA
US
ZEXP_MCHC
Description
NotStat_frame_master_V3-3.ruc
Rule File
NotStat_frame_master_ProdComp_V3-3.mdb
NotStat_frame_master_StandComp_V3-3.mdb
NotStat_externvalues.mdb
External Database
NotStat_V3-3.ruc
NotStat_sub_TSCA12b_V3-3.ruc
NotStat_sub_expl_V3-3.ruc
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
NotStat_frame_master__HISTORY.mdb
ReleaseNote_NotStat_V3-3.pdf
Release Note
Notstat_V3-3.pdf
Functional Description
RestrictionStatus
File name
Description
76
SAP AG
Rule File
RestrictionStatus_V1-71.mdb
Mapping Database
RestrictionStatus_externvalues.mdb
External Database
GS_base_V1-1.ruc
RestrictionStatus__HISTORY.mdb
ReleaseNote_RestrictionStatus_V1-71.pdf
Release Note
RestrictionStatus_V1-71.pdf
Functional Description
Name
ZEXP_NOTS
NotStat_frame_master_ProdComp_V3-3.mdb
(ProdComp variant)
NotStat_frame_master_StandComp_V3-3.mdb
(StandComp variant)
Rule File
NotStat_frame_master_V3-3.ruc
Additional Settings
Name
IgnoreWarnings
Value
322,330,332,355
Name
ZEXP_RESST
Mapping Database
RestrictionStatus_V1-71.mdb
Rule File
RestrictionStatus_V1-71.ruc
77
SAP AG
Name
NOTSTAT_SUB
Rule File
NotStat_V3-3.ruc
Name
NOTSTAT_SUB_TSCA12B
Rule File
NotStat_sub_TSCA12b_V3-3.ruc
Name
NOTSTAT_SUB_EXPL
Rule File
NotStat_sub_expl_V3-3.ruc
Description
DangGoods_master_global_V4-0.ruc
DangGoods_master_V4-0.ruc
DangGoods_master_global_V4-0.mdb
DangGoods_master_V4-0.mdb
DangGoods_externvalues.mdb
External Database
78
SAP AG
sub rule set (central part for classification process for solids/liquids)
GHS_sub_pb2009_V1-1.ruc
DangGoods_gas_V4-0.ruc
sub rule set (classification for gaseous mixtures and hazard inducer determination)
DangGoods_sub_binary_V4-0.ruc
DangGoods_report_quant_V4-0.ruc
GS_ident_externvalues.mdb
the
external
database
GS_ident_externvalues.mdb must be located
in the same directory
GS_base_V1-1.ruc
GS_ident_V1-0.ruc
GS_physchem_V1-21.ruc
DangGoods_master__HISTORY.mdb
ReleaseNote_DangGoods_V4-0.pdf
Release Note
DangGoods_V4-0.pdf
Functional Description
Name
ZEXP_DG
Mapping Database
DangGoods_master_global_V4-0.mdb
DangGoods_master_V4-0.mdb
Rule File
DangGoods_master_global_V4-0.ruc
DangGoods_master_V4-0.ruc
79
SAP AG
Name
DG_SUB_4_0
Rule File
DangGoods_V4-0.ruc
Name
DG_SUB_GAS_4_0
Rule File
DangGoods_gas_V4-0.ruc
Name
DG_GAS_BINARY
Rule File
DangGoods_sub_binary_V4-0.ruc
Name
DG_RQ_4_0
Rule File
DangGoods_report_quant_V4-0.ruc
Name
GHS_SUB_PB2009_1_1
Rule File
GHS_sub_pb2009_V1-1.ruc
80
SAP AG
Description
MSDSRule_V3-7.ruc
Rule File
MSDSRule_V3-7.mdb
MSDSMaker.mdb
MSDSRule_sub_V3-7.ruc
GS_base_V1-1.ruc
GS_physchem_V1-21.ruc
ReleaseNote_MSDSMaker_V3-7.pdf
Release Note
MSDSMaker_V3-7.pdf
Functional Description
Name
ZEXP_SDS
Mapping Database
Rule File
MSDSRule_V3-7.ruc
81
SAP AG
Name
MSDSRULE_SUB
Rule File
MSDSRule_sub_V3-7.ruc
82
SAP AG
Where to do
What to do
General
O
Review documentation
Technical Part
O
Upload files
Import transports
Customizing (spro)
Import templates
Templates
Identify changes in templates and consider these for the updated templates
Detailed information on how to execute the single steps will be provided in this How-To-documents:
Description
83
SAP AG
MSDS Templates
SDS_AP_AU_2011_1.dat
Template Import-file
SDS_AP_CN_2011_1.dat
Template Import-file
SDS_AP_JP_2011_1.dat
Template Import-file
SDS_AP_KR_2011_1.dat
Template Import-file
SDS_AP_TW_2011_1.dat
Template Import-file
SDS_AP_NZ_2011_1.dat
Template Import-file
SDS_AP_SG_2011_1.dat
Template Import-file
SDS_AP_AU_2011_1_unix.dat
SDS_AP_CN_2011_1_unix.dat
SDS_AP_JP_2011_1_unix.dat
SDS_AP_KR_2011_1_unix.dat
SDS_AP_TW_2011_1_unix.dat
SDS_AP_NZ_2011_1_unix.dat
SDS_AP_SG_2011_1_unix.dat
SDS_AP_AU_2011_1.doc
Template document-file
SDS_AP_CN_2011_1.doc
Template document-file
SDS_AP_JP_2011_1.doc
Template document-file
SDS_AP_KR_2011_1.doc
Template document-file
SDS_AP_TW_2011_1.doc
Template document-file
SDS_AP_NZ_2011_1.doc
Template document-file
SDS_AP_SG_2011_1.doc
Template document-file
SDS_AP_AU_2011_1_Datamapping.pdf
SDS_AP_CN_2011_1_Datamapping.pdf
SDS_AP_CN_2011_1_changes_marked_
yellow.doc
SDS_AP_CN_2011_1_Datamapping_highlighted.pdf
DataMapping
highlighted
SDS_AP_JP_2011_1_Datamapping.pdf
SDS_AP_JP_2011_1_changes_marked_
yellow.doc
SDS_AP_JP_2011_1_Datamapping_highlighted.pdf
DataMapping
highlighted
SDS_AP_KR_2011_1_Datamapping.pdf
SDS_AP_KR_2011_1_changes_marked_
yellow.doc
84
SAP AG
MSDS Templates
SDS_AP_KR_2011_1_Datamapping_highlighted.pdf
DataMapping
highlighted
SDS_AP_TW_2011_1_Datamapping.pdf
SDS_AP_TW_2011_1_changes_marked_
yellow.doc
SDS_AP_TW_2011_1_Datamapping_highlighted.pdf
DataMapping
highlighted
SDS_AP_NZ_2011_1_Datamapping.pdf
SDS_AP_NZ_2011_1_changes_marked_
yellow.doc
SDS_AP_NZ_2011_1_Datamapping_highlighted.pdf
DataMapping
highlighted
DataMapping - Document for SDS SG (Singapore)
SDS_AP_SG_2011_1_Datamapping.pdf
SDS_AP_SG_2011_1_Datamapping_highlighted.pdf
DataMapping
highlighted
SDS WWI Layout with updated parts highlighted
SDS_AP_SG_2011_1_changes_marked_
yellow.doc
Description
SDS_EU_2011_1.dat
Import-file Template
SDS_EU_2011_1.doc
Template-file
SDS_EU_2011_1_unix.dat
SDS_EU_2011_1_Datamapping.pdf
DataMapping - Document
85
SAP AG
MSDS Templates
SDS_EU_2011_1_changes_marked_yellow.doc
SDS_EU_2011_1_Datamapping_highlighted.pdf DataMapping
highlighted
Description
ReleaseNote_SDS_GHS_2011_1.pdf
ReleaseNote
Description
SDS_NA_2011_1.dat
Import-file Template
SDS_NA_2011_1.doc
Template-file
SDS_NA_2011_1_unix.dat
SDS_NA_2011_1_Datamapping.pdf
DataMapping - Document
86
SAP AG
MSDS Templates
SDS_NA_2011_1_changes_marked_ yellow.doc
SDS_NA_2011_1_Datamapping_highlighted.pdf DataMapping
highlighted
SDS_BR_2011_1.dat
Import-file Template
SDS_BR_2011_1.doc
Template-file
SDS_BR_2011_1_unix.dat
SDS_BR_2011_1_Datamapping.pdf
DataMapping - Document
SDS_BR_2011_1_changes_marked_ yellow.doc
SDS_BR_2011_1_Datamapping_highlighted.pdf DataMapping
highlighted
87
SAP AG
SAP AG
How To ...
Ask your administrator for the upload path on your application server. You may check for the
path also via transaction AL11.
For example :
\\<server>\ \\Globaltrans\trans or F:\usr\sap\trans\upload
Use transaction CG3Z for uploading and choose BIN(ary) transfer format as shown in the
screen shot below.
Size of path and filename is limited. It may be necessary to either shorten the import file names
or choose a short directory path to upload the files.
Please check that you upload the correct files for the operating system of your application
server. The update delivery includes import files formatted for MS Windows and UNIX. You
can get info about the OS in R/3 at -> System -> Status. Under the "Host data" header you can
see the operating system used by the R/3 server. You may also have to consider if Unicode
or Non Unicode system.
The upload of import files onto the application server and the import into EHS are completely
independent from any language specific settings on the front-end PC, i.e. phrases can be
uploaded and imported with every regional default setting.
89
SAP AG
How To ...
On the second screen you will see a list of available queues (After pressing the van-icon).
Depending to your system you may have virtual transport queue(s) or not. The virtual queue
enables you to transfer transports between multiple systems if you uploaded the transports
into the virtual queue (and the systems are connected to the virtual queue).
Double click the queue you want to work with.
If you have uploaded the corresponding pair of files (co-file and datafile) to the appropriate
places they appear in the transport queue. If not you may use the menu ->"Extras->other
90
SAP AG
How To ...
requests->add". Then you will get a dialog box to choose additional transport files to be shown
in the actual transport queue.
There is a naming convention :
Zxxxxxxx.yyy is the name of the file where Z is K for the co-file and R for the data file.
x is a numerical value. y is the extension. The extension is the System ID (i.e. SH2, TD3 ... )
After you uploaded the file you will find the files in the queue with a different name! In the
queue they will appear like:
yyyKxxxxxxx (The system ID as a prefix followed by the "K" of the co-files and the numeric
value.)
Example : K102002.SH2 and R102002.SH2 would be the filenames and the list entry would
be : SH2K102002
Setting filters :
To find the transports you may use a filter. The transports can be identified by user who created
the transport - not the user who did the upload!
Setting the filters is initiated by a mouse click on the column to be filtered and then a click on
the filter-icon. More than one filter can be defined. To delete a filter start the same way but in
the dialog click on the bin - icon.
To specify the transports to be imported use the 4th button (black arrow pointing to the red
button) you may mark more than one item. Be careful, some transports have dependencies
so those cannot be imported at once.
If the selection is complete start the import by pressing the van-icon with the small orange top
edge. A dialog will appear where you can give additional options. In most cases the standard
flags will be sufficient.
If you start the import you will see the van-symbol on the right side of the list of transports. If you
refresh the screen with the (first icon in the screen shot above) the van symbol will disappear
when the transport has finished.
91
SAP AG
How To ...
Choose transaction CG1B "Edit phrase sets" and create manually phrase sets for all
characteristics which are described in the file "Changes....pdf" as "new, CHAR 30, multiple phrases" or new, CHAR 30, single phrase. Enter the characteristic key as the new
phrase set key. Add appropriate phrases to the new phrase sets. Exceptions are characteristics such as "Accuracy" or "GLP". For these characteristics, phrase sets already
exist (SAP_EHS_XXXX_XXX_PREC, SAP_EHS_XXXX_XXX_GLP) and can directly be
assigned.
Customers of SAP EHS Regulatory Content - multilanguage phrase library for hazard
communication receive the allocation of phrases to phrase sets of new characteristics
with the corresponding update.
Choose transaction CGAB "Edit phrase set-attribute assignment". Assign all new phrase
sets to the appropriate characteristics.
Run transaction CGCZ "Match up master data" with flag "Activate Phrasing of Characteristics." only. This function assigns the function module
C14K_PHRASECHARACT_CHECK to all phrase-related characteristics. This enables
the system to call an assigned phrase set in the specification data base.
92
SAP AG
How To ...
2. During an initial setup: Customizing activity "Generate Standard Phrase Sets"
Ensure that no one is working with the affected property tree or is using the affected the
properties and characteristics in the EHS specification workbench.
If an EHS system is set up initially the customizing activity "Generate Standard Phrase
Sets" is used in general to create and allocate phrase sets to all characteristics of type
CHAR 30.
Navigate to the activity "Generate Standard Phrase Sets" in the SAP customizing (IMDG)
(path within EHS 3.2 and higher releases: Environment, Health & Safety -> Basic Data and
Tools -> Specification Management -> Specification Data Base Structure -> Settings for
Value Assignment). A complete overview about this activity is given in the corresponding
IMDG activity documentation.
Start the activity.
Phrase sets are generated and allocated to all characteristics of type CHAR 30. Phrases
are not allocated to the new phrase sets. Assignments of phrase sets to characteristics
that already exist are not overwritten by the system.
Some characteristics defined as CHAR 30 are not meant to be assigned to phrase sets,
for example "Value in Non-Standard Unit". These characteristics shall be used to store a
numerical value and a unit but were unfortunately defined as a free text fields of CHAR
30. In this case, the assigned phrase set has to be deleted in the table "Edit phrase
set-attribute assignment" (transaction CGAB) after the standard phrase sets have been
created.
Run transaction CGCZ "Match up master data" with flag "Activate Phrasing of Characteristics" only. This function assigns the function module
C14K_PHRASECHARACT_CHECK to all phrase-related characteristics. This enables the system to call an assigned phrase set in the specification data base.
If the phrase set was deleted in the table "Edit phrase set-attribute assignment" (transaction CGAB) before carrying out this transaction, then the function module
C14K_PHRASECHARACT_CHECK is deleted in the corresponding CHAR 30-characteristic and this characteristic can be filled as a free text field.
SAP AG
How To ...
Additional information:
In a standard R/3 System symbols are generated with descriptions in the logon language. The
flag "Regenerate Symbol Descriptions" within transaction CGCZ can be used to generate the
symbol descriptions in another language different from the logon language.
If the transaction CGCZ is run with the flag "Match Up Symbols-Phrase-Enabled Characteristics" the symbol definitions for the characteristic symbols that have been changed from phraserelated to non-phrase-related (or vice versa) will be updated..
94
SAP AG
How To ...
1.3. Choose the entry "Create Entries for the Value Assignments". The window "Filling
Customizing Table for Table-based Value Assignment" appears:
95
SAP AG
How To ...
1.4. Enter a property key of a new property or a series of property keys in the field "Value
assgmt type" and start the process (pushbutton "Execute").
A general example for a property key is SAP_EHS_1023_043 (for property "GHS Classification"). Select the property keys of the new properties within a specific property tree
package from the file "Changes_.....pdf". The file name for a specific property tree package can be found in the Appendix.
Please avoid to execute this process with the same property key multiple times because
this would create multiple entries in the customizing table!
1.5. Return to the previous window (push button "Back"):
96
SAP AG
How To ...
1.6. Choose the entry "Set Up Table-Based Value Assignment". The complete customizing table opens. Check all entries for the configured property/properties:
1.7. Return to the previous window (push button "Back"):
1.8. Repeat the steps 1.2 to 1.7 to create the necessary entries for all new properties.
2. Set up Table-based Value Assignment for existing properties with new characteristics
For EHS 3.2 and higher releases you have to change the configuration of existing properties where new characteristics were added and which were already configured for the Table-Based Value Assignment. The recommended procedure is to delete all entries for existing properties with new characteristics in the customizing table and to create the entries
for these properties again (see the following steps 2.1 to 2.14).
If the configuration of the Table-Based Value Assignment for properties with new characteristics was already changed, then these changes should be documented before deleting the
entries. In this case, an alternative could be not to delete all entries for a changed property
but to update the Table-Based Value Assignment for the existing property only (follow steps
1.1 to 1.8). Then, the new characteristics would be appended to the already existing entries
for this property. The correct order of the characteristics would have to be set up manually.
Please note, that the Table-based Value Assignment customizing table can only be changed
in SAP systems where the direct customizing is enabled. If the direct customizing is disabled
(for example in a production system), then the Table-based Value Assignment should be set
up in a system where the direct customizing is enabled (for example a development system).
The correct entries can be then transported to the system with the disabled customizing
(customizing transport).
2.1. Navigate to the activity "Set Up Table-Based Value Assignment" in the SAP customizing (IMG) (path within EHS 3.2 and higher releases: Environment, Health & Safety ->
Basic Data and Tools -> Specification Management -> Specification Data Base Structure
-> Settings for Value Assignment -> Set Up Table-Based Value Assignment). A complete
overview about this activity is given in the corresponding IMG activity documentation.
2.2. Start the activity. The following screen appears:
97
SAP AG
How To ...
2.3. Choose the entry "Set Up Table-Based Value Assignment". The complete customizing table opens.
2.4. Choose the push button "Position", enter a property key of an existing property with
new characteristics and navigate to this property. Select the property key from the file
"Changes_.....pdf". The specific file name for a certain property tree package can be found
in the Appendix.
2.5. Select all entries for this property.
2.6. Delete the selected entries (push button "Delete").
2.7. Return to the previous window:
2.8. Choose the entry "Create Entries for the Value Assignments". The window "Filling
Customizing Table for Table-based Value Assignment" appears:
98
SAP AG
How To ...
2.9. Enter the property key of the property, which entries you deleted in the previous step,
in the field "Value assgmt type":
2.10. Start the process (pushbutton "Execute").
2.11. Return to the previous window:
2.12. Choose the entry "Set Up Table-Based Value Assignment" again. The customizing
table opens. Check all entries for the configured property:
2.13. Return to the previous window (push button "Back"):
2.14. Repeat the steps 2.2 to 2.13 to create the necessary entries for all existing properties
with new characteristics.
SAP AG
How To ...
Choose Data Transfer - > Phrases (Transaction CG31) ; please see screen shot below.
"File with path" - Enter the path and file name (same as target file section upload files )
"Character standard" - Choose MS-NT for all files that have no _unicode.dat ending in their
filename; this applies also to unicode systems!
For files with unicode only languages ( with _unicode.dat ending in their filename) choose
UTF-8 as character standard.
You can leave all other options blank
Optional: You can limit the import to certain languages if you want (Button "Language selection" )
Check the file (F5)
Carefully check the displayed information before importing the phrases. Make sure you import to the passive CED or TDCLE library, the versions are correct and no errors are displayed.
If necessary approve the message "Date of phr. lib. to be imported is identical to date of
current library", this is just for your information.
However if the file you want to import is older than the library in your system, you can not
import it. Please make sure you have chosen the correct import file. In section upload files
you can also find information on how to change the header data of your import files.
Choose "Transfer/start time" (F6)
Choose "Immediate" or specify a time
Save
Note
For the TDCLE phrase library you have the choice to import either a single unicode
file including all languages, except for American English and Canadian French, or
separate import files based on the language group.
Due to the size of the phrase library and technical limitations with the phrase import
functionality, the option of a single import file for all languages is currently not available for the CED library.
Phrase import files for CED and TDCLE libraries include all phrases of the library,
not only those that are new or updated. Please be aware that all manual changes
made in your CED or TDCLE phrases will be overwritten.
Caution
Please do not set the flag for full import as this will delete your
passive library!
100
SAP AG
How To ...
101
SAP AG
How To ...
102
SAP AG
How To ...
Note
It is not recommended to press the "Determine target phrase" - button as this may
select phrases as target phrases that are not appropriate or may not have e.g. all
language translations.
Note
The merging process normally does not perform well when processing several thousand phrases at one time. Therefore, we strongly recommend that only a part of the
phrase library is merged at one time (e.g. filtered by phrase groups or phrase keys).
103
SAP AG
How To ...
Sometimes none or only a few assignments are imported. If you encounter this error, the first
step would be to run this import several times until no more phrases are assigned to phrase
sets. If this does not help an easy work-around is to change the name of the phrase library in
the import file to the name of your active library. Upload and import this modified file. In section
upload files you can also find information on how to change the header data of your import files.
As the phrase set assignment files are based on the latest SAP EHS standard property tree
there will be warnings in the logfile of the import if your system is not updated with the latest
standard property tree. These warnings can usually be ignored. Customers with valid maintenance contracts for SAP EHS Regulatory Content - expert rules for substance and mixture
classification or - substance lists and reference data receive the latest tree as part of their
104
SAP AG
How To ...
regular maintenance. Should you need any additional info on this topic please feel free to
contact us.
105
SAP AG
How To ...
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.
106
SAP AG
How To ...
If not used, choose -> Edit -> Delete
Phrases deleted from the SAP system are stored in the backup phrase library unless an active
phrase that originated in a passive phrase library is deleted.
Note
For installation local administrator rights might be required. Registry settings will be
added under the following paths:
107
SAP AG
How To ...
Activities
1. In Customizing for Basic Data and Tools, call the IMG activity Manage User Exits.
2. Create a new user exit with user exit category SUB_SEDACA using
C1E5_SUB_EXPERT_EVALUATE as Function Module (copy the entry of a DEMO-rule set
as template for your new user exit).
Note
You can determine the address number of the data provider in Customizing for Basic
Data and Tools in the IMG activity Specify Authorization Groups. To do this, call the
input help for the Data prov. field in the IMG activity. You will find the value you require
in the Addr. no. field. The address number is not displayed in address management
in the Product Safety component.
If you enter the value C the SAP system resets the active indicator for the newest of the
data records and deletes all other existing ones. The number of data records to be deactivated can be derived from the parameter EXPERT_NUM_OF_DEACT_VALUATION.
The data records that were newly determined by the EHS Expert are also created. If the
EXPERT_RES_BY_SRSID_OWNID_FLG parameter is set, then only those data records
are deleted that were determined during previous runs of the EHS Expert. This helps
108
SAP AG
How To ...
you prevent data records being deleted inadvertently. The SAP system uses the data origin (parameter EXPERT_WRITE_SOURCE_ID) and the data provider (parameter
EXPERT_WRITE_OWNER) to recognize which data was determined previously by the EHS
Expert.
EXPERT_DESTINATION
Corresponds with the name of the RFC destination that is entered under Tools -> Administration -> Administration -> Network -> RFC Destinations (transaction SM59) (for example
EHS_EXPERT).
EXPERT_READ_RATING and EXPERT_READ_VALIDITY_AREA
Determine the rating and validity area for which the data is transferred from the SAP system
to the EHS Expert.
EXPERT_WRITE_RATING and EXPERT_WRITE_VALIDITY_AREA
Determine the rating and validity area with which the data determined is stored in the SAP
system. In the EHS Expert set of rules you can also specifically define a different rating and
validity area that are used when storing data in the system.
EXPERT_READ_USAGE_1...n and EXPERT_WRITE_USAGE_1...n
These parameters can be used in addition to the two previous parameter pairs. You can
specify any number of usages in the format VACLID/RVLID/EXCLFLG (rating/validity/exclude indicator). The parameter numbering has to start with 1 and has to be consecutive.
Examples
EXPERT_READ_USAGE_1:PUBLIC/REG_EU EXPERT_READ_USAGE_2:PUBLIC/DE/X
In this example, the system reads all data records that are valid in the EU but not in Germany.
EXPERT_WRITE_USAGE_1:PUBLIC/REG_EU
EXPERT_WRITE_USAGE_2:PUBLIC/US
In this example, the system writes all data records that are valid both for the EU and for
the USA.
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
109
SAP AG
How To ...
available again more quickly for other parallel calls. During development and testing it may
be useful to not set the indicator, so that error messages from the update function are logged
in the log files and so you have the option of displaying the runtime of the update function
on the console or in the event display.
EXPERT_NUM_OF_DEACT_VALUATION
Determines the number of data records that are not deleted for save mode C, but are set
to inactive.
EXPERT_PARAMETER_CHANGE_MODE
If you enter the value S (default), the SAP system displays the Determine Secondary Data dialog box in display mode when starting secondary data determination using the EHS
Expert.
If you enter the value E you can revise the environment parameters in the Determine Secondary Data dialog box when starting secondary data determination using the EHS Expert.
The environment parameters you specified in Customizing are displayed as default values.
If you enter the value H the SAP system does not display the Determine Secondary Data
dialog box when starting secondary data determination using the EHS Expert.
EXPERT_RES_BY_SRSID_OWNID_FLG
Set this indicator if in backup modes C or D only data is to be deleted by the EHS Expert
that was determined during previous runs of the EHS Expert.
Warning
If you do not set this indicator, data that has also been entered manually or imported
can be deleted in backup mode C or D by the EHS Expert during secondary data
determination.
EXPERT_WRITE_OWNER
Data provider that you must have created in the SAP component Product Safety under Tools
-> Addresses -> Edit Data Providers. The data provider must always be entered with 10
digits.
If you do not specify a data provider, the SAP system uses the authorization group for the
specification to determine the respective data provider (see IMG activity Specify Authorization Groups). If the SAP system does not find any data providers there, it creates the data
without a data provider.
EXPERT_HIDDEN_PROCESSING_MODE
You can choose between two operating modes.
ONLINE (default): The EHS Expert run starts immediately after you choose Execute.
BACKGROUND: The EHS Expert runs as a background job. The indicator for the parameter
EXPERT_ASK_FOR_STARTTIME must be set for the start time prompt.
EXPERT_ASK_FOR_STARTTIME
If you set this indicator, you will be prompted in a dialog box when the EHS Expert is to start
as a background job.
EXPERT_ADD_PARAM_1...n
110
SAP AG
How To ...
You can pass any number of parameters to the set of rules. This means you can make sets
of rules configurable. In the set of rules you must create a fact for this purpose that is mapped
to the external ID P:I_TAB_PARAM in fact mapping.
EXPERT_WRITE_RUN_DATE
With this parameter, the Expert will write the current date with each run of
the given Expert rule: Enter the value X here, and set the further parameters EXPERT_EXPLANATION_ESTCAT, EXPERT_EXPLANATION_RULE_PROP, and
EXPERT_EXPLANATION_DATE_PROP as described below.
You set up the explanation component (optional) of the EHS Expert using the following parameters:
EXPERT_EXPLANATION_DISPLAY
If you set this parameter to X and allow the set of rules to run in the foreground, the system
displays the explanation immediately after the set of rules run. For sets of rules that run in
the background, the system does not display the explanation automatically.
EXPERT_EXPLANATION_SAVE
Set this parameter to X if you want to save the explanation for the set of rules run in the
specification. If you set the parameter to X, you must also edit the following parameters:
EXPERT_EXPLANATION_ESTCAT
In this parameter you specify the value assignment type in which the explanation is to be
saved as a user-defined text. The standard version of the demo sets of rules contains the
entry SAP_EHS_0101_002. This value assignment type is not in a property tree because
the explanation is not displayed as a user-defined text but in the menu.
EXPERT_EXPLANATION_RULE_PROP
In this parameter you specify the characteristic in which the name of the set of rules is
saved to allow its assignment when displayed at a later stage. The characteristic must be in
the same value assignment type as the user-defined text for the explanation. The standard
version of the demo sets of rules contains the entry SAP_EHS_0101_002_RULESET.
Note
If you run a master data match up, the system automatically appends a phrase set
and a check module to the characteristic. You must remove this check module again.
EXPERT_EXPLANATION_DATE_PROP
In this parameter you specify the characteristic in which the current date is written with each
rule run. The characteristic must be in the same value assignment type as specified in the
parameter EXPERT_EXPLANATION_ESTCAT. The standard version of the demo sets of
rules contains the entry SAP_EHS_0101_002_RUN_DATE. The last run date is only written
when triggered separately with the parameter EXPERT_WRITE_RUN_DATE.
EXPERT_EXPLANATION_TEXTCAT
In this parameter you specify the user-defined text type with which the explanation is to be
saved in the specification. The standard version of the demo sets of rules contains the entry
EX.
EXPERT_ADD_PARAM_1
111
SAP AG
How To ...
In this parameter you specify the path and name of the index / header file of your SAP EHS
Regulatory Content database.
EXPERT_ADD_PARAM_2
In this parameter you can specify a user name to access your SAP EHS Regulatory Content
database if it is stored in a password protected storage location or web server.
EXPERT_ADD_PARAM_3
In this parameter you can specify a password to access your SAP EHS Regulatory Content
database if it is stored in a password protected storage location or web server.
EXPERT_TAB_FIELD_1
This parameter is the specification key from SAP EHS, it should not be changed.
EXPERT_TAB_FIELD_2
In this parameter you specify the identifier that OCC should use when looking for substance
data. This is usually either the CAS or the UN number.
EXPERT_TAB_FIELD_3
In this parameter you specify the identifier that OCC should use for display. Choose an
identifier that is available for all substances like synonym name.
EXPERT_TAB_FIELD_4
In this parameter you can specify a second identifier that OCC should use when looking for substance data. This is identifier is only used when the identifier specified in
EXPERT_TAB_FIELD_2 does not give a search result. The main purpose is for loading data
that is not assigned to CAS numbers.
Sample value
EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION
C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_EXPERT
EXPERT_EXPLANATION_DISPLAY
EXPERT_EXPLANATION_ESTCAT
SAP_EHS_0101_002
EXPERT_EXPLANATION_RULE_PROP
SAP_EHS_0101_002_RULESET
EXPERT_EXPLANATION_SAVE
EXPERT_EXPLANATION_TEXTCAT
EX
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE
EXPERT_READ_RATING
PUBLIC
EXPERT_READ_VALIDITY_AREA
REG_WORLD
EXPERT_RES_BY_SRSID_OWNID_FLG
EXPERT_RULE_SET
ZEXP_GHS
EXPERT_WRITE_OWNER
112
SAP AG
How To ...
EXPERT_WRITE_RATING
PUBLIC
EXPERT_WRITE_SOURCE_ID
ZEXP_GHS
EXPERT_WRITE_VALIDITY_AREA
REG_WORLD
Sample Value
EXPERT_ADD_PARAM_1
headerurl=<path
to
CLEO
PS
DB>\PS_DB
\header.xml
EXPERT_ADD_PARAM_2
usernameurl=x
EXPERT_ADD_PARAM_3
passwordurl=x
EXPERT_CALL_ONCE
EXPERT_COMMIT_FLG
EXPERT_COMMIT_FUNCTION
C1E5_SUB_EXPERT_DATA_CHANGE
EXPERT_COMMIT_MODE
EXPERT_DESTINATION
EHS_OCC
EXPERT_NUM_OF_DEACT_VALUATIONS 1
EXPERT_PARAMETER_CHANGE_MODE
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_WRITE_OWNER
EXPERT_WRITE_RATING
PUBLIC
EXPERT_WRITE_SOURCE_ID
TECHNIDATA
EXPERT_WRITE_VALIDITY_AREA
REG_WORLD
Tip
If you want to define your own function modules, display the documentation for the
corresponding reference function module (SE37). Write the new function module analogous to the reference function module and its interface.
113
SAP AG
How To ...
Activities
1. Call the IMG activity.
2. Check if the default settings are correct.
3. You can assign a specification category to a user exit so that this user exit is displayed
depending on the specification category (for example, for user exits on secondary data
determination).
The assignment is relevant only for user exits that relate to specifications.
SAP AG
How To ...
Start transaction "spro" and navigate to: Environment, Health and Safety -> Basic Data and
Tools -> Specification Management -> Specification Master -> Specify Regulatory Lists
115
SAP AG
How To ...
116
SAP AG
How To ...
117
SAP AG
How To ...
118
SAP AG
How To ...
Save your settings
Caution
Be aware, that the validity area "REG_WOLRLD" is "empty" and
has the default behaviour to recognize all countries.
Once you have used a validity area in a productive system, it can
no longer be deleted.
Newly created validity areas are not evaluated correctly by the
Expert before restarting the Expert Server.
119
SAP AG
How To ...
Go to the IMG customizing ("spro"):
Navigate to Environment, Health and Safety -> Basic Data and Tools -> Additional Information for Value Assignment -> Usage ->Specify Validity Areas.
Press F5 or "New Entry" and enter the Validity area category (e.g. REGION) and the new
area as well as the description. Mark the entry and switch to the navigation sidebar
Double clicking the "Assign Validity Area/Country" entry the list of countries belonging to
this area opens (- empty). There you can assign all countries that shall belong to this new
validity area.
120
SAP AG
How To ...
Note
If you are updating an existing database, the setup program will suggest a path for
the installation based on the storage path of the last installation from this computer.
Please carefully check this installation path to avoid mixing up e.g. productive and test
databases.
In your XML substance database folder, a text file called version.txt is stored which
will have information about the currently installed database. Please check the version
file before updating the database to avoid overwriting your database with the same or
older files.
Each installation of the substance lists and reference data XML substance database takes
approximately 1,5 GB for Product Safety and 1,1 GB for Dangerous Goods database.
After installation of the XML files, the structure of the database should look like:
Product Safety:
<path to XML substance database>\CLEO\
<path to XML substance database>\CLEO\1 subfolder with all CAS numbers starting with 1
<path to XML substance database>\CLEO\... subfolders for other CAS numbers starting
with 2 to 9
<path to XML substance database>\CLEO\G subfolder with all substance groups
<path to XML substance database>\CLEO\N subfolder with all non-substances data, e.g.
mixtures and data with no CAS number
121
SAP AG
How To ...
<path to XML substance database>\CLEO subfolder with all data for DG regulation
\ADN
ADN(R)
<path to XML substance database>\CLEO\... subfolders for other DG regulations
<path to XML substance database>\CLEO subfolder with all available UN numbers
\UN
Alternatively extract the files and burn a DVD if no network folder should be used (performance
loss!). The network path for database must be accessible for all users (read access). For
security reasons, access should be limited to persons allowed to load SAP EHS Regulatory
Content - substance lists and reference data. Please note the path to the database in the
installation protocol.
It is possible to have separate databases for Test, Development and Productive systems. This
allows testing of data updates without impact on the productive data load. If you want to do this,
copy the whole database including all subfolders to a different storage location. In addition,
changes to the mapping database and user exit are required to support multiple databases
(see also chapters How to configure the User Exit, How to configure EHS OCC and How to
setup Mapping Database).
Note
Please make sure that you have a fast network connection between your OCC frontend computer, SAP application server and the storage location of the XML substance
database. WAN connections are usually unsuitable for OCC as large amounts of data
have to be transferred. See also SAP note 1235663 for further hints to improve the
OCC performance.
122
SAP AG
How To ...
Only one database needs to be maintained/updated
All users have the same mapping settings
Disadvantages of a central database:
If network access is slow or bandwidth is limited, response time during data load might be
longer. Especially creating the cache will be much slower.
In rare cases conflicts in opening the database if several persons are loading substance lists
and reference data at the same time
Note
Please make sure that you have a fast network connection between your OCC frontend computer and the storage location of the mapping database. WAN connections
are usually unsuitable for OCC as large amounts of data have to be transferred. As the
mapping database is used to store cached data for improved performance, this file can
get quite big (over 100 MB). See also SAP note 1235663 for further hints to improve
the OCC performance.
If you are copying the mapping database from a CD/DVD to your local drive/network,
please remove the write protection of the file td_cleo.mdb after copying to your local
drive.
If the active phrase library is different than CUST, changes to the mapping database are required:
1. Open td_cleo.mdb / td_cleo_dg.mdb in MS Access
2. Open table ExpPhraseMap
3. Choose column External_id and replace CUST:
Search for: CUSTReplace with:????- (name of active phrase library)
Search in: External_id
Compare: Beginning of field
Replace all
Note
If several installations were done for the database (test/dev/prod), we recommend a
separate mapping database for each of the installations.
The OCC mapping database follows the same structure as SAP EHS Expert mapping databases. There are separate mapping tables for properties, phrases and other values:
123
SAP AG
How To ...
You can find the path of your mapping database in the ExpertAdmin tool installed on your front
end computer. On the instances tab there should be entries for e.g. CLEO_PS or CLEO_DG
which specify the path to the current mapping database. Please see Section A.23, How to
configure EHS OCC for details.
Repeat the above steps for all installations of the SAP EHS Regulatory content - substance
lists and reference data mapping database if you are using more than one mapping database
or if each user has a local copy of the mapping database.
Note
We recommend to create a backup copy of your existing mapping database before
overwriting it with the new version of the mapping database.
In all tables, Internal_id means the key/value in the database and External_id the corresponding key/value in SAP EHS.
Note
Please note that everything described in this chapter is only valid for SAP EHS Open
Content Connector (OCC) Service Pack 21 (November 2009) or higher. Please update
OCC to this version or contact us for the settings in older OCC versions.
Note
If multiple installations of the database exist for test, development and productive systems, the below steps must be repeated for all of them. Assign the name of the instances as specified in the user exit parameter EXPERT_RULE_SET and assign the
appropriate mapping database.
Product Safety
A new instance entry has to be configured for Product Safety data:
124
SAP AG
How To ...
Execute OCC: ->Start -> Programs -> EHS -> Open Content Connector
Choose: Options -> Instance Configuration ...
Choose Add
Name: CLEO_PS
System: EHSOCC
Mapping: Path to your mapping database TD_CLEO.mdb which was part of the installation
in step "How to setup Mapping Database"
Execute OCC: ->Start -> Programs -> EHS -> Open Content Connector
Choose: Options -> Preferences ...
Switch to the Systems tab
Choose Add
Name: EHSOCCDG
Options: All settings should have been automatically copied when the EHSOCCDG key was
created. No changes necessary.
Choose Apply
125
SAP AG
How To ...
126
SAP AG
How To ...
Meaning
Internal_Id
Record
Optional assignment of the fact to a record in the set of rules / OCC XML file
Group
External_Id
Descriptions
Options
IsPhrase
Identifies whether the fact contains values that are to be subject to value
conversion via phrase mapping tables. This will mostly be used for facts
that represent characteristics with phrases assigned in order to convert
an easily recognizable phrase identification used in the set of rules / OCC
XML file to the phrase key in EHS and vice versa.
127
SAP AG
How To ...
The first three fields together form a unique identifier for the fact in the set of rules.
Meaning
Internal_Id
Group
External_Id
Descriptions
Options
The first two fields together identify the record uniquely in the set of rules.
Note
Phrase mapping allows an assignment to be made between an internal and an external
value for any fact value. The phrase does not have to be an EHS phrase. The corresponding conversion takes place if the IsPhrase indicator is set in fact mapping.
Expert generates a warning message if the rule set or OCC reads phrases which are
not contained in the Mapping table.
Table Fields in the Phrase Mapping Table (ExpPhraseMap)
Table Field
Meaning
Internal_Id
Phrase code in the set of rules. The rule editor uses a special syntax for
phrase codes to distinguish them from normal texts. For this purpose the
phrase codes are enclosed in square brackets and number signs, for example [#R20#] .
External_Id
Phrasetext
Phrase text
Options
128
SAP AG
How To ...
Tip
We recommend to insert these phrases using the following pattern:
Internal_Id: <Catalog name>-<Phrase key> , e.g. CUST-N09.00101280
External_Id: <Catalog name>-<Phrase key> , e.g. CUST-N09.00101280
To consider these enhancements for updates of the standard mapping you should label
these manual settings in the database e.g. in the Version column.
129
SAP AG
How To ...
Note
With the SAP EHS Regulatory Content 2009-1 update we have provided enhanced
functionality for the list substance search which performs much faster than older version
of the program. Please check the technical details of this update and make sure that
the new version of the program is installed to avoid long run times or time-out issues.
1. Choose Extended Search: List Substance with new content ...
130
SAP AG
How To ...
2. Specify the path to the file cleo_update_2010-1.txt which can be found in folder 6-UpdateTools.
3. Combine with any other search option, e.g. SUBID or identifiers and execute the search.
4. A hit list of all list substances will be created that potentially have new or updated regulatory
data available.
131
SAP AG
How To ...
5. We recommend saving the created hit list so you have it available in the future without rerunning the query.
Note
Starting with update 2010-1, we also provide a file cleo_new_group_assignments.txt.
This file can be used in the same way as described above, however it generates a list
of substances with new group assignments compared to the last release.
Note
For performance reasons, we are only checking the changes on a per substance level
not on single data sets. As a result you may have substances on your hit list for which
you do not get any new or changed data when you try to load them. This is the case if
You have not licensed all regional packages for SAP EHS Regulatory Content - substance lists and reference data and the changes are in an area you have not licensed.
You have switched off certain lists/regions in your filter settings; changed data therefore will not be displayed.
You have decided not to load certain data and/or groups in the past for this substance, if the change is in one of these data sets, it will not be displayed.
132
SAP AG
How To ...
5. Set data options "Load Changes Only" and optionally "Use Substance Groups"
2.
3.
4.
5.
6.
-> File -> New -> New from template -> General Templates -> cleo_simulation.xlt
When prompted, enable macros
Open the spreadsheet with the new and revised list substance data you created during the
data load simulation if it is no longer open
Click the button Import OCC Data. The tool will check for any open OCC simulation file
and ask for your confirmation to import the data. If no spreadsheet with OCC data is found,
please either copy the data manually or open the correct file (starting with occSimu_*.csv)
Click the button Start Analysis to analyze the imported OCC data.
Save the new spreadsheet
The Simulation spreadsheet offers some functionality for a first analysis of new and changed
data:
Two lines per dataset, the first one (white background) is the new SAP EHS Regulatory
Content data. The second line (grey background) is existing data in SAP EH&S
133
SAP AG
How To ...
Pairs of related data are assigned a unique record number in column A, e.g. 1_CLEO and
1_EHS
In column "Mode" each record is marked as either new, changed or inactivated
Filter options for all fields, e.g. by property or regulatory list
New records are highlighted bold red (complete line)
In changed records, only important changes are highlighted bold red
Inactivated records are highlighted in italics (complete line)
In the top right corner a summary is given (number of substances and records)
Explanation of some fields:
Column A: Unique record number for pairs of related data, e.g. 1_CLEO and 1_EHS
Column B: Substance ID of SAP EH&S (SubID)
Column C: Group ID of SAP CLEO => Data is from a generic group, not for the substance
itself
Column E: Mode - "New" , "Change" or "Inactivated"
Column F: Property - this is the property or identifier with the new/changed data
Column H: CAS number or identifier type
Column I: Name of the substance
134
SAP AG
How To ...
If the data analysis in the previous chapters has not shown any critical changes and a lot of
substances have new data available, the autoload functionality should be used.
Note
If a new group was assigned to a substance, the group information will not be loaded
using the autoload functionality combined with the "load changes only" option. This
is the intended behaviour to avoid unintentional group assignments which were not
reviewed by your regulatory experts.
135
SAP AG
How To ...
If new or changed data becomes available within an existing group, your choices in the
past decide if the data will be loaded:
If a group was loaded in the past, all new and changed data will be loaded as well.
If a group was set to "no load" in the past, new and changed data will be ignored
and not loaded.
136
SAP AG
How To ...
Table Customer UN Numbers allows you to maintain a list of UN numbers you are using
Query Impact Analysis gives you an overview which of the UN numbers currently in use are
affected by the changes if the table Customer UN Numbers is maintained
137
SAP AG
How To ...
10.Save data to EH&S
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.
138
SAP AG
How To ...
Specify the value assignment type the profile shall be used with (standard is
SAP_EHS_1022_042 provided with the EHS standard property tree)
(optional)
Select
the
function
module
used
for
output
conditions
(DG50_PRICOND_USRDEFTXT is delivered with the standard)
Save your settings
Then press F5 or "New Entry" and enter the new ratings as well as the description and save
your entries.
139
SAP AG
How To ...
You can copy the files by using EHS Service Administration or by connecting to the Expert
Server PC directly.
Direct copy
Connect to the Expert Server PC and copy all files in the RULES subdirectory of the Expert
installation.
SAP AG
How To ...
All Expert rule sets have to be registered on the Expert Server PC. You can do this in the SAP
system using EHS Service Administration or directly on the Expert Server PC with the help of
the Expert Admin Tool. Some rule sets uses additional settings, e.g. IgnoreWarnings. These
additional settings could not be set using EHS Service Administration.
141
SAP AG
How To ...
External_id
ext_target_organ T:Target_Organ/OSHA_Hazard_Determination_externvalues.mdb
142
SAP AG
How To ...
Example: Record-Mapping Full declaration of the path for the external data
Internal_id
External_id
External_id
i_switch_harmful T:harmful_check;Switches/
OSHA_Hazard_Determination_externvalues.mdb
Example: Fact-Mapping Full declaration of the path for the external data
Internal_id
External_id
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
Descriptions
Options
CHANGES_in_mapping_table_____ExpFactMap
CHANGES_in_mapping_table_____ExpPhraseMap
CHANGES_in_mapping_table_____ExpRecordMap
CHANGES_in_mapping_table_____ExpGroupMap
Changes which have been made concerning the externvalues database are also documented
here, e.g.
143
SAP AG
How To ...
Changes_in_external_table____GHS_table
Table_Changes_in_external_table_not_P_Statements
There are three different cases of mapping changes: new entries, changed entries, and deleted
entries.
Every changed, new, or deleted entry is added to the HISTORY.mdb as a new line.
If there is a change, it is additionally checked if the given entry already exists in the
HISTORY.mdb (i.e. if it has already been changed in a former version); if this is the case, the
matching entry is updated and the old version information is preserved as described below.
The additional columns Version and Remark are maintained as follows:
Version:
the version number without a preceding "V", e.g. "1.5"
if a line is updated, the old Version entry is replaced by the new one
144
SAP AG
How To ...
145
SAP AG
How To ...
The option "Usage check" is utilized to control the way in which the usages are compared.
There are four options to select: 0, 1, 2 and 3.
If you do not specify a value, the SAP System uses the value 0 as default.
Value 0: The usage is appropriate if - with the same rating used - the generation variant validity
area that is expanded to its countries and regions is the same as or is a subset of the expanded
validity area of the usage with which it is to be compared.
Example: Generation variant: DE Value assignment usage: REG_EU If a safety data sheet is
created for Germany, value assignment instances are also taken into account that are valid
for the validity area REG_EU.
Please see the SAP Help function for all the details on the option.
Under "Rating/Validity", additional validity/language combinations can be maintained:
These validity areas or languages must be addressed directly by the WWI coding in the
template (G-Repeating-Group) to be effective. By the use of these Rating/Validity options, it
is for example possible to give out special phrases in English on a template in Chinese or
Spanish.
146
SAP AG