configuration-sap econfiguration-sap ehs managemenths management

8/10/2019 Configuration-SAP EConfiguration-SAP EHS ManagementHS Management

1/116

SAP EHS Management

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 fortranslating 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 internationalISO 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.


2/116


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 fortranslating 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 internationalISO standard.

Standard settings


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 Active Languages

Use

In this Customizing activity, you can define the available target languages for translating free text fields in the system. If youwant to translate a free text, you can choose one of these defined languages and then translate the text into the chosenlanguage.

Standard settings


3/116


Activities


2. If necessary, define additional entries.

A unique key must be assigned to each entry.

Specify Field Control

Use

In this Customizing activity, you can specifyfield controlfor business objects in the SAP EHS Management (EHS-MGM)component.

You can use field control to adapt the user interface to specific conditions of a data record. You specify these conditions andhow the system adapts the UI on the node level of a business object. You can, for example, set up field control to make specificfields visible and editable on the user interface depending on the country or region of the data record. Field control is possible onall nodes of a business object and for all properties of the node. You can also specify more than one profile to accommodateeach relevant set of conditions of a data record.

Prerequisites

You are familiar with the modelling and structure of the business objects of SAP EHS Managementin the Business ObjectProcessing 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

1. Check the existing examples and adapt them as required.2. If necessary, define additional entries.

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 settingsyou make for the following fields:

o Authorization-Based Profile

o Authorization Check Result


4/116

o Function Class

o Node Attribute Value

(The system determines if field control applies in the order that the above fields are listed here.)If you create more than one profile for a node, you can make settings for themerge strategyfor each profile.4. After creating the profile, you can define the property settings for the business object node in the subdialogs. Theseare settings that control the behavior and appearance of the user interface. In this step, you can also specify how topropagate the settings to subnodes.

Example

You use SAP EHS Management 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 todisplay the Privacy CaseandAdditional Criteriaradio buttons when you record data about injuries/illnesses that occurred in theUnited States. Otherwise, these fields are not displayed.

Field Control for Merge StrategyDefinitionSpecifies the strategy for merging profiles with different values specified for the attribute, node, action and associationproperties so that only one profile is returned and used for field control.Use

You can specify, for example, that disabled values always win (pessimistic), or that enabled values always win(optimistic).The system gives priority to the optimistic profile when there is more than one profile.By default, the merge strategy is pessimistic.

Create Regulations

Use

In this Customizing activity, you can create regulations for business objects used in SAP EHS Management. You can use

regulations as the conditional basis for applying field control settings and to control the forms available to the data record. Thisway, the system adapts a data record automatically according to a specific regulation and helps you fulfill regulatoryrequirements.

If your organization operates in countries and regions with specific regulatory requirements, for example, for managing incidents,you createthe regulations in this activity.

If your organization has internal policy, for example, for managing incidents, you create the internal policy as a regulation in thisactivity.

Standard settings


5/116


Note that you must specify these regulations further for use in incident management. For more information, see the CustomizingactivitySpecify Regulations.

Activities




Further information

For more information about field control, see Customizing activitySpecify Field Control

Specify Document Storage

Use

SAP EHS Management (EHS-MGM)uses theContent Management Serviceto store documents, for example, attachmentsand generated PDF reports.

The connection to the Content Management Service is specified and implemented by the attachment folder (ATF) of thebusiness object (a reusable object for the BOPF environment in the SAP_BS_FND software layer).

In this activity, you can learn about setting up attachment types and assigning these to attachment schemas. An attachmentschema may be assigned for a given business object (BO) node that uses the dependent object attachment folder.

Standard settings

The standard system is delivered with settings that use the content repository BS_ATF_DB_REPOSITORY and the contentcategory BS_ATF_DB to store documents in the database.

The standard system is also delivered with an alternative configuration to connect to a separate file server. To achieve this, theattachment schema needs to be assigned to the content category BS_ATF. This content category uses the content repositoryBS_ATF_CONTENT_SERVER.

Activities

Ensure that the settings for the Content Management Service are correct in Customizing for SAP NetWeaverunder KnowledgeManagement -> Settings in the Knowledge Warehouse System -> Content Management Service.

Ensure that the settings for the attachment schema are correct for the SAP EHS Managementbusiness objects in Customizingfor Cross-Application Components in activityMaintain Attachment Type Schema.

If you want to create your own attachment schema, you must assign it to the respective ROOT nodes of the three deliveredbusiness objects.

Further information


6/116

For more information about the Content Management Service, see SAP Library for SAP NetWeaver 7.0 EHP 2 on SAP HelpPortal at http://help.sap.com under SAP Netweaver Library -> SAP NetWeaver by Key Capability -> Application Platform by KeyCapability -> Business Services -> Knowledge Provider (BC-SRV-KPR) -> Content Management Service (BC-SRV-KPR).

Foundation for EHS Management->Process Foundation

Basic Settings

Perform Automatic Workflow Customizing

Use

In this Customizing activity, you can perform automatic customizing for workflows. The activity is mandatory if you use theprocesses of the SAP EHS Management (EHS-MGM)component. If you do not perform this activity, theprocess foundationcannot support your business processes.

Activities

Select the top node of the first section and choose the Perform Automatic Workflow Customizingpushbutton or F9. Perform thisstep for all subsequent sections.

To run EHS Management, ensure that the following settings were made:

Maintain Runtime Environment: all settings

Maintain Definition Environment:

o Check Number Ranges

Maintain Additional Settings and Services:

o Maintain Standard Domain for Internet Mail


7/116

o Activate Send to Objects and HR Objects

o Maintain Demo and Verification Environment

Classify Tasks as General: all settings

Guided Procedures:

o Maintain Generation of Standard Tasks

o Classify Generic Standard Tasks as General

When you choose to perform automatic workflow customizing, only those activities that currently have the error status areexecuted automatically. If an activity still has the error status after performing automatic workflow customizing, you may need tomake additional settings, and peform automatic workflow customizing again or manually perform customizing.

Further information

For more information, see SAP Help Portal -> ERP Central Component Enhancement Package 4 -> SAP NetWeaver Library ->SAP NetWeaver by Key Capability -> Application Platform by Key Capability -> Business Services -> SAP Business Workflow ->Reference Documentation -> Workflow System Administration.


8/116


9/116

Requirements

You have set up the workflow system in the Customizing activityPerform Automatic Workflow Customizingfor Foundationfor EHS Management.

If you want to extend your processes with additional functionalities in the SAP Business Workflow, you have implemented acustomer-specificPCOclass to handle the process. For more information about extending or changing the PCO class, seeCustomizing activityExtend and Adapt Processin Foundation for EHS Management.

Standard settings


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.3. If necessary, select the Exclude checkbox to exclude a process from process monitoring and analysis.

BAdI: Create and Initialize Process Control Objects (PCBOs)

Use

This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM)component. You can use this BAdI toimplement customer-specific logic to adapt the processes in the system. You can use this BAdI, for example, if your organizationmust comply with regulatory requirements in more than one country or region. You can create a variation of the process for aspecific country or region.

The PCBO creation BAdI is called each time the system creates aprocess control business object(PCBO).

Requirements


10/116

You have specified process definitions in the Customizing activitySpecify Process Definitionsfor Foundation of SAP EHSManagement.

You have performed a consistency check without errors in the Customizing activityList Configured Processesfor Foundationof SAP EHS Management.

Standard settings

This BAdI does not have a default implementation.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You thenchoose one of them by choosing Create, and continue as follows:

1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.

The system displays the initial screen for creating Business Add-In implementations.

2. On this screen, enter a short description for your implementation in the Implementation Short Textfield.

3. If you choose the Interfacetab, you will notice that the system has populated the Name of the Imp lementing Classfield automatically, by assigning a class name based on the name of your implementation.

4. Save your entries and assign the Add-In to a package.

5. To edit a method, double-click its name.

6. Enter your implementation code between the method ~.and

endmethod.statements.

7. Save and activate your code. Navigate back to the Change Imp lementationscreen.

Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not

perform the following step:

8. Choose Act ivate.

When the application program is executed, the code you created is run through.

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 scheduledprocesses.

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. Byactivating the event type linkage, you allow a central user with batch administration authorizations (WF-BATCH) to schedule andtrigger 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


11/116


12/116

List Configured Processes

Use

In this Customizing activity, you can display a list of the process definitions in the SAP EHS Management (EHS-MGM)component. From this list, you can view the status, the instances, and the technical information of process definitions. This helpsyou ensure that the process definitions are configured correctly.

Requirements

You have specified process definitions in the Customizing activitySpecify Process Definitionfor Foundation for EHSManagement.

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 displaysthe results of the process definition check in the reportR_EHFND_WFF_PROCDEF_CHECK.

Choose the List icon to display a list of the instances of the specified process in the reportR_EHFND_WFF_PROCESS_LIST.


13/116

Choose the Info icon to display technical information about the selected process in the reportR_EHFND_WFF_PROCDEF_INFO.

Schedule Jobs for Process Statistics

Use

In this Customizing activity, you can schedule a report to collect statistical information about processes on a regular basis. Thisinformation is used by the workflow reporting and analytics functions in the SAP EHS Management (EHS-MGM) component.

This activity is mandatory if you use the EHS Management processes. If you do not perform this activity, theprocessfoundationcannot collect all of the information about the processes, which can result in problems with the workflow reportingand analytics functions.

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_WFF_UPDATE_STATISTICS.

2. Schedule the job to run at regular intervals, such as once a day.


14/116

Extend and Adapt Processes

Use

In this activity, you can learn about how to extend and adapt theprocess foundationin SAP EHS Management (EHS-MGM)tosuit 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 Builderthat 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 thecorresponding tasks in the workflow inbox. For more information, see Notebelow.3. Activate the event binding for the CREATEevent of the corresponding PCO class.


15/116

4. Disable the event linkage for the old workflow template to prevent creating two workflow instances when the eventoccurs.

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 intransaction 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 Customizing activitySpecify Process Definitionfor Foundation for EHS Management.

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 oroverwrite 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 Customizing activityBAdI: Create and Initialize Process ControlObjects (PCBOs)for Foundation for EHS Management.

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 extendingthe abstract base class for the PCO class CL_EHFND_WFF_ROOT_PCO.

After you create the PCO class, enter it in the activitySpecify Process Definitionfor the relevant process definition.

Note

SAP EHS Managementuses the POWL-based inbox. If you adapt processes and the corresponding workflow templates, youmust configure the tasks in the workflow inbox in Customizing for Cross-Application Componentsunder Processes and Tools forEnterprise Applications -> Inbox.

See also the corresponding process component to obtain the correct application ID and POWL type for the workflow inbox.


16/116

Specify Types

Use

In this Customizing activity, you can specifytypesfor actions and notifications.

When you create an action or a notification in the SAP EHS Management (EHS-MGM)component, you can choose the typefrom the values you specify in this activity.

Standard settings


Activities


If you want the system to display a value on the user interface automatically, you can select the Defaultcheckbox for

the corresponding entry.



Specify Subjects

Use

In this Customizing activity, you can specifysubjectsfor actions and notifications.


17/116

When you create an action or a notification in the SAP EHS Management (EHS-MGM)component, you can choose the subjectfrom the values you specify in this activity.

Requirements

You have made the settings for Customizing activity Specify Typesfor Foundation for EHS Management.

Standard settings


Activities






Specify Effectiveness

Use

In this Customizing activity, you can specify theeffectivenessfor actions and notifications.

When you create an action or a notification in the SAP EHS Management (EHS-MGM)component, you can choose theeffectiveness from the values you specify in this activity.

Standard settings


Activities







18/116

Specify Protection Goals

Use

In this Customizing activity, you can specify theprotection goalsfor actions and notifications.

When you create an action or a notification in the SAP EHS Management (EHS-MGM)component, you can choose theprotection 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 SAP EHS Management(EHS-MGM)component. The template stores the standard values for the action or notification. During processing, you canchoose an action or a notification from the template. The system automatically retrieves the values for the following fields fromthe template and fills them in on the user interface:

Type

Subject

Category

Notification

Description

You can use templates to speed up the process of creating actions and notifications.

Requirements

You have made the settings in Customizing for Foundation for EHS Managementfor the following activities:


19/116

Specify Types

Specify Subjects



Standard settings


Activities




Note that you must scroll all the way to the right to see all of the settings for a template.

BAdI: Define Process Steps

Use

This Business Add-In (BAdI) is used in the SAP EHS Management (EHS-MGM)component. You can use this BAdI to see thepersons that are involved in the process step of a given work process.

The process can contain the following people:

Responsible Person

Implementor

Approver

In thecomponentsof SAP EHS Management, there are specific processes that involve action. In these processes, workflowtasks 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:

EHFND_ACTION_BADI

The BAdI is filter-dependent and not designed for multiple use.

Activities


20/116

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You thenchoose one of them by choosing Create, and continue as follows:

1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.

The system displays the initial screen for creating Business Add-In implementations.

2. On this screen, enter a short description for your implementation in the Implementation Short Textfield.

3. If you choose the Interfacetab, you will notice that the system has populated the Name of the Imp lementing Class

field automatically, by assigning a class name based on the name of your implementation.

4. Save your entries and assign the Add-In to a package.

5. To edit a method, double-click its name.

6. Enter your implementation code between the method ~.and

endmethod.statements.

7. Save and activate your code. Navigate back to the Change Imp lementationscreen.

Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not

perform the following step:

8. Choose Act ivate.

When the application program is executed, the code you created is run through.

Specify Forms

Use

Forms contain data for a business object. You can use forms, for example, in legal and internal reporting or as inquiryquestionnaires.

In this Customizing activity, you can specify and configure forms to integrate them into the application. You can also assign thelanguages in which the forms are available. Each form can exist in multiple languages. The available languages are determined


21/116


22/116

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 acomponent.

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 groupinstead 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 for SAP EHS ManagementunderSpecify ADS Forms,you have defined the available forms.

Standard settings


Activities

1. Define a logical name and a description for theform group.

2. Assign a component for the form group.

3. Select a form group and chooseAssign Forms to Form Groups.

4. Assign theformsand select adefault form.


23/116

Specify Destinations for Integration

Use

In this Customizing activity, you can specify destinations for integrating other SAP components into the SAP EHS Management(EHS-MGM)component. You can access the data in those components directly on your local system or using an RFCconnection 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

Customer Service

Human Resource Management

Plant Maintenance

Quality Management

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 thelocal system only. For more information about the data that you cannot access via remote access, see Notesbelow.

Requirements

You have defined RFC connections of connection type 3(ABAP connection). To check and define RFC connections, on the SAPEasy Accessscreen, choose Tools -> Administration -> Administration -> Network -> RFC Destinations. You can specify acustomer-specific name for the RFC destination.

You have ensured the following:

You are using SAP ERP 6.0 (Basis 700) or higher for the remote system of your Quality Managementsystem.


24/116

You are using R/3 Enterprise 4.70 Extension Set 2.00 (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 and for PM notifications 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 onthe 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 datarequired on the local system and the table or object where it is located:

Data Required in Local System Table/Object

Business partner roles Tables TB003, TB003T

Plants and plant descriptions

Material and material descriptionMaterial number and material description from the material

masterCurrencies and exchange rates

Region texts Table T005U

Country texts Table T005T

Language texts Table T002T

Notification types for PM, QM, and CS 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 Infotype 1039 and tables T77DB, T77DT, T77ED, T77ET

Organizational data, including organizational units and persons inPA-OS Table T554S

Note that to make organizational data from PA-OS available in the local system, you can distribute the relevant HR master databetween the PA-OS system and the EHS-MGM system. However, since the EHS-MGM applications only require specific PA-OSdata, a distribution limited to the basic infotypes is sufficient. The distributed organizational data cannot be changed from theEHS-MGM applications as the system settings only allow read access.

The assignment of a user to employee (infotype 0105) for workflows must be done in the HR system. The users themselvesmust be maintained in the local system.


25/116

Specify Notification Types

Use

In this Customizing activity, you can specify thenotification typesto use in the SAP EHS Management (EHS-MGM)component. You must specify the notification types here in order to choose the following notification categories later in theapplication:

Quality notifications

Maintenance notifications

Service notifications

Requirements

You have defined notification types that you want to use in SAP EHS Managementin the Customizing activityDefineNotification Typesfor Cross-Application Components.

You have specified destinations for the integration of the Quality Management (QM), Plant Maintenance (PM), and CustomerService (CS) components in the Customizing activitySpecify Destinations for Integrationfor Foundation for EHSManagement.

The following requirements apply only to the notification types that you want to use in SAP EHS Management:

1. You have not defined any allowed changes for the desired notification types in the Customizing activityAllowed

Change of Notification Typefor Cross-Application Components.

2. You have ensured that the desired notification types contains tasks in the Customizing activityDefine Screen

Templatesfor Cross-Application Components. For each action or notification in SAP EHS Management, 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:

o The desired notification types do not contain any mandatory fields in the Customizing activityDefine ScreenTemplatesfor Cross-Application Components. If you have specified mandatory fields that do not exist in SAPEHS Management, the user cannot create a notification and receives an error message.

o Fields that you want to be mandatory exist in SAP EHS Management, are visible on the user interface, and areset as mandatory in the Customizing activitySpecify Field Controlfor Foundation for EHS Management.

4. You have ensured that the desired notification types have internal (and not external) number range assignments.

Standard settings


26/116


Activities




Specify Number Range Intervals for Location ID

Use

A unique number is assigned to each record created during processing in SAP EHS Management. In this Customizing activity,you can definenumber rangeintervals for the location ID.

Standard settings

The standard system is delivered with a predefined set of intervals for the location ID number range.

Activities

1. Display the existing number range intervals for the location ID.

2. To define a number range interval for internal number assignment, enter the value IE.


27/116

3. Specify the limits of the number range interval. The individual number range intervals must not overlap.

4. If the number range interval is intended for external number assignment, set the Extindicator.

5. Save your changes.

Enable / Disable PM Integration

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.

Once the PM integration has been enabled and used, that is, there are locations linked to a technical object in PM, you cannotdisable the integration. Note that this setting does not affect other points of integration with PM in the application.

Configure Periodical PM Synchronization

Use

In this organizational activity, you can learn about configuring a background job to synchronize master data when you integratelocationsfrom the Plant Maintenance (PM)component.

Note that you also synchronize the data of individual locations when you open the location's master data maintenance screen orlink it to a technical object.

Requirements

You have enabled PM integration in Customizing activityEnable/Disable PM Integration.

You have linked locations to PM technical objects.

Activities

1. Ensure that you have sufficient authorizations to read from the PM system and to update locations.

2. Schedule report R_EHFND_SYNCEAM_LOCATION 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 that the background job queries all integrated technical objects for changes. Depending on the number of objects that areintegrated, this may create additional load for the SAP EHS Management and PM system.

Further information

For more information about scheduling background jobs, see SAP Help Portalat http://help.sap.com -> Background Processing-> Job Scheduling Explained-> Scheduling Background Jobs.


28/116

Specify Authorization Groups

Use

In this Customizing activity, you can defineauthorization 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 ascribeto the authorizations for the location.

Standard settings


Activities




Specify Location Types

Use

In this Customizing activity, you can define the type oflocation.

You can use the location type to search for a location.

Standard settings


Activities





29/116

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 sidepanel. 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 locationaddress.

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 fieldsentered 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 mostcases, 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 displayedautomatically.

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=


30/116

The tag will be automatically completed with the current location's corresponding address string.

Further information

For more information about configuring Web Dynpro CHIPs and the Web Dynpro Side Panel, see SAP Help Portal athttp://help.sap.com -> Web Dynpro for ABAP-> Web Dynpro ABAP: Development in Detail ->Advanced Concepts-> WebDynpro ABAP Page Builder-> and the following topics:

Enhancing Web Dynpro Applications with a Side Panel

Creating Side Panels

Creating CHIPs

Incident Management

Configure Foundation for EHS Management

Use

Before performing the Customizing activities under Incident Management, you must first process Customizing for the Foundationfor EHS Management (EHS-MGM-FND)component. Below, you will f ind information about the foundation Customizing activitiesand their relevance to incident management.

General Configuration and Sett ings for Bus iness Objects

In incident management, you can enter texts manually, translate these texts into other languages, and enter amounts in a givencurrency. For more information, see the following Customizing activities for Foundation for EHS Management:


Specify Active Languages

You can customize the business objects used in incident management to usefield control,support you in fulfilling regulatoryrequirements, and store attached documents. For more information, see the following Customizing activities for Foundation forEHS Management:

Specify Field Control

Create Regulations

Specify Attachment Type Schema

Process Foundat ion


31/116

You can customize theprocess foundationto support your incident-specific processes. For more information, see the followingCustomizing activities for Foundation for EHS Management:

Specify Process Definitions

BAdI: Create and Initialize Process Control Objects (PCBOs)

Extend and Adapt Processes

Once you have configured processes for incident management, you can perform checks on the system, display the configuredprocesses, and collect statistics about your processes. For more information, see the following Customizing activities forFoundation for EHS Management:

Check Configuration of Workflow System

List Configured Processes

Schedule Jobs for Process Statistics

Act ions

During incident recording, you can specifyactionsand notifications in response to incidents, or to prevent future incidents fromoccurring. In Customizing, you can configure the settings for actions and notifications. For more information, see the followingCustomizing activities for Foundation for EHS Management:

Specify Types

Specify Subjects



Specify Templates

BAdI: Define Process Steps

Print Forms and Interactive Forms

Forms necessary for recording incident details and reporting incidents are integrated into the incident recording process. Youcan configure the available forms and their grouping. For more information, see the following Customizing activities forFoundation for EHS Management:

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 TimeManagement (PT), materials from Material Management (MM), and notification types from Cross-Application Components. Formore information, see the following Customizing activities for Foundation for EHS Management:

Specify Destinations for Integration


32/116

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 Contractual Relationships

Locat ions

You can uselocationsin incident management to describe where an incident occurred. For more information, see the followingCustomizing activities for Foundation for EHS Management:

Specify Number Range Intervals for Location ID

Enable / Disable PM Integration

Configure Periodical PM Synchronization

Specify Authorization Groups

Specify Location Types

Configure Embedded Search

Use

In this organizational activity, you can learn about using theEmbedded Searchservice in the SAP EHS Management (EHS-MGM) component.

Requirements

You have the SAP_ESH_LOCAL_ADMIN role assigned to your user.

Activities

If you want to use the NetWeaver Enterprise Search, you must first make the general settings in Customizing for SAPNetWeaverunder Search-> Embedded Search.

To activate the search function, you need to make the following additional configurations:

1. Create a search object connector from the EHHSS_BO_INCIDENT template in EHS Management.

2. Schedule indexing for the search object connector as follows: for the object types EHHSS_BO_INCIDENT,

USER_AUTHORITY, and EHFND_TEXT_COLLECT, create real-time indexing. All other object types contain

Customizing data and only need to be indexed as required, for example, for scheduling indexing once a week or for a

manual start.

Further information

For more information about SAP NetWeaver Enterprise Search, see SAP Help Portal at http://help.sap.com-> SAP NetWeaverEnterprise Search.


33/116

Specify Number Range Intervals for EHS Management

Use

A unique number is assigned to each record created during incident recording in SAP EHS Management. The appropriatenumber rangeobject determines the number automatically by the system.

In this Customizing activity, you can define number range intervals for the following number range objects:

EHFNDACTIDAction Identifier

EHFNDLCNIDLocation Identifier

EHFNDPSEIDProcess Setup ID

EHFNDRPTIDReport ID

EHHSSCASIDPerson Injured External Case ID

EHHSSINCIDIncident Management Identifier

EHHSSPIID ID for initial personsThis is required for PERID conversion.

Standard settings

The standard system is delivered with a predefined set of intervals for the number range objects mentioned above.

Activities

1. Specify the object for which you want to define a number range interval.

2. Display the existing number range intervals.

3. To define a number range interval for internalnumber assignment, enter the value IE.

4. Specify the limits of the number range interval. The individual number range intervals must not overlap.

5. If the number range interval is intended for external number assignment, set the Extindicator.

6. To transport the number range interval, select Interval -> Transport.

Caution

When you transport the newly-defined number range intervals, all existing intervals are deleted so that only the new numberrange intervals are available in the target system. The number status, however, is saved. That is, numbers are always assigned

sequentially. The next assigned number follows on from the number assigned to the object before the transport.

Specify Regulations

Use

In this Customizing activity, you can specify which regulations apply to a certain incident group, incident category, region, andcountry.

The system uses these settings to provide the regulatory information for processing the incident data records that have thespecified group, category, country and region.


34/116


35/116

Requirements

You have specified processes for the health and safety (HSS) component in the Customizing activitySpecify ProcessDefinitionsfor Foundation for EHS Management.

You have checked the processes by implementing the Customizing activityList Configured Processesfor Foundation for EHSManagement.

Standard settings


The standard system is delivered with settings for a fatality notification functionality. If you want to use this functionality, do notmake changes to the current process definition for the incident lifecycle process in the Customizing activity Specify ProcessDefinitions. When a fatality is recorded in incident management, this functionality raises the event FATALITY_OCCURRED ofthe PCO in the incident lifecycle process (CL_EHHSS_PCO_INC_LC). The workflow retrieves the people to be notified, and thesystem 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

500037 - EHHSS_ACT_CS CL_EHHSS_PCO_INC_ACTION_CS

500038 - EHHSS_ACT_QM CL_EHHSS_PCO_INC_ACTION_QM

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:


36/116

You can change the process flow directly in the workflow template (in the Workflow Builder), or copy the deliveredtemplate 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 Actionsfor Cross-Application Components.

3. Add the new tasks to the workflow inbox configuration in the Customizing activityAssign Task IDs to POWL Typesfor Cross-Application Components. Enter the application ID EHHSS_INBOXand the POWL type

EHHSS_INBOX_TYPEfor 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:

o Implement the logic directly in the PCO method.

o Implement the logic in a BOPF action of the corresponding process control business object (PCBO). Note: thisis the architecture that SAP EHS Managementfollows.

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 activityConfigure Process Definitionsfor Incident Management.

You can use the dispatcher workflow to react to changes in the incident with an automatic notification. To add to thecurrent changes that trigger a notification via the dispatcher process, start the dispatcher workflow and extend theworkflow template as required.

Configure Process Definitions

Use

In this Customizing activity, you can configure the processes used in the incident management application of the SAP EHSManagement (EHS-MGM) component.

Requirements

You have specified processes for the health and safety (HSS) component in the Customizing activitySpecify ProcessDefinitionsfor Foundation for EHS Management.

You have ensured that the linkage between PCO classes and the corresponding workflows of SAP Business Workflowis correctby implementing the Customizing activityList Configured Processesfor Foundation for EHS Management.

Standard settings


Activities


37/116




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 forFoundation for EHS Management.

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 applicationin SAP EHS Management (EHS-MGM). It is critical that you execute this activity if you want to use the process foundationtosupport your business processes.

Requirements

You have set up the workflow system in the Customizing activityPerform Automatic Workflow Customizingfor Foundation

for EHS Management.

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


38/116

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 reportR_EHHSS_CONFIG_TASK_ROLES.

Further information

You can assign roles manually to tasks by opening each task in transaction PFTC_CHG.

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 formsavailable in the data record only if the corresponding regulation applies.

This activity is critical if you want to uses forms for reporting incidents, for example, to legal authorities, organization-internal

recipients, or insurance companies.

Requirements

You have created regulations in the Customizing activityCreate Regulationsfor Foundation for EHS Management.

You have specified forms in the Customizing activitySpecify Formsfor Foundation for EHS Management.

You have specified regulations for the incident group, incident category, region, and country in Customizing activitySpecifyRegulationsfor Incident Management.

Standard settings


39/116


Activities



3. If you have created an internal regulation in Customizing activity Create Regulationsand 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 usethe following settings delivered in the standard system:

OSHA regulation (EHFND_US_OSHA) specified for the United States (US), for incidents (001 Incident), and for theincident 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 a near miss or a safety observation, for

example. You can store the forms on a medium (such as an Intranet or a public file share) that can be accessed by all personswho should be able to use them to report such events.

Requirements

You have specified the offline forms in the Customizing activitySpecify Formsfor Foundation for EHS Management.

Standard settings


You can use the following example forms for offline recording:

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.

Further information


40/116

If you use the example forms delivered in the standard system, you can record safety observations and near misses offline andchoose the Sendpushbutton in the form to submit it to the incident manager. The form is sent by e-mail to the system, where thee-mail inbound handler creates a data record for the near miss or safety observation using theinbound persisterof thecorresponding form. For more information about setting up the inbound handling of forms, seeDefine InboundProcessing forE-Mails.

Define Inbound Processing for E-Mails

Use

An e-mail inbound process is often required in the SAP EHS Management (EHS-MGM)component. For example, the recipientof aninquirycompletes a form and sends it back to a defined e-mail address. The system attaches the returned form to therelevant workflow and the business process continues.

In this Customizing activity, you can define how the system processes such inbound e-mails by configuring the e-mail exithandler for each e-mail address that should receive the relevant form.

Requirements

You have configured the inbound e-mail address for each form in the Customizing activitySpecify Forms.

Your company's e-mail system is set up in such a way that it forwards the e-mail to the SAP EHS Managementcomponent based on the e-mail address that is configured for the form.

You have assigned the PFCG role SAP_EHSM_HSS_INCIDENT_EML_REC to the user SAPCONNECT. This rolecontains the authorization profiles needed to receive and process e-mails.

Standard settings

There is a default exit handler for EHS Management: CL_EHHSS_INC_INB_PROC_BCS. It logs the e-mails that are receivedusing the SAP Application Log. You can use transaction SLG1 to view the logs by entering the following parameters:

Object: EHHSS_BO_INC

Subobject: EHHSS_AIF_INC_INBD

Activities

In this Customizing activity, you should specify the following parameters:

Communication Type: Internet Mail

Recipient Address: Specify the e-mail address(es) that are configured for the corresponding forms. If you use anasterisk (*) as the value, this inbound handler is called for each e-mail address. However, it is recommended that youuse the recipient address(es) of the forms that are configured.

Document Class: *


41/116

Exit Name: CL_EHHSS_INC_INB_PROC_BCS

If you want to change how the e-mail exit handler behaves, you can create your own implementation that inherits from thedefault class. In this case, go to transaction SE24, create a new class that inherits from CL_EHHSS_INC_INB_PROC_BCS, andmodify the HANDLE_FORMS method.

Specify Inquiry FormsUseIn this Customizing activity, you can specify which inquiry forms are assigned to which reference category when an event isreported in the SAP EHS Management (EHS-MGM) component.

RequirementsYou have specified forms in Customizing activitySpecify Formsfor Foundation for EHS Management.Standard settingsThe standard system is delivered with examples.Activities





42/116

Specify Incident Groups

Use

In this Customizing activity, you can define additionalincident groups.

Depending on the data you enter during the initial recording step for the incident record, the system automatically classifiesincidents according to groups, such as Release. You can change this classification during the review and completion step. If youassign an incident group delivered with the standard system, the system modifies the user interface to either reveal relevant orhide irrelevant incident parameters. If you assign a customer-specified group, this will have no effect on the user interface.

Standard settings


Activities




Incident GroupDefinition

Classifies the incident based on whether it is, for example, an injury or illness.UseIf you assign one or more than one incident group to an incident, the system automatically displays relevant data fields orhides unnecessary data fields in the incident record.

Specify Near Miss GroupsUseIn this Customizing activity, you can define additionalnear miss groups.You can use near miss groups to classify near misses, either during the initial recording step or during the review andcompletion step for incident records.Standard settingsThe standard system is delivered with examples.Activities





43/116

Near Miss GroupDefinitionClassifies the near miss based on the situation it involved, for example, an unsafe action.Use

You can select more than one near miss group, if necessary.

Specify Safety Observation GroupsUseIn 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 thereview and completion step for incident records.Standard settings

The standard system is delivered with examples.Activities




Safety Observation Group classifies the safety observation based on the situation it involved, for example, the use of

defective material. You can select more than one safety observation group, if necessary.

Specify Location Classifications

Use

In this Customizing activity, you can define the location types. During the initial recording step for the incident record, you canenter a location type which describes where the incident occurred.

Standard settings


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


44/116


45/116


Specify Estimated Risk Types

Use

In this Customizing activity, you can define estimated risk typesfor near misses and safety observations.

Standard settings


Activities






Estimated Risk Type indicates the potential risk of a future incident resulting from the circumstances of a nearmiss or safety observation.


46/116

Specify Roles

Use

In this Customizing activity, you can define therolesof 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 notcorrespond with the roles that are assigned to business partners.You can define business partner roles in Customizing for Cross-Application Componentsunder SAP Business Partner ->Business Partner -> Basic Settings -> Business Partner Roles -> Define BP Roles.

Standard settings


Activities





47/116

Role of Involved Person indicates the role or roles of a person or organization involved in an incident, such as aWitness.

Injured Person

Specify Incident Types

Use

In this Customizing activity, you can define differentincident typesfor incidents that involve the injury or illness of an involvedperson. For each incident type, you can specify whether it is occupational or non-occupational according to the regulations thatare 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. Theclassification is required for legal reporting.


48/116

Standard settings


Activities






Incident Type classifies further the type of incident that occurred, such as an incident on the way to work.Depending on regulations, different types of incident are relevant for legal reporting. You can use the incident type todetermine which incidents are taken into account for reporting purposes. For example, if you select an incident type that isclassified as occupational according to OSHA standards, the incident is included in the OSHA 300 Log.

Specify Additional Reporting Criteria (OSHA)

Use

In this Customizing activity, you can defineadditional reporting criteriafor OSHA reporting.

OSHA regulations require that certain cases of injury or illness are explicitly reported beyond general reporting criteria, such asthe following:

Needlestick and sharps injuries (in case of contamination with another person's blood or other potentially infectiousmaterial)

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 f ield control settings that display this field only when the incident is subject to OSHArecording requirements. For more information, see the settings for business object EHHSS_INCIDENT-> node

PERSON_INJ_INFO-> field control profile OSHAin the Customizing activitySpecify Field Controlfor Foundation for EHSManagement.

Activities


49/116






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 typesto specify where a person died.

Standard settings


The standard system is delivered with field control settings that display this field only when the incident is subject to OSHArecording requirements. For more information, see the settings for business object EHHSS_INCIDENT-> node

PERSON_INJ_INFO-> field control profile FATALITY_STATEin Customizing activitySpecify Field Controlfor Foundation foEHS Management.

Activities







50/116


51/116

In this Customizing activity, you can define different means of transportation that can be used to take an injured person from firstaid treatment to further treatment or to their home.

Standard settings


The standard system is delivered with field control settings that display this field only when the incident is subject to OSHArecording requirements. For more information, see the settings for business object EHHSS_INCIDENT-> node

PERSON_INJ_INFO-> field control profile OSHAin the Customizing activitySpecify Field Controlfor Foundation for EHSManagement.

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 tospecify why a person died.

Standard settings


52/116


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-> nodePERSON_INJ_INFO-> field control profile FATALITY_STATEin Customizing activitySpecify Field Controlfor Foundation foEHS Management.

Activities






Specify Injury/Illness Classifications

Use

In this Customizing activity, you can define aninjury or illness classificationaccording to the current OSHA standards. Thisclassification is required to classify the injury or illness in legal reporting.

Standard settings



53/116

Activities






Injury/Illness Classification classifies the injury or illness typeaccording to OSHA standards, for example, as aninjury or one of several occupational health conditions.The OSHA 300 form collects data on specific occupational health conditions, such as the following:

Skin diseases or disorders

Respiratory conditions

Poisoning

Hearing loss

All other illnessesAfter specifying a classification for an injury or illness, you can select only the injury or illness types that correspond to theselected classification.

Injury/Illness Type indicates the type of injury or illness that an injured person suffered due to an incident. Eachinjury/illness type is classified according to an OSHA-specific injury/illness classification.

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 illnesscaused by the incident. Each injury or illness type must be assigned to an injury or illness class as defined in theinjury/illnessclassificationto allow a classification according to OSHA standards.

Requirements

You have defined an injury/illness classification in the Customizing activitySpecify 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 Defaultcheckbox for the

corresponding entry.

2. If necessary, define additional injury or illness types and assign them to an injury/illness class.



54/116

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. Duringincident recording, you can use these definitions to give a detailed description of the injury.

Standard settings


Activities







55/116

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. Duringincident recording, you can use these definitions to give a detailed description of the injury.

Standard settings


Activities







56/116

Specify Restriction Types

Use

In this Customizing activity, you can define differentrestriction types.During incident recording, you can assign theserestriction types to an injured person to give detailed information about the consequences of an injury or illness.

Note

To specify theabsence typesthat are relevant for incident recording, you use the Customizing activitySpecify Relevant HRAbsence Types.

Standard settings


Activities







57/116

Influencing Factors

Specify Incident-Causing Objects

Use

In this Customizing activity, you can define differentincident-causing objects.During incident recording, you can specify theseobjects to provide detailed information about why an incident occurred.

Standard settings


Activities



58/116


59/116



Incident-Causing ObjectDefinitionSpecifies an object that contributed to the occurrence of the incident.DependenciesTo further describe what happened to the incident-causing object at the time of the incident, you can also specify themovementof this object.

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 incidentoccurred.

Standard settings


Activities







60/116

Specify Movements of Injured Persons

Use

In this Customizing activity, you can define different kinds of movement. During incident recording, you can use these movementdefinitions to provide detailed information about what the injured person was doing when the incident occurred.

Standard settings


Activities







61/116

Specify Personal Protective Equipment

Use

In this Customizing activity, you can define thepersonal protective equipmentthat can or must be used for certain jobs.

Standard settings


Activities






Specify External Influences

Use


62/116

In this Customizing activity, you can define differentexternal influences.During incident recording, you can specify theseexternal influences to provide detailed information about the circumstances under which an incident occurred.

Standard settings


Activities






External Influence specifies an external influence that contributed to the incident, for example, rain or snow.

Specify Immediate Actions

Use

In this Customizing activity, you can define different actions describing the steps that are taken immediately after an incidentoccurred.

Standard settings


Activities





A unique key must be assigned to each entry. Example


63/116

Specify Technical Safety Devices

Use

In this Customizing activity, you can define differenttechnical safety devices.

Standard settings


Activities







64/116

Assets

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 involvedasset during incident recording of SAP EHS Management (EHS-MGM).

You can do the following:

Select equipment types from Plant Maintenance (PM)to restrict the number of available equipment types in EHS-MGM

Define new equipment types for EHS-MGM

Requirements

If you want to select equipment types from PM, you have definedtechnical object typesin Customizing for Plant Maintenance

underDefine Types of Technical Objects.You can specify these technical object types as equipment types in Customizing forSAP EHS Management.

Standard settings

The standard system is delivered without equipment types.

Activities

If you want to use a restricted number of PMequipment types for EHS-MGM, select the required equipment types andenter a description for all relevant languages. If you do not enter a description, the system automatically uses thedescription 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-MGM, define the required entries and enter adescription for all relevant languages.

If you do not specify any equipment types, all PMequipment types can be selected during incident recording. However, onceyou have specified equipment types for EHS-MGM, you can only use the equipment types that are defined in this Customizingactivity.


65/116

Recommendation

Although it is possible to use PMequipment types together with equipment types that are only relevant for EHS-MGM,we do notrecommend this. If you used both, you would be able to select a non-PMequipment type, for example, but you would not find aP

configuration-sap econfiguration-sap ehs managemenths management

Documents