EH&S Industrial Hygiene and Safety
SAP Best Practices for Chemicals (Russia)
SAP Best Practices
Scenario Overview
Purpose and Benefits:
Purpose

© SAP 2008 / Page 2
The purpose of to describe business processes related to Industrial Hygiene &
Safety.
Scenario Overview
SAP Applications Required:
Required

SAP ECC 6.00 EhP3
Company roles involved in process flows

© SAP 2008 / Page 3
EH&S Clerk
Scenario Overview
Business Requirement: Comply with substance exposure regulations and safety
procedures
Collect and maintain data on exposure to hazardous substances
Define Product
Master Data
Requirements
Enter Exposure
Data, Collect
Data from
Plants and
Warehouses
Generate
Reports and
Registers
Define safety procedures and apply to plant procedures to ensure safe working conditions
Define Safety
Procedures
© SAP 2008 / Page 4
Map Safety
Procedures to
Plant Procedures
(Maintenance
etc.)
Business View: Industrial Hygiene & Safety (1)
Business
Benefits
You can use
the work area
concept to
continually and
effectively
improve the
safety situation
of the
employees
concerned.
This is very
helpful for
evaluations
performed at a
later stage.
In this scenario,
the integration
to the storage
locations is
used to upload
data from
inventory
management
for use in the
hazardous
substances
register.
© SAP 2008 / Page 5
Production/Quality
Chemical Company
Responsible
Define Work area
Maintaining Industrial
Hygiene and Safety
Data
Setting up Integration
with Storage
Locations
Maintaining Exposure
Profile
Entering
Measurement Values
for Agents in the
Exposure Profile
Generating a
Hazardous
Substances Register
Product/Packaging
Supplier
Developer
Product
Authority
Manager
Business View: Industrial Hygiene & Safety (2)
Business
Benefits
You can include
all the agents
(for example
hazardous
substances,
noise,
mechanical
hazards, mental
stress) that
exist in the
company.
The Hazardous
Substances
Register is
displayed,
including
information on
work areas and
related agents,
amounts stored,
received and
issued (as far
as available in
the system) and
substance
classification.
© SAP 2008 / Page 6
Production/Quality
Chemical Company
Responsible
Defining Safety
Measures
Creating Work-AreaRelated SOPs
Displaying Existing
SOPs
Product/Packaging
Supplier
Developer
Product
Authority
Manager
Interactive View: Industrial Hygiene & Safety
SAP ERP
Work Area Definition in General
CBIH02
Registering the Technical Equipment
CBIH02
Exposure Profile:
Adding/Qualifing Agents
CBIH02
Perform Risk Assessment
CBIH12
Setting up Safety Measures
for Work Areas
CBIH02
Creating and Release SOP
CBIH12
Displaying the Hazardous
Substance Register
CBIH63
© SAP 2008 / Page 7
Standard Operating Procedures
© SAP 2008 / Page 8
EH&S Clerk
Event
Process Flow Diagram
IHS legal
requirement
Define and
edit work
areas
© SAP 2008 / Page 9
Maintain
IH&S
data
Set up
Integration
with SLOC
Maintain
exposure
profile
Enter
measurement
values for
agents
Display
substance
inventory
Define
safety
measure
Create
SOP for
work area
Display
SOP
Legend
<Function>
Symbol
Description
Usage
Comments
Band: Identifies a user role, such as Accounts
Payable Clerk or Sales Representative. This band
can also identify an organization unit or group,
rather than a specific role.
Role band
contains tasks
common to that
role.
Symbol
Diagram
Connection
The other process flow symbols in this table go into
these rows. You have as many rows as required to
cover all of the roles in the scenario.
Hardcopy /
Document
External
to SAP
External Events: Contains events that start or end the
scenario, or influence the course of events in the
scenario.
Business
Activity /
Event
Flow line (solid): Line indicates the normal sequence
of steps and direction of flow in the scenario.
Flow line (dashed): Line indicates flow to infrequentlyused or conditional tasks in a scenario. Line can
also lead to documents involved in the process flow.
Connects two
tasks in a
scenario
process or a
non-step event
Business Activity / Event: Identifies an action that
either leads into or out of the scenario, or an outside
Process that happens during the scenario
Does not
correspond to a
task step in the
document
Unit Process: Identifies a task that is covered in a
step-by-step manner in the scenario
Corresponds to
a task step in
the document
SubProcess
Reference
Proces
s
Decisio
n
© SAP 2008 / Page 10
Usage Comments
To next / From last Diagram: Leads
to the next / previous page of the
Diagram
Flow chart continues on the next /
previous page
Hardcopy / Document: Identifies a
printed document, report, or form
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Financial Actuals: Indicates a
financial posting document
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Budget Planning: Indicates a
budget planning document
Does not correspond to a task
step in a document; instead, it is
used to reflect a document
generated by a task step; this
shape does not have any outgoing
flow lines
Manual Process: Covers a task
that is manually done
Does not generally correspond to
a task step in a document;
instead, it is used to reflect a task
that is manually performed, such
as unloading a truck in the
warehouse, which affects the
process flow.
Existing Version / Data: This block
covers data that feeds in from an
external process
Does not generally correspond to
a task step in a document;
instead, this shape reflects data
coming from an external source;
this step does not have any
incoming flow lines
System Pass / Fail Decision: This
block covers an automatic
decision made by the software
Does not generally correspond to
a task step in the document;
instead it is used to reflect an
automatic decision by the system
that is made after a step has been
executed.
Financial
Actuals
Budget
Planning
Manual
Proces
s
Unit Process
Process
Reference
Description
Process Reference: If the scenario references another
scenario in total, put the scenario number and name
here.
Sub-Process Reference: If the scenario references
another scenario in part, put the scenario number,
name, and the step numbers from that scenario here
Process Decision: Identifies a decision / branching
point, signifying a choice to be made by the end
user. Lines represent different choices emerging
from different parts of the diamond.
Corresponds to
a task step in
the document
Corresponds to
a task step in
the document
Does not
usually
correspond to a
task step in the
document;
Reflects a
choice to be
made after step
execution
Existing
Version /
Data
System
Pass/F
ail
Decisio
n