SAP EHS Regulatory Content

Concept for GHS rules

INTERNAL: SAP CUSTOMER

TABLE OF CONTENTS
1 CONCEPT FOR COMPANIES OPERATING GLOBALLY .............................................................. 2
2 LOAD LIST DATA FOR GHS ........................................................................................................... 2
1.1 Maintain primary data ...................................................................................................................... 2
1.2 Use national and regional GHS rule sets for Pure_Sub .............................................................. 2
1.3 Use GHS rule sets for classifying/labeling Real_Subs ................................................................ 2
1.4 Summary of Actions ........................................................................................................................ 3
2 SIMPLIFIED CONCEPT FOR COMPANIES USING ONLY EUROPEAN DATA (NOT
RECOMMENDED) ............................................................................................................................................. 4
2.1 Used GHS properties for this concept .......................................................................................... 4
2.2 Load list data for GHS ..................................................................................................................... 4
2.3 Maintain primary data ...................................................................................................................... 4
2.4 Use GHS rule sets for classifying and labelling of Pure_Subs (Ingredients) ............................ 4
2.5 Using GHS rule sets for classifying and labelling of Real_Subs................................................ 4
ANNEX - OVERVIEW GHS PROPERTIES ...................................................................................................... 5
SAP EHS REGULATORY CONTENT – CONCEPT FOR GHS RULE SETS

1 CONCEPT FOR COMPANIES OPERATING GLOBALLY

This is the recommended concept. It takes into consideration that a company wants to harmonize the GHS
classifications globally as far as possible, but wants to fulfill local GHS regulations at the same time.

2 LOAD LIST DATA FOR GHS

The regulatory data are loaded in the List specific GHS properties. The following GHS properties are
available for loading ERC Regulatory data:
1) GHS Classification (List Data) (SAP_EHS_1023_043)
2) GHS Labeling (List Data) (SAP_EHS_1023_044)
3) M-Factor (SAP_EHS_1023_075)
4) Specific concentration limits (GHS) (SAP_EHS_1023_074)

1.1 Maintain primary data

Maintain physical chemical data, toxicological and eco-toxicological data that is relevant for the classification
procedure. See functional description for details on rule input data.

1.2 Use national and regional GHS rule sets for Pure_Sub

The regional/national rule sets, e.g. GHS_EU, GHS_KR, GHS_JP, GHS_NZ, etc and GHS UN need to be
run on the Pure_Sub level. The general GHS classification can be used as classification for a country and as
a basis for a UN based Safety Data Sheet i.e. used by countries not having specific requirements and which
follows the purple book.
These rule sets copy GHS regulatory list data (depending on the GHS Regulatory list entry in the mapping
table) to the region specific, consolidated GHS properties. E.g. if GHS regulatory list data is available for
Europe this data will be copied to the GHS properties for Europe.
If no list data is available the GHS classification is derived from a combination of physical chemical data (e.g.
Flash point), test data (e.g. Acute toxicity data) and the maintenance of specific phrases. In some GHS rule
set there is specific logic concerning the evaluation of list data. Please see the functional description for
further details.
As another option, which is not the standard setting it is possible to fill the general GHS classification and
use this classification as second priority. This might be an option if no test data of the components is
available. In this case the GHS classification can be assessed and maintained manually. The general GHS
classification can then be transferred to the respective country specific GHS properties as second priority
before checking the test data. If the hazard class or categories, which are maintained in the general
classification are not applicable for the respective country or region, this classification will be reduced
accordingly.
The user can decide by rules set settings (switches), whether the listed data and/or the general data are
used to fill the region specific/consolidated properties. For details on optional settings see functional
descriptions of the GHS rule sets. Recommended is to use list data and test data as second priority.

1.3 Use GHS rule sets for classifying/labeling Real_Subs

After the GHS classification has been maintained or generated for the Pure_Sub level (components), the
GHS rules can be executed on the Real_Sub level. The GHS rule sets read product test data in addition to
the compositions´ (Pure Subs) GHS classification and Labelling data.

In the country specific versions of the GHS rule sets (e.g. GHS_KR, GHS_NZ for the Asia pacific region and
GHS_EU (CLPEU) for Europe) ingredient classification and labelling data from the respective region/country
specific GHS properties is considered. The result of the rule sets is also written back to the region/country
specific GHS properties on the Real_Sub level.

INTERNAL: SAP CUSTOMER 2

SAP EHS REGULATORY CONTENT – CONCEPT FOR GHS RULE SETS

The general GHS rule, which classifies and labels substances and mixtures according to the “Purple Book”,
reads component data from the general GHS properties and writes the result back to these general GHS
properties at the real sub level.

1.4 Summary of Actions

1) Load GHS List data in List_Subs and generate reference or inheritance relationships to the appropriate
Pure_Subs
2) Run general GHS and country or region specific GHS rules for the Pure_Subs
3) Run general GHS and country or region specific GHS for the Real_Subs

INTERNAL: SAP CUSTOMER 3

SAP EHS REGULATORY CONTENT – CONCEPT FOR GHS RULE SETS

2 SIMPLIFIED CONCEPT FOR COMPANIES USING ONLY EUROPEAN DATA (NOT

RECOMMENDED)

In case that a company only is interested in having CLP data (e.g. because of only having European
business relations), a simplified approach can be chosen, which does not consider the region specific
properties “GHS Classification (EMEA)” and “GHS Labeling (EMEA)”
For implementation of this approach changes in rule set mapping and templates are required, as the
standard configuration does not support this approach. It might also be necessary to map additional rule set
reading the CLP data.

2.1 Used GHS properties for this concept

With this concept only one set of properties is used. The following properties would be used:
1) GHS Classification (List Data) (SAP_EHS_1023_043)
2) GHS Labeling (List Data) (SAP_EHS_1023_044)
3) M-Factor
4) Specific concentration limits (GHS)
5) Labeling of special preparations (GHS) )

2.2 Load list data for GHS

The regulatory data would be loaded into the List specific GHS properties:
1) GHS Classification (List Data) (SAP_EHS_1023_043)
2) GHS Labeling (List Data) (SAP_EHS_1023_044)
3) M-Factor (SAP_EHS_1023_075)
4) Specific concentration limits (GHS) (SAP_EHS_1023_074)

2.3 Maintain primary data

Maintain physical chemical data, toxicological and ecotoxicological data that is relevant for the classification
procedure. See functional description for details on rule input data.

2.4 Use GHS rule sets for classifying and labelling of Pure_Subs (Ingredients)

Inheritance or reference relationships can be used for some Pure_Subs in order to copy EU GHS list data to
this level. Where list data is not available the rule sets GHS_EU (CLPEU) or EU-to-GHS can be used. They
have to be configured to write data in the list specific GHS properties by adapting the rule set mapping.
Additional management processes would be required as the rules do not recognise whether GHS list data
already exists and this could be overwritten by the rule sets.

2.5 Using GHS rule sets for classifying and labelling of Real_Subs

The user would use the GHS_EU (CLPEU rule) to determine the GHS classification and labelling for the
mixture. The rule set mapping would need to be adapted to read from the list properties.
If a new user would like to use the „simple“ solution he would need to change the standard WWI template for
Europe.

INTERNAL: SAP CUSTOMER 4

SAP EHS REGULATORY CONTENT – CONCEPT FOR GHS RULE SETS

ANNEX - OVERVIEW GHS PROPERTIES

There are three categories of GHS properties, those containing:

1) List information:
a. GHS Classification (List Data) (SAP_EHS_1023_043)
b. GHS Labeling (List Data) (SAP_EHS_1023_044)
These properties should only be used to store GHS data which is published on a Regulatory list, e.g. on
Annex VI, Table 3.1 of the EU CLP regulation (Regulation (EC) No 1272/2008). This data can be delivered
by a content provider or manually maintained by the EHS user. These properties are valid for regulatory list
data from all regions.

2) General information:
a. GHS Classification (General) (SAP_EHS_1023_088)
b. GHS Labeling (General) (SAP_EHS_1023_093)
These properties should be used to store GHS data which represent the UN GHS classification. These
properties are not to be used for GHS regulatory list data or region specific data.

Examples of general classifications include:

• A GHS classification which has been undertaken using the criteria according to the UN Purple Book
determined by the GHS UN rule.
• A self-determined GHS classification using toxicological or physical-chemical data
Only one valid general classification has to be maintained for each substance.
These properties shall not be used for GHS regulatory list data or region specific data

3) Consolidated regional information:

a. GHS Classification (EMEA) (SAP_EHS_1023_089)

b. GHS Labeling (EMEA) (SAP_EHS_1023_094)
c. GHS Classification (A/P) (SAP_EHS_1023_091)
d. GHS Labeling (A/P) (SAP_EHS_1023_096)
e. GHS Classification (NA) (SAP_EHS_1023_090)
f. GHS Labeling (NA) (SAP_EHS_1023_095)
g. GHS Classification (LA) (SAP_EHS_1023_092)
h. GHS Labeling (LA) (SAP_EHS_1023_097)

These properties should be used to store GHS data which represent a GHS classification for a specific
country or region e.g. Europe.

4) Other GHS related information

Additionally there are properties which are not split by use or country specific and exist only one time.
Different country variants can be maintained with their respective validity area. These properties are:
1) M-Factor (SAP_EHS_1023_075)
2) Specific concentration limits (GHS) (SAP_EHS_1023_076)
3) Labeling of special preparations (GHS) (SAP_EHS_1023_074)

INTERNAL: SAP CUSTOMER 5

www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
information and notices.