SUS300

SUS300
Product Safety and Stewardship

Overview
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 10
Course Duration: 5 Day(s)
e-book Duration: 20 Hours 15 Minutes
Material Number: 50106944
SAP Copyrights and Trademarks
© 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.
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. Please see http://global12.sap.com/
corporate-en/legal/copyright/index.epx for additional trademark information and notices.
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 SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP SE 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, which
speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Typographic Conventions
American English is the standard used in this handbook.

The following typographic conventions are also used.
This information is displayed in the instructor’s presentation
Demonstration
Procedure
Warning or Caution
Hint
Related or Additional Information
Facilitated Discussion
User interface control Example text
Window title Example text
© Copyright. All rights reserved. iii

© Copyright. All rights reserved. iv
Contents
vii Course Overview
1 Unit 1: EHS Tools and the Integration with SAP ERP
2 Lesson: EHS Basics: Tools and Integration with SAP ERP

10 Lesson: Working with Specifications
18 Lesson: Maintaining Properties
40 Lesson: Managing and Assigning Phrases
56 Unit 2: Basic Configuration
57 Lesson: Configuring and Customizing Sustainability Products
71 Unit 3: EHSM Data Structure
72 Lesson: Defining a Property Tree

83 Lesson: Managing Phrases
90 Unit 4: Data Migration
91 Lesson: Defining and Setting up the Data Model

97 Lesson: Transferring Data Between Test and Production System
102 Lesson: Migrating of Substance Data
110 Lesson: Migrating of Phrases and Reports
120 Unit 5: Windows Word Processor Integration and Expert Server Set Up
121 Lesson: Installing Expert Server

126 Lesson: Installing Windows Word Processor Integration
141 Lesson: Configuring Windows Word Processor Integration
168 Unit 6: Dangerous Goods
169 Lesson: Setting up Document Printing

177 Lesson: Setting Up Dangerous Goods Checks
185 Unit 7: Global Label Management
186 Lesson: Determining User Requirements

194 Lesson: Setting Up Standard Customizing and Configuration
203 Lesson: Setting up Data in the System
209 Lesson: Testing of Global Label Management
220 Unit 8: SAP Product and REACH Compliance
221 Lesson: Setting Up and Customizing
© Copyright. All rights reserved. v

231 Unit 9: Substance Volume Tracking
232 Lesson: Basic understanding in Substance Volume Tracking

237 Lesson: Understanding the Procurement Scenario
242 Lesson: Understanding the Production Scenario
© Copyright. All rights reserved. vi

Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
© Copyright. All rights reserved. vii

© Copyright. All rights reserved. viii
UNIT 1 EHS Tools and the
Integration with SAP
ERP
Lesson 1
EHS Basics: Tools and Integration with SAP ERP 2
Lesson 2
Working with Specifications 10
Lesson 3
Maintaining Properties 18
Lesson 4
Managing and Assigning Phrases 40
UNIT OBJECTIVES
Examine the structure of SAP EHS Management
Use the EHS Workbench
Search and create specifications
Create properties manually
Manage phrases
© Copyright. All rights reserved. 1

Unit 1
Lesson 1
EHS Basics: Tools and Integration with SAP
ERP
LESSON OVERVIEW
This lesson explains the scope of the SAP EHS (Environment, Health, and Safety) tools and
the SAP EHS integration into the SAP ERP system.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Regulatory Requirement of Managing EHS Data
Figure 1: SAP Services: Sustainability Services Portfolio
SAP EHS helps companies to evaluate if they are effective in their sustainability initiatives.
With SAP EHS, companies can optimize current SAP solutions to drive and support
sustainability.

Lesson: EHS Basics: Tools and Integration with SAP ERP
Regulatory Requirements of Managing EHS Data
Figure 2: Regulatory Requirements of Managing EHS Data
EHS Management covers global, regional, and local regulatory requirements to manage EHS
data.
Sustainability Tools - EHS Management
Figure 3: Sustainability Tools - SAP EHS Management

Unit 1: EHS Tools and the Integration with SAP ERP
Health and Safety Pillar
Figure 4: Health and Safety Pillar
Health and Safety supports the establishment of preventive health and safety management. It
ensures the well-being of employees and gains higher productivity with fewer incidents and
absences.
Product Safety and Stewardship Pillar
Figure 5: Product Safety and Stewardship Pillar
Product Safety and Stewardship allows the development, production, and sale of products
which are safe, healthy, and have minimal environmental impact.

Environmental Performance Pillar
Figure 6: Environmental Performance Pillar
Environmental Performance supports the minimization of the environmental impact of

operations, plants, and the supply chain to retain an operating license and reduce resource
use.
Technical Integration of EHS Management (EHSM) in SAP ERP
Required SAP components

You must have installed the following SAP components to be able to use all the functions of
Basic Data and Tools :
Engineering Change Management (LO-ECH)
Document Management (CA-DMS)
Classification System (CA-CL)
Material Master (LO-MD-MM)
Sales and Distribution (SD)

Purpose of the Specification Database
Figure 7: Purpose of the Specification Database
In the specification database, companies maintain all their relevant EHS data. The database
supports the creation of reports, also different types of reports based on the same data
source.
One Database for all Types of Specifications
Figure 8: One Database for all Types of Specifications
The specification database contains data for all types of specifications:

Health and safety
Product safety and stewardship
Product and REACH compliance
Environmental performance
One Database for all Types of Specification Categories and Types
Figure 9: One Database for all Types of Specification Categories and Types
The specification database contains all types of specification categories and specification
types, sample:
Specification category Specification types
Substance Pure substance, listed substance, ...

Agent Noise, Psychological factor, ...

Reporting Concept for EHS Data
Figure 10: Reporting Concept for EHS Data
The reporting concept for EHS data follows a two-step approach:
1. Maintain the specification data by using properties.
2. Create reports.
The EHS Workbenches
Figure 11: The EHS Workbenches

The EHS Workbenches are designed to support the maintenance of specification categories.
Entry Screen: Personalization - Overview
User settings for the navigation area and detailed structure:
Remember column settings
Remember structure layouts
Remember window arrangement
Remember sort column
Mode: Edit or Display
Default search screen
Columns
Favorites
Default properties
Personalization is requested when using the workbench for the first time. You can change it
later using the Personalization button in the toolbar.
LESSON SUMMARY
You should now be able to:

Unit 1
Lesson 2
Working with Specifications
LESSON OVERVIEW
This lesson explains how you can structure data by working with specifications.
LESSON OBJECTIVES
Header Data of Specifications
Figure 12: Specification – Structure – Header Data
The specification header contains identifiers. An identifier is an element that identifies a

specification. The identifier is defined in detail using the identification category and
identification type.

Lesson: Working with Specifications
Technical Header Data
Figure 13: Tab Page Specification Header
In the specification header, make the required entries, whereas you also find entries
generated by the system.
Identifiers and their Purpose
Figure 14: Identifiers
From a technical point of view, it is not necessary to enter an identifier. Recommendation is to

enter at least one identifier (for example to use it as search criteria).

Search Types for Specifications
Figure 15: Workbench: Searching for a Specification
Search for a specification process:
1. Start the workbench.
2. Open the search screen.
3. Fill in the search criteria.
4. Examine the result, a hit list.
Structure of the Search in the Workbench
Figure 16: Structure of the Specification Search Screen

The design of the workbench supports you in your search. You can use search criteria in the
header data and in the validity. You can also restrict the search criteria. Extended search
functions which depend on the specification category are available too.
Workbench: Specification Header – Search Criteria
Figure 17: Workbench: Specification Header – Search Criteria
The SAP system uses data origin to create a record of the system from which the data
originates for all specification data records. If a specification data record is changed, the SAP
system automatically assigns the data origin that is set as the default in Customizing to the
data record.
The data provider is responsible for ensuring the data is correct and is assigned to an
authorization group in Customizing for Basic Data and Tools under Specify Authorization
Groups .

Specifications
Figure 18: Workbench: Start Functionality “Create Specification“
There are various options to create a specification:
Use the Create button in the application toolbar.
The data provider is responsible for ensuring the data is correct and is assigned to an
authorization group in Customizing for Basic Data and Tools under Specify Authorization
Groups
Use the context menu and choose Create .
In the menu, choose Specification -> Create .
Use the context menu on a node in the navigation area and choose Create .
Additional Information on Identifiers

Identifiers – Additional Information 1

Figure 19: Identifiers – Additional Information 1
You can add more lists. On the SAP Easy Access screen, choose Logistics -> Environment,
Health, and Safety -> Basic Data and Tools -> Tools -> Current settings ->Specify Regulatory
Lists (transaction S_SHB_72000974 ).
Identifiers – Additional Information 2
Figure 20: Identifiers – Additional Information 2
Material Specification Assignment

Material Assignment: Material versus Specification

Figure 21: Material Assignment: Material versus Specification
Specification is an SAP EHS Management object, which is linked to a material (for example
the specification category substance), or which is not linked to a material (for example the
specification category agent).
Material is an object of the logistic chain.
Tab Page: Material Assignment
Figure 22: Tab Page: Material Assignment
When the specification is not only used in the component PS, then choose a 1:1 or n:1
relationship.
It is necessary to use only 1:1 or n:1 relationships between materials and substances (SAP
EHS Management) for reasons of integration in Product Safety and Dangerous Goods.

There are specific solutions how to handle 2-component materials ( “ kits” ). Discuss the
handling of 2-component materials in the blueprint phase.
Status and Restrictions
Figure 23: Tab Page: Status
Customer-specific status can be entered between IP (in process) and FR (for release) so that
the following status can be defined freely.
Using customer exits you can allocate value assignment types to each status. Edit the
customer exits before the status can be transferred further.
Tap Page: Restrictions

With this function, you can assign combinations of ratings and validity areas to the header
data of a specification. These combinations serve as a supplement to the authorization group,
so that by specifying these restrictions, you can restrict the authorization for a specification
more closely, for example, to certain validity areas only.
Example:
A specification belongs to the authorization group ALL; the rating PUBLIC and the validity
area DE were assigned as restrictions. If users have change authorization for ALL and
PUBLIC/DE, they can edit the header data. If users only have display authorization for
PUBLIC/DE, they can only display the header data even if they have change authorization
for the authorization group ALL.
LESSON SUMMARY

Unit 1
Lesson 3
Maintaining Properties
LESSON OVERVIEW
This lesson explains the different property types to you and how to maintain them.
LESSON OBJECTIVES
Properties and Property Trees
Figure 24: Properties and Property Trees
Property
The details on a specification in the form of numeric values including the appropriate unit
of measure, or in the form of textual information. The details can be linked with
information on the source of the data or on the method of analysis. Properties can be
grouped as follows: Physical, Chemical, Toxicological, Ecological, First aid measures,
Safety measures, Hazard classes.

Lesson: Maintaining Properties
Data Stored with Properties
Figure 25: Property: Central Information
Each specification property has between 5 and 7 tab strips, of which 1-3 tab strips allow
maintenance of major information and 4 tab strips allow maintenance of additional
information.
You can customize the type and number of tab strips.
Value Assigned Properties
Figure 26: Values
You can define your own fields through customization of the tabstrip Value Assignment , using
the SAP classification system.

Major Tab Strips
Figure 27: Property: Major Tab Strips
Major tab strips for properties are the following:
Values assignment
Composition
Listing
Transport classification
Hazardous inducer
Normal Property = Value Assignment
Figure 28: Normal Property = Value Assignment
Several different characteristics can be assigned to a property.

A data record is created for each value assignment. A maximum of 99 data records are
allowed.
Characteristics can have the following data types:
Numerical characteristics and a unit
Number range numerical characteristics and a unit
One phrase (to choose from a phrase set)
Multiple phrases (to choose from a phrase set)
Free text can be added as an exception
Table Based Value Assignment
Figure 29: Workbench: Table Based Value Assignment
The values can be characteristic values of this property or values of the additional tab strips.
You can customize each property.

Composition Properties
Figure 30: Manual Entry: Composition
The value assignment category composition lists a specification’s ingredients and

concentrations (for example exact chemical composition). In addition to the specification key,
the compound type, an average value, the lower and upper limit can be maintained.
If multiple rows of data are maintained, the order the data is shown both in the display and on
a report can be controlled by defining a sorting value.
An exception value can be used for compounds with no available data. A figure remark such
as “ unknown” or “ traces” is displayed instead ( ACT_AGENT = active agent).
Value Assignment Instance in ONE Property
Figure 31: Value Assignment Instance in ONE Property
Make sure that you perform value assignment instance within one property.

Important Additional Tab Strips
Figure 32: Property: Important Additional Tab Strips
Important additional tab strips are Usage , Assessment , Source , and User defined texts /
documents .
Additional Tools
Figure 33: Manual Entry Usage
Further uses of data in reporting are controlled by entering ratings and validity categories with
the validity area.
Ratings specify the group of persons for which documents are intended, for example for the
public, for authorities, or only for internal users.
Validity categories with validity areas specify the geographical validity. Regional validity area
categories as well as organizational units can be selected (for example plant). Examples of
validity areas include worldwide, Europe, ADR, and so on.
You can maintain the usages manually or with a usage profile.

You can specify frequently used combinations of ratings and validity areas in usage profiles.
The system proposes ratings and validity areas automatically when you edit the value
assignments of a specification.
If you set the usage to active, the corresponding value assignment can be output in a report.
Note that each change made to the data record requires renewed setting of the active
indicator.
If you have made relevant changes to a data record you must set the relevancy indicator in
the usage. This results in the creation of a new report with a new main version, which is
applied to subsequent shipping. The relevant change can be marked on the corresponding
report.
Note:
You need to know the key dates if you want to compare something.
BOM / BOS Interface - Structure
Figure 34: BOM / BOS Interface - Structure
The server administration is started in the SAP system.

Manual Entry: Source
Figure 35: Manual Entry: Source
You can assign sources to the data records. You maintain sources in a separate list (TA
specify sources). The maintained sources can be selected in the item data and can be
supplemented by source notes. The source is a user-defined text, which can specify the page
number of a book, for example.
Manual Entry: Assessment
Figure 36: Manual Entry: Assessment
In Customizing, one of the assessments can be defined as the standard choice. These value
assignments are only additional information; they do not include any control functions.

Manual Entry: User-Defined Texts / Documents
Figure 37: Manual Entry: User-Defined Texts / Documents
You can assign user-defined texts including, for example, remarks on the measurement
results for the data records.
You can maintain user-defined texts in different languages. However, translations are not
maintained centrally (as in phrase management) and have to be entered individually for each
entry.
There are various types of user-defined text.

Value Assignment Instance in ONE Property
Figure 38: Value Assignment Instance in ONE Property
Make sure that you perform value assignment instance within one property.
Where-Used List: Access
Figure 39: Where-Used List: Access

The where-used list function enables the user to search all specifications marked in a hit list at
the component, transport class, and reference level. These three searches return the
following specifications:
Specifications that contain the search component(s) in compositions or listings directly or

indirectly.
Specifications that are defined in the transport classification.
Specifications that are used as references for the search criteria.
You also have the option of defining your own where-used lists in Customizing ( Manage User
Exits ) with a function provided by the user exit category SUB_USAGE (where-used list in the
hit list).
In the standard, SAP provides the user exit SUB_SUB_USAGE1 Components/Transportcl./
reference.. . .
Direct and Indirect Component
Figure 40: Direct and Indirect Component
In the where-used list, searching for “ indirect components” returns a hit list with indirect
components as well as the upstream direct components, which contain those indirect
components.

Manual Entry: Engineering Change Management
Figure 41: Manual Entry: Engineering Change Management
In SAP EHS Management, engineering change management always runs in the background.
The validity period ranges from 01.01.0001 to 31.12.9999.
When you use a change number operation while creating a new validity period with a specific
key date (for example 01.08.2003) the validity period will be divided according to your values.
Manual Entry: Change Document Log
Figure 42: Manual Entry: Change Document Log

The SAP System logs all changes that are made within specification management . In
Customizing for Product Safety in the Specify Context Fields for Creation of Change
Documents activity, you can specify which context information is displayed on the objects
that are determined in the creation of change documents log for specifications. Samples are
identifier, material assignment, and transport approval.
In the change document, objects are determined that were created, deleted, or changed.
Changes that were made by a reference or inheritance are highlighted. For each object, the
change date, the change time, and the user name of the person who performed the change
are displayed in addition to the context information.
Hint:
The job RC1_CHANGE_DOCS_GET (the entry report) is executed only at the
times scheduled in Customizing. To enter changes in advance, you can start the
entry report manually. To do this, in the Change Document Log main toolbar,
choose Program -> Update Data, or Program -> Execute .
Copying - Referencing - Inheriting
Figure 43: Copying - Referencing - Inheriting
Using the copying function to apply the data from one specification to another specification
does not result in a connection between data entries of the two specifications after the copy is
performed.
Using the referencing function to apply the data from one specification to another
specification results in a connection between the data entries of the two specifications after
the reference is performed. If a change is made to the data of the original specification, the
same change automatically is made in the data of the referencing specification.
The inheritance function was made available in Release 2.7. Inheritance works the same way
as referencing, but has many additional functions.

Copy Templates
Figure 44: Copy Templates
When you copy templates, data for details and header data are copied too.
Reference - Structure
Figure 45: Reference - Structure
Synonym of target specification is referencing spec.

Synonym of source specifications is references spec.

The referencing function allows the user to maintain values in one source specification and
automatically give these details to other specifications. The referencing function can
significantly reduce the time required to maintain data.
Note:
Multilevel references are not allowed.
You can use several sources for one target as long as the value assignments
are unique.
Inheritance - Structure
Figure 46: Inheritance – Structure
Be aware that you have the options to either temporarily or permanently overwrite data when
you use inheritance.

Inheritance – Overwrite Data Temporarily
Figure 47: Inheritance – Overwrite Data Temporarily
Inheritance - overwrite data temporarily
Proceed as follows:
1. Create the inheritance.
2. In the target, create a new data record with new data values.
3. Overwrite the values in the source.

Inheritance - Overwrite Data Permanently
Figure 48: Inheritance – Overwrite Data Permanently
Inheritance - overwrite data permanently
Proceed as follows:
1. Create the inheritance.
2. In the target, create a new data record with new data values.
3. Overwrite the values in the source.
4. Delete the created data record with the new values in the target.

Inheritance - Status
Figure 49: Inheritance - Status
The approval status is only used in certain combinations with the inheritance status.
The inheritance relationship status can only change from INITIAL to READY FOR
INHERITANCE if an inheritance request has been approved.
If source data of a consistent inheritance relationship is modified, the status also changes
from CONSISTENT to READY FOR INHERITANCE.
You can set authorization restrictions to ensure that only authorized employees can request
and approve inheritances.

Integration of Inheritance and Referencing
Figure 50: Integration of Inheritance and Referencing
A specification cannot be the target of a reference and an inheritance function

simultaneously. The following combinations of reference and inheritance are possible:
Get data with referencing and give data with inheritance
Get data with inheritance and give data with reference
Give data with reference and with inheritance

SAP EHS Management Expert
Figure 51: SAP EHS Management Expert
SAP EHS Management Expert is a tool for secondary data determination. Secondary data
determination allows you to calculate R- and S-Sentences and store them in the system
automatically.
For example, one rule set created by SAP AG addresses DAPEC regulations. This rule set
classifies preparations according to the European directive 99/45/EC.
Using the DAPEC rule set determine the following data:
Labeling data (R-sentences...)
Hazardous substance rating (classification)
Hazardous inducing components
Labeling of special preparations
Secondary Data: Rule Sets
Table 1: Examples of SAP Regulatory Content rule sets

Comp standard composition
Hazard Comp EU hazardous ingredients, substances with OEL
for EU
Hazard Comp U.S. hazardous ingredients, substances with OEL
for US
The rule set Comp calculates the standard composition of a preparation, meaning that the
compounds of the lowest level are determined. This rule set does not address any regulatory

requirement, but instead presents a technical basis as the standard composition is needed as
input data for other rule sets (for example DAPEC). With the rule set Hazard Comp EU the
hazardous ingredients (according to 91/155/EC including 2001/155/EC) and substances with
occupational exposure limits (OELs) are determined. Concerning the substances with
occupational exposure limits one data record is created for each European country due to
their different regulations.
System Landscape
Figure 52: System Landscape
Components of SAP EHS Management Expert are the following:
SAP EHS Management Expert Server

The application of rules to existing SAP EHS Management data is used to derive new
data, which is then transferred back to the SAP EHS Management substance database.
SAP EHS Management Expert Rules and Rule Sets

Rules are based on facts which can be defined. Facts are linked to SAP EHS Management
data, for example characteristics, identifiers, usage, validity area. SAP EHS Management
Expert rules are processed quickly and effectively in the SAP EHS Management Expert
rules editor. Individual rules are combined to form sets of rules.
Mapping tables
Mapping tables are needed to assign the facts used in rules to SAP EHS Management
fields and the internal phrase keys used to the phrase keys in SAP EHS Management.

BOM / BOS Interface - Structure
Figure 53: BOM / BOS Interface - Structure
Materials are created in the SAP Materials Management module and bills of material in the
SAP Production Planning module. The BOM-BOS interface of SAP EHS Management PS
component lets you create the composition of a specification, which is assigned to the
material.
Prerequisites for the BOM BOS-interface
The specifications do not react with each other.
In positions on the BOM have to be assigned to exact one specification.
The units on the BOM have to be the same (either weight or volume).
Different levels within the positions of the BOM are not possible.
LESSON SUMMARY

Unit 1
Lesson 4
Managing and Assigning Phrases
LESSON OVERVIEW
This lesson explains how to manage and assign phrases to properties.
LESSON OBJECTIVES
Manage phrases
Phrase Definition
Phrase
A phrase is a text module, which can be used in one or more fields in the database:
- “ Das ist ein Beispiel”
- “ This is an example”
- “ Ceci est un exemple”
- ...
One phrase might be available in all languages.

One phrase can contain further information besides the text.

Lesson: Managing and Assigning Phrases
Phrase Libraries
Figure 54: Phrase: Overview
Phrase
A phrase is a standard text. Phrases can be used for the following:
Value assignment of characteristic fields in the property tree
Value assignment of certain input fields in screens
Phrases are managed in libraries. A phrase can group the same text in several languages.

Phrase Libraries
Figure 55: Phrase Libraries
Phrase Library
A phrase library is a collection of phrases used as a value assignment. Apart from the
active company library, other libraries can be kept for information purposes.
Only one library can be active at any given time!

Only the phrases in the active library can be used as phrases in the properties!

Phrase Groups in Libraries
Figure 56: Phrase Groups in Libraries
A phrase library is divided into one or more phrase groups.

A phrase group combines phrases of a library according to logical points of view, which make
it easier to search for and manage phrases (similar to a table of contents). It is not identical to
the phrase set.
You can assign a phrase to only one phrase group.
The description provides more information on the phrase group.
The phrase key identifies a phrase uniquely. The phrase key is either assigned manually or
assigned automatically by the system.

Phrase
Figure 57: Phrase
While creating a phrase, you can maintain all relevant data in the Header screen.
Edit a Phrase
Edit Phrase: Search Screen
Search for key fields (library, group, key).
Search for language key (this field is defaulted to the system language, but it can be
overwritten).
Search of phrases in other codepages. You can only use search criteria in the languages,
which are available on the front end. However, because of the Unicode-System SAP EHS
Management will display all imported languages for the phrases in the right character (for
example Greek, Chinese, ...)
Search string “ *” : (If the symbol for a generic search (*) is placed to the right of the
search string in the Phrase text field, then only the first 132 characters of a phrase are
searched for (Physician*, for example). If not, a full-text search is run (Phys*ician*, for
example, or *Physician*).
The search field is case sensitive. It distinguishes between lower case letters and upper
case letters. Exception: Search for long text phrases is not case sensitive.
Note:
All entries are “ AND” criteria. The search is realized as user-exit and you can
customize it.

Language Selection
Start: For example on the Position Data screen, choose Utilities -> Language Selection ,
then the Language selection for phrase texts dialog box.
- Select each language you would like to see in the phrase positions.
- You can choose one language as comparison language (flag C). When you open the
long text editor you see the text of the phrase on top of the page in the C language.
When you do not set a flag, the comparison language is the source language.
- In the Sequences field. you can type the order number, which defines the order of the
positions.
Note:
The chosen settings are available up until the moment you leave the transaction.
Active and Passive Phrase Libraries
Figure 58: Process Phrase Maintenance
The concept of passive and active libraries manages the phrase maintenance.
Create Phrases Manually
Process Step Action
Start Use search screen or hit list

Process Step Action
Enter header data

Choose passive library + phrase group.
Enter a phrase key (start with “ Y” ) or use

internal numbers (automatically after sav-
ing).
Choose a source language (while main-

taining properties, phrases are displayed
in the source language when the user lan-
guage is not maintained).
Enter, as minimum, the phrase text (in

this screen the maximum length is 132
characteristic).
When the phrase text covers a text varia-

ble, you can assign a user-exit to find the
correct value for this variable.
One option is to assign an inspection

method of the QM module dependent on a
special plant.
Maintain positions data ……………………………………

..
Proportion Phrases - Phrase Sets
Figure 59: Proportion Phrases - Phrase Sets
Phrases can be used to assign values to properties only if they have been assigned to a
phrase set. These phrase sets are grouped together according to logical points of view. This
means that phrases, which have not been assigned to a phrase set cannot be used for value
assignment.

A phrase can be assigned to more than one phrase set.

A phrase set contains a number of phrases.
Activities to Start in the Hit List
Figure 60: Activities to Start in the Hit List: Combining 1
If the phrase to be replaced has phrase references: The phrase references are transferred
from the replacement phrase. Phrase references with original text transfer are transferred as
phrase references without original text transfer.
If the phrase to be replaced appears in value assignments: The phrase is replaced in the value
assignment by the replacement phrase.
If the phrase to be replaced appears in dangerous goods fields: The phrase is replaced in the
dangerous goods fields by the replacement phrase.
If the phrase to be replaced has phrase items that do not occur in the replacement phrase:
The phrase items are not copied to the replacement phrase.
If a phrase that is to be replaced is used in a report, replace the symbol for the phrase
manually in the appropriate report template with the symbol for the replacement phrase. You
can use the where-used list to determine the reports that are affected before combining the
phrases. Before combining, make sure that the replacement phrase is available in the same
language as the previous phrases.

Deleting Phrases in Libraries
Figure 61: Delete Phrases
The process to delete phrases depends on how they are used.
Phrase in the active library when used:

Delete this phrase manually from the phrase sets, because the assignments still remain
there, but new assignments of this phrase are no longer possible.
Phrase in the active library when not used:
The system deletes the phrase from the phrase sets.

Phrase Based Reporting
Figure 62: Goal: Output
Texts from phrase management appear on a material safety data sheet, for example as
headings “ R Phrases” , or information on substances (such as “ Flammable” , “ Xn” ), or as
graphic symbols.
LESSON SUMMARY
Manage phrases

Unit 1
Learning Assessment
1. Name the three pillars of EHS Management.
2. Is the number of properties or property trees limited?

Choose the correct answer.
X A Yes, only the delivered properties and property trees can be used.
X B No, you can configure / customize an almost unlimited number of properties and
trees.
3. Do I have to use all properties of a property tree in an output report?

X A Yes, otherwise the output report would not be complete.
X B No, from a technical aspect the semantic grouping of properties in a tree is not
inevitably connected to any form of output report.
4. Why do you think there are so many different workbenches?
5. Which relationship between material and specification is recommended?

Choose the correct answers.
X A 1:1
X B 1:n
X C n:1
X D n:m

Unit 1: Learning Assessment
6. How many identifiers can you maintain per specification?

X A One identifier can be maintained.
X B One per language.
X C You can only maintain the ones in your logon language
X D You can define an “ arbitrary” number of identifiers, overall and per language.
7. You can search only via the identifier for a specification.

Determine whether this statement is true or false.
X True
X False
8. You can store an (almost) unlimited number of instances per property.

X True
X False
9. What is the main advantage of inheritance or referencing of specifications?

X A You can copy easily identical substances.
X B You can group substances by using the same "basic data set".
X C You can buy in verified contend by third parties, use it, but keep it separated from
your data.
X D By using inheritance, you can centralize certain aspects of data maintenance and
avoid redundancy.
10. Complex rulesets are part of standard delivery of EHS Management.

X True
X False

11. What purpose do phrases have?

X A Ease data editing
X B Simplify translation of data entered
X C Avoid typos in data entered
X D Use formulations that are industry standard or given by legislative requirements
12. A phrase can exist in many languages, but consists only of text.
X True
X False
13. A phrase must exist at any time in all languages available in the system.
X True
X False

Unit 1
Learning Assessment - Answers
1. Name the three pillars of EHS Management.
Health and Safety pillar, Product Safety and Stewardship pillar, Environmental
Performance pillar.
2. Is the number of properties or property trees limited?

X A Yes, only the delivered properties and property trees can be used.
X B No, you can configure / customize an almost unlimited number of properties and
trees.
3. Do I have to use all properties of a property tree in an output report?

X A Yes, otherwise the output report would not be complete.
X B No, from a technical aspect the semantic grouping of properties in a tree is not
inevitably connected to any form of output report.
4. Why do you think there are so many different workbenches?
Depending on the specific work area you are in, a specialized view on your area of
expertise may ease the work to do. You may concentrate only on those parts of the
specification workbench you actually need.

Unit 1: Learning Assessment - Answers
5. Which relationship between material and specification is recommended?

X A 1:1
X B 1:n
X C n:1
X D n:m
6. How many identifiers can you maintain per specification?

X A One identifier can be maintained.
X B One per language.
X C You can only maintain the ones in your logon language
X D You can define an “ arbitrary” number of identifiers, overall and per language.
7. You can search only via the identifier for a specification.

X True
X False
You can search for specifications in many ways. For example by creator, creation time,
modification time, specification type, content of header or property data, usage profile,
and so on. In case you can implement customer-specific searches by extending the
specification workbench.
8. You can store an (almost) unlimited number of instances per property.

X True
X False

9. What is the main advantage of inheritance or referencing of specifications?

X A You can copy easily identical substances.
X B You can group substances by using the same "basic data set".
X C You can buy in verified contend by third parties, use it, but keep it separated from
your data.
X D By using inheritance, you can centralize certain aspects of data maintenance and
avoid redundancy.
10. Complex rulesets are part of standard delivery of EHS Management.

X True
X False
11. What purpose do phrases have?

X A Ease data editing
X B Simplify translation of data entered
X C Avoid typos in data entered
X D Use formulations that are industry standard or given by legislative requirements
12. A phrase can exist in many languages, but consists only of text.
X True
X False
13. A phrase must exist at any time in all languages available in the system.
X True
X False

UNIT 2 Basic Configuration
Lesson 1
Configuring and Customizing Sustainability Products 57
UNIT OBJECTIVES
Set up standard Customizing and configuration
Create additional basic configuration
Set up RFC (remote function control) connections to logistics systems

Unit 2
Lesson 1
Configuring and Customizing Sustainability
Products
LESSON OVERVIEW
This lesson explains the basic configuration steps for SAP's Sustainability products.
LESSON OBJECTIVES
Default Customizing with Client 000
Figure 63: Cross System Viewer – Overview
The Cross System Viewer (CSV) compares settings in two separate systems or settings in
two clients of the same system. It can also be used to compare settings in an SAP system with
settings stored in a BC set, in an IMG project, or in a transport request. It is used to create a

Unit 2: Basic Configuration
comparison and then analyze the results. Either a general comparison can be done for status
checks or a detailed comparison for identifying differences.
The CSV identifies the following:
View/table entry differences
Field contents differences
Entry only exists in the logon client
Entry only exists in the comparison client
Additional features and benefits of the CSV:
The CSV provides a detail view of selected table rows. It lists out statistics on total entries,
modified entries, only entries, and identical entries.
CSV is designed specifically for comparing SAP systems. It is an integral part of every SAP
R/3 system since release 4.0A. It can handle self-defined groups of objects, for example
BC sets, IMG projects, and so on.
This tool can be used by project teams for comparing settings during different
implementation phases or during upgrade projects. It can also be used by administrators for
running effective online comparisons in a cross-system landscape. The tool also allows fixing
of discrepancies as soon as there are any after listing them out.
Cross-System Viewer (Customizing)
Figure 64: Cross-System Viewer (Customizing)
You can find more information about the Customizing of the CSV in the SAP Help portal.

Lesson: Configuring and Customizing Sustainability Products
Cross System Viewer: Display a Comparison
Figure 65: Cross System Viewer: Display a Comparison
Transactions:
SCU0 - Cross-System Viewer
SCMP - Single Table Comparison
SADJ - For Adjusting Differences
Authorizations
Table 2: Required Authorizations for the Customizing Cross-System Viewer

Procedure Logon client Comparison Client
Object comparison
S_TABU_DIS S_TABU_DIS
(display authorization) (display authorization)
S_TABU_RFC
Object processing
(maintenance authoriza- S_TABU_DIS
tion)
S_TABU_RFC
Additional authorization for S_TABU_CLI

editing cross-client objects

Note:
To compare objects in a system before release 4.5A, you need authorization
S_TABU_CLI but not S_TABU_RFC in the compare client.
The authorization S_TABU_RFC is part of the authorization profiles S_A.SYSTEM,

S_A.CUSTOMIZ, and S_CUS_CMP.
How to Compare Customizing with Client 000

Make sure that you fulfill the prerequisites for this demo.
You need the following authorizations for the Customizing of the CSV:
Procedure Logon Client Comparison Client
Object comparison
(display authorization) (display authorization)
S_TABU_RFC
Object processing
(maintenance authoriza- S_TABU_DIS
tion)
S_TABU_RFC
Additional authorization for S_TABU_CLI

editing cross-client objects
1. To start the CSV, choose transaction SCU0.
Figure 66: Cross System Viewer (Transaction SCU0)

2. Select the SAP Reference IMG radio button. Choose Create .
3. Choose Select activities .
Figure 67: Selection by: Enterprise IMG
Recommendation: Name the comparison as the node in the tree.
4. Select the R/3-Connection (normally: Installation client 000)
5. Choose Total comparison .
Note:
Depending on the system, a comparison may take some time. More than 10
minutes is possible.
Status Icon Description
Processing status Open
In process
Completed
Comparison status Views/tables not yet com-

pared
View/table contents are

identical
View/table contents are

identical and there are
structure differences
View/table contents are not

identical

Status Icon Description
View/table contents are not

identical and there are
structure differences
Cannot be compared (see

the following list)
Comparison may not be possible for the following reasons:
Process canceled
Table/view does not exist in logon or compare client
Table/view is too wide
User has no display authorization in the logon or compare client
No extended table maintenance dialog in the compare client
Communication error (RFC)
Comparison system crash
Key structure not convertible
Field structure not convertible
The table is a system table and therefore excluded from comparison
6. Select an entry and choose Compare .
7. Select and expand the object and check the overview. Now decide:
Difference in field content:
Transfer new entries (green) from the remote client
Is there an entry in target client? If this one is better, keep it!
8. Transfer. Open another system session.
9. Go to the compared part of the customizing. Open this entry.
10. In the menu, choose Utilities -> Compare .
11. Select the entries to be transferred and save those changes into a transport.
Adopt Standard Database Structure
Use:
- An IMG activity to transfer the classes and characteristics delivered in the standard
system for the SAP component Environment, Health and Safety from the SAP
reference client to the current client.

The value assignment types delivered in the standard system and the standard
property tree are not transferred. You must transport them manually to the current
client.
Recommendation:
- We recommend that you use these pre-Customizing settings and that you only make
enhancements to the existing database structure, particularly if you wish to use
integrated specification management.
If you do not use this pre-Customizing, you must set up the whole database structure
manually.
Caution:
Don’t use in a running system! Be aware that the system will overwrite any
modifications that you have made to the standard SAP classes and
characteristics.
Generate Standard Phrase Sets
Use:
- In this IMG activity, you generate standard phrase sets for all characteristics of data
type CHAR 30 .
Caution:
Be aware:
Phrases are not assigned during this generation.
Assignments of phrase sets to characteristics that already exist are

not overwritten by the system.
Phrase sets are not created for characteristics with a check table.
If you do not want to generate a phrase set for a characteristic of the

type CHAR 30 , delete this assignment in the phrase set-to-attribute
assignment after the standard phrase sets have been created.
To Implement Standard Phrase Sets

Adopt the Standard Database Structure.
To navigate to this activity, in Customizing (transaction SPRO) choose Environment, Health &
Safety -> Basic Data and Tools -> Specification Management -> Specification Database
Structure -> Settings for Value Assignment . Execute Adopt Standard Specification Database
Structure .
Use
When you execute this IMG activity, you transfer the classes and characteristics
delivered in the standard system for the SAP component Environment, Health and Safety

from the SAP reference client to the current client. The value assignment types delivered
in the standard system and the standard property tree are not transferred. Transport
them manually to the current client.
Recommendation
We recommend that you use these pre-Customizing settings. Make enhancements only
to the existing database structure, particularly if you wish to use integrated specification
management.
If you do not use this pre-Customizing, set up the whole database structure manually.
Caution:
Do not use in a running system! Be aware that the system overwrites any
modifications that you have made to the standard SAP classes and
characteristics.
Activities
Proceed as follows to transfer the supplied database structure to the current client when
you set up your EH&S system for the first time or when you upgrade to a newer EH&S
release:
1. Execute this IMG activity. Note that the system will overwrite any modifications that you
have made to the standard SAP classes and characteristics.
2. Copy the supplied value assignment types and property trees from the SAP reference
client (000) to the current client by running a client matchup. Use the client matchup to
delete the entries in the target client that no longer exist in the SAP reference client.
3. Once the classes and characteristics have been transferred, carry out a master data
matchup.
4. In the steps listed, the long texts for the classes and, therefore, the help texts for the value
assignment types are not copied. If you want to transfer the supplied long texts, run the
report RSTXTCPY with the following parameters:
Text name: 100SAP_EHS*
Object name: KLAT
Text ID: *
Language: *
Source client: <your installation client>
Target name: <blank>
Action log: X
Further Notes
The names of the predefined SAP classes, characteristics, and value assignment types
begin with “ SAP_EHS” . You cannot change these characteristics in the current client.

If you use the characteristics delivered with the standard SAP system, a warning
message appears telling you that the data is of type A. Ignore this message.
To match up the master data, the EH&S administrator requires the following
authorizations. Otherwise, the administrator cannot execute these IMG activities.
Authorization to edit client-independent objects
AUTHORITY-CHECK OBJECT 'S_TABU_CLI'

ID 'CLIIDMAINT' FIELD 'X'.
Authorization CCCFLOW to change (2) or to display (3)
AUTHORITY-CHECK OBJECT 'S_TABU_DIS'

ID 'ACTVT' FIELD '02' or '03' if not successful for '02'
ID 'DICBERCLS' FIELD TDDAT-CCLASS.
Authorization to create authorization profiles
AUTHORITY-CHECK OBJECT 'S_USER_PRO'

ID 'PROFILE' FIELD '*'
ID 'ACTVT' FIELD '01'.
Authorization to edit user groups
AUTHORITY-CHECK OBJECT 'S_USER_GRP'

ID 'CLASS' FIELD '*'
ID 'ACTVT' FIELD '01'.
For more information, see SAP Note 1146700.
Notes on Transport
If you execute this IMG activity, the standard SAP classes and characteristics are not
automatically transported to other systems. As a result, execute this IMG activity in each
system in which you require the standard SAP classes and characteristics.
To Generate Standard Phrase Sets

To navigate to this activity, in Customizing (transaction SPRO) choose Environment, Health &
Safety -> Basic Data and Tools -> Specification Management -> Specification Database
Structure -> Settings for Value Assignment . Execute Generate Standard Phrase Sets .
Use
In this IMG activity, you generate standard phrase sets for all characteristics of data type
CHAR 30 . In doing so, the following applies:
The phrase sets are assigned the same names as the characteristics. The description
is made up as follows:
- First 15 characters of the value assignment type
- First 15 characters of the characteristic description
The exceptions are the characteristics that end with _GLP, _PREC, and _TEST_SUB. For
these exceptions, the phrase sets SAP_EHS_XXXX_XXX_GLP,
SAP_EHS_XXXX_XXX_PREC, and SAP_EHS_XXXX_XXX_TEST_SUB are generated and
assigned. The descriptions are formed from the characteristic description only.

The languages that are defined for the value assignment types and for characteristics
are taken into account.
The newly generated phrase sets are automatically assigned to the respective
characteristic of the appropriate value assignment type. You can check the
assignments in the SAP component Basic Data and Tools by choosing Phrases -> Edit
Phrase Set-to-Attribute Assignments .
Phrases are not assigned during this generation.
Assignments of phrase sets to characteristics that already exist are not overwritten by
the system.
Phrase sets are not created for characteristics with a check table.
Phrase sets for the fields in the dangerous goods master are created in Customizing
for Dangerous Goods Management under Create Standard Phrase Sets.
Activities
Carry out this activity once only and directly after the IMG activity Adopt Standard
Specification Database Structure.
Caution:
If you do not want to generate a phrase set for a characteristic of the type
CHAR 30, delete this assignment in the phrase set-to-attribute assignment
after the standard phrase sets have been created.
Further notes
This IMG activity starts the report to generate standard phrase sets in the background.
System Distribution between EHS and Logistics
Figure 68: System Distribution between EHS and Logistics

You can exchange EH&S data and logistics data.
Tools
Application Link Enabling (ALE)

- Process:
Define logical systems
Install distribution model
Define partner contracts
Install serialization
Define reports for distribution

- Objects:
Specifications
Phrases
Report bodies (released and historical)
ALE enables you to facilitate the distribution process between two systems. In contrast to the
import/export no up- and download to/from the application server is used, but a direct
distribution via RFC. To enable this, logical systems based on the distribution model have to
be defined on which the necessary partner contracts can be generated. To guarantee a
chronological registration of the IDOCs independent from the size, activate a serialization of
the single object before the initial- and delta-distribution take place.
An automatic periodic distribution via ALE-standard-reports is possible in the source system
(RBDMIDOC) as well as in the target system (RBDAPP01).
In Customizing, choose Environmental, Health and Safety -> Basic data and tools -> Tools ->
Environmental, Health and Safety Application Link Enabling (ALE) as the necessary activity.
To specify RFC Connections to Logistics System
EH&S Application Link Enabling (ALE)

In this section, you set up EH&S Application Link Enabling (ALE) for the distribution of EH&S
data.
Information about the concept

Due to organizational or technical reasons, companies set up SAP applications on several
SAP systems. Data in an SAP system could be needed in one of the other SAP systems. For
this reason, ALE allows data to be distributed between networked systems. The following
constellations are supported for the Basic Data and Tools component:
1. ALE for information Systems:
Data is distributed to the information systems by the system in which the data is
created. Existing data is not changed in the target system.
2. ALE between several maintenance systems:

Data can be created in several maintenance systems if the data is entered separately,
for example, according to chemical family or subject area.
Data is combined using ALE in a reference system.
3. Enhancement for import and export:
Import and export is used in systems where data is exchanged only occasionally.
Decide whether it is a good idea to use ALE (static delta matchup that you can
automate), or import and export (manually controllable procedure) depending on the
application.
4. Link to SAP components:
In your company, you may want to distribute SAP components to different systems for
organizational or technical reasons.
For this reason, distribution is possible for SAP components that require specification
data (for example, Materials Management , Sales and Distribution ).
5. ALE for external systems:
External systems are all non-SAP systems. External systems can require data from the
Basic Data and Tools component.
ALE provides a defined interface.
Further notes
You can make your own adjustments to the ALE process by copying the object methods
REPLICATE and SAVREPMULT. Modify them, and then generate the Business Application
Programming Interfaces (BAPIs). In doing so, you generate the ALE interface.
You can reduce the amounts of data to be distributed by removing one or more method
interface parameters.
You can extend the amount of data to be distributed by including one or more segments in
the interface for the methods. For example, you can add the material header segment to
the specification header segment. Afterwards, adjust the reading and writing of the data to
be distributed in the object methods.
For more information, see Cross-Application Components -> Distribution (ALE) in the SAP
Implementation Guide.
Detailed description in Customizing:
ALE for Specification Management
ALE for Phrase Management
ALE for EH&S Reports
ALE for Incident/Accident Management
LESSON SUMMARY

Unit 2
Learning Assessment
1. What purpose has the Cross System Viewer for setting up the system?
X A Compare specifications stored in the different systems.
X B Compare and / or align customizing settings between systems, for example Client
000 and QA.
X C Transport large amounts of data between the systems.
X D Control versions of the maintained customizing.
2. What can be a reason to use the delivered pre-Customizing settings?

X A Otherwise you cannot set up the EHS database structure at all.
X B It delivers best practice settings, which are highly recommended.
X C If you set up your specification database manually, you are in danger of losing
integration of other EHS Management solutions (such as SAP product and REACH
compliance).
3. What purpose does the setup of ALE connections have?

X A Distribute data between systems independently from import or export of data.
X B Load balancing between different EHS Management systems.
X C Backing up data to a remote system.

Unit 2
1. What purpose has the Cross System Viewer for setting up the system?
X A Compare specifications stored in the different systems.
X B Compare and / or align customizing settings between systems, for example Client
000 and QA.
X C Transport large amounts of data between the systems.
X D Control versions of the maintained customizing.
2. What can be a reason to use the delivered pre-Customizing settings?

X A Otherwise you cannot set up the EHS database structure at all.
X B It delivers best practice settings, which are highly recommended.
X C If you set up your specification database manually, you are in danger of losing
integration of other EHS Management solutions (such as SAP product and REACH
compliance).
3. What purpose does the setup of ALE connections have?

X A Distribute data between systems independently from import or export of data.
X B Load balancing between different EHS Management systems.
X C Backing up data to a remote system.

UNIT 3 EHSM Data Structure
Lesson 1
Defining a Property Tree 72
Lesson 2
Managing Phrases 83
UNIT OBJECTIVES
Navigate in a property tree
Maintain a property tree
Create value assignment types
Set up phrase catalogs, phrase sets, and phrase set assignment

Unit 3
Lesson 1
Defining a Property Tree
LESSON OVERVIEW
This lesson explains how to navigate through and define property trees.
LESSON OBJECTIVES
Property Tree
Property tree:
- A filter, a structured view on the properties in the specification database
Figure 69: Property Trees, Classes, ... – Terms: Overview
Customizing activities may be required to enable users working with tables, classes, or
characteristics.

Lesson: Defining a Property Tree
Properties and Property Trees
A property tree is the structured depiction of properties. Properties are sometimes called
value assignment types (VAT).
The visibility of property trees depends on specification types.
Characteristics
Characteristic:
- Defines a field in the property and allows values to be entered

Unit 3: EHSM Data Structure
Figure 71: Properties
Properties (classes) can be assigned to different value assignments (characteristics).

They are grouped in the tree under the aspect of functional logics.
Classes
The class contains assigned characteristics. The class and the value assignment type
(customizing) control the appearance of a property.
Flexible Property Tree

A property tree is the structured depiction of properties. Properties are sometimes called
value assignment types.
The visibility of property trees depends on specification types.
Creating / Modifying Property Trees
Where?
In Customizing, choose Environment, Health and Safety -> Basic Data and Tools ->
Specification Management -> Specification Database Structure -> Settings for Value
Assignment -> Set Up Property Trees .
Which data?
Value assignment type (ID).
Property position is determined by consecutive number. Root ID = 1.
Nodes need their own ID.
The level defines where the node is integrated in the property tree.
Select ComprInd , if expanded view of the respective subtree is not to be displayed.
Configuration of the Property Tree
You can configure a property tree in the following way:
Select the property tree to be modified (edit mode).
Open a second system session (one system for displaying, one system for entering
modifications).
On the display screen, identify the position where the new property is to be added.
On the modification screen:
Select an ID between the previous and the following entry. Attention: reserve intervals for
future enhancements.
Choose the New Entries button, enter the ID, and the new value assignment type.
If required, enter Level and ComprInd .
Specification Database: Dynamic Adjustment
Reasons for Adjusting the Specification Database

Customer-specific creation of new characteristics and classes
Assignment of value assignment types to classes
Customer-specific configuration of the property tree / creation of new property trees
Assignment of phrase sets to characteristics and respective filling of the characteristics
In most cases, the property trees delivered with the standard system are sufficient for
specification data management.
If enhancements are necessary, then execute the following steps:

Create new classes (master data).
Create new characteristics (master data).
Assign value assignment types to characteristics (Customizing).
Configure the property tree (Customizing).
If the new characteristics are based on phrases, then proceed as follows:
Create phrases and phrase sets, if they do not exist already.
Assign phrase sets to the respective characteristics.
Creating New Classes
Where?
On the SAP Easy Accessscreen, choose Cross-Application components -> Classification ->
Master Data -> Classes (transaction CL02).
Class type: Use only 100 (value assignment).
Which data?
Basic data
Characteristics
Creating New Characteristics
Where?
On the SAP Easy Accessscreen, choose Cross-Application components -> Classification ->
Master Data -> Characteristics (transaction CT04).
Which data?
Basic data: description of the characteristic, data type ( NUM/ CHAR), number of
charachters, unit of measure, template, single/multiple value assignment possible
Description
Values (allowed or with check)
Restrictions
The first step is to create characteristics. This is possible in transaction CT04. The data
maintained in this function determines the type of characteristic values to be maintained.
To Create a New Characteristic

Create a new characteristic using the corresponding transaction.
1. On the SAP Easy Accessscreen, choose Cross-Application Components -> Classification

System -> Master Data -> Characteristics (transaction CT04).
2. In the Characteristic field, enter a name.

3. Choose (Create).
4. Enter data in all mandatory fields. Example:

Field name Value
Characteristic BOILINGPOINT METHOD
Description Method
Data type Character format
Number of characters 30
Restrictions 100
Be aware that you might have to enter data on all tab pages on the Characteristics screen.
5. Save your entries.
To Create a New class

Create a new class.

System -> Master Data -> Class (transaction CL02).
2. Select a class and a class type.
3. Choose (Create).
4. Enter a description.
To Assign New Characteristics to the New Class

System -> Master Data -> Class (transaction CL02).
2. Choose an existing class and choose (Change).
3. Choose the Characters tab page.
4. Enter characteristics in the table.
Table Based Value Assignment Types

Value assignment type
The value assignment type (VAT) is the link between the classification system and the
property. With the VAT, EHS-specific settings such as the usage profile are defined. In

addition, the characteristics of the value assignments are assigned to the class delivered
by SAP.
Customer-specific classes can be defined and assigned to properties. The properties
themselves are assigned to property trees by which the maintenance of the data is
performed.
Creating New Value Assignment Types
Where?
- In Customizing, choose Environment, Health & Safety -> Basic Data and Tools ->
Specification Management -> Specification Database Structure -> Settings for Value
Assignment -> Specify Value Assignment Types .
Which data?
- ID of value assignment type = class ID
- Language-dependent description
- Specified value assignment category
- Class
- Control flags
- Entry of the usage profile
- Entry of the identifier listing
Table Based Value Assignments: Overview
Figure 73: Table Based Value Assignments: Overview
Table based value assignment simplifies maintaining and using specification data.
The new controls used optimize maintaining data.

You can use vertical or horizontal tables and you can switch between them.
Set Up Table Based Value Assignments
Figure 74: Set Up Table Based Value Assignments
Customizing of table based value assignment is supported by the report RC1TCG11_02. The
report delivers for all properties and characteristics the entries, which are necessary for the
table based presentation. Thus, it is possible to adjust the sorting and properties of the
individual field in the dialog.
The table entries created are not automatically placed in a transport request. You manually
add them to a transport once the program has been run if you want to transport them to other
systems.
To Specify Table-Based Value Assignments

In Customizing, create a new VAT. Then, create a node for it.
1. In Customizing, create a VAT.

a) On the SAP Easy Accessscreen, choose Tools -> Customizing -> IMG -> Execute
Project (transaction SPRO).
b) To select the IMG activity, choose the SAP Reference IMG pushbutton. Then, choose
Environment, Health & Safety -> Basic Data and Tools -> Specification Management ->
Specification Database Structure -> Settings for Value Assignment -> Specify Value
Assignment Types .
c) Choose the New Entries pushbutton. Enter data in or maintain the following fields:
Field name

Field name
Description
Value assignment category
Class (VA)
New VA active
Change active
Usage profile
ID listing
d) Press ENTER. Save your entries.
e) Choose ( Back ) to go back to the Change View "Value Assignment Type":

Overview screen. Remain on this screen.
2. Create a node for the new VAT.

a) Choose the New Entries pushbutton. Enter data in or maintain the following fields:
Field name

Description
Value assignment category
b) Press ENTER. Save your entries.
c) Choose ( Back ) to go back to the Display IMG screen.
To Adjust the Property Tree

In Customizing, copy and include a new value assignment and a new node into a property
tree.
1. In Customizing, choose the Set Up Property Trees activity to copy and include your new
value assignment and your new node into the property tree. Use an existing (for example
Z_TR_PROF) property tree as template and rename it.
a) On the Display IMG screen, choose Environment, Health & Safety -> Basic Data and
Tools -> Specification Management -> Specification Database Structure -> Settings for
Value Assignment -> Set Up Property Trees .
b) Select the Z_TR_PROFproperty tree (EH&S Professional Training) and choose

( Copy as ). You copy and include a new value assignment and the new node into the
property tree.
c) Overwrite the old property tree and enter a new description.
d) Press ENTER. In the pop up, choose Copy all to all connected entries.

e) Confirm the number of dependent copies. Check in the status line if your entries were
copied.
f) Save your entries. Check in the status line if your entries were saved.
g) Remain on the Change View "Property Tree": Overview screen.
2. Adjust the copied property tree with “ Value assignment type assignment” .
a) On the Change View "Property Tree": Overview screen, select the copied entry.
b) In the Dialog Structure , double-click the Value Assignment Type Assignment folder.
c) Enter the data, for example:

ID Level Value Assignment Type
400000 (no spaces!) 2 Z_##_node (new node for

property tree)
400100 (no spaces!) 3 Z_##_BOILINGPOINT (so
you can see this property
in the tree)
d) Press ENTER. Save your entries. Check in the status line if your entries were saved.
To Assign a VAT to the Property Tree
1. Adjust a copied property tree with “ Value assignment type assignment” . Enter the
following data:
a) On the Change View "Property Tree": Overview screen, select an entry you copied
before.
b) In the Dialog Structure , double-click the Value Assignment Type Assignment folder.
c) Enter the following data, for example:

ID Level Value Assignment Type
400000 (no spaces!) 2 Z_00_node (new node for

property tree)
400100 (no spaces!) 3 Z_00_BOILINGPOINT (so
you can see this property
in the tree)
d) Press ENTER. Save your entries. Check in the status line if your entries were saved.
To Create a New Specification Type

In case to adopt to certain customer needs, you may create one or more specification types.

Caution:
In case you introduce new specification types to you system, certain adoptions
may have to be taken into account to ensure proper functionality of the EHS
modules.
1. In Customizing, choose the activity Specify Specification Types .

b) Choose the SAP Reference IMG pushbutton.
c) To choose the activity, choose Environment, Health & Safety -> Basic Data and Tools ->
Specification Management -> Specification Master -> Specify Specification Types .
2. Choose New Entries pushbutton.
3. Complete the dialog with intended values.
To Assign Specification Types to the Property Tree

Assign a specification type to a new property tree.
1. In Customizing, choose the activity Specify Specification Types .

b) Choose the SAP Reference IMG pushbutton.
c) To choose the activity, choose Environment, Health & Safety -> Basic Data and Tools ->
Specification Management -> Specification Master -> Specify Specification Types .
2. Assign the specification type to the new property tree.

a) Select the specification type.
b) In the Dialog Structure , double-click Specification Type - Property Tree Assignment .

Choose the New Entries pushbutton.
c) To add the new property tree, enter a name in the Prop. tree column. Press ENTER.
d) Save your entries. In the status line, check if your data was saved.
e) Choose ( Back ) to go to the SAP Easy Accessscreen.
LESSON SUMMARY

Unit 3
Lesson 2
Managing Phrases
LESSON OVERVIEW
This lesson explains how to manage phrases and set up phrase sets.
LESSON OBJECTIVES
Catalogs and Phrase Sets
Figure 75: Phrases Overview
Phrase
A phrase is a standard text. Phrases can be used for:
Value assignment of characteristic fields in the property tree
Value assignment of certain input fields in screens and dialog boxes
Phrases are managed in libraries. A phrase can group the same text in several languages.

Phrase Libraries
Figure 76: Phrase Libraries
Only one library can be active at any given time!

Only the phrases in the active library can be used as phrases in the properties!
Phrase Groups in Libraries
Figure 77: Phrase Groups in Libraries

Lesson: Managing Phrases
A phrase library is divided into one or more phrase groups. A phrase group combines phrases
of a library according to logical points of view. which simplifies searching for and managing
phrases (similar to a table of contents). A phrase group is not identical to a phrase set.
You can assign a phrase to only one phrase group.
The phrase key identifies a phrase uniquely. The phrase key is either assigned manually or
assigned automatically by the system.
The description provides more information about the phrase group.
LESSON SUMMARY

Unit 3
Learning Assessment
1. The visibility of property trees depends on specification types.

X True
X False
2. The characteristic defines a field in the ...

X A ... property
X B ... property tree
3. Which class type is the one for value assignments?

X A 10
X B 100
X C 110
X D 300
4. What is the action to enhance property trees?

X A Create new material master records
X B Create new classes
X C Create new characteristics
X D Configure the property tree

5. Which data do you use to create new value assignment types?

X A Class ID
X B Characteristics data
X C Language independent description
X D Entry of the usage profile
6. More than one phrase libraries can be active at a certain point in time.
X True
X False
7. To how many phrase groups can you assign a phrase?

Unit 3
1. The visibility of property trees depends on specification types.

X True
X False
2. The characteristic defines a field in the ...

X A ... property
X B ... property tree
3. Which class type is the one for value assignments?

X A 10
X B 100
X C 110
X D 300
4. What is the action to enhance property trees?

X A Create new material master records
X B Create new classes
X C Create new characteristics
X D Configure the property tree

5. Which data do you use to create new value assignment types?

X A Class ID
X B Characteristics data
X C Language independent description
X D Entry of the usage profile
6. More than one phrase libraries can be active at a certain point in time.
X True
X False
7. To how many phrase groups can you assign a phrase?
You can assign it to only one phrase group.

UNIT 4 Data Migration
Lesson 1
Defining and Setting up the Data Model 91
Lesson 2
Transferring Data Between Test and Production System 97
Lesson 3
Migrating of Substance Data 102
Lesson 4
Migrating of Phrases and Reports 110
UNIT OBJECTIVES
Analyze and migrate typical legacy data
Transfer master data
Navigate in master data tools
Migrate phrases
Migrate reports

Unit 4
Lesson 1
Defining and Setting up the Data Model
LESSON OVERVIEW
This lesson explains how to migrate and prepare legacy data, and it lists possible problems.
LESSON OBJECTIVES
Availability Analysis
Specification Types
Table 3: Specification Types Summary

Specification type Definition Functionality Example
Real substance Substances that are Real substances can Glass cleaner, metal
physically present in be assigned to mate- cleaner
an enterprise and rials
correspond to a ma-
terial in logistics
Pure substance Ideal substance Chemical, physical Acetone
and toxic properties
assigned; Lowest lev-
el of composition.
Listed substance Substance on a (reg- Listed substances are Acetone
ulatory) list used as reference
substances, they can-
not be assigned to
materials.
Real substance group Group of real sub- To simplify the struc- Surface cleaner
stances formed from ture when the same
a logical point of view properties are given
Exposure scenario Specification to store Contain all data to be PROC8A_IND
the annex data for the printed in the annex,
extended SDS except the data for
(eSDS-EU) section 1 of the annex
UN-listed substance Regulatory data in Assignment of regu- 1993 (flammable liq-
dangerous goods latory data from dif- uid, n.o.s.)
ferent dangerous
goods directives

Unit 4: Data Migration
Specification type Definition Functionality Example
Dangerous goods Regulatory classifica- Assigns a unique Classification key:

classification tion of a dangerous classification to a CL1993_II_00
good dangerous good
Data Model with Real Substance Group
Figure 78: Data Model with Real Substance Group
Companies can use a template substance with the substance type real substance group to
maintain one time first aid details. If they do so, they can use this template to reference or to
inherit this data to several similar substances.

Lesson: Defining and Setting up the Data Model
Data Model Additions
Figure 79: Data Model Additions
Additional specification types can be linked to the real substance.
Values
Figure 80: Values
You can define your own fields by customizing the value assignment tabstrip, using SAP's
classification system.

Availability of Data Sets
Figure 81: Availability of Data Sets
It is necessary to map these data sets field by field, to see each difference, and to adjust the
possible entries for example for phrases. Each difference requires a detailed check and may
cause a customer-specific property.
To Analyze Typical Legacy Data

Availability analysis of required data.
1. Check data in existing systems/reports.

Analyze and list all data printed on MSDS and other reports, with storage location and
format. List all used phrases and compare/map with CED-phrases.
2. Data mapping / data description for MSDS.

For example: Chapter: Hazards identification from SERC EU MSDS 2007
Information Technical Informa- Data Source Comment
tion
Heading: Risk advice Phrase CED- Coding in WWI-tem-

to man and the envi- E20.00000020 plate
ronment
List of phrases, one Property: Hazardous Manual or ruleset
line per phrase substance rating DAPEC
(SAP_EHS_1023_00
4)
If no phrase can be
found, then output
of "Additional Info"
of Property “Hazard-
ous Substance Rat-
ing”
(SAP_EHS_1023_00
4)

Lesson: Defining and Setting up the Data Model

tion
List of phrases, one Property “Possible Manual or ruleset

line per phrase hazards (summary)” MSDS-MAKER
(SAP_EHS_1011_001
), field advice
For example: Fields

tion
pH Value:
Property:
SAP_EHS_1013_
019
Char:
SAP_EHS_1013_
019_VALUE
NUM 4.2, Single-
value, intervals
allowed, negative
values allowed
No unit
3. Transfer in mapping spreadsheet (extract)
Specification Identifier Physical- Physical- Physical-

header/ CAS Number chemical chemical chemical
specification Identifikator properties/ properties/ properties/
key CAS Numm- Oxidizing/ Vapor pres- Vapor pres-
Spezifika- er Oxidizing sure/Accu- sure/
tionskopf/ CHAR=132 type racy Temperature
Spezifika- Physik./ Physik./ Physik./
tionsschlüs- Chem.Eigen- Chem.Eigen- Chem.Eigen-
sel schaften/ schaften/ schaften/
CHAR=12 Brandför- Damp- Damp-
dernde Ei- fdruck/ fdruck/
genschaf- Genauigkeit Temperatur
ten/Typ PHRASE NUM=7; 2
PHRASE Decimals;
Unit °C (Ein-
heit muss
nicht einge-
geben wer-
den)
H:SUBID I:IDENT,ID- M:SAP_EHS_10 M:SAP_EHS_10 M:SAP_EHS_10

TYPE="NUM",ID- 14_004_TYPE; 13_003_PREC;S 13_003_EC_TE
CAT="CAS" SAP_EHS_1014 AP_EHS_1013_0 MP
_004 03

string;void.book STRING.LIST<"; STRING NUMWITHUNIT

is<>;void.bookis ">
<>
0000000001 100-00-5 CUST- 20
X01.01112345
0000000002 100-00-5
0000000003 100-01-6 20
4. Possible problems:
Format of data fields is different
Different units
Different dimensions kg, g, mg
Phrase does not exist
Phrases are not part of phrase sets
Spelling is different
Spelling mistakes
Translation mistakes
Limitations of MS Excel (256 columns, 64000 rows)
Automatic formatting in MS Excel
Non-unicode sign sets (go via Access newer as Access 2000)
Data migration needs a high effort in data cleansing before, and data control after import!
LESSON SUMMARY

Unit 4
Lesson 2
Transferring Data Between Test and
Production System
LESSON OVERVIEW
This lesson explains the transfer of master data between test system and production system.
LESSON OBJECTIVES
Transfer Master Data
Tools - Import and Export
Process:
- Defining import folder, export folder, and file names
- Defining data origin
- Creating exchange profiles
Objects:
- Specifications
- Phrases
- Reports
- Property trees
- Templates
Import and export is used for transporting data from an old system.
You can also use this function for routine exchange of data and up-dating data, for example
for phrase libraries.
If you maintain specifications in different systems you can use this tool to import the data in
one central system of consolidation.

Import and Export - Migration Overview
Figure 82: Import and Export - Migration Overview
The major steps of a migration are the following:
1. Data export
2. Download
3. Upload
4. Data import
Import and Export - Call
Table 4: Import and Export - Call

Export Import
In the applications of SAP EHS Management In the basic tools of SAP EHS Management
or in the IMG, use the export functionalities. start and check the import.
<Object> Logistics
Exchange data SAP EHS Management
Exporting Basic data and tools
Tools
Data transfer
Import <Object>

Lesson: Transferring Data Between Test and Production System
Export
<Object> is a wild card for several objects of Environment, Health, and Safety such as:
Specification
Hit list in Specification Workbench (transaction GCG02BD), then in the menu choose
Specification -> Data exchange -> Export .
Phrases
Hit list in Phrases ( CG12), then choose Phrase -> Data Exchange -> Export .
Report templates
Hit list in Report templates ( CG42), then choose Report templates -> Export .
Property trees
Define property trees in Customizing and export from there. In the IMG , choose:
Environment, Health and Safety -> Basic Data and Tools -> Specification Management ->
Specification Database Structure -> Settings for Value Assignment Categories -> set up
prosperity trees .
Start the activity and choose the Export pushbutton.
Import and Export - Export of Phrases (Example)
Import and export - export of phrases

- Where?
Transaction CG12(Hit list phrases)
Menu: Phrase -> Data exchange -> Export

- Parameters:
Exchange profile
Overwrite file
Key date for export
Complete export
Phrase reference
Phrase set assignments
Phrase item status
Language selection
Exchange profile is only important when you want to import or export specifications.
If you choose the Overwrite flag, then an existing exchange file will be overwritten.
Key date is only important if you use the SAP change service.
If you choose one phrase and set the flag Complete export , then the whole library will be
exported.

If you choose the flags Phrase reference , Phrase set assignments , and Phrase item status ,
then these details will also be exported.
Using the Language selection you can export phrases in only one special language.
Import and Export - Import of Phrases (Example)
Import and Export - Import of Phrases (Example)

Where?
On the SAP Easy Accessscreen, choose Logistics -> Environment, Health and Safety -
>Basic Data and Tools -> Tools -> Data transfer -> Import phrases .
Parameter:
Exchange profile, for example Standard
Character standard
Complete import*, see the caution in the script
Phrase reference, assignment of phrases to phrase sets, status of the phrase item
Language selection
Preliminary check of the file
Exchange profile
It is good to use a profile with default parameters. You can define it in Customizing.
Choose Environment, Health and Safety -> Product safety -> Interfaces -> Import and
export -> Basic settings for import and export -> Specify exchange profiles .
Character standard
In case of doubt the format of the character can be chosen from the header data of the
import file.
If you mark one phrase and set the Complete export flag, the whole library will be
exported.
Caution:
We recommend strongly not to import into the active library. If you do so,
all phrases of the active phrase library will be deleted. The content of the
update file is written in the empty library. Even slight errors in the update
file result in losing the complete phrase library.
When you set the flags for Phrase reference , Phrase set assignments , and Phrase item status,
these details will also be exported.
Using Language selection you can export phrases in only one language.
Preliminary check
It is best to use Identifiers for your search: Choose an identifier listing, which you had
created for import and which has only one identifier with unique value.

Lesson: Transferring Data Between Test and Production System
LESSON SUMMARY

Unit 4
Lesson 3
Migrating of Substance Data
LESSON OVERVIEW
This lesson explains the Data Editor and the Open Content Connector
LESSON OBJECTIVES
Data Editor
Figure 83: Data Editor and OCC - Overview
OCC stands for Open Content Connector. The EH&S OCC dialog box allows you to compare
the data from a content provider with the data that you already have in your specification
database. You can import the data, postpone the decision to import until a later date, or reject
the import of the data offered.
Functions
Compared to other add-ons:
Expert:

Lesson: Migrating of Substance Data
- Calculates secondary data for existing substances
OCC:
- Loads primary data for existing substances
EHS data editor:

- Edits existing substances online or offline
- Loads primary data for existing substances
- Creates new substances
Data Editor
The EHS data editor being an add-on product to SAP EHS Management is a comfortable tool
for the following situations:
Edit EHS data manually
Create reports and safety data sheets
Migrate legacy data easily
Take over supplier data into the business process easily
The EHS data editor can be used online connected to an SAP EHS Management system or
offline without connection to this system:
Clearly arranged in the original property tree from SAP EHS Management
With value selection from original phrases and data definitions from SAP EHS
Management
Offline using local files to be imported later, based on existing data which has been
exported before or
Online connected to the SAP EHS Management database
Integrating suppliers
An offline installation of EHS data editor can be provided to suppliers, together with
previously exported data definitions and phrase sets from an EHS property tree and
optionally with list substance data. Suppliers enter their product data offline and deliver
the resulting files together with their products. The EHS data editor integrates functionality
to export property trees and phrase sets as well as substance data. Likewise the EHS data
editor offers functionality to import substance data into EHS Management, which was
previously manually edited or read in by the integrated migration tools.
Migrating legacy data
The EHS data editor supports two scenarios to take over external data or legacy data
automatically. These scenarios are implemented using two additional tools.
The EHS substance import tool (SIT) interprets and imports data in table format, which
can easily be created from a legacy system and maintained by MS Access or MS Excel. The
heading lines of a table maps table columns to EHS data elements.

The EHS phrase import tool (PIT) creates import files based on a MS Excel-Spreadsheet/
Txt-File.
Data Editor Overview
Data Editor
Introduction
Main functions
Examples
Installation / support
On the next slides you can find more information about the Data Editor, its main functions,
some examples, and where to find information on installation and support.
Data Editor Introduction
Introduction
Data editor - what is it?
C++ add-on for EH&S
Data editor - what is it not?
No official part of EH&S

- Extra license! Predefined service
- No CSS support
Data Editor Main Functions
Main Functions
Editing of substances (online / offline with property tree)
Creating new substances
Reading data from SDS
Phrase import from text-file

- Import with transaction CG31
Substance import from text-file

- Migration from different systems
- Import with transaction CG33or online via RFC & Substance API

Example Editing a Substance Online (1/4)
Figure 84: Example Editing a substance online (1/4)

Figure 87: Example Editing a Substance Online (4/4)

Example Importing a Substance (1/2)
Figure 88: Example Importing a Substance Online (1/2)
The figure shows substance data in an ASCII-Text file.
Example Importing a Substance (2/2)
Figure 89: Example Importing a Substance (2/2)
Import online or offline or use a .DAT file.
Installation / Support
1. Download from marketplace
2. Execute as local administrator
3. Start the data editors as local admin
4. Enter license key

Open Content Connector
OCC - Open Content Connector

OCC - what is it?
C++ add-on for EH&S
Open interface for loading of substance data
SAP standard software

- CSS support (EHS-BD-TLS-OCC)
- No extra license required
Example Loading of Substance Data (1/2)
Figure 90: Example Loading of Substance Data (1/2)

Example Loading of Substance Data (2/2)
Figure 91: Example Loading of Substance Data (2/2)
Installation / Support
Installation:
Read in IMG : Basic Data and Tools -> Tools -> EH&S Open Content Connector
Download from the SAP Service Marketplace
Execute and select OCC instead of Expert
Configuration:
Create and/or configure user exit ( IMG : Environment, Health and Safety -> Basic Data and
Tools -> Basic Settings -> Manage User Exits )
Create RFC destination (transaction SM59)
Create load instance on front end
Support:
Installed documentation
SAP Online Help
CSS: component EHS-BD-TLS-OCC
LESSON SUMMARY

Unit 4
Lesson 4
Migrating of Phrases and Reports
LESSON OVERVIEW
This lesson explains the migration (import and export) of phrases and reports.
LESSON OBJECTIVES
Migrate phrases
Migrate reports
Phrase Migration
Tools: Import and Export

Process:
Defining import folder, export folder, and file names
Defining data origin
Creating exchange profiles
Objects:
Specifications
Phrases
Reports
Property trees
Templates

Lesson: Migrating of Phrases and Reports
Import and Export - Migration Overview
Figure 92: Import and Export - Migration Overview
Import and export is used for transporting data from an old system.
You can use this function also for routine exchange of data and updating data, for example for
phrase libraries.
If you maintain specifications in different systems, you can use this tool to import the data in
one central consolidation system.
Export Import
Use in the applications of EHS Management In the basic tools of EHS Management start
or in the IMG the export functionalities and check the import
<Object> Logistics
Exchange data SAP Management
Exporting Basic data and tools
Tools
Data transfer
Import <Object>
Export
<Object> is a wild card for several objects of Environment, Health and Safety such as:

Specification
Hit list specification workbench (transaction GCG02BD), then in the menu choose
Specification -> Data exchange -> Export .
Phrases
Hit list phrases ( CG12), then choose Phrase -> Data Exchange -> Export .
Report templates
Hit list report templates ( CG42), then choose Report templates -> Export .
Property trees
Define properties in Customizing and export then from there. In the IMG , choose:
Environment, Health and Safety -> Basic Data and Tools -> Specification Management ->
Specification Database Structure -> Settings for Value Assignment Categories -> set up
prosperity trees .
Start the activity and choose the Export pushbutton.
Import and Export - Export of Phrases (Example)
Import and Export - of Phrases (Example)

Where?
Transaction CG12(Hit list phrases)
Menu: Phrase -> Data exchange -> Export .
Parameters:
Exchange profile
Overwrite file
Key date for export
Complete export
Phrase reference
Phrase set assignments
Phrase item status
Language selection
Exchange profile is only important when you want to import or export specifications.
When you choose the Overwrite flag, then an existing exchange file will be overwritten.
Key date is only important if you use the SAP change service.
If you choose one phrase and set the flag Complete export , then the whole library will be
exported.
If you choose the flags Phrase reference , Phrase set assignments , and Phrase item status ,
then these details will also be exported.
Using the Language selection you can export phrases in only one special language.

Lesson: Migrating of Phrases and Reports
Import and Export - Check Export

Where?
On the SAP Easy Accessscreen, choose Logistics -> Environmental, health and safety ->
Basic Data and Tools -> Tools -> Export log -> check <Object export> .
or
Transaction SM37(Simple Job Selection)
or
On the SAP Easy Accessscreen, in the menu choose System -> Own Jobs . Choose the
desired job and in the overview, then choose the Job-log button.
Report Migration
Export and import of reports

Each report has two files: *.dat and *.doc . Two options:
1. Recommended: Import with transaction CG36( Import Reports ).
This transaction provides a 1:1 check and a match of each symbol.
2. Not recommended: Manual creation of the header, copy and paste in MS Word.
Fast, no detailed checks, may work if all recommendations are respected.
Import of Vendor MSDS
Reports are provided via supplier or third parties as PDRF or RTF/DOC.

The reports are stored in the DMS with information about language, specification, Report
Generation Variant, version, date, and an optional supplier.
To import, use transaction CG36VEN( Import of Vendor MSDS ).
Note:
There is no relation between the report data and the data in the specification
database.
LESSON SUMMARY
Migrate phrases
Migrate reports

Unit 4
Learning Assessment
1. What is a “ pure substance” in the sense of the specification database?

X A A substance in my production process, which is 100% pure.
X B An idealistic model of a chemical pure substance that holds basic data.
X C A material that can purely be sold.
2. Why is it beneficial to match customer maintained phrases to CED phrases?

X A To avoid doublets.
X B To ensure legal accurate formulations and benefit from the updates of the phrase
catalog.
X C To make report generation faster. Handling of CED phrases is speed optimized.
X D Only the CED phrases are allowed to be used on legal binding documents.
3. What is the primary purpose of the transfer of master data?

X A Backup
X B Synchronize different systems with identical data.
X C Transfer data from an old SAP system to a new one.

4. Which data can be transferred with the described methods?

X A Materials
X B Phrases
X C Specifications
X D Property trees
X E Report templates
5. What do you consider when you import phrases into an active phrase library?
X A It creates duplicates in the phrase library
X B The target phrase library will be deleted (emptied) before import. You may lose all
phrases.
X C Importing into the active phrase library is to slow due to technical reasons.
X D You can only import into passive phrase libraries.
6. For which purpose can you use the data editor?

X A Involvement of third parties of data delivery
X B Online and offline data editing
X C Report generation outside of the SAP frontend
X D Run expert rulesets for secondary data determination.
7. Can you edit existing data with the open content connector (OCC)?
X True
X False

8. For which purpose can you use the phrase import and export?
X A For initial filling of an SAP system.
X B For backup reasons.
X C Transporting phrase data from one system to another one (for example, due to
system renewal).
9. How can you access the exported phrase data?

X A File share of the application server.
X B It will be sent automatically by e-mail.
X C Via FTP to the application server.
10. From which parts does a complete report exist of?

X A a .DAT file
X B a. .BAK file
X C a .DOC file
X D an .XLS file

Unit 4
1. What is a “ pure substance” in the sense of the specification database?

X A A substance in my production process, which is 100% pure.
X B An idealistic model of a chemical pure substance that holds basic data.
X C A material that can purely be sold.
2. Why is it beneficial to match customer maintained phrases to CED phrases?

X A To avoid doublets.
X B To ensure legal accurate formulations and benefit from the updates of the phrase
catalog.
X C To make report generation faster. Handling of CED phrases is speed optimized.
X D Only the CED phrases are allowed to be used on legal binding documents.
3. What is the primary purpose of the transfer of master data?

X A Backup
X B Synchronize different systems with identical data.
X C Transfer data from an old SAP system to a new one.

4. Which data can be transferred with the described methods?

X A Materials
X B Phrases
X C Specifications
X D Property trees
X E Report templates
5. What do you consider when you import phrases into an active phrase library?
X A It creates duplicates in the phrase library
X B The target phrase library will be deleted (emptied) before import. You may lose all
phrases.
X C Importing into the active phrase library is to slow due to technical reasons.
X D You can only import into passive phrase libraries.
6. For which purpose can you use the data editor?

X A Involvement of third parties of data delivery
X B Online and offline data editing
X C Report generation outside of the SAP frontend
X D Run expert rulesets for secondary data determination.
7. Can you edit existing data with the open content connector (OCC)?
X True
X False

8. For which purpose can you use the phrase import and export?
X A For initial filling of an SAP system.
X B For backup reasons.
X C Transporting phrase data from one system to another one (for example, due to
system renewal).
9. How can you access the exported phrase data?

X A File share of the application server.
X B It will be sent automatically by e-mail.
X C Via FTP to the application server.
10. From which parts does a complete report exist of?

X A a .DAT file
X B a. .BAK file
X C a .DOC file
X D an .XLS file

UNIT 5 Windows Word
Processor Integration
and Expert Server Set
Up
Lesson 1
Installing Expert Server 121
Lesson 2
Installing Windows Word Processor Integration 126
Lesson 3
Configuring Windows Word Processor Integration 141
UNIT OBJECTIVES
Set up the EH&S Expert Server
Install Windows Word Processor Integration (WWI) software
Set up report templates
Set up generation variants
Apply necessary graphic files to server location
Start initial report generation

Unit 5
Lesson 1
Installing Expert Server
LESSON OVERVIEW
This lesson explains the installation of the EH&S Expert Server.
LESSON OBJECTIVES
Expert Server
Figure 93: Introduction to SAP EHS Expert
With EHS Management Expert, you can derive secondary data for existing specification data
using rule sets. Classification samples which can be derived by the SAP EHS Management
Expert from existing specification data and written into the specification database:
OSHA (Occupational Safety and Health Administration)
SARA (Superfund Amendments Reauthorization Act)
European Classifications

Unit 5: Windows Word Processor Integration and Expert Server Set Up
Expert Example Europe
Figure 94: Expert Example Europe
This slide shows an Expert example for Europe.
Components of EHS Management Expert
EHS Management Expert Server

The application of rules to existing EHS Management data derives new data, which is
transferred back to the EHS Management substance database.
EHS Management Expert Rules and Rule Sets
Rules are based on facts which can be defined. Facts are linked to EHS Management
data, for example characteristics, identifiers, usage, and validity area. EHS Management
Expert rules are processed quickly and effectively in the rules editor of EHS Management
Expert. Individual rules are combined to form sets of rules.
Expert Example U.S.
Figure 95: Expert Example U.S.

Lesson: Installing Expert Server
Mapping tables
Mapping tables are necessary to assign the facts used by rules to EHS Management
fields and to assign the internal phrase keys to the phrases used in EHS Management.
Rule Set Composition
Figure 96: Rule Set Composition
The Composition rule set determines the Standard composition from the Exact composition
based on products property.
Expert Rule Sets
Table 5: Examples of SAP AG Cleo (Clear language for expressing orders) rule sets
Composition Standard composition
Hazard Comp EU Hazardous ingredients, components with oc-
cupational exposure limits
Hazard Comp U.S. Hazardous ingredients, components with oc-
cupational exposure limits, California PROP
65, Carcinogens
DAPEC Labeling, hazardous substance rating, haz-
ard inducing components (according to ac-
tual EU directive)
GHS-EU GHS-labeling and GHS-classification accord-
ing to the CLP regulation
OSHA OSHA classification, SARA classification
DangGoods Dangerous goods classification -…

The Composition rule set calculates the standard composition of a substance, meaning, the
lowest level components are determined. There are no regulations for this rule set. Standard
composition is used as input for most rule sets (for example DAPEC, OSHA).
The Hazard Comp rule set determines the hazardous ingredients and substances with
occupational exposure limits (OELs) . Regarding the substances with OELs, one data record is
created for each country due to the different regulations.
The DAPEC rule set classifies preparations in accordance with EU Directive 2001/60/EC.
The GHS-EU rule set classifies preparations in accordance with CLP regulation.
The OSHA rule set classifies substances in accordance with the Hazard Communication
Standard (29 CFR 1910.1200). In addition, the SARA classification is also provided.
The DangGoods rule set determines the dangerous goods classification of a substance for
ADR, IATA_C, IATA_P, and so on. Other physical-chemical properties and hazard inducers are
determined also.
Detailed information about the rule sets is provided in their functional description.
Other rule sets are available in addition to the ones mentioned already.
Expert Tools
Tools:
- Expert
Process
Set up RFC destination
Set up Expert Server
Install rules
Set up Customizing
Set up Windows services
Check mapping (phrases)

- Objects
Specifications
You can use the expert server for secondary data determination or mass data changing. Using
special rules primary data can be converted into secondary data of the specification. The
determination of the appropriate R- and S-phrases can be calculated from the flashpoint of
the specification.
The necessary customizing activity is: In IMG , choose Environment, Health and Safety ->
Basic data and tools -> tools -> Environment, Health and Safety Expert .
You can find more information on the EH&S Easy Expert tool in the SAP Help portal.
To Install Expert Server Software

You can find the installation program for EH&S Expert on the current SAP Server
Components CD. More detailed information is available in Customizing (choose Environment,
Health & Safety -> Basic Data and Tools -> Tools -> EH&S Expert ).

Lesson: Installing Expert Server
1. Execute the installation program and follow the user instructions.
For the installation of the EH&S Expert Server, choose the setup type Expert Server.
For the installation of the EH&S Expert Rule Editor, choose the setup type Rule Editor.
If you want to install the EH&S Expert Server and the Rule Editor on the same PC for
test purposes, choose the setup type Server & Rule Editor.
Make sure to enter the correct data when the system prompts for the version of the EH&S
module. Otherwise problems may occur when you work with EH&S Expert.
Note:
During installation, a dialog box appears that contains icons with the links to
the programs Expert Rule Editor ( RuleEdit.exe ), Expert Server
( EhsExper.exe ), Expert Admin ( ExpAdmin.exe ), and Remove EH&S
Expert, depending on the setup type you chose. You can copy these icons to
your desktop using drag and drop.
When you have installed EH&S Expert successfully, a directory is created

on your PC with the name that you specified during installation (default
name: C:\Program Files\EHS\Expert ) and that contains all the
relevant subdirectories and files.
The subdirectory RULESis the default directory for your sets of rules and
already contains sample sets of rules.
The subdirectory LOGis used to store log files for EH&S Expert if the log
creation is activated.
The subdirectory BIN contains executable programs.
To Customize for Expert Server Software

Use the detailed information in Customizing for Expert Server Software.
1. Access the information. In Customizing, choose Environment, Health and Safety -> Basic
Data and Tools -> Tools -> Import and Export -> Basic Settings for Import and Export ->
File Names and File Paths -> Platform-Independent File Names .
LESSON SUMMARY

Unit 5
Lesson 2
Installing Windows Word Processor Integration
LESSON OVERVIEW
This lesson explains the installation of the Windows Word Processor Integration software.
LESSON OBJECTIVES
Windows Word Processor Integration Server
Figure 97: Set Up the WWI Generation Server: Process
The purpose of installing the WWI generation server is to generate reports eventually.

Lesson: Installing Windows Word Processor Integration
WWI Installations
Figure 98: WWI Installations
Reports are generated on the WWI server.

Raw reports can be generated for test purposes on the frontend.
Templates are edited on the frontend.
For more information on the WWI: License key for generation server , see SAP Note 513330.
For more information about the actual version of WEH&S WWI and EH&S Expert , see SAP
Note 568302.
To download, in the SAP Software Download Center , choose Support Packages and Patches -
> Search for Support Packages and Patches . Enter WWI, then choose the Search button.
Make your choice.
Generate Report Symbols and Edit Symbols
Specify SAP R/3 tables for report symbol generation
Create report symbols
Check and specify report symbols
Specify report symbol groups
Specify SAP R/3 tables for report symbol generation

In this step, you specify for which SAP R/3 tables located in other SAP R/3 applications
(not SAP EHS Management) you want to generate symbols. Furthermore, you specify for
which fields of the respective tables symbols are to be generated.
Create report symbols

Standard settings:

Symbols are not shipped because classes and characteristics can vary.
Activities:
In the SAP EHS Management Product Safety menu, in the menu choose Tools ->
Match up master data . Select the Generate symbols checkbox and choose Execute .
Check and specify report symbols

The section describes the manual maintenance of symbols.
Specify report symbol groups

There are two function modules for each symbol group:
1. The first function module is used for symbol expansion within value file generation.
2. The second function module is used for default parameter determination of symbol
groups, which were defined for symbols of the category parameter. Default
parameters can be determined for report symbol groups 04 and upwards. Report
symbol groups 01 - 03 may not be changed.
Specify parameter objects

In this IMG activity you specify parameter objects. They are then available in the IMG
activity Specify parameter hierarchies for the definition of structural dependencies
between the parameter objects.
Report Symbols
Figure 99: Report Symbols
Report Symbols are primarily generated (in each client) and only in some special cases, such
as the attachment of resolve methods, it is necessary to create and edit symbols manually.
It is easy to recognize the meaning of a symbol from it‘s structure.

Caution:
Symbols from customer characteristics are generated according to different
rules. In the case of name identity the symbols are numbered in sequence. For
this reason, transport customer symbols from the development system to the
productive system. Otherwise the customer symbols in the development system
may belong to another characteristic than the same customer symbols in the
productive system.
Generate Report Symbols

Transaction CGCZ: Generation of symbols with master data matchup:
Generate symbols
Regenerate symbol descriptions
Match up symbol-phrase-related characteristics
When should a generation be executed?
Initial:
After the setup of SAP EHS Management or after adoption of database structure
Delta:
Always when new customer-specific characteristics are created
Delta:
Always when a characteristic is switched from non-phrased to phrased or the other way
round (match up symbol-phrase-related characteristics).
None:
In a production system when customer-specific characteristics are in use. In that case

it is better to transport the symbol customizing table into the production system.
Report Template and Final Report

Figure 100: Report Template and Final Report
Symbols from customer characteristics are generated according to different rules. In the case
of name identity the symbols are numbered in sequence. For this reason it is recommended
to transport customer symbols from the development system to the productive system.
Otherwise the customer symbols in the development system may belong to another
characteristic than the same customer symbols in the productive system. Templates can
contain placeholders for values from the SAP EHS Management database or other SAP R/3
modules. Different symbols connect the template to SAP R/3 data. Make sure that you define
templates in a way that they are language-independent.

Report Generation III: Generating Reports
Figure 101: Report Generation III: Generating Reports
With the report generation variant (RGV), the report is generated directly for a substance and
a key date in a specific language. The generation is done by the WWI generation server. The
symbols are then expanded. This means that they are replaced by data from the EHS
Management specification database, phrases or from other SAP R/3 components.
Values are selected using a symbol list containing all symbols in the template, and by the
RGV, the language, and the key date.
The generated report is stored as an rtf document (rtf = rich text format). Test reports are not
stored in the SAP R/3 once they have been created.

WWI Generation Server: Generation Process
Figure 102: WWI Generation Server: Generation Process
The report generation is done by the WWI Generation Server.
To Install Windows Word Processor Integration

Install and set up a WWI frontend PC for editing templates:
1. Installation of WWI (local) for editing templates
2. Installation of a generation server
3. Removal of the new WWI server
4. Set up the generation server as a job
5. Set up the job EHS start
1. Installation and setup of a WWI frontend PC for editing templates. In the directory C:
\wwi_schulung , start the file EHSWWI32_****_********.EXE . During your installation,
enter the following data:
Type of setup Workstation for editing report templates
Version SAP R/3 Enterprise 47x200/ SAP ERP
2004/2005
Installation type Install WWI locally
Destination folder D:\wwi

Note:
For installing WWI, you need authorization for local administration.
Adjust the settings in MS Word. In the Options , change the following data:
Storage place
Templates for workgroups C:\wwi
Safety
Macro Safety Low
Restart your PC and test your installation.

a) Start your Windows Explorer and navigate into the directory D:\wwi_schulung .
b) Start the program EHSWWI32_****_********.EXE by double-click. The trainer

provides the newest available version.
c) During the installation, enter the data as described in the exercise.
d) Confirm the information given by the install guide and wait for the install guide finishing
the installation.
e) Start MS-Word. Choose the menu Settings/Options/Storage place . Enter path c:

\wwi in register file storage as templates for work groups
f) Choose Settings/Options/Safety . Choose the Macro Safety button. Change the

priority to Low .
g) Restart your computer.
h) To test your installation, log on to the SAP system. Start transaction CG02. Choose
Find substance (left frame).
i) In the Specification field, enter P182.I n the menu, choose Specification -> Report ->
Report from template .
j) Choose generation variant MSDS_DE1.
k) Choose the Display button. As result you should see MS-Word starting, and you see a
MSDS filled up with data from specification P182.
2. Install and setup of a WWI generation server and test of the installation. In the directory C:
\wwi_schulung , start the file EHSWWI32_****_********.EXE . During your installation,
enter the following data:
Type of setup Install Generation Server
Version SAP R/3 Enterprise 47x200/ SAP ERP
2004/2005
Use job management no
Destination Folder D:\WWI_## (## = your group number)

Note:
For installing WWI you need authorization for local administration. Your front-
end PC might not be the generation server.
Note:
The paths for installing the server are mandatory, as they are related to
settings in the cross-client-customizing, which cannot be changed. In other
system you are free to chose the paths and entries as long as they are
corresponding.
To adjust your MS Word settings, enter the following data:

Storage place
Templates for workgroups D:\WWI_##
Safety
Macro safety Low
a) Start your Windows Explorer and navigate into the directory D:\wwi_schulung .
b) Start program EHSWWI32_****_********.EXE by double-click
c) Follow the instructions given by the install guide and enter the data as described.
Choose the option 10 days free .
d) Confirm the information given by the install guide and wait for the install guide finishing
the installation.
e) Apply changes to saprfc.ini ., path: D:\WWI\_## * . Open saprfc.ini and add your SAP
system information a shown in the example earlier. The following system information
is valid for the system EH3 in case you access the system from the TechniData
network.

Figure 103: SAP Logon Change Entries
f) Start MS Word and choose the menu Settings/Options/Storage place .
g) Enter the path D:\WWI_## * in register file storage as templates for work groups.
h) Choose Settings/Options/Safety . Choose the Macro Safety button and change the
priority to “ low” . Close MS Word.
i) Administration of RFC connections to the generation server (The following data are
available. These are cross-client settings):
a) Log on to the SAP system.
b) Choose transaction SM59.
c) Expand the TCP/IP connections.
d) Define the RFC connection. Enter the entries as given in the saprfc.ini of the
generation server.
Example section of saprfc.ini:
.......
/* this entry points to TCP/IP-Destination WWI_GENPC1*/
[PC1]
DEST= EHS_SERVER_EH3_TRAIN##.... (*1)
PROGID= EHS_SERVER_EH3_TRAIN##.... (*2)
TYPE=R
GWHOST=/H/e07.alias/S/3269/H/marley.prod-technidata.local
GWSERV=sapgw00
......

a) Put the cursor on the tree node TCP/IP connections in SM59.
b) Choose the Create button.
c) In the input field RFC destination , enter the name of the destination, which is
written down in file saprfc.ini on the generation server (in example: (*1) ).
d) In the input field Connection type , enter the value T ( TCP/IP connection).
e) Press ENTER.
f) Choose the Registration button.
g) In the input field Program ID, enter the value which is written down in the saprfc.ini
file on the generation server (in example: ( *2 ) ).
h) Save your entries.
Note:
For better clearness and traceability we recommend to name both entries
in the same way, but this is not mandatory.
Start of generation server:
Navigate to the directory D:\WWI_## and start the server by double clicking the file
Wwistart.exe . 2 DOS-boxes appear and you receive the message:
EHS_SERVER_EH3_TRAIN## successfully started.
j) Define the generation server (The following data are available. These are cross-client
settings): In the IMG , choose Environment, Health & Safety -> Basic data and Tools ->
Report definition -> Windows Wordprocessor Integration (WWI) -> Setup of generation-
PCs -> Setup of Generation servers -> Manual setup of generation servers -> Specify
Generation Servers .
a) Choose the New Entries pushbutton.
b) In the WWISV field, enter SVTR## .
c) Enter the name of the RFC-connection you have created previously. In example
( *1 ).
d) In the WWI-root field, enter the working directory: D:\WWI_## * .
e) Add a description, for example Genserver Training ## (local PC) .
f) Do not select the WWI active checkbox.
g) Save your entries.
k) Define the WWI destinations. In the IMG, choose Environment, Health & Safety -> Basic
data and Tools -> Report definition -> Windows Wordprocessor Integration (WWI) ->
Setup of generation-PCs -> Setup of Generation servers -> Manual setup of generation
servers -> Check WWI destinations and assign generation server .

a) Copy the destination DEST1 delivered by standard. Change the input field WWI
dest. to SVTR## .
b) Select the line on change to “ Assignment of WWI Server to the WWI Destination” .
c) In the Windows printer field, enter Standard .
d) Save your entries.
l) Activate the servers and schedule the dispatcher job.
a) Call transaction SE38 .
b) Execute the report RC1WWIDS(no feedback occurs).
c) Exit without saving.
d) Call transaction CG5Z(WWI Monitor).
e) Position the cursor on the name of the server of the current client (for example
061).
f) In the menu, choose Utilities -> Activate server .
Note:
The setup of jobs by report RC1WWIDSmay last a few minutes. During
this process, you see no information of client assignment to your WWI
generation server in CG5Z.
m) Test the installation.
a) Call transaction CG02.
b) Select specification P182 .
c) In the menu, choose Specification -> Report -> Create report .
d) Choose generation variant MSDS_DE1.
e) Choose the Create Report button.
The expecatation is that on your PC MS Word starts and the report is generated. You
receive the message: “ 1 report created” .
a) Call transaction CG50.
b) Search for your specification P182 and check the new report.
3. Removal of the new WWI server.
4. Set-up the generation server as a job.
Logon on to the generation server with administration authorization.
Start the program SvcAdmin.exe in WWI directory.
Choose Install a service .
Enter data.

a) Start your Windows Explorer and navigate to directory D:\WWI_## .
b) Execute the file SvcAdmin.exe . Choose the option Install a service . Enter the following
data:
General
Parameter Entry
Host Name of your front end PC

Name Well-defined internal name of the job, for
example wwi_serv_## (max. 256 char-
acters).
Display Name Arbitrary name, (max. 256 characters),
for example WWI generation server .
Executable Path Path to file: WwiSvc.exe , for example: D:

\wwi\wwisvc.exe . It is possible to in-
stall several jobs using the same
wwisvc.exe .
Service Arguments Enter destination and trace level of WWI
generation servers. Syntax is defined as:
-D<Destination> -T<Level> ,
for example
DDEST_GENSV1 -T2
The destination in our example is
DEST_GENSV1.
The trace level (TLEVEL) may be selected

from 0 (minimum) to 5 (maximum). This
controls the joblog during the generation.
Service Attributes. Deactivate the option Allow Service to interact with desktop .
Parameter Entry
Service type Choose Own Process .

Start type Choose Automatically to start the job au-
tomatically with every restart of the PC.
Error control Choose Normal .
Event logging
a) Activate Use Windows event logging .
b) Choose the option Application Logfile as logfile as well as the event types
Information , Warning , and Error .

c) Parameter Message files : Add path to program file WwiSvc.exe of the job, for
example D:\WWI_##\wwisvc.exe .
d) To install, choose OK .
c) Restart your computer and check if the job is started. Start SvcAdmin.exe and select
the option Control and configure services . Your job should have the status Started .
5. Setup and monitor the job “ EHS Start” .
Logon on to the generation server with administration authorization.
Start the program SvcAdmin.exe in the WWI directory.
Choose the option Install a service .
Enter data.
a) Start your Windows explorer and navigate to directory D:\WWI_## *.
b) Execute the file SvcAdmin.exe . Choose the option Install a service . Enter the following
data:
Parameter Entry
Host Name of the front end PC

Name for example EHS Start
Display name for example EH&S Failure Recovery
Executable path WWI - or Expert Bin directory \Ehs-

Start.exe
Service Arguments Entry
User Account Local system

Service Type Own process
Desktop Interaction No
Start type Automatically
Error Control Normal
Event logging Entry
Service Dependency Event log (automatically generated)

Use event logging Yes
Event logfile
Event types

Event logging Entry
Message files WWI - or Expert Bin directory

\Win32Svc.dll
WWI - or Expert Bin directory \Ehs-

Start.exe
c) Monitor the WWI generation server. Prerequisite: EhsStart.exe is already configured as

a job.
d) Execute the service management program SvcAdmin.exe from the directory bin of the
WWI.
a) Select the function Control and configure services .
b) Select the WWI generation server job , which you have created in the previous step.
c) To have a dialog, choose Options .
d) Choose the Service Attributes tab page.
e) Set parameter start type to the Manually option.
f) To add your internal job name (for example EhsStart ), choose Add Dependency to
the dialog Service Dependency .
g) To confirm your changes, choose OK .
e) Test the jobs. Stop the job EhsStart and your monitoring job (created in previous
step). Start the job EhsStart. After a few seconds EHSStart should start all the
dependent jobs and monitor them.
LESSON SUMMARY

Unit 5
Lesson 3
Configuring Windows Word Processor
Integration
LESSON OVERVIEW
This lesson explains the configuration of the Windows Word Processor Integration.
LESSON OBJECTIVES
Purpose of Report Templates
Figure 104: Report Template and Final Report
Templates in most cases contain placeholders for values from the SAP EHS Management
database or other SAP R/3 modules. Different symbols connect the template to SAP R/3
data. Define templates in such a way that they are not language-dependent.

Settings in Document Management
Table 6: Document types

SBV Substance report template (report template)
SBR Substance report - draft (report body)
SBE Substance report - final version (final report)
DBV Cover sheet template
DBE Cover sheet - final version
EBV Acknowledgement of receipt - template
EBE Acknowledgement of receipt - final version
IBD Inbound document
SBV
A report template uses various symbols to define the layout of your report. In
combination with the RGV (report generation variant), it allows you to generate report
bodies and final reports.
SBR
The report body is generated for a specific substance using the released report template
in which the symbols are replaced by substance data.
SBE
The final report is based on a released report body and is completed by data from other
SAP components during report shipping in another generation step.
DBV
The cover sheet template uses various symbol types to define the layout of a cover sheet,
for example a letter accompanying the report.
DBE
The final version of the cover sheet is generated directly from a released cover sheet
template.
EBV/EBE
Such as for the cover sheet template, you can define acknowledgement of receipt
templates that are used to create the acknowledgement of receipt.
IBD
Inbound documents are documents from external systems, which have been imported
into SAP DMS.
To Set Up and Adopt Report Templates

Create a new report template and edit in WWI. Check storage functions within WWI.
1. Create a new report template in English language. Enter the description in another
language of your choice as well.

Lesson: Configuring Windows Word Processor Integration
a) On the SAP Easy Accessscreen, choose Logistics -> Environment, Health and Safety ->
Basic Data and Tools -> Report Definition -> Edit Report Templates (transaction CG42).
b) To create a new template, choose ( Create ).
c) Enter data for:

Field name
Template/version
Language
Description
Save your entries.
d) To maintain data for another language, choose Goto -> Description in the menu.
Save your entries.
2. Check storage functions within WWI.

a) To edit the report template, choose Goto -> Document in the menu.
b) Close the editing process with Cancel :
Enter a couple of characters in the document.
Choose the Save button in the toolbar.
A screen appears with the message Document was not checked since the last
change appears. Choose the Cancel pushbutton in this step.
c) Close the editing process with Only Save .
Enter a couple of characters in the document.
Choose the Save button in the toolbar.
A screen appears with the message Document was not checked since the last
change appears. Choose the Only Save pushbutton in this step.
Choose ( Back ) to view the hit list with report templates.
d) Repeat the previous steps. Close the editing process with Save .
e) Summary of the status:

Pushbutton Status
Cancel SW – Start of work (only if the report

template has just been created newly,
otherwise IW – In Work). The report tem-
plate can be maintained without any in-
terruption.
Only Save UB - Unknown

Pushbutton Status
Check IW – In Work
3. Create a new report generation variant (RGV).

a) Open the screen Edit Generation Variant: Initial Screen . On the SAP Easy Access
screen, choose Logistics -> Environment, Health and Safety -> Basic Data and Tools ->
Report Definition -> Edit Generation Variants (transaction CG2B).
b) To create a new RGV, choose ( Create ). Complete the data on this screen.
c) To enter a description, choose the (Description) button. Enter a description in

English and in other languages if required.
d) To enter ratings, choose the Rating/Validity pushbutton.
e) Choose the Application Objects pushbutton. The table is empty. This is correct.
Note:
The table is filled automatically when the corresponding symbols will be
used in the assigned report template, for example:
Report application
MATMASTER material master

SUBMASTER substance master
f) Save your report generation variant.
4. Adjust settings in Microsoft (MS) Word and WWI. Create a hit list with your report
template and open it. In MS Word check if the following settings are available:
Formatting marks -> All select
Show -> Field codes select
Correct the settings in case the options Codes have not been selected and in section
Formatting marks the option All is selected.
Check the WWI settings. Make sure that you enter settings on the following tab pages:
General
- Visible names
- Color settings
- Settings for descriptors
Wizard

- Table Options
- Frame for Header
- Frame for Data Lines
- Style
Preview
- Preview
a) Open the screen Edit Report Template: Initial Screen . On the SAP Easy Accessscreen,
choose Logistics -> Environment, Health and Safety -> Basic Data and Tools -> Report
Definition -> Edit Report Templates (transaction CG42).
b) To generate a hit list with your report, choose ( Hit list ).
c) To open the template, select it from the hit list. In the menu, choose Goto ->
Document .
d) Check the settings in MS Word. Open MS Word and choose Tools -> Options ... Check
the options as described.
e) Check the WWI settings. In your report template, choose Utilities -> WWI Settings .
Make sure that you make settings as described .
f) .To save your entries, do choose the Save pushbutton.
Caution:
Do not choose the Save as Default pushbutton!
You would overwrite the default settings in the EHS Customizing.
Remain on this screen for the next step.
5. Generate a test report. Check the preset values and choose the Display button. Go back to
the report template.
a) To generate the report, choose Document -> Start Preview .
b) Enter new or check existing data for:

Preview
Generation variant
Specification
Choose the Display button. You access the dialogue window Display Report Template:
Preview . Check the displayed report.
c) To go back to the report template, choose Goto -> Switch to Template .

Note:
If you want to switch to the test report (not changed) starting from the
report template, choose the Switch to Preview button.
If you want to generate a current test report with a changed report

template, choose Document -> Start Preview again.
Purpose of Generation Variants
Figure 105: Report Generation Variant
Report generation variant

The report generation variant (RGV) is the link between a report template, and a validity
area and one or more ratings. In addition to the leading validity area, other discrete
validity areas can be specified if the resulting document is intended for a number of
combinations of validity area and language.

Generation 1
Figure 106: Generation 1
Together with the RGV, the report is generated directly for a substance and a key date in a
specific language. The generation is done by the WWI generation server. The symbols are
then expanded: This means that they are replaced by data from the EHS Management
specification database, by phrases, or by data from other SAP components.
RGV, the language and the key date.
Test reports are not stored in the DMS after having been created.
Trigger Reports
Figure 107: Trigger Reports

You can trigger a report from a hit list in the Specification Workbench (transaction CG02BD).
You can create a new report, or create a report using a report template.
To Set up Generation Variants

Navigate to the transaction “Edit Generation Variant: Initial Screen” to edit RGVs or to create
a new one.
1. Create a new RGV. Enter a description and ratings.

a) On the SAP Easy Accessscreen, choose Logisticts -> Environment, Health and Safety -
> Basic Data and Tools -> Report Definition -> Edit Generation Variants (transaction
CG2B).
b) To create a new RGV, enter data for:

Field name
Generation variant
Report category
Template/version
Status check
Validity area
Usage check
Generate manual requests automatically
Change Marks
Initial release status
Version requirement
Set historical automatically
Date format
Decimal display
Press ENTER.
c) To enter descriptions, choose the Description button. Choose first English as language,
then any other language and enter data.
d) To enter ratings, choose the Rating/Validity pushbutton. Enter data.
e) Choose the Application Objects pushbutton. The table is empty. This is correct.

Note:
The table is filled automatically when the corresponding symbols will be
used in the assigned report template, for example:
Report Application
MATMASTER Material master
SUBMASTER Substance master data
f) Save your RGV.
Graphic Files in the Windows Word Processor Integration system
Graphics on Server and Frontend

For all kind of report generation with WWI keep in mind that there are always at least two
kinds of WWI installations:
Local on frontend: For editing templates / create reports from template (Installation
directory available via Microsoft Explorer)
WWI-Server-Instances: Generate raw-/final-reports (Installation directory available for

Admins and via CGSADM)
Note:
Both are complete installations. They have all graphics stored in the installation
directory. This is necessary for the report creation.

WWI Installation: Directories on Workstation
Figure 108: WWI Installation: Directories on Workstation
The folders shown on the slide are created after the installation of WWI under the folder WWI.
The TEMPfolder is generally located on the C drive.
To Apply Necessary Graphic Files to Server Location
WWI-Installations: Adapt path for graphic files

Change of wwi.ini
Enter path to WWI-directory in [Paths] as GUI-HOME
Local for example: c:\wwi
Central for example: GUI-HOME=\\Fileserver\WWI or GUI-HOME=Z:\WWI
To set up the path for the directories GRAPHICS and LANG, enter the following data:
1. For local WWI installation:

a) Open the WWI.INI file on your front-end PC under the WWI installation directory (for
example, C:\WWI ).
b) Enter the WWI installation directory as the GUI-HOME under [Paths], for example,
GUI-HOME=C:\WWI .
c) If the graphics are located in a different subdirectory, you can enter the name of the
subdirectory under an additional entry, for example, GRAPHICS=MYGRAPHICS.
2. For central WWI installation:

a) Open the WWI.INI file on the file server under the WWI installation directory (for
example, C:\WWI ).
b) Enter under [Paths] as the GUI-HOME the path via which the respective front-end PCs
reference the WWI installation. For example: GUI-HOME=Z:\WWI or enter the file
server, for example, GUI-HOME=\\Fileserver\WWI .
c) If the graphics are located in a different subdirectory, you can enter its name under an
additional entry, for example, GRAPHICS=MYGRAPHICS.
Initial Start of Report Generation
Figure 109: Trigger a Report
The report generation starts in the Substance Workbench . Successfully created reports can
be stored in a DMS (document management system).

Report Generation (not) Successful
Figure 110: Report Generation (not) Successful
Report generation might fail for the following reasons:
Hardware issues (System error or generation failed)
Database errors (Generation with warning)
For report generation with warning you can still decide, if you want to release the report.
To Start Initial Report Generation

Choose the Substance Workbench and make the required settings.
1. Open the Substance Workbench . On the SAP Easy Accessscreen, choose transaction
CG02.
2. Create a hit list.
3. Select one or more specifications.
4. In the menu, choose Specification -> Report -> Create reports .
5. In the pop window, make settings as required.

The WWI Monitor
Figure 111: WWI Monitor
The WWI monitor allows report generation to be tracked on the WWI server. You find this
transaction under Basic Data , then Tools . On the monitor, you can track the following:
List of all jobs (new/in process/generated)
List of servers (active/busy/inactive)
Test connection to the server (RFC)
Reporting
Overview Reporting
Figure 112: Overview Reporting
Reporting helps you to perform tasks in the following areas:
Maintain specification data:

- Display reports for test purposes.

- Trigger the creation of reports.
Release and version report bodies:

- Check, accept, or reject reports
Display and send released report bodies

- Trigger report shipping
- Display reports
Check shipping orders for financial reports

- Check shipping orders and, for example release them
- Check who receives which report about which material and when
Search Screen
Figure 113: Search Screen for Reports
The search screen for reports offers various search options, such as report category or report
language.

Figure 114: Search Screen for Reports - Details
Display of Reports
Figure 115: Display of Reports: Substance Related Report Tree
The reports shown in the report tree can now be edited.

Figure 116: Display of Reports: Material Related Report Tree
It is also possible to display reports related to a material, a work area, or other application
objects.
Report Management
Figure 117: Report Management - Overview Activities
These transactions lead you through the individual work steps required to manage reports
from report generation to report release. You can see the reports in a hierarchical tree
structure.

Reports without references to a specification do not appear in report management. They are
handled as released reports after the assignment of a generation variant to the report
template and appear directly in the report information system.
Together with the RGV, the report is generated directly for a substance and a key date in a
specific language. The generation is done by the WWI generation server. The symbols are
then expanded, that means they are replaced by data from the EHS Management
specification database, by phrases or by data from other SAP R/3 components.
RGV, the language and the key date.
Test reports are not stored in the system after having been created.

Figure 120: Report Body - Validation
The work list contains all report requests that have been created manually and those that
have been automatically triggered by the system due to changes. They can be edited in report
management.
After successful generation the report has the status Generation Successful (GS) and can
then be further processed in report management.
The report has the status Generated with Warning (GW) if, for example, not all phrase
symbols are available in the required language when the report is generated or a position
frame is too small for the text despite dynamic text sizing. You can still process the report
further.
Note:
Automatic work list generation can only function, if at least one report has already
been created manually for a report generation variant (RGV) for a selected
specification in a selected language.

Figure 121: Report Body - Release
The statuses GS and CO are predefined by the system with release. Any other release status
in between can be freely defined.
The number and sequence of the individual release status depend on how many checkpoints
(toxicologist/dangerous goods officer) have to be passed through. You can bypass the
release process using the initial status after generation. The initial status is defined in the RGV
and specifies the first release status after the worklist.
After the report has been released for the last time, it has the status Completed (CO) and can
now have a version assigned. As long as a report is not released and versioned a new report
replaces the older one.
Figure 122: Report Body - Versioning
Specify, whether a report is to be assigned versions or not. The versioning indicator is an

attribute of the RGV and therefore applies to all reports which are created from the RGVs. If
versioning is not necessary, the current report version remains at 1.0. New reports replace old
ones.

When reports require versioning, each new report version is assigned a unique version
number (main version and sub-version); gaps in the main version numbering are not
permitted.
The number of the main version is incremented, when a relevant change has been made to a
specification. The relevancy indicator for the usage is then included in the report header. The
subversion is set to 0.
If a change in the specification was not relevant, only the sub-version is incremented, the main
version remains unchanged. Changes to phrases are always non relevant changes.
If in versioning the system discovers that a previous version of the new report does not exist,
it is possible to assign a start version. This start version can be used to enable you to start
numbering with a specific report version following the replacement of legacy systems.
The version numbers can be printed on the report using the appropriate symbols.
Figure 123: Report Body - Setting to Historical
Only those reports with a key date in the past can be set to historical. Once a report has been
set to Historical , it cannot be reset to Released status.
Figure 124: Report Information System

LESSON SUMMARY

Unit 5
Learning Assessment
1. For which purpose do you use EHS Management Expert?

X A It is a necessary component of EHS Management. Without it, EHS Management

will not run!
X B It is an optional component supporting you in creating data.
X C It calculates secondary data, such as classifications from already existing facts

data (primary data), such as physical properties.
X D It creates reports out of data and templates.
2. Are there further components which are required to run EHS Management Expert Server?
X A None, it just runs out of the box.
X B I need rulesets (either own development or from SAP regulatory content) to tell
Expert Server what to do.
X C My specifications I want to process must have filled the according properties.

Either maintained manually or inherited from listed substances (LIST_SUB, for
example, also from SAP regulatory content).
3. What purpose does the Windows Word Processor Integration have?

X A It keeps my property data in the specifications up to date.
X B It is a text processing software for editing additional texts in the specification

database, similar to MS Word.
X C It generates legal relevant reports and / or labels out of existing specification data
and templates.
X D It calculates new "secondary data" such as classifications out of existing primary

data, such as physical properties.

4. How is data transferred between the WWI Server and the application server?
X A Via FTP
X B Via file share access
X C Automated emails are send, received, and processed
X D Via RFC connections
5. What else, besides the WWI software, do you need to successfully run WWI?
X A Nothing, it runs just out of the box.
X B I need to have EHS Management Expert Server up and running.
X C Properly filled specifications with the data required to appear on the report.
X D The according report templates (for example for an EU-MSDS) I want to create a
report for.
6. What purpose do report templates have?

X A They facilitate as an example how a report is expected to look like.
X B They contain the layout of a final report with placeholders for data, which will be
replaced with "live data" from the specification database for the final report.
X C Report templates will completely be replaced by the final report data.
7. What does a Report Generation Variant (RGV) contain (among other settings)?
X A Target language
X B Report template
X C Usage and profiles
X D Release status

8. Why must you store some graphics on the WWI installation directory?
X A It is necessary to use graphics referenced in phrases properly, such as R-, S-, H-,
and P- sentences symbols.
X B You want to be able to place a company logo on a report.
X C For performance reasons, locally stored phrases are easier to access. This is
optional.
9. What can cause the status "Generated with Warning" (GW)?

X A Not all phrases are available in the desired target language.
X B A text box is too small for the intended text.
X C The generation took too long.
X D Overload on the WWI server.
10. When does a report receive a new main (major) version number?
X A Can be configured completely free (implementation dependent).
X B Each month, quarter, or year (depending on the configuration).
X C When a "relevant change" is done in a specification (relevant flag is set).
X D On each generation a new version is applied.

Unit 5
1. For which purpose do you use EHS Management Expert?

X A It is a necessary component of EHS Management. Without it, EHS Management

will not run!
X B It is an optional component supporting you in creating data.
X C It calculates secondary data, such as classifications from already existing facts

data (primary data), such as physical properties.
X D It creates reports out of data and templates.
2. Are there further components which are required to run EHS Management Expert Server?
X A None, it just runs out of the box.
X B I need rulesets (either own development or from SAP regulatory content) to tell
Expert Server what to do.
X C My specifications I want to process must have filled the according properties.

Either maintained manually or inherited from listed substances (LIST_SUB, for
example, also from SAP regulatory content).
3. What purpose does the Windows Word Processor Integration have?

X A It keeps my property data in the specifications up to date.
X B It is a text processing software for editing additional texts in the specification

database, similar to MS Word.
X C It generates legal relevant reports and / or labels out of existing specification data
and templates.
X D It calculates new "secondary data" such as classifications out of existing primary

data, such as physical properties.

4. How is data transferred between the WWI Server and the application server?
X A Via FTP
X B Via file share access
X C Automated emails are send, received, and processed
X D Via RFC connections
5. What else, besides the WWI software, do you need to successfully run WWI?
X A Nothing, it runs just out of the box.
X B I need to have EHS Management Expert Server up and running.
X C Properly filled specifications with the data required to appear on the report.
X D The according report templates (for example for an EU-MSDS) I want to create a
report for.
6. What purpose do report templates have?

X A They facilitate as an example how a report is expected to look like.
X B They contain the layout of a final report with placeholders for data, which will be
replaced with "live data" from the specification database for the final report.
X C Report templates will completely be replaced by the final report data.
7. What does a Report Generation Variant (RGV) contain (among other settings)?
X A Target language
X B Report template
X C Usage and profiles
X D Release status

8. Why must you store some graphics on the WWI installation directory?
X A It is necessary to use graphics referenced in phrases properly, such as R-, S-, H-,
and P- sentences symbols.
X B You want to be able to place a company logo on a report.
X C For performance reasons, locally stored phrases are easier to access. This is
optional.
9. What can cause the status "Generated with Warning" (GW)?

X A Not all phrases are available in the desired target language.
X B A text box is too small for the intended text.
X C The generation took too long.
X D Overload on the WWI server.
10. When does a report receive a new main (major) version number?
X A Can be configured completely free (implementation dependent).
X B Each month, quarter, or year (depending on the configuration).
X C When a "relevant change" is done in a specification (relevant flag is set).
X D On each generation a new version is applied.

UNIT 6 Dangerous Goods
Lesson 1
Setting up Document Printing 169
Lesson 2
Setting Up Dangerous Goods Checks 177
UNIT OBJECTIVES
Set up document printing
Set up Dangerous Goods checks

Unit 6
Lesson 1
Setting up Document Printing
LESSON OVERVIEW
A company would like to ship a new product and has to create international transport
documents including dangerous goods data. Dangerous goods text phrases are to be printed
on the transport documents. The delivery note will be printed together with dangerous goods
data automatically
LESSON OBJECTIVES
Text Patterns
Creation of Dangerous Goods (DG) Documents
The integrated output of the DG documents within SD Sales Management occurs with the
help of SAPscript forms and the corresponding SAP print programs.
The following data can be included out on the delivery note:
Data from the delivery
Data from the DG master
DG texts (header or item level)

Unit 6: Dangerous Goods
Output Types in Sales and Distribution
Figure 125: Output Types in Sales and Distribution
The output of dangerous goods can be output on different SD documents. SAP provides the
integration for the delivery note (LD00). If DG data is required on other SD documents, then
analyze the process of output DG data on the delivery note. This information is required to
develop a customer-specific solution.
Generating Documents
Figure 126: Generating Documents
Example for delivery note in a rough overview:

Lesson: Setting up Document Printing
If a delivery note is saved, the output type LD00 is determined automatically according to
standard output determination with condition. If the condition is fulfilled, an entry is written
for the header and forwarded into table NAST. Usually the processing routine RVADDN01 is
called by a scheduled background job. If RVADDN01 is processed, then the include
RVADDN01_DG is called too. In here, the DG data is collected according to the given data.
Legal Document Requirements

Requirements on DG documents are regulatory-specific:
Document layout
Dangerous goods data content
Sequence of dangerous goods data (document header data, item-relate data)
Languages
Examples for paint:

ADR: UN1263 Paint, 3, II, (D/E)
IATA: UN1263, Paint, 3, II //…package…// PIN305
IMDG UN1263 PAINT, 3, II, EmS No. F-D, S-D
Not only legal requirements must be fulfilled but also the shippers requirements. Otherwise,
the shippers do not forward the dangerous goods.
To avoid fees make sure that the proper shipping name and the sequence of the dangerous
goods data on the document is according to the DG regulation.
In the example for IATA a mixture of DG master data and logistical data / packing data is
required. In such a case further discussion with the customer is required to implement an
acceptable solution.
Text Pattern Concept - 1
Output of the DG data with SAPscript forms:

Forms contain the layout information. Forms contain symbols, which act as placeholder for
the data.
A symbol can be linked with a formatting method (function module)
The method recognizes conditions under which data is output or not
SAPscript is the standard text processing and printing of forms. The text pattern is based on
SAPscript and supports SAPscript commands.
Use of text pattern in SAPscript forms:
Text patterns are phrases based SAPscript commands, which can be edited.
A text pattern is specific for a DG regulation.
Text patterns are stored as phrases in the DG master, which are retrieved by the SAPscript
program.

The text pattern is usually maintained in the DG classification in specification

management.
By using a profile, text patterns can be set up document-specific.
To use text patterns for specific document types, a special profile can be set up. In the IMG
activity Define Profiles for DG Text Pattern a profile is set up. With this text pattern profile you
can control which text pattern is used for output types. The assignment is done within the IMG
activity Assign Text Pattern Profile to Output Type .
A text pattern phrase determines DG data output for SD documents:
Per material
Per DG regulation
Per language
Advantage
No work on printing program/documents if DG regulation changes the requirements
Full control of DG data output by the data owner (logistics, DG experts)
A text pattern can be set up specific to document types and will be assigned by a profile
To create specific text patterns for output types, configure text pattern profiles. Afterwards
for the combination of application (for example V1 = Sales; V2 = Delivery) and output type the
text pattern profile is assigned.
Text Patterns
Figure 127: Text Patterns
A text pattern is a phrase based on SAPscript commands. It can be language-dependant. It is

set up for each regulation. A text pattern consists of symbols, texts, and control parameters.

Common Formats for Text Patterns
Format Description
* Default paragraph
/: Command
/* Comment
= Long line
These are the common formats for text patterns.
More Text Formats for Text Patterns
Format Description
/ New line
= Long line
/= Long line with line feed
( Raw line
/( Raw line with line feed
These are more defined text formats (TDFORMAT) which are not common to use.
Text Pattern Sample
Figure 128: Text Pattern Sample
The figure shows a text pattern sample.

Formatting Methods
Language-independent symbols of the text pattern are replaced by the corresponding values
of the DG master. Example:
DG class
Packing group
...
Language-dependent symbols of the text pattern are replaced by using a formatting method.
Example:
DG description (proper shipping name)
DG text pattern
...
Formatting methods can be used to overwrite values of a particular symbol respectively a

value of the DG master. For example, the phrase ID of the proper shipping name (DG
description) is saved in the DG master. The formatting method reads the phrase text for the
phrase ID and saves the Proper Shipping Name as SAPscript text in the text memory. The
corresponding SAPscript key is handed over to the print structure RDGPRINT. When the
formatting method of text pattern is processed later, the SAPscript text is read for the given
SAPscript key and the symbol for the DG description is replaced with the text.
Technology / Support for Text Pattern
Text pattern
The text pattern:
Is based on SAPscript commands
Is supported on SAPscript delivery note (LD00)
Is supported for Adobe Forms with Enhancement Pack 4
Smart forms are not officially supported, but possible. Text patterns are not integrated into
sales and transport documents. To use the text pattern concept on other SD documents,
analyze the standard delivery note:
Output type LD00
Form RVDELNOTE
Processing routine RVADDN01 -> RVADDN01_DG
Phrases in Print Reports
Overview of Dangerous Goods Texts

Dangerous Goods texts are managed as phrases.
Dangerous Goods independent standard texts are used to define and output texts that are not
related to the material/dangerous goods.

Dangerous Goods-specific texts are directly assigned to the dangerous goods master.
Dangerous Goods Independent Standard Texts - 1
Figure 129: Dangerous Goods Independent Standard Texts - 1
Independent standard texts can be printed on header level and item level:
Header level:
Phrase text printed underneath all items
Item level:
Phrase text printed underneath each item
Dangerous Goods Independent Standard Texts - 2
Output conditions can be used to print the text or not:
The output condition will be processed by a function module.
The function module is assigned to a user exit.
The user exit is linked to a phrase.
The phrase is assigned to the header or item level by phrase sets.
Special phrase sets must exist:
PAPHEAD (Document header text)
PAPPOS (Document item text
Phrase sets must be assigned to the structure RDGTPOSPSET.
Dangerous Goods: Specific Texts - 1

For Dangerous Goods specific texts, the following applies:

They are material specific, for example: Special Provision.
They are printed on item level underneath the text pattern.
They can be integrated into the text pattern.
They are maintained as Dangerous Goods user-defined text:
Note:
Dangerous goods profiles can be used to control the output. Output conditions
and formatting methods can be used.
Output Languages
Primary/Secondary languages:
DG texts are primarily output in the form language (the language used by the customer).
Customizing settings specify one or more primary languages per validity area and per
mode of transport category.
There is a further language for each validity area and for each mode of transport category.
Rule for output on the delivery note:
Form language equals primary language: ok
Form language does not equal to primary language: additional output in secondary
language
LESSON SUMMARY

Unit 6
Lesson 2
Setting Up Dangerous Goods Checks
LESSON OVERVIEW
Dangerous goods routes
Check methods
Check schemes
Checks, sales organizations, and document types
LESSON OBJECTIVES
Dangerous Goods Routes

Routes from the Dangerous Goods (DG) Points of View
A route is a prerequisite for determining the DG regulation for each country / mode of
transport combination:
Which countries are involved?
Which mode-of-transport is used per route / shipping leg?
A route is a prerequisite for processing DG checks. Without a relevant route, no DG checks

can be processed!
Setting up routes and their shipping types are original SD customizing. Involve the SD
responsible person as early as possible.
What is a Route?
A route is a course of travel between a starting point and an end point. A route connects the
point of departing and the destination. Point of departing and destination can be one of the
following:
A regional area (for example Bavaria)
A country (for example Germany)
An area (for example Europe)
A route can include several stages. The transit country table can be taken into account.
For a route, the shipping type must be maintained. If stages are assigned, then for each stage
the shipping type must be maintained.

A route which connects a point of departure and a destination can include several stages,
which can be:
Shipment leg: Connection between two points
Load transfer point: Point/location at which a shipment is transferred from one means of
transport to another
Border crossing point: Point/location at which a shipment crosses a border
A route can also connect destination areas (North America and Europe). The route can be
used as a criterion for the selection of deliveries for a shipment; therefore, it is an important
control parameter for shipments. The check methods use the route, for example, for
determining the permissibility of the transportation mode category for each validity area. The
shipment can contain the route in the shipment header for information purposes. It can be
transferred from the deliveries or entered manually. Only one route per shipment is allowed.
Routes are defined in Customizing. This definition contains information that is relevant for the
shipment, such as distance, transportation lead time, duration of trip, shipping type, and so
on. For the DG check, information about the transportation mode category per route stage is
important. The transport relevance is set in Customizing for transportation. Routes that are
not relevant for transportation are not considered in the DG check.
Determine DG Regulation - 1
Determination of departure country:
From shipping point
Determination of destination country:
Form ship-to-party
Determination of transit countries:
The transit country table is taken into account when the corresponding flag on the route is
set.
In addition if a route is defined with stages then for each stage the address of transport
connection points (location) is taken into account.
Determination the mode-of-transport used in each country:
From shipping type of header route or from shipping type of stages
The address of the shipping point and ship-to-party must be maintained. The transit country
table is a configuration table of the Dangerous Goods Management. If the transit country
table should be taken into account the corresponding flag in the header route must be set.
If the header of a route is maintained only (without stages) then the shipping type must be
set. If the route has stages then on each stage the shipping type must be maintained.
In the business process, the route is set on the header of the delivery note (manually or
automatically). If the route is missing, then the processing of DG checks results in an error
message.
Determine DG Regulation - 2
Determine all mode-of-transport / country combinations.
Determine the DG Regulation for each mode-of-transport / country combination.

Lesson: Setting Up Dangerous Goods Checks
For each combination only one DG regulation can exist!
Exxample:
Mode-of-transport = Road
Country = Germany
Combination Road / Germany -> ADR
For each mode-of-transport / country combination only one DG regulation can exist. The
process to determine the DG-regulation is as follows:
1. The shipping type is assigned to the mode-of-transport.
2. The mode-of-transport is assigned to the DG transportation mode category.
3. The DG transportation mode category is assigned to the DG regulation and the validity
area (respectively country) is assigned to the DG regulation.
Check Methods
Overview of check methods
DG checks can be executed from the order, deliver and / or from the shipment
transaction.
All check modules create an entry in the log.
Checks have the same interface for all document categories.
Integration of customer-specific check methods is possible.
Process DG checks only where necessary by using usage profiles.
Examples of Standard Check Methods
General checks HAZMAT_CHK_VARIOUS

Permissibility of transportation mode cate- HAZMAT_CHK_MOT
gory
Poisonous by inhalation HAZMAT_CHK_PIH
Initialization module DG63_CHK_INIT_HEADER
Mix loading check DG63_CHK_MLOAD
These checks can be used as templates for customer-specific checks.
Customer-specific checks must be specified and developed.
HAZMAT_CHK_VARIOUS
Check if data is complete, for example missing route or DG master exist. It is not a check
if all necessary DSG data is available! This is not the purpose of the check method and
cannot be checked because it is master data.
HAZMAT_CHK_MOT
Check if transportation mode category is approved respectively checks the flag whether
the transport is permitted or not.

HAZMAT_CHK_PIH
Check whether the hazard zone for poisonous by inhalation is set or not.
DG63_CHK_INIT_HEADER
This check is used as an initialization module for header checks.
DG63_CHK_MLOAD
Check prohibitions of mixed loading.
To Set Up Check Methods

Specify a customer-specific check method:
What has to be checked?
For which DG regulation should the check be processed?
Does the check method need logistical data for processing?
Where does the logistical data come from?
What should be the result of the check method?
What should be the message in the log?
1. Use a standard check method as a template to set up the interface properly.
2. Develop a customer-specific check method according to the specification.
3. Add the customer-specific check method to the IMG-activity Specify Dangerous Goods
Check Methods .
Check Schemes
What is a check scheme?
A check scheme combines check methods to be processed.
The sequence of the check methods within a check scheme can be defined.
For each check method in the check scheme the following applies:
A response can be defined.
The sales document can be blocked.
The save of a sales document in online modus is allowed / forbidden.
The save of a sales document by collective processing is allowed / forbidden.
To Set Up Check Schemes

Think about on which level DG checks are to be processed. It is reasonable to process every
DG check on every level (sales, delivery, shipment).
Think about if the necessary data is available to process a DG check. For example, the mixed
loading of DG is unknown on the level of the sales order, therefore to process a DG check for
mixed loading on the sales order does not make sense. Eventually this is known later on in the
process on the shipping or shipment level. Process the check on that level if reasonable.

Lesson: Setting Up Dangerous Goods Checks
What should be the result of the check method? Ínformation, a warning, or an error message.
With the message type, the SD document can be blocked.
Is there a special sales organization which handles Dangerous Goods? Then define a check
scheme for that team only. The same applies for SD document types. Are there any specific
document types in place for Dangerous Goods? If yes, then define particular check schemes
for those document types if reasonable.
Afterwards specify the check scheme in the IMG and define the results of each check method:
1. At which level should be a check processed?
2. Are all data available to process the check?
3. What should be the result of a check method?
4. Keep in mind the organizational structure / SD document types!
5. Specify the check scheme in IMG.
Checks, Sales Organizations, and Document Types

Check scheme assignment
One or multiple check schemes can be set up for sales, shipping, and shipment.
Check schemes can be specific for a sales organization.
Check schemes can be specific for document types.
The check scheme will be assigned to a sales organization and / or to SD documents.
Standard Check Processing
Figure 130: Standard Check Processing
The check can be started manually or automatically when the SD document is saved. As a
prerequisite for checks and documents, the dangerous goods indicator profile must be set.

Technical Process
Figure 131: Technical Process
The technical process of a dangerous goods checks happens also in SD document processing
and not standalone in SAP EHS.
To assign Checks to Sales Organizations and Document Types

Think about for which level check schemes were defined (sales, delivery, shipment).
What was the reason? Was it a special sales organization that handles Dangerous Goods?
Then assign the check scheme for that team only. The same applies to SD document types.
Are there any check schemes for particular SD documents? If yes, then assign the check
scheme for those document types only.
Assign the check scheme to the SD documents.
To use the check scheme in the process, assign a determination routine:
1. Check the specified check schemes and why they were implemented.
2. Think about the organizational structure / SD document types.
3. Assign check schemes to SD documents.
4. Assign a check scheme determination routine.
LESSON SUMMARY

Unit 6
Learning Assessment
1. The output of further dangerous goods-independent standard texts at header/footer and

item level is controlled by indicators set in the delivery. How can you set these indicators?
X A Only automatically (by check modules)
X B Only manually
X C Either automatically or manually
2. What is contained in a route from the Dangerous Goods perspective?

X A Total traveling costs.
X B A list of countries involved.
X C Methods of transport (train / ship / road / airplane / ...).
X D List of toll charges along the shipping legs.
3. What is a check scheme?

X A A scheme is the right management means to decide, who may execute Dangerous
Goods checks.
X B A scheme is a set of Dangerous Goods checks.
X C A scheme defines the color of warning and error messages of Dangerous Goods
checks.

Unit 6
1. The output of further dangerous goods-independent standard texts at header/footer and

item level is controlled by indicators set in the delivery. How can you set these indicators?
X A Only automatically (by check modules)
X B Only manually
X C Either automatically or manually
2. What is contained in a route from the Dangerous Goods perspective?

X A Total traveling costs.
X B A list of countries involved.
X C Methods of transport (train / ship / road / airplane / ...).
X D List of toll charges along the shipping legs.
3. What is a check scheme?

X A A scheme is the right management means to decide, who may execute Dangerous
Goods checks.
X B A scheme is a set of Dangerous Goods checks.
X C A scheme defines the color of warning and error messages of Dangerous Goods
checks.

UNIT 7 Global Label
Management
Lesson 1
Determining User Requirements 186
Lesson 2
Setting Up Standard Customizing and Configuration 194
Lesson 3
Setting up Data in the System 203
Lesson 4
Testing of Global Label Management 209
UNIT OBJECTIVES
Identify user requirements in Global Label Management (GLM)
Identify legal requirements in Global Label Management (GLM)
Set up local Windows Wordprocessor Integration on user PCs
Specify label categories, label sizes, label stock sizes, packaging units, and transfer and
check printers.
Set up data for Global Label Management
Test the installed system and data in GLM

Unit 7
Lesson 1
Determining User Requirements
LESSON OVERVIEW
This lesson explains the determination of user requirements for Global Label Management.
LESSON OBJECTIVES
Number of Users
Figure 132: Who is Involved in Labeling
The figure show the various departments which are involved in the labeling process.
Labeling Introduction - Affected Departments

If the process chain of a company is analyzed regarding labels, it is clear at an early stage that
many departments are affected. This refers also to departments which you not may think
about in first line.
Marketing
They are interested to place and publish a brand name, make the product unique on the
market, show the quality.

Lesson: Determining User Requirements
Product Stewardship
They focus on the security of the environment, the human safety, and sustainability.
R&D
They have to label samples of new products.
Warehouse Management
They need to know where the goods have to be put and will be found in the storage bin.
Production
They need to identify the produced products for further processing.
Logistics
They must provide the information for the safe transportation of the goods to the
customers.
How to Print Labels Today as User
Print labels as a user - considerations:
Without global Global Label Management (GLM), users have to print their labels from the
Substance Workbench .
Before users can print a label, they have to collect all necessary information from all parts
of EH&S, and also from other SAP applications.
You can start the specification database with transaction CG02in an SAP system.
Different Views on Labels
Views on labels:
Regulatory authorities classify labels as a critical and important component for human and
environmental safety.
Companies classify labels as a significant contribute to successfully carry out logistic

processes within the supply chain and distribution across all industries.
Two major interest groups can be identified when the purpose of a label is analyzed. Both
groups classify labels as a critical and as an important component.
Regulatory view
The human and environmental safety is here the main aim. Labels are be used to signal
safety risks and provide safety information to avoid accidents. Typical labels are for
example hazardous labels, dangerous goods labels, and storage and transportation
labels.
Company view
The company view classifies labels additionally as a significant contribution to
successfully carry out the production and logistic processes within the supply chain. The
main aim is here to assure and optimize the process flows. Typical labels are for example
storage, warehouse and transportation labels, and quality labels.

Unit 7: Global Label Management
Label Types
Figure 133: Label Types
In addition, the type of label required depends on factors such as the product to be labeled, its
physical and chemical properties, the size of the packaging, and the country of destination.
Furthermore, organizations need labels that are tailored to customer requirements. This
leads to more stringent requirements for the labels used by a company and, as a result, for all
the associated processes.
GLM supports complex labeling processes, reducing the effort required and the risks
involved. GLM is based on the EHS Management solution and is integrated seamlessly into
this system. GLM provides user support, from label planning and creation up to label
management.
The solution can be tailored for company-specific requirements. For example, companies
create all the labels they need for their production and distribution processes – covering the
areas of product innovation, engineering, design, and quality management as well as
warehousing and transport.

Country Labels Requirements
Figure 134: Country Labels Requirements
GLM supports the creation of country-specific labels for example of the same chemical
product.
GHS (Global Harmonized System of Classification and Labeling of Chemicals)
GHS has been adopted in Europe and is in the process of adoption in the United States,
Canada, and many other industrialized nations.
The goal of GHS is to create a single way to describe and classify chemical hazards on
product labels and chemical safety data sheets (SDS) used everywhere in the world.
With standardized label content based on standardized classifications, standardized

hazard statements, standardized signal words, and official graphic symbols and colors,
producers, workers, and consumers in every country will share an understanding of the
potential human health hazards posed by chemicals and other products.
Country-specific regulations: In reality there are still many country-specific regulations in use
all over the world; for example NFPA, OSHA, VOC, and WHMIS. Therefore, GLM has
automated processes to identify the correct labels, no matter in which country a product is
sent to.

Company Labeling Processes
Figure 135: Standard Approach
Every company has a clearly defined supply chain management (SCM) process flow which
starts with ordering and ends with shipment. In parallel, there is a labeling process flow which
is linked to the SCM processes. The process includes:
Label data maintenance
Label design
Validation and approval processes
(Pre) Printing of labels
Interfacing / integration into SCM processes
This kind of process is often not well structured compared to the SCM process flow. However,
the labeling process flow is an import part of the overall process in a company:
Label data is interfaced from the database systems or maintained twice in different
systems.
Validation and approval is made with much paper work and is critical when the data is
coming from different systems.
Integration into other processes requires interfaces.
Printing is processed from several stand-alone systems.

Global Label Management (GLM) Solution Approach
Figure 136: Global Label Management (GLM) Solution Approach
The approach of the GLM solutions includes all necessary labeling processes just as other
solutions. The difference is, everything is integrated in the main SAP ERP system.
The advantages of the integrated solution:
No interfaces necessary to produce labels
Duplicate data maintenance is avoided
Full central control on data and the output
Label Print Requirements
Hardware Requirements (Scenario 1)

To identify the required hardware and staff for the label printing it is important to identify the
number of labels that has to be printed per day or per hour.
Assumptions:
1.0 mio labels per month (size per label ~ 30-50kB)
10 labels per print job (1.5 mio shipments per year)
26 sites with 5 print locations (spreading 40% EU, 40% AP, 20% US)
Estimations:
1.0 mio / 30 working days = 50000 labels per day
50000 label per day / 10 labels per print job = 5000 jobs per day
5000 jobs per day / 24 h / 60 min = 3.5 Jobs per min
60 sec / 3.5 Jobs per min = 17.14 sec per Job
Measurement:

GLM needs ~ 2-3 sec within SAP
WWI needs ~ 8 sec (using report body)
Start printing first label ~ 4-5 sec
First result: One WWI generation server may handle all requests (if they are sequential).
Hardware Requirements Assumption: Concurrent Requests

Critical periods for requests are the ones where there is an overlap in timezones.
Figure 137: Hardware Requirements Assumption: Concurrent Requests
Hardware Requirements (Scenario 2)

Estimation:
5000 jobs per day / 0.4 = 2000 jobs per region EU, AP
5000 jobs per day / 0.2 = 1000 jobs per region US
(26 *5 print stations) * 0.4 = 52 print stations per region
One region handles 70% (1400) of the print jobs alone in 7 h:
1400 jobs / 52 print stations per region = 27 jobs per print station
1400 jobs per day / 7 h / 60 min = 3.3 jobs per min
60 sec / 3.3 jobs per min = 18.2 sec per job
Overlapping region 30% (600+300) print jobs in 2 h:
900 jobs per day / 2 h / 60 min = 7.5 jobs per min
60 sec / 7.5 jobs per min = 8 sec per job
Second result: One WWI Server may handle all requests (when they are sequential).

Hardware Requirements End Result
Figure 138: Hardware Requirements End Result
End result: Two WWI generation servers with three WWI services serve up to six concurrent
requests. This is sufficient. One additional server is added as a fallback solution.
LESSON SUMMARY

Unit 7
Lesson 2
Setting Up Standard Customizing and
Configuration
LESSON OVERVIEW
This lesson explains the setting up of standard customizing and configuration in Global Label
Management (GLM).
LESSON OBJECTIVES
check printers.
Local Installation of the Windows Wordprocessor Integration (WWI)
The WWI installation on a frontend PC is used to create report templates (layouts) and/or
display reports.
Microsoft Word is installed on the local computer.
The WWI installation includes all the files required for the following:
Workstation for editing report templates

- If you want to edit report templates
- As an option, use your workstation as information system PC or for labeling
Information system/labeling workstation

- If you want to only display documents in RTF format on the information system PC

Lesson: Setting Up Standard Customizing and Configuration
Print Tool GLMPT.EXE
Figure 139: Print Tool GLMPT.EXE
To print labels from a workplace PC, you need an auxiliary program.

Copy this program to a suitable directory on all the workplace PCs you want to use to print
labels. Alternatively, you can also store the program centrally in a network that can be
accessed by all workplace PCs, or make it available to download from your intranet.
Register the GLMPT.EXE program as the default program for printing labels by executing it
once on each of the workplace PCs in question.
This auxiliary program under the name GLMPT.EXE is invisible to the users, except that GLM
(Global Label Management) cannot find the required printer. In this case the user can redirect
the data stream to the right printer. The redirect can be stored within the auxiliary program,
and it can be automatically used by the program when it is needed.
Label Categories
Figure 140: Label Categories
The type of labels required depends on factors such as the product to be labeled, its physical
and chemical properties, the size of the packaging and the country of destination.
Furthermore, organizations need labels that are tailored to customer requirements. This

leads to more stringent requirements for the labels used by a company and, as a result, for all
the associated processes.
Specify Label Categories
Label Categories and Specification

Label categories - characteristics:
Label categories and their defined properties play a central role in the label determination.
The number of the label categories is the same as the number of the labels.
Define label categories: Which report categories can be used as label categories?
Label categories - specification
Prerequisites: Customizing activity Specify Report Categories was processed.
Maintain the key and the description of the label category.
For a more detailed definition of the label category set one or more of the following indicators
as required:
Contains use symbols
Contains transport symbols
Customer-specific label category
Additional determination of customer-specific labels
Generation variants without dangerous goods regulations
Specify Report Categories
You can specify report categories in Customizing.

Choose SAP EHS Management -> Product safety -> Report management -> Specify report
categories .
Use symbol
Indicates that labels of that category can contain use symbols.
If you set this indicator, then the system takes during the label determination only labels
into account which permit the printing of the appropriate symbols. This means that the
label contains a preprinted, colored area for the symbol.
TranspSymb
Indicates that labels of that category can contain transport symbols.
If you set this indicator, then the system during the label determination takes only labels
into account which permit the printing of the appropriate symbols (that means the label
contains a preprinted, colored area for the symbol.)
CusSpec.Label
When you set this indicator, the system searches for a customer-specific label or a
customer-specific report generation variant for this label category during label

determination. No other labels or report generation variants are determined for this label
category.
Dependencies:
When you set this indicator, you shall only create one entry for this label category in the
labeling specification in the material master and you may not enter a validity area, label
size, or report generation variant there.
When you set both the Customer-Specific Label Category and the Additional
Determination of Customer-Specific Labels indicator, the system only takes the
Customer-Specific Label Category indicator into account. This means that the system
searches for a customer-specific label or report generation variant for the label category
during label determination. You cannot create any more entries or enter any more data in
the labeling specification.
Det.CusSpec.Lbl
When you set this indicator, in addition to other labels or report generation variants, the
system also tries to find a customer-specific label or a customer-specific report
generation variant when it determines labels for this label category.
Dependencies:
When you set this indicator, enter a label size or a report generation variant in the entries
for this label category (for label categories that are not customer-specific as well) in the
labeling specification in the material master. You can also create several entries with
different validity areas. The data you created is used to find non-customer-specific labels
or report generation variants during label determination. In addition, the system also
uses this indicator to find customer-specific labels or report generation variants.
When you set both the Customer-specific label category and the Additional Determination
of Customer-Specific Labels indicator, the system only takes the Customer-Specific Label
Category indicator into account. This means that the system searches for a customer-
specific label or report generation variant for the label category during label
determination and you cannot create any more entries or enter any more data in the
labeling specification.
No DGReg
At the end of label determination, the system reduces the number of report generation
variants found, in the following way:
The system might find dangerous goods regulations. This means the material that is
to be labeled is relevant for dangerous goods. If so, only the report generation variants
in whose validity areas the dangerous goods regulations that were found, were
specified are used.
The system has not found any dangerous goods regulations. This means the material
to be labeled is not relevant for dangerous goods. If so, only the report generation
variants in whose validity areas no dangerous goods regulations were specified are
used.
When you set this indicator, for the label category the system only takes into account
report generation variants in whose validity areas no dangerous goods regulations were
specified. This happens irrespective of whether the system found dangerous goods
regulations during label determination or not. Thus, you no longer have to specify the
dangerous goods regulations explicitly in the corresponding report generation variants.

You can use the latter for both materials that are relevant for dangerous goods and for
the ones that are not.
Label Sizes and Label Stock Sizes
Figure 141: Label Size
The specified label sizes are available to you in the material master for describing the label
properties and to configure the label stock object. The system uses the label sizes to
determine suitable labels during label determination.
Label Properties Description
Figure 142: Label Properties Description
The label sizes can be assigned in the label data view of the material master.
Specify Label Size
Label size specification

- No prerequisites.

- With the label size, fitting labels or label stocks will be determined in the label
determination.
- The standard settings can be modified to customer-specific settings.
Lbl Width
The width is always considered to be the lower and upper edge of the label. This is based
on the assumption that you always hold the label so that you can read it.
Lbl Hght
The height is always considered to be the left or right edge of the label. This is based on
the assumption that you always hold the label so that you can read it.
UoM
Unit of measure for the width and height.
Size of Label Stock - Label on Rolls
Figure 143: Size of Label Stock - Label on Rolls
The size of label stock indicates the height and width of the label stock. The label stock is the
paper on which the label sticks on. In this example, the label stock is a paper roll.

Size of Label Stock - Label on Paper
Figure 144: Size of Label Stock - Label on Paper
In this example, the label stock is a sheet of paper.
Specify Size of Label Stock

Size of label stock specification:
- No prerequisites.
- Choose a standardized description if applicable, for example A4, and specify the height
and width measurements belonging to it as well as a unit of length.
- In this context the longer of the two sides of the label stock is always described as the
height and the shorter one as the width, irrespective of whether the stock is used in
portrait or landscape format.
SizeLblStk
The size of the label stock is calculated from its width and height. In this context, the
upper or lower edge of the paper is always described as the width and the left or right
edge as the height. This is based on the assumption that you always hold the label so that
you can read it. For size, enter a description (standardized if applicable), for example A4.
WdthLblStk
The width of the label stock refers to the shorter of the two sides, irrespective of whether
the stock is being edited in portrait or landscape format.
HghtLblStk
The height of the label stock refers to the longer of the two sides, irrespective of whether
the stock is being edited in portrait or landscape format.
UoM
Unit of measure for the width and height.

Transfer and Check Printers
Specify the printers that are to be used to print your labels.

- Prerequisites: Install the WWI generation servers first (recommended).
Two main functions:

- Transfer printers:
The existing printer and printer driver belonging to it are transferred from the
generation server.
- Check printers:
This option is used to check the table and add manually new when it is necessary.
Specify the printers:
Specify here the description of the printer along with the printer driver belonging to it.
Prerequisites:
Install the WWI generation server first so that it is possible to fill the printer table with initial
data.
Transfer Printers:
Be careful when you choose this activity and the printer table is already configured. This
activity deletes all printers from the table which are not available on the WWI generation
server (manually added entries)!
Packaging Units
Figure 145: Packaging Units
A packaging unit is a unit of measure used for packaging.
Specify Packaging Units
Packaging units specification:

- No prerequisites.

- The input help you use to specify your packaging units corresponds to the table of the
existing UoM (Units of Measurement).
- You can use the input help to choose from the ones that are available, the units of
measure that can be used as packaging units, for example bottle, carton, or pallet.
- The entries you make in this IMG activity appear as input help on the configuration tab
page in the label data view in the material master.
UoM
Internal, language-independent, measurement unit format
UoM Text
Name of unit of measurement
LESSON SUMMARY
check printers.

Unit 7
Lesson 3
Setting up Data in the System
LESSON OVERVIEW
This lesson explains the setting up of data for Global Label Management in the system.
LESSON OBJECTIVES
Label Stocks
Editing label stocks:

- In transaction CBGL_LS02you can edit label stocks. Before editing the label stock,
define in Customizing:
Label categories
Label sizes
Sizes of the label stocks

- Types of label stock:
Paper roll
Paper sheet

Specify Label Stock
Figure 146: Specify Label Stock
Label stock
The label stock is an object which plays a central role in the label determination.
At the label stock the data for the adjustment of the label on the label stock are defined
(number, pitches for each row/column, distance from edge). The label stock is assigned
to a generation variant, which has the properties maintained in the label stock (validity
area, label category, label size).

Lesson: Setting up Data in the System
Label Data in Materials Management
Figure 147: Label Data in Materials Management
The label and the number of labels are dependent on the packaging size and type. Thus for
each packaging size and type, different labels are required. Example:
1 bottle needs 1 label.
1 carton needs 1 label and contains 6 bottles.
1 pallet needs 2 labels and contains 24 cartons.
Each of this packaging unit (bottle, carton, pallet) needs another label type.
The Label Data Page in the Material Master
Figure 148: The Label Data Page in the Material Master
Make sure that you define label data separately for each packaging unit. Requirements for
label determination, defined in the material master, are the following: label category, label size
or generation variant, number of labels.

Specify Label Data in Materials Management
Requirements for label determination, defined in the material master:

- Label category
- Label size or generation variant
- Number of labels
Label Determination (Dynamic)
Figure 149: Label Determination (Dynamic)
Variant 1 (determination vial label size) is the dynamic way to determine a label.
Starting point is also the entry of a material number in the material master by the user. The
result is that the system provides the required data for the label stock, the layout (report
template), and the reports from the report information system.
Caution:
Determination via the label size is useful because the majority of changes are not
on the material side. Thus, changes only have to be done in the label stock and in
the generation variant.
Advantages of this variant:
It is a dynamic way.
If there are changes, the configuration effort is low (few places where the changes have to
be done).

Lesson: Setting up Data in the System
Label Determination (Static)
Figure 150: Label Determination (Static)
Variant 2 (determination via generation variant) is the static way to determine a label.
Starting point is the entry of a material number in the material master by the user. The result
is that the system provides the needed data for the label stock, the layout (report template),
and the reports from the report information system.
Caution:
Determination via the generation variant is in case of required changes the wrong
way, because each variant requires a manual change. If you have more than one
change, you have a high effort to make all the required changes.
Logistic Data
Starting point for the printout of labels in GLM can be a material, or a logistic process.
Table 7: Logistic Processes

Delivery Note Transaction VL0XN
Process Order Transaction CORX
Material Document Transaction MB0X
x=1 create, x=2 change, x=3 display
Table 8: Related Labeling Scenarios

Delivery Note GLM Scenario Delivery

Process Order GLM Scenarios Make-to-Stock and Make-to-

Order
Material Document GLM Scenario Goods Receipt
LESSON SUMMARY

Unit 7
Lesson 4
Testing of Global Label Management
LESSON OVERVIEW
This lesson explains how to test the installed system and data.
LESSON OBJECTIVES
Test Labels
Figure 151: GLM Print Process: Integration within SAP
The GLM (Global Label Management) print process is integrated within SAP. The following
data influences the GLM print process:
MM: Goods receipt
PP: Make-to-stock
SD: Document data

GLM Print Process: Display Determined Labels
Figure 152: GLM Print Process: Display Determined Labels
The entry of few data enables unexperienced users to determine labels and to start the GLM
printing process.
Based on the input data, labels are determined and then displayed in the generated label tree.
The label tree displays all the determined labels. To preview a label, or to print a label the
generation variant has to be called for the expected label.
After choosing the right generation variant, the user can be allowed to make some manual
user entries.
GLM Print Process: Business Process Walk Through
Figure 153: GLM Print Process: Business Process Walk Through

Lesson: Testing of Global Label Management
The business process that is the basis for the print process runs in the following steps:
1. SAP content
2. GLM labeling scenario
3. GLM label selection
4. GLM label generation
5. GLM label printout
GLM Print Process: SAP Content
Figure 154: GLM Print Process: SAP Content
SAP content which influences the GLM print process stems from the following components:
EHS Management
- Data from PS, DG
- Phrases
- Label templates
- Validity area, languages
- Regulation
Materials Management
- Packaging hierarchy
- Material data
- Label definition
Production Planning and Control

- Process data
- Batch data
GLM Print Process: Label Scenario
Figure 155: GLM Print Process: Label Scenario
Label scenarios and the production of labels are tied to different SCM (Supply Chain
Management) processes:
Production: make-to-order (MTO) and make-to-stock (MTS)
Sales and Distribution (Delivery)
Procurement (goods receipt)
Generic
Samples
Customer-specific scenarios can be added
The label scenarios require little data entry for the user: Data entry is supported:
Default values
Dropdown lists

GLM Print Process: Label Selection
Figure 156: GLM Print Process: Label Selection
The system supports your employees in label selection and label printing.
GLM Print Process: Label Generation
Figure 157: GLM Print Process: Label Generation
The label generation happens in the following steps:
1. Users access EHS Management from their workplaces.
2. EHS Management retrieves data, also from the logistics system

3. Data is sent to the WWI generation server.
4. The WWI generation server processes the data and sends it back to the EHS Management.
5. The EHS Management sends data to the workplace.
6. From the workplace, the label is printed.
GLM Print Process: Label Printout
Figure 158: GLM Print Process: Label Printout
This is a sample of a printed label.
GLM Print Process: Label Tree Overview
Figure 159: GLM Print Process: Label Tree Overview
The label tree displays the labels that were found during label determination together with the
number of labels determined in an overview tree. You can access the label tree when you
determine labels.

GLM Print Process: Label Tree Functionalities
Figure 160: GLM Print Process: Label Tree Functionalities
Label tree functionalities:
Display of the determined labels (generation variants) sorted by packaging unit
The calculated number of labels and the determined report language may be changed
manually before printing
Selection of the printer and printing of the label
Preview of the labels
Protocol of the label determination
LESSON SUMMARY

Unit 7
Learning Assessment
1. A user cannot print labels without Global Label Management.

X True
X False
2. The Global Harmonized System of Classification and Labeling of Chemicals (GHS) is

adopted only in Europe but will not be adopted in the U.S. and Canada.
X True
X False
3. The WWI (Windows Word Processor Integration) installation on a frontend PC is used to:
X A Create report templates
X B Display reports
X C Evaluate reports
X D Archive reports
4. A prerequisite to specify label categories is that the customizing activity ... has been
processed.
5. In the material master, a label data view exists.

X True
X False

6. What are the parameters to specify a label size?
7. You can create new packaging units in the material master.

X True
X False
8. Before you edit label stocks, what must you define in Customizing?
X A Only label categories
X B Only label sizes
X C Only sizes of the label stocks
X D All of the above
9. For each packaging size and type different labels are needed.
X True
X False
10. What is a requirement to call to preview a label?

Unit 7
1. A user cannot print labels without Global Label Management.

X True
X False
2. The Global Harmonized System of Classification and Labeling of Chemicals (GHS) is

adopted only in Europe but will not be adopted in the U.S. and Canada.
X True
X False
3. The WWI (Windows Word Processor Integration) installation on a frontend PC is used to:
X A Create report templates
X B Display reports
X C Evaluate reports
X D Archive reports
4. A prerequisite to specify label categories is that the customizing activity ... has been
processed.
Specify report categories
5. In the material master, a label data view exists.

X True
X False

6. What are the parameters to specify a label size?
Width (Lbl Width), Heigt (Lbl Hght), unit of measure (UoM) for width and height.
7. You can create new packaging units in the material master.

X True
X False
8. Before you edit label stocks, what must you define in Customizing?
X A Only label categories
X B Only label sizes
X C Only sizes of the label stocks
X D All of the above
9. For each packaging size and type different labels are needed.
X True
X False
10. What is a requirement to call to preview a label?
You have to call a generation variant.

UNIT 8 SAP Product and
REACH Compliance
Lesson 1
Setting Up and Customizing 221
UNIT OBJECTIVES
Set up e-mail communication
Maintain Basic settings for Discrete Industries (DI)

Unit 8
Lesson 1
Setting Up and Customizing
LESSON OVERVIEW
.
This lesson explains the setting up and customizing of e-mail communication and for discrete
industry.
LESSON OBJECTIVES
E-Mail Addresses
E-Mail Usage
The application uses e-mail for the supply chain communication (sending and receiving
substance information). Therefore, two e-mail addresses need to be implemented and
configured, one for customer and one for supplier communication. The configuration is
separated in two parts: one for inbound mails (receiving mails) and one for outbound mails
(sending mails).
Inbound Mail Configuration
Figure 161: Two Addresses for Inbound Communication

Unit 8: SAP Product and REACH Compliance
In transaction SPRO, choose IMG , then Product and REACH Compliance -> Basic Data ->
Specify Environment Parameters for Back-End Processes .
For inbound connectivity there is the need to define two e-mail addresses. The SMTP server
has to forward all entries for these e-mail addresses to the SAP system. In SAP Product and
REACH Compliance, you can define the environmental parameters for the two addresses. The
values from the parameters are used in the e-mail text and as reply address.
Furthermore this address defined here must be the same as the one used in the Adobe
Interactive Form template. There is no need to establish a sub domain for e-mails!
To activate the address type for business objects, enter transaction SO16 (Shared office
settings). Choose the Addressing tabstrip. Choose SAP Business Objects . This enables
forwarding incoming mails to shared folders. You have to make this setting only once.
Outbound mail configuration

For outbound mail configuration, a regular task has to be scheduled in transaction SCOTto
deliver mails to the outgoing SMTP mail server. This is the only setting for outgoing mail and
has to be done only once.
If you want to deliver mails immediately, you can either choose the Send directly button
from the menu bar, or use transaction SOST, which offers similar functionality.
Texts Communication Tasks

SAP Product and REACH Compliance
The SAP Product and REACH Compliance helps managing informational requirements on
products and chemical substances according to the REACH legislation and others. This
information can be gathered from within a company, but in most cases the information must
be obtained from business partners such as customers or suppliers (vendors).
Therefore the SAP Product and REACH Compliance offers several campaign types in the
supply chain communication, where the user can communicate with the business partners
according to the information requirements. For example, a campaign for determining “ uses”
according to the REACH legislation.
Triggering such campaigns is being reflected in tasks that shall be completed by the users of
the application.
The e-mails sent out by the application and several other items need to be configured
accordingly. The most important steps for the configuration of the supply chain
communication are explained in this lesson.
Report for E-Mail Processing

The application will receive several e-mails, which will contain requested information. To be
able to evaluate this information, the e-mails and the attached files are to be processed. This
causes a transfer of the information from the attachments to machine readable information in
the application. The repost is /TDAG/CPR_TASK_EMAILPROCESS, which will be maintained
and customized via transaction /TDAG/CPT03 .
Public Mail Folders

Public mail folders can be accessed by all users of SAP ERP systems, if they have the
according permissions granted. In the public mail folders, information can be stored that shall

Lesson: Setting Up and Customizing
be accessible by many people in comparison to your personal e-mail folders, where only the
user has access to.
The following are folders for customer response:
CUS_INBOX - for unprocessed customer mails
CUS_FAILED - for mails that caused an error during processing (see log files)
CUS_IMPORTED - for successfully processed mails
CUS_UNKNOWN - for mails with none or unknown attachments after unsuccessful

processing
The following are folders for supplier response:
SUP_INBOX - for unprocessed supplier mails
SUP_FAILED - for mails that caused an error during processing (see log files)
SUP_IMPORTED - for successfully processed mails
SUP_UNKNOWN - for mails with none or unknown attachments after unsuccessful

processing
The names of the public folders can be different. The suggested names are best practice. If
different names are chosen, customizing has to reflect the different names of the public
folders.
The SAP Product and REACH Compliance stores all of its e-mails in public folders, which are
accessible with transaction SWBP. The SAP Product and REACH Compliance requires eight
public folders.
E-Mail Forwarding
Once the e-mail addresses have been created, the SAP system needs to establish the
connection between the address itself and the place where incoming mails shall be placed.
The incoming mails shall be placed in the public folders created in the previous step.
Therefore an e-mail forwarding must be established.
Adobe Interactive Forms (AIF)

To collect the information to fulfill several legislative requirement the SAP Product and
REACH Compliance uses the campaign concept to address business partners. With the help
of Adobe Interactive Forms (AIF) the application offers means to supply information in a
structured manner.
AIFs are PDF documents that can be opened and filled out with a standard PDF viewing tool.
Internally the information entered is stored within the PDF file. The PDF will be sent back to
the application and can automatically be processed.
Preconditions
To be able to edit or modify the AIFs several preconditions need to be fulfilled. On the SAP
NetWeaver server, the Adobe Document Service (ADS) must be configured properly. It is part
of the standard delivery of SAP NetWeaver. To activate it, a “ credentials file” must be
requested and installed by the SAP basis team, see SAP note 736902.
To check the proper setup of ADS, several reports are available which can be run via
transaction SE38 :

FP_PDF_TEST_00: general ADS Test
FP_TEST_00: Test RFC connection to ADS
FP_TEST_IA_01: Test of the interactive ADS component
Only if these reports run successfully, the setup of ADS is successful. For further
troubleshooting, see SAP note 944221.
To edit the AIF templates, the Adobe LiveCycle Designer must be installed on each client
computer. To edit AIF Templates, call transaction SFP .
Basic Materials and Surfaces Management

General Information about Discrete Industries Solution
The SAP Product and REACH Compliance is divided in two major areas of functionality:
Process industry functionality and discrete industry functionality.
Process industry is about things that are measured in tons and liters. Discrete industry is
about pieces and items. The discrete item definition: A discrete item is defined by its shape by
a stronger degree than by its chemical composition.
Nevertheless discrete items must adhere to various regulations such as RoHS (Restriction of
(the use of certain) Hazardous Substances, directive 2002/95/EG) that limit the content of
hazardous substances in products such as lead, mercury, and bromines.
To represent discrete items in the system, a set of certain specification types has been
introduced to model them in the specification database. Specific reports called “ checks”
analyze a specification structure with these types and summarize the amounts of certain
components along the product structure. Compared to defined threshold levels, the report
can then decide whether an item is compliant according a specific regulation or not.
Standard Data Model for Discrete Industry (DI)
Figure 162: General Data Model for DI

Lesson: Setting Up and Customizing
There is a standard data model for the DI as denoted in the following illustration:
At the top we have the finished product subject of underlying one or several requirements. It
may consist of one or several product parts. A product part in turn consists of basic materials
and a surface. These relationships are modeled in the “ Exact composition based on starting
materials” .
The basic materials can be modeled as a group (pure group) oft the substances it consists of.
The group is modeled in the “ Standard composition” . The pure group in turn consists of pure
substances (ideal models of chemical substances) in the “ Grouping” property.
Down to the level of basic materials and surfaces, this information can automatically be
generated with the BOMBOS transfer: Bills of Materials to Bills of Substances. This is usually
done during the set-up of new products in the specification database. The compositions on
the pure substance and pure substance groups usually will be modeled by experts.
Standard Data Model in Specifications

The standard data model must be transferred to specifications in the specification database.
The following specification types exist especially for DI:
MAT_PART
BASMAT
PURE_GRP
SURFACE
The specification types of PURE_SUB and REAL_SUB are also part of the standard EHS
environment. PURE_GRP also exists in the standard EHS environment, but is rarely used
there.
Data Structure DI - Specification Types
Figure 163: Data Structure DI - Specification Types

The standard data model displayed in specifications is shown in the figure.

In case there is a supplier relationship available, the corresponding specification is created as
an “ EXTERNAL” variant, for example MAT_PART_E instead of MAT_PART. In case a
specification such as MAT_PART_E has subsequent bills of specifications, all of them will also
be EXTERNAL, for example SURFACE_E.
To Create a DI-Specific Specification Structure

To create a DI-specific specification structure successfully, you are supported by the
BOMBOS transfer (Bills of Materials to Bills of Specifications). Usually only the PURE_SUB
and PURE_GRP levels have to be amended in a manual step.
1. Define exactly the set of materials that shall be transferred into the specification database.
Usually you have more material data objects in your ERP system than the ones that are
subject of DI-specific regulations. With the help of certain criteria, an automated collection
or separation of material objects can be done, and only a minority of materials may be
transferred in a second, manual step.
2. Define the conversion parameters of the BOMBOS transfer. The BOMBOS interface is a
powerful tool that can aggregate, separate, modify, amend and / or exclude data available
in the SAP ERP system or from third party sources during the conversion step to the
specification database. A great part of an implementation time shall be spend on proper
configuration of the BOMBOS transfer.
3. Perform a test run the BOMBOS transfer. Choose typical materials from your set and test
the transfer. Examine the result of the transfer in the specification database with
transaction CG02
4. Do the complete run of BOMBOS transfer. Depending on the number of materials to be

transferred and the complexity of the modifications during the transfer, the complete
transfer may be split up into several sessions, probably over several days.
5. Recheck the transferred specifications. Amend necessary data in the property tree of the
specifications. Amend PURE_GRP and / or PURE_SUB compositions where necessary.
This must usually be done in several manual steps by experts.
6. Use the checks of the DI-specific functionality to see if your products are compliant.
LESSON SUMMARY

Unit 8
Learning Assessment
1. I can use only one predefined e-mail template in one language for my campaigns.
X True
X False
2. I can completely redesign my adobe template to my requirements, such as adding

arbitrary questions.
X True
X False
3. My incoming mails from suppliers and customers are automatically processed and the
contained data is automatically extracted. I just have to check the FAILED folder once and
a while.
X True
X False
4. The Adobe Document Service (ADS) has just to be installed - it simply runs “ Out of the
box” .
X A Yes, it is just one of the installation packages.
X B No, I need to obtain a “ credentials file” and install it in addition as described in an

SAP note.

5. Name specific specification types that have been introduced for discrete industries:
X A Material Part (MAT_PART)
X B Basic Material (BAS_MAT)
X C Surface (SURFACE)
X D Pure Substance Group (PURE_GRP)
X E Pure Substance (PURE_SUB)
6. When the BOMBOS transfer has taken place, I can directly start doing checks on my
materials.
X True
X False
7. What special purpose do the _E (external) specification types have?

X A None, I can use them equivalent to the standard types.
X B They model material, that is actually not produced but in the future will.
X C External specifications are used to hold supplier delivered information.
X D The data modeled in external specifications is not valid.

Unit 8
1. I can use only one predefined e-mail template in one language for my campaigns.
X True
X False
2. I can completely redesign my adobe template to my requirements, such as adding

arbitrary questions.
X True
X False
3. My incoming mails from suppliers and customers are automatically processed and the
contained data is automatically extracted. I just have to check the FAILED folder once and
a while.
X True
X False
4. The Adobe Document Service (ADS) has just to be installed - it simply runs “ Out of the
box” .
X A Yes, it is just one of the installation packages.
X B No, I need to obtain a “ credentials file” and install it in addition as described in an

SAP note.

5. Name specific specification types that have been introduced for discrete industries:
X A Material Part (MAT_PART)
X B Basic Material (BAS_MAT)
X C Surface (SURFACE)
X D Pure Substance Group (PURE_GRP)
X E Pure Substance (PURE_SUB)
6. When the BOMBOS transfer has taken place, I can directly start doing checks on my
materials.
X True
X False
7. What special purpose do the _E (external) specification types have?

X A None, I can use them equivalent to the standard types.
X B They model material, that is actually not produced but in the future will.
X C External specifications are used to hold supplier delivered information.
X D The data modeled in external specifications is not valid.

UNIT 9 Substance Volume
Tracking
Lesson 1
Basic understanding in Substance Volume Tracking 232
Lesson 2
Understanding the Procurement Scenario 237
Lesson 3
Understanding the Production Scenario 242
UNIT OBJECTIVES
Describe the basics of SVT (substance volume tracking)
Use Substance Volume Tracking (SVT) in the procurement scenario
Use Substance Volume Tracking (SVT) in the production scenario

Unit 9
Lesson 1
Basic understanding in Substance Volume
Tracking
LESSON OVERVIEW
This lesson provides the basic information about Substance Volume Tracking
LESSON OBJECTIVES
Material-Based SVT versus EHS Management SVT

Automatic identification of produced, imported/purchased, exported/sold substances
Determination of quantities of produced, imported/purchased, exported/sold substances
Periodic tracking of quantities (by year, quarter, month, week …)
Offline monitoring of quantities
Online checks with the possibility to block business processes
Archiving of determined quantities in EHSM properties
SVT uses the substance data in SAP EHS Management (EHSM). It links the substance data
with the material data in the logistic processes to identify produced, purchased or imported,
sold, or exported substances. Use SVT to identify the import (purchase), production- or
export (sales) volumes of substances.SVT allows the tracking by a defined period like a
quarter, month, week, or day. The default tracking period is the calendar year. SVT provides
an offline monitor (transaction CBRC20) which shows the tracking data on one screen. The
business process owners are informed when a threshold is exceeded. Information can be
provided by e-mail. Business processes can be blocked. Volumes of one substance can be
archived per period in the EHSM database (in the properties Produced Quantities, Consumed
Quantities, Purchased Quantities, and Sold Quantities).
Typical Tracking Scenarios
Tracking Scenarios
Production:
Produced Quantities
Consumed Quantities
Procurement:
Purchased Quantities

Lesson: Basic understanding in Substance Volume Tracking
Imported Quantities
Sales:
Sold Quantities
Exported Quantities
For the production business process (production scenario), SVT can track the produced and
consumed quantities of substances. Produced quantities are quantities, which are newly
created in a chemical reaction. Consumed quantities are quantities, which are consumed in a
chemical reaction.
For the procurement scenario, the tracked quantities can be purchased and/or imported.
Purchased quantities are all quantities determined in the procurement scenario. Imported
quantities are only quantities, which are imported from outside a validity area of a regulation
into the validity area of a regulation.
For the sales scenario, the tracked quantities can be sold and/or exported. Sold quantities are
all quantities determined in the sales and distribution scenario. Exported quantities are only
quantities which are exported in either of the following ways:
From inside a validity area of a regulation to a country outside the validity area of a
regulation
From outside a validity area of a regulation to a country inside the validity area of a
regulation
Typical Tracking Scenarios: Example REACH

REACH:
Produced Quantities in EEA
Imported Quantities to EEA
Exported Quantities to Customers in EEA
The regulation REACH (Registration, Evaluation & Authorization of Chemicals) is the

framework legislation for the Registration, Evaluation, Authorization of Chemicals and was the
trigger for the implementation of EHSM SVT.
REACH is valid for all countries in the European Economic Area (EEA). The registration is for
REACH has to be done by substance. The registration requirements depend on substance
volumes. REACH impacts imported and produced substances. A typical SVT implementation
for REACH includes the tracking of produced quantities in the European Economic Area (EEA)
and quantities imported into the EEA. Companies located outside the EEA do typically track
quantities exported to customers in the EEA.

Unit 9: Substance Volume Tracking
Schematic Overview on SVT
Figure 164: SVT: Schematic Overview
This picture gives a schematic overview of the SVT business process. SVT is runs in the
Logistic System. It reads and analyses purchase orders, production orders, and SD orders. If
the orders are relevant for SVT, then SVT recalculates from the material volumes the
substance volumes. For this recalculation, SVT uses data from SAP EHS Management stored
in special tables in the logistic system. To fill these tables, a report transfers the data from
SAP EHS Management into special SVT data tables in logistics. The tracked and recalculated
data are written in tables in the logistic system. A transaction displays this tracked data
(transaction CBRC20). The collected data can be archived automatically or manually to the
SAP EHS Management.
SVT Implementation Landscapes
Figure 165: Simple SVT Landscapes

Lesson: Basic understanding in Substance Volume Tracking
Simple SVT Landscapes

Landscape 1:
Logistics and SAP EHS Management are in one client, EHSM and SVT runs in the same
box. Even if EHSM and Logistics do run in the same client, the data from SAP EHS
Management is transferred to the SVT data table in logistics.
Landscape 2:
Logistics and SAP EHS Management are in different clients: The data from SAP EHS
Management client is transferred via an RFC connection to the SVT data tables in the
Logistics client. SVT runs on the logistic clients. The result of SVT can be monitored in the
logistic system. If you want to monitor the results in EHS you can call the SVT result in the
logistic system using RFC.
Complex SVT Landscape
Figure 166: Complex SVT Landscape
One central SAP EHS Management client and several Logistics clients: The data from SAP
EHS Management client is transferred via an RFC connection to the SVT data tables in every
logistics client. SVT runs on every logistic client. The result of SVT can be monitored in the
logistic systems. If you want to monitor the results in EHS you can call the results in the
logistic systems using RFC. You cannot monitor several logistic systems in one SVT monitor
in the EHS system. If this is required, enhancements are necessary.
System Requirements for SVT

Release Support Package
SAP R/3 4.6C with EHS2.7b SP 14

SAP R/3 Enterprise 470x110 SP 24
SAP R/3 Enterprise 470x200 SP 13

Release Support Package
SAP ERP 2004 SP 16

SAP ERP 2005 (6.0) SP 09
SAP ERP 6.0 EHP 2
SAP ERP 6.0 EHP 3
SAP ERP 6.0 EHP 4
SAP ERP 6.0 EHP 5
SAP ERP 6.0 EHP 6
SVT was delivered with the releases and support packages listed in this table. The releases
listed have to be installed on the logistic and EHSM system if you want to use EHSM SVT. SVT
is delivered with EHSM and is part of the technical component EA-APPL (SAP Enterprise
Extension PLM, SCM, Financials) or with the add-on EHS (only for SAP R/3 4.6C). Some
additional functionality and legal changes there delivered with higher releases and support
packages. For more information, see SAP note 905726.
LESSON SUMMARY

Unit 9
Lesson 2
Understanding the Procurement Scenario
LESSON OVERVIEW
This lesson explains how Substance Volume Tracking is used in the procurement scenario.
LESSON OBJECTIVES
Input Data for Procurement Process in SVT
Input Data
Vendor:
Address of the vendor
Ordering address
Delivery address:
Delivery address
Customer or warehouse address
Ordering plant
Ordered material:
Material
Ordered quantity
SVT reads and analyzes the vendor, the delivery address, and the information about the
material and the quantity from the purchase order.
From the vendor, SVT analyzes the partner rolls and looks for the vendor address and the
optional ordering address. If one of these addresses is in the REACH area, then the purchase
is not an import.
A similar process is done for the delivery address. SVT looks here first if a manually entered
address exists. If this address is not available, SVT looks for addresses from address
management (for example, the customer or warehouse address). If nothing is available in the
area delivery address, then SVT uses the automatically applied ordering plant.
Finally, SVT analyzes the material and reads the ordered quantity. The quantity in the
purchase order could be different from SI-Units (for example, barrels, pallets, gallons, and so
on). To convert the units, SVT looks in the material master.

Online Checks
Purpose of Online Checks

Online checks do the following:
Monitor thresholds for substances
Give information to the creator of a REACH relevant order
Send an e-mail to responsible persons
Interrupt business processes before the registered quantity is exceeded
The online checks work like a traffic light: If no online check appears, you are far from
exceeding the registered quantity. The first online check pop-up indicates that you have
reached or crossed the first threshold usually set at 70% of the registered quantity (still
green). The next two thresholds are defined at 90% (yellow) and 100% (red). The system
reacts to the online checks with an information pop-up on the screen, by sending e-mails, or
blocking the order. The thresholds and the reactions are both customizable and definable for
each substance.
Example REACH: Imports into the EEA
Figure 167: Import into EEA
According to REACH import means the physical introduction into the customs territory of the
European Economic Area (EEA). For the everyday work, the REACH definition of “ import” is
not always clear, especially when you consider consignment, customs warehouse, third party
sales, and so on. Analyze and discuss the business processes of configuring SVT to meet the
needs of your company. In the following demo, we use simple and clear definitions: An import

Lesson: Understanding the Procurement Scenario
into the EEA does exist if the supplier of a purchase order is located outside the EEA, and the
recipient of the purchase order is located inside the EEA. In the demo we look at later, a
company in Germany (company code 1000) purchases a material from a vendor in South
Korea.
Demo Data Model
Figure 168: SVT Data Model
To prepare for the demonstration, we examine how SVT determines the substance volumes.
SVT uses the material number from the purchase order. For this, SVT looks for the material
substance assignment. SVT finds the corresponding real substance. In the legal or standard
composition of the real substance, SVT gets the detailed substance composition of the
material. With the volumes in the purchase order and the composition data, SVT calculates
the substance volumes of the order.

Procurement Data Access
Figure 169: SVT Procurement Data Access
In the procurement process demonstration we look at a purchase order and what SVT will do
with the order. We track imports into the EEA. In the first part of the demonstration we create
a purchase order for a material which has to be registered under REACH and look at the result
of the Online Check. In the second demonstration we then track the purchase order with SVT
and look at the output of SVT in the offline monitor.
Offline Checks
The SVT tracking data is collected during an overnight run of the tracking report. The
collected data is shown in the offline monitoring table in the transaction CBRC20. The table
shows the tracking result for each combination of scenario/order/material/real sub/pure
sub.
The overall status summarizes the results for each pure substance and shows it in relation to
the threshold. The result is shown as a traffic light.
For the calculation of the overall status all volumes of a pure (tracked) substances in a
company (represented by the company code) are added up and compared with the defined
thresholds. The Planned quantities flag shows if a quantity is planned, or already confirmed.
Offline Monitoring Table
Over. Stat
Traffic light status of a single tracked substance
Plnd. Qty
X represents a planned quantity
Material | Specification | Tracked Subs.
Material ID, Specification ID Real_Sub, Specification ID Pure_sub
CoCd

Lesson: Understanding the Procurement Scenario
Company code = code of the legal entity
In the second part of the procurement process demo we run the job which tracks the volumes
in SVT and look at the output of SVT in the offline monitor. We confirm the quantities of the
purchase order we created in the first part of the demonstration and then rerun the tracking.
Planned and Confirmed Amounts
Figure 170: SVT Planned Versus Confirmed Quantities
When a company sends out a purchase order to a vendor, they intend to receive the material
as indicated in the purchase orders. It is not sure, however, if the material is delivered or not,
or if only parts of the order are delivered.
For SVT this means that the amounts of these purchase orders are planned amounts. If a
material is delivered and confirmed with a goods receipt, then the planned amounts become
confirmed amounts. SVT condenses all confirmed amounts for the given pair of material/real
substance/pure substance/plant.
LESSON SUMMARY

Unit 9
Lesson 3
Understanding the Production Scenario
LESSON OVERVIEW
This lesson explains how Substance Volume Tracking is used in the production scenario.
LESSON OBJECTIVES
Mixture Versus Reaction in SVT
Figure 171: SVT Mixing Versus Reaction
In the chemical industry, you can distinguish between two types of production processes:
Blending/mixing
Blending or mixing means to mix two or more raw materials into one product, for
example, shampoo. All substances from the raw material are chemically unchanged in
the end product. In the example (see figure) material 207 consists 100% of the chemical
207P (ethyl acetate), and material 206 contains 100% of the chemical 206P (toluene).
The end product 180 contains 80% of 207P and 20% of 206P. In the demonstration
which you see later we produce 10.000 kg of material 180. To do this, we mix 8000 kg of
material 207 with 2000 kg of material 206.

Lesson: Understanding the Production Scenario
Chemical reaction
In a chemical reaction, two or more raw materials are mixed and the substances of these
materials react to a new substance. The end product of such a reaction contains new
substances. In the example (see figure), material 205 consists of 2 chemical 501P
(ethanol, 98%) and 502P (cyclohexane, 2%), and material 208 contains the chemical
208P (acetic acid, 100%). The chemicals react to the chemical 207P (ethyl acetate) in
material 207. Material 207 contains 100% of chemical 207P. In the demonstration which
you see later we produce 15.000 kg of material 207. To do this, we use 7845 kg of
material 205, and 10.230 kg of material 208.
Since the substances of the mixture are the same before and after the production step, only
the chemical reaction – where a new substance is created – is considered as a production in
SVT. To determine if a substance is produced, SVT compares the input substances of the
production with the output substances of a production.
Blocking Concept for Production
Blocking Concept
Control options:
Customizing
Substance specific in properties
Main parameters:
Registered quantity / tonnage band
Relative limits
Type of reaction
Properties for registered quantities:
REACH registration
REACH preregistration
Registration (company-specific)
Property for specific relative limits:
Set threshold
Set reaction type
SVT has two options for controlling the reaction of SVT. You find a global part of settings in
Customizing and you can specify substance-specific settings. Substance-specific settings
overwrite Customizing settings.
Substance-specific Settings in SAP EHS Management

For substance-specific settings, you can use properties in SAP EHS Management.
Registered quantity
You can define what your registered quantity is or will be for each REACH-relevant
substance. SAP EHS Management and SAP Product and REACH Compliance provides

three different properties. The sequence in which these properties are read by SVT are as
follows:
1. REACH Registration
2. REACH Preregistration
3. Registration (company-specific)
The third property is the SVT standard property, delivered with SAP EHS Management.
The first 2 properties are delivered as part of the SAP Product and REACH compliance. If
none of the properties is maintained, SVT assumes that the substance is not registered.
In such a case SVT uses the upper quantity limit of the lowest tonnage band defined in
Customizing (for REACH this is 1 metric ton).
Control Options in Customizing

You can find the customizing activities for SVT in Customizing (transaction SPRO). Choose
Environment, Health and Safety - Product Safety - Substance Volume Tracking .
Choose the customizing activity Specify Quantity Limits and Reactions on Overall Status .
Here, you define the relevant tonnage bands and the relative quantity limits for a regulation
(regulatory List), and reactions if limits are exceeded. You can define three different relative
quantity limits per tonnage band: information, warning, and error limit.
For each of the relative quantity limits you can define the following three reactions:
Display a message
Send e-mail to responsible persons
Block the business process
SVT-Specific Quantities Property
Figure 172: SVT-Specific Quantities Property

Lesson: Understanding the Production Scenario
You can also define substance-specific relative limits and reactions in the Specific Quantity
Limits (SVT) property. You find this property in the EHS standard property tree in the node for
Substance Volume Tracking . To overrule the customizing settings for a certain specification,
you can make substance-specific settings in this property. If you do not define this property,
settings made in Customizing are used.
Caution:
If you want to change only one setting, you still have to maintain all of the other
settings. For example, if you set the limit for an additional warning to 50%, you
must also define the other limits. The Customizing settings will not be
automatically used in this case.
Blocking Concept
Figure 173: SVT Blocking Concept
This figure describes how the online check works and how the decision is made if a block is
required.
First the online check determines the volume. For that the online check adds up the current
quantities from the process/production order and the volumes in the tracking table already
tracked by the overnight tracking report. This volume is compared with the thresholds
maintained for the substance:
If a registered quantity is maintained for the substance in one of the registration properties,
this quantity is used. If not the first tonnage band in customizing is used. Next the online
check determines the relevant relative quantity limit. If a specific relative limit for the
determined tonnage band in property the Specific Quantity Limits (SVT) exists, then this one
is used; if not, then the relative limits for the determined tonnage band from Customizing is
used.
A relative quantity is relevant if the tracked quantity exceeds the relative limit. If more than
one relative quantity limit is exceeded, the highest quantity limit is used. A block is executed
only if the block is defined for the determined relative quantity limit.

Production Data Access
Figure 174: SVT Production Data Access
In the production process demo we look at a process order which exceeds the default
quantity limit defined in Customizing. In the first step of the demonstration we create
the process order for a material which has to be registered under REACH. We then look at the
result of the online check. Next, we maintain a registration for a produced substance. Finally
we have a look at the process of unblocking a blocked purchase order.
LESSON SUMMARY

Unit 9
Learning Assessment
1. In which part of the SAP ERP system does Substance Volume Tracking mainly run?
X A In EHS classic
X B In the specification database
X C In sales, purchasing and production
X D In Materials Management (MM)
2. The Substance Volume Tracking can only be used for REACH purposes.
X True
X False
3. Does SVT block business processes in all cases?

X True
X False
4. The monitoring table shown in transaction CBRC20 shows life results of my business.
X True
X False

5. In which priority online checks are carried out (highest to lowest)?

X A Customizing > relative tonnage threshold > property maintained threshold
X B Relative tonnage threshold > customizing > property maintained threshold
X C Property maintained threshold > relative tonnage threshold > customizing
X D Property maintained threshold > customizing > relative tonnage threshold
6. If I change the composition of a tracked substance, Substance Volume Tracking will notice
without any further action.
X True
X False

Unit 9
1. In which part of the SAP ERP system does Substance Volume Tracking mainly run?
X A In EHS classic
X B In the specification database
X C In sales, purchasing and production
X D In Materials Management (MM)
2. The Substance Volume Tracking can only be used for REACH purposes.
X True
X False
3. Does SVT block business processes in all cases?

X True
X False
4. The monitoring table shown in transaction CBRC20 shows life results of my business.
X True
X False

5. In which priority online checks are carried out (highest to lowest)?

X A Customizing > relative tonnage threshold > property maintained threshold
X B Relative tonnage threshold > customizing > property maintained threshold
X C Property maintained threshold > relative tonnage threshold > customizing
X D Property maintained threshold > customizing > relative tonnage threshold
6. If I change the composition of a tracked substance, Substance Volume Tracking will notice
without any further action.
X True
X False

SUS300 - EN - Col10 Product Safety and Stewardship

Uploaded by

Copyright:

Available Formats

SUS300 - EN - Col10 Product Safety and Stewardship

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SUS300 - EN - Col10 Product Safety and Stewardship

Uploaded by

Copyright:

Available Formats

Product Safety and Stewardship

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

American English is the standard used in this handbook.

This information is displayed in the instructor’s presentation

Related or Additional Information

User interface control Example text

Window title Example text

© Copyright. All rights reserved. iii

vii Course Overview

1 Unit 1: EHS Tools and the Integration with SAP ERP

2 Lesson: EHS Basics: Tools and Integration with SAP ERP

56 Unit 2: Basic Configuration

57 Lesson: Configuring and Customizing Sustainability Products

71 Unit 3: EHSM Data Structure

72 Lesson: Defining a Property Tree

90 Unit 4: Data Migration

91 Lesson: Defining and Setting up the Data Model

121 Lesson: Installing Expert Server

168 Unit 6: Dangerous Goods

169 Lesson: Setting up Document Printing

185 Unit 7: Global Label Management

186 Lesson: Determining User Requirements

220 Unit 8: SAP Product and REACH Compliance

221 Lesson: Setting Up and Customizing

© Copyright. All rights reserved. v

232 Lesson: Basic understanding in Substance Volume Tracking

© Copyright. All rights reserved. vi

© Copyright. All rights reserved. vii

Examine the structure of SAP EHS Management

Use the EHS Workbench

Search and create specifications

Create properties manually

© Copyright. All rights reserved. 1

Examine the structure of SAP EHS Management

Use the EHS Workbench

Regulatory Requirement of Managing EHS Data

Figure 1: SAP Services: Sustainability Services Portfolio

© Copyright. All rights reserved. 2

Regulatory Requirements of Managing EHS Data

Figure 2: Regulatory Requirements of Managing EHS Data

Sustainability Tools - EHS Management

Figure 3: Sustainability Tools - SAP EHS Management

© Copyright. All rights reserved. 3

Health and Safety Pillar

Figure 4: Health and Safety Pillar

Product Safety and Stewardship Pillar

Figure 5: Product Safety and Stewardship Pillar

© Copyright. All rights reserved. 4

Environmental Performance Pillar

Figure 6: Environmental Performance Pillar

Environmental Performance supports the minimization of the environmental impact of

Technical Integration of EHS Management (EHSM) in SAP ERP

Required SAP components

Engineering Change Management (LO-ECH)

Document Management (CA-DMS)

Classification System (CA-CL)

Material Master (LO-MD-MM)

Sales and Distribution (SD)