Environment, Health and Safety PDF

Copyright(c) 2018 by Nixon Vunganai.
All rights reserved.
Neither this document nor any part of it may be copied or reproduced in any form or by any
means or translated into another language, without the prior consent of Nixon Vunganai. The
information contained in this document is subject to change without notice.
WHATSAPP +255738656506
INTRODUCTION 4
FOUNDATION FOR EHS 5
INCIDENT MANAGEMENT 26
HEALTH AND SAFETY MANAGEMENT 26
ACCESS TO DATA AVAILABLE VIA A REMOTE SYSTEM 27
ACCESS TO DATA AVAILABLE VIA THE LOCAL SYSTEM ONLY 28
INCIDENT MANAGEMENT 40
BADI: INTEGRATION OF FINANCIAL TRANSACTION OBJECTS 89

INVESTIGATION 95
LOGISTICS INTEGRATION 98
NOTE 99
RECOMMENDATION 99
NOTE 100
RECOMMENDATION 100
NOTE 101
RECOMMENDATION 101
NOTE 118
HEALTH AND SAFETY MANAGEMENT 124
GENERAL CONFIGURATION 124
PROCESS CONFIGURATION 133
CONFIGURE PROCESS DEFINITIONS 135
AGENTS 171
AUTOMATIC DETERMINATION 199
INTRODUCTION
Welcome to the fascinating world of SAP. This book helps you crack the tricks of mastering SAP HANA
Customization
WHATSAPP +255738656506
Environment, Health and Safety
This section contains all information on the introduction for Environment, Health, and Safety.
Foundation for EHS
General Configuration
Specify General Settings
Use
In this Customizing activity, you can configure the following general systems settings:
- Default Language Key

By setting the default language, you determine the language for entering texts as well as the default
target language for translating texts. If texts do not exist in the language selected at logon, they will
be displayed in this language.
- Currency
Currencies are defined according to the international ISO standard.
Standard settings
The standard system is delivered with examples.
Activities
1. Check the existing examples and adapt them as required.

2. If necessary, define additional entries.
A unique key must be assigned to each entry.
Specify Number Range Intervals for Foundation
Use
In this Customizing activity, you can specify number range intervals for foundation objects.
A unique number is assigned to each record. The appropriate number range object determines the number
automatically.
You can specify number range intervals for the following number range objects:
- EHFNDACTID - Action ID
- EHFNDATMID - Action Template ID
- EHFNDCHMID - Chemical ID
- EHFNDCTRID - Control ID
- EHFNDLSUID - Listed Substance ID
- EHFNDLCNID - Location ID
- EHFNDPSEID - Process Setup ID
- EHFNDRPTID - Report ID
- EHFNDDYNPH - Dynamic Phrase ID
- EHFNDSPLM - Sampling Method ID
- EHFNDSAMPL - Sample ID
- EHFNDSPLNG - Sampling ID
For more information about other number range objects, see:
- For Environment, Health, and Safety:

- Specify Number Range Intervals for Incidents
- Specify Number Range Intervals for Health and Safety Management - For Product
Compliance for Discrete Industries:
- Specify Number Range Intervals for Product Compliance
Standard settings
The standard system is delivered with number range objects. Each number range object includes an
internal interval.
You can change the standard internal interval IE, for example, if you want to use a different number
range. If you do not have the standard internal interval in your system client, you must create your own
internal interval (IE).
Note: The standard internal interval for listed substances (EHFNDLSUID) is 01.
In the standard delivery, the number range interval for the chemical ID starts at 100000. We
recommend disjunct number ranges for the chemical and agent number range objects (used in health and
safety management).
Activities
If you want to make changes to the standard internal interval of a number range object or if you need to
create your own internal interval, perform the following steps:
1. Specify a number range object and choose Number ranges.

2. Choose the pushbutton to enter edit mode for the intervals of the number range object.
3. Adapt the limits of the standard internal interval (number range number IE) as required, or create an
internal interval. Since the standard system uses only the internal interval, leave the checkbox for
indicating external number ranges empty.
WHATSAPP +255738656506
Note
If you have already created data records in the system, we recommend avoiding changes to the
corresponding number range object. Changes to a number range object can lead to inconsistent data.
Specify Active Languages
Use
In this Customizing activity, you can specify the available target languages for translating free text fields
and statements.
If you want to translate a free text or a statement in the application, you can select the languages
specified here.
Standard settings
Activities

Specify Field Control
Use
In this Customizing activity, you can specify field control for business objects in components
Environment, Health, and Safety and Product Safety and Stewardship.
You can use field control to adapt the user interface to specific conditions of a data record. You specify
these conditions and how the system adapts the UI on the node level of a business object. You can, for
example, set up field control to make specific fields visible and editable on the user interface depending
on the country or region of the data record. Field control is possible on all nodes of a business object and
for all properties of the node. You can also specify more than one profile to accommodate each relevant
set of conditions of a data record.
Note: The following business objects are not using this customizing activity for field control, but have a
specific logic implemented in a property determination. To adapt the behavior of these business objects,
enhance the business object with a custom property determination:
EHPRC_COMPLIANCE_DATA (Property determination class:
CL_EHPRC_COD_SET_PROPERTIES)
Prerequisites
You are familiar with the modeling and structure of the business objects of Environment, Health, and
Safety and Product Safety and Stewardship in the Business Object Processing Framework (BOPF).
You are familiar with the legal reporting requirements of your country or region and the data that is
required to be compliant.
Standard settings
Activities

To create new field control profiles, perform the following steps:
1. Specify the business object for which you want to use field control.
2. Specify the node of the business object for which you want to create a profile.
3. Make the settings for the profile. You can decide when field control applies at the node level based
on the settings you make for the following fields:
- Authorization-Based Profile
- Authorization Check Result
- Function Class
- Node Attribute Value
(The system determines if field control applies in the order of the just mentioned fields.) If you
create more than one profile for a node, you can make settings for the merge strategy for each
profile.
4. After creating the profile, you can define the property settings for the business object node in the
subdialogs. These property settings control the behavior and appearance of the user interface. In this
step, you can also specify how to propagate the settings to subnodes.
Example
You use Environment, Health, and Safety to record incidents that occur in the United States and are
subject to OSHA requirements. There are certain injury/illnesses that are handled as privacy cases in the
United States. In this case, you can use field control to display the Privacy Case and Additional
Criteria radio buttons when you record data about injuries/illnesses that occurred in the United States.
Otherwise, these fields are not displayed.
Create Regulations
Use
In this Customizing activity, you can create regulations. You can use regulations in the application in the
following ways:
- To adapt the UI for a specific regulatory region

- To control the forms available to the data record
- To provide an informational context to the data record
WHATSAPP +255738656506
You use regulations to support your business processes, especially when your organization operates in
more than one country or region and must comply with the regulatory requirements of each
country/region. You can also use regulations to represent your organization's internal policy in the
system, for example, if you require specific fields on the UI or a specific internal report.
Standard settings

Note that you must specify these regulations further for use in the components of Environment, Health,
and Safety. For more information, see the following Customizing activities:
- Specify Regulations under Incident Management

- Specify Regulations under Compliance and Risk Management
A unique key must be assigned to each entry.The key must be unique to the other regulations in this
activity and to the regulatory lists and customer lists in Customizing activity Create Regulatory
Lists and Customer Lists.
Further information
For more information about adapting the UI for a specific regulatory region, see Customizing activity
Specify Field Control.
Create Regulatory Lists and Customer Lists
Use
In this Customizing activity, you can create regulatory lists or customer lists, and assign them to the
country or region where they apply. Regulatory lists provide information about substances that are
subject to legal or industry-specific regulation. If your organization uses its own lists, for example, if
your organization places additional restrictions on usage of a substance, you can also create customer
lists here.
Standard settings

Note that you must specify these regulatory lists further for use in the components
Environment, Health, and Safety and Product Safety and Stewardship. For more information, see
the following Customizing activities:

- Specify Regulatory Lists for OELs
- Specify Lists for Restricted Substances Check
- For Product Safety and Stewardship
- Specify Regulatory Lists and Customer Lists
A unique key must be assigned to each entry.The key must be unique to the other regulatory lists
and customer lists in this activity and to the regulations in Customizing activity Create Regulations.
3. Assign the regulatory list to the country or region where the regulatory list applies. In health and
safety management, if you want to analyze exposure to chemicals by comparing actual amounts of a
chemical (a risk) to its OEL, the country or region of the risk's location must match the country or
region of the regulatory list.
Specify Document Storage
Use
In this activity, you can learn about setting up attachment types and assigning these to attachment
schemas. An attachment schema may be assigned for a given business object (BO) node that uses the
dependent object attachment folder.
Environment, Health, and Safety uses the Content Management Service to store documents, for
example, attachments and generated PDF reports.
The connection to the Content Management Service is specified and implemented by the attachment
folder (ATF) of the business object (a reusable object for the BOPF environment in the SAP_BS_FND
software layer).
Standard settings
The standard system is delivered with the following:
- Settings that use the content repository BS_ATF_DB_REPOSITORY and the content category
BS_ATF_DB to store documents in the database.
- An alternative configuration to connect to a separate file server. To achieve this, the attachment
schema needs to be assigned to the content category BS_ATF. This content category uses the
content repository BS_ATF_CONTENT_SERVER.
- Customizing settings for attachments, for example, for when you attach a document to a business
object delivered with Environment, Health, and Safety.
1. Ensure that the settings for the Content Management Service are correct in Customizing for SAP
NetWeaver under Knowledge Management -> Settings in the Knowledge Warehouse
System -> Content Management Service.
2. Ensure that the settings for the attachment schema are correct for the Environment, Health, and
Safety business objects in Customizing under Cross-Application Components in activity
Maintain Attachment Type Schema.
If you want to attach additional file types, you must add the corresponding MIME types manually.
For example, if the standard settings only allow you to attach PDF files for a given business object,
you can add a MIME type that allows you to attach a Microsoft Word file (MIME Type:
application/msword). If you want to create your own attachment schema, you must assign it to the
respective BO node.
Dynamic Creation of Statements
Assign Assistant Classes to Business Objects
Use
In this Customizing activity, you can enable the dynamic creation of statements for a business object
(BO) by assigning an assistant class to the BO.
Requirements
For each business object for which you want to use the dynamic creation of statements, you have to
create an assistant class in transaction SE24 (Class Builder) and assign it to the BO in this Customizing
activity.
Note: The assistant class has to implement the interface IF_EHFND_DSC_ASSIST (Dynamic Creation
of Statements: Interface for Assistant Class).
Standard settings
Activities

Example
You can use assistant class CL_EHFND_CHM_DSC_ASSIST (Assistant Class for Dynamic Creation of
Statements) for the chemical BO as an example for implementing you own class.
Enable BO Fields for Dynamic Creation of Statements
Use
In this Customizing activity, you can specify business object fields (attributes) that are enabled for a
dynamic creation of statements.
You need to enter the business objects, the name for Customizing table in which the statements are
stored, and the alias of the OTR text. This text will be displayed on the manage statements screen.
Requirements
If you want to enable the dynamic creation of statements for fields other than the delivered ones, the
following activities are required:
- You have to assign an assistant class for the business object in Customizing activity Assign
Assistant Classes to Business Objects.
- For each persistent code field that you want to use for dynamic creation of statements, you have to
create a transient description field at the same node of the BO in transaction /BOBF/CUST_UI
(BOPF Enhancement Workbench). In transaction SE11 (ABAP Dictionary Maintenance), you also
need to create a corresponding data element using the naming convention *_DESC.
Note: To define the value of this transient field, you must create a determination at the node using
the naming convention: *_DSC_SET_TRANS_ATTR). For implementation of a determination,
you can use the generic class CL_EHFND_DSC_D_TRANS_ATTR. For the data element for the
transient field, you have to create a search help that uses
EHFND_SEARCH_CASE_INSENSITIVE as search help exit.
- You have to create a Customizing table in which you want to store the statements.
- You have to create an OTR text in transaction SOTR_EDIT (Editor for OTR Texts).
- Standard settings
Activities
To create new entries, proceed as follows:
1. Enter the business object for which you want to enable the dynamic creation of statements.
2. Select a corresponding node from the F4 value help.
3. Select a corresponding attribute from the F4 value help.
4. Enter the name of the transient description field.
5. Enter the name for Customizing table in which the statements are stored.
6. Assign an OTR-Alias
Note: You have to check authorizations for authorization object EHFND_DSC (Dynamic Creation of
Statements) and attribute EHFND_DSCC.
Process Foundation
Basic Settings
Specify RFC Destination for System Callback
Use
In this Customizing activity, you can define an RFC destination for system callbacks. This RFC
destination is used for launching applications and dialog boxes (such as task management) from e-mails
and from transactions such as SAP Business Workplace.
In addition, this destination is used to open the same set of applications from transactions such as SAP
Business Workplace.
If you do not define an RFC destination, the system does not know whether you want to open an
application in the NetWeaver Business Client or in the Enterprise Portal.
Activities
- Execute the activity and click on the folder HTTP Connections to ABAP System.
- Create a new connection by choosing the Create button in the toolbar.
- Enter SAP_EH_FW_WFF_REPORT_TARGET as connection name and enter a description.
- Enter the URL of the back-end system into the field Target Host.
- Enter the HTTP port of the application into the field Service No..
- Enter the following data in the field Path Prefix:
- /nwbc/<NWBC>, if you want to use the NetWeaver Business Client.
- /irj/portal<PORT>, if you want to use the Enterprise Portal.
- Save your new created destination.
Note: The connection test does not work due to the braced statements <NWBC> or <PORT> in the path
prefix setting. These placeholders will be replaced by the correct parameters at runtime.
Maintain Archive Retrieval Settings for Workflows
Use
In this Customizing activity, you can define settings for retrieving archived workflows. To read archived
workflows, the system must be configured to index these workflows.
Requirements
You have completed the automatic workflow customizing in transaction SWU3.
Activities
To define the workflow retrieval settings:
1. Open transaction SARI or execute this Customizing activity.

2. Choose the Customizing button.
3. Create a new entry and provide the following information:
- Infostructure: WORKITEM
- Archiving Object: WORKITEM
- Field Catalog: SAP_O2WI_001 or SAP_BO2WI_001
4. Include all the available fields in your infostructure and save your entries.
5. Return to the entry screen and activate your infostructure.
A database table is created automatically. This database table is used by transaction SARA and also the
task management functionality in Environment, Health, and Safety and Product Safety and
Stewardship to retrieve information about archived workflows.
Perform Automatic Workflow Customizing
Use
In this Customizing activity, you can perform automatic customizing for workflows. The activity is
mandatory if you use the processes of the components Environment, Health, and Safety and Product
Safety and Stewardship. If you do not perform this activity, the process foundation cannot support
your business processes.
Activities
Select the top node of the first section and choose the Perform Automatic Workflow Customizing
button or F9. Perform this step for all subsequent sections.
To run Environment, Health, and Safety or Product Compliance for Discrete Industries, ensure
that the following settings were made: - Maintain Runtime Environment: all settings -
Maintain Definition Environment:
- Check Number Ranges
- Maintain Additional Settings and Services:
- Maintain Standard Domain for Internet Mail
- Activate Send to Objects and HR Objects
- Maintain Demo and Verification Environment - Classify Tasks as General: all
settings - Guided Procedures:
- Maintain Generation of Standard Tasks
- Classify Generic Standard Tasks as General
When you choose to perform automatic workflow customizing, only those activities that currently have
the error status are executed automatically. If an activity still has the error status after performing
automatic workflow customizing, you may need to make additional settings, and perform automatic
workflow customizing again or manually perform customizing.
Processes
Specify Process Definitions
Use
In this Customizing activity, you can specify the process definitions for processes handled by the
process foundation. You can also exclude existing processes from process monitoring and process
analysis.
You can use the process definition to specify the workflows that are available where and when you want
them in the application. You can also create a variant of a standard workflow to accommodate variations
of the process. Be aware that the UI refers to Tasks for simplicity, but tasks are part of processes. For
example, when a user creates a task in the application, the system creates a process instance in the back-
end system.
A process definition consists of the following information:
- Component
- Purpose
- Variant
- PCO class
Requirements
You have set up the workflow system in the one of the following Customizing activities:
- For Environment, Health, and Safety: Perform Automatic Workflow Customizing

- For Product Safety and Stewardship: Perform Automatic Workflow Customizing
If you want to extend your processes with additional functionalities in the SAP Business Workflow,
you have implemented a customer-specific PCO class to handle the process. For more information about
extending or changing the PCO class, see one of the following Customizing activities:
- For Environment, Health, and Safety: Extend and Adapt Process

- For Product Safety and Stewardship: Extend and Adapt Process
Standard settings

You can use the standard process definitions and their corresponding workflows to support your business
processes. If you want to adapt the processes or the workflows, you can change the process definitions to
incorporate the adaptions. We recommend that a system administrator or a person with the necessary
experience in adapting workflows and developing classes is involved in making the settings in this
Customizing activity.
Activities

3. If necessary, select the Exclude checkbox to exclude a process from process monitoring and
analysis.
Example
The standard system is delivered with a process definition for the offline investigation step. The elements
of this process definition are explained in the following text:
- Component: Health and Safety

The applications in the health and safety component, such as incident management or health and
safety management, can use this process definition.
- Purpose: INC_INVESTIGATION_STEP
The process definition supports the processing of a step in the incident investigation.
- Process Variant: OFFLINE

The process definition is available in an offline situation. In the offline variant, the system sends an
inquiry form via e-mail. The recipient can fill the form out offline and send it back.
- PCO Class Name: CL_EHHSS_PCO_INC_INQUIRY

This PCO contains the logic for creating an inquiry form, sending the form as an e-mail to the
person responsible for the investigation step, and handling the form once it is returned to the
system.
Activate Linkage for Scheduled Processes
Use
In this Customizing activity, you can activate the event type linkage to link the event creator and the
event receiver for scheduled processes.
When you schedule an action or notification in the application, you can schedule the task, for example, to
recur every week for a year. In the system, the task is part of a process that must be scheduled and
triggered again to occur the following week. By activating the event type linkage, you allow a central
user with batch administration authorizations (WF-BATCH) to schedule and trigger the corresponding
process for the task.
You must activate the linkage, so that the central user (event receiver) can schedule and trigger the
processes for the user (event creator) that created and scheduled the action or notification originally.
Standard settings
The standard system is delivered with the event type linkage deactivated.
Activities
For the following object, activate the event type linkage:

Object Category: ABAP Class
Object Type: CL_EHFND_SCHEDULER_REPLANNER
Event: TRIGGER_REPLANNING
Specify Templates for Task Notification
Use
In this Customizing activity, you can configure templates for notifications that you send manually from
task management. You can specify the text source (a standard task from SAP Business Workflow) and
assign templates to processes. If you assign a template to a specific process, the template is only
available when you send notifications related to that process. Unassigned templates are available for
notifying processors of any task.
You can use templates to standardize notification texts and reduce the effort involved in notifying task
processors. Within these templates, it is possible to include variables from the workflow, work item
container, and from the process control object (PCO). It is recommended to use the same (or extended)
PCO class for the template as for the process itself. This enables you to include the variables that are
needed for the process.
Requirements
- You have experience using SAP Business Workflow.

- You have specified process definitions in Specify Process Definitions, and are familiar with their
corresponding workflows in Workflow Builder. Note that the PCO class is the link between a
process and a workflow.
- You have created or edited standard tasks in transaction PFTC_INS or PFTC_CHG, respectively.
Standard settings
Activities

Example
You want to notify a processor to remind him or her about a reporting task. In Customizing, you have
specified the two following templates:
- Report Verification - The template uses a standard task that requires the processor to verify that a
report is relevant for legal authorities.
- Report Generation - The templates uses a standard task that requires the processor to generate a
legal report manually.
You have assigned the templates to the process for reporting, and selected the report verification template
as the default.
In the application, you select a reporting task and choose the Notify Processor pushbutton. The system
opens a notification screen and fills the text fields with the report verification template's text.
BAdI: Create and Initialize PCBOs
Use
This Business Add-In (BAdI) is used in the components Environment, Health, and Safety and
Product Safety and Stewardship. You can use this BAdI to implement customer-specific logic to
adapt the processes in the system. You can use this BAdI, for example, if your organization must comply
with regulatory requirements in more than one country or region. You can create a variation of the
process for a specific country or region.
The PCBO creation BAdI is called each time the system creates a process control business object
(PCBO).
Requirements
You have made settings in the following Customizing activities:

- Specify Process Definitions
- List Configured Processes
- For Product Safety and Stewardship:
- List Configured Processes
You have performed a consistency check without errors in the Customizing activity
Standard settings
This BAdI does not have a default implementation.
Checks and Tools

Check Configuration of Workflow System
Use
In this Customizing activity, you can perform several checks on the workflow system that is used in the
process foundation.
Upon executing the activity, the checks are run and the result is displayed.
If the checks are successful, the system is set up correctly and you can execute the processes in the
components Environment, Health, and Safety and Product Safety and Stewardship.
Requirements
You have performed the following Customizing activities:

For Environment, Health, and Safety:
- Perform Automatic Workflow Customizing

For Product Safety and Stewardship
- Perform Automatic Workflow Customizing

List Configured Processes
Use
In this Customizing activity, you can display a list of the process definitions in the Environment,
Health, and Safety component. From this list, you can view the status, the instances, and the technical
information of process definitions. This helps you ensure that the process definitions are configured
correctly.
Requirements
You have specified process definitions in the Customizing activity Specify Process Definition for
Foundation for EHS.
Standard settings
The system displays the configured processes automatically using the report
R_EHFND_WFF_PROCDEF_LIST.
Activities
Choose the Status traffic light icon to display details about the status of the configured process
definition. The system displays the results of the process definition check in the report
R_EHFND_WFF_PROCDEF_CHECK.
Choose the List icon to display a list of the instances of the specified process in the report
R_EHFND_WFF_PROCESS_LIST.
Choose the Info icon to display technical information about the selected process in the report
R_EHFND_WFF_PROCDEF_INFO.
Extend and Adapt Processes
Use
In this activity, you can learn about how to extend and adapt the process foundation in the components
Environment, Health, and Safety and Product Safety and Stewardship to suit your customer-
specific business processes. You can make the following changes:
- Adapt existing processes

- Add data fields to the PCBO
- Add new variants of a process definition
- Change the BAdI implementation for PCBOs
- Extend or change the PCO class for a process
Activities
To extend and adapt processes in the following ways, perform the activities described below:
Adapt Existing Processes
1. Create a copy of the workflow template in the Workflow Builder that you want to modify.
2. Make the desired changes in the copied template.
Note that if you add customer-specific dialog steps and these step appear in the user's inbox, you
must configure the corresponding tasks in the workflow inbox. Changes to workflow templates can
also affect how tasks are displayed in the system. For more information, see Note below.
3. Activate the event binding for the CREATE event of the corresponding PCO class.
4. Disable the event linkage for the old workflow template to prevent creating two workflow instances
when the event occurs.
Add Data Fields to a PCBO
You can add customer-specific data fields to a process control business object (PCBO) by modifying the
extension structure in transaction SE11.
Add New Variants of a Process Definition
You can create customer-specific variants of processes by adding a new definition with your own variant
name.
For more information, see the following Customizing activities:
- For Environment, Health, and Safety: Specify Process Definitions

- For Product Safety and Stewardship: Specify Process Definitions
Change the BAdI implementation for PCBOs
To change the implementation of the BAdI for the creation of the PCBOs, you can do one of the
following:
- Extend the default implementation CL_EHFND_WFF_DEF_PCBO_CREATION and add the

required methods or overwrite existing ones.
- Implement the IF_EHFND_WFF_PCBO_CREATION interface.
After you have implemented the class, configure it in the BAdI.
For more information about implementing the BAdI, see the following Customizing activities:

- BAdI: Create and Initialize PCBOs (PCBOs)
- BAdI: Create and Initialize PCBOs (PCBOs)
Extend or Change the PCO Class for a Process
If you want to implement a customer-specific PCO, you can do one of the following:
- Inherit and then modify the class of an existing purpose and variant that is delivered in the
standard system (recommended).
- Create an own implementation of a PCO class by implementing the interface
IF_EHFND_WFF_PCO, or by extending the abstract base class for the PCO class
CL_EHFND_WFF_ROOT_PCO.
After you create the PCO class, enter it in the Customizing activity Specify Process Definition for the
relevant process definition.
Note
If you create a new version of a workflow template, any tasks already performed based on the previous
version of the template can still be displayed during a search on the Tasks menu or in analytical
dashboards. However, if you create a new template, any tasks created with the previous template are no
longer displayed in the system.
Environment, Health, and Safety and Product Safety and Stewardship use the POWL-based inbox.
If you adapt processes and the corresponding workflow templates, you must configure the tasks in the
workflow inbox in Customizing for Cross-Application Components under Processes and Tools for
Enterprise Applications -> Inbox.
See also the corresponding process component to obtain the correct application ID and POWL type for
the workflow inbox.
Print Forms and Interactive Forms
Specify Forms
Use
In this Customizing activity, you can specify the following:
- SAP Interactive Forms by Adobe

Forms contain data for a business object. You can use forms, for example, in legal and internal reporting
or as inquiry questionnaires.
In this Customizing activity, you can specify and configure forms to integrate them into the application.
You can also assign the languages in which the forms are available. Each form can exist in multiple
languages. The available languages are determined dynamically at runtime. If you need the form in an
additional language, you can translate it using transaction SFP and choosing Goto -> Translation.
Furthermore, you can specify one language as a fallback language. If the requested language is not
available, the system uses the fallback language.
If you use the form to collect user input (such as an inquiry), the form contains a pre-defined e-mail
address that should receive the content, once the form is filled out and sent back by the user. In this
Customizing activity, a system administrator can define the e-mail address that is included in the form.
If you use a form that includes scripts, you have to assign it to the form category Dynamic
Questionnaire. Otherwise, the scripts will not be processed.
- Custom document types

Document types provide means for classification of documents.
In this Customizing activity, you can specify custom document types that you can integrate into the
application. You can use the document types to group and classify attached documents. Additionally, the
document type enables you to control the access to the corresponding documents. You can grant or
revoke access to specific groups of documents depending on their type.
For example, in incident management you can classify the documents that you attach to the incident
record of an injured person. Documents of type Medical Document can potentially contain private
information that must not be displayed publicly. Thus, by manipulating the security settings of the
document type (using the corresponding authorization profiles) you can grant access to medical
documents to particular users only.
To specify a custom document type, you can create an entry in the table and set the Unknown
Document form type to it.
Requirements
The configured classes (Form Controller, Data Provider and, if relevant, the Inbound
Persister) must be available and active. Furthermore, the Form Object (Form Repository Object of
transaction SFP) must be active and the corresponding interface structure must be the same as the one
that is returned by the GET_DATA method of the Data Provider.
If the form requires a response e-mail address, you have defined the address in the Customizing activity
Define Inbound Processing for E-Mail (under Incident Management -> Print Forms and
Interactive Forms and under Health and Safety Management -> Print Forms and Interactive
Forms). When you configure the e-mail, you specify the class (exit handler) that processes the data that
is returned in the form for this e-mail address.
Standard settings
Note that the German accident notification form (BG_UNF_BER) is available in German only. You must
be logged on in German to use the form.
Activities

3. If the form is a questionnaire and you would like to store the data within an inquiry process, define
the Inbound Persister.
4. If the form contains a Send pushbutton (such as a questionnaire), enter a response e-mail address
that receives the returned form.
5. If required, set the form popup name.
6. If a dialog for accepting the data exists, you can also add the Configuration for Accepting Data to
use a specified Web Dynpro configuration ID.
Example
The following example describes the definition of an SAP Interactive Form by Adobe.
- Form name: INC_INFO_WITNESS

- Description: Incident Information Questionnaire for a Witness
- Form type: SAP Interactive Form
- Form category: Questionnaire
- Form creation controller: CL_EHFND_FW_ADS_FORM_CR_CTRL
Specifies a class that enables you to create, manipulate and store SAP Interactive Forms by Adobe.
- Data provider: CL_EHHSS_AIF_INC_WITN_Q_DPROV

A data provider is used to extract persistent data and to create the interface structure for the form.
- Name of form object: EHHSS_INC_AIF_INC_WITN

Specifies the name of the form object that is used as a template for the offline form that is
configured in this activity. You create the form object in transaction SFP.
The following example describes the definition of a custom document type.
- Form name: MEDICAL

- Description: Medical Document
- Form type: Unknown Document (cannot be created)
- Form category: <empty>
- Form creation controller: <empty>
- Data provider: <empty>
- Name of form object: <empty>
Specify Form Groups and Assign Forms
Use
In this Customizing activity, you can define into which groups you want to subdivide forms and assign
each form group to a component.
In a second step, you assign forms to the defined form groups. In the incident recording, these form
groups allow an easier selection of the required form. For example, if you want to send an inquiry, you
can select only a form of the inquiry form group instead of all available forms in the system.
One form group can contain multiple forms. For an automatic selection, you can define one form of a
group as a default form.
Requirements
In Customizing, you have defined the available forms.
- For Environment, Health, and Safety under Specify Forms

- For Product Compliance for Discrete Industries under Specify Forms
Standard settings
Activities
1. Define a logical name and a description for the form group.

2. Assign a component for the form group.
3. Select a form group and choose Assign Forms to Form Group.
4. Assign the forms and select a default form, if necessary.
Define Inbound Processing for E-Mails

An e-mail inbound process is often required in the components Environment, Health, and Safety and
Product Safety and Stewardship. For example, the recipient of an inquiry completes a form and sends
it back to a defined e-mail address. When the e-mail is received in the system, the system calls an exit
handler (functional class) that automatically reads the attached form, and then sends the information to
the corresponding workflow. The system attaches the returned form to the relevant workflow and the
business process continues.
In this Customizing activity, a system administrator can define an e-mail address that should receive the
relevant form and then binds an exit handler to that e-mail address. Thus, the system administrator
defines how the system processes such inbound e-mails.
Requirements
You have configured the inbound e-mail address for each form in the one of the following Customizing
activitie:
- For Environment, Health, and Safety: Specify Forms

- For Product Safety and Stewardship: Specify Forms
- Your company's e-mail system is set up in such a way that it forwards the e-mail to the components
Environment, Health, and Safety and Product Safety and Stewardship based on the e-mail
address that is configured for the form.
- You have assigned the e-mail recipient PFCG role to the user that processes incoming e-mails
(default user is SAPCONNECT). This role contains the authorization profiles needed to receive and
process e-mails. You can find the user ID that is assigned as the user for processing incoming e-
mails in the SMTP Host node in transaction SICF. E-mail recipient PFCG role for incident
management: SAP_EHSM_HSS_EML_REC E-mail recipient PFCG role for health and safety
management:
SAP_EHSM_HSS_EML_REC
Standard settings
There is a default exit handler that logs the e-mails that are received using the SAP Application Log. You
can use transaction SLG1 to view the log.
Incident Management
- Exit handler: CL_EHHSS_INC_INB_PROC_BCS

- Object: EHHSS_BO_INC
- Subobject: EHHSS_AIF_INC_INBD
Health and Safety Management
- Exit handler
- General: CL_EHHSS_RAS_INB_PROC_BCS
- Control Inspections: CL_EHHSS_CINSP_INB_PROC_BCS
- Object: EHHSS_BO_RAS
- Subobject: EHHSS_AIF_RAS_INBD
Activities
In this Customizing activity, you specify the following parameters:
- Communication Type: Internet Mail

- Recipient Address: Specify the e-mail address that you configured for the corresponding form in
Specify Forms. If you use an asterisk (*) as the value, this inbound handler is called for each e-
mail address. However, it is recommended that you use the e-mail address that you configured.
- Document Class: *
- Exit Name
- Incident Management: CL_EHHSS_INC_INB_PROC_BCS
- Health and Safety Management: CL_EHHSS_RAS_INB_PROC_BCS (general),
CL_EHHSS_CINSP_INB_PROC_BCS (control inspections)
If you want to change how the e-mail exit handler behaves, you can create your own implementation that
inherits from the default class.
To do this:
1. Go to transaction SE24.
2. Create a new class that inherits from:
- CL_EHHSS_INC_INB_PROC_BCS for incident management
- CL_EHHSS_RAS_INB_PROC_BCS for health and safety management
- CL_EHHSS_CINSP_INB_PROC_BCS for control inspections in health and safety

management
3. Modify the HANDLE_FORMS method.
Integration
Specify Destinations for Integration
Use
In this Customizing activity, you can specify destinations for integrating other SAP components into the
Environment, Health, and Safety component or into the Product Compliance for Discrete
Industries component. You can access the data in those components directly on your local system or
using an RFC connection to a remote system. Some data is available only on the local system.
Access to Data Available via a Remote System
If you want to use data that is stored in a remote system, you can specify the RFC destinations
individually in this activity.
You can integrate the following components:
- Business Partner
- Human Resource Management
- Plant Maintenance
- Extended Warehouse Management
- Inventory Management
- Accounting
- SAP EHS Management as part of SAP ERP
- SAP Management of Change
Note: For Product Compliance for Discrete Industries it is sufficient to use only the available data
via your local system.
Access to Data Available via the Local System Only
The system cannot read some data via remote access, such as data from Customizing, data from the
Materials Management (MM) component, and specific data from components that you may have
already integrated. You can access this data via the local system only. For more information about the
data that you cannot access via remote access, see Notes below.
Requirements
You have defined RFC connections of connection type 3 (ABAP connection). To check and define RFC
connections, on the SAP Easy Access screen, choose Tools -> Administration -> Administration ->
Network -> RFC Destinations or open transaction SM59. You can specify a customer-specific name
for the RFC destination.
Note: To maintain RFC connections, you require authorization object S_RFC_ADM and
permissions for activities 01, 02, 03, and 06 (insert, modify, show, and delete). The user that needs
to be able to read RFC connections at runtime, requires permissions for activity 03 (show).
You have ensured the following:
- You are using R/3 Enterprise 40 Extension Set 20 (Basis 620) or higher for the remote system of all
other systems.
Standard settings
The standard system is delivered without RFC destinations. You can access data from the local system
only.
Activities
To access data from a remote system, perform the following steps:
1. Choose the remote system for the destination type.

2. Enter an existing RFC destination (connection type 3) for the specified remote system. Note: The
remote system for PM assets, PM notifications, and PM orders is always the same system.
If it is necessary to improve performance when integrating to a remote PM system, you can create
customer-specific indices on the remote PM system. The following are example indices that you can
create:
- Table EQUI: Create an extension index with fields EQUNR and EQART.
- Table IFLOT: Create an extension index with fields TPLNR and EQART.
- Table ILOA: Create an extension index with fields ILOAN and SWERK.
Notes
You must access certain data directly on a local system. To make this data available on the local system,
you can distribute it, for example, using an Application Link Enabling (ALE) or by replicating data from
Customizing. The following is a list of the data required on the local system and the table or object where
it is located:
Data Required in Local System for Environment, Health, and Safety Processes
Table/Object
Business partner roles Tables TB003, TB003T
Plants and plant descriptions
Material and material description Material number and material description from the material
master Currencies and exchange rates
Notification types for PM Table TQ80
Attendance and absence types Table T554S and T554T
Marital status texts for HR persons Table T502T
Marital status texts for business partners Table TB027T
Attendance and absence types
Shift group and shift planning of the organizational unit Info type 1039 and tables T77DB,
T77DT, T77ED, T77ET
Organizational data, including organizational units and persons in PA-OS Table T554S
Positions in PA-OS Table HRP1000
Note that to make organizational data from PA-OS available in the local system, you can distribute the
relevant HR master data between the PA-OS system and the Environment, Health, and Safety system.
However, since the EHS applications only require specific PA-OS data, a distribution limited to the basic
info types is sufficient. The distributed organizational data cannot be changed from the EHS applications
as the system settings only allow read access.
The assignment of a user to employee (info type 0105) for workflows must be done in the HR system.
The users must be maintained in the local system.
Data Required in Local System for Product Compliance Processes Table/Object

Business partner roles Tables TB003, TB003T
Plants and plant descriptions Table T001W
Material and material description the Material number and material description from
material master
Suppliers and contact person details Services Table KNVK and tables in Business Address
Purchase Info Records Table EINA with referenced foreign tables

Approved manufacturer part list Table AMPL
Source list Table EORD
Bill of material Tables MAST, STAS, STKO, STPO, STZU, and
TCGBA with referenced foreign tables
Specify Notification Types
Use
In this Customizing activity, you can specify notification types to use in the Environment, Health, and
Safety component. You must specify the notification types here in order to choose the maintenance
notification categories later in the application.
Requirements
You have defined notification types that you want to use in Environment, Health, and Safety in the
Customizing activity Define Notification Types for Cross-Application Components.
You have specified destinations for the integration of the Plant Maintenance (PM) component in the
Customizing activity Specify Destinations for Integration for Foundation for EHS.
The following requirements apply only to the notification types that you want to use in Environment,
Health, and Safety:
1. You have not defined any allowed changes for the desired notification types in the Customizing
activity Allowed Change of Notification Type for Cross-Application Components.
2. You have ensured that the desired notification types contains tasks in the Customizing activity
Define Screen Templates for Cross-Application Components. For each action or notification in
Environment, Health, and Safety, one task is created in the notification. The task will be filled
with the following:
Sort number: 1 (constant)
Task text: Task description (short)

Task long text: Task description
3. You have ensured one of the following with respect to mandatory fields in notifications:
- The desired notification types do not contain any mandatory fields in the Customizing
activity Define Screen Templates for Cross-Application Components. If you have
specified mandatory fields that do not exist in Environment, Health, and Safety, the user
cannot create a notification and receives an error message.
- Fields that you want to be mandatory exist in Environment, Health, and Safety, are visible
on the user interface, and are set as mandatory in the Customizing activity Specify Field
Control for Foundation for EHS.
4. You have ensured that the desired notification types have internal (and not external) number range
assignments.
Standard settings
Activities

Schedule Job for Notification Status Check
Use
In this Customizing activity, you can schedule jobs to check whether notifications have been completed
in other components, for example, in the Plant Maintenance (PM) component.
When you create a notification in the Environment, Health, and Safety application, the notification is
communicated and initiated in the corresponding component using the notification process. The system
uses the report Check for Completed Notifications
(R_EHFND_CHECK_COMPL_EXT_NOTIF) to monitor the status of each notification process until it is
completed. Once the notification has been completed, the report triggers the next process step to create a
task for the approver to complete the notification in the application.
Activities
1. In the activity, use the Job Wizard to specify the general data and schedule the job. You define the
job for the report R_EHFND_CHECK_COMPL_EXT_NOTIF.
2. Schedule the job to run at regular intervals, such as once a day.
Human Resources Integration
Check Authorizations for Person Information
Use
In this activity, you can learn about the organizational activities necessary for accessing data within the
Environment, Health, and Safety component or people and organizations that you already manage in
other SAP components.
In Environment, Health, and Safety, you can use the data managed in the SAP Human Resources
Management (HR) component and the SAP Business Partner (BP) component. For employees and
applicants, the data is managed in HR. Because this data is of a sensitive nature, it is protected by a
comprehensive authorization concept. For external parties who are not managed in HR, the data is
managed in BP.
Standard settings
The standard system is delivered with active integration to the Personnel Management (PA) and the
SAP Business Partner component. Integration with the Personnel Time Management (PT)
component is not activated in the standard system.
Activities
Environment, Health, and Safety uses the settings and authorizations that you have already maintained
in the integrated systems. To ensure that you have access to the required data for Environment, Health,
and Safety, ensure that you have performed the following activities:
1. Check the settings of the following authorization objects:
- HR: Master data (P_ORGIN)

Check whether display authorizations are entered for the following infotypes:
- 0000 Actions
- 0001 Organizational assignment
- 0002 Personal data
- 0006 Addresses
- 0007 Planned working time
- 0013 Social insurance D
- 0105 Communication
Note: To use the Choose Me function in incident management, ensure that the subtype
System user name (SY-UNAME) for communication contains your user name.
- 2001 Absences
You can change the settings for absences, if necessary. For more information, see Check Time
Management Customizing.
- 2002 Order notification (attendances)

- 2003 Substitutions: individual working time - 2005 Overtime
- HR: Master data - extended check (P_ORGXX)
Ensure that the check by the authorization object HR: Master Data - Extended check
(P_ORGXX) is activated. P_ORGXX can be used in addition to or instead of the check by the
authorization object HR: Master Data. In the standard system, the check is not active.
- HR: Applicants (P_APPL)

Check whether display authorization exists for the following infotypes:
- 0001 Organizational assignment

- 0002 Personal data
- 0006 Addresses
- 0105 Communication
- Business partner: BP roles (B_BUPA_RLT)
Check whether the required authorizations exist for the BP roles used (processing; possibly display
only), and for at least the following roles:
- CBIH10 External person

- HEA010 Physician
- HEA030 Health center (hospital)
- Business partner: field groups (B_BUPA_FDG)
Using this authorization object, you can set up a special authorization check for individual field
groups in the business partner dialog box.
2. Check the settings for structural authorization profiles.
- If you use structural authorization profiles, ensure that you have granted authorizations accordingly
to Environment, Health, and Safety users for objects that are stored in a hierarchical structure.
You can assign authorization profiles in activity Assign Structural Authorizations.
Specify Relevant Subtypes for a Party Infotype
Use
In this Customizing activity, you can assign relevant subtypes of infotypes required in the Environment,
Health, and Safety component.
For example, you configure the subtype of the infotype 0105 (Communication) where you define the e-
mail address in Human Resources (HR).
Standard settings
Activities
Check the existing examples and adapt them as required:
- For the subtype to read the relevant address (infotype 0006), define the subtype of HR addresses
(infotype 0006) that is relevant for Environment, Health, and Safety.
- For the subtype to read the relevant e-mail (infotype 0105), define the subtype of HR
Communication (infotype 0105) that includes the relevant e-mail address for Environment,
Health, and Safety.
- For the subtype to read the relevant fax number (infotype 0105), define the subtype of HR
Communication (infotype 0105) that includes the relevant fax number for Environment, Health,
and Safety.
Specify Person Groups and Contractual Relationships
Use
In this Customizing activity, you can define the person groups and contractual relationships that an
involved person can be assigned to.
You can assign employee groups, employee subgroups, or business partner roles to person groups. By
making these settings, you specify the contractual relationships that are required for some legal reports,
for example, the German accident notification.
Based on the assignment of employee groups, subgroups, and business partner roles to person groups, the
system determines the person group of an involved person automatically in the application. In addition,
you can change the person group in the application manually.
Requirements
You have defined the employee groups and employee subgroups in the Customizing activities for
Enterprise Structure under Definition -> Human Resources Management -> Employee Groups
and Employee Subgroups.
You have defined business partner roles in Customizing for Cross-Application Components under
SAP Business Partner -> Business Partner -> Basic Settings -> Business Partner Roles ->
Define BP Roles.
Standard settings
Activities

The system determines person groups according to the following rules:
- Applicant (EHFND_PGR_APPLICANT)
The person group applicant is determined if you enter an involved person that is an applicant with
HR master data (maintained in HR transaction PB30, for example). For this entry, you do not need
to maintain detailed data in this Customizing activity.
- Apprentice (EHFND_PGR_APPRENTICE)
An apprentice is a subgroup of employees that are maintained in HR master data (maintained in HR
transaction PA30, for example). For this entry you should maintain detailed data about the
employee group and employee subgroup. All employees with the employee group and employee
subgroup specified in the detail are determined as an apprentice.
- Contractor (EHFND_PGR_CONTRACTOR)
A contractor can be a HR person or a business partner. Ensure you specify the employee groups and
employee subgroups and business partner roles.
- Employee (EHFND_PGR_EMPLOYEE)
Employees are HR persons with HR master data (maintained in HR transaction PA30, for example).
It is not necessary to maintain details. All HR persons are determined as employees if they are not
already determined as an apprentice or a contractor
- External Person (EHFND_PGR_EXT_PER)

External persons are business partners. You do not need to specify details for these persons.
Example
The settings for the Apprentice (EHFND_PGR_APPRENTICE) person group have the following
assignments:
- Employee group: 1 (active)

- Employee subgroup: B7
When you enter a person in Environment, Health, and Safety that is an employee (or person whose
data is stored in the HR component) that has the employee group 1 and employee subgroup B7, the
system determines the Apprentice person group.
BAdI: Change Party Address Data
Use
This Business Add-In (BAdI) is used in the Environment, Health, and Safety component. You can use
this BAdI to enhance the standard delivery when you want to get and display personnel data that is read
from an integrated HR system.
When you report or review an incident, you can specify involved persons. Once a person is specified, the
incident management application displays information about that person, for example name, telephone
number, e-mail address, and so on. When the involved person is specified from an integrated HR system,
the application reads the corresponding subtype for a party infotype and gets the information directly
from the HR system.
Using this BAdI, you can implement your own business logic to handle the information from the
subtypes of a party infotype. Thus, you can enhance the standard delivery and get (and display) further
details for the involved person.
By default, the standard system gets and displays information for an involved person from the following
subtypes of the 0105 Communication infotype:
- 0005 Fax
- 0010 E-mail
- 0020 First telephone number at work

- CELL Cell Phone
- MPHN Car phone/other mobile phone

Note: Environment, Health, and Safety features a functional module
(EHFND_PARTY_PROXY_APPL_0105) that handles the required information on the remote HR
system and accesses that information over an RFC destination. To be able to pull and display
HR data in the incident management application, you should install the
EHFND_PARTY_PROXY_APPL_0105 function module on the HR system.
Standard settings
The BAdI is intended for multiple uses and is not filter-dependent. This BAdI is inactive in the standard
system and uses the following method:
BAdI Method
- CHANGE_PARTY_ADDRESS_DATA - Change Party Address Data
Change Parameter
- CT_PARTY_ADDRESS - Party Address Data
This change parameter can manipulate the following components (fields):
Component Description
STREET_HOUSE_NUM Street / House Number Concatenated
POSTAL_CODE City Postal Code
CITY City
STATE_CODE Region
STATE_DESC Region Description
COUNTRY_CODE Country
COUNTRY_DESC Country Description
TELEPHONE_NUM Telephone Number
E_MAIL E-Mail Address of Party
TELEPHONE_NUM_PRIVATE Private Telephone Number
TELEPHONE_NUM_MOBILE Mobile Telephone Number
TELEPHONE_NUM_MPHN Mobile Telephone Number
STREET Street Address
HOUSE_NUM House Number
FAX_NUM Fax Number
This BAdI definition uses the IF_EHFND_PARTY_ADDRESS_DATA interface.
File-Based Reporting
Configure General Settings
Use
In this Customizing activity, you can specify general settings for the file-based reporting.
You can define a limit for e-mail attachment size and the lifetime of reports for download in days for
background generation of file-based reports.
Requirements
You have defined threshold for background exporting in the Customizing activity Define Export
Profiles.
To use the download service for reports, you must activate the ICS service under
/sap/ehsm/file_download in transaction SICF.
Standard settings
The standard system is delivered with examples. Default maximum e-mail size is one MB; default time
until generated reports are deleted is five days.
Specify File Formats
Use
In this Customizing activity, you can specify the file formats, in which a report can be generated. The
specified file formats are used in the Customizing activity Define Export Profiles to create export profiles
for file-based reporting.
You can set the Template flag for each file format. This flag indicates that thefile format supports
template files.
Note: You can use the Customizing activity Define Export Profiles to upload a template file.
Requirements
For each specified file format, a BAdI implementation has to be available in the Customizing activity
BAdI: Generate Export Files.
Standard settings
Specify Data Selections
Use
In this Customizing activity, you can specify the data selections for file-based reporting.
The data selection is independent of any file format or export purpose and thus can be reused for
different export profiles.
The business object nodes selected for a data selection specify a tree-like hierarchy. You have to select
one lead business object whose topmost node, the ROOT node, represents the root of the hierarchy.
Based on the ROOT node of the lead business object, you can select associations with child nodes. For
these child nodes, you can select associations with further child nodes. This first selected child node will
become the parent node of further associated child nodes. This way, you can build up a node hierarchy.
For each associated node, you can select the fields from which you want to export data. The data
extracted from these fields is combined in one data selection.
Note: To get a denormalized table in the generated report, only one node on each node level is allowed to
have a 1:n child node.
Standard settings
Activities
Check the existing examples and adapt them as required. If necessary, you can specify new data
selections. Proceed as follows:
1. Enter a unique ID for the new data selection.

2. Enter a description for the new data selection.
Note: In the case of a Microsoft Excel 2007/2010 report, this description is used as the sheet name.
In the case of a CSV report, this description acts as the CSV file name if more than one data
selection is configured for one export profile.
3. Enter the lead business object for the data selection.

4. Flag whether you want to include admin fields in your report and save your entry.
5. Select the newly created data selection and specify the hierarchy of business objects nodes in the
Node Structure view.
Note: By default, the root node of your lead business object is displayed in the first line. You can
create the node hierarchy by selecting the accordant associations. Use the F4 help to get only the
applicable associations.
6. For each line created in the Node Structure, select the Node Fields view to specify the single fields
to be extracted for this node. Enter the field name and a description or use
the F4 help to get all available fields for this node. You can enter a sort number to sort the columns
according to your needs. Use the Insert All Fields view insert all the fields of the current node the
table. You can remove or change the entries later. afterwards. Note: The field description is used as
column header in thereport.
Specify Export Profiles
Use
In this Customizing activity, you can specify export profiles for file-based reporting.
Each export profile has a lead business object. This lead business object is used to select the data
selections allowed for the export profile. Only data selections containing the same lead business object
can be assigned to the export profile.
You can assign more than one data selection in one export profile. The assigned data selections specify
the data to be extracted for the report.
In addition to the lead business object and the data selection, you have to specify the file format of the
resulting file. If the file format XLSX (Microsoft Excel 2007/2010) is used, the export profile can
contain an Excel template file that is used for the export. After the file upload, the name of the uploaded
file is displayed as file name. This file name can be changed later.
Furthermore, you can enter a threshold for background exporting to configure whether a report is
processed in foreground or in background.
Note: The EHFND_EXPP authorization object can be used to specify which user should be able to
generate file-based reports based on the configured export profile.
Requirements
You have entered general settings in the Configure General Settings Customizing activity.
You have specified data selections in the Specify Data Selections Customizing activity.
You have specified file formats in the Specify File Formats Customizing activity.
Standard settings
The standard system is delivered without export profiles.
Activities
To use the functions of file-based reporting, you have to specify profiles. To create an export profile,
proceed as follows:
1. Enter a unique ID for the new export profile.

2. Enter a description for the new export profile.
Note: This description is displayed in the export profile selection screen when you press the Export
button on the UI.
3. Enter the lead business object.

4. Select a file format from the F4 help.
5. If you want to upload a template file, go to the detailed view and press the F4 help in the Field
Name field. Note that the language of a template file has to match the system language when using
file-based reporting.
6. You can enter a file name for the export file. If no file name is specified, the name of the export
profile is used as the file name.
7. You can enter a threshold for background exporting.
8. You can decide if output conversions that are assigned to data elements of the fields contained in
the export have to be executed or not. If you select the Output Conversion checkbox, codes stored
in the database that reference entries in Customizing tables are automatically converted into the
corresponding language-dependent texts.
9. Save your entries and select the newly created export profile. Go to the Data Selections view and
use the F4 help to display all the data selections of the same lead business object that can be
assigned in this export profile.
10. Enter data selections and save your entries.
Note: The adjustment of Customizing entries is not supported for this Customizing activity because it
includes a file upload. If you need to set up Customizing in a different system or client, we recommend
that you compare your Customizing entries, edit the entries manually, and then upload the required files
again.
Alternatively, you can transport the entries via Customizing transport or use client copy (SCC1).
Business Add-Ins for File-Based Reporting
BAdI: Generate Export Files
Use
Product Safety and Stewardship. You can use this BAdI to export data form the application into
different file formats.
Each BAdI implementation corresponds to one file format, given by the filter value of the BAdI.
The BAdI definition is called for one specific export profile.
You can assign one or more data selections to each export profile. The data from these data
selections was exported in the selected file format and can be used for file-based reporting.
Requirements
You have made settings in the following Customizing activities:

- Specify File Formats
- Define Data Selections
- Define Export Profiles
- Specify File Formats
- Define Data Selections
- Define Export Profiles
Standard settings
The BAdI definition contains the following methods:
- INITIALIZE
This method is called once at the beginning of the export process. It initializes the file export.
- INITIALIZE_SECTION
This method is called once per data selection. It initializes a new data section within the export file.
- ADD_DATA_TO_SECTION
This method is called once for each data package that has been extracted. It adds the data package
to the data section of the export file.
If necessary, this method converts the extracted data to a denormalized table before writing the data
to the file.
- FINALIZE_SECTION
This method is called once per data selection after the last data package has been added to the data
section of the export file. It finalizes the data section within the export file.
- FINALIZE
This method is called once at the end of the export process. It finalizes the export file.
- VALIDATE_TEMPLATE_FILE
This method is called in Customizing and during generation of the export file to check whether the
uploaded template file is valid. The
- Customizing activity "Define Export Profiles" contains a check when saving the data which calls
this method to ensure that no technical problem occurs during report generation based on the
template file.
BAdI Implementations
- BADI_EHFND_EXP_CSV_GENERATOR
This implementation enables you to generate a CSV file with the extracted data.
If only one data selection is selected, the exported file is a CSV file.
If several data selections are selected, the exported file is a ZIP archive which includes one CSV
file per data selection.
- BADI_EHFND_EXP_XSLX_GENERATOR
This implementation enables you to generate a Microsoft Excel 2007/2010 export file, with format
XLSX, which contains the extracted data.
For each data selection, one sheet is created in the exported Excel file. Note: If you have
entered an Excel file template in the export profile, this template is used for generating the
export file.
Activities
If you want to generate files in further file formats, you have to create a BAdI implementation for the
required file format, using the file format as filter setting.
Incident Management
Configure Foundation for EHS
Use
Before performing the Customizing activities under Incident Management, you must first process
Customizing for the Foundation for EHS. Below, you will find information about the foundation
Customizing activities and their relevance to incident management.
In incident management, you can enter texts manually, translate these texts into other languages, and
enter amounts in a given currency.
For more information, see the following Customizing activities for Foundation for EHS:
- Specify General Settings

- Specify Active Languages
You can customize the incident management to use field control, support you in fulfilling regulatory
requirements, and store attached documents.
- Specify Field Control

- Create Regulations
- Specify Document Storage
Process Foundation
You can customize the process foundation to support your incident-specific processes.

- BAdI:Create and Initialize PCBOs
- Extend and Adapt Processes
Once you have configured processes for incident management, you can perform checks on the system,
display the configured processes, and collect statistics about your processes.
- Check Configuration of Workflow System - List Configured Processes

Forms necessary for recording incident details and reporting incidents are integrated into the incident
recording process. You can configure the available forms and their grouping.
- Specify Forms
- Specify Form Groups and Assign Forms
Integration
In incident management, you can use data from other SAP components, for example, assets from Plant
Maintenance (PM), person information from Personnel Management (PA) and SAP Business
Partner (BP), time data from Personnel Time Management (PT), materials from Material
Management (MM), and notification types from Cross-Application Components.
- Specify Destinations for Integration

Note that the documentation for this activity contains information about specifying
destinations to make integrated data available, as well as notes about the data that you can
access only on your local system.
- Specify Notification Types

- Check Authorizations for Person Information
- Specify Relevant Subtypes for a Party Infotype
- Specify Person Groups and Contractual Relationships
-
Specify Number Range Intervals for Incidents
Use
A unique number is assigned to each record created during incident recording in Environment, Health,
and Safety. The appropriate number range object determines the number automatically by the system.
In this Customizing activity, you can define number range intervals for the following number range
objects:
- EHHSSCASID # Injured Person External Case ID

- EHHSSINCID # Incident Management ID
- EHHSSPIID # ID for initial persons
The system creates initial persons when you enter a person in the incident data record who does not
exist in the HR or the SAP Business Partner system. The person is stored only in the Environment,
Health, and Safety system.
This number range is required for the conversion of the person ID (PERID). When you create a
business partner from the initial person, the system converts the initial person ID to the new
business partner ID.
- Specify Number Range Intervals for Foundation

- Specify Number Range Intervals for Health and Safety Management
Standard settings
internal interval.
Activities
Note
Specify Regulations
Use
In this Customizing activity, you can specify which regulations apply to a certain incident group,
incident category, region, and country.
The system uses these settings to provide the regulatory information for processing the incident data
records that have the specified group, category, country and region.
Requirements
You have created regulations in the Customizing activity Create Regulations.
Standard settings
Activities

Specify Import Mapping
Use
In this Customizing activity, you can map customer-specific enhancement data fields to business object
nodes and attributes when you import incidents into the Environment, Health, and Safety system.
Requirements
You are familiar with the modeling and structure of the business objects in Business Object Processing
Framework (BOPF) in the Environment, Health, and Safety system.
You are familiar with the enhancement data field names used in the source (import) file.
You have configured the corresponding nodes and attributes in the business object. At a later stage, the
user specified data is imported in these nodes and attributes.
Standard settings
The customer-specific enhancement data mapping is not set in the standard configuration.
Activities
1. Identify the business object for which you want to map customer-specific enhancement data fields.
2. Map the enhancement data fields to the corresponding business object node and attribute fields.
Example
You want to migrate an incident in the Environment, Health, and Safety system. The import source
file has customer-specific enhancement data that you want to store in the incident business object. To
store the data, you define mappings from the enhancement data fields to the nodes and attributes of the
incident business object.
Specify Export Mapping for Data Transfer
Use
In this Customizing activity, you can specify customer-specific enhancement BO nodes when you export
incidents from an Environment, Health, and Safety system.
Note: If you do not specify customer-specific enhancement BO nodes, by default the system exports all
BO nodes from the customer name space that start with Z or Y.
Requirements
- You are familiar with the modeling and structure of the business objects in Business Object
Processing Framework (BOPF) in the Environment, Health, and Safety system.
- You are familiar with the enhancement data node names used in the business object.
Standard settings
The customer-specific enhancement data mapping is not set in the standard configuration.
Activities
1. Identify the customer-specific enhancement data BO nodes.

2. Add new entries for the enhancement BO nodes in the table.
Example
You want to transfer an incident from an Environment, Health, and Safety system. The incident has
customer-specific enhancement BO nodes. To export the data to a file, you need to identify the nodes
that host data and create entries in the table for those objects.
To export the incident from the system, you use the R_EHHSS_INC_TO_CSV report. The report reads
the table, then gets the customer-specific data from the specified nodes and writes it in the export file.
Assign Access Level to Tabs
Use
In this Customizing activity, you can toggle visibility of particular UI elements (tabs, sub-tabs, or
specific areas on tabs or sub-tabs) in the incident management application, depending on the incident
access level authorizations of the logged user.
Each UI element in incident management can be identified uniquely by the following web dynpro
components with which it is configured in the application configuration:
- Incident Main View

- Incident Tabbed UIBB Configuration
- Incident Tabbed UIBB Variant
- Incident Tabbed UIBB Tab ID
To toggle visibility of a tab or a sub-tab, you can create a configuration entry for it that comprises the
element's technical details and an assigned incident access level. The access level is a predefined set of
permissions for accessing data on the application UI. By assigning an access level to the UI element, you
can set the element visible to people who have the same access level assigned to their users (via the
assigned user role). If the access level is not assigned to the user, the UI element remains hidden for that
user. Moreover, if you have defined any custom access levels, they are listed in the Acc. Level
dropdown menu in this activity and you can assign them to the specified UI elements.
In incident management application configuration, you can create tabbed UIBB configurations that are
not displayed as tabs on the UI. Those tabbed UIBB configurations can comprise UI elements (areas) that
are displayed independently on the UI (without the corresponding tab). For example, the Task Details in
the Tasks tab is an independent area, part of a tabbed UIBB configuration. In this Customizing activity
you can toggle visibility only of those areas that are part of a tabbed UIBB configuration by assigning an
access level to the corresponding tabbed UIBB configuration.
Note that the assignment of an access level is valid only for main views and tabbed UIBBs. If the tabbed
UIBB comprises more than one UI area, all UI areas are hidden when you assign an access level to that
tabbed UIBB.
Note: By default, the Basic Information tab of an incident must be visible for all users. Therefore, the
standard system is configured to always display the tab for all users. However, if you remove or disable
this configuration, the incident is opened in a read-only mode and an error message is displayed on the
user interface.
Note: If you assign an empty access level to an UI element, that element is voided and it is not displayed
on the incident UI.
Caution:
Note that the UI elements will be hidden for the users but they can still be reached programatically in the
background. However, if you want to additionally restrict the access to concrete fields, you should
implement your own business logic for the newly specified access level. To do this, you can use the
business add-in (BAdI) for authorization. For more information, see the documentation of theExtended
Authorization Checks BAdI.
Requirements
- You are familiar with the incident management application configuration.

- You are familiar with the incident access levels, defined in the system.
Standard settings

Warning:
If you have created any custom tabs in the incident management application, you must assign an access
level to those tabs in this Customizing activity. If you do not assign an access level, the tabs are not
displayed to any user.
Activities
1. Identify the incident UI elements (tabs, sub-tabs, or tabbed UIBB configurations) that you want to
hide or display.
2. Add an entry for each UI element in the table.
3. Enter a configuration code for each assignment that you want to create.
4. Specify the incident access level.
5. Specify the technical names of the UI elements in the corresponding fields:
- Incident Main View
- Incident Tabbed UIBB Configuration
- Incident Tabbed UIBB Variant
- Incident Tabbed UIBB Tab ID
Example
To set the main Reports/Documents tab visible to users that have the Injury/Illness Access
access level, create the following assignment. The tab will be invisible to all other users,
- Configuration Code of Tab Assignment: EHHSS_BASIC_DOCUMENTS

- Access Level: Injury/Illness Access
- Incident Main View: DOCUMENTS

- Incident Tabbed UIBB Configuration: (empty)
- Incident Tabbed UIBB Variant: (empty)
- Incident Tabbed UIBB Tab ID: (empty)
To set the Reports/Documents sub-tab of the People tab visible to those users who are authorized to
see personnel data, create the following assignment. The sub-tab will be invisible to all other users.
- Configuration Code of Tab Assignment: EHHSS_PEOPLE2
- Access Level: Person Involved Access

- Incident Main View: (empty)
- Incident Tabbed UIBB Configuration: EHHSS_INC_REC_OIF_V3_INV_PER_MD
- Incident Tabbed UIBB Variant: (empty)
- Incident Tabbed UIBB Tab ID: DOC
Further information
For more information about using access levels, see EHSM: Incident authorization object.
For more information about creating custom access levels, see the documentation of the Create Incident
Access Levels activity.
For more information about the BAdI for extending authorization checks, see the documentation of the
BAdI: Extended Authorization Checks BAdI.
Create Incident Access Levels
Use
In this organizational activity, you can learn about creating access levels in the incident management of
Environment, Health, and Safety.
Standard settings
Activities
To create incident access levels that can be used to toggle visibility of incident UI elements, proceed as
follows.
1. Start transaction SE11.

2. Select the Domain radio button and then in the text field enter
EHHSS_INC_ACCESS_LEVEL_CODE.
3. Choose the Change pushbutton.
4. Open the Value Range tab.
5. Insert a new row in the Single Vals table and then proceed as follows:
- In the Fix. Val. field, enter a code for the access level that is used internally in the business
logic.
- In the Short Description field enter a name of the access level.
6. Save your entries.
7. Open the Goto menu and then choose Fixed Value Append.
8. In the Append Name field enter the name of the append structure that you want to create.]
This structure is used to decouple the business logic of the standard delivery and the custom
implementation. It also hosts the implementation of all user-defined access levels.
9. Enter a description of the append structure and then in the Single Vals table enter the fixed vallue
and the short description of the access level that you specified above.
10. Save and activate your entries.
The procedure above is sufficient to create an access level with which you can control the visilibility of
incident UI elements by assigning this access level to them. Note that the UI elements will be hidden for
the users but they can still be reached programatically in the background. However, if you want to
additionally restrict the access to concrete fields, you should implement your own business logic for the
newly specified access level. To do this, you can use the business add-in (BAdI) for authorization. For
more information, see the documentation of the BAdI: Extended Authorization Checks.
Example
1. Insert a new row in the Single Vals table and then proceed as follows:
- In the Fix. Val. field, enter 005.
- In the Short Description field enter Financial Access.

2. Open the Goto menu and then choose Fixed Value Append.
3. In the Append Name field enter ZEHHSS_INC_ACCESS_LEVEL_CODE.
4. Using BAdI: Extended Authorization Checks, implement in the

ZEHHSS_INC_ACCESS_LEVEL_CODE structure your own enhanced business logic for handling
access to financial-related data.
Further information
For more information about managing visibility of incident tabs by assigning access levels to the
corresponding tabbed UIBB components, see the documentation of the Assign Access Level to Tabs
activity.
Process Configuration
Adapt Workflows for Incident Management
Use
In this activity, you can learn about the organizational activities for adapting the workflows of
SAP Business Workflow to suit your customer-specific processes. The process foundation of the
Environment, Health, and Safety component makes integration with workflows possible. You can
adapt workflows to your processes in the following ways:
- Change the workflow template

- Add steps within a process
- Call further logic from a workflow task (process step)
- Use a dispatcher to send notifications about changes to the data record
Requirements
You have specified processes for the health and safety (HSS) component in the Customizing activity
Specify Process Definitions for Foundation for EHS.
You have checked the processes by implementing the Customizing activity List Configured Processes
for Foundation for EHS.
Standard settings

The standard system is delivered with settings for a fatality notification functionality. If you want to use
this functionality, do not make changes to the current process definition for the incident lifecycle process
in the Customizing activity Specify Process Definitions. When a fatality is recorded in incident
management, this functionality raises the event
FATALITY_OCCURRED of the PCO in the incident lifecycle process
(CL_EHHSS_PCO_INC_LC). The workflow retrieves the people to be notified, and the system assigns
these people to workflow task 500086. Then, the system starts the notification workflow for each person.
The following workflow templates are delivered with the corresponding PCO class and event:
WF Template PCO Class Name and Event
500001 - EHHSS_INC CL_EHHSS_PCO_INC_LC
500002 - EHHSS_INQY CL_EHHSS_PCO_INC_INQUIRY
500003 - EHHSS_APPR CL_EHHSS_PCO_INC_APPROVAL
500004 - EHHSS_NOTI CL_EHHSS_PCO_INC_NOTIFIC
500005 - EHHSS_ACT CL_EHHSS_PCO_INC_ACTION_STD
500006 - EHHSS_DPAT CL_EHHSS_PCO_INC_LC
500031 - EHHSS_INV_LC CL_EHHSS_PCO_INV_LC
500032 - EHHSS_INVSTP CL_EHHSS_PCO_INV_STEP
500034 - EHHSS_REPORT CL_EHHSS_PCO_INC_REPORT
500036 - EHHSS_ACT_PM CL_EHHSS_PCO_INC_ACTION_PM
500039 - EHHSS_HR_ABS CL_EHHSS_PCO_INC_HR_ABSENCE
500040 - EHHSS_HRANTF CL_EHHSS_PCO_INC_HR_ABS_NOTI
500051 - EHHSS_RPT_CR CL_EHHSS_PCO_INC_REPORT_GEN
Activities
To adapt workflows, you can perform the following activities:
- You can change the process flow directly in the workflow template (in the Workflow Builder), or
copy the delivered template to the customer-specific namespace.
- You can add additional steps within a process by performing the following steps:
1. Change the workflow template (or copy the delivery to the customer-specific namespace)
2. Create further steps and (if necessary) workflow tasks in the customer-specific namespace in the
Customizing activity Define Tasks and Actions for Cross-Application Components.
3. Add the new tasks to the workflow inbox configuration in the Customizing activity Assign Task
IDs to POWL Types for Cross-Application Components. Enter the application ID
EHHSS_INBOX and the POWL type EHHSS_INBOX_TYPE for your task.
4. Activate the workflow template.
- You can add logic that can be called from a workflow task (process step) by performing the
following steps:
1. Create a PCO class that inherits from the delivered class of the process that is specified in the
Customizing activity Configure Process Definitions. It is recommended to inherit from the delivery
class and adapt it with further public methods. To include your business logic, use one of the
following two options:
- Implement the logic directly in the PCO method.
- Implement the logic in a BOPF action of the corresponding process control business object
(PCBO). Note: this is the architecture that Environment, Health, and Safety follows.
2. Use the standard event (WORKITEM_COMPLETED) if you open a dialog and the workflow has to
wait for an event. If you want to use a more specific event, you must define the new event on the
PCO class. For the dialog to raise the new event to continue the workflow, you can use the static
method RAISE_WF_EVENT of the root PCO CL_EHFND_WFF_ROOT_PCO.
3. After you have finished implementing and adapting the workflow template, configure the new PCO
class in the process definition in the Customizing activity Configure Process Definitions for
Incident Management.
- You can use the dispatcher workflow to react to changes in the incident with an automatic
notification. To add to the current changes that trigger a notification via the dispatcher process, start
the dispatcher workflow and extend the workflow template as required.
Configure Process Definitions
Use
In this Customizing activity, you can configure the processes used in the incident management
application of the Environment, Health, and Safety component.
Requirements
You have specified processes for the health and safety (HSS) component in the Customizing activity
Specify Process Definitions for Foundation for EHS.
You have ensured that the linkage between PCO classes and the corresponding workflows of SAP
Business Workflow is correct by implementing the Customizing activity List Configured Processes for
Foundation for EHS.
Standard settings
Activities

3. If necessary, select the Excludecheckbox to exclude a process from process monitoring and
analysis.
Note that entries you change in this activity are changed as well in the Customizing activity Specify
Process Definitions for Foundation for EHS.
Assign Default Roles to Workflow Tasks
Use
In this Customizing activity, you can assign default roles to workflow tasks that are used in the incident
management application in Environment, Health, and Safety. It is critical that you execute this
activity if you want to use the process foundation to support your business processes.
Requirements
You have set up the workflow system in the Customizing activity Perform Automatic Workflow
Customizing for Foundation for EHS.
You have assigned the roles used in this report to the required users in the transaction PFCG.
Standard settings
In the standard system, there are no agents assigned to the workflow tasks used in incident management.
The standard system is delivered with default roles.
Activities
To implement the standard setup and automatically assign the roles, execute this activity once.
For more information about the tasks and the roles that are assigned by this activity, see the report
R_EHHSS_CONFIG_TASK_ROLES.
Example
To assign an investigation lead (incident manager) to the investigation lifecycle workflow task, proceed
as follows:
1. Start transaction PFTC_CHG.

2. In the Task type drop down menu, enter Standard task.
3. In the Task field, enter the number of the task you want to configure. In this particular case the
number is 00500118.
4. Choose Change.
The system displays information about the standard task.
5. Choose Additional data -> Agent assignment -> Maintain.

6. Assign a user to the role and save your changes.
Further information
You can assign roles manually to tasks by opening each task in transaction PFTC_CHG.
Master Data Configuration
Locations
Specify Role of Person Responsible

Use
In this Customizing activity, you can specify the roles of persons responsible for special tasks at a
location. You can allow multiple persons responsible to be assigned to a role for location.
Standard settings

The Operator role is set by default as assigned to multiple persons responsible.
Activities

Note: When you set the corresponding flag for a role, the system allows you to assign multiple persons to
the selected role for a specific location. When this option is not enabled in customizing it is only possible
to assign one person responsible for a given role.
Example
An environmental manager, for example, responsible for scheduling data collections. Persons with this
role can schedule the collection of measurement data from devices within the industrial plant.
Specify Location Types
Use
In this Customizing activity, you can define the type of location.

You can use the location type to search for a location.
Standard settings
Activities

Enable/Disable PM Integration for Locations
Use
In this Customizing activity, you can enable or disable the integration for locations with the Plant
Maintenance (PM) component.
You can use the PM integration to import locations from PM and also to link existing locations to PM
technical objects.
Requirements
If you want to navigate in the application from the location to the linked PM technical object and display
its data, ensure that your system fulfills the following requirements:
- You are using SAP enhancement package 5 for SAP ERP 6 or higher on the integrated PM system.
- You have activated the business function LOG_EAM_SIMPLICITY in the PM system.
Note that it is still possible to integrate PM technical objects without this navigation function.
Activities
Once you have activated integration and used an integrated PM object in the application, you should keep
integration activated. Deactivating integration can lead to data inconsistency.
Schedule Jobs for Location Synchronization
Use
In this Customizing activity, you can schedule a background job to synchronize the master data for the
locations that are linked to objects in the Plant Maintenance (PM) component. This ensures that the
location data is up-to-date, for example, in search screens, analytical reports, and so on. If you do not use
the report, or the system has not run the scheduled report yet, you can open a location's master data to
synchronize that location's data with PM.
Requirements
- You are authorized to read data from the PM system and to update locations.
- You have enabled PM integration in the Customizing activity Enable/Disable PM Integration for
Locations.
- You have linked locations to PM technical objects.
Activities
1. Use the Job Wizard to specify the general data and schedule the job. You define the job for the
report R_EHFND_SYNCEAM_LOCATION.
2. Schedule the job to run as a background job once a day. If the PM data rarely changes, you can
schedule the background job to run less frequently.
Note: The background job queries all integrated technical objects for changes. The number of integrated
objects can create additional load for the Environment, Health, and Safety and PM systems and affect
performance.
Specify Evaluation Paths for Position Details
Use
In this Customizing activity, you can specify the evaluation paths for retrieving the objects assigned to a
position from the Organizational Management (PA-OS) component. This activity enables you to
assign a position to a location, and then display the people who currently occupy that position.
When you assign a position to a location, the position ID is stored in the location. The system uses a
function module to read the current organizational structure and evaluate it along the configured
evaluation path. The system returns the corresponding objects for the ID, such as business partners and
employees, at runtime.
Requirements
- You have integrated the system with the PA-OS system and the organizational structure is available
locally in the Environment, Health, and Safety system.
- You have entered evaluation paths in Customizing for PA-OS under Personnel Management ->
Organizational Management -> Basic Settings -> Maintain Evaluation Paths.
Standard settings
The entry delivered in the standard system is an evaluation path to return all people associated with a
position.
Activities
Check the existing evaluation path and specify additional entries, if necessary.
Specify Authorization Groups
Use
In this Customizing activity, you can define authorization groups.

You can assign authorization groups to locations. The authorization groups are used in the authorization
checks for the location. This way, you can restrict access to certain locations to specific users.
There are no separate authorization groups for the location structure. All actions performed inside the
location structure ascribe to the authorizations for the location.
Standard settings
Activities

Configure Integration of Map
Use
In this organizational activity, you can learn about how to enhance the location Web Dynpro to include a
map function in the side panel. This enables users to visualize the position of a location on a map.
You can implement the map function by using a third party CHIP to interpret and display the string
parameter from the location address.
Requirements
You have a map provider that is capable of interpreting an address string and displaying it on a map.
Standard settings
The standard system is delivered without an integrated map.
The location provides tagging for the tag name EHFND_LOC_ADDRESS. The address string is built
from the address fields entered in a location. If geographical coordinates are specified, they will take
priority over the address.
Activities
To integrate a map, perform the following steps:
1. Create a side panel entry for the map in the embedded side panel.
2. Create a Web Dynpro CHIP that is capable of interpreting an address string and displaying it on a
map. In most cases, this will be a URL CHIP (see the example below).
3. Create an enhancement of the Location Side Panel (Web Dynpro Configuration:
EHFND_LOC_OIF_SIDE_PANEL). In this enhancement configuration, integrate the Web Dynpro
CHIP that you created for displaying the map. Use the "EHFND_LOC_ADDRESS" tab to enable
automatic wiring (tagging); otherwise, the map will not be displayed automatically.
Example
Map providers that offer URL parameters can be integrated as a Web Dynpro URL CHIP.
An example URL would be: http://your-map-provider/map?address=<EHFND_LOC_ADDRESS>
The <EHFND_LOC_ADDRESS> tag will be automatically completed with the current location's
corresponding address string.
Actions and Controls
Specify Types
Use
In this Customizing activity, you can specify types for actions, notifications, and controls.
When you create an action or a notification in the application on the Tasks tab, you can choose the type
from the values you specified in this activity. You can classify controls using the subtype in the hazard
and control register.
Standard settings

You can make further settings for controls in Customizing activity Configure Hazard and Control
Register.
Activities

If you want the system to display a value on the user interface automatically, you can select the
Default checkbox for the corresponding entry.

Specify Subtypes
Use
In this Customizing activity, you can specify subtypes for actions, notifications, and controls.
When you create an action or a notification in the application on the Tasks tab, you can choose the
subtype from the values you specified in this activity. You can classify controls using the subtype in the
hazard and control register.
Requirements
You have made the settings for Customizing activity Specify Types for Foundation for EHS.
Standard settings

Register.
Activities


Specify Effectiveness
Use
In this Customizing activity, you can specify the effectiveness for actions and notifications.
When you create an action or a notification in the Environment, Health, and Safety component, you
can choose the effectiveness from the values you specify in this activity.
Standard settings
Activities


Specify Protection Goals
Use
In this Customizing activity, you can specify the protection goals for actions and notifications.
When you create an action or a notification in the Environment, Health, and Safety application, you
can choose the protection goal from the values you specify in this activity.
Activities


Specify Templates
Use
In this Customizing activity, you can specify templates for actions and notifications that you create in the
Environment, Health, and Safety component. The template stores the standard values for the action or
notification. During processing, you can choose an action or a notification from the template. The system
automatically retrieves the values for the following fields from the template and fills them in on the user
interface:
- Type
- Subtype
- Category
- Protection Goal
- Description
You can use templates to speed up the process of creating actions and notifications.
Requirements
You have made the settings in Customizing for Incident Management for the following activities:
- Specify Types
- Specify Subtypes
- Specify Effectiveness
- Specify Protection Goals
Standard settings

Templates are available for use in incident management.
Activities

Note that you must scroll all the way to the right to see all of the settings for a template.
Specify Priority Mapping for Notifications
Use
In this Customizing activity, you can specify the mapping between the priority of notifications used in
the component Environment, Health, and Safety and the priority of notifications used in Plant
Based on the priority in the notification in Environment, Health, and Safety, a notification is created
in the corresponding component with the specified priority.
Requirements
- You have configured priorities in the Customizing activity Define Priorities.
- If you use RFC destinations for creating notifications in another system, you have configured
priorities in the connected system under Cross-Application Components -> Notification ->
Notification Processing -> Response Control -> Define Priorities. Note: You can check
whether you have configured RFC destinations for other systems in the Customizing activity
Specify Destinations for Integration.
Standard settings
Activities
Specify the mapping of notifications priorities. If no priority mapping is configured, the corresponding
notification in another component will be created without any priority.
Specify Priority Due Date Mapping
Use
In this Customizing activity, you can specify the mapping between the priority with which an action or a
notification must be executed and the due date for this action or notification set by the system.
choose a priority and the due date will be determined based on your entries in this activity.
Note: When you define an action or a notification in the application, the system lets the best matching
configuration to determine the due date. If the current action category or business object is not defined in
this activity, the system does not determine any due date. You then have to enter the due date manually.
Furthermore, you can change the due date in the application either by specifying a different priority or
specifying a new due date.
Standard settings
Activities

BAdI: Definition of Process Steps
Use
this BAdI to define the persons that are involved in the process step of a given work process.
The process can contain the following people:
- Responsible Person
- Implementer
- Approver
In Environment, Health, and Safety, there are specific processes that involve action. In these
processes, workflow tasks are used to perform the work. You can use this BAdI to return the specific
workflow task and to integrate your business processes.
Standard settings
In the standard system, the following BAdI implementations are activated:
- EHHSS_ACTION_BADI_IMPL (implementation for incident management) -
BADI_IMPL_EHHSS_RAS_ACTION (implementation for health and safety management)
The BAdI is filter-dependent and not designed for multiple use.
Assign Forms to Regulations
Use
In this Customizing activity, you can assign the forms that are relevant to a specific regulation. The
system makes these forms available in the data record only if the corresponding regulation applies.
This activity is critical if you want to use forms for reporting incidents, for example, to legal authorities,
organization-internal recipients, or insurance companies.
Requirements
You have created regulations in the Customizing activity Create Regulations for Foundation for EHS.
You have specified forms in the Customizing activity Specify Forms for Foundation for EHS.
You have specified regulations for the incident group, incident category, region, and country in
Customizing activity Specify Regulations for Incident Management.
Standard settings
Note that the German accident notification form (BG_UNF_BER) is available in German only. You must
be logged on in German to use the form.
Activities

3. If you have created an internal regulation in Customizing activity Create Regulations and the
corresponding internal forms in Customizing activity Specify Forms, you can assign these forms
to the internal regulation.
Example
An incident involving a work-related injury occurred in the United States and is subject to OSHA
reporting requirements. You use the following settings delivered in the standard system:
- OSHA regulation (EHFND_US_OSHA) specified for the United States (US), for incidents
(001 Incident), and for the incident group for injury/illness (EHHSS_IGR_OCC_INC)
- OSHA 301 report form (OSHA_301) is assigned to the OSHA regulation

(EHFND_US_OSHA) as a legal report
When you choose to add a report form to the data record, the system proposes the OSHA 301 form.
Generate Forms for Offline Recording
Use
In this Customizing activity, you can generate offline forms that are used for recording an incident, a near
miss or a safety observation. You can store the forms on a medium (such as an Intranet or a public file
share) that can be accessed by all persons who should be able to use them to report such events.
Requirements
You have specified the offline forms in the Customizing activity Specify Forms for Foundation for
EHS.
Standard settings

You can use the following example forms for offline recording:
- INC_OFFLINE_REC_INC - Form for recording incidents offline

- INC_OFFLINE_REC_NM - Form for recording near misses offline
- INC_OFFLINE_REC_SO - Form for recording safety observations offline
Activities
Select the form for offline recording in the language you require, and store it on a public medium.
Ensure that when you generate the form, you only select a form for offline recording; otherwise, an
exception may occur.
Note: The offline recording forms use JavaScript for some features, for example, validating the user
input, starting your local e-mail client and attaching the form to an e-mail message. If for security
reasons JavaScript is disabled on your workstation, make sure that you enabled it for the offline
recording form before you fill out the form and send it to the SAP system.
Further information
If you use the example forms delivered in the standard system, you can record incidents, safety
observations and near misses offline and choose the Send pushbutton in the form to submit it to the
incident manager. The form is sent by e-mail to the system, where the e-mail inbound handler creates a
data record for the incident, near miss or safety observation using the inbound persister of the
corresponding form. For more information about setting up the inbound handling of forms, see Define
Inbound Processing for E-Mails.
Specify Inquiry Forms
Use
In this Customizing activity, you can specify which inquiry forms are assigned to which reference
category when an event is reported in Environment, Health, and Safety.
Requirements
You have specified forms in Customizing activity Specify Forms for Foundation for EHS.
Standard settings
Activities

Disable Initial Report Generation
Use
In this Customizing activity, you can enable and disable the automatic generation of an initial incident
report in Environment, Health, and Safety. If automatic generation is enabled, the system generates a
PDF of the data that you reported during initial recording of an incident. The PDF is stored on the
Reports/Documents tab of the incident data record. By disabling the initial incident report, the report is
not generated automatically and you cannot generate the report manually later.
Requirements
You have configured the incident lifecycle process in Customizing activity Configure Process
Definitions.
Standard settings
The standard system is delivered with automatic generation enabled.
Activities
You can select the checkbox to disable automatic generation of the initial incident report.
You can deselect the checkbox to enable automatic generation again. The setting takes effect only for the
incidents that are recorded initially after the setting has been changed.
BAdI: Electronic Report Shipment
Use
This Business Add-In (BAdI) is used to send incident reports in the Environment, Health, and Safety
component. You can use this BAdI to implement customer-specific logic for electronically shipping
reports to a receiving party, for example, a legal authority, such as the German workers' compensation
association. The BAdI allows you to adapt the report shipment process to company-specific requirements
by enabling the use of different exchange formats and different channels of communication. You can, for
example, use the BAdI if you want to send incident reports in an XML format via a Web service.
This BAdI is called before a report is sent to determine if a BAdI implementation exists for that type of
report. If an implementation exists, you can choose to send the report electronically, and the system calls
the BAdI again in the report shipment process. The BAdI then uses the SEND_REPORT method to do the
following:
- Generate the report in the correct output format

- Ship the report to the receiving party
- Complete the shipment process by reporting the success or failure of the shipment back to the
system
Requirements
- You have configured the process foundation in Customizing for Environment, Health, and
Safety under Foundation for EHS -> Process Foundation. Ensure that the event linkage is
active in activity Activate Linkage for Scheduled Processes.
- You have configured the processes used in incident management, specifically the following process
definition, in Customizing activity Configure Process Definitions:
Component: HSS
Purpose: INC_REPORT
Variant: STANDARD
- You have specified task recipients in Customizing activity Assign Default Roles to Workflow
Tasks.
Standard settings
The standard system does not include a default implementation for the BAdI.
For more information about the standard settings (filters, single or multiple uses), see the Enhancement
Spot Element Definitions tab in the BAdI Builder (transaction SE18).
See also
For more information about electronic report shipment and about the actions that are required to adapt
the shipment process to your needs, see the technical documentation for this BAdI in the BAdI Builder.
File-Based Reporting
Schedule Jobs for Extracting to XML Files
Use
In this Customizing activity, you can schedule jobs to automatically extract data (for all incidents) to use
in analytical reporting with a spreadsheet application. In contrast to analytical reporting via SAP
NetWeaver Business Warehouse or via a search of specific incidents in the application, this approach
enables you to extract all incident data via a back-end report. You can also run the report at any time if
you choose not to extract data regularly.
Requirements
- You are authorized to use the report All Incidents as XML (R_EHHSS_ALL_INC_TO_XML).
- You have defined a variant of the report All Incidents as XML to generate an XML file that
contains the incident data.
- You have defined a variant of the report All Incidents as XML to download the XML file into a
specified directory.
We recommend you use a directory with restricted access, so that only authorized users can open
the XML file.
Activities
1. In the activity, use the Job Wizard to specify the general data and schedule the job. You define the
job for the report All Incidents as XML (R_EHHSS_ALL_INC_TO_XML).
2. Select the option Generate data at AS.
3. Schedule the job as a background job to run at regular intervals, such as once a day.
Incident Recording
Basic Information
Specify Incident Groups
Use
In this Customizing activity, you can define additional incident groups.
Depending on the data you enter during the initial recording step for the incident record, the system
automatically classifies incidents according to groups, such as Release. You can change this
classification during the review and completion step. If you assign an incident group delivered with the
standard system, the system modifies the user interface to either reveal relevant or hide irrelevant
incident parameters. If you assign a customer-specified group, this will have no effect on the user
interface.
Standard settings
Activities

Specify Near Miss Groups
Use
In this Customizing activity, you can define additional near miss groups.
You can use near miss groups to classify near misses, either during the initial recording step or during the
review and completion step for incident records.
Standard settings
Activities

Specify Safety Observation Groups
Use
In this Customizing activity, you can define additional safety observation groups.
You can use safety observation groups to classify safety observations, either during the initial recording
step or during the review and completion step for incident records.
Standard settings
Activities

Specify Location Classifications
Use
In this Customizing activity, you can define the location classifications. During the initial recording step
for the incident record, you can enter a location classification which describes where the incident
occurred.
Standard settings
Activities


Specify Wind Directions
Use
In this Customizing activity, you can define the wind directions.

During the review and completion step for incident records, you can enter a wind direction. This
parameter contributes to the weather description for an incident.
Standard settings

In the standard delivery, weather data is entered only for incidents that involved a release. For more
information, see the documentation under Specify Incident Groups.
Activities


Specify Estimated Risk Types
Use
In this Customizing activity, you can define estimated risk types for near misses and safety observations.
Standard settings
Activities


People
Specify Roles
Use
In this Customizing activity, you can define the roles of an involved person or organization.
You can also define that a role can be used only for certain incident categories by selecting the
corresponding indicators.
Note
The person roles you define in this Customizing activity do not correspond with the roles that are
assigned to business partners. You can define business partner roles in Customizing for Cross-
Application Components under SAP Business Partner -> Business Partner -> Basic Settings ->
Business Partner Roles -> Define BP Roles.
Standard settings
Activities

Injured Person
Specify Incident Types
Use
In this Customizing activity, you can define different incident types for incidents that involve the injury
or illness of an involved person. For each incident type, you can specify whether it is occupational or
non-occupational according to the regulations that are valid for your company.
You can select an incident type during incident recording to classify an incident with regard to the
resulting injury or illness. The classification is required for legal reporting.
Standard settings
Activities


Specify Additional Reporting Criteria (OSHA)
Use
In this Customizing activity, you can define additional reporting criteria for OSHA reporting.
OSHA regulations require that certain cases of injury or illness are explicitly reported beyond general
reporting criteria, such as the following:
- Needlestick and sharps injuries (in case of contamination with another person's blood or other
potentially infectious material)
- Tuberculosis
- Hearing losses
- Cases involving medical removal
Standard settings
The standard system is delivered with example definitions for the above-named cases of injury or illness.
The standard system is delivered with field control settings that display this field only when the incident
is subject to OSHA recording requirements. For more information, see the settings for business object
EHHSS_INCIDENT -> node PERSON_INJ_INFO -> field control profile OSHA in the Customizing
activity Specify Field Control.
Activities


Specify Location of Death Types
Use
In this Customizing activity, you can define different location of death types. During incident recording,
you can use these types to specify where a person died.
Standard settings
EHHSS_INCIDENT -> node PERSON_INJ_INFO -> field control profile FATALITY_STATE in
Customizing activity Specify Field Control for Foundation for EHS.
Activities

If you want the system to display a value on the user interface automatically, you can
select the Default checkbox for the corresponding entry.

Specify Transportation to First Aid
Use
In this Customizing activity, you can define different means of transportation that can be used to take
injured persons to first aid treatment.
Standard settings
Activities


Specify Transportation to Further Treatment
Use
In this Customizing activity, you can define different means of transportation that can be used to take an
injured person from first aid treatment to further treatment or to their home.
Standard settings
Activities


Specify Cause of Death Types
Use
In this Customizing activity, you can define different cause of death types. During incident recording,
you can use these types to specify why a person died.
Standard settings
EHHSS_INCIDENT -> node PERSON_INJ_INFO -> field control profile FATALITY_STATE in
Customizing activity Specify Field Control for Foundation for EHS.
Activities

If you want the system to display a value on the user interface automatically, you can
select the Default checkbox for the corresponding entry.

Specify Injury/Illness Classifications
Use
In this Customizing activity, you can define aninjury or illness classification. This classification is
required to classify the injury or illness in legal reporting. The injury/illness classifications must
correspond with the injury/illness types. This means that when you report an incident, the values for
classification and type must match. Otherwise, an error message is displayed and the incident cannot be
reported.
Standard settings
Activities


Caution
When you report an incident using the simplified incident reporting application, the default
injury/illness classification and type are not displayed on the UI and, therefore, you cannot change
them. The simplified incident reporting application only allows you to enter an injury/illness
description (free text). Since the injury/illness classification must correspond with the injury/illness
type, you must ensure that the default values for the classification and type match before you report
an incident. Otherwise, the application displays an error message and does not allow you to report
the incident.
Specify Injury/Illness Types
Use
In this Customizing activity, you can define different injury and illness types that give a detailed
description of the injury or illness caused by the incident. Each injury or illness type must be assigned to
an injury or illness class as defined in the injury/illness classification.
Requirements
You have defined an injury/illness classification in the Customizing activity Specify Injury/Illness
Classification.
Standard settings
Activities
1. Check the existing examples and their definitions (extra short and long). Adapt them as required.
If the system should automatically display a value on the user interface, you can select the Default
checkbox for the corresponding entry.
Caution
Before you choose a default injury/illness type, make sure that this type is assigned to a
classification that is also selected as default.
Note that when you report an incident using the simplified incident reporting application, the
default injury/illness classification and type are not displayed on the UI and, therefore, you cannot
change them. The simplified incident reporting application only allows you to enter an
injury/illness description (free text). Since the injury/illness classification must correspond with the
injury/illness type, you must ensure that the default values for the classification and type match
before you report an incident. Otherwise, the application displays an error message and does not
allow you to report the incident.
2. If necessary, define additional injury or illness types and assign them to an injury/illness class.
Specify Body Parts
Use
In this Customizing activity, you can define the different body parts of a person that can be injured
during an incident. During incident recording, you can use these definitions to give a detailed description
of the injury.
Standard settings
Activities


0 Specify Body Sides
Use
In this Customizing activity, you can define the different sides of a person's body that can be injured
during an incident. During incident recording, you can use these definitions to give a detailed description
of the injury.
Standard settings
Activities

1 Specify Restriction Types
Use
In this Customizing activity, you can define different restriction types. During incident recording, you
can assign these restriction types to an injured person to give detailed information about the
consequences of an injury or illness.
Note
To specify the absence types that are relevant for incident recording, you use the Customizing activity
Specify Relevant HR Absence Types.
Standard settings
Activities


2 Specify Injured Person as Confidential
Use
In this Customizing activity, you can enable or disable the automatic assignment of an injured person as
confidential. If automatic assignment is enabled, the system specifies as confidential the injured person
that you reported during the initial recording of an incident. Later on, in the incident management
application, the Restricted Access radio button on the Basic Information sub-tab of the injured person
is set to Yes.
By disabling the automatic assignment, the injured person is not set automatically to confidential and you
can specify it manually later. Thus, in the incident management application, the Restricted Access
radio button on the Basic Information sub-tab of the injured person is set to Unknown.
Standard settings
The standard system is delivered with disabled automatic assignment of confidential injured person.
Activities
- You can select the checkbox to enable automatic assignment of confidential injured person.
- You can deselect the checkbox to disable automatic assignment of confidential injured person.
3 Influencing Factors
3 Specify Incident-Causing Objects
Use
In this Customizing activity, you can define different incident-causing objects. During incident recording,
you can specify these objects to provide detailed information about why an incident occurred.
Standard settings
Activities


3 Specify Movements of Incident-Causing Objects
Use
In this Customizing activity, you can define different kinds of movement referring to the incident-causing
object. During incident recording, you can specify these movements to provide detailed information
about why an incident occurred.
Standard settings

The standard system is delivered with field control settings that display this field only when an incident-
causing object exists. For more information, see the settings for business object
EHHSS_INCIDENT -> node HEALTH_SAF_INFO -> field control profile
INC_CAUSING_SUBST_IN in Customizing activity Specify Field Control for Foundation for EHS.
Activities


3 Specify Activities of Injured Persons
Use
In this Customizing activity, you can define different activities that describe what the injured person was
doing when the incident occurred.
Standard settings
Activities


3 Specify Movements of Injured Persons
Use
In this Customizing activity, you can define different kinds of movement. During incident
recording, you can use these movement definitions to provide detailed information about what the injured
person was doing when the incident occurred.
Standard settings
Activities


3 Specify Personal Protective Equipment
Use
In this Customizing activity, you can define the personal protective equipment that can or must be used
for certain jobs.
Standard settings
Activities


3 Specify External Influences
Use
In this Customizing activity, you can define different external influences. During incident recording, you
can specify these external influences to provide detailed information about the circumstances under
which an incident occurred.
Standard settings
Activities

3 Specify Immediate Actions
Use
In this Customizing activity, you can define different actions describing the steps that are taken
immediately after an incident occurred.
Standard settings
Activities


A unique key must be assigned to each entry. Example
3 Specify Technical Safety Devices
Use
In this Customizing activity, you can define different technical safety devices.
Standard settings
Activities


Assets
Specify Damage Types
Use
In this Customizing activity, you can define the damage types for involved assets. You can also specify
to which asset types each damage type can apply .
When you record damages for an involved asset, only the damage types assigned to the relevant asset
type can be selected on the user interface.
Standard settings
Activities


3. Select the checkbox for the asset types that you want to assign to the damage types.
Releases
Specify Release Types
Use
In this Customizing activity, you can define release types. When you review and complete an incident
record, you use release types to describe how a material was released.
Standard settings
Activities


Specify Release Sizes

Use
In this Customizing activity, you can define release sizes. When you review and complete an incident
record, you use these release sizes to describe the amount of material that was released.
Standard settings
Activities


Specify Material States
Use
In this Customizing activity, you can define material states. When you review and complete an incident
record, you use these states to give a detailed description of the material that was released.
Standard settings
Activities


Specify Affected Land Types
Use
In this Customizing activity, you can define different land types.
Standard settings

Activities


Specify Disposal Methods
Use
In this Customizing activity, you can define different disposal methods.
Standard settings
Activities


Specify Disposal Sites
Use
In this Customizing activity, you can define different types of disposal sites.
Standard settings
Activities


Specify Recovery Methods
Use
In this Customizing activity, you can define different recovery methods
Standard settings
Activities


Specify Waste Types
Use
In this Customizing activity, you can define differentwaste types. When you review and complete an
incident record, you use these waste type to indicate how dangerous the released material is to the
environment.
Standard settings
Activities


Specify Cleanup Methods
Use
In this Customizing activity, you can define different cleanup methods.
Standard settings
Activities


Risk Matrix
Specify Affected Areas
Use
In this Customizing activity, you can defineareas affected by the incident. When you review and
complete an incident record, you can assess the risk to an area on the Risk Matrix tab.
Standard settings
Activities

Specify Severity
Use
In this Customizing activity, you can define severity values and the corresponding risk scores. When you
review and complete an incident record, you can assign a severity value to an affected area on the Risk
Matrix tab. The severity is one of several risk parameters used to calculate the risk to that area.
Requirements
You have defined affected areas in the Specify Affected Areas Customizing activity.
Standard settings

There is a unique set of severity values for each area.
Activities

2. Check the existing example scores under Risk Score and adapt them as required.
Specify Likelihood
Use
In this Customizing activity, you can define likelihood values. When you review and complete an
incident record, you can assign a likelihood value to an affected area on the Risk Matrix tab. Each
likelihood value has a corresponding score value. The likelihood is one of several risk parameters used
to calculate the risk to an area.
Standard settings
Activities

Specify Frequency
Use
In this Customizing activity, you can define frequency values. When you review and complete an
incident record, you can assign a frequency value to an affected area on the Risk Matrix tab. Each
frequency value has a corresponding score value. The frequency is one of several risk parameters used to
calculate the risk to an area. Standard settings
Activities

Specify Duration Classifications
Use
In this Customizing activity, you can define duration classifications.

When you review and complete an incident record in incident management, you can assign a duration to
an affected area on the Risk Matrix tab. Each duration classification has a corresponding score value.
The duration is one of several risk parameters used to calculate the risk to an area.
Standard settings
Activities

Specify Risk Ratings
Use
In this Customizing activity, you can define risk ratings.

When you review and complete an incident record, you can assess the risk to an affected area on the Risk
Matrix tab by entering information for the following risk parameters:
- Severity
- Likelihood to Reoccur
- Frequency
- Duration
You can enter a data value for each risk parameter. A risk score is assigned to each of these values.
The system automatically calculates and assigns a risk rating when the sum of the risk scores falls within
a certain range (between a lower score limit and an upper score limit).
Requirements
You have defined risk score values in the following Customizing activities:
- Specify Incident Severity

- Specify Incident Likelihood
- Specify Incident Frequency
- Specify Incident Duration Classifications
Standard settings
Activities
1. Select the Default checkbox if you want the system to display a specific risk rating on the Risk
Matrix tab automatically until a different risk rating is calculated.
2. In the Description (XS) field, enter a letter grade or word to describe the corresponding Risk
Rating value. You can use generic descriptors, such as C or Moderate.
3. In the Description (L) field, enter words or a phrase to further describe the risk rating, for example,
Acceptable with Controls.
4. In the Risk Icon field, enter the color of the LED icon that is to be displayed for the corresponding
risk rating.
5. In the Lower Score field, enter the lowest score for the range of possible scores for the
corresponding risk rating. Risk rating ranges must not overlap, that is, the lower score for one risk
rating must not have the same value as the upper score for another risk rating.
6. In the Upper Score field, enter the highest score for the range of possible scores for the
corresponding risk rating.
BAdI: Calculate Risk Rating and Determine Risk Icon
Use
this BAdI to adapt the standard logic to calculate risk ratings and to determine the risk icons that are
displayed.
The risk icons are set according to the risk rating. The risk rating is calculated for each affected area
based on configurable scores for the following risk parameters: severity, likelihood to reoccur, frequency
and duration. The calculated value can be manually overwritten by the user.
The default logic for calculating risk ratings and determining risk icons is as follows:
- The scores of the affected areas are added.

- The rating is determined according to the lower and upper limit of the sum of scores.
- The risk icon is determined according to the risk rating configuration.
The BAdI method calculate_risk receives the precalculated sum of risk scores, the distinctive scores for
severity, likelihood to reoccur, frequency and duration, and returns the value for the risk icon.
The BAdI method calculate_risk_ext receives one additional parameter to the ones which the method
calculate_risk receives. There are no differences in the returned parameters of the two methods.
Requirements
You have made the following settings in the Customizing for Environment, Health, and Safety under
Incident Management:
Specify Severity
Specify Likelihood
Specify Frequency
Standard settings
This BAdI is active in the standard system.
Notices of Violation
Specify Violation Categories
Use
In this Customizing activity, you can define violation categories.
Standard settings
Activities


Specify Violation Types
Use
In this Customizing activity, you can define violation types.
Standard settings
Activities

Specify Violation Sources
Use
In this Customizing activity, you can define violation sources.
Standard settings
Activities


Financial Tracking
Specify Financial Transaction Categories
Use
To track the expenses and income associated with an incident, you can assign financial transactions to an
incident record. You can either enter the transaction data manually, or assign cost collectors from
integrated components.
In this Customizing activity, you can define categories of financial transactions that you want to use for
financial tracking. For each category, you can specify whether it refers to a cost collector from an
integrated component or is used to classify transaction data that you enter manually in the incident
management application.
Prerequisites
- To ensure that currencies can be correctly converted for all financial transaction categories, you
have maintained exchange rates in the Customizing activity Enter Exchange Rates.
- An implementation of the Business Add-In (BAdI) Add Financial Transaction Objects
(BADI_EHHSS_FIN_TRANS_OBJ_ADD) exists for each financial transaction category that refers
to an integrated cost collector. You define the required BAdI implementations in the Customizing
activity BAdI: Integrate Financial Transaction Objects.
Standard settings
The standard system is delivered with examples of both categories that refer to cost collectors in
integrated components and categories for transactions that you enter manually.
Activities


3. Select the IntegrObj checkbox for all categories that refer to cost collectors from integrated
components.
Example
You want to define the following additional categories:
- Additional Costs for the manual entry of additional costs transactions in the incident management
application
- Work Breakdown Structure (WBS) for the assignment of WBS elements as financial transactions
to an incident
To define the Additional Costs category, proceed as follows:
1. Add a new entry to the table.

2. Enter EHHSS_FC_ADD_COSTS as the technical name and Additional Costs as the description for
this entry.
Do not select the IntegrObj checkbox.
To define the Work Breakdown Structure category, proceed as follows:
1. Add a new entry to the table.

2. Enter EHHSS_FO_WBS as the technical name and Work Breakdown Structure as the description
for this entry.
3. Select the IntegrObj checkbox.
4. Create an implementation of the BAdI Add Financial Transaction Objects
(BADI_EHHSS_FIN_TRANS_OBJ_ADD). Use the financial transaction category as the filter
value.
BAdI: Integration of Financial Transaction Objects
Use
this BAdI to enable access to cost collectors in other components for financial tracking. The components
can either be managed locally or in a remote system.
This BAdI is delivered with active implementations for the following types of cost collectors:
- Internal order (Accounting (AC))

- Maintenance order (Plant Maintenance (PM))
To enable access to other cost collectors, you can create additional BAdI implementations. The following
methods are available:
- ADD_FIN_TRANS_OBJECT (Add Financial Transaction Object)

This method is executed when you add a financial transaction to an incident record.
- DETAILS_FIN_TRANS_OBJECT (Display Details for Financial Transaction Object) This

method is executed when you display the details for a financial transaction object.
- REFRESH_FIN_TRANS_OBJECT (Refresh Data for Financial Transaction Object)
This method is executed when you refresh the list of financial transaction objects.
If this BAdI is implemented, you can assign cost collectors from integrated components as financial
transactions to an incident record.
Note
If you have defined an enhancement including customer-defined dialog boxes for the application
configuration EHHSS_INC_REC_OIF_V3, you can use implementations of the BAdI methods
ADD_FIN_TRANS_OBJECT and DETAILS_FIN_TRANS_OBJECT to specify which dialog boxes are
called when you assign cost collectors to an incident.
Requirements
- In the Customizing activity Specify Financial Transaction Categories, you have added a financial
transaction category for each cost collector type that you want to use for financial tracking. You
have selected the IntegrObj checkbox for these categories.
- If you want to use cost collectors in components that are managed in a remote system, you have
defined the required RFC destinations in the Customizing activity Specify Destinations for
Integration.
Standard settings
- BADI_EHHSS_FIN_TR_INT_ORDER
This BAdI implementation enables access to internal orders that exist in Accounting.
- BADI_EHHSS_FIN_TR_MAINT_ORDER
This BAdI implementation enables access to maintenance orders that exist in Plant Maintenance.
Activities
You must create a BAdI implementation for each financial transaction category that refers to an
integration object. Use the financial transaction category as the filter value for the filter
FIN_TRANS_CAT.
Business Add-Ins (BAdIs) for Checks

BAdI: Check Readiness for Action
Use
this BAdI to perform checks on the following actions:
- Set status of a data record to Closed

- Set status of a data record to Void
- Set status of an incident investigation to Closed
- Set status of an investigation step to Closed
For each action, a BAdI implementation is delivered that you can use to perform the corresponding check
in the standard system. If necessary, you can also deactivate the standard implementations and
implement customer-specific checks instead.
Caution
If you implement customer-specific checks, you must ensure that these are complete in terms of data
consistency and legal requirements, for example, when generating legal reports based on the incident
data.
Standard settings
The BAdI is active in the standard system.
- BADI_RDY_FOR_ACT_INC_CLOSE
You use this BAdI implementation to perform the following checks before the status of an incident
is set to Closed:
- Check if the Restricted Access attribute for the incident is set to Yes or No
- Check if an incident group is assigned
- Check if the Investigation Required attribute is set to Yes or No
- If an investigation is required, check if the investigation is completed
- If the incident is an occupational incident, check if at least one involved person has the
Injured Person role
- If the incident is classified as Release, check if at least one release is assigned
- Check if the Reporting Required attribute for a release is set to Yes or No
- Check if risk matrix entries are complete and confirmed
- If the incident is classified as a notice of violation, check if at least one notice of violation is
assigned
- If the incident has actions assigned, check if all actions that are not recurring are complete
- Check if all inquiry processes are complete
- For any injured person, check if the Required in Summary Report attribute is set to
Yes or No
- For any release of incident, check if the Reporting Required attribute is set to Yes or No
- BADI_RDY_FOR_ACT_NM_CLOSE
You use this BAdI implementation to perform the following checks before the status of a
near miss is set to Closed :
- If the near miss has actions assigned, check if all non-recurring actions are complete
- BADI_RDY_FOR_ACT_SO_CLOSE
You use this BAdI implementation to perform the following checks before the status of a safety
observation is set to Closed:
- If the safety observation has actions assigned, check if all non-recurring actions are complete
- Check if all inquiry processes are complete - BADI_RDY_FOR_ACT_INC_VOID /
BADI_RDY_FOR_ACT_NM_VOID /
BADI_RDY_FOR_ACT_SO_VOID
You use these BAdI implementations to implement customer-specific checks that you want to
perform before an incident, near miss, or safety observation is set to Void. The implementations do
not perform any checks in the standard system.
- BADI_RDY_FOR_ACT_INV_CLOSE
You use this BAdI implementation to perform the following checks before the status of an
investigation is set to Closed:

- Check if an investigation lead is assigned
- Check if a major root cause is selected
- Check if all investigation steps are complete (status Closed, Void, or Completed)
- BADI_RDY_FOR_ACT_STEP_CLOSE
You use this BAdI implementation to perform the following check before the status of an
investigation step is set to Closed:
- For investigation steps with the step category EHHSS_ST_CAT_ROOTCAUS, check if all
assigned actions are complete (status Closed, Void, or Completed).
· BADI_RDY_FOR_ACT_CHANGE_CAT
You use this BAdI implementation to perform the following checks before changing the category of an
incident:
o Check if incident status is set to Void or Closed o Check if incident

investigation status is In Process or Reopened o Check if HR
absence worklflow step is New or In Process o Check if incident inquiry
status is New or In Process o Check if incident report status is New or In
Process o Check if incident approval task is New or In Process
o Check if a reopened incident worklflow instance is In Process, and the
process status is not Initial
Activities
You can use the following filter values when defining customer-specific BAdI implementations:
- INCIDENT_CATEGORY
- 001 Incident
- 002 Near Miss
- 003 Safety Observation
- ACTION_NAME
- SET_VOID_ROOT
- SET_CLOSED_ROOT
- INVESTIG_RESULT_SET_CLOSED
- NODE_NAME
You can use all existing node names from business object EHHSS_INCIDENT. To display the
nodes of this business object, use transaction /BOBF/CUST_UI or execute the search help
EHFND_ELM_BO_NODE_NAME in transaction SE11 in test mode using BO_NAME =
EHHSS_INCIDENT.
Example
You want to define a check that is only executed if:
- The incident is a Near Miss

- The action that is performed to set the status to Closed
- The BASIC_INFO_ALL node is processed.
To do this, set the following filter values:
- INCIDENT_CATEGORY = 002 (Near Miss)
- ACTION_NAME = SET_CLOSED_ROOT
- NODE_NAME = BASIC_INFO_ALL
BAdI: Check Incident Reports
Use
this BAdI to perform checks for data completeness in incident reports.
If you implement customer-specific checks , you must ensure that these are complete in terms of data
data.
Caution
If you deactivate or change a check, you must also ensure that all actions are complete or are in the
process of completing.
Standard settings

- BADI_IRT_CHECK_OSHA_301
This BAdI implementation performs the following checks:
- Check if the person exists in HR or exists as a business partner

- Check if a first physician or a further treatment provider is maintained
- Check if the Emergency Room attribute is set to Yes or No
- Check if the Inpatient Overnight attribute is set to Yes or No
- Check if the actual start working time for the injured person is maintained
- Check if either an activity was selected, or a free text description for the injured person's
activity is maintained
- Check if a statement that can be included in reports is maintained
- If an injury/illness is maintained, check if the injury/illness information and body part
information is maintained
- Check if only the first reportable injury/illness or the first reportable unknown injury /illness is
defined
- Check if the incident-causing object or an incident-causing substance is maintained
- Check if the Fatality attribute is set to Yes or No
- If the Fatality attribute is set to Yes, check if the date of death is maintained
- BADI_IRT_CHECK_BG_UNF_BER

- Check if the incident time zone is maintained
- Check if the address where the incident occurred is maintained
- Check if a statement that can be included in reports is maintained - Check if an
injury/illness is maintained.
- If an injury/illness was maintained, check if a body part is maintained
- Check if the actual end working time for the injured person is maintained
- Check if the position description is maintained
- Check if the duration in position is maintained
- Check if the organizational unit of the injured person is maintained
- Check if the ceased work date and time is maintained
- Check if end dates of absences are maintained
- BADI_IRT_CHECK_REL_REP
This BAdI implementation does not perform any checks in the standard system. You need to create
your own implementation if you want to implement customer-specific checks.
Activities
- Possible filter values for the incident category are:

- INCIDENT_CATEGORY = 001 Incident
- INCIDENT_CATEGORY = 002 Near Miss
- INCIDENT_CATEGORY = 003 Safety Observation
- Possible filter values for form names are all form names that are entered in Customizing for
Investigation
Specify Step Categories
Use
In this Customizing activity, you can add new step categories and modify the categories that are provided
with the standard system. This activity allows you to add your own functions to the investigation
solution.
Requirements
To create new step categories, you have already developed the new FPM dialog box and variant for the
review and completion step and for the investigation step quick activity.
Standard settings
Activities


You can specify the form name of an existing Interactive Form (IF). This setting is used for offline
investigation steps when the step is sent via e-mail as an IF to the person responsible for the step.
For more information, see Specify Steps.
We recommend that you create new categories instead of adapting existing categories to ensure
that the standard examples are not affected. To create new step categories, you must enter the
variant ID and dialog box ID. Note: You must ensure that this data is consistent since the system
cannot validate this data fully.
Specify Steps
Use
In this Customizing activity, you can specify investigation steps in the investigation process. You can add
steps individually to the investigation process in the application, or you can group these steps together in
an investigation template (see Customizing activity Specify Templates).
The investigation steps you define here are only available for the incidents that have the corresponding
attributes. For example, you can specify a step in this activity for investigating the root cause of an
environmental release. You can only use this step in investigating incidents in which you have recorded a
release.
Requirements
- To use offline forms, you have specified an Interactive Form for each offline step category in the
Specify Step Categories Customizing activity.
- To specify a root cause hierarchy for steps with the category Root Cause Hierarchy
(EHHSS_ST_CAT_ROOTCAUS) or Root Causes and Control Evaluation
(EHHSS_ST_CAT_RC_FCTRL), you have specified a root cause hierarchy in the Specify Root
Cause Types Customizing activity.
- To use root cause steps for offline steps using the INV_ROOTCAUSE_FORM Interactive Form,
the hierarchy has a maximum of three levels.
Standard settings
Activities

Note: You can upload a document to use as a template for performing an offline investigation step by
double-clicking the investigation step and entering a local file in the File Name field.
Note: The adjustment of Customizing entries is not supported for this Customizing activity, because it
that you compare your Customizing entries, then edit the entries manually, and upload the required files
again.
Specify Guidelines
Use
In this Customizing activity, you can assign investigation guidelines to incident categories and incident
groups. The investigation lead can access these guidelines at the start of the investigation process.
The investigation guideline is part of the template for the investigation flow that the system determines
based on specific incident attributes.
Activities
Add new investigation guidelines, as required.

To ensure that you have an overview of all guidelines that you have used, we recommend that you do not
change or delete old guidelines. We recommend that you add new guidelines with a higher version
number.
Note: The adjustment of Customizing entries is not supported for this Customizing activity, because it
that you compare your Customizing entries, then edit the entries manually, and upload the required files
again.
Specify Templates
Use
In this Customizing activity, you can define investigation templates.

You can assign investigation templates to specific kinds of incidents using criteria, such as
incident category, incident group, plant ID, country, and region. You can also define the standard
investigation steps in the template and the sequence in which these steps should be performed.
Requirements
If you want to assign templates to investigation steps, you have defined investigation steps in the
Specify Steps Customizing activity.
Activities
1. Specify investigation templates, as required.

2. Assign investigation templates to incidents using the criteria incident category, incident group, plant
ID, country, and region.
3. Define the standard investigation steps that the template is composed of under Steps in Template.
We recommend that you align the templates and guidelines for each incident category to ensure that the
investigation lead can follow the prescribed process and guidelines. For more information, see the
Specify Guidelines Customizing activity.
Specify Root Cause Types
Use
In this Customizing activity, you can specify the root cause hierarchies that you can use when you define
investigation steps in the Specify Steps Customizing activity. Root cause hierarchies
are used in investigation steps with the EHHSS_ST_CAT_ROOTCAUS or
EHHSS_ST_CAT_RC_FCTRL category.
Requirements
To use root cause steps for offline steps with the INV_ROOTCAUSE_FORM Interactive Form, the
hierarchy has a maximum of three levels.
Standard settings
Activities

You must enter a description for each root cause.
You must enter a unique description for each root cause hierarchy.
3. You can restrict the selection of root causes in an incident investigation step. By default, the
Restrict selection to last level checkbox is unselected and it allows you to process root causes at
any level in the hierarchy. If you select the checkbox, you can process only the last level root
causes.
BAdI: Investigation Lead Determination
Use
This Business Add-In (BAdI) is used in the Environment, Health, and Safety component. By default,
the investigation lead is automatically set to the current incident manager. You can use this BAdI to
change how the default investigation lead is determined.
Integration
Logistics Integration
Specify Involved Assets - Equipment Types
Use
In this Customizing activity, you can specify the equipment types that are allowed to be entered as a
classification of an involved asset during incident recording in the Environment, Health, and Safety
application.
You can do the following:
- Select equipment types from Plant Maintenance (PM) to restrict the number of available
equipment types in EHS
- Define new equipment types for EHS
Requirements
If you want to select equipment types from PM, you have defined technical object types in Customizing
for Plant Maintenance underDefine Types of Technical Objects. You can specify these technical object
types as equipment types in Customizing for Environment, Health, and Safety.
Standard settings
The standard system is delivered without equipment types.
Activities
- If you want to use a restricted number of PM equipment types for EHS, select the required
equipment types and enter a description for all relevant languages. If you do not enter a
description, the system automatically uses the description that is defined for the selected equipment
types in PM.
Note
To maintain the description in other languages, when you edit an IMG activity, select the relevant
record and then choose Goto -> Translation.
- If you want to use equipment types that are only relevant for EHS, define the required entries and
enter a description for all relevant languages.
If you do not specify any equipment types, all PM equipment types can be selected during incident
recording. However, once you have specified equipment types for EHS, you can only use the equipment
types that are defined in this Customizing activity.
Recommendation
Although it is possible to use PM equipment types together with equipment types that are only relevant
for EHS, we do not recommend this. If you used both, you would be able to select a non-PM equipment
type, for example, but you would not find a PM equipment type for it, which could cause some
confusion.
Example
In Plant Maintenance, the technical object types 1000 and 2000 are defined. In Plant Maintenance,
pieces of equipment are created with these technical object types.
In the incident recording, it shall be possible to add pieces of equipment from Plant Maintenance with
the technical object type 1000 or 2000 as pieces of equipment to an incident.
Specify the following entries:
Equipment Type Equipment Type Description
1000 Incident Equipment 1000
2000 Incident Equipment 2000
As a result, it is possible to add pieces of equipment with the equipment type 1000 or 2000 to an
incident.
Specify Involved Assets - Property Types
Use
In this Customizing activity, you can specify the property types that are allowed to be entered as a
classification of an involved asset during incident recording of Environment, Health, and Safety.
- Select property types from Plant Maintenance (PM) to restrict the number of available property
types in EHS
- Define new property types for EHS
Requirements
If you want to select property types from PM, you have defined technical object types in Customizing
for Plant Maintenance underDefine Types of Technical Objects. You can specify these technical object
types as property types in Customizing for Environment, Health, and Safety.
Standard settings
The standard system is delivered without property types.
Activities
- If you want to use a restricted number of PM property types for EHS, select the required property
types and enter a description for all relevant languages. If you do not enter a description, the
system automatically uses the description that is defined for the selected property types in PM.
Note
- If you want to use property types that are only relevant for EHS, define the required entries and
enter a description for all relevant languages.
If you do not specify any property types, all PM property types can be selected during incident
recording. However, once you have specified property types for EHS, you can only use the property
types that are defined in this Customizing activity.
Recommendation
Although it is possible to use PM property types together with property types that are only relevant for
EHS, we do not recommend this. If you used both, you would be able to select a non-PM property type,
for example, but you would not find a PM property type for it, which could cause some confusion.
Example
In the incident recording, it shall be possible to add properties from Plant Maintenance with the
technical object type 1000 or 2000 as properties to an incident.
Property Type Property Type Description
1000 Incident Property 1000
2000 Incident Property 2000
As a result, it is possible to add properties with the property type 1000 or 2000 to an incident.
Specify Involved Assets - Vehicle Types
Use
In this Customizing activity, you can specify the vehicle types that are allowed to be entered as a
classification of an involved asset during incident recording of Environment, Health, and Safety.
- Select vehicle types from Plant Maintenance (PM) to restrict the number of available vehicle
types in EHS
- Define new vehicle types for EHS
Requirements
If you want to select vehicle types from PM, you have defined technical object types in Customizing for
Plant Maintenance underDefine Types of Technical Objects. You can specify these technical object
types as vehicle types in Customizing for Environment, Health, and Safety.
Standard settings
The standard system is delivered without vehicle types.
Activities
- If you want to use a restricted number of PM vehicle types for EHS, select the required vehicle
types and enter a description for all relevant languages. If you do not enter a description, the
system automatically uses the description that is defined for the selected vehicle types in PM.
Note
- If you want to use vehicle types that are only relevant for EHS, define the required entries and enter
a description for all relevant languages.
If you do not specify any vehicle types, all PM vehicle types can be selected during incident recording.
However, once you have specified vehicle types for EHS, you can only use the vehicle types that are
defined in this Customizing activity.
Recommendation
Although it is possible to use PM vehicle types together with vehicle types that are only relevant for
EHS, we do not recommend this. If you used both, you would be able to select a non-PM vehicle type,
for example, but you would not find a PM vehicle type for it, which could cause some confusion.
Example
In the incident recording, it shall be possible to add vehicles from Plant Maintenance with the technical
object type 1000 or 2000 as vehicles to an incident.
Vehicle Type Vehicle Type Description
1000 Incident Vehicle 1000
2000 Incident Vehicle 2000
As a result, it is possible to add vehicles with the vehicle type 1000 or 2000 to an incident.
Human Resources Integration
Check Customizing for Personnel Time Management
Use
Integration with the SAP component Personnel Time Management (PT) allows you to access
working time data and absences for injured persons during the review and completion step for incident
records.
Note
As PT manages time data for employees, integration is only possible for internal persons.
To be able to make full use of PT integration, check that the following settings are correct before you
activate PT integration for incident management:
Personnel Time Management
The link between person and absence is established based on the relationship between personnel subarea
and absence type that is defined in Customizing for Personnel Time Management. This includes the
following steps:
1. Group together personnel subareas for which the same absence types are valid (personnel subarea
grouping) in the Customizing activity Group Personnel Subareas for Attendances and Absences.
2. Assign absence types to the personnel subarea groupings in the Customizing activity Define
Absence Types
The relationship between personnel subarea groupings and absence types is time-related. The
validity period is limited by the start and end date of the relationship.
Foundation for EHS
For access to PT data, the required authorizations for the Absences infotype are assigned to all users
with display authorization for incident records. For more information, see the Customizing activity
Check Authorizations for Person Information.
Activate Personnel Time Management Integration
Use
In this Customizing activity, you can configure the following settings:
- Personnel Time Management (PT) Integration Activated

By selecting this checkbox, you enable searches for personnel time data, such as normal working
times and absences, directly in the Personnel Time Management (PT) component during the
review and completion step for incident records.
- Creation of HR Absences via Process Activated

By selecting this checkbox, you enable the creation of absences in PT using a process that
automatically informs the responsible HR manager about the required changes. Enter the e-mail
address of the HR manager in the corresponding field.
You can use the report Check for Changed Absences in PT to periodically check if the required
absences have been created.
- Personnel Time Management (PT) Negative Time Recording

- Select this checkbox if you use negative time recording in the PT system. The system calculates
working hours as follows:
Working hours = regular working hours + overtime hours - absence hours.
- If you do not select this checkbox, the system calculates the working hours as follows:
Working hours = attendance hours + overtime hours - absence hours
Regular hours are hours an employee works according to the assigned working plan. Attendance
hours are hours that are captured by Personnel Time Management.
- Number of Hours Worked per Year by Full-Time Employee

Enter the number of hours one full-time employee works in one year. This value is used to calculate
the full-time equivalent (FTE) for a given number of hours.
- Number of Days Worked per Year by Full-Time Employee

Enter the number of days one full-time employee works in one year. This value is used to calculate
the full-time equivalent (FTE) for a given number of days.
- Months in Past
This value is used to calculate PT key figures for analytical reporting using the Business
Information Warehouse. If you specify a date for PT data in analytical reporting, the system
determines the data from the specified date to the specified number of days into the past.
Requirements
You have checked the settings for Personnel Time Management as described in Customizing activity
Check Customizing Settings for Personnel Time Management.
Specify Relevant HR Absence Types
Use
In this Customizing activity, you can specify which Human Resources (HR) absence types are relevant
for incident management. During incident recording, you can select an absence type to describe an
absence in more detail.
Note
The HR absence types that you specify in this Customizing activity are pulled from Human Capital
Management (HCM). In HCM, the absence type keys have assigned personnel subarea grouping (PSG).
Both the absence type key and the assigned PSG define uniquely the absence type description.
The specified absence types are taken into account by the report Check for Changed Absences in PT that,
for example, automatically notifies the responsible incident manager, if absence data of the maintained
types changed in Personnel Time Management (PT).
Note
To specify the restriction types that are relevant for incident recording, you use the Customizing activity
Specify Restriction Types.
Requirements
You have activated PT Integration in the Customizing activity Activate Personnel Time Management
Integration.
Standard settings
Activities

Schedule Jobs for HR Absence Check
Use
In this Customizing activity, you can schedule jobs for the report Check for Changed Absences in PT
(R_EHHSS_CHECK_HCM_ABS_CHANGED). You can use this report to check for absences of injured
persons that have been created or changed in Personnel Time Management (PT).
Requirements
You have activated PT integration in the Customizing activity Activate Personnel Time Management
Integration.
Implementation: Determination of FTE and Working Time from PT
Use
You can use this BAdI implementation to activate or deactivate the integration of Personnel Time
Management (PT) for analytical reporting in Environment, Health, and Safety. If you activate the
BAdI implementation, the system determines the key figure values for Full-Time Equivalents and
Working Time per organizational unit and calendar day from PT.
As only employee data is managed in PT, no key figure values are determined for external persons or
business partners. To include key figures for external persons or business partners in analytical reports,
you can create a customer-specific implementation of the Business Add-In Determination of FTE and
Working Time.You can also use an implementation of this BAdI to determine key figure values
according to company-specific determination rules.
Note
If you activate this implementation and an implementation of the BAdI Determination of FTE and
Working Time, the system combines the results of both determination runs per employee, if appropriate.
Requirements
You have specified the required forms for legal reporting in the Customizing activity Specify Forms for
Foundation for EHS for Foundation for EHS.
Standard settings
The BAdI implementation is active in the standard system.
BAdI: Determination of FTE and Working Time
Use
This Business Add-In (BAdI) is used in Environment, Health, and Safety. You can use this BAdI to
determine the key figure values for Full-Time Equivalents and Working Time according to customer-
specific rules. The key figures are determined for reporting purposes:
- Full-Time Equivalents: analytical reporting

- Working Time analytical reporting and legal reporting, for example, OSHA reporting
Note
The key figure values for Full-Time Equivalents and Working Time values are always determined per
organizational unit and date period. The system takes into account all objects (for example, employees or
business partners) that are directly assigned to an organizational unit or that are assigned to a subordinate
organizational unit.
Requirements
The following prerequisites must be met:
- You have specified the required forms for legal reporting in the Customizing activity Specify Forms
for Foundation for EHS.
Standard settings
The BAdI is not active in the standard system.
BAdI Methods
- READ_EXT_DATA
You can use this BAdI method to read person information from external sources. The method is
called for a date period for an organizational management object that is requested for analytical
reporting.
Import Parameters
- IV_FROM_DATE - Calendar date
- IV_TO_DATE - Calendar date

- IS_ORG_MAN_OBJ - Structure containing the object type and the object ID of the organizational
management object that uniquely identifies the organizational unit
Export Parameters
- EV_WORKTIME - Cumulated Working Time value for the imported calendar date and
organizational management object
- EV_NUMFTE - Cumulated Full-Time Equivalents value for the imported calendar date and
Activate Integration with SAP Management of Change
Use
In this Customizing activity, you can activate the integration with SAP Management of Change. This
enables you to add a change request as a task in Environment, Health, and Safety and communicate it
to the SAP Management of Change system.
Requirements
- You have specified the RFC destination of the SAP Management of Change system
(DEST_MOC) in the Customizing activity Specify Destinations for Integration.
- You have activated object-based navigation (OBN navigation) by defining an HTTP connection to
the SAP Management of Change system in transaction sm59.
- You have specified the RFC connection or the HTTP connection in the relevant PFCG roles.
Standard settings
Integration with SAP Management of Change is disabled in the standard system.

This integration is available for incident management and health and safety management.
Activities
If you activate the integration, the integration is activated for both incident management and health and
safety management.
If you want to later deactivate the integration, this setting also affects both incident management and
health and safety management. If you have already added change requests in an incident or a risk
assessment, you can still display existing change requests. However, you cannot add any new change
requests.
Business Add-Ins
Business Add-Ins for Authorization

BAdI: Extended Authorization Checks
Use
Product Safety and Stewardship. You can use this BAdI to enhance the standard functionality when
you define additional authorization mechanisms.
You use the authorization objects within the standard delivery to grant access to particular groups of
incidents, incident BO nodes, or incidents depending on their location. This BAdI allows you to enhance
the standard delivery and develop your own authorization checks in addition to the existing authorization
objects.
Standard settings
The BAdI is intended for multiple uses and is not filter-dependent. This BAdI is active in the
standard system and uses the following method:
- GET_AUTH_CHECK_RES
The method does not contain default implementation and allows you to implement your own
business logic that handles the additional authorization checks. The method includes the
following import parameters: Import Parameters
- IV_ACTVT - Activity
- IS_VAL_CTX - Context information for determinations
- IS_DET_CTX - Context information for validations

- IT_KEY - Key table
- IO_READ - Interface to read data
- IO_MESSAGE - Interface of message object

- IT_FAILED_KEY - Key table
- IO_MODIFY - Interface to change data
This BAdI definition uses the IF_EHFND_EXT_AUTH_CHECK interface.
Business Add-Ins for Migration
BAdI: Import of Incidents
Use
this BAdI to enhance the standard functionality when you import incidents.
You use the standard functionality to migrate incident entries to the Environment, Health, and Safety
system by importing data files. If the files contain customer-specific enhancement data, the standard
implementation may not read and migrate the data correctly. The BAdI allows you to examine the input
and manipulate the output of the migration. You can enhance the standard implementation using the
BAdI as an enhancement spot that manipulates customer-specific data. As a result, you can migrate the
data correctly.
Standard settings
The BAdI is intended for multiple uses and is not filter-dependent. This BAdI is not active in the
BAdI Methods
- IMPORT_INCIDENT
business logic that handles your enhancement data specifics. The method includes the following
import and export parameters:
Import Parameters
- IV_ROOT_KEY - BOPF key of the incident imported in the Environment, Health, and
Safety system
- IS_BASIC_INFO_ALL - Incident basic information
- IT_PERSON_INVOLVED - Incident persons involved

- IT_PERSON_ROLE - Incident person roles
- IT_PERSON_STATEMENT - Incident person statement
- IT_STATEMENT_TEXT - Incident person statement long text

- IT_PERSON_INJURED_INFO - Incident person injuries information
- IT_PERS_INJ_INT_TEXT - Person injuries internal information long text
- IT_PERS_INJ_EXT_TEXT - Person injuries external information long text
- IT_HEALTH_SAFETY_INFO - Incident safety information

- IT_INJURY_ILLNESS - Incident injuries illness information
- IT_ABSENCE - Person absences
- IT_RESTRICTION - Person restrictions
- IT_EXTENSION_DATA - Extensions data table

- IT_DAMAGE - Asset damages
- IT_EQUIPMENT - Equipment affected
- IT_TIME_DATA - Persons time data

- IT_FREETEXT - Free texts
- IT_FREETEXT_TEXT - Free texts long text

- IT_ACTIONS - Incident actions
- IT_ACTIONS_TEXT - Incident actions long text
Export Parameters
- CT_MESSAGE - Error messages
This BAdI definition uses the IF_BADI_EHHSS_INC_IMPORT interface.
BAdI: Import of Incidents (Data Transfer)
Use
this BAdI to enhance the standard functionality when you import incidents from another Environment,
Health, and Safety system.
You use the standard functionality to transfer incident entries to a Environment, Health, and Safety
system by importing data files. If the files contain customer-specific enhancement data, the standard
implementation may not read and transfer the data correctly. The BAdI allows you to examine the input
and manipulate the output of the data transfer. You can enhance the standard implementation using the
BAdI as an enhancement spot that manipulates customer-specific data. As a result, you can transfer the
data correctly.
Standard settings
The BAdI is intended for multiple uses and is not filter-dependent. This BAdI is not active in the
BAdI Methods
- IMPORT_EHSM_INCIDENT
business logic that handles your enhancement data specifics. The method includes the following
Import Parameters
- IV_ROOT_KEY - BOPF key of the incident imported in the Environment, Health, and
Safety system
- IT_KEY_MAP - Mapping table
- IT_ASSET_INVOLVED - Incident asset involved
- IT_ASSET_PROPERTY - Incident property
- IT_DAMAGE - Incident damage
- IT_EQUIPMENT - Incident equipment
- IT_VEHICLE - Incident vehicle
- IT_BASIC_INFO_ALL - Incident basic information all
- IT_PERSON_INVOLVED - Incident person involved - IT_PERSON_INITIAL -
Incident person injured info
- IT_PERSON_ROLE - Incident person role
- IT_PERSON_STATEMENT - Incident person statement
- IT_PERSON_INJ_INFO - Incident person initial
- IT_HEALTH_SAFETY - Incident health and safety information
- IT_INJURY_ILLNESS - Incident injury illness
- IT_RESTRICTED_DUTY - Incident restricted duty
- IT_TIME_DATA - Incident time data
- IT_GROUP - Incident group
- IT_REGUL - Incident regulation
- IT_RELEASE - Incident release exceptional
- IT_RELCLEAN - Incident release cleanup
- IT_RELMAT - Incident release material
- IT_VIOLATN - Incident notices of violation
- IT_NEAR_MISS - Incident near miss
- IT_SAF_OBS - Incident safety observation
- IT_FIN - Incident financial
- IT_TRA - Incident transaction
- IT_RA_TYP Incident - Risk Assesment Type
- IT_RA - Incident risk assesment
- IT_PASSENGER - Incident passenger
- IT_ACTION - Incident action
- IT_ATT_DOCUMENT - Incident documents
- IT_INV_RES - Incident investigation result
- IT_INV_STEP - Incident investigation step
- IT_INV_FRTXT - Incident investigation freetext step
- IT_INV_RC - Incident investigation root cause
- IT_INV_SUMRE - Incident investigation summary report
- IT_INV_GUIDE - Incident investigation guideline
- IT_INV_CEFF - Incident investigation control effectiveness
- IT_ENHANCE_FIELD - Enhancement data
- IT_ENHANCE_NODE - Enhancement node data
Export Parameters
- CT_MESSAGE - Error messages
This BAdI definition uses the IF_BADI_EHHSS_INC_EHSM_IMPORT interface.

Business Add-Ins for Human Resources Integration
Implementation: Determination of FTE and Working Time from PT
Use
You can use this BAdI implementation to activate or deactivate the integration of Personnel Time
Management (PT) for analytical reporting in Environment, Health, and Safety. If you activate the
BAdI implementation, the system determines the key figure values for Full-Time Equivalents and
Working Time per organizational unit and calendar day from PT.
As only employee data is managed in PT, no key figure values are determined for external persons or
business partners. To include key figures for external persons or business partners in analytical reports,
you can create a customer-specific implementation of the Business Add-In Determination of FTE and
Working Time.You can also use an implementation of this BAdI to determine key figure values
according to company-specific determination rules.
Note
If you activate this implementation and an implementation of the BAdI Determination of FTE and
Working Time, the system combines the results of both determination runs per employee, if appropriate.
Requirements
You have specified the required forms for legal reporting in the Customizing activity Specify Forms for
Foundation for EHS for Foundation for EHS.
Standard settings
The BAdI implementation is active in the standard system.
BAdI: Determination of FTE and Working Time
Use
determine the key figure values for Full-Time Equivalents and Working Time according to customer-
specific rules. The key figures are determined for reporting purposes:
- Full-Time Equivalents: analytical reporting

- Working Time analytical reporting and legal reporting, for example, OSHA reporting
Note
The key figure values for Full-Time Equivalents and Working Time values are always determined per
organizational unit and date period. The system takes into account all objects (for example, employees or
business partners) that are directly assigned to an organizational unit or that are assigned to a subordinate
organizational unit.
Requirements
The following prerequisites must be met:
- You have specified the required forms for legal reporting in the Customizing activity Specify
Forms for Foundation for EHS.
Standard settings
The BAdI is not active in the standard system.
BAdI Methods
- READ_EXT_DATA
You can use this BAdI method to read person information from external sources. The method is
called for a date period for an organizational management object that is requested for analytical
reporting.
Import Parameters
- IV_FROM_DATE - Calendar date
- IV_TO_DATE - Calendar date
- IS_ORG_MAN_OBJ - Structure containing the object type and the object ID of the
organizational management object that uniquely identifies the organizational unit
Export Parameters
- EV_WORKTIME - Cumulated Working Time value for the imported calendar date and
- EV_NUMFTE - Cumulated Full-Time Equivalents value for the imported calendar date and
Business Add-Ins for Checks
Use
this BAdI to perform checks on the following actions:

- Set status of an incident investigation to Closed
- Set status of an investigation step to Closed
For each action, a BAdI implementation is delivered that you can use to perform the corresponding check
in the standard system. If necessary, you can also deactivate the standard implementations and
implement customer-specific checks instead.
Caution
data.
Standard settings

- BADI_RDY_FOR_ACT_INC_CLOSE
You use this BAdI implementation to perform the following checks before the status of an incident
is set to Closed:
- Check if the Restricted Access attribute for the incident is set to Yes or No
- Check if an incident group is assigned
- If an investigation is required, check if the investigation is completed
- If the incident is an occupational incident, check if at least one involved person has the
Injured Person role
- If the incident is classified as Release, check if at least one release is assigned
- Check if the Reporting Required attribute for a release is set to Yes or No
- Check if risk matrix entries are complete and confirmed
- If the incident is classified as a notice of violation, check if at least one notice of
violation is assigned
- If the incident has actions assigned, check if all actions that are not recurring are complete
- For any injured person, check if the Required in Summary Report attribute is set to
Yes or No
- For any release of incident, check if the Reporting Required attribute is set to Yes or No
- BADI_RDY_FOR_ACT_NM_CLOSE
You use this BAdI implementation to perform the following checks before the status of a near miss
is set to Closed :
- If the near miss has actions assigned, check if all non-recurring actions are complete
- BADI_RDY_FOR_ACT_SO_CLOSE
You use this BAdI implementation to perform the following checks before the status of a safety
observation is set to Closed:
- If the safety observation has actions assigned, check if all non-recurring actions are complete
- Check if all inquiry processes are complete - BADI_RDY_FOR_ACT_INC_VOID /
BADI_RDY_FOR_ACT_NM_VOID /
BADI_RDY_FOR_ACT_SO_VOID
You use these BAdI implementations to implement customer-specific checks that you want to
perform before an incident, near miss, or safety observation is set to Void. The implementations do
not perform any checks in the standard system.
- BADI_RDY_FOR_ACT_INV_CLOSE
You use this BAdI implementation to perform the following checks before the status of an
investigation is set to Closed:

- Check if an investigation lead is assigned
- Check if a major root cause is selected
- Check if all investigation steps are complete (status Closed, Void, or Completed)
- BADI_RDY_FOR_ACT_STEP_CLOSE
You use this BAdI implementation to perform the following check before the status of an
investigation step is set to Closed:
- For investigation steps with the step category EHHSS_ST_CAT_ROOTCAUS, check if all
assigned actions are complete (status Closed, Void, or Completed).
· BADI_RDY_FOR_ACT_CHANGE_CAT
You use this BAdI implementation to perform the following checks before changing the category of an
incident:
o Check if incident status is set to Void or Closed o Check if incident

investigation status is In Process or Reopened o Check if HR
absence worklflow step is New or In Process o Check if incident inquiry
status is New or In Process o Check if incident report status is New or In
Process o Check if incident approval task is New or In Process
o Check if a reopened incident worklflow instance is In Process, and the
process status is not Initial
Activities
- INCIDENT_CATEGORY
- 001 Incident
- 002 Near Miss
- 003 Safety Observation
- ACTION_NAME
- SET_VOID_ROOT
- SET_CLOSED_ROOT
- INVESTIG_RESULT_SET_CLOSED
- NODE_NAME
You can use all existing node names from business object EHHSS_INCIDENT. To display the
nodes of this business object, use transaction /BOBF/CUST_UI or execute the search help
EHFND_ELM_BO_NODE_NAME in transaction SE11 in test mode using BO_NAME =
EHHSS_INCIDENT.
Example
You want to define a check that is only executed if:
- The incident is a Near Miss

- The action that is performed to set the status to Closed
- The BASIC_INFO_ALL node is processed.
To do this, set the following filter values:
- INCIDENT_CATEGORY = 002 (Near Miss)
- NODE_NAME = BASIC_INFO_ALL
BAdI: Check Incident Reports
Use
this BAdI to perform checks for data completeness in incident reports.
If you implement customer-specific checks , you must ensure that these are complete in terms of data
data.
Caution
If you deactivate or change a check, you must also ensure that all actions are complete or are in the
process of completing.
Standard settings
- BADI_IRT_CHECK_OSHA_301

- Check if the Emergency Room attribute is set to Yes or No
- Check if the Inpatient Overnight attribute is set to Yes or No
- Check if either an activity was selected, or a free text description for the injured person's
activity is maintained
- Check if a statement that can be included in reports is maintained
- If an injury/illness is maintained, check if the injury/illness information and body part
information is maintained
- Check if only the first reportable injury/illness or the first reportable unknown injury /illness is
defined
- Check if the incident-causing object or an incident-causing substance is maintained
- If the Fatality attribute is set to Yes, check if the date of death is maintained
- BADI_IRT_CHECK_BG_UNF_BER

- Check if the incident time zone is maintained
- Check if the address where the incident occurred is maintained
- Check if a statement that can be included in reports is maintained - Check if an
injury/illness is maintained.
- If an injury/illness was maintained, check if a body part is maintained
- Check if the actual end working time for the injured person is maintained
- Check if the position description is maintained
- Check if the duration in position is maintained
- Check if the organizational unit of the injured person is maintained
- Check if the ceased work date and time is maintained
- Check if end dates of absences are maintained
- BADI_IRT_CHECK_REL_REP
This BAdI implementation does not perform any checks in the standard system. You need to create
your own implementation if you want to implement customer-specific checks.
Activities
- Possible filter values for the incident category are:

- INCIDENT_CATEGORY = 001 Incident
- INCIDENT_CATEGORY = 002 Near Miss
- INCIDENT_CATEGORY = 003 Safety Observation
- Possible filter values for form names are all form names that are entered in Customizing for
Business Add-Ins for Investigation
BAdI: Investigation Lead Determination
Use
This Business Add-In (BAdI) is used in the Environment, Health, and Safety component. By default,
the investigation lead is automatically set to the current incident manager. You can use this BAdI to
change how the default investigation lead is determined.
Business Add-Ins for Health and Safety Management
BAdI: Calculate Risk Rating and Determine Risk Icon
Use
this BAdI to adapt the standard logic to calculate risk ratings and to determine the risk icons that are
displayed.
The risk icons are set according to the risk rating. The risk rating is calculated for each affected area
based on configurable scores for the following risk parameters: severity, likelihood to reoccur, frequency
and duration. The calculated value can be manually overwritten by the user.
The default logic for calculating risk ratings and determining risk icons is as follows:
- The scores of the affected areas are added.

- The rating is determined according to the lower and upper limit of the sum of scores.
- The risk icon is determined according to the risk rating configuration.
The BAdI method calculate_risk receives the precalculated sum of risk scores, the distinctive scores for
severity, likelihood to reoccur, frequency and duration, and returns the value for the risk icon.
The BAdI method calculate_risk_ext receives one additional parameter to the ones which the method
calculate_risk receives. There are no differences in the returned parameters of the two methods.
Requirements
You have made the following settings in the Customizing for Environment, Health, and Safety under
Incident Management:
Specify Severity
Specify Likelihood
Specify Frequency
Standard settings
This BAdI is active in the standard system.

Business Add-Ins for Financial Tracking
BAdI: Integration of Financial Transaction Objects
Use
this BAdI to enable access to cost collectors in other components for financial tracking. The components
can either be managed locally or in a remote system.
This BAdI is delivered with active implementations for the following types of cost collectors:
- Internal order (Accounting (AC))

- Maintenance order (Plant Maintenance (PM))
To enable access to other cost collectors, you can create additional BAdI implementations. The following
methods are available:
- ADD_FIN_TRANS_OBJECT (Add Financial Transaction Object)

This method is executed when you add a financial transaction to an incident record.
- DETAILS_FIN_TRANS_OBJECT (Display Details for Financial Transaction Object) This

method is executed when you display the details for a financial transaction object.
- REFRESH_FIN_TRANS_OBJECT (Refresh Data for Financial Transaction Object)
This method is executed when you refresh the list of financial transaction objects.
If this BAdI is implemented, you can assign cost collectors from integrated components as financial
transactions to an incident record.
Note
If you have defined an enhancement including customer-defined dialog boxes for the application
configuration EHHSS_INC_REC_OIF_V3, you can use implementations of the BAdI methods
ADD_FIN_TRANS_OBJECT and DETAILS_FIN_TRANS_OBJECT to specify which dialog boxes are
called when you assign cost collectors to an incident.
Requirements
- In the Customizing activity Specify Financial Transaction Categories, you have added a financial
transaction category for each cost collector type that you want to use for financial tracking. You
have selected the IntegrObj checkbox for these categories.
- If you want to use cost collectors in components that are managed in a remote system, you have
defined the required RFC destinations in the Customizing activity Specify Destinations for
Integration.
Standard settings
- BADI_EHHSS_FIN_TR_INT_ORDER
This BAdI implementation enables access to internal orders that exist in Accounting.
- BADI_EHHSS_FIN_TR_MAINT_ORDER
This BAdI implementation enables access to maintenance orders that exist in Plant Maintenance.
Activities
You must create a BAdI implementation for each financial transaction category that refers to an
integration object. Use the financial transaction category as the filter value for the filter
FIN_TRANS_CAT.
Business Add-Ins for Print Forms and Interactive Forms
BAdI: Electronic Report Shipment
Use
This Business Add-In (BAdI) is used to send incident reports in the Environment, Health, and Safety
component. You can use this BAdI to implement customer-specific logic for electronically shipping
reports to a receiving party, for example, a legal authority, such as the German workers' compensation
association. The BAdI allows you to adapt the report shipment process to company-specific requirements
by enabling the use of different exchange formats and different channels of communication. You can, for
example, use the BAdI if you want to send incident reports in an XML format via a Web service.
This BAdI is called before a report is sent to determine if a BAdI implementation exists for
that type of report. If an implementation exists, you can choose to send the report electronically, and the
system calls the BAdI again in the report shipment process. The BAdI then uses the SEND_REPORT
method to do the following:
- Generate the report in the correct output format

- Ship the report to the receiving party
- Complete the shipment process by reporting the success or failure of the shipment back to the
system
Requirements
- You have configured the process foundation in Customizing for Environment, Health, and
Safety under Foundation for EHS -> Process Foundation. Ensure that the event linkage is
active in activity Activate Linkage for Scheduled Processes.
- You have configured the processes used in incident management, specifically the following process
definition, in Customizing activity Configure Process Definitions:
Component: HSS
Purpose: INC_REPORT
Variant: STANDARD
- You have specified task recipients in Customizing activity Assign Default Roles to Workflow
Tasks.
Standard settings
The standard system does not include a default implementation for the BAdI.
See also
For more information about electronic report shipment and about the actions that are required to adapt
the shipment process to your needs, see the technical documentation for this BAdI in the BAdI Builder.
Business Add-Ins for Regulations
BAdI: Establishment Enhancements for OSHA300 Generation
Use
this BAdI to enhance the standard delivery when you want to generate OSHA 300 reports based on an
establishment different from the organizational unit.
The OSHA regulation requires that a separate OSHA 300 log be kept for each physical location
that is expected to be in operation for one year or longer. In the standard delivery, the data in OSHA 300
reports is calculated based only on organizational units. However, this prevents you from generating
OSHA reports based on other criteria, such as, plants or locations.
The BAdI provides means to overwrite or enhance the existing standard method and thus allows you to
enhance the standard delivery and provide your own establishments that you can use to generate OSHA
300 reports.
Standard settings
The BAdI is intended for multiple uses and is not filter-dependent. This BAdI is active in the standard
BAdI Methods
- FIND_PERSONS
The method contains default implementation and allows you to implement your own business logic
that handles your specific generation of OSHA 300 reports. The method includes the following
Import Parameters
- IS_INC_CONTEXT - Context of an incident form.
- IO_BO_ACC - Provides access to the implementation of the business objects.
Export Parameters
- EO_PERSON_INJ_INFO - Custom BOPF node.
- ES_FORM_CONTEXT - Interface structure for OSHA 300 report.
This BAdI definition uses the IF_BADI_EHHSS_INC_OSHA300 interface.

BAdI: Establishment Enhancements for OSHA300A Generation
Use
this BAdI to enhance the standard delivery when you want to generate OSHA 300A reports based on an
establishment different from the organizational unit.
The OSHA regulation requires that a separate OSHA 300A log be kept for each physical location that is
expected to be in operation for one year or longer. In the standard delivery, the data in OSHA 300A
reports is calculated based only on organizational units. However, this prevents you from generating
OSHA reports based on other criteria, such as, plants or locations.
The BAdI provides means to overwrite or enhance the existing standard method and thus allows you to
enhance the standard delivery and provide your own establishments that you can use to generate OSHA
300A reports.
Standard settings
BAdI Methods
- FIND_PERSONS
that handles your specific generation of OSHA 300A reports. The method includes the following
Import Parameters
- IS_INC_CONTEXT - Context of an incident form.
- IO_BO_ACC - Provides access to the implementation of the business objects.
Export Parameters
- EO_PERSON_INJ_INFO - Custom BOPF node.
- ES_SUMMARY_NUMBERS - Summary of numbers for reporting; comprises the amount of

cases and days.
- ES_FORM_CONTEXT - Interface structure for OSHA 300A report.
This BAdI definition uses the IF_BADI_EHHSS_INC_OSHA300A interface.
Business Add-Ins for Incident Category
BAdI: Change Incident Category
Use
this BAdI to enhance the standard delivery when you want to change the incident category (incident, near
miss, or safety observation).
Using the standard delivery, you can change the incident category to any of the other pre-defined
categories. In this case, the application verifies both the current and the new incident categories and
merges the applicable incident data into the new incident category. The following rules apply:
- Common incident data for both categories is preserved and remains in the new category.
- Data that is applicable only for the current incident category is deleted and not added to the
new category.
For example, incident groups differ from the near miss groups and thus the incident groups are
deleted and not added to the near miss.
- Incident data from the current incident category that is inconsistent with the new category can
be provided in a separate dialog in the incident management application. For example, in the
dialog that opens during the category change, you can replace the injured person role
(assigned to a person in the incident) with the nearly injured person role (in the near miss).
The BAdI enables you to enhance the standard delivery and provide custom business logic to handle
differently the data that is potentially inconsistent with the new incident category.
Standard settings
BAdI Method
- CHANGE_CATEGORY
to handle the data of the incident category you want to set. The method includes the following
Import Parameters
The import parameters represent the incident BO nodes that potentially contain differences between
the current and the new incident category. Using the parameters, you can manipulate directly the
BO nodes influenced by the change. Furthermore, you can map the current category-specific data in
the BO nodes to the new incident category and thus provide automatic data provisioning by the
program in the new category.
- IV_ROOT_KEY - NodeID
- IV_CATEGORY_CODE - Incident Category

- IT_INC_GROUP - Change Category: Group Table
- IT_INC_REGULATION - Change Category: Regulation Table

- IT_INC_PERSON_INVOLVED - Change Category: Person Involved Table
Export Parameters
- EO_MESSAGE - Interface of Message Object
This BAdI definition uses the IF_BADI_EHHSS_INC_CHANGE_CAT interface.
Business Add-Ins for Integrated Notifications
BAdI: Creation and Completion Check of Integrated Notifications
Use
this BAdI when you want to enhance both the creation of integrated notifications and the completion
checks of these notifications, in the standard delivery of incident management.
When you create a maintenance notification task in incident management, a default method takes the
information from the maintenance notification and then sends it to Plant Maintenance (PM) for further
processing. However, if you specified custom fields for a notification, the method in the standard
delivery cannot handle the information in these fields and thus cannot send the entire notification for
processing.
The BAdI enables you to enhance the standard delivery or completely replace the business logic of the
default method and provide your own logic for creating integrated notifications or getting the completed
notifications from the corresponding functional areas.
Standard settings
The BAdI is intended for multiple uses and is filter-dependent. It depends on the category code of the
incident action (EHFND_ACT_CATEGORY_CODE). The following category code is used for filtering:
- 002 Maintenance Notification

Depending on the type of the notification you want to create, there are implementations of the BAdI.
This BAdI is active in the standard system and uses the following methods:
BAdI Methods
- CREATE_EXT_NOTIFICATION
to create an integrated notification. The method includes the following import and export
parameters:
Import Parameters
- IV_NOTIF_TYPE - Integrated notification type
- IS_NOTIF_HEADER - Integrated notification header

- IV_RFC_DEST - RFC destination to the external functional area
Export Parameters
- EV_NOTIF_ID - Integrated notification ID
- ET_RETURN - Table with BAPI return information
- GET_COMPLETED_NOTIFICATIONS
The method contains default implementation and allows you to implement your own business
logic to get the completed notifications from the corresponding functional areas and set their status
in incident management. The method includes the following import and change parameters:
Import Parameters
- IS_ACTION - Incident action root
Change Parameters
- CT_NOTIF - Table of IDs of completed integrated notifications
- CO_MESSAGE - Interface of message object
This BAdI definition uses the IF_BADI_EHFND_EXT_NOTIF_CREATE interface.
Health and Safety Management
Specify Number Range Intervals for Health and Safety Management
Use
In this Customizing activity, you can define number range intervals.

A unique number is assigned to each record created in Environment, Health, and Safety. The
appropriate number range object determines the number automatically.
You can define number range intervals for the following number range objects:
- EHHSSAGTID - Agent ID
Note that this number range object is used for physical and airborne agents. For chemicals,
you must maintain the chemical number range object in Customizing activity Specify Number
Ranges for Foundation.
- EHHSSHSPID - Protocol ID
Note that this number range object is used for health surveillance protocols, an integrated object
from the EHS Management as part of SAP ERP system. For more information about integrating
with other systems, see Specify Destinations for Integration.
- EHHSSJOBID - Job ID
- EHHSSSTEP - JHA - Step ID
- EHHSSRASID - Risk Assessment ID
- EHHSSRSKID - Risk ID
- EHHSSSEGID - Similar Exposure Group ID
- EHHSSCINID - Control Inspection ID
- EHHSSSPLCP - Sampling Campaign
- Specify Number Range Intervals for Foundation

- Specify Number Range Intervals for Incidents
Standard settings
internal interval.
We recommend disjunct number ranges for agents and chemicals. In the standard system, the agent
number range is from 0 to 99999, and the chemical number range starts at 100000. This enables
unique identification of physical agents and chemical agents.
Activities

Note
Specify Graphics
Use
In this Customizing activity, you can specify graphics you can use, for example, as labels for dangerous
chemicals.
Requirements
The graphic is loaded into the MIME repository in transaction Object Navigator (SE80).
Note: Graphics used for labeling of dangerous chemicals are under SAP -> BC ->
WebDybpro -> SAP -> PUBLIC -> EHSM -> Chemical_Data_Management Repository.
If you want to use graphics other than the provided ones, you can upload your own graphic into the
MIME repository after you have defined a path where the graphic should be stored.
Standard settings
Activities

Specify Risk Assessment Types
Use
In this Customizing activity, you can specify risk assessment types. The application is delivered
with services to create risk assessments based on each of the specified risk assessment types.
You can also specify which risk assessment types involve agents. In the application, this setting enables
you to specify agents during risk identification, analyze exposure to them, and later use the exposure data
in similar exposure groups and personal exposure profiles. In addition, you can specify which risk
assessment types contain job-based information. In the application, this setting enables you to create a
job hazard analysis for this risk assessment types.
Standard settings
Activities

- If you want to use agents in the risk assessment type, select the Agents checkbox. Note: If you
want to create similar exposure groups based on jobs, you must enable agents for the risk
assessment types you want to use for a job hazard analysis.
- If you want to use a risk assessment type for a job hazard analysis, you must select the Job-Based
checkbox.
2. If you want to define additional entries, proceed as follows:
- For each new entry, create a new service in the menu of the relevant role in transaction
PFCG. This makes the new risk assessment type visible in the application menu for the
users assigned to this role. Make the following entries for the service as required:
- Web Dynpro Application: EHHSS_RAS_OIF
- Description: <description specified by customer in Customizing entry>
- Parameter CHANGE_MODE: C
- Parameter RAS_TYPE: <unique key specified by customer in Customizing entry> -
Parameter sap-explanation: X (if you want to enable screen explanations on the
UI)
In Other Node Details for the service, enter under Object-Based Navigation the method
bpr_eh_ras.Create.
- For each new entry, you have to create a new implementation of the Business Add-In
BAdI: Check Readiness for Action.
- For each new entry, you have to specify the severity to calculate the risk level in
Customizing activity Specify Severity.
Specify Reason Types
Use
In this Customizing activity, you specify reason types for assessment reasons and make settings for
reason types that cite data objects as references. In a risk assessment, you can enter a reason for
performing the risk assessment and cite the corresponding reference (such as a URL, attached document,
or data record) on the Basic Information tab.
You can also extend the standard settings to enable referencing the following integrated objects as
assessment reasons:
- Incident (Environment, Health, and Safety)

- Change request (SAP Management of Change)
Requirements
- If you want to reference change requests as an assessment reason, you have activated integration in
Customizing activity Enable/Disable Integration of Risk Assessment Requests.
- If you want to reference incidents, you have ensured in the ABAP workbench that the relevant
search help for the object is included in the append search help
EHHSS_CLC_RAS_REASON_APPEND.
Note: Although the incident is a business object of Environment, Health, and Safety, it is
handled as an integrated object. This means, the incident ID search help
(EHHSS_ELM_INC_ID_SE) has been included in the append search help
EHHSS_CLC_RAS_REASON_APPEND to enable you to search for an incident from within the risk
assessment. The search help for incidents returns the key of the root (/BOBF/CONF_KEY of
business object EHHSS_INCIDENT) of the selected incident to enable navigation to the actual
incident data record.
Standard settings
Activities

3. If you want to enter an integrated object as the assessment reason, perform the following steps:
a) Select the IntegrObj checkbox to indicate an integrated object. If you deselect the checkbox,
you can only reference URLs or documents for the reason type.
b) For referencing incidents, specify a search help. This enables the system to determine which
data records can be assigned as a reference to the assessment reason.
c) If you want to enable links from the risk assessment to the data record of the integrated object,
specify the name of the relevant business object.
d) For referencing change requests, select the requester type Change Request from
4. If you do not use integrated objects, remove the irrelevant entries.
Further information
If you want to integrate objects not listed above from other SAP components, ensure that the required
authorizations are available to permit the risk assessment append search help to use the search help of the
integrated component.
Specify Roles for Health and Safety Management
Use
In this Customizing activity, you can define the roles that can be assigned to people who are involved in
health and safety management.
Standard settings
The Assessment Lead (EHHSS_RAS_LEAD) role is required in workflows to determine the receiver of
notifications.
Activities

3. If you also use similar exposure groups (SEGs), you must also perform Customizing activity
Specify Roles for Similar Exposure Groups.
Specify Administrator for Requests
Use
During a risk assessment process, you can request new entries for any hazards, impacts, controls, or
agents that you identify as missing.
In this Customizing activity, you can specify an administrator for these requests.
When you request a new entry, the system notifies the administrator by e-mail about the request. The
administrator is responsible for evaluating the request and adding the new entry in Customizing, if
necessary.
Requirements
The administrator is authorized to change settings in Customizing.

Activities
Enter the e-mail address and language of the administrator.
Specify Regulations
Use
In this Customizing activity, you can specify which regulations in Environment, Health, and Safety
are used in the health and safety management application. For each regulation, you can specify a
hyperlink as reference and define the MIME repository path that specifies where you have stored risk
symbols specific to the regulation. Note that risk symbols are only relevant if Plant Maintenance (PM)
integration is enabled.
You can also specify to which countries and regions each regulation applies. The system compares the
countries and regions assigned to each regulation and those assigned to the location of the risk to
determine which occupational exposure limits are available for exposure analyses.
Note: If you specify a country, but no region, the regulation applies to all regions within the country.
Requirements
- You have created regulations in the Customizing activity Create Regulations.

- You have made the country and region settings in the Customizing activities for SAP NetWeaver
under General Settings -> Set Countries.
Standard settings
Activities

See also
To maintain a default MIME repository path and for more information about required authorizations for
maintaining MIME objects, see Specify Default MIME Repository Path.
Specify Objectives and Targets
Use
In this Customizing activity, you can specify your organization's objectives and the corresponding targets
that must be met to achieve those objectives. During a risk assessment process, you can specify targets
for controls.
Standard settings
Activities

Specify Operational Statuses
Use
In this Customizing activity, you can specify operational statuses that are relevant to risk assessments.
You use the operational status of a location to indicate the mode of operation, such as maintenance or
normal operation, to which the risk assessment applies.
Standard settings
Activities

Note: Operational statuses are sorted alphanumerically by operational status code.
If you want to specify the order of the statuses, we recommend you include numbering in the
operational status code. We recommend using the pattern
EHHSS_OPSTATUS_<number>_<description>, for example, EHHSS_OPSTATUS_1_NORMAL.
0 Specify Default MIME Repository Path
Use
In this Customizing activity, you specify the default path for the MIME repository where you have stored
risk symbols for hazards, regulations, and controls.
If Plant Maintenance (PM) integration is enabled, you can export risk assessment information and
corresponding risk symbols to the PM component. When exporting risk symbols, the system identifies
whether a specific MIME repository path is specified for the regulations assigned to the risk assessment.
If a specific path is not specified or no regulations are assigned to the risk assessment, the system uses
the default path for the MIME repository.
You can specify specific MIME repository paths for regulations in the Customizing activity
Specify Regulations.
Note: Risk symbols are only used in the PM component. You can enable PM integration in the
Customizing activity Activated and Configure PM Integration.
Prerequisites
To maintain objects in the MIME repository, you require authorization object S_DEVELOP for the
ABAP Workbench for the object type SMIM (object from MIME repository) and permissions for
activities 01, 02, 03, 06 (insert, modify, show, and delete). For only read permissions, use activity 03
(show).
Standard settings
The standard system is delivered without any specified MIME repository paths or risk symbols.
1 Specify Document Types for Business Objects
Use
In this Customizing activity, you can specify document types for a business object.
In the application, you can upload only documents of the type you specified in this Customizing activity
to a business object.
Requirements
If you want to use document types other than the delivered ones, you have enhanced the fixed values of
domain EHFND_DOC_TYPE with a fixed value append.
Standard settings

Activities

Note: You can only define document types for the following business objects:
- Chemical (EHFND_CHEMICAL)
- Sampling Campaign (EHHSS_SAMPLING_CAMPAIGN) For other business objects,

document types are not supported.

Use
this BAdI to perform checks on the following actions in the risk assessment data record:

For each action and for each risk assessment type, a BAdI implementation is delivered in the standard
system to perform the check. The check ensures, for example, that all tasks have been completed before
you can change the status of the data record. If necessary, you can deactivate the standard
implementations and implement customer-specific checks instead.
Caution
consistency.
Standard settings

BAdI Methods
The BAdI has the following methods:
- IF_BADI_EHHSS_RAS_RDY_FOR_ACT~CHECK_COMPLETENESS_ON_ACTION - Check
completeness on the action given by filter value
The system executes this method when you change the status. The method checks the risk
assessment and can return a success, warning, or error message, or no message. The system returns
an error when recurring tasks are still open and prevents the status change. Otherwise, the system
changes the status.
- IF_BADI_EHHSS_RAS_RDY_FOR_ACT~FURTHER_ACTIONS_AFTER_CHECK - Additional
actions after checking completeness
The system executes this method after the check when it changes the status. The method does not
provide functionality in the standard system. You can use this method to create customer-specific
functionality that executes additional actions on the risk assessment.
You can use the following BAdI implementations for environmental risk assessments:
- BADI_RDY_FOR_ACT_RAS_ENV_CLOSE
Checks that all tasks are completed before the status is set to Closed.
- BADI_RDY_FOR_ACT_RAS_ENV_VOID
Checks that all tasks are completed before the status is set to Void.
You can use the following BAdI implementations for health risk assessments:
- BADI_RDY_FOR_ACT_RAS_HEA_CLOSE
- BADI_RDY_FOR_ACT_RAS_HEA_VOID
You can use the following BAdI implementations for safety risk assessments:
- BADI_RDY_FOR_ACT_RAS_SAF_CLOSE
- BADI_RDY_FOR_ACT_RAS_SAF_VOID
You can use the following BAdI implementations for job hazard analyses:
- BADI_RDY_FOR_ACT_RAS_JHA_CLOSE
- BADI_RDY_FOR_ACT_RAS_JHA_VOID
Activities
- RAS_TYPE (Risk Assessment Type)

- EHHSS_RAT_ENV (Environmental Risk Assessment)
- EHHSS_RAT_HEA (Health Risk Assessment)
- EHHSS_RAT_JHA (Job Hazard Analysis)
- EHHSS_RAT_SAF (Safety Risk Assessment)
- ACTION_NAME (action of business object EHHSS_RISK_ASSESSMENT for node ROOT)
- SET_VOID_ROOT
- SET_CLOSED_ROOT
- NODE_NAME (node name of business object EHHSS_RISK_ASSESSMENT)
- ROOT
Example
You want to redefine a check that the system executes for a job hazard analysis when you change the
status from In Progress to Closed:
- Deactivate the delivered BAdI Implementation BADI_RDY_FOR_ACT_RAS_JHA_CLOSE.

- Create a new BAdI Implementation with following filter values:
- RAS_TYPE = EHHSS_RAT_JHA
- NODE_NAME = ROOT
- During the creation process, you can choose to do one of the following:
- Create a completely new class for your checks. - Copy an existing example class and enhance it.
- Create a new class deriving from the delivered example class.
Process Configuration
Adapt Workflows for Health and Safety Management

Use
In this activity, you can learn about the organizational activities for adapting the workflows of SAP
Business Workflow to suit your customer-specific processes. The process foundation of the
Environment, Health, and Safety component makes integration with workflows possible. You can
adapt workflows to your processes in the following ways:
- Change the workflow template

- Add steps within a process
- Call further logic from a workflow task (process step)
Requirements
- You have specified processes for the health and safety (HSS) component in the Customizing
activity Specify Process Definitions under Foundation for EHS.
- You have checked the processes by implementing the Customizing activity List Configured
Processes under Foundation for EHS.
Standard settings

The following workflow templates are delivered with the corresponding PCO class/triggering event:
Workflow Template Class Name/Triggering Event
00600060 - EHHSS_RRQ CL_EHHSS_PCO_RAS_REQUEST
00600072 - EHHSS_RAS_RP CL_EHHSS_PCO_RAS_CONTROL_RPL
00800016 - EHHSS_RA_FTC CL_EHHSS_PCO_RA_FTC_NOTIFIC
00800018 - EHHSS_RAS_AC CL_EHHSS_PCO_RAS_ACTION_STD
00800019 - EHHSS_RAS_PM CL_EHHSS_PCO_RAS_ACTION_PM
00800025 - EHHSS_RA_RAM CL_EHHSS_PCO_RA_AMOUNTS
00800028 - EHHSS_RAS_AP CL_EHHSS_PCO_RAS_APPROVAL
00800029 - EHHSS_RAS CL_EHHSS_PCO_RAS_LIFECYCLE
00800031 - EHHSS_RAS_SI CL_EHHSS_PCO_RAS_SIGNATURE
00800032 - EHHSS_RAS_EV CL_EHHSS_PCO_RAS_EVL_INQUIRY
00800033 - EHHSS_RSKREL CL_EHHSS_PCO_RAS_RSK_REL
00800040 - EHHSS_RA_IMP CL_EHHSS_PCO_RAS_IMP_NOTIFIC
00800041 - EHHSS_RA_HAZ CL_EHHSS_PCO_RAS_HAZ_NOTIFIC
00800042 - EHHSS_RA_AGT CL_EHHSS_PCO_RAS_AGT_NOTIFIC
00800049 - EHHSS_RAS_CF CL_EHHSS_PCO_RAS_EVL_INC_CFA
00800050 - EHHSS_RA_CTR CL_EHHSS_PCO_RAS_CTRL_NOTIFIC
Activities
To adapt workflows, you can perform the following activities:
- You can change the process flow directly in the workflow template (in the Workflow Builder), or
copy the delivered template to the customer-specific namespace.
- You can add additional steps within a process by performing the following steps:
1. Change the workflow template (or copy the delivery to the customer-specific namespace)
2. Create further steps and (if necessary) workflow tasks in the customer-specific namespace in the
Customizing activity Define Tasks and Actions for Cross-Application Components.
3. Add the new tasks to the workflow inbox configuration in the Customizing activity Assign Task
IDs to POWL Types for Cross-Application Components. Enter the application ID
EHHSS_INBOX and the POWL type EHHSS_INBOX_TYPE for your task.
4. Activate the workflow template.
- You can add logic that can be called from a workflow task (process step) by performing the
following steps:
1. Create a PCO class that inherits from the delivered class of the process that is specified in the
Customizing activity Configure Process Definitions. It is recommended to inherit from the delivery
class and adapt it with further public methods. To include your business logic, use one of the
following two options:
- Implement the logic directly in the PCO method.
- Implement the logic in a BOPF action of the corresponding process control business object
(PCBO). Note: this is the architecture that Environment, Health, and Safety follows.
2. Use the standard event (WORKITEM_COMPLETED) if you open a dialog and the workflow has to
wait for an event. If you want to use a more specific event, you must define the new event on the
PCO class. For the dialog to raise the new event to continue the workflow, you can use the static
method RAISE_WF_EVENT of the root PCO CL_EHFND_WFF_ROOT_PCO.
3. After you have finished implementing and adapting the workflow template, configure the new PCO
class in the process definition in the Customizing activity Configure Process Definitions under
Health and Safety Management.
Configure Process Definitions
Use
In this Customizing activity, you can configure the processes used in the health and safety management
application of the Environment, Health, and Safety component.
Requirements
- You have specified processes for the health and safety (HSS) component in the Customizing
activity Specify Process Definitions under Foundation for EHS.
- You have ensured that the linkage between PCO classes and the corresponding workflows of SAP
Business Workflow is correct by implementing the Customizing activity List Configured
Processes under Foundation for EHS.
Standard settings

You can identify the process definitions for health and safety management by the technical key of the
purpose (RAS_*).
Activities
3. If necessary, select the Exclude checkbox to exclude a process from process monitoring and
analysis.
Note that entries you change in this activity are changed as well in the Customizing activity Specify
Process Definitions under Foundation for EHS.
Assign Default Roles to Workflow Tasks
Use
In this Customizing activity, you can assign default roles to workflow tasks that are used in the health
and safety management application of the Environment, Health, and Safety component. It is important
that you execute this activity in order to use the process foundation.
Requirements
- You have set up the workflow system in the Customizing activity Perform Automatic Workflow
Customizing for Foundation for EHS.
- You have assigned the roles used in this activity to the required users in the transaction PFCG.
- You are authorized to edit roles for tasks in the workflows.
Standard settings
In the standard system, there are no agents assigned to the workflow tasks used in health and safety
management.
The standard system is delivered with default roles.
Activities
To implement the standard setup and automatically assign the roles, execute this activity once.
For more information about the tasks and the roles that are assigned by this activity, see the report
Automatic Configuration of Roles for Tasks (R_EHHSS_RAS_CONFIG_TASK_ROLES).
Further information
You can assign roles manually to tasks by opening each task in transaction PFTC_CHG.
Master Data Configuration
Locations
Specify Roles of Person Responsible
Specify Role of Person Responsible
Use
In this Customizing activity, you can specify the roles of persons responsible for special tasks at a
location. You can allow multiple persons responsible to be assigned to a role for location.
Standard settings

The Operator role is set by default as assigned to multiple persons responsible.
Activities

Note: When you set the corresponding flag for a role, the system allows you to assign multiple persons to
the selected role for a specific location. When this option is not enabled in customizing it is only possible
to assign one person responsible for a given role.
Example
An environmental manager, for example, responsible for scheduling data collections. Persons with this
role can schedule the collection of measurement data from devices within the industrial plant.
Specify Role of Person to Receive Chemical Approval Requests
Use
In this Customizing activity, you can specify which role receives a newly created chemical approval
request.
Standard settings
Activities
Specify which role receives the task directly after a chemical approval request has been submitted.
Note: This activity starts a report. After you have entered the role, you have to execute the report by
choosing the Execute button. The report saves your entry. By choosing the Save button, you can save a
report execution variant.
Example
A chemical approval request has been submitted for a certain location. The person that is assigned to this
location as a person responsible with the role that is specified in this Customizing activity, receives a task
to open the approval dialog and to carry out the required steps to approve the chemical. If there is no one
with the specified role assigned at the location, someone with this role at a location higher up in the
hierarchy is selected.
Specify Role Responsible for Initial Chemical Risk Identification
Use
In this Customizing activity, you can specify which role performs the risk identification process.
Standard settings
Activities
Specify which role receives the workitem to perform the risk identification process.
Example
After a chemical has been approved for use at a specific location, someone must check whether there are
risks associated with this chemical that have not yet been identified. The person at this approved
location, who has been assigned the role specified in this Customizing activity, receives a workitem to
identify risks for this location. If there is no-one with the specified role at the location, someone with this
role at a location higher up in the hierarchy is selected.
Specify Role Responsible for Sampling
Use
In this Customizing activity, you can specify which role is responsible for sampling.
In the application, you can select a person responsible for sampling if the person is assigned to the role
you specified in this Customizing activity.
Requirements
You have specified the role in Customizing activity Specify Role of Person Responsible.
Standard settings

Specify Role for Local Emergency Contact Person
Use
In this Customizing activity, you can specify which role is displayed as the local emergency (first aid)
contact.
Requirements
The role that you want to specify in this Customizing activity must be defined in the Specify Role of
Person Responsible Customizing activity as well.
Standard settings
Activities
Specify the role that is displayed as the first aid contact in the Retrieve Safety Information app.
Specify Location Types
Use
In this Customizing activity, you can define the type of location.

You can use the location type to search for a location.
Standard settings
Activities

Enable/Disable PM Integration for Locations
Use
In this Customizing activity, you can enable or disable the integration for locations with the Plant
You can use the PM integration to import locations from PM and also to link existing locations to PM
technical objects.
Requirements
If you want to navigate in the application from the location to the linked PM technical object and display
its data, ensure that your system fulfills the following requirements:
- You are using SAP enhancement package 5 for SAP ERP 6 or higher on the integrated PM system.
- You have activated the business function LOG_EAM_SIMPLICITY in the PM system.
Note that it is still possible to integrate PM technical objects without this navigation function.
Activities
Once you have activated integration and used an integrated PM object in the application, you should keep
integration activated. Deactivating integration can lead to data inconsistency.
Schedule Jobs for Location Synchronization
Use
In this Customizing activity, you can schedule a background job to synchronize the master data for the
locations that are linked to objects in the Plant Maintenance (PM) component. This ensures that the
location data is up-to-date, for example, in search screens, analytical reports, and so on. If you do not use
the report, or the system has not run the scheduled report yet, you can open a location's master data to
synchronize that location's data with PM.
Requirements
- You are authorized to read data from the PM system and to update locations.
- You have enabled PM integration in the Customizing activity Enable/Disable PM Integration for
Locations.
- You have linked locations to PM technical objects.
Activities
1. Use the Job Wizard to specify the general data and schedule the job. You define the job for the
report R_EHFND_SYNCEAM_LOCATION.
2. Schedule the job to run as a background job once a day. If the PM data rarely changes, you can
schedule the background job to run less frequently.
Note: The background job queries all integrated technical objects for changes. The number of integrated
objects can create additional load for the Environment, Health, and Safety and PM systems and affect
performance.
Specify Evaluation Paths for Position Details

Use
In this Customizing activity, you can specify the evaluation paths for retrieving the objects assigned to a
position from the Organizational Management (PA-OS) component. This activity enables you to
assign a position to a location, and then display the people who currently occupy that position.
When you assign a position to a location, the position ID is stored in the location. The system uses a
function module to read the current organizational structure and evaluate it along the configured
evaluation path. The system returns the corresponding objects for the ID, such as business partners and
employees, at runtime.
Requirements
- You have integrated the system with the PA-OS system and the organizational structure is available
locally in the Environment, Health, and Safety system.
- You have entered evaluation paths in Customizing for PA-OS under Personnel Management ->
Organizational Management -> Basic Settings -> Maintain Evaluation Paths.
Standard settings
The entry delivered in the standard system is an evaluation path to return all people associated with a
position.
Activities
Check the existing evaluation path and specify additional entries, if necessary.
Specify Authorization Groups
Use
In this Customizing activity, you can define authorization groups.

You can assign authorization groups to locations. The authorization groups are used in the authorization
checks for the location. This way, you can restrict access to certain locations to specific users.
There are no separate authorization groups for the location structure. All actions performed inside the
location structure ascribe to the authorizations for the location.
Standard settings
Activities

Configure Integration of Map
Use
In this organizational activity, you can learn about how to enhance the location Web Dynpro to include a
map function in the side panel. This enables users to visualize the position of a location on a map.
You can implement the map function by using a third party CHIP to interpret and display the string
parameter from the location address.
Requirements
You have a map provider that is capable of interpreting an address string and displaying it on a map.
Standard settings
The standard system is delivered without an integrated map.
The location provides tagging for the tag name EHFND_LOC_ADDRESS. The address string is built
from the address fields entered in a location. If geographical coordinates are specified, they will take
priority over the address.
Activities
To integrate a map, perform the following steps:
1. Create a side panel entry for the map in the embedded side panel.
2. Create a Web Dynpro CHIP that is capable of interpreting an address string and displaying it on a
map. In most cases, this will be a URL CHIP (see the example below).
3. Create an enhancement of the Location Side Panel (Web Dynpro Configuration:
EHFND_LOC_OIF_SIDE_PANEL). In this enhancement configuration, integrate the Web Dynpro
CHIP that you created for displaying the map. Use the "EHFND_LOC_ADDRESS" tab to enable
automatic wiring (tagging); otherwise, the map will not be displayed automatically.
Example
Map providers that offer URL parameters can be integrated as a Web Dynpro URL CHIP.
An example URL would be: http://your-map-provider/map?address=<EHFND_LOC_ADDRESS>
The <EHFND_LOC_ADDRESS> tag will be automatically completed with the current
location's corresponding address string.
Actions and Controls
Specify Types
Use
In this Customizing activity, you can specify types for actions, notifications, and controls.
When you create an action or a notification in the application on the Tasks tab, you can choose the type
from the values you specified in this activity. You can classify controls using the subtype in the hazard
and control register.
Standard settings

Register.
Activities


Specify Subtypes
Use
In this Customizing activity, you can specify subtypes for actions, notifications, and controls.
When you create an action or a notification in the application on the Tasks tab, you can choose the
subtype from the values you specified in this activity. You can classify controls using the subtype in the
hazard and control register.
Requirements
You have made the settings for Customizing activity Specify Types for Foundation for EHS.
______________________________________________________________
SAP System
Standard settings
Register.
Activities


Specify Effectiveness
Use
In this Customizing activity, you can specify the effectiveness for actions and notifications.
When you create an action or a notification in the Environment, Health, and Safety component, you
can choose the effectiveness from the values you specify in this activity.
Standard settings
Activities


Specify Protection Goals
Use
In this Customizing activity, you can specify the protection goals for actions and notifications.
______________________________________________________________
SAP AG 144
______________________________________________________________
SAP System
can choose the protection goal from the values you specify in this activity.
Activities


Specify Priority Mapping for Notifications
Use
In this Customizing activity, you can specify the mapping between the priority of notifications used in the
component Environment, Health, and Safety and the priority of notifications used in Plant
Based on the priority in the notification in Environment, Health, and Safety, a notification is created in
the corresponding component with the specified priority.
Requirements
- You have configured priorities in the Customizing activity Define Priorities.

- If you use RFC destinations for creating notifications in another system, you have configured
priorities in the connected system under Cross-Application Components -> Notification ->
Notification Processing -> Response Control -> Define Priorities. Note: You can check
whether you have configured RFC destinations for other systems in the Customizing activity
Specify Destinations for Integration.
Activities
Specify the mapping of notifications priorities. If no priority mapping is configured, the corresponding
notification in another component will be created without any priority.
______________________________________________________________
SAP AG 145
______________________________________________________________
SAP System
Standard settings
Specify Priority Due Date Mapping
Use
In this Customizing activity, you can specify the mapping between the priority with which an action or a
notification must be executed and the due date for this action or notification set by the system.
choose a priority and the due date will be determined based on your entries in this activity.
Note: When you define an action or a notification in the application, the system lets the best matching
configuration to determine the due date. If the current action category or business object is not defined in
this activity, the system does not determine any due date. You then have to enter the due date manually.
Furthermore, you can change the due date in the application either by specifying a different priority or
specifying a new due date.
Standard settings
Activities

BAdI: Definition of Process Steps
Use
this BAdI to define the persons that are involved in the process step of a given work process.
The process can contain the following people:
- Responsible Person
- Implementer
- Approver
In Environment, Health, and Safety, there are specific processes that involve action. In these
processes, workflow tasks are used to perform the work. You can use this BAdI to return the specific
workflow task and to integrate your business processes.
______________________________________________________________
SAP AG 146
______________________________________________________________
SAP System
Standard settings
In the standard system, the following BAdI implementations are activated:
- EHHSS_ACTION_BADI_IMPL (implementation for incident management) -
BADI_IMPL_EHHSS_RAS_ACTION (implementation for health and safety management)
The BAdI is filter-dependent and not designed for multiple use.
Chemicals
Specify Hazard Classifications According to GHS
Specify Signal Words
Use
In this Customizing activity, you have to specify signal words you can use to label chemicals according to
the Global Harmonized System (GHS).
You can select from the data specified here when you edit a chemical in the application.
Activities

Specify Hazard Classes/Categories and Assign Pictograms and Signal Words
Use
In this Customizing activity, you have to specify hazard classes and hazard categories. Furthermore, you
have to assign pictograms and signal words to enable the system to set a pictogram and a signal word
when you select a hazard class/hazard category in the application.
______________________________________________________________
SAP AG 147
______________________________________________________________
SAP System
Standard settings
To assign a hazard pictogram, enter the name of the corresponding graphic specified in the Customizing
activity Specify Graphics.
You can assign more than one graphic to a hazard class/hazard category by listing them, separated by
commas, in one field.
To assign a signal word, enter the key of the signal word you specified in the Customizing activity
Specify Signal Words.
Requirements
- If you want to use graphics other than the delivered ones, you have specified them in the
Customizing activity Specify Graphics.
- If you want to use signal words other than the delivered ones, you have specified them in the
Customizing activity Specify Signal Words.
Standard settings
Activities

Specify Hazard Statements and Assign Hazards
Use
In this Customizing activity, you can specify hazard statements you can use to classify and label
chemicals according to the Global Harmonized System (GHS).
Furthermore, you have to assign hazards you have specified in Customizing activity Configure Hazard
and Control Register.
When you add a chemical as agent in the risk identification process in the application, you can determine
the applicable hazards by using the hazard determination method based on hazard statements. This
determination method will read the assignment of hazards to hazard statements in this Customizing
activity to recommend applicable hazards.
Requirements
You have specified hazards in the Customizing activity Configure Hazard and Control Register.
______________________________________________________________
SAP AG 148
______________________________________________________________
SAP System
Standard settings
Activities

Assign Hazard Statements to Hazard Classes/Categories
Use
In this Customizing activity, you can assign hazard statements to hazard classes/categories. You can use
these settings to classify chemicals according to the Global Harmonized System (GHS).
When you select a hazard class/hazard category in the application, the hazard statements are set by the
system based on the hazard statements you assigned in this Customizing activity.
______________________________________________________________
SAP AG 149
_____________________________________________________________
_SAP System
Requirements
- You have specified hazard classes/categories in the Customizing activitySpecify Hazard

Classes/Categories and Assign Pictograms and Signal Words.
- You have specified hazard statements in the Customizing activity Specify Hazard Statements.
Specify Hazard Classifications According to 67/548/EEC or 1999/45/EC
Specify Categories of Danger and Assign Hazard Symbols
Use
In this Customizing activity, you can specify categories of danger. Furthermore, you have to assign a
hazard symbol to a category of danger. This enables the system to set a hazard symbol when you
select a category of danger in the application.
To assign a hazard symbol, enter the name of the corresponding graphic specified in the Customizing
You can assign more than one graphic to a category of danger by listing them, separated by commas,
in one field.
Requirements
If you want to use graphics other than the delivered ones, you have specified them in the Customizing
Standard settings
Activities

Specify Risk Phrases
_____________________________________________________________
_
SAP AG 150
_____________________________________________________________
_SAP System
Use
In this Customizing activity, you can specify risk phrases you can use to classify chemicals.
Standard settings
Activities

Specify First Aid Measures
Specify First Aid General Advice
Use
In this Customizing activity, you can specify general advices on first aid measures.

Standard settings
_____________________________________________________________
_
SAP AG 151
_____________________________________________________________
_SAP System
Activities
Specify First Aid Following Inhalation
Use
In this Customizing activity, you can specify first aid measures following inhalation.
Standard settings
Activities

Specify First Aid Following Skin Contact
Use
In this Customizing activity, you can specify first aid measures following skin contact.
Standard settings
_____________________________________________________________
_
SAP AG 152
______________________________________________________________
SAP System
Activities
Specify First Aid Following Eye Contact
Use
In this Customizing activity, you can specify first aid measures following eye contact.
Standard settings
Activities

Specify First Aid Following Ingestion
Use
In this Customizing activity, you can specify first aid measures following ingestion.

Standard settings
______________________________________________________________
SAP AG 153
______________________________________________________________
SAP System
Activities
Specify First Aid Note for Physicians
Use
In this Customizing activity, you can specify first aid notes for a physician.
Standard settings
Activities

Specify Firefighting Measures
Specify Suitable Extinguishing Media
Use
In this Customizing activity, you can specify suitable extinguishing media for firefighting.
Standard settings
______________________________________________________________
SAP AG 154
______________________________________________________________
SAP System
Activities
Specify Unsuitable Extinguishing Media
Use
In this Customizing activity, you can specify unsuitable extinguishing media for firefighting.
Standard settings
Activities

Specify Accidental Release Measure
Specify Personal Precautions
Use
In this Customizing activity, you can specify personal precautions measures.


Standard settings
______________________________________________________________
SAP AG 155
______________________________________________________________
SAP System
Activities
Specify Environmental Precautions
Use
In this Customizing activity, you can specify environmental precaution measures.

Standard settings
Activities

Specify Methods for Cleaning up
Use
In this Customizing activity, you can specify cleaning up measures.
Standard settings
______________________________________________________________
SAP AG 156
______________________________________________________________
SAP System
Activities
Specify Personal Protective Equipment
Specify Eye Protection
Use
In this Customizing activity, you can specify personal protective equipment for eye protection.
Standard settings
Activities

Specify Hand Protection
Use
In this Customizing activity, you can specify personal protective equipment for hand protection.

Standard settings
______________________________________________________________
SAP AG 157
______________________________________________________________
SAP System
Activities
Specify Body Protection
Use
In this Customizing activity, you can specify personal protective equipment for body protection.
Standard settings
Activities

Specify Respiratory Protection
Use
In this Customizing activity, you can specify personal protective equipment for respiratory protection.
Standard settings

______________________________________________________________
SAP AG 158
______________________________________________________________
SAP System
Activities
Specify Protective Measures
Use
In this Customizing activity, you can specify protective measures.

Standard settings
Activities

Specify Physical and Chemical Data
Specify Physical States
Use
In this Customizing activity, you can specify the different physical states of chemicals.

Specify Forms
Standard settings
______________________________________________________________
SAP AG 159
______________________________________________________________
SAP System
Activities
Use
In this Customizing activity, you can specify the different forms of chemicals.
During a risk assessment process, you use the form to identify and rate hazards and impacts of a
chemical.
Standard settings
Activities

Specify Colors
Use
In this Customizing activity, you can specify the colors of chemicals.

During a risk assessment process, you can use the color to identify a chemical.
______________________________________________________________
SAP AG 160
______________________________________________________________
SAP System
Standard settings
Activities

Specify Odors
Use
In this Customizing activity, you can define odors of chemicals. You can select from the odors specified
here when you edit chemical data in the application.
During a risk assessment process, you can use the odor to help identify a chemical. Specifying the odor of
hazardous chemicals is important, since a pungent odor can often act as a warning. Hydrogen cyanide
(HCN), for example, has a characteristic odor of bitter almonds.
Standard settings
Activities

Specify Water Solubility Remarks
Use
______________________________________________________________
SAP AG 161
______________________________________________________________
SAP System
In this Customizing activity, you can specify remarks on water solubility.

Standard settings
Activities

Specify Further Regulations
Specify German Water Hazard Classes
Use
In this Customizing activity, you can specify water hazard classes you can use to classify water
endangering chemicals.
Standard settings
Activities

Specify Storage Classes
Use
In this Customizing activity, you can specify storage classes you can use to classify chemicals.
______________________________________________________________
SAP AG 162
______________________________________________________________
SAP System
Standard settings
Activities

Dynamic Creation of Statements
Assign Assistant Classes to Business Objects
Use
In this Customizing activity, you can enable the dynamic creation of statements for a business object
(BO) by assigning an assistant class to the BO.
Requirements
For each business object for which you want to use the dynamic creation of statements, you have to create
an assistant class in transaction SE24 (Class Builder) and assign it to the BO in this Customizing activity.
Note: The assistant class has to implement the interface IF_EHFND_DSC_ASSIST (Dynamic Creation
of Statements: Interface for Assistant Class).
Standard settings
Activities

Example
You can use assistant class CL_EHFND_CHM_DSC_ASSIST (Assistant Class for Dynamic Creation of
Statements) for the chemical BO as an example for implementing you own class.
______________________________________________________________
SAP AG 163
______________________________________________________________
SAP System
Enable BO Fields for Dynamic Creation of Statements
Use
In this Customizing activity, you can specify business object fields (attributes) that are enabled for a
dynamic creation of statements.
You need to enter the business objects, the name for Customizing table in which the statements are stored,
and the alias of the OTR text. This text will be displayed on the manage statements screen.
Requirements
If you want to enable the dynamic creation of statements for fields other than the delivered ones, the
following activities are required:
- You have to assign an assistant class for the business object in Customizing activity Assign
Assistant Classes to Business Objects.
- For each persistent code field that you want to use for dynamic creation of statements, you have to
create a transient description field at the same node of the BO in transaction /BOBF/CUST_UI
(BOPF Enhancement Workbench). In transaction SE11 (ABAP Dictionary Maintenance), you also
need to create a corresponding data element using the naming convention *_DESC.
Note: To define the value of this transient field, you must create a determination at the node using
the naming convention: *_DSC_SET_TRANS_ATTR). For implementation of a determination,
you can use the generic class CL_EHFND_DSC_D_TRANS_ATTR. For the data element for the
transient field, you have to create a search help that uses
EHFND_SEARCH_CASE_INSENSITIVE as search help exit.
- You have to create a Customizing table in which you want to store the statements.
- You have to create an OTR text in transaction SOTR_EDIT (Editor for OTR Texts).
- Standard settings
Activities
To create new entries, proceed as follows:
1. Enter the business object for which you want to enable the dynamic creation of statements.
2. Select a corresponding node from the F4 value help.
3. Select a corresponding attribute from the F4 value help.
4. Enter the name of the transient description field.
5. Enter the name for Customizing table in which the statements are stored.
6. Assign an OTR-Alias
______________________________________________________________
SAP AG 164
______________________________________________________________
SAP System
Note: You have to check authorizations for authorization object EHFND_DSC (Dynamic Creation of
Statements) and attribute EHFND_DSCC.
0 Data Transfer from EHS Specification Database 0 Schedule Job for Data
Transfer of Chemicals
Use
In this Customizing activity, you can schedule a background job to transfer phrases, listed substances,
occupational exposure limits (OELs), and substance data from the specification database of SAP EHS
Management as part of SAP ERP or of Product Safety as part of SAP S/4HANA to Environment,
Health, and Safety as part of SAP S/4HANA.
Requirements
- You have entered substance data in the specification database.

- You have fulfilled the prerequisites as described in the documentation of the following reports
and BAdIs
- Transfer of Phrases (R_EHFND_PHRASE_TRANSFER);BAdI: Transfer of Phrases
- Transfer of OEL Data (R_EHFND_FILL_REGL_BY_EHS_SUBST); BAdI Transfer of OEL
Data
- Transfer of Chemicals (R_EHFND_FILL_CHM_BY_EHS_SUBST); BAdI: Transfer of
Chemicals
Activities
1. Use the Job Wizard to schedule the job. You define the job for the reports
R_EHFND_PHRASE_TRANSFER, R_EHFND_FILL_REGL_BY_EHS_SUBST, and
R_EHFND_FILL_CHM_BY_EHS_SUBST.
The job should execute these three reports as separate steps in the given sequence.
2. Schedule the job to run as a background job once a day. If the data in the specification database
rarely changes, you can schedule the background job to run less frequently.
______________________________________________________________
SAP AG 165
______________________________________________________________
SAP System
0 BAdI: Transfer of Phrases
Use
This Business Add-In (BAdI) is used in Environment, Health, and Safety component. You can use this
BAdI to specify phrase sets that were taken into account when transferring phrases from SAP EHS
Management as part of SAP ERP or from Product Safety as part of SAP S/4HANA to
Environment, Health, and Safety as part of SAP S/4HANA.
This BAdI is called when report Transfer of Phrases (R_EHFND_PHRASE_TRANSFER) is executed.
Standard settings
The BAdI definition is active in the standard system. It contains the following method:
- DETERMINE_PHRASE_SETS
The system returns a table with all phrase sets from SAP EHS Management as part of SAP ERP
or from Product Safety as part of SAP S/4HANA and the corresponding tables and fields of
In addition, you can select a checkbox if you want to concatenate a phrase code in the statement text.
If you select the checkbox, a phrase that contains, for example, the phrase code H330 and the phrase
text Fatal if inhaled, will be transferred as statement with the text H330: Fatal if
inhaled.
The BAdI implementation BADI_EHFND_PHRASE_TRANSFER is delivered with the standard

system. This BAdI implementation determines specified phrase sets for the phrase transfer. For
information about the delivered settings, see Mapping Table for Phrase Sets.
Activities
Add new implementations to BADI_EHFND_PHRASE_TRANSFER, when you implement this BAdI.
Example
You can find example implementations in the BAdI Builder in class

CL_BADI_EHFND_PHRASE_TRANSFER.
BAdI: Transfer of OEL Data
______________________________________________________________
SAP AG 166
______________________________________________________________
SAP System
Use
BAdI to specify data sources for transferring substance data from SAP EHS Management as part of
SAP ERP or from Product Safety as part of SAP S/4HANA to Environment, Health, and Safety as
part of SAP S/4HANA.
This BAdI is called when report Transfer of OEL Data
(R_EHFND_FILL_REGL_BY_EHS_SUBST) is executed.
The BAdI methods GET_EHS_CLASSES and GET_EHS_SUBST_IDENT_LISTING are also called
when the report Transfer of Chemicals (R_EHFND_FILL_CHM_BY_EHS_SUBST) is executed.
Requirements
- You have ensured that the Customizing entries and phrases of the specification database also exist in
the Environment, Health, and Safety system.
For more information, see prerequisites in the documentation of report report Transfer of OEL
Data.
Standard settings
The BAdI definition is active in the standard system. It contains the following methods:
- GET_HITLIST_ID:
This method determines the Set of Hits - Group and the Set of Hits - Group Entry that is used
for transferring substance data. Note that only substances from the selected hit list are transferred.
- GET_EHS_CLASSES:
This method specifies the sources for the OELs, the regulatory list, the value type and the class
itself. Note that you have to use the parameter of the interface
IF_EHFND_REGL_FILL.
- GET_EHS_SUBST_IDENT_LISTING:
This method determines the identification listing for transferring data like the CAS number or
substance name. Note that the CAS number and the substance name have to be included in the
identification listing.
- MAP_VALUE_TYPE:
This method specifies the mapping between the value type in the SAP EHS Management as part
of SAP ERP application or the Product Safety as part of SAP S/4HANA application and in the
Environment, Health, and Safety application.
- MAP_REGLIST_ID:
This method specifies the mapping between the Regulatory List ID in the SAP EHS
Management as part of SAP ERP application or the Product Safety as part of SAP S/4HANA
application and in the Environment, Health, and Safety application.
The BAdI implementation BADI_EHFND_REG_LIST_TRANSFER is delivered with the standard

system. It determines data for transferring as follows:
______________________________________________________________
SAP AG 167
______________________________________________________________
SAP System
- It uses the method GET_HITLIST_ID to set the Set of Hits - Group as HITLIST and the Set
of Hits - Group Entry as LISU.
- The method GET_EHS_CLASSES determines the class as data sources. For more information about
the standard delivery, see the list of Classes and Characteristics used as data sources for OEL data
transfer.
- The method GET_EHS_SUBST_IDENT_LISTING used the identification listing D_DEFAULT
for transferring data for listed substances.
Note: The CAS number and the substance name have to be included the identification listing
D_DEFAULT. Otherwise, the data cannot be transferred.
- The method MAP_VALUE_TYPE determines the value types in the SAP EHS Management as
part of SAP ERP application or the Product Safety as part of SAP S/4HANA application.
Note: In the standard implementation, the determined value type must be the same as in the
Environment, Health, and Safety application. Otherwise, the data cannot be transferred.
- The method MAP_REGLIST_ID maps the regulatory list ID in the SAP EHS Management as
part of SAP ERP application or the Product Safety as part of SAP S/4HANA application to an
ID in the Environment, Health, and Safety application.
Note: In the standard implementation, the IDs in the SAP EHS Management as part of SAP ERP
application or the Product Safety as part of SAP S/4HANA application must be the same as in
the Environment, Health, and Safety application. Otherwise, the data cannot be transferred.
Activities
When you implement this BAdI, add new implementations to the business add-in
BADI_EHFND_REGL_FILL.
We recommend you derive from CL_EHFND_REG_LIST_TRANSFER and overwrite the methods

according to your needs.
Example

CL_EHFND_REG_LIST_TRANSFER.
BAdI: Transfer of Chemicals
______________________________________________________________
SAP AG 168
______________________________________________________________
SAP System
Use
this BAdI to specify sources of data and data conversions for transferring substance data from the
specification database of SAP EHS Management as part of SAP ERP or of Product Safety as part of
SAP S/4HANA to Environment, Health, and Safety as part of SAP S/4HANA.
This BAdI is called when report Transfer of Chemicals (R_EHFND_FILL_CHM_BY_EHS_SUBST) is
executed.
Requirements
For more information, see prerequisites in the documentation of report Transfer of Phrases
(R_EHFND_PHRASE_TRANSFER) and report Transfer of OEL Data
(R_EHFND_FILL_REGL_BY_EHS_SUBST).
BAdI Methods
- GET_CHARACTERISTICS:
This method returns the properties and characteristics of the substances that are transferred. For each
characteristic, the method also returns a usage that is used to read data for that characteristic. Thus,
it is possible to read, for instance, the components with workplace control parameters with a
different validity area than other transferred data. For each characteristic, the method also returns
the node and the field of the chemical to which the data are transferred. Note that the only nodes
supported are those that are provided by the default implementation.
- GET_SDS_DOCUMENT_PARAMETERS:
This method returns the parameters used to identify documents to transfer. It returns a list of triples
where each triple contains values for report category, validity area, and language. report Transfer of
Chemicals uses report category and validity area to determine generation variants. For each
determined generation variant and language, released and historic reports are transferred to the
chemical.
- GET_HITLIST_ID:
for transferring substance data. Note that only substances of the selected hit list are transferred.
- GET_IDENT_LISTING_CHM:
This method determines the identification listing for transferring data like the name of the chemical
or the CAS number. Each position in the identification listing is transferred to corresponding field
of the chemical BO. The field assignment of the listing positions must be as follows: 1. Name of the
chemical
2. Internal names
3. IUPAC name
______________________________________________________________
SAP AG 169
______________________________________________________________
SAP System
4. EINECS number
5. Molecular formula
6. CAS number
7. Synonyms
This means that the identifier configured at position 1 of the identification listing is being
transferred into the name of the chemical field in the chemical BO, the identifier configured at
position 2 is being transferred into the internal name, and so on.
- MAP_TO_CHEMICAL_TYPE:
This method maps phrase IDs of the specification database to the chemical type (fix values of
domain EHFND_CHM_NATURE) of chemical BOs.
- MAP_TO_HAZARD_CLASSIFICATION:
Chemicals have only one field for hazard class/hazard category. In the specification database, this
information is spread over multiple fields. This method maps the phrase IDs from up to 4
characteristics to one value for the hazard class/hazard category.
- MAP_TO_ACCURACY:
This method maps phrase IDs of accuracy characteristics, as well as accuracy operators of
compositions and numerical characteristics to values for the numerical accuracy fields in the
chemical.
- MAP_TO_COUNTRY:
Documents that are attached to chemicals have a country code and no validity area. This method
maps the validity area of a generation variant to a country code.
- ADJUST_NAMES_OF_CHEMICAL:
This method allows you to adjust the identifiers that are supposed to be transferred as name of the
chemical. Chemical names are language dependent and require a language code. In SAP EHS
Management as part of SAP ERP and Product Safety as part of SAP S/4HANA, it is possible to
enter identifiers without any language code. In this method, you can, for example, assign a default
language for those identifiers that do not have a language code or replicate it with different
languages codes.
- GENERATE_DOCUMENT_REFERENCE:
In the specification database, generated reports are usually report bodies; they are not completely
finished. It is still necessary to generate a final report. When reports are transferred from a
specification to a chemical, this generation step is also necessary. This method generates the final
report when a user wants to display a report body that has been attached to a chemical via the
transfer report for chemicals. This method also specifies the file format in which the final report is
generated.
The BAdI implementation BADI_EHFND_CHM_TRANSFER is delivered with the standard system.
Example
______________________________________________________________
SAP AG 170
______________________________________________________________
SAP System
You can find example implementations in the BAdI Builder on the Enhancement Spot Element
Definitions tab in the Implementation Example Classes section.
Agents
Specify Amount Categories by Hazards
Use
In this Customizing activity, you can specify amount categories. You can also specify the dimension of
each amount category and the default dimension (only relevant if you transfer data from the EHS
specification database).
When analyzing exposure to an agent in the application, you can only compare amounts and OELs that
have the same amount category.
In addition, you can assign amount categories to specific hazards. When you edit occupational exposure
limits for physical agents in the application, you can only select amount categories that are assigned to the
hazard of the physical agent. If a hazard can involve physical agents that have multiple amount
categories, you can also specify the default amount category for agents assigned to that hazard.
Requirements
- You have defined the dimensions and measurement units in the Customizing activity Check Units
of Measurement.
- You have defined hazards in the Customizing activity Configure Hazard and Control Register.
Standard settings
Activities

______________________________________________________________
SAP AG 171
______________________________________________________________
SAP System
Specify Value Types
Use
In this Customizing activity, you can define the types of values for agents. Value types are assigned to the
values of occupational exposure limits (OEL) and amounts.
When analyzing exposure to an agent, you can only compare amounts and OELs that have the same value
type.
Standard settings
Activities

Specify Regulatory Lists for OELs
Use
In this Customizing activity, you specify the regulatory lists or customer-specific lists that contain
substances and their occupational exposure limits (OELs).
In the health and safety management application, you use regulatory lists to store the occupational
exposure limits (OELs) for listed substances. When you create chemicals, you reference listed substances
as hazardous ingredients. In this way, you define OELs for chemicals.
Note: When you revise OELs or use OELs in exposure analysis in the application, you can use only these
lists specified here.
Requirements
You have created the appropriate regulatory lists in the Customizing activityCreate Regulatory Lists and
Customer Lists.
Standard settings
______________________________________________________________
SAP AG 172
______________________________________________________________
SAP System
Activities

Jobs
Specify Job Types
Use
In this Customizing activity, you can specify job types. You use job types when you create jobs for job
hazard analyses.
Standard settings
Activities

Similar Exposure Groups (SEGs)
Specify Roles for Similar Exposure Groups
Use
In this Customizing activity, you can define the role that can be assigned to people who are involved in
maintaining a similar exposure group (SEG).
______________________________________________________________
SAP AG 173
______________________________________________________________
SAP System
Standard settings
Activities

BAdI: Determination of Risks for Similar Exposure Group
Use
This Business Add-In (BAdI) is used in the Environment, Health, and Safety component.
You can use this BAdI to determine the risks that are relevant for a similar exposure group (SEG). In turn,
the risks enable you to set up SEGs that use jobs, locations, and agents that belong together. Otherwise,
you could mistakenly create an SEG for a job and reference agents that are not actually involved in that
job. Later, this leads to incorrect exposure profiles for your workers. The BAdI ensures that SEGs are
accurate and based on real risk data.
For example, if you create an SEG for a specific job, the BAdI finds the risks that have already been
identified for this job. These risks are relevant to the SEG and you can use only their corresponding
agents in the SEG.
The system calls the BAdI to determine risks in the following two situations:
- When you create an SEG, you create it based on jobs, jobs at selected locations, or locations. The
system calls the BAdI to determine the risks that correspond to the jobs/locations and displays the
agents that are involved in the jobs or exist at the locations.
- When you edit an SEG later, you can add jobs, locations, and agents to the SEG. The system calls
this BAdI to determine the risks that correspond to the locations, jobs, and agents that are currently
assigned to the SEG.
In addition, you can use this BAdI to determine the risk assessment types of theses risk assessments that
contains the determined SEG-relevant risks. The risk assessment types are used for authority checks.
The system calls the BAdI for the authority check when you want to create, edit, or display an SEG. If
you have authorization for at least one risk assessment type, the screen for creating, editing, or displaying
SEGs opens. However, only SEGs containing risks with a risk assessment type for which you have
authorizations are displayed.
Standard settings
- GET_RISKS
The system returns a table with all risks relevant for the SEG.
______________________________________________________________
SAP AG 174
______________________________________________________________
SAP System
- GET_RAS_TYPES
The system returns a table with all risk assessment types relevant for the SEG.
The BAdI implementation BADI_EHHSS_SEG_GET_RISKS is delivered with the standard system.
Hazard and Control Register
Specify Control Inspection Questions
Use
In this Customizing activity, you can specify questions that inspectors must answer when conducting a
control inspection. You can assign these questions to specific controls when you edit control master data
in the application.
If you specify questions directly in the control master data in the application, those questions also appear
in this Customizing table.
Note: The system determines the level of control effectiveness based on the number of yes answers.
Therefore, you must form each question in a way where a yes answer is a positive result.
For example, a yes answer to the question Is the fire extinguisher fully charged? is a positive result;
whereas, a yes answer to the question Is the fire extinguisher empty? is a negative result.
Standard settings
The standard system is delivered without examples.
Activities
Define questions that can be assigned to controls for use in control inspections.
Configure Hazard and Control Register
Use
In this Customizing activity, you can configure the hazard and control register to use in a risk assessment.
The register provides an inventory of hazards, their impacts, and controls. You can configure it, so that
you see only the hazards, impacts, and controls that are relevant to your risk assessment type. In
Environment, Health, and Safety, you use this information in the identification, analysis, and treatment
of risk:
______________________________________________________________
SAP AG 175
______________________________________________________________
SAP System
- Hazards are used during risk identification to specify the source of risk.
- Impacts are used during risk identification to specify how a risk can affect the health and safety of
people or the environment.
- Controls are used primarily in risk treatment and play a role in risk analysis when you analyze the
initial risk and residual risk associated with the hazard.
Note: During risk assessment, you can only assign hazards, impacts, and controls to risks based on the
relationships specified in this Customizing activity.
Requirements
If you want to identify risks that involve hazards and agents, ensure that you have enabled agents for the
relevant risk assessment types in Customizing activity Specify Risk Assessment Types.
Standard settings
Activities
1. Specify the control types, subtypes, and catalogs that classify controls. You use the type, subtype,
and catalog in the application when you create controls as master data. For control types, you can
also specify the levels in the hierarchy of controls by entering a value under Level in the Control
Type table.
Note: Changes to type and subtype entries in this activity are automatically made in the
Customizing activities Specify Types and Specify Subtypes under Foundation for EHS.
2. Specify the impact types and impacts.

Impact types are used to group impacts according to their type of harm, for example, environmental,
health, or safety harm. Impact types are assigned to risk assessment types, and this relationship
controls which hazards and impacts you can choose from in a risk assessment.
3. Specify the hazard categories and hazards.

Hazard categories are used to group hazards.
Also, for each hazard category, you can enter whether or not it involves agents. When you create a
chemical in the application, for example, you can only assign hazards that belong to a hazard
category that is specified here as involving chemical agents.
4. Assign impacts and control catalogs to the hazards.

Establishing the relationship between a hazard and its potential impacts and controls enables you to
select and use these impacts and controls for the corresponding hazard during a risk assessment
process.
Also, the assignment of an impact to a hazard in Customizing determines whether the application
displays the hazard for selection in the application. For example, if you create a health risk
assessment, the application displays only those hazard categories and hazards that have at least one
impact assigned that belongs to an impact type assigned to the risk assessment type Health.
______________________________________________________________
SAP AG 176
______________________________________________________________
SAP System
5. If Plant Maintenance (PM) integration is enabled, you can specify risk symbols for hazards and
control catalogs.
Further notes
You must also assign impact types to risk assessment types in the Customizing activity Assign Impact
Types to Risk Assessment Types.
Assign Impact Types to Risk Assessment Types
Use
In this Customizing activity, you can assign impact types to risk assessment types.
Since a hazard can have multiple types of impacts, this assignment enables you to concentrate on a
specific type of impact when you perform a risk assessment.
Requirements
- You have specified impact types in the Customizing activity Configure Hazard and Control
Register.
- You have specified risk assessment types in the Customizing activity Specify Risk Assessment
Types.
Standard settings
Activities

Example
You want to perform a job hazard analysis (JHA) and concentrate only on the health impacts of a hazard.
By assigning the impact type Health to the risk assessment type JHA, the system displays only the health
impacts for the hazard.
______________________________________________________________
SAP AG 177
______________________________________________________________
SAP System
Assign Form Group to Safety Instructions
Use
In this Customizing activity, you have to specify the form group that is relevant for safety instructions.
A safety instruction document summarizes all health and safety relevant information for a chemical,
as well as the required protective equipment for safe handling at a location. This document can be
used to train employees and inform them about safe handling of the chemical.
In the application you can create safety instruction documents as controls for chemicals as part of the risk
treatment process. In the control master data, you have to link an adobe document service template. When
you select the form group specified in this Customizing activity, extra functions are offered to create or
display a safety instruction document for a risk.
Requirements
You have specified form groups in Customizing activity Specify Form Groups and Assign Forms.
Standard settings
Activities

Assign Form Groups to Risk Assessment Types
Use
In this Customizing activity, you can specify form groups for risk assessment types.
During a risk assessment process, you can create reports for a risk assessment on the
Documents tab. You can create reports using only the forms that belong to the form group
assigned to the risk assessment type, for example, only forms of the group relevant to health risk
assessments.
Requirements
- In Customizing activity Specify Forms under Foundation for EHS, you have defined the available
forms.
______________________________________________________________
SAP AG 178
______________________________________________________________
SAP System
- In Customizing activity Specify Form Groups, under Foundation for EHS, you have specified form
groups and assigned forms to form groups.
Standard settings
Activities

2. If necessary, assign forms groups for each risk assessment type.
Chemical Approval
Specify Role of Person to Receive Chemical Approval Requests
Use
In this Customizing activity, you can specify which role receives a newly created chemical approval
request.
Standard settings
Activities
Specify which role receives the task directly after a chemical approval request has been submitted.
Note: This activity starts a report. After you have entered the role, you have to execute the report by
choosing the Execute button. The report saves your entry. By choosing the Save button, you can save a
report execution variant.
Example
A chemical approval request has been submitted for a certain location. The person that is assigned to this
location as a person responsible with the role that is specified in this Customizing activity, receives a task
to open the approval dialog and to carry out the required steps to approve the chemical. If there is no one
with the specified role assigned at the location, someone with this role at a location higher up in the
hierarchy is selected.
______________________________________________________________
SAP AG 179
______________________________________________________________
SAP System
Specify Approval Steps and Checklists
Use
In this Customizing activity, you can specify data necessary to enable a chemical approval process.
You can specify approval steps that the assessor has to perform during the chemical approval and
combine them into checklists.
If you want to give more information about an approval step, you can assign a quick help text to each
single step.
In the application, the chemical approval screen consists of a static part that is provided with the standard
system and dynamic parts that you can assign to the steps in this Customizing activity. These dynamic UI
elements contain all information needed to confirm a specific step this element is assigned to.
If specific checks should be performed when completing an approval step, you can implement the
checking logic in a class and assign the class to the step.
During the approval process, an approval team consisting of multiple approvers with different expertise,
who have to perform different steps during the approval process, can be involved. Therefore, you can
assign the checklists to roles.
To specify what steps a specific assessor has to perform to approve a chemical request, you can assign a
checklist also to an approval scenario.
If you want to give more information about the aim of the different approval scenarios, you can assign a
quick help text to each scenario.
To specify which additional approvers have to be part of the approval team, you can select roles and
assign them to an approval scenario.
When you perform a chemical approval in the application, the system proposes an approval team based
on the settings you enter in this Customizing activity.
Requirements
- If you want to assign quick help texts other than the texts provided in the standard system, you have
to create a general text (object type TX) in transaction SE61 (Document Maintenance), and enter the
ID of the new general text in this Customizing activity.
- If you want to assign dynamic UI elements other than the elements provided in this Customizing
activity, you have to create new tabs in the Component Configuration for component
EHFND_UI_CHA_OVP_DYNAMIC_TAB, using transaction SE80 (Object Navigator) and enter
the ID of the new tab in this Customizing activity.
Standard settings
Activities
1. Select an initial approver.
______________________________________________________________
SAP AG 180
______________________________________________________________
SAP System
2. Specify all needed approval steps.

- You can assign quick help texts to each step to provide further information.
- You can assign dynamic UI elements you want to use for the chemical approval screen.
- You can assign a class containing specific checks performed when completing an approval
step.
3. Specify checklists and assign the needed approval steps to the checklist.
Note: The approval step for requesting SDS data entry only works correctly in checklists for an
approval of a new chemical.
4. Select a role and an approval scenario and assign the created checklist and a quick help text.
5. Specify an assessment team by assigning a role to an approval scenario.
Specify Lists for Restricted Substances Check
Use
In this Customizing activity, you can specify regulatory lists or customer-specific lists. In the application,
you can use these lists to create regulatory list revisions for restricted substances.
In addition, the specified lists are take into account for a restricted substance check in the chemical
approval process.
All lists that you specify in this Customizing activity will be displayed in the application in the approval
steps Check for Restricted Substances. In this step, you can check whether a hazardous ingredient is
listed on any of these lists or not. A red icon indicates if a list contains any listed substances that are
entered as hazardous ingredients for the chemical.
Requirements
You can enter regulatory lists that have been specified in the Customizing activity Specify Regulatory
Lists and Customer Lists in the product compliance application.
Specify Purposes
______________________________________________________________
SAP AG 181
______________________________________________________________
SAP System
Use
In this Customizing activity, you can specify purposes.

You can select from the data specified here when you request a chemical approval in the application.
Standard settings
Activities

Specify Methods of Use
Use
In this Customizing activity, you can specify methods of use.

You can select from the data specified here when you request a chemical approval in the application.
Standard settings
Activities

Risk Identification
Specify Role Responsible for Initial Chemical Risk Identification
Use
In this Customizing activity, you can specify which role performs the risk identification process.
______________________________________________________________
SAP AG 182
______________________________________________________________
SAP System
Standard settings
Activities
Specify which role receives the workitem to perform the risk identification process.
Example
After a chemical has been approved for use at a specific location, someone must check whether there are
risks associated with this chemical that have not yet been identified. The person at this approved location,
who has been assigned the role specified in this Customizing activity, receives a workitem to identify
risks for this location. If there is no-one with the specified role at the location, someone with this role at a
location higher up in the hierarchy is selected.
BAdI: Hazard Determination Methods for Chemicals
Use
This Business Add-In (BAdI) is used in the Environment, Health, and Safety component. You can
use this BAdI to determine hazards for chemicals when identifying risks. This BAdI is called when
you add a chemical as agent in the risk identification process and apply a hazard determination
method.
Requirements
You have assigned hazards to hazard statements in in Customizing activity Specify Hazard Statements
and Assign Hazards.
Standard settings
- GET_TAB_ID
The system returns the tab ID for possible parameters for the hazard determination method.
- DTERMINATE_HAZARDS
The system determines hazards for chemicals based on hazard statements.
The BAdI implementation BADI_EHHSS_RAS_HDM_BAS_ON_CHM is delivered with the standard

system. This BAdI implementation determines hazards for chemicals based on hazard statements.
______________________________________________________________
SAP AG 183
______________________________________________________________
SAP System
Activities
When defining customer-specific BAdI implementations, you can enhance the following filter values for
the hazard determination method:
- 01 = Manual
- 02 = Based on Hazard Statements
When you implement this BAdI, execute the following steps:
- Enhance the filter value range EHHSS_HAZ_DETERM_METHOD.

- Add new implementations to BADI_EHHSS_HAZ_DET_METHOD.
- Set the filter value for the new implementation.
- Enhance the value range of domain EHHSS_HAZ_DETERM_METHOD.
- Add a new tab to component configuration EHHSS_RAS_IDENTIF_CHM_DLG_DY_TAB with
the same Tab ID as the one you entered in method GET_TAB_ID.
- Insert FPM-UIBB that represents the parameters of the hazard determination method.
- To set the parameters of the hazard determination method, set the fields in the application controller:
CL_EHHSS_RAS_IDENTIF_CTRL-MS_CHEMICAL-HAZ_PARAMETER
CL_EHHSS_RAS_CHA_IDENTIF_CTRL- MR_PARAMETERS
- To apply the hazard determination method, raise an FPM Event with the ID
'HDM_APPLY'
Example
- CL_BADI_EHHSS_HDM_BAS_ON_CHM
______________________________________________________________
SAP AG 184
______________________________________________________________
SAP System
Risk Analysis
Specify Assessment Steps and Analysis Methods
Use
In this Customizing activity, you specify the steps that can be used for assessing identified risks. You use
these assessment steps to define the process that guides you through the activities involved in analyzing,
evaluating, and treating risks. You can include different assessment steps for each risk assessment type.
In this activity, you can also specify the analysis methods that you want to use for analyzing a specific
risk type, for example, a risk matrix to analyze residual risk.
Note: The assessment steps and analysis methods defined in this Customizing activity are required for
most risk assessment activities. This Customizing activity is therefore critical to configuring the system to
suit your risk assessment process.
Standard settings
Activities
1. Check the existing assessment steps and adapt them, if required:

- You can specify the order in which the assessment steps must be performed by changing the
step number.
- You can specify a risk type for each assessment step that you want to use for the analysis of
identified risks.
Each assessment step must be assigned to a variant that determines the layout and contents of the
step on the user interface.
2. Check the existing analysis methods and adapt them, if required:

- You can assign templates (Microsoft Word or Microsoft Excel) to document-based analysis
methods. This can be useful, for example, if you want to analyze risks based on a company-
specific assessment template. To upload a template for an existing analysis method, double-
click the relevant entry and specify the template in the File Name field.
Each analysis method must be assigned to a tab that you can include in different analysis steps. You
use analysis methods to specify which tabs are displayed on the user interface depending on risk
assessment type and hazard category.
Note: Analysis methods are required only for assessment steps that have a risk type assigned.
3. Assign assessment steps and analysis methods to risk assessment types:

- You select the risk assessment types that have been specified in the Customizing activity
Specify Risk Assessment Types.
______________________________________________________________
SAP AG 185
______________________________________________________________
SAP System
- For each risk assessment type, you specify the assessment steps that you want to use. These
can include analysis steps as well as steps that you want to use for the evaluation and treatment
of risks. If you want to use a completion status icon for an assessment step, select the
checkbox to enable the icon.
- For each analysis step, you specify the analysis methods that you want to use. You can select
from the analysis methods that are included in the analysis step variant. Note: A risk type must
be assigned to each assessment step that involves one or more analysis methods. If you assign
analysis methods to an assessment step that has no risk type assigned, the system ignores this
assignment. Instead, in the application, the system displays the completevariant that is assigned
to the assessment step.
- You can further restrict the use of each analysis method by assigning it to a hazard category.
The analysis method is then only displayed for the analysis of risks that involve the same
hazard category. If you do not assign an analysis method to a specific hazard category, it is
displayed for the analysis of all risks.
Note: You should assign the analysis method EXP_ASSMNT_QUANT (Quantitative Exposure
Assessment) only to hazard categories that are configured to involve agents in the Customizing
activity Configure Hazard and Control Register.
See also
The adjustment of Customizing entries is not supported for analysis methods, because these can include a
file upload. If you need to set up Customizing in a different system or client, we recommend that you
compare your Customizing entries, then edit the entries manually, and upload the required files again.
Workplace Sampling
Specify Role Responsible for Sampling
Use
In this Customizing activity, you can specify which role is responsible for sampling.
In the application, you can select a person responsible for sampling if the person is assigned to the role
you specified in this Customizing activity.
Requirements
You have specified the role in Customizing activity Specify Role of Person Responsible.
Standard settings
______________________________________________________________
SAP AG 186
______________________________________________________________
SAP System
Specify Sampling Method Types
Use
In this Customizing activity, you can specify types of sampling methods by selecting attributes that are
important during the sampling process.
You can select a sampling method type that you have specified here when you edit a sampling method in
the application.
When you select a sampling method type in the application, only the fields that you specified in this
Customizing activity are displayed.
Standard settings
Activities

Example
If you want to sample chemicals, such as formaldehyde, carbon monoxide or diesel fuel, you need a
special detector tube attached to a sampling head and a pump with an appropriate flow rate. In order to
have all required fields available in the application when editing a sampling method, you have to select
the following check boxes:
- Equipment
- Medium
- Head
- Flow Rate
- Analytes
If you want to measure noise, you only need a dosimeter. In order to have all required fields available in
the application when editing a sampling method, you only have to select the Equipment check box.
Assign Sampling Method Types to Hazards
Use
______________________________________________________________
SAP AG 187
______________________________________________________________
SAP System
In this Customizing activity, you can assign a sampling method type to a physical hazard.
In the application, you can select only sampling methods for a physical agent that have a sampling
method type which is assigned to the agents' hazard.
Requirements
You have specified hazards for the hazard category that involves physical agents in Customizing activity
Configure Hazard and Control Register.
You have specified a type of sampling method suitable for measuring physical hazards in Customizing
activity Specify Sampling Method Types.
In the application, you have created a physical agent with the same hazard that you have assigned to the
sampling method type.
Standard settings
Example
You want to sample noise.

In the application, you create a physical agent (AGENT_NOISE) with the hazard Noise Exposure.
In the Customizing, you create a sampling method type suitable for measuring noise
(EXAMPLE_SPM_NOISE) and assign this type to the hazard Noise Exposure. In the application, you
select the physical agent for noise (AGENT_NOISE) as the sampling target when you are planning a
sampling campaign. For the sampling method, you can select all sampling methods with the sampling
type EXAMPLE_SPM_NOISE.
Specify Shift Patterns for OEL Adjustment
Use
In this Customizing activity, you can specify shift pattern.

Shift patterns are used to adjust OEL values, if workplace samples were taken with a different shift
pattern than the shift pattern that is used by the OEL value.
Entries in this Customizing activity are used to adjust OEL values using the Business Add-In BAdI: OEL
Adjustment to Shift Pattern (BADI_EHFND_OEL_SHIFT_ADJ).
______________________________________________________________
SAP AG 188
______________________________________________________________
SAP System
Standard settings
Activities

Specify Methods for OEL Adjustment to Shift Pattern
Use
In this Customizing activity, you can specify methods to adjust OEL values to shift pattern. In addition,
you have to assign an applicable value type.
If workplace samples were taken with a different shift pattern than the shift pattern that is used by the
OEL value, the OEL values have to be adjusted mathematically to be able to compare the analytical
results of the sampling with the OEL.
Entries in this Customizing activity are used to adjust OEL values using the Business Add-In BAdI: OEL
Adjustment to Shift Pattern (BADI_EHFND_OEL_SHIFT_ADJ).
Standard settings
Activities

______________________________________________________________
SAP AG 189
______________________________________________________________
SAP System
Specify Lab Template
Use
In this Customizing activity, you can specify a spreadsheet template (file format XLSX) that contains
information about samples. The sample information is needed by a laboratory to analyze these samples.
When you prepare the shipping of the samples in the application, you can generate a lab template based
on the spreadsheet template that you have specified in this Customizing activity.
In your sampling process, you can send the lab template to the laboratory together with the samples. The
laboratory will fill out the template and send the analytical results back to you to record them in the
system.
Requirements
The lab template is loaded into the MIME repository in transaction Object Navigator (SE80).
Standard settings
Activities
You can download the template that is delivered as an example, adapt it to your needs, and upload the
changed template in the MIME repository.
Note: The template that is delivered with the standard system as an example contains the worksheets
Lab Template and CONFIGURATION. In the Lab Template worksheet, the sample data is loaded.
The CONFIGURATION worksheet is used to map sample data columns of the Lab Template
worksheet to configuration parameters in the system.
In both worksheets, you can change fonts or coloring of the cells or add comments. However, you must
not add, rearrange, or delete any columns. You can, however, add additional worksheets to provide, for
example, company or contact information.
BAdI: Calculation of Sampling Campaign Performance
Use
this BAdI to determine specific performance aspects of a sampling campaign, such as a percentage value
or a specific color to indicate the performance levels.
This BAdI is called when a performance value or a color indicating the sampling campaign performance
is displayed on the screen.
Standard settings
______________________________________________________________
SAP AG 190
______________________________________________________________
SAP System
- CALC_CAMPAGIN_PERF_INDEX
This method calculates a percentage value representing the performance of a sampling campaign.
For details refer to the method documentation Calculate Percentage Value for Campaign
Performance.
- CALC_CAMPAIGN_PERF_INDEX_COLOR
This method determines the color to be displayed for a certain performance of a sampling campaign.
For details refer to the method documentation Return Color for Campaign Performance.
BAdI implementations
The BAdI implementation BADI_EHHSS_CAMP_PER_CAL_IMPL is delivered active with the

standard system.
This BAdI implementation enables you to determine specific performance aspects of a sampling
campaign.
Activities
- Create a new implementation

- Optional: Copy the methods of the default implementation as a basis for your own implementation.
- Adjust your own implementation.
- Activate the methods and the BAdI implementation.
Example
BAdI: OEL Adjustment to Shift Pattern
Use
use this BAdI to define adjustment methods for the adjustment of occupational exposure limits (OELs)
to shift pattern.
This BAdI is called whenever the exposure of a certain worker is to be compared to an OEL in order to
make the OEL actually comparable to the exposure.
______________________________________________________________
SAP AG 191
______________________________________________________________
SAP System
Standard settings
- CALC_ADJ_OEL
For details refer to the method documentation Calculate Adjusted OEL Values for a Selected Shift
Pattern.
The following BAdI implementations are delivered active with the standard system:
- BADI_EHFND_SHFTADJ_DLYADJ
Adjustment of an OEL based on the daily working hours.
- BADI_EHFND_SHFTADJ_WKLYADJ
Adjustment of an OEL based on the weekly working hours.
- BADI_EHFND_SHFTADJ_CONSADJ
Conservative or worst case adjustment: The lowest OEL value from daily and weekly adjustment is
taken into account.
- BADI_EHFND_SHFTADJ_NOADJUST
No adjustment of an OEL needed/wanted.
The BAdI uses filter values that are specified in Customizing activity Specify Methods for OEL
Adjustment to Shift Pattern.
Activities

Example
______________________________________________________________
SAP AG 192
______________________________________________________________
SAP System
Exposure Analysis
Specify Exposure Ratings for Chemicals and Airborne Agents
Use
In this Customizing activity, you can specify exposure ratings for chemicals and airborne agents and
assign thresholds to the exposure ratings. You can also specify the exposure rating description that
appears in the risk assessment.
Requirements
You have specified hazards that involve chemicals and airborne agents in the Customizing activity
Configure Hazard and Control Register.
Standard settings
Activities

Specify Exposure Ratings for Physical Agents
Use
In this Customizing activity, you can specify exposure ratings for physical agents and assign the exposure
ratings to specific hazards.
You can also specify the exposure rating message that appears in the risk assessment when the result of
the exposure analysis is below or above the action value of an occupational exposure limit (OEL) or when
the result exceeds the OEL. Specifying exposure ratings by hazard, allows you to adapt the messages to
each hazard.
Requirements
You have specified hazards that involve physical agents in the Customizing activity Configure Hazard
and Control Register.
Standard settings
______________________________________________________________
SAP AG 193
______________________________________________________________
SAP System
Activities

Specify Confidence Levels for Exposure Assessments
Use
In this Customizing activity, you can specify confidence levels.

In the application, you can select the confidence levels you have entered in this Customizing
activity.
Standard settings
Activities

Specify Templates for Statistical Analysis
Use
In this Customizing activity, you can specify spreadsheet templates that contain statistical analysis
methods for analyzing workplace sampling data.
In the application, the results of the statistical calculations help you to assess risks related to the exposure
of employees to agents at a specific location and for a specific job.
Requirements
______________________________________________________________
SAP AG 194
______________________________________________________________
SAP System
The lab template is loaded into the MIME repository in transaction Object Navigator (SE80).
Standard settings
Activities
You can download the example template, adapt it to your needs, and upload the changed template in the
MIME repository.
Note: The template that is delivered with the standard system is an example. However, it contains the
following worksheets that you must not change:
- Sample Data: In this worksheet, the system loads data for location, job, and exposure.
- Sample Data (Raw): In this worksheet, the system loads the data that should be analyzed.
- Statistical Results: In this worksheet, the system writes the results of the statistical calculation.
In these worksheets, you can change fonts or the coloring of the cells, add comments, or
delete the text boxes. However, you must not add, rearrange, or delete any columns.
In addition to the worksheets that are used by the system to load or write data, the template contains the
Sample Statistics worksheet. This worksheet contains an example of a statistical calculation. You can
change this worksheet or you can add additional worksheets that use data from the Sample Data (Raw)
worksheet to calculate your own statistics or display your own graphics.
Risk Matrix
Specify Risk Matrix Dimensions
Use
In this Customizing activity, you can specify whether exposure frequency is used, in addition to
likelihood and severity, as a dimension for the risk matrix.
Standard settings
In the standard system, exposure frequency is disabled.

The graphical risk matrix can only support two dimensions. If you enable this third dimension, the
graphical risk matrix does not appear on the user interface.
Note: This setting affects the values available when you select the desired effect of a control. If you do
not have the exposure frequency dimension enabled, you cannot select that the desired effect is to reduce
the exposure frequency.
______________________________________________________________
SAP AG 195
______________________________________________________________
SAP System
Specify Risk Levels
Use
In this Customizing activity, you can define the risk levels and the risk values that correspond to each risk
level. You can also specify the colors used in the graphical risk matrix to indicate the risk levels.
When you perform a risk assessment, the system automatically assigns a risk level when the risk value
falls within a certain range (between a lower limit and an upper limit). The system calculates the risk
value from the risk scores of the following parameters:
- Severity
- Likelihood
- Exposure Frequency
Standard settings
Activities

See also
For information about risk level calculation, see BAdI: Risk Level Calculation
(BADI_EHHSS_RISK_LEVEL_CALC).
Specify Likelihood
Use
In this Customizing activity, you can define levels of likelihood and their risk scores.
When you analyze a risk in a risk matrix, you can specify the likelihood of the hazard occurring and
resulting in the impacts identified for it. The score of the likelihood is used to calculate the risk level.
______________________________________________________________
SAP AG 196
______________________________________________________________
SAP System
Standard settings
Activities

Specify Severity
Use
In this Customizing activity, you can define severities and their risk scores. If the severity of an impact
differs depending on the context, you can also assign risk assessment types to the severities.
When you analyze a risk in a risk matrix, you can specify the severity of the impacts in the event that the
hazard occurs. The score of the severity is used to calculate the risk level.
Standard settings
Activities

Specify Exposure Frequency
Use
In this Customizing activity, you can define exposure frequencies and their risk scores.
When you analyze a risk in the risk matrix, you can specify the frequency of exposure to the hazard. The
score of the exposure frequency is used to calculate the risk level.
Requirements
You have enabled this risk dimension in the Customizing activity Specify Risk Matrix Dimensions.
Standard settings
______________________________________________________________
SAP AG 197
______________________________________________________________
SAP System
Activities

BAdI: Risk Level Calculation
Use
You can use this BAdI to determine the risk value and the risk level for an identified risk.
The BAdI uses the method CALCULATE_RISK to determine the risk level:
- It calculates the risk value by using a mathematical operator to combine the risk scores of the
individual risk matrix dimensions:
- Severity
- Likelihood
- Exposure frequency
Note: If you use a graphical risk matrix, the BAdI automatically determines the risk values for all
possible combinations of risk scores that are included in the risk matrix.
- It determines the risk level that is specified for the calculated risk value in the Customizing
activity Specify Risk Levels.
Requirements
You have configured a risk matrix and specified risk levels for in the Customizing activities under
Environment, Health and Safety -> Health and Safety Management -> Risk Analysis -> Risk
Matrix.
Standard settings
The BAdI implementation EHHSS_RISK_LEVEL_CALC_IMPL is delivered with the standard system.

This BAdI implementation calculates the risk value by multiplying the risk scores that have been
specified for the individual risk matrix dimensions.
Risk Evaluation
Specify Risk Evaluation Results
______________________________________________________________
SAP AG 198
______________________________________________________________
SAP System
Use
In this Customizing activity, you can specify the possible risk evaluation results.
Note: In the standard system, risk evaluation results appear on the tab for the risk matrix analysis method.
If you use customer-defined analysis methods instead of the risk matrix analysis method, this
Customizing activity is no longer relevant. For more information about adapting analysis methods, see
the Customizing activity Specify Assessment Steps and Analysis Methods.
Standard settings
Activities

If you want the system to automatically display these risk evaluation results in the application based on
the risk level, see also the Customizing activity Enable / Disable Automatic Determination for Risk
Evaluation.
Automatic Determination
Enable / Disable Automatic Determination for Risk Evaluation
Use
In this Customizing activity, you can enable or disable the automatic determination for risk evaluation.
Automatic determination helps you save time when you perform a risk assessment by returning an
evaluation result that the system derived automatically from the risk level. If you want to determine the
risk evaluation result manually, you can disable the function.
Requirements
You have assigned risk levels to risk evaluation results in Customizing activity Assign Risk Levels to
Risk Evaluation Results.
Standard settings
______________________________________________________________
SAP AG 199
______________________________________________________________
SAP System
Automatic determination is enabled in the standard system.
Assign Risk Levels to Risk Evaluation Results
Use
In this Customizing activity, you can assign risk levels to risk evaluation results. This enables risk
evaluation results to be automatically determined based on the risk levels calculated in the risk matrix.
Requirements
- You have specified the risk levels in the Customizing activity Specify Risk Levels.
- You have specified the risk evaluation results in the Customizing activity Specify Risk Evaluation
Results.
- You have enabled automatic determination of risk evaluation results in the Customizing activity
Enable / Disable Automatic Determination for Risk Evaluation.
Standard settings
Activities

0 Risk Treatment
0 Health Surveillance Protocols
0 Specify Age Trigger for Health Surveillance Protocols
Use
In this Customizing activity, you can specify possible values for the age as a trigger for health
surveillance protocol recommendation.
______________________________________________________________
SAP AG 200
______________________________________________________________
SAP System
In the application, you can select the specified values for the age when you edit recommendation criteria
for health surveillance protocols for controls.
Requirements
- You have implemented the Business Add-In in the Customizing activity BAdI: Occupational Health
Integration.
- You have activated the integration of the health and safety management application with an external
occupational health application in Customizing activity Specify Risk Assessment Types for
Integration with Occupational Health.
Standard settings
Activities

0 Schedule Jobs for Recommending Health Surveillance Protocols
Use
In this Customizing activity, you can schedule jobs for the report Transfer Recommended Health
Surveillance Protocols To OH App (R_EHHSS_PROPOSE_HSPROTOCOLS). You can use this report
to extract information about recommended health surveillance protocols for risks from the Environment,
Health, and Safety system and to transfer this information to an integrated occupational health
application.
Requirements
- You have activated the integration with an occupational health application by activating an
implementation of the Business Add-In BAdI: Occupational Health Integration.
- In the Customizing activity Specify Risk Assessment Types for Integration with Occupational
Health, you have specified the risk assessment types that you want to integrate with the
occupational health application.
0 BAdI: Person Determination for Recommended Health Surveillance Protocols
Use
______________________________________________________________
SAP AG 201
______________________________________________________________
SAP System
This Business Add-In (BAdI) is used in the Environment, Health, and Safety component. If you want
to provide person-specific recommendations of health surveillance protocols for a specific risk to an
integrated occupational health application, you can use this BAdI to determine all persons that are
exposed to the risk. After the jobs and locations of the risk have been determined by the BAdI
Determination of Health Surveillance Protocols (BADI_EHHSS_RAS_HSP), the BAdI uses the method
Determine Persons
(IF_BADI_EHHSS_RAS_HSP_PERS) to create a list of affected persons according to their job,
location, or similar exposure group (SEG) and transfers this information back to the BAdI Determination
of Health Surveillance Protocols.
Requirements
You have activated an implementation of the BAdI Determination of Health Surveillance Protocols
(BADI_EHHSS_RAS_HSP).
Standard settings
The BAdI definition is active in the standard system.

- BADI_EHHSS_RAS_HSP_PERS_LJ
This implementation determines the affected persons according to their jobs and locations:
- For job hazard analyses, it determines the persons that are assigned to the job and job location
of each job hazard analysis. Note that the implementation checks only the location that a job
hazard analysis has been performed for. It does not check for additional locations that have
been assigned to the job hazard analysis later.
- For all other risk assessment types, it determines the persons that are assigned to the location of
the risk.
- BADI_EHHSS_RAS_HSP_PERS_SEG
This implementation determines the affected persons according to their SEG. If an SEG exists for
the location, job, or both job and location of the risk, it checks for all persons that are assigned to
this SEG.
Example
0 BAdI: Determination of Recommended Health Surveillance
______________________________________________________________
SAP AG 202
______________________________________________________________
SAP System
Protocols
Use
this BAdI to enable the automatic determination of recommended health surveillance protocols for a
specific risk in the health and safety management application. You can also use this BAdI to check
whether these recommendations apply to each person that is exposed to the risk, and to create a list of
person-specific recommendations that can be transferred to the integrated occupational health
application.
The BAdI uses the following methods:
- AUTOMATIC_PROPOSALS
This method determines the health surveillance protocols that are recommended for a risk according
to the recommendation criteria of each protocol.
It automatically assigns all determined recommendations to the risk that is selected in a risk
assessment.
The method is called when a user chooses the Recommend Automatically button on the Health
Surveillance Protocols tab while editing the controls of a risk assessment.
- DETERMINE_HSPROTOCOLS
This method creates a person-specific list of recommended health surveillance protocols for a risk.
After all persons exposed to a risk have been determined by using the BAdI Determination of Risk-
Related Person Assignment for Health Surveillance,the method checks whether the
recommendations apply to each person according to the recommendation criteria of each protocol.
This method is called within a background job that you schedule by using the Customizing activity
Schedule Jobs for Recommending Health Surveillance Protocols to transfer the recommended
health surveillance protocols to an integrated occupational health application.
Requirements
- You have activated an implementation of the Business Add-In BAdI: Occupational Health
Integration to enable integration with an occupational health application.
Health, you have specified the risk assessment types that you want to integrate with the occupational
health application.
Standard settings

The BAdI implementation BADI_EHHSS_RAS_HSP is delivered with the standard system. It determines
the person-specific recommendations of health surveillance protocols as follows:
______________________________________________________________
SAP AG 203
______________________________________________________________
SAP System
1. It uses the method AUTOMATIC_PROPOSALS to determine the health surveillance protocols that
are recommended for a risk according to the following recommendation criteria:
- Agent assigned to the risk
- Risk level of the risk
- Value type of the agent
- Exposure rating of the risk
2. For each person that is exposed to the risk, it uses the method
DETERMINE_HSPROTOCOLS to check whether the recommendations apply according to the
following recommendation criteria:
- Gender of the person

- Age of the person
Example
0 Occupational Health Integration
0 Specify Risk Assessment Types for Integration with Occupational Health
Use
In this Customizing activity, you can specify which risk assessment types are relevant for integration with
an occupational health application. If you specify a risk assessment type, you can add health surveillance
protocols to risks for this specific risk assessment type on a new tab during the risk assessment process.
If you activate the integration for a risk assessment type, you can also enter recommendation
criteria for health surveillance protocols in the application. The system uses this data to determine if a
health surveillance protocol should be recommended as a control to treat risks.
Requirements
- You have implemented the Business Add-In in Customizing activity BAdI: Occupational Health
Integration.
Note: The BAdI implementation BADI_EHFND_BO_HSP_PROXY_IMPL is active in the standard
system. This BAdI implementation provides the integration into the occupational health function of
SAP EHS Management as part of SAP ERP.
______________________________________________________________
SAP AG 204
______________________________________________________________
SAP System
- If you want to integrate with the occupational health function of SAP EHS Management as part of
SAP ERP, you must implement SAP Note 90994 or a support package level for EA-APPL that
contains this note.
- In Customizing activity Specify Destinations for Integration, you have specify RFC destination
DEST_HR to your occupational health application.
Note: The occupational health application must be installed on the Human Resources system.
Standard settings
In the standard system, the integration is deactivated for all risk assessment types.
Activities
Activate the integration for all risk assessment types you want to use.
Note: We recommend you activate the integration for the risk assessment types specified in Customizing
activity Specify Risk Assessment Types that involve agents.
0 BAdI: Occupational Health Integration
Use
this BAdI to enable the integration with the occupational health function provided by the SAP EHS
Management as part of the SAP ERP or with other occupational health data provider systems.
The BAdI reads protocol information from an occupational health system, determines the risk-related
proposals for health surveillance, and sends a person-related protocol proposal list to the occupational
health system.
Requirements
- You have specified the RFC destination of the Human Resources system (DEST_HR) in the
Customizing activity Specify Destinations for Integration.
Note: Since the occupational health application has to be installed on the Human Resources system,
destination DEST_HR is also used to call the integrated occupational health application.
- To activate object-based navigation (OBN navigation) for the method

DISPLAY_HSPROTOCOLS, you have defined an HTTP connection to the integrated system by
using transaction sm59.
- You have added the service to display health surveillance protocols in the corresponding PFCG role.
For more information, see Copying Services for Health Surveillance Protocol Integration.
Standard settings
______________________________________________________________
SAP AG 205
______________________________________________________________
SAP System
The BAdI definition is active in the standard system and contains the following methods:
- READ_HSPROTOCOLS
The system reads health surveillance protocols used in the integrated occupational health system and
provides a list of available protocols.
The health surveillance protocols are selected by date, language, and health surveillance protocol
type.
- READ_HSPROTOCOL_DESCS
The system reads the language-dependent description of a health surveillance protocol in the
integrated occupational health system and provides a list of all available descriptions. The language-
dependent descriptions are selected by date and health surveillance protocol type.
- READ_HSPROTOCOL_TYPES
The system reads health surveillance protocol types used in the integrated occupational health
system and provides a list of all available types.
The health surveillance protocol types are selected by a provided language or based on the system
language.
- READ_HSPROTOCOL_TYPE_DESC
The system reads the language-dependent description of a health surveillance protocol type in the
integrated occupational health system and provides a list of all available descriptions. The language
dependent descriptions are selected by date.
- DISPLAY_HSPROTOCOLS
The system uses OBN navigation to display health surveillance protocols within the integrated
occupational health system.
The system executes these methods when you edit or use a health surveillance protocol in Environment,
Health, and Safety.
The BAdI implementation BADI_EHFND_BO_HSP_PROXY is delivered with the standard system. This
BAdI implementation provides the integration into the occupational health function of SAP EHS
Management as part of the SAP ERP.
Example
______________________________________________________________
SAP AG 206
______________________________________________________________
SAP System
1 Risk Monitoring and Review
1 Specify Control Inspection Questions
Use
In this Customizing activity, you can specify questions that inspectors must answer when conducting a
control inspection. You can assign these questions to specific controls when you edit control master data
in the application.
If you specify questions directly in the control master data in the application, those questions also appear
in this Customizing table.
Note: The system determines the level of control effectiveness based on the number of yes answers.
Therefore, you must form each question in a way where a yes answer is a positive result.
For example, a yes answer to the question Is the fire extinguisher fully charged? is a positive result;
whereas, a yes answer to the question Is the fire extinguisher empty? is a negative result.
Standard settings
The standard system is delivered without examples.
Activities
Define questions that can be assigned to controls for use in control inspections.
1 Specify Control Effectiveness
Use
In this Customizing activity, you can specify values for control effectiveness and indicate which of those
values is treated by the system as effective. In the application, you can evaluate controls and specify their
effectiveness either manually or automatically as one of these values.
If a control is evaluated and determined to be effective, the system does not start any further processes,
such as follow-up assessments.
Standard settings
Activities
______________________________________________________________
SAP AG 207
______________________________________________________________
SAP System

1 Specify Results for Risk Assessment Review
Use
The investigation of incidents that occurred in your organization can include a control effectiveness
evaluation. Based on the results of this evaluation, you can review and update the risk assessments that
the evaluated controls are assigned to. You can then notify the responsible incident investigation lead of
the review results .
You use this Customizing activity to specify the review results that can be communicated to the
investigation lead.
Requirements
- You use the incident management application that is delivered with the Environment, Health, and
Safety component.
- You have configured the control effectiveness evaluation as an incident investigation step in the
Customizing activity Specify Steps.
Standard settings
Activities


1 BAdI: Calculation of Control Effectiveness
______________________________________________________________
SAP AG 208
______________________________________________________________
SAP System
Use
automatically calculate whether a control is effective based on the answers given to control inspection
questions.
The BAdI uses the method CALC_CNTR_EFFECTIV to calculate the control effectiveness using the
following logic:
- If 100% of the answers are Yes, the control is Effective.

- If more than 75% of the answers are Yes, the control is Improvable.
- If fewer than 75% of the answers are Yes, the control is Ineffective.
Requirements
You have specified effectiveness values in the Customizing activity Specify Control Effectiveness.
Standard settings
The BAdI implementation BADI_EHHSS_CINSP_RESULT_CALC is active in the standard system.
Example
1 BAdI: Automatic Control Evaluation
Use
this BAdI to provide automatic evaluation of the effectiveness of controls. In the application, the user can
choose to evaluate the effectiveness automatically instead of manually entering the effectiveness or
requesting a control evaluation be performed.
Requirements
You have specified effectiveness values in Customizing activity Specify Control Effectiveness for
Environment, Health, and Safety under Health and Safety Management.
Standard settings
______________________________________________________________
SAP AG 209
______________________________________________________________
SAP System
The BAdI has the two following exporting parameters:
- Date of effectiveness evaluation (EHFND_DATE)

- Effectiveness code (EHHSS_CTRL_EFFECTIVN_CODE)
Activities
Once you have created an implementation of this BAdI, the system displays the Create and Evaluate
Automatically pushbutton on the screen for evaluating controls.
1 BAdI: Creation of 1:1 Copy of Risk Assessment
Use
You can use this BAdI to copy data from an existing risk assessment that is already closed to a follow-up
risk assessment. The BAdI is called when you need to update the effectiveness in a closed risk
assessment. If the new value is no longer effective and the risk assessment is closed, the new value will
be set in the follow up risk assessment created by the BAdI.
The BAdI uses the method COPY_ALL_RISK to copy all relevant data. It creates a new risk revision for
each risk that is copied to the follow-up assessment. This allows you to edit risk data in a follow-up
assessment without changing the data that was originally recorded for the selected risk.
By default, the BAdI copies the following data:
- Risk assessment data - Assessment title

- Regulations on assessment level
- Assessment reasons
- Assessment team
- Recurrent tasks that are still open
- Additional assessment data for job hazard analyses
- Observed person
- Job location
- Job steps
- Risk data
- Identified risks
- Impacts
- Regulations on risk level
______________________________________________________________
SAP AG 210
______________________________________________________________
SAP System
- Analysis data
Note: The analysis data is a copy of the original data with the exception of the OEL values in
the risk, which are obsolete and not copied.
- Controls (including control effectiveness values) are copied to the existing controls for the risk
- Health surveillance protocols are copied to the health surveillance protocols related to the
existing controls for the risk
- Documents
Standard settings
The BAdI implementations EHHSS_RAS_COPY_NO_CHANGES_IMPL is delivered with the standard

system and is active by default.
1 BAdI: Creation of Follow-Up Revisions of Risks
Use
this BAdI to create follow-up revisions of risks and copy data from the predecessing risk revision to the
follow-up risk revision. The BAdI is called when you select risks and assign them to risk assessments for
follow-up.
The BAdI uses the method CREATE_RISK_FOLLOW_UP to copy all relevant data. It creates a new risk
revision for each risk that is copied to the assigned follow-up risk assessment. This allows you to edit risk
data in the assigned risk assessment without changing the data that was originally recorded for the
selected risk.
In the standard delivery, the BAdI copies the following data to the follow-up risk revision:
- Risk data
- Impacts
- Analysis data
Note: With the implementation of BADI_EHHSS_RISK_FOLLOW_UP, the system does not copy
analysis data for an initial risk. Instead, it uses the analysis data from the residual risk for the initial
risk data in the follow-up risk assessment.
- Controls (including control effectiveness values) are copied to the existing controls for the risk.
- Health surveillance protocols are copied to the health surveillance protocols related to the existing
controls for the risk.
- Documents
Standard settings
______________________________________________________________
SAP AG 211
______________________________________________________________
SAP System
The BAdI implementations BADI_EHHSS_RISK_FOLLOW_UP is delivered with the standard system

and is active by default.
1 BAdI: Data Transfer to Follow-Up Assessment
Use
this BAdI to copy data from an existing risk assessment to a follow-up risk assessment. The BAdI is
called when you create a follow-up assessment, for example, to reassess identified risks after a regulation
has changed.

- Assessment team
- Observed person
- Job location
- Job steps
- Risk data
- Identified risks
- Impacts
- Analysis data
Note: For the implementation EHHSS_COPY_ASSESSMENT_IMPL, the system does not
copy any analysis data for initial risk. Instead, it uses the analysis data from the residual risk
for the initial risk data in the follow-up assessment.
______________________________________________________________
SAP AG 212
______________________________________________________________
SAP System
existing controls for the risk.
- Documents
Standard settings
The BAdI implementations EHHSS_COPY_ASSESSMENT_IMPL is delivered with the standard system

2 Integration
2 PM Integration
2 Activate and Configure PM Integration
Use
In this Customizing activity, you can activate and configure integration of the health and safety
management component with the worker safety feature in the Plant Maintenance (PM) component. You
can use this integration in the following ways:
- Communicate risk information (such as risk ID, risk level, and controls for a risk) from the
health and safety management component to PM. - Link controls to the following safety
measures types:
- Material (MM)
- Equipment (PM)
- Document (PM)*
- Permit (PM)*
- Task list (PM)*
- Other production resource/tool (Other PRT)*
*For these objects, only the data records that have been classified as safety measures in PM are
available for selection in Environment, Health, and Safety.
Requirements
- You are using SAP enhancement package 6 for SAP ERP 6 or higher on the system that you
want to integrate. If you are using a lower version, you cannot activate integration.
- You have activated the business function /EAMPLM/LOG_EAM_WS for the worker safety
function in the PM system.
______________________________________________________________
SAP AG 213
______________________________________________________________
SAP System
- You have specified the hierarchy level for control types in Customizing activity Configure
Hazard and Control Register. The controls sent to PM are sorted according to the hierarchy in
the PM object.
- You have specified the risk levels in Customizing activity Specify Risk Levels. The risks sent
to PM are sorted according to the risk level determined in the risk assessment.
- In the application, you have linked locations to the PM objects that should receive risk
information.
Standard settings
The integration from the health and safety management component to the PM component is deactivated in
standard system.
Activities
1. Activate integration with PM.

2. Specify the risk assessment types that are relevant for the integration. Only the risks identified for
the specified risk assessments types are sent to PM.
3. Specify the safety measure types that you want to link controls to.
See also
For more information about communicating risk information to PM plants, see the Customizing activity
Specify Location Types for PM Plants. The communication of risk information to plants is based on the
location type.
2 Map Risk Levels for PM Integration
Use
In this Customizing activity, you can map the risk levels of Environment, Health, and Safety to the
risk levels of the worker safety functionality in the Plant Maintenance (PM) component. Mapping is
necessary, because the risk level of risk assessment can have up to 21 characters and the PM risk level
can have only up to 4 characters. This enables the system to communicate risk levels from risk
assessment to PM.
Requirements
______________________________________________________________
SAP AG 214
______________________________________________________________
SAP System
- You have set up PM integration in Customizing activity Activate and Configure PM Integration.
- You have specified the risk levels in Customizing activity Specify Risk Levels.
Standard settings
Activities

2 Specify Location Types for PM Plants
Use
In this Customizing activity, you can specify location types that correspond to plants in the Plant
Maintenance (PM) component. This enables you to communicate risk information for a location to its
corresponding plant in PM. If you do not specify location types in this activity, no risk information is
communicated to PM plants.
In the application, you can assign a PM plant to a location, but you cannot create a direct link (as you
would for the PM technical object). The system uses the location type to identify the locations that
correspond to a plant. When Environment, Health, and Safety delivers the risk information for the PM
plant, the system communicates the risk information for all determined locations that have the assigned
plant.
Prerequisites
- You have specified location types in Customizing activity Specify Location Types under
Foundation for EHS.
- You have set up PM integration in Customizing activity Activate and Configure PM Intgration.
Standard settings
Activities

Example
______________________________________________________________
SAP AG 215
______________________________________________________________
SAP System
You specify the location type Site as corresponding to PM plants. In the system, you create a location as
a site and assign a PM plant to the location. When the PM system requests risk information for that plant,
Environment, Health, and Safety communicates risk information for only the locations (with the plant
assigned) that are sites.
2 Specify Risk Assessment Types for Integration with Occupational Health
Use
In this Customizing activity, you can specify which risk assessment types are relevant for integration with
an occupational health application. If you specify a risk assessment type, you can add health surveillance
protocols to risks for this specific risk assessment type on a new tab during the risk assessment process.
If you activate the integration for a risk assessment type, you can also enter recommendation criteria for
health surveillance protocols in the application. The system uses this data to determine if a health
surveillance protocol should be recommended as a control to treat risks.
Requirements
- You have implemented the Business Add-In in Customizing activity BAdI: Occupational Health
Integration.
Note: The BAdI implementation BADI_EHFND_BO_HSP_PROXY_IMPL is active in the standard
system. This BAdI implementation provides the integration into the occupational health function of
SAP EHS Management as part of SAP ERP.
- If you want to integrate with the occupational health function of SAP EHS Management as part of
SAP ERP, you must implement SAP Note 90994 or a support package level for EA-APPL that
contains this note.
- In Customizing activity Specify Destinations for Integration, you have specify RFC destination
DEST_HR to your occupational health application.
Note: The occupational health application must be installed on the Human Resources system.
Standard settings
In the standard system, the integration is deactivated for all risk assessment types.
Activities
Activate the integration for all risk assessment types you want to use.
Note: We recommend you activate the integration for the risk assessment types specified in Customizing
activity Specify Risk Assessment Types that involve agents.
Use
______________________________________________________________
SAP AG 216
______________________________________________________________
SAP System
health system.
Requirements

Standard settings
- READ_HSPROTOCOLS
The system reads health surveillance protocols used in the integrated occupational health system and
provides a list of available protocols.
The health surveillance protocols are selected by date, language, and health surveillance protocol
type.
integrated occupational health system and provides a list of all available descriptions. The language-
dependent descriptions are selected by date and health surveillance protocol type.
language.
______________________________________________________________
SAP AG 217
______________________________________________________________
SAP System
-
READ_HSPROTOCOL_TYPE_DESC
Health, and Safety.
The BAdI implementation BADI_EHFND_BO_HSP_PROXY is delivered with the standard system.

This BAdI implementation provides the integration into the occupational health function of SAP EHS
Example
2 Integration with SAP Management of Change
2 Activate Integration with SAP Management of Change
Use
In this Customizing activity, you can activate the integration with SAP Management of Change. This
enables you to add a change request as a task in Environment, Health, and Safety and communicate it
to the SAP Management of Change system.
Requirements
______________________________________________________________
SAP AG 218
______________________________________________________________
SAP System
-
You have specified the RFC destination of the SAP Management of Change system
(DEST_MOC) in the Customizing activity Specify Destinations for Integration.
- You have activated object-based navigation (OBN navigation) by defining an HTTP connection to
the SAP Management of Change system in transaction sm59.
- You have specified the RFC connection or the HTTP connection in the relevant PFCG roles.
Standard settings
Integration with SAP Management of Change is disabled in the standard system.

This integration is available for incident management and health and safety management.
Activities
If you activate the integration, the integration is activated for both incident management and health and
safety management.
If you want to later deactivate the integration, this setting also affects both incident management and
health and safety management. If you have already added change requests in an incident or a risk
assessment, you can still display existing change requests. However, you cannot add any new change
requests.
2 Activate Integration of Risk Assessment Requests
Use
In this Customizing activity, you can activate the integration of risk assessment requests. You can use this
integration to allow the SAP Management of Change system to send requests for performing risk
assessments to the Environment, Health, and Safety system.
Activating the integration also enables you to simulate risk assessments, for example, if your organization
wants to perform risk assessments to collect information about planned changes before they happen.
Since simulated risks are not real risks, they do not affect the real risk level at your organization. You can
only search for and access simulated risk assessments when integration is activated.
Requirements
- You have performed the Customizing Assign Default Roles to Workflow Tasks. The system assigns
the users with the role Industrial Hygienist, Environmental Manager, or Safety Manager as
possible agents for the tasks.
______________________________________________________________
SAP AG 219
______________________________________________________________
SAP System
-
If your Management of Change application runs on a separate system, you have to specify the
RFC destination in Customizing activity Specify Destinations for Integration. Note: For integration
with SAP Management of Change, you need an HTTP connection to an ABAP system (type H).
To enable the object-based navigation from the Environment, Health, and Safety application to
the SAP Management of Change application, the RFC destination of the target system must be
entered in the relevant PFCG roles.
Standard settings
Integration of risk assessment requests is disabled in the standard system.
- The standard system is set up to receive risk assessment requests from change requests in SAP
Management of Change. The Risk Assessment Request function module
(EHHSS_RFC_RAS_REQUEST) only accepts requests from requester type Change Request from
SAP Management of Change (specified in the domain EHHSS_RAS_REQ_TYPE_CODE).
Activities
You can enable or disable integration. Note that if you enable and later disable integration, open risk
assessment requests are affected. For example, the application no longer displays the search screen for
simulated risk assessments.
2 Product Stewardship Network
2 Specify SAP Product Stewardship Network Integration
Use
In this Customizing activity, you get details that describe how to integrate SAP Product Stewardship
Network into Product Compliance using Web Services.
All users work with one single SAP Product Stewardship Network user, so that the credentials can be
configured in the logical port of the Web Service.
In the Activities section of this document, it is defined how to configure the available Web Services for
the integration of the following functionalities:
- Side panel functionality

- Supplier collaboration
- Regulatory list content load
Hint
______________________________________________________________
SAP AG 220
______________________________________________________________
SAP System
-
For further import and export options of regulatory list revisions see Customizing
______________________________________________________________
SAP AG 221
______________________________________________________________
SAP System
activty Export and Import of Regulatory List Revisions

For IMDS specific import topics see Customizing activty Set Up System with IMDS All Files
Requirements
- You have registered an enterprise account on SAP Product Stewardship Network

- For the integration of the side panel functionality, either you have the WSDL file (web service
definition language file) or you know the URL to the WSDL file of the Product Declaration Web
Service.
Hint:
To complete the Web Service configuration for the regulatory list content load you do not
need to setup the configuration for the side panel functionality because there is no
dependency between the two configurations.
Be aware:
Before you can use the Web Service, you need to import the related certificates from SAP
Product Stewardship Network. For more details, see SAP Note 66375.
Standard settings
SAP Product Stewardship Network is integrated into the compliance interfaces in a Business Context
Viewer side panel. For more information, see the documentation for the Customizing activity Integrate
Compliance Data with Business Context Viewer.
Activities
Configure the necessary Web Service consumer proxies. You have to perform the following steps twice,
once for each proxy. The step description indicates whether specific data for a proxy has to be entered.
1. Start the transaction SOA Manager and navigate to Web Service Configuration in Service
Administration View. Search for the consumer proxy and manually create the logical port for the
following Web Service proxies:
- A for the integration of the side panel functionality. Compare step 6A.:
CO_EHFND_OD_PRODUCT_DECLARAT
- B for the integration of the regulatory list content load and of the supplier collaboration.
Compare step 6B.: CO_EHFND_OD_PRODUCT_STEWARDSHI
2. Select the service proxy and choose Apply Selection. Create or edit the logical port
EHSM_OD_PORT in the detail table view Configurations.
3. Select the Logical Port is Default checkbox.
4. Enter a Description for the logical port.
5. Select Configuration Type WSDL Based Configuration
6. Select the option Via HTTP Access and specify the corresponding WSDL URLs from SAP
Product Stewardship Network:
- A for the integration of the side panel functionality. Compare step 1A.: https://<
name of the system>/services/ProductDeclaration?wsdl
______________________________________________________________
SAP AG 222
______________________________________________________________
SAP System
- B for the integration of the regulatory list content load and of the supplier
collaboration. Compare step1B.: https://< name of the
system>/services/ProductStewardshipNetwork?wsdl Hint:
You need to make sure that the WSDL file can be accessed successfully. Depending on your
network configuration, it can be necessary to specify an HTTP proxy server using the
Show/Hide Proxy Settings button. Alternatively you can manually download the WSDL
files from the URLs specified above and use the option Via File instead. If you choose this
option, you need to ensure a valid proxy server configuration under Transport Settings in the
following screen.
7. Enter a user ID and password in the authentication settings of your logical port under Consumer
Security. Use your registered user on the SAP Product Stewardship Network.
2 Business Add-Ins for Integrated Notifications
2 BAdI: Creation and Completion Check of Integrated Notifications
Use
When you create a maintenance notification task in incident management, a default method takes the
information from the maintenance notification and then sends it to Plant Maintenance (PM) for further
processing. However, if you specified custom fields for a notification, the method in the standard delivery
cannot handle the information in these fields and thus cannot send the entire notification for processing.
Standard settings

BAdI Methods
______________________________________________________________
SAP AG 223
______________________________________________________________
SAP System
parameters:
Import Parameters

Export Parameters

to get the completed notifications from the corresponding functional areas and set their status in
incident management. The method includes the following import and change parameters:
Import Parameters
Change Parameters
3 Fiori Apps for Health and Safety Management
3 Specify Role for Local Emergency Contact Person
Use
In this Customizing activity, you can specify which role is displayed as the local emergency (first aid)
contact.
Requirements
______________________________________________________________
SAP AG 224
______________________________________________________________
SAP System
The role that you want to specify in this Customizing activity must be defined in the Specify Role of
Person Responsible Customizing activity as well.
Standard settings
Activities
Specify the role that is displayed as the first aid contact in the Retrieve Safety Information app.
3 BAdI: Extend Data of Gateway Service of Retrieve Safety Information App
Use
This Business Add-In (BAdI) is used in the transactional app Retrieve Safety Information. You use this
BAdI to provide values for custom OData attributes.
Standard settings
This BAdI is not active in the standard system and comprises the following method:
BAdI Methods
- FILL_CHM_AT_LOC_EXT
This method is used to add custom fileds in the OData service.
The method includes the following import and change parameters: Import
Parameter
- IO_CHM_REV_NODE - Custom BOPF node that is used to access the sub-nodes. Change
Parameters
- CS_RESULT_CHEMICALS - Gateway proxy structure for a chemical at location This BAdI
definition uses the IF_EHHSS_BADI_SAFETY_INFO_DPC interface.
3 BAdI: Extend Model of Gateway Service of Retrieve Safety Information App
Use
BAdI to add custom attributes to an existing application OData service.
Standard settings
______________________________________________________________
SAP AG 225
______________________________________________________________
SAP System
BAdI Methods
- ENHANCE_GW_SERVICE_ENTITY_MPC
This method is used to enhance the OData model with new properties in existing entity sets.
The method includes the following import parameters:
Import Parameter
- IO_ENTITY_TYPE - Interface that represents a script-based OData entity type
- IV_ENTITY_TYPE_NAME - Name of the OData entity type
This BAdI definition uses the IF_EHHSS_BADI_SAFETY_INFO_MPC interface.
4 Business Add-Ins
4 BAdI: Determination of Risks for Similar Exposure Group
Use
You can use this BAdI to determine the risks that are relevant for a similar exposure group (SEG). In
turn, the risks enable you to set up SEGs that use jobs, locations, and agents that belong together.
Otherwise, you could mistakenly create an SEG for a job and reference agents that are not actually
involved in that job. Later, this leads to incorrect exposure profiles for your workers. The BAdI ensures
that SEGs are accurate and based on real risk data.
For example, if you create an SEG for a specific job, the BAdI finds the risks that have already been
identified for this job. These risks are relevant to the SEG and you can use only their corresponding
agents in the SEG.
The system calls the BAdI to determine risks in the following two situations:
- When you create an SEG, you create it based on jobs, jobs at selected locations, or locations. The
system calls the BAdI to determine the risks that correspond to the jobs/locations and displays the
agents that are involved in the jobs or exist at the locations.
- When you edit an SEG later, you can add jobs, locations, and agents to the SEG. The system calls
this BAdI to determine the risks that correspond to the locations, jobs, and agents that are currently
assigned to the SEG.
In addition, you can use this BAdI to determine the risk assessment types of theses risk assessments that
contains the determined SEG-relevant risks. The risk assessment types are used for authority checks.
The system calls the BAdI for the authority check when you want to create, edit, or display an SEG. If
you have authorization for at least one risk assessment type, the screen for creating, editing, or displaying
______________________________________________________________
SAP AG 226
______________________________________________________________
SAP System
SEGs opens. However, only SEGs containing risks with a risk assessment type for which you have
authorizations are displayed.
Standard settings
- GET_RISKS
The system returns a table with all risks relevant for the SEG.
- GET_RAS_TYPES
The system returns a table with all risk assessment types relevant for the SEG.
The BAdI implementation BADI_EHHSS_SEG_GET_RISKS is delivered with the standard system.
4 BAdI: Check Readiness for Action
Use
this BAdI to perform checks on the following actions in the risk assessment data record:

For each action and for each risk assessment type, a BAdI implementation is delivered in the standard
system to perform the check. The check ensures, for example, that all tasks have been completed before
you can change the status of the data record. If necessary, you can deactivate the standard
implementations and implement customer-specific checks instead.
Caution
consistency.
Standard settings

BAdI Methods
The BAdI has the following methods:
______________________________________________________________
SAP AG 227
______________________________________________________________
SAP System
- IF_BADI_EHHSS_RAS_RDY_FOR_ACT~CHECK_COMPLETENESS_ON_ACTION - Check
completeness on the action given by filter value
The system executes this method when you change the status. The method checks the risk
assessment and can return a success, warning, or error message, or no message. The system returns
an error when recurring tasks are still open and prevents the status change. Otherwise, the system
changes the status.
- IF_BADI_EHHSS_RAS_RDY_FOR_ACT~FURTHER_ACTIONS_AFTER_CHECK - Additional
actions after checking completeness
The system executes this method after the check when it changes the status. The method does not
provide functionality in the standard system. You can use this method to create customer-specific
functionality that executes additional actions on the risk assessment.
You can use the following BAdI implementations for environmental risk assessments:
- BADI_RDY_FOR_ACT_RAS_ENV_CLOSE
- BADI_RDY_FOR_ACT_RAS_ENV_VOID
You can use the following BAdI implementations for health risk assessments:
- BADI_RDY_FOR_ACT_RAS_HEA_CLOSE
- BADI_RDY_FOR_ACT_RAS_HEA_VOID
You can use the following BAdI implementations for safety risk assessments:
- BADI_RDY_FOR_ACT_RAS_SAF_CLOSE
- BADI_RDY_FOR_ACT_RAS_SAF_VOID
You can use the following BAdI implementations for job hazard analyses:
- BADI_RDY_FOR_ACT_RAS_JHA_CLOSE
- BADI_RDY_FOR_ACT_RAS_JHA_VOID
Activities
- RAS_TYPE (Risk Assessment Type)
______________________________________________________________
SAP AG 228
______________________________________________________________
SAP System
- EHHSS_RAT_ENV (Environmental Risk Assessment)

- EHHSS_RAT_HEA (Health Risk Assessment)
- EHHSS_RAT_JHA (Job Hazard Analysis)
- EHHSS_RAT_SAF (Safety Risk Assessment)
- ACTION_NAME (action of business object EHHSS_RISK_ASSESSMENT for node ROOT)
- SET_VOID_ROOT
- SET_CLOSED_ROOT
- NODE_NAME (node name of business object EHHSS_RISK_ASSESSMENT)
- ROOT
Example
You want to redefine a check that the system executes for a job hazard analysis when you change the
status from In Progress to Closed:
- Deactivate the delivered BAdI Implementation BADI_RDY_FOR_ACT_RAS_JHA_CLOSE.

- Create a new BAdI Implementation with following filter values:
- RAS_TYPE = EHHSS_RAT_JHA
- NODE_NAME = ROOT
- During the creation process, you can choose to do one of the following:
- Create a completely new class for your checks. - Copy an existing example class and enhance it.
- Create a new class deriving from the delivered example class.
4 Business Add-Ins for Chemicals
4 BAdI: Transfer of Phrases
Use
BAdI to specify phrase sets that were taken into account when transferring phrases from SAP EHS
Management as part of SAP ERP or from Product Safety as part of SAP S/4HANA to
Environment, Health, and Safety as part of SAP S/4HANA.
This BAdI is called when report Transfer of Phrases (R_EHFND_PHRASE_TRANSFER) is executed.
Standard settings
______________________________________________________________
SAP AG 229
______________________________________________________________
SAP System
The BAdI definition is active in the standard system. It contains the following method:
- DETERMINE_PHRASE_SETS
The system returns a table with all phrase sets from SAP EHS Management as part of SAP ERP
or from Product Safety as part of SAP S/4HANA and the corresponding tables and fields of
In addition, you can select a checkbox if you want to concatenate a phrase code in the statement text.
If you select the checkbox, a phrase that contains, for example, the phrase code H330 and the phrase
text Fatal if inhaled, will be transferred as statement with the text H330: Fatal if
inhaled.
The BAdI implementation BADI_EHFND_PHRASE_TRANSFER is delivered with the standard

system. This BAdI implementation determines specified phrase sets for the phrase transfer. For
information about the delivered settings, see Mapping Table for Phrase Sets.
Activities
Add new implementations to BADI_EHFND_PHRASE_TRANSFER, when you implement this BAdI.
Example

CL_BADI_EHFND_PHRASE_TRANSFER.
4 BAdI: Transfer of OEL Data
Use
BAdI to specify data sources for transferring substance data from SAP EHS Management as part of
SAP ERP or from Product Safety as part of SAP S/4HANA to Environment, Health, and Safety as
part of SAP S/4HANA.
This BAdI is called when report Transfer of OEL Data
(R_EHFND_FILL_REGL_BY_EHS_SUBST) is executed.
The BAdI methods GET_EHS_CLASSES and GET_EHS_SUBST_IDENT_LISTING are also called
when the report Transfer of Chemicals (R_EHFND_FILL_CHM_BY_EHS_SUBST) is executed.
Requirements
______________________________________________________________
SAP AG 230
______________________________________________________________
SAP System
For more information, see prerequisites in the documentation of report report Transfer of OEL
Data.
Standard settings
- GET_HITLIST_ID:
for transferring substance data. Note that only substances from the selected hit list are transferred.
- GET_EHS_CLASSES:
This method specifies the sources for the OELs, the regulatory list, the value type and the class
itself. Note that you have to use the parameter of the interface
IF_EHFND_REGL_FILL.
- GET_EHS_SUBST_IDENT_LISTING:
This method determines the identification listing for transferring data like the CAS number or
substance name. Note that the CAS number and the substance name have to be included in the
identification listing.
- MAP_VALUE_TYPE:
This method specifies the mapping between the value type in the SAP EHS Management as part
of SAP ERP application or the Product Safety as part of SAP S/4HANA application and in the
Environment, Health, and Safety application.
______________________________________________________________
SAP AG 231
______________________________________________________________
SAP System
MAP_REGLIST_ID:
This method specifies the mapping between the Regulatory List ID in the SAP EHS
Management as part of SAP ERP application or the Product Safety as part of SAP S/4HANA
application and in the Environment, Health, and Safety application.
The BAdI implementation BADI_EHFND_REG_LIST_TRANSFER is delivered with the standard

system. It determines data for transferring as follows:
- It uses the method GET_HITLIST_ID to set the Set of Hits - Group as HITLIST and the Set
of Hits - Group Entry as LISU.
- The method GET_EHS_CLASSES determines the class as data sources. For more information about
the standard delivery, see the list of Classes and Characteristics used as data sources for OEL data
transfer.
- The method GET_EHS_SUBST_IDENT_LISTING used the identification listing D_DEFAULT
for transferring data for listed substances.
Note: The CAS number and the substance name have to be included the identification listing
D_DEFAULT. Otherwise, the data cannot be transferred.
- The method MAP_VALUE_TYPE determines the value types in the SAP EHS Management as
part of SAP ERP application or the Product Safety as part of SAP S/4HANA application.
Note: In the standard implementation, the determined value type must be the same as in the
Environment, Health, and Safety application. Otherwise, the data cannot be transferred.
- The method MAP_REGLIST_ID maps the regulatory list ID in the SAP EHS Management as
part of SAP ERP application or the Product Safety as part of SAP S/4HANA application to an
ID in the Environment, Health, and Safety application.
Note: In the standard implementation, the IDs in the SAP EHS Management as part of SAP ERP
application or the Product Safety as part of SAP S/4HANA application must be the same as in
the Environment, Health, and Safety application. Otherwise, the data cannot be transferred.
Activities
When you implement this BAdI, add new implementations to the business add-in
BADI_EHFND_REGL_FILL.
We recommend you derive from CL_EHFND_REG_LIST_TRANSFER and overwrite the methods

according to your needs.
Example

CL_EHFND_REG_LIST_TRANSFER.
______________________________________________________________
SAP AG 232
______________________________________________________________
SAP System
-
4 BAdI: Transfer of Chemicals
Use
this BAdI to specify sources of data and data conversions for transferring substance data from the
specification database of SAP EHS Management as part of SAP ERP or of Product Safety as part of
SAP S/4HANA to Environment, Health, and Safety as part of SAP S/4HANA.
This BAdI is called when report Transfer of Chemicals (R_EHFND_FILL_CHM_BY_EHS_SUBST) is
executed.
Requirements
For more information, see prerequisites in the documentation of report Transfer of Phrases
(R_EHFND_PHRASE_TRANSFER) and report Transfer of OEL Data
(R_EHFND_FILL_REGL_BY_EHS_SUBST).
BAdI Methods
- GET_CHARACTERISTICS:
This method returns the properties and characteristics of the substances that are transferred. For each
characteristic, the method also returns a usage that is used to read data for that characteristic. Thus,
it is possible to read, for instance, the components with workplace control parameters with a
different validity area than other transferred data. For each characteristic, the method also returns
the node and the field of the chemical to which the data are transferred. Note that the only nodes
supported are those that are provided by the default implementation.
GET_SDS_DOCUMENT_PARAMETERS:
This method returns the parameters used to identify documents to transfer. It returns a list of triples
where each triple contains values for report category, validity area, and language. report Transfer of
Chemicals uses report category and validity area to determine generation variants. For each
determined generation variant and language, released and historic reports are transferred to the
chemical.
- GET_HITLIST_ID:
This method determines the Set of Hits - Group and the Set of Hits - Group Entry that is used for
transferring substance data. Note that only substances of the selected hit list are transferred.
- GET_IDENT_LISTING_CHM:
______________________________________________________________
SAP AG 233
______________________________________________________________
SAP System
This method determines the identification listing for transferring data like the name of the chemical
or the CAS number. Each position in the identification listing is transferred to corresponding field
of the chemical BO. The field assignment of the listing positions must be as follows: 1. Name of the
chemical
2. Internal names
3. IUPAC name
4. EINECS number
5. Molecular formula
6. CAS number
7. Synonyms
This means that the identifier configured at position 1 of the identification listing is being
transferred into the name of the chemical field in the chemical BO, the identifier configured at
position 2 is being transferred into the internal name, and so on.
- MAP_TO_CHEMICAL_TYPE:
This method maps phrase IDs of the specification database to the chemical type (fix values of
domain EHFND_CHM_NATURE) of chemical BOs.
- MAP_TO_HAZARD_CLASSIFICATION:
Chemicals have only one field for hazard class/hazard category. In the specification database, this
information is spread over multiple fields. This method maps the phrase IDs from up to 4
characteristics to one value for the hazard class/hazard category.
- MAP_TO_ACCURACY:
This method maps phrase IDs of accuracy characteristics, as well as accuracy operators of
compositions and numerical characteristics to values for the numerical accuracy fields in the
chemical.
- MAP_TO_COUNTRY:
Documents that are attached to chemicals have a country code and no validity area. This method
maps the validity area of a generation variant to a country code.
- ADJUST_NAMES_OF_CHEMICAL:
This method allows you to adjust the identifiers that are supposed to be transferred as name of the
chemical. Chemical names are language dependent and require a language code. In SAP EHS
Management as part of SAP ERP and Product Safety as part of SAP S/4HANA, it is possible to
enter identifiers without any language code. In this method, you can, for example, assign a default
language for those identifiers that do not have a language code or replicate it with different
languages codes.
______________________________________________________________
SAP AG 234
______________________________________________________________
SAP System
-
GENERATE_DOCUMENT_REFERENCE:
In the specification database, generated reports are usually report bodies; they are not completely
finished. It is still necessary to generate a final report. When reports are transferred from a
specification to a chemical, this generation step is also necessary. This method generates the final
report when a user wants to display a report body that has been attached to a chemical via the
transfer report for chemicals. This method also specifies the file format in which the final report is
generated.
The BAdI implementation BADI_EHFND_CHM_TRANSFER is delivered with the standard system.
Example
4 Business Add-Ins for Risk Identification
4 BAdI: Hazard Determination Methods for Chemicals
Use
use this BAdI to determine hazards for chemicals when identifying risks. This BAdI is called when
you add a chemical as agent in the risk identification process and apply a hazard determination
method.
Requirements
You have assigned hazards to hazard statements in in Customizing activity Specify Hazard Statements
and Assign Hazards.
Standard settings
______________________________________________________________
SAP AG 235
______________________________________________________________
SAP System
- GET_TAB_ID
The system returns the tab ID for possible parameters for the hazard determination method.
DTERMINATE_HAZARDS
The system determines hazards for chemicals based on hazard statements.
The BAdI implementation BADI_EHHSS_RAS_HDM_BAS_ON_CHM is delivered with the standard

system. This BAdI implementation determines hazards for chemicals based on hazard statements.
Activities
When defining customer-specific BAdI implementations, you can enhance the following filter values for
the hazard determination method:
- 01 = Manual
- 02 = Based on Hazard Statements
- Enhance the filter value range EHHSS_HAZ_DETERM_METHOD.

- Add new implementations to BADI_EHHSS_HAZ_DET_METHOD.
- Set the filter value for the new implementation.
- Enhance the value range of domain EHHSS_HAZ_DETERM_METHOD.
- Add a new tab to component configuration EHHSS_RAS_IDENTIF_CHM_DLG_DY_TAB with
the same Tab ID as the one you entered in method GET_TAB_ID.
- Insert FPM-UIBB that represents the parameters of the hazard determination method.
- To set the parameters of the hazard determination method, set the fields in the application controller:
CL_EHHSS_RAS_IDENTIF_CTRL-MS_CHEMICAL-HAZ_PARAMETER
CL_EHHSS_RAS_CHA_IDENTIF_CTRL- MR_PARAMETERS
- To apply the hazard determination method, raise an FPM Event with the ID
'HDM_APPLY'
Example
______________________________________________________________
SAP AG 236
______________________________________________________________
SAP System
-
- CL_BADI_EHHSS_HDM_BAS_ON_CHM
4 Business Add-Ins for Risk Analysis
4 BAdI: Risk Level Calculation
Use
You can use this BAdI to determine the risk value and the risk level for an identified risk.
The BAdI uses the method CALCULATE_RISK to determine the risk level:
- It calculates the risk value by using a mathematical operator to combine the risk scores of the
individual risk matrix dimensions:
- Severity
- Likelihood
- Exposure frequency
Note: If you use a graphical risk matrix, the BAdI automatically determines the risk values for all
possible combinations of risk scores that are included in the risk matrix.
- It determines the risk level that is specified for the calculated risk value in the Customizing activity
Specify Risk Levels.
Requirements
You have configured a risk matrix and specified risk levels for in the Customizing activities under
Environment, Health and Safety -> Health and Safety Management -> Risk Analysis -> Risk
Matrix.
Standard settings
The BAdI implementation EHHSS_RISK_LEVEL_CALC_IMPL is delivered with the standard system.

This BAdI implementation calculates the risk value by multiplying the risk scores that have been
specified for the individual risk matrix dimensions.
______________________________________________________________
SAP AG 237
______________________________________________________________
SAP System
4 BAdI: Calculation of Sampling Campaign Performance
Use
this BAdI to determine specific performance aspects of a sampling campaign, such as a percentage value
or a specific color to indicate the performance levels.
This BAdI is called when a performance value or a color indicating the sampling campaign performance
is displayed on the screen.
Standard settings
- CALC_CAMPAGIN_PERF_INDEX
This method calculates a percentage value representing the performance of a sampling campaign.
For details refer to the method documentation Calculate Percentage Value for Campaign
Performance.
- CALC_CAMPAIGN_PERF_INDEX_COLOR
This method determines the color to be displayed for a certain performance of a sampling
campaign.
For details refer to the method documentation Return Color for Campaign Performance.
BAdI implementations
The BAdI implementation BADI_EHHSS_CAMP_PER_CAL_IMPL is delivered active with the

standard system.
This BAdI implementation enables you to determine specific performance aspects of a sampling
campaign.
Activities

Example
______________________________________________________________
SAP AG 238
______________________________________________________________
SAP System
4 BAdI: OEL Adjustment to Shift Pattern
Use
use this BAdI to define adjustment methods for the adjustment of occupational exposure limits (OELs)
to shift pattern.
This BAdI is called whenever the exposure of a certain worker is to be compared to an OEL in order to
make the OEL actually comparable to the exposure.
Standard settings
- CALC_ADJ_OEL
For details refer to the method documentation Calculate Adjusted OEL Values for a Selected Shift
Pattern.
The following BAdI implementations are delivered active with the standard system:
- BADI_EHFND_SHFTADJ_DLYADJ
Adjustment of an OEL based on the daily working hours.
- BADI_EHFND_SHFTADJ_WKLYADJ
Adjustment of an OEL based on the weekly working hours.
- BADI_EHFND_SHFTADJ_CONSADJ
Conservative or worst case adjustment: The lowest OEL value from daily and weekly adjustment is
taken into account.
- BADI_EHFND_SHFTADJ_NOADJUST
No adjustment of an OEL needed/wanted.
The BAdI uses filter values that are specified in Customizing activity Specify Methods for OEL
Adjustment to Shift Pattern.
Activities

______________________________________________________________
SAP AG 239
______________________________________________________________
SAP System
Example
4 Business Add-Ins for Risk Treatment
4 Health Surveillance Protocols
4 BAdI: Person Determination for Recommended Health Surveillance

Protocols
Use
This Business Add-In (BAdI) is used in the Environment, Health, and Safety component. If you want
to provide person-specific recommendations of health surveillance protocols for a specific risk to an
integrated occupational health application, you can use this BAdI to determine all persons that are
exposed to the risk. After the jobs and locations of the risk have been determined by the BAdI
Determination of Health Surveillance Protocols (BADI_EHHSS_RAS_HSP), the BAdI uses the method
Determine Persons
(IF_BADI_EHHSS_RAS_HSP_PERS) to create a list of affected persons according to their job,
location, or similar exposure group (SEG) and transfers this information back to the BAdI
Determination of Health Surveillance Protocols.
Requirements
You have activated an implementation of the BAdI Determination of Health Surveillance
Protocols (BADI_EHHSS_RAS_HSP).
Standard settings

- BADI_EHHSS_RAS_HSP_PERS_LJ
This implementation determines the affected persons according to their jobs and locations:
- For job hazard analyses, it determines the persons that are assigned to the job and job location
of each job hazard analysis. Note that the implementation checks only the location that a job
hazard analysis has been performed for. It does not check for additional locations that have
been assigned to the job hazard analysis later.
______________________________________________________________
SAP AG 240
______________________________________________________________
SAP System
- For all other risk assessment types, it determines the persons that are assigned to the location
of the risk.
- BADI_EHHSS_RAS_HSP_PERS_SEG
This implementation determines the affected persons according to their SEG. If an SEG exists for
the location, job, or both job and location of the risk, it checks for all persons that are assigned to
this SEG.
Example
4 BAdI: Determination of Recommended Health Surveillance

Protocols
Use
use this BAdI to enable the automatic determination of recommended health surveillance protocols for a
specific risk in the health and safety management application. You can also use this BAdI to check
whether these recommendations apply to each person that is exposed to the risk, and to create a list of
person-specific recommendations that can be transferred to the integrated occupational health
application.
The BAdI uses the following methods:
- AUTOMATIC_PROPOSALS
This method determines the health surveillance protocols that are recommended for a risk
according to the recommendation criteria of each protocol.

It automatically assigns all determined recommendations to the risk that is selected in a risk
assessment.
The method is called when a user chooses the Recommend Automatically button on the Health
Surveillance Protocols tab while editing the controls of a risk assessment.
- DETERMINE_HSPROTOCOLS
This method creates a person-specific list of recommended health surveillance protocols for a risk.
After all persons exposed to a risk have been determined by using the BAdI Determination of Risk-
Related Person Assignment for Health Surveillance,the method checks whether the
recommendations apply to each person according to the recommendation criteria of each protocol.
This method is called within a background job that you schedule by using the Customizing activity
Schedule Jobs for Recommending Health Surveillance Protocols to transfer the recommended
health surveillance protocols to an integrated occupational health application.
Requirements
- You have activated an implementation of the Business Add-In BAdI: Occupational Health
Integration to enable integration with an occupational health application.
______________________________________________________________
SAP AG 241
______________________________________________________________
SAP System
Health, you have specified the risk assessment types that you want to integrate with the
occupational health application.
Standard settings

The BAdI implementation BADI_EHHSS_RAS_HSP is delivered with the standard system. It
determines the person-specific recommendations of health surveillance protocols as follows:
1. It uses the method AUTOMATIC_PROPOSALS to determine the health surveillance protocols that
are recommended for a risk according to the following recommendation criteria:
- Agent assigned to the risk
- Risk level of the risk
- Value type of the agent
- Exposure rating of the risk
2. For each person that is exposed to the risk, it uses the method
DETERMINE_HSPROTOCOLS to check whether the recommendations apply according to the
following recommendation criteria:
- Gender of the person

- Age of the person
Example
Use
health system.
______________________________________________________________
SAP AG 242
______________________________________________________________
SAP System
Requirements

Standard settings
- READ_HSPROTOCOLS
The system reads health surveillance protocols used in the integrated occupational health system
and provides a list of available protocols.
The health surveillance protocols are selected by date, language, and health surveillance
protocol type.
integrated occupational health system and provides a list of all available descriptions. The
language-dependent descriptions are selected by date and health surveillance protocol type.
language.
- READ_HSPROTOCOL_TYPE_DESC
Health, and Safety.
The BAdI implementation BADI_EHFND_BO_HSP_PROXY is delivered with the standard system.

This BAdI implementation provides the integration into the occupational health function of SAP EHS
______________________________________________________________
SAP AG 243
______________________________________________________________
SAP System
Example
4 Business Add-Ins for Risk Monitoring and Review
4 BAdI: Calculation of Control Effectiveness
Use
automatically calculate whether a control is effective based on the answers given to control inspection
questions.
The BAdI uses the method CALC_CNTR_EFFECTIV to calculate the control effectiveness using the
following logic:
- If 100% of the answers are Yes, the control is Effective.

- If more than 75% of the answers are Yes, the control is Improvable.
- If fewer than 75% of the answers are Yes, the control is Ineffective.
Requirements
You have specified effectiveness values in the Customizing activity Specify Control Effectiveness.
Standard settings
The BAdI implementation BADI_EHHSS_CINSP_RESULT_CALC is active in the standard system.
Example
4 BAdI: Automatic Control Evaluation
Use
this BAdI to provide automatic evaluation of the effectiveness of controls. In the application, the user can
choose to evaluate the effectiveness automatically instead of manually entering the effectiveness or
requesting a control evaluation be performed.
Requirements
______________________________________________________________
SAP AG 244
______________________________________________________________
SAP System
You have specified effectiveness values in Customizing activity Specify Control Effectiveness for
Environment, Health, and Safety under Health and Safety Management.
Standard settings

The BAdI has the two following exporting parameters:
- Date of effectiveness evaluation (EHFND_DATE)

- Effectiveness code (EHHSS_CTRL_EFFECTIVN_CODE)
Activities
Once you have created an implementation of this BAdI, the system displays the Create and Evaluate
Automatically pushbutton on the screen for evaluating controls.
4 BAdI: Creation of 1:1 Copy of Risk Assessment
Use
this BAdI to copy data from an existing risk assessment that is already closed to a follow-up risk
assessment. The BAdI is called when you need to update the effectiveness in a closed risk assessment. If
the new value is no longer effective and the risk assessment is closed, the new value will be set in the
follow up risk assessment created by the BAdI.

- Assessment team
- Observed person
- Job location
- Job steps
- Risk data
- Identified risks
______________________________________________________________
SAP AG 245
______________________________________________________________
SAP System
- Impacts
- Analysis data
Note: The analysis data is a copy of the original data with the exception of the OEL values in
the risk, which are obsolete and not copied.
existing controls for the risk
- Documents
Standard settings
The BAdI implementations EHHSS_RAS_COPY_NO_CHANGES_IMPL is delivered with the standard

system and is active by default.
4 BAdI: Creation of Follow-Up Revisions of Risks
Use
this BAdI to create follow-up revisions of risks and copy data from the predecessing risk revision to the
follow-up risk revision. The BAdI is called when you select risks and assign them to risk assessments
for follow-up.
The BAdI uses the method CREATE_RISK_FOLLOW_UP to copy all relevant data. It creates a new
risk revision for each risk that is copied to the assigned follow-up risk assessment. This allows you to
edit risk data in the assigned risk assessment without changing the data that was originally recorded for
the selected risk.
In the standard delivery, the BAdI copies the following data to the follow-up risk revision:
- Risk data
- Impacts
- Analysis data
Note: With the implementation of BADI_EHHSS_RISK_FOLLOW_UP, the system does not copy
analysis data for an initial risk. Instead, it uses the analysis data from the residual risk for the initial
risk data in the follow-up risk assessment.
- Controls (including control effectiveness values) are copied to the existing controls for the risk.
- Health surveillance protocols are copied to the health surveillance protocols related to the existing
controls for the risk.
- Documents
______________________________________________________________
SAP AG 246
______________________________________________________________
SAP System
Standard settings
The BAdI implementations BADI_EHHSS_RISK_FOLLOW_UP is delivered with the standard system

4 BAdI: Data Transfer to Follow-Up Assessment
Use
this BAdI to copy data from an existing risk assessment to a follow-up risk assessment. The BAdI is
called when you create a follow-up assessment, for example, to reassess identified risks after a regulation
has changed.
The BAdI uses the method COPY_ALL_RISK to copy all relevant data. It creates a new risk revision
for each risk that is copied to the follow-up assessment. This allows you to edit risk data in a follow-up

- Assessment team
- Observed person
- Job location
- Job steps
- Risk data
- Identified risks
- Impacts
- Analysis data
Note: For the implementation EHHSS_COPY_ASSESSMENT_IMPL, the system does not
copy any analysis data for initial risk. Instead, it uses the analysis data from the residual risk
for the initial risk data in the follow-up assessment.
existing controls for the risk.
______________________________________________________________
SAP AG 247
______________________________________________________________
SAP System
- Documents
Standard settings
The BAdI implementations EHHSS_COPY_ASSESSMENT_IMPL is delivered with the standard system

4 Business Add-Ins for Integrated Notifications
4 BAdI: Creation and Completion Check of Integrated Notifications
Use
When you create a maintenance notification task in incident management, a default method takes
the information from the maintenance notification and then sends it to Plant Maintenance (PM) for
further processing. However, if you specified custom fields for a notification, the method in the standard
delivery cannot handle the information in these fields and thus cannot send the entire notification for
processing.
Standard settings

BAdI Methods
parameters:
Import Parameters

______________________________________________________________
SAP AG 248
______________________________________________________________
SAP System
Export Parameters
The method contains default implementation and allows you to implement your own business
logic to get the completed notifications from the corresponding functional areas and set their status
in incident management. The method includes the following import and change parameters:
Import Parameters
Change Parameters
4 Business Add-Ins for Health and Safety Management Fiori Apps
4 BAdI: Extend Data of Gateway Service of Retrieve Safety Information App
Use
BAdI to provide values for custom OData attributes.
Standard settings
BAdI Methods
- FILL_CHM_AT_LOC_EXT
This method is used to add custom fileds in the OData service.
The method includes the following import and change parameters: Import
Parameter
- IO_CHM_REV_NODE - Custom BOPF node that is used to access the sub-nodes.

Change Parameters
- CS_RESULT_CHEMICALS - Gateway proxy structure for a chemical at location
This BAdI definition uses the IF_EHHSS_BADI_SAFETY_INFO_DPC interface.
______________________________________________________________
SAP AG 249
______________________________________________________________
SAP System
4 BAdI: Extend Model of Gateway Service of Retrieve Safety Information App
Use
BAdI to add custom attributes to an existing application OData service.
Standard settings
BAdI Methods
- ENHANCE_GW_SERVICE_ENTITY_MPC
This method is used to enhance the OData model with new properties in existing entity sets.
The method includes the following import parameters:
Import Parameter
- IO_ENTITY_TYPE - Interface that represents a script-based OData entity type
- IV_ENTITY_TYPE_NAME - Name of the OData entity type This BAdI definition

uses the IF_EHHSS_BADI_SAFETY_INFO_MPC interface.
______________________________________________________________
SAP AG 250

Environment, Health and Safety PDF

Uploaded by

Copyright:

Available Formats

You might also like

Environment, Health and Safety PDF

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

Environment, Health and Safety PDF

Uploaded by

Copyright:

Available Formats

Copyright(c) 2018 by Nixon Vunganai.

All rights reserved.

FOUNDATION FOR EHS 5

BADI: INTEGRATION OF FINANCIAL TRANSACTION OBJECTS 89

Foundation for EHS

Specify General Settings

- Default Language Key

The standard system is delivered with examples.

1. Check the existing examples and adapt them as required.

Specify Number Range Intervals for Foundation

- For Environment, Health, and Safety:

1. Specify a number range object and choose Number ranges.

Specify Active Languages

The standard system is delivered with examples.

1. Check the existing examples and adapt them as required.

Specify Field Control

The standard system is delivered with examples.

1. Check the existing examples and adapt them as required.

- To adapt the UI for a specific regulatory region

The standard system is delivered with examples.

- Specify Regulations under Incident Management

Create Regulatory Lists and Customer Lists

The standard system is delivered with examples.

- For Environment, Health, and Safety:

The standard system is delivered with the following:

Dynamic Creation of Statements

Assign Assistant Classes to Business Objects

The standard system is delivered with examples.

1. Check the existing examples and adapt them as required.

Enable BO Fields for Dynamic Creation of Statements

To create new entries, proceed as follows:

Specify RFC Destination for System Callback

Maintain Archive Retrieval Settings for Workflows

You have completed the automatic workflow customizing in transaction SWU3.

To define the workflow retrieval settings:

1. Open transaction SARI or execute this Customizing activity.

Perform Automatic Workflow Customizing

Specify Process Definitions

- For Environment, Health, and Safety: Perform Automatic Workflow Customizing

- For Environment, Health, and Safety: Extend and Adapt Process

The standard system is delivered with examples.

1. Check the existing examples and adapt them as required.

- Component: Health and Safety

- Process Variant: OFFLINE

- PCO Class Name: CL_EHHSS_PCO_INC_INQUIRY

Activate Linkage for Scheduled Processes

For the following object, activate the event type linkage:

- You have experience using SAP Business Workflow.

The standard system is delivered with examples.

1. Check the existing examples and adapt them as required.

BAdI: Create and Initialize PCBOs

You have made settings in the following Customizing activities:

- For Environment, Health, and Safety:

This BAdI does not have a default implementation.

Checks and Tools

You have performed the following Customizing activities:

- Perform Automatic Workflow Customizing

- Perform Automatic Workflow Customizing