INCIDENT MANAGEMENT

General Configuration
SPRO > EHS > INCIDENT MANAGEMENT > GENERAL
CONFUGURATION

Configure Foundation for EHS

Use
Before carrying out the Customizing activities under Incident Management, you must first
process Customizing for the Foundation for EHS Management (EHS-MGM-FND)
component. Below, you will find information about the foundation Customizing activities
and their relevance to incident management.
General Configuration
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, to support you in fulfilling
regulatory requirements, and to store attached documents.
For more information, see the following Customizing activities for Foundation for EHS:
 Specify Field Control
 Create Regulations
 Specify Document Storage

Process Foundation
You can customize the process foundation to support your incident-specific processes.
For more information, see the following Customizing activities for Foundation for EHS:
 Specify Process Definitions
 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.
For more information, see the following Customizing activities for Foundation for EHS:
 Check Configuration of Workflow System
 List Configured Processes
 Schedule Jobs for Process Statistics
Actions
During incident recording, you can specify actions and notifications in response to incidents,
or to prevent future incidents from occurring. In Customizing, you can configure the settings
for actions and notifications. For more information, see the following Customizing activities
for Incident Management -> Master Data Configurations -> Actions and Controls.
 Specify Types
 Specify Subtypes
 Specify Effectiveness
 Specify Protection Goals
 Specify Templates
 BAdI: Definition of Process Steps
Print Forms and Interactive Forms
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.
For more information, see the following Customizing activities for Foundation for EHS:
 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), personnel 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.
For more information, see the following Customizing activities for Foundation for EHS:
 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
Locations
You can use locations in incident management to describe where an incident occurred. For
more information, see the following Customizing activities for Incident Management ->
Master Data Configurations -> Locations.
 In the Customizing activity Specify Number Range Intervals for Foundation,
define the number range intervals for the location ID.
 Enable / Disable PM Integration
 In the Customizing activity Schedule Jobs for Location Synchronization , configure
periodical PM synchronization.
 Specify Authorization Groups
 Specify Location Types

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.
For more information about other number range objects, see:
 Specify Number Range Intervals for Foundation
 Specify Number Range Intervals for Health and Safety Management
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).
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.
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 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
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 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 the Extended 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
The standard system is delivered with examples.
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 EHS 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
The standard system is delivered with examples.
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.