Professional Documents
Culture Documents
JDE92 - Health and Safety
JDE92 - Health and Safety
July 2018
Describes the Health and Safety Incident Management
module, and discusses how to enter, report, and manage
incidents.
JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide,
Release 9.2
E63994-12
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it
on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users
are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and
adaptation of the programs, including any operating system, integrated software, any programs installed on
the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to
the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages
caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of
third-party content, products, or services, except as set forth in an applicable agreement between you and
Oracle.
Contents
iii
2.1.5 Detailed Incident Report..................................................................................................... 2-4
2.1.6 One View Reporting of Incidents ...................................................................................... 2-4
2.1.7 Health and Safety OSHA and BLS Reports ..................................................................... 2-4
2.1.8 Health and Safety EnterpriseOne Pages........................................................................... 2-5
2.1.9 Task Tickler Reminder (Release 9.2 Update) ................................................................... 2-5
2.2 Understanding General System Setup..................................................................................... 2-5
2.3 Understanding Tables Used by the JD Edwards EnterpriseOne Health and Safety Incident
Management System 2-7
2.4 Setting Up User Defined Codes (UDCs).................................................................................. 2-7
2.4.1 Incident User Defined Codes ............................................................................................. 2-8
2.4.2 Incident People User Defined Codes ................................................................................ 2-9
2.4.3 Incident Injury or Illness User Defined Codes ............................................................. 2-11
2.4.4 Incident Equipment User Defined Codes ..................................................................... 2-11
2.4.5 Incident Environment User Defined Codes.................................................................. 2-12
2.4.6 User Defined Codes for User Defined Incident Data (Release 9.2 Update) ............. 2-12
2.5 Setting Up Category Codes .................................................................................................... 2-13
2.6 Setting Up User Defined Incident Data (Release 9.2 Update) ........................................... 2-14
2.6.1 Setting Up UDC Values for User Defined Incident Data............................................ 2-15
2.6.2 Setting Up Incident User Defined Data Templates...................................................... 2-15
2.7 Understanding Safety Hours.................................................................................................. 2-17
2.8 Setting Up Email Distribution Groups ................................................................................. 2-18
2.8.1 Forms Used to Set up Email Distribution Groups ....................................................... 2-18
2.9 Setting Up Composite Application Framework.................................................................. 2-18
2.10 Understanding Next Numbers .............................................................................................. 2-19
2.11 Understanding Failure Analysis............................................................................................ 2-19
2.12 Understanding Establishments.............................................................................................. 2-20
iv
3.3 Entering Incidents Using the Report an Incident Program (P54HS30)............................ 3-18
3.3.1 Understanding How to Enter Incidents Using the Report an Incident Program
(P54HS30) 3-18
3.3.2 Form Used to Report Incidents Using the Report an Incident Program (P54HS30) 3-18
3.3.3 Setting Processing Options for the Report an Incident Program (P54HS30) ........... 3-18
3.3.3.1 Process......................................................................................................................... 3-19
3.4 Inquiring on Cases ................................................................................................................... 3-19
3.4.1 Understanding the Incident Case Inquiry Program (P54HS210) .............................. 3-19
3.4.2 Form Used to Inquire On Cases ..................................................................................... 3-19
3.4.3 Setting Processing Options for the Case Inquiry Program (P54HS210) ................... 3-19
3.4.3.1 Defaults ....................................................................................................................... 3-20
3.5 Entering Safety Hours ............................................................................................................ 3-20
3.5.1 Understanding the Safety Hours Entry Program (P54HS20)..................................... 3-20
3.5.1.1 Understanding How the System Determines Safety Hours ............................... 3-21
3.5.2 Form Used to Enter Safety Hours .................................................................................. 3-21
3.6 Inquiring on Tasks (Release 9.2 Update) .............................................................................. 3-22
3.6.1 Understanding the Incident Task Inquiry Program (P54HS215)............................... 3-22
3.6.2 Form Used to Inquire On Tasks...................................................................................... 3-22
3.6.3 Setting Processing Options for the Task Inquiry Program (P54HS215) ................... 3-22
3.6.3.1 Process......................................................................................................................... 3-22
3.6.3.2 Versions....................................................................................................................... 3-22
3.7 Generating the Task Tickler Reminder Report (Release 9.2 Update)............................... 3-23
3.7.1 Understanding the Task Tickler Reminder Program .................................................. 3-23
3.7.2 Running the Task Tickler Reminder Program.............................................................. 3-23
3.7.3 Setting Processing Options for Task Tickler Reminder Report (R54HS420)............ 3-23
3.7.3.1 Process......................................................................................................................... 3-23
3.8 Entering User Defined Incident Data (Release 9.2 Update)............................................... 3-24
3.8.1 Adding User Defined Data to an Incident .................................................................... 3-24
3.8.2 Revising Incident User Defined Data ............................................................................ 3-25
3.8.3 Deleting Incident User Defined Data............................................................................. 3-25
3.8.4 Personalizing User Defined Incident Data.................................................................... 3-26
4 Reporting Incidents
4.1 Understanding Regulatory Incident Reporting...................................................................... 4-1
4.2 Generating the OSHA 300 Log Report and OSHA 300A Summary Report....................... 4-1
4.2.1 Understanding the OSHA 300 Log Report and the OSHA 300A Summary Report.. 4-2
4.2.2 Running the OSHA 300 Log Report.................................................................................. 4-2
4.2.3 Setting Processing Options for OSHA 300 Log Report (R54HS300) ............................ 4-2
4.2.3.1 Process............................................................................................................................ 4-2
4.2.4 Running the OSHA 300A Summary Report .................................................................... 4-2
4.2.5 Setting Processing Options for OSHA 300A Summary Report (R54HS300A)............ 4-3
4.2.5.1 Process............................................................................................................................ 4-3
4.3 Generating the OSHA 301 Injury/Illness Report (R54HS301) ............................................. 4-4
4.3.1 Understanding the OSHA 301 Injury/Illness Report..................................................... 4-4
4.3.2 Running the OSHA 301 Injury/Illness Report ................................................................ 4-4
4.3.3 Setting Processing Options for OSHA 301 Injury/Illness Report (R54HS301)........... 4-5
4.3.3.1 Process............................................................................................................................ 4-5
v
4.4 Generating the Bureau of Labor Statistics (BLS) Survey Report (R54HS320) .................... 4-5
4.4.1 Understanding the Bureau of Labor Statistics (BLS) Survey Report ........................... 4-5
4.4.2 Running the BLS Survey Report........................................................................................ 4-5
4.4.3 Setting Processing Options for the BLS Survey Report (R54HS320)............................ 4-5
4.4.3.1 Process............................................................................................................................ 4-6
4.5 Generating the Detailed Incident Report ................................................................................ 4-6
4.5.1 Understanding the Detailed Incident Report .................................................................. 4-7
4.5.2 Running the Detailed Incident Report.............................................................................. 4-7
4.5.3 Setting Processing Options for Detailed Incident Report (R54HS400) ........................ 4-7
4.5.3.1 Print ................................................................................................................................ 4-7
vi
Preface
Audience
This guide is intended for implementers and end users of the JD Edwards
EnterpriseOne Health and Safety Incident Management system.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
vii
Related Information
For additional information about JD Edwards EnterpriseOne applications, features,
content, and training, visit the JD Edwards EnterpriseOne pages on the JD Edwards
Resource Library located at:
http://learnjde.com
Conventions
The following text conventions are used in this document:
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code
in examples, text that appears on the screen, or text that you enter.
viii
1
Introduction to JD Edwards EnterpriseOne
1
Figure 1–1 Health and Safety Incident Management Business Process (Release 9.2
Update)
This business process flow explains the processes involved in incident tracking and
reporting using the JD Edwards EnterpriseOne Health and Safety Incident
Management system. You enter the incident using the Incident Master program
(P54HS00) or the Report an Incident program (P54HS30) or the mobile Report an
Incident applications. The system automatically notifies those that need to know, such
as the company safety officer and other interested parties. The reported incident and
1-2 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
JD Edwards EnterpriseOne Health and Safety Incident Management Integrations
recordable cases are investigated and additional details are recorded in the system.
You can assign tasks and enter costs associated with the incident. Employees are able
to review the case logs using the Case Inquiry program (P54HS210) as required by
OSHA or review tasks using the Incident Task Inquiry program (P54HS215) (Release
9.2 Update). Finally, you can use One View Reporting programs to analyze the
incident, frequency rates, and other safety metrics. People can be reminded of tasks
that are due or are overdue (Release 9.2 Update).
1-4 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
JD Edwards EnterpriseOne Health and Safety Incident Management Implementation Steps
■ Set up establishments.
1-6 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
2
Setting Up the JD Edwards EnterpriseOne
2
Setting Up the JD Edwards EnterpriseOne Health and Safety Incident Management System 2-1
Understanding the JD Edwards EnterpriseOne Health and Safety Incident Management System
2.1.2 Investigation, Cost, Follow-Up Actions Items, and Incident Task Inquiry (Release
9.2 Update)
Typically, after the incident is recorded in the JD Edwards EnterpriseOne Health and
Safety Incident Management system, it is investigated. In the process of investigating
an incident, you determine further details and the extent of the incident, direct and
root cause of an incident, and take preventive or remedial actions. During the
investigation, you also record information about who is investigating, who is handling
the incident, and the information determined from the investigation. You capture any
estimated or actual costs related to the incident. You can also associate an incident
with a work order and display the estimated and actual work order costs. Tasks can be
assigned to and viewed by individuals related to an incident. You will also be
reminded of tasks that are due or are overdue via an email or a Work Center message.
2-2 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Understanding the JD Edwards EnterpriseOne Health and Safety Incident Management System
You can track detailed information about any injuries or illnesses that the employees
suffer during the performance of their jobs within the organization. This information
includes the following, but it is not limited to:
■ Date of incident
■ Time of incident
■ Description of incident
■ Employee name
■ Description of the injury or illness
■ Part of body affected
You use the injury or illness case information to create and print regulatory health and
safety reports.
After you enter the required information for an injury or illness, you can enter
information about any additional injuries or illnesses for the person related to the
same incident. Additional data includes any information that you want to track about
injuries and illnesses, regardless of whether you need to report the case to
governmental health and safety organizations.
To support the OSHA requirements to give all employees access to the information
recorded for an injury or illness case, the JD Edwards EnterpriseOne Health and Safety
Incident Management system provides a special view-only program, the Incident Case
Inquiry program (P54HS210). This program provides a view of the data recorded on
the OSHA 300 Log Report of the Work-Related Injuries and Illnesses and the OSHA
301 Injury/Illness Report, in the Tell us about your case section.
Note: The terms 'incident' and 'case' are used in the JD Edwards
EnterpriseOne Health and Safety Incident Management system. An
incident refers to a single occupational health or safety event at an
organization. A case refers specifically to an injury or illness to an
employee as a result of an incident. An incident can have several
employees who are injured and therefore result in several cases. A
single injured employee can have several injuries related to the same
incident, but only the most severe injury is recorded as a case. The
system allows you to record information about the additional injuries.
However, the most severe injury is typically the one reported, and
therefore you can record only one injury or illness as a case per
employee per incident. The system tracks non-employees who are
injured but cases would not be created for them. You use OSHA and
BLS reports to report case information. Tracking all injured people and
their injuries is important as you analyze incidents. You use the
Incident People table (F54HS02) to record case information, and
Incident Injury/ Illness table (F54HS021) to record additional injuries.
Setting Up the JD Edwards EnterpriseOne Health and Safety Incident Management System 2-3
Understanding the JD Edwards EnterpriseOne Health and Safety Incident Management System
cannot locate an email address, it sends a message to the work center using a send
message command. A link is embedded in the email that points to the incident record.
When you click the link, the system uses the version of the application used at the time
the email was generated
2-4 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Understanding General System Setup
Topic Description
Email Distribution Groups Set up email distribution groups to send an email notification to
the interested parties after the incident is recorded.
Section 2.8, "Setting Up Email Distribution Groups"
External Safety Hours Set up external safety hours to calculate the reporting and
analytical information unless you retrieve this information from
the JD Edwards EnterpriseOne Payroll system tables.
If you are not using the JD Edwards EnterpriseOne Payroll
system, you will need to enter external safety hours and the
average annual number of employees using the Safety Hours
Entry program (P54HS20).
Section 2.7, "Understanding Safety Hours"
Composite Application Framework Set up Composite Application Framework to display a map
showing the incident location using either the address fields or
the Latitude/Longitude fields.
Section 2.9, "Setting Up Composite Application Framework"
Setting Up the JD Edwards EnterpriseOne Health and Safety Incident Management System 2-5
Understanding General System Setup
Topic Description
Establishments Set up establishments for OSHA reporting in the address book
records. You use the Establishment Condition program
(P086011) to enter a condition record for each establishment for
each calendar year being reported. To default the establishment,
when creating a new incident for each user who enters incidents
into the system, you must set up the establishment in the
Employee Supplemental Data program
Section 2.12, "Understanding Establishments"
Companies, Business Units, and Projects Set up companies using the Company Master program (P0010).
Set up business units and projects using the Business Unit
Master program (P0006). You can associate incidents with
companies, business units, and projects. This is useful for
analyzing incidents by these different organizational units.
See: "Setting Up Companies" in the JD Edwards EnterpriseOne
Applications Financial Management Fundamentals Implementation
Guide
See: "Setting Up Business Units" in the JD Edwards
EnterpriseOne Applications Financial Management Fundamentals
Implementation Guide
Home Business Unit and Home Company To default the company and business unit fields, when creating
a new incident for each user who enters incidents into the
system, set up their home company and home business unit in
the Employee Master program (P0801). Then make sure that the
Employee Profile Setup program (P20103) is set to use the
Employee Master as the Source Table.
Address Book Records Set up address book records using the Address Book Master
program (P01012). Address book records are used for
establishments, employees, agencies, contractors, distribution
lists, and facilities. You do not have to use address book records
for employees, but if you do, the system uses the default values
of many of the fields related to the employee. There are some
fields on the incident record that must have a valid address
book record if you want to use them. These fields include
Establishment, Distribution List, Individuals to be Notified,
Contractor Responsible for Product (on the Environmental
Impact record), Originator, Reported By, Investigated By,
Incident Handler, Foreman, Mentor, Supervisor, Facility
(medical), and Contractor/3rd Party.
Inventory Items For incidents that have an environmental impact, you can
associate products or substances spilled or released with the
incident. You may want to select this from the Inventory Item
Master, although it is optional. You can set up products or
substances in the Inventory Item Master program (P4101). The
system does not use the item branch record.
Equipment, Property, and Motor Vehicles Many times, incidents involve motor vehicles or result in
damage to property or equipment. You can use the information
already set up in the Asset Master table for company owned
equipment, but it is optional. You use the Work with Equipment
Master program (P1701) and the License Information program
(P1206) to set up equipment or assets.
Work Orders If you want to use work orders to track remedial actions and
related costs for incidents, you must set up work orders in one
of the many work order programs. You can then associate the
incident with the work order and display the actual and
estimated work order costs in the Costs section of the incident
master. If a parent work order number is associated with an
incident, the costs shown will include the costs of the children
work orders.
2-6 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Setting Up User Defined Codes (UDCs)
Table Description
Incident Master (F54HS01) Contains detailed information about the company, business
unit, establishment, project number, contractor, or third party or
party responsible for incidents. This table also contains incident
descriptions, date, location, causal details, and other
information related to the specific incident.
Incident People (F54HS02) Contains detailed information of the people involved in an
incident in any role. This table also includes information of
primary injury or illness of injured people with related
recordable case details.
Incident Injury/Illness Details (F54HS021) Contains information about any additional injuries or illnesses
of an injured person related to an incident.
Incident Equipment (F54HS03) Contains detailed information for any property, equipment, or
motor vehicle involved in an incident.
Incident Agencies (F54HS04) Contains information about any agency, department, or group
related to an incident.
Incident Notification Members (F54HS05) Contains information about distribution lists or individuals to
notify about the incident.
Incident Notifications Sent (F54HS05H) Contains information about any individual or distribution list to
which a notification is sent.
Incident Tasks (F54HS06) Contains detailed information about the tasks assigned related
to the incident.
Incident Costs (F54HS07) Contains detailed information about any actual or estimated
costs related to the incident.
Incident Environmental Impact (F54HS08) Contains detailed information about any environmental impact
related to the incident such as the product or substance that was
spilled, quantity, and environmental impact.
Safety Hours (F54HS20) Contains both safety hours and average annual number of
employees for all establishments, business units, projects,
companies, and contractors for each calendar year. The system
uses this information when calculating incident rates.
Incident User Defined Data Templates Contains detailed information about the incident user defined
(F54HS15) (Release 9.2 Update) data templates that are defined for each data group and incident
record type.
Incident User Defined Data (F54HS16) Contains the user defined incident data that is added to an
(Release 9.2 Update) incident master record.
Setting Up the JD Edwards EnterpriseOne Health and Safety Incident Management System 2-7
Setting Up User Defined Codes (UDCs)
2-8 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Setting Up User Defined Codes (UDCs)
Setting Up the JD Edwards EnterpriseOne Health and Safety Incident Management System 2-9
Setting Up User Defined Codes (UDCs)
2-10 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Setting Up User Defined Codes (UDCs)
Setting Up the JD Edwards EnterpriseOne Health and Safety Incident Management System 2-11
Setting Up User Defined Codes (UDCs)
2.4.6 User Defined Codes for User Defined Incident Data (Release 9.2 Update)
This table lists the user defined codes for user defined incident data.
2-12 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Setting Up Category Codes
Setting Up the JD Edwards EnterpriseOne Health and Safety Incident Management System 2-13
Setting Up User Defined Incident Data (Release 9.2 Update)
2-14 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Setting Up User Defined Incident Data (Release 9.2 Update)
You can customize these UDC tables to meet your needs. Additionally, you can
use any existing UDC table when setting up user defined incident data.
This table illustrates an example of a user defined data plan for a safety observation
that uses 5 fields:
Once you understand your data needs, you then add all of your data groups in UDC
table 54HS/DG, and add any necessary values to other UDC tables you will use.
Once your UDC tables are complete, you use the Incident User Defined Data
Templates program (P54HS115) to build your templates.
Note: A data group can be used for more than one incident record
type but the fields need to be defined separately for each data
group/record type combination. Consider using the copy function in
the Work With Incident User Defined Data Templates program for
this.
Setting Up the JD Edwards EnterpriseOne Health and Safety Incident Management System 2-15
Setting Up User Defined Incident Data (Release 9.2 Update)
2. On the Work With Incident User Defined Data Templates form, click Add.
On the Incident User Defined Data Template Revisions form, you will create a
record for each user defined field in a data group. These fields will be accessible
and editable from the Incident Master. To begin, enter a unique combination of
values in these required fields:
■ Incident Record Type
Note: Note that if the incident record type field is left blank when
defining a data group, the data group will only be available to use
with incidents where the record type is left undefined or blank.
■ Data Group
■ Field Number
Note that the field number is used as the default display sequence on the
Incident User Defined Data Revisions form, where users will add user defined
data to an incident.
3. If you are creating a field that is similar to an existing data dictionary item,
complete the Data Dictionary Item field in the Copy Data Dictionary Details
section of the form.
When you exit out of this field, the system automatically populates the values in
your record with values from the specified data dictionary item. You can override
these values if necessary.
Note: Note that the data dictionary field is not stored but is available
on the form to help default in the desired field attributes when
defining a field.
2-16 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Understanding Safety Hours
Setting Up the JD Edwards EnterpriseOne Health and Safety Incident Management System 2-17
Setting Up Email Distribution Groups
■ Establishment
■ Company
■ Project
■ Business Unit
■ Contractor
2-18 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Understanding Failure Analysis
Set up your failure analysis codes so that they can be used in the Failure Analysis
Search and Select grid on the Investigation subform in the Incident Details tab in the
Setting Up the JD Edwards EnterpriseOne Health and Safety Incident Management System 2-19
Understanding Establishments
Incident Master program. Oracle recommends that you categorize the health and
safety failure codes using one of the Failure Analysis category codes. Configure the
Failure Analysis Search and Select grid with a custom grid to see the category code
when the search and select appears. If you are also using Failure Analysis for Capital
Asset Management, you need to distinguish your health and safety failure codes from
the maintenance failure codes. Categorizing your codes enable you to search failure
codes by using the Query By Example (QBE) with a custom grid to quickly find the
appropriate health and safety failure code.
Note: You do not need this step if you are using the Safety Hours
Entry program (P54HS20) for safety hours and average annual
number of employees.
4. Use the Establishment Condition program (P086011) from the Health & Safety
Incident Setup menu to enter a condition record for each establishment for each
calendar year being reported. The JD Edwards EnterpriseOne Health and Safety
Incident Management system uses establishment information for OSHA and
Bureau of Labor Statistics reporting. To produce the OSHA and BLS reports you
need a condition record for each establishment and year combination, even if
nothing unusual happened that year.
2-20 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Understanding Establishments
(Release 9.2 update) You can associate a company with the establishment in the
P086011 program. This association of company and establishment can be
leveraged in the Incident Master program (P54HS00) to default in the company
based on the establishment using this relationship. Use the P086011 program to
record a change reason if you are re-submitting the electronic version of the 300A
to OSHA. The program will use the most recent change reason recorded.
Use the Establishment Condition program (P086011) to enter the following
additional information about an establishment:
■ Maximum Size
Enter a code that represents the maximum number of employees that have
worked at an establishment at any point in the reporting year.
■ Form Exit Establishment Information
Use this form exit to associate a company with an establishment and to define
the establishment type. This information is used when submitting an
electronic file to OSHA for the 300A report.
■ Row Exit Change Reason
Use this row exit to record a reason why you are re-submitting an electronic
file to OSHA. If there is more than one change reason given for the same
establishment/year/report type combination, the re-submitted electronic file
will use the one with the highest sequence number.
Setting Up the JD Edwards EnterpriseOne Health and Safety Incident Management System 2-21
Understanding Establishments
2-22 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
3
Entering and Managing Incidents
3
3.2 Entering and Updating Incidents Using the Incident Master Program
(P54HS00)
This section provides an overview of incident records and discusses how to:
■ Set up processing options for the Incident Master program (P54HS00).
■ (Release 9.2 Update) Set up processing options for the Incident Task Details
program (P54HS17).
■ Enter and update incidents using the Incident Master program (P54HS00).
3-2 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Entering and Updating Incidents Using the Incident Master Program (P54HS00)
Incident
Use the Incident tab on the Manage Incidents program to locate incidents. You can
search incidents using dates, severity, status, or incident attributes.
The system provides you an option to easily print a detailed report of an incident from
the Manage Incidents form. To print a report for an incident, select the Print Report
button for the incident row. The system prints the report for the incident, and
automatically selects the incident in the grid row.
People
Use the People tab to locate incidents based on the people involved. You can also
search for incidents based on employee, incident role, and whether the person is
injured.
Equipment
Use the Equipment tab to locate incidents based on the property or equipment
involved. You can also search for incidents based on third-party equipment and motor
vehicle.
3.2.3 Setting Processing Options for the Incident Master Program (P54HS00)
Processing options enable you to specify the default processing for programs and
reports.
3.2.3.1 Defaults
1. Establishment
You use this processing option to specify whether the system uses a default value for
the establishment when you add an incident. The system uses this processing option
for both the Incident Entry program (P54HS00) and the Report an Incident program
(P54HS30). Enter a valid address book number for an establishment.
7. Default Job Title when Job Title is Blank in Employee Master (Release 9.2 Update)
Use this processing option to indicate how the system uses the values in the employee
master when the job title is blank in employee master. Values are:
Blank: Do not default Job Title.
1: Default Job Title to Job Type/Job Step description.
2: Default Job Title to Position ID description.
3-4 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Entering and Updating Incidents Using the Incident Master Program (P54HS00)
8. Default Security
Use this processing option to specify whether the system defaults the security
classification to selected or not selected when you add a new incident. This processing
option is used for both the Incident Entry program (P54HS00) and the Speed Incident
Entry program (P54HS30). Values are:
Blank = Not Selected
1 = Selected
3-6 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Entering and Updating Incidents Using the Incident Master Program (P54HS00)
3.2.3.3 Process
1. Send Notification on Incident Creation
Use this processing option to automatically send a notification to all members in the
incident notification list when you add an incident. Values are:
Blank: Do not send notification.
1: Send notification.
4. Lock Incident Number During 'ADD' using P54HS00 (Release 9.2 Update)
Use this processing option to lock the Incident Number field from being edited when
you add a new incident using the Incident Master program (P54HS00). This processing
option does not apply when you add an incident by using the Speed Incident Entry
program (P54HS30). Values are:
Blank: Locking is not enabled.
1: Locking is enabled.
3-8 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Entering and Updating Incidents Using the Incident Master Program (P54HS00)
3.2.3.5 Display
1. Display or Hide Change History Information
You use this processing option to determine whether the system displays the change
history information related to an incident. Values are:
Blank: Hide change history information.
1: Display change history information.
Note: When you add a new incident, the system does not display
the Change History tab.
Note: When you add a new incident, the system does not display the
HR Competencies tab.
Note: When you add a new incident, the system displays the
Licenses tab.
4. Privacy Case
You use this processing option to determine whether the system should respect the
privacy case or not, for this application. If the Privacy processing option is ON and the
privacy case is checked for an individual, then personal details such as Person ID,
Name, and Injury description will be masked, and the fields will be disabled
accordingly. Values are:
Blank: Privacy OFF
1: Privacy ON
Note: The version of the Who's Who Search and Select form is set up
under the Versions tab of the processing options.
3-10 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Entering and Updating Incidents Using the Incident Master Program (P54HS00)
3.2.3.6 Versions
1. Quick Customer/Contact Add (P01015) Version
You use this processing option to define the version of the Quick Customer/Contact
Add program (P01015) that the system uses to add a contact. When you choose to
display the Who's Who Search and Select for the Agency number, you can select a
contact from this form. If you leave this processing option blank, the system will not
display the form. Values are:
Blank = ZJDE0001
3.2.4 (Release 9.2 Update) Setting Processing Options for the Incident Task Details
Program (P54HS17)
Processing options enable you to specify the default processing for programs and
reports.
3.2.4.1 Versions
1. Incident Master (P54HS00)
Use this processing option to reference the version of the P54HS00 program for the
system to determine whether to lock the task fields for editing. The system uses the
Conditional Locking of Edits to the Incident and Tasks processing option of the
P54HS00 program to determine the locking status of the records.
If you leave this option blank, the system uses the default version ZJDE0001.
3.2.5 Entering and Updating Incidents Using the Incident Master Program (P54HS00)
Access the Add Incident form.
The header contains these fields that you can use to record the core details of an
incident:
Incident Number
The system can assign an incident number from the Incident Number Next Number,
but you can also enter a value. This is a mandatory field.
Incident Description
Enter a brief description of the incident.
Record Type
Enter a value from the Record Type UDC table (54HS/RT) to indicate the type of
incident record.
Incident Severity
Enter a value from the Severity Value UDC table (54HS/SV) to indicate the severity of
the incident.
Incident Status
Enter a value from the Incident Status UDC table (54HS/ST) to indicate the current
status of the incident.
Incidents YTD
This is a display only field and shows the number of incidents that have occurred year
to date. It ignores any incidents marked as either potential incidents or those with
Exclude From Safety Statistics selected.
The header also contains these options that you can use to classify an incident:
Potential Incident
Select this option if you are recording a near miss, observed unsafe act or condition, a
safety inspection, or anything else that is not an actual health and safety incident.
Authorities Alerted
Select this option to indicate that the authorities were alerted about the incident.
3-12 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Entering and Updating Incidents Using the Incident Master Program (P54HS00)
Environmental Impact
Select this option to indicate the incident had an impact on the environment such as a
spill or release.
Injury / Illness
Select this option to indicate the incident has people who were injured or were ill.
Security
Select this option to indicate the incident has a security issue such as a threat or
assault. When you select this option, a list of options from the Security Classification
UDC table (54HS/SC) appears next to it. You can use this list of options to categorize
the security type.
Other
Select this option to indicate whether the incident has other attributes, such as a fire,
explosion, or perhaps is being used to indicate a safety inspection. When you select
this option, a list of options from the Other Classification UDC table (54HS/OC)
appears next to it. You can use this list of options to categorize the other type.
You can access Attachments from the Form menu to attach a media object such as an
image or a document related to the incident.
3.2.5.1 Details
In the Edit Incident form, select the Details tab.
The Details form contains these collapsible subforms:
Location or Organization
You enter information about the location of the incident and the organization
associated with the incident. You can set a processing option to let the system populate
the value in the establishment field by default. The street address of the incident will
default from the mailing address of the address book record for the establishment
entered on the incident. You can also show a map of where the incident took place.
You use the Composite Application Framework field to show a map of where the
incident took place using the street address or the latitude or longitude coordinates for
the incident. The business unit can also default in, based on the employee profile setup
program (P20103) of the logged-in user, and the relationship of the business unit to a
company as set up in the Business Unit Master. If no employee profile is set up for the
user, the system will use the business unit on the address book record of the logged-in
user.
Notifications
You enter and maintain information about emails sent or email addresses associated
with the incident. You can also send emails or messages to individuals or groups.
There are two tabs on this subform, Notifications List and Sent History. The
Notifications List form is like an address book for the specific incident, containing a
list of individuals or distribution lists that are to be notified. When you add an incident
in the system, the system adds the originator of the incident, the distribution list, and
the individual specified in the processing options to the Notifications List form. You
can add additional members to the list. Notifications are sent out automatically when
an incident is added. Select the rows to re-notify and use the Send Notification button
if you want to re-notify the members in the Notifications List. To remove a member
from the list, select the row for the member and use the Delete button. The Sent
History form records each time a notification is sent, and the member to whom the
notification is sent.
Responsibility
You enter information about who is responsible for the incident, drug and alcohol
testing, insurance claim information, and causal factors and other risk information on
this subform. The Contractor / 3rd Party Involved option and the Contractor / 3rd
Party fields are used extensively in the One View Reporting and Safety Hours
programs.
Environmental Impact
You enter information about products or substances that are spilled or released, the
impact to the environment, and the remediation and corrective measures. There are
many fields on this sub-form that you can use to meet the special needs for an
organization, such as five category codes and four pairs of quantity and associated
unit of measure fields. An incident can have any number of environmental impact
records, one record for each product or substance spilled or released. For example, an
incident can involve several substances that are spilled. You enter a record in the grid
for each substance spilled, so the incident can have multiple environmental impact
records.
Agencies
You enter information about the organizations or agencies involved, such as law
enforcement, EPA, DOT, insurance companies, and so on. If the Who's Who Search and
Select processing options are set up, the contact information for an agency can be
selected from Who's Who. The system displays the contact form when you enter the
agency number.
Category Codes
You use Incident Category Codes to categorize and associate the incident with up to 20
user defined category codes. The five user-reserved fields, common to most JD
Edwards EnterpriseOne tables, are located on this subform directly below the category
codes, though they remain hidden. To use them in this form, your System
Administrator must enable them in the Form Design Aid program. However, they are
already incorporated into the processing logic of the incident.
Investigation
You enter information about who is investigating, who is handling the investigation,
and what has been determined in the Investigation subform. The system uses the user
ID of the person entering the incident as the default value for the originator. You use
the Failure Analysis feature to associate failures, analyses, or resolutions with
incidents. There are four additional media objects on this subform for additional
information about the incident.
Costs
You can enter any estimated or actual costs related to this incident. You can associate
an incident with a work order and display the estimated and actual work order costs.
The system displays the total of the estimated and actual costs that you enter in the
grid. The work order costs are displayed for the user’s convenience but are not
automatically entered into the grid. You enter them as grid rows if you want these
costs included in the total incident costs. There are five category codes for your use to
further describe costs. The value in the Currency Code field comes from the company
of the incident. The currency code is required when you enter more than one cost
record.
3-14 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Entering and Updating Incidents Using the Incident Master Program (P54HS00)
Activities
You can create tasks and keep track of them, along with corrective measures. Tasks can
be assigned to individuals and tracked in terms of status, priority, and dates. The
system notifies the individuals through emails when a task is assigned. There are 10
category codes for Tasks for your use. The Corrective Measures tab provides a media
object for the incident. If you update the person assigned to the task or the task status
fields, the system re-notifies automatically.
There are four date fields available for activities: Task Beginning Date, Task Ending
Date, Task Estimated Completion Date, and Task Actual Completed Date. The values
in these fields cannot be earlier than the values in Incident Date/Time fields.
(Release 9.2 Update) When you set the processing option to allow task reminders, the
system displays the Send Reminder button above the task grid. Select the tasks for
which you want to receive reminders using the row select, and click the Send
Reminder button. Based on the processing options that are set up, the system sends an
email or Work Center message to the people associated with the task, the incident
associated with the task, or the task's assignee. The email message will contain a link
to the incident for the recipient to use.
(Release 9.2 Update) The system displays the Task Details button above the task grid.
You can use this button to access the Incident Task Details program. The Task Details
form organizes the information into logical sections in a single form to facilitate data
entry. Based on the setting in the processing options, you can edit the task details. In
the header section, the system locks all fields, except the Task Description field, for
editing. After you add or update information in the Task Details form, click the Save
button on that form to save the changes, and click the Save button on the Edit Incident
form to save the changes made to the incident. You can also access the Task Details
form from the Incident Task Inquiry program (P54HS215) by displaying it in a
CafeOne window and dynamically linking the incident number and task number.
3.2.5.2 People
In the Edit Incident form, select the People tab.
You use the fields in the People tab to enter information of a person or people involved
with this incident, their role, injuries and regulatory (OSHA) illness or injury
information. If you enter a person by selecting them from the Address Book certain
fields can default in for that person.
The People form contains these collapsible subforms:
People
You identify all people associated with the incident using the People subform. When
you click the Contact Information button, the system displays emergency contact
information for the grid row selected. You can add information about a person directly
in the grid or after entering their name, you can use the People Details button to
complete entering the details for that person. You can enter information for any
person, even if that person is not an employee. If the person has an address book
record, you can enter a valid address book number. If the person does not have an
address book record, you can skip this field and enter the name of the person. After
you enter the address book number, indicate the role the person had in the incident.
The People Details form organizes the information into convenient sections to facilitate
data entry. The options at the top of this form are important for One View Reporting.
You use these options to indicate if individuals are employees or not, and if they are
injured or ill. The people detail sections are:
■ Job Related: The system can populate some of the fields in this section using
default values from the employee record. If you add or edit information in this
section it will not update the employee master. It will be stored in the people
record for the incident.
■ Personal / Contact: Use the fields in this section to record additional personal
information.
■ Risk: Use the fields in this section to record worker compensation or other
insurance information along with drug and alcohol testing information.
■ Reported Injury: Use the fields in this section to describe the primary or most
severe injury or illness for the person. If you flag the injury or illness as OSHA
Recordable, the incident will be included for regulatory reporting.
■ Case Information: You must enter a case and report on the case if an employee is
injured or ill on the job. Select the Recordable option to let the system assign a case
number. The system assigns case numbers sequentially starting over each calendar
year. It does not take into account any other field such as establishment. Select the
Privacy Case option, if a person wants to remain anonymous on reports and in the
Case Inquiry program. This will replace the name with Privacy Case, the Person
ID with 99999999 and display the Privacy Case Alternate Description. Complete
this section to record the information necessary for the OSHA and BLS reporting.
There is a processing option to control whether privacy case is recognized for the
Incident Master program.
■ Category Codes: There are ten category codes to further describe and categorize
the person related to the incident.
You can use the People Details button to access all the people fields on one form. After
you add or update information in the People Details form, click the Save button on
that form to save the changes. You must also click the Save button on the Edit Incident
form to save the changes made to the incident.
Competencies
You can set processing options to display the HR Competencies for the employees
related to the incident.
3.2.5.3 Equipment
In the Add Incident form, select the Equipment tab.
3-16 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Entering and Updating Incidents Using the Incident Master Program (P54HS00)
You use the fields in the Equipment tab to enter information about equipment or
property, including motor vehicles that are involved in this incident. You can also view
equipment permits and licenses information.
The Equipment form contains these collapsible subforms:
Equipment
Use this subform to record any equipment, property, or motor vehicle involved in the
incident.
You can enter equipment information directly into the grid or use the Equipment
Details form that you access by clicking on the Equipment Details button.
The options at the top of the Equipment Details form are important for One View
Reporting. You need to select these options to indicate if the equipment is damaged, if
it is a motor vehicle, or if it belongs to a third-party. If the Third-Party Equipment
option is not selected, the system assumes that the equipment is company owned. The
fields in this form are arranged in these sections:
■ Incident: Use this section to describe incident conditions and to provide more
information about equipment damage.
■ Operator: Use this section to record information about the driver or operator.
■ Equipment: Use this section to record additional information about the equipment.
■ Risk: Use this section to record risk related to the equipment.
■ Category Codes: Use the five category codes in this section to further describe the
equipment or damage related to the incident.
After you add or update information in the Equipment Details form, click the Save
button on that form to save the changes. You must also click the Save button on the
Edit Incident form to save the changes made to the incident.
Equipment Licenses
If you are using the Permits and Licenses program (P1206) of the Capital Asset
Management system, licenses can be displayed for any equipment related to the
incident. You must set a processing option to display the Equipment Licenses subform.
When you select equipment from the Equipment Master, the VIN #, Equipment Make,
and Equipment Model will default in. You can also simply enter the description for
equipment and not use the equipment number field.
3.3.1 Understanding How to Enter Incidents Using the Report an Incident Program
(P54HS30)
The Report an Incident program is a simplified program. Any employee can use this
program to quickly enter the initial details of an incident such as what, when, who,
and where. When an employee enters an incident using this program, the system uses
the processing option settings to select a version of the Incident Master program
(P54HS00) to determine whether to send notifications automatically and to use default
values for the establishment, individual to notify, and distribution list to notify. It will
also be used to determine the incident record type. Although this application is a
standard JD Edwards EnterpriseOne application, this program is designed to fit when
being used on a tablet device. The information presented requires no scrolling.
3.3.2 Form Used to Report Incidents Using the Report an Incident Program (P54HS30)
3.3.3 Setting Processing Options for the Report an Incident Program (P54HS30)
Processing options enable you to specify the default processing for programs and
reports.
3-18 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Inquiring on Cases
3.3.3.1 Process
1.Version of Incident Master P54HS00 to use for Processing Options
You use this processing option to define the version of the Incident Master program
(P54HS00) to use. The Report an Incident program uses this version's processing
option to send notifications and the default value for establishment when entering a
new incident. If you leave this option blank, the system uses the default version
ZJDE0001.
3.4.3 Setting Processing Options for the Case Inquiry Program (P54HS210)
Processing options enable you to specify the default processing for programs and
reports.
3.4.3.1 Defaults
1. Establishment (Required)
You use this processing option to specify the establishment for inquiry in the Incident
Case Inquiry program (P54HS210). You must set this processing option to enter a value
in the Establishment field in the Incident Case Inquiry program. The Establishment
field is disabled in the Incident Case Inquiry program.
4. Century/Year
You use this processing option to enter the century and year information that is used
in the Incident Case Inquiry program (P54HS210). If you leave this option blank, the
system populates the current system century and the year to the field in the header.
3-20 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Entering Safety Hours
Safety Hours Group field in the header to filter the grid rows. To create a new safety
hours record, go to the end of the grid rows and click in a new row.
3.5.1.1.1 Safety Hours Retrieved from Safety Hours Table (F54HS20) The system retrieves the
safety hours from the F54HS20 for the specific safety hours group for a specific
calendar month/year. A safety hours group can be an establishment, company,
business unit, project, or contractor.
3.5.1.1.2 Safety Hours Retrieved from Payroll Tables The system retrieves safety hours
from the payroll tables for all employees associated with the organizational unit
(establishment, company, business unit, or project). The system cannot retrieve
contractor safety hours from the payroll tables and so, the contractor safety hours must
be entered in the Safety Hours table (F54HS20). The system uses the HR supplemental
data to determine all of the employees for the establishment and then retrieves the
employee time cards. The system retrieves the payroll time cards directly by company.
The system retrieves all of the business units from the Business Unit Master table
(F0006) by project and then retrieves the time cards by business unit. The system
retrieves the payroll time cards directly by business unit.
3.5.1.1.3 Safety Hours Table as an Override to Payroll Tables Hours If you choose to use the
F54HS20 table to override the payroll hours, the system searches the Safety Hours
table first to determine the information. If it is not able to find a match, it will then look
in the payroll tables. The system cannot retrieve contractor hours from the payroll
tables, so the system will only look in the Safety Hours table for contractor safety
hours.
3.6.3 Setting Processing Options for the Task Inquiry Program (P54HS215)
Processing options enable you to specify the default processing for programs and
reports.
3.6.3.1 Process
1. Lock Assigned To Filter Field
You use this processing option to lock the Assigned To field and restrict from being
edited.
3.6.3.2 Versions
1. Incident Master (P54HS00)
You use this processing option to specify the version of the Incident Master program
(P54HS00). Incident Task Inquiry program will use this version's processing option to
3-22 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Generating the Task Tickler Reminder Report (Release 9.2 Update)
access the Incident Master when you select the Incident Number to drill down into the
incident record. If you leave this option blank, the system uses the default version
ZJDE0001.
(Release 9.2 Update) The Incident Master version will also define whether or not the
Send Reminder button will appear in the header of this application and will be used to
determine who will receive the message.
3.7 Generating the Task Tickler Reminder Report (Release 9.2 Update)
This section provides an overview of the Task Tickler Reminder program (R54HS420)
and discusses how to set up processing options for this program.
3.7.3 Setting Processing Options for Task Tickler Reminder Report (R54HS420)
Processing options enable you to specify the default processing for programs and
reports.
You can configure the Task Tickler Reminder Report through processing options that
control how tasks are selected based on the Task Ending Date and who will receive a
reminder message.
3.7.3.1 Process
1. Tickler Days
Use this processing option to specify the number of days + or - from the Task Ending
Date to send task reminders. If today is greater than or equal to the Task Ending Date
+ or - the specified tickler days, then the reminder notification will be sent for the task.
3-24 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Entering User Defined Incident Data (Release 9.2 Update)
■ Select Incident Master. On the Manage Incidents form, search for and select
the incident you want to update, and click the User Defined Data button
above the grid.
Note: The User Defined Data button is displayed only if you defined
a value for the Data Group processing option.
■ Select Incident Master. On the Manage Incidents form, search for and select
the incident you want to update. On the Edit Incident form, select the User
Defined Data Form exit.
2. On the Incident User Defined Data Revisions form, complete these fields:
■ Incident Number
When you populate this field, the system automatically populates the Incident
Record Type field.
■ Data Group
Select a data group that is associated with the incident record type for the
specified incident. If you select a data group that has not been set up for the
incident record type, the system issues an error.
3. In the detail area of the form, expand each of the three group box sections to view
the available fields.
4. Complete all necessary fields, and then click OK.
Figure 3–3 Incident User Defined Data Revisions - Personal Forms Manager
Use the descriptions below to understand the flexible fields that are displayed in the
Personal Forms Manager:
A
The field label, which you entered in the Data Description field when each field of the
data group was defined.
B
The date field, which has a field size of 6 characters.
C
The numeric field, which has a maximum field size of 15 characters and is used for
numeric fields and table-validated fields.
D
The alphanumeric field, which has a maximum field size of 50 characters and is used
for alphanumeric fields, time, and UDC associated fields.
3-26 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Entering User Defined Incident Data (Release 9.2 Update)
E
The associated description, which is used with UDC associated fields and
table-validated fields.
Tip: Depending on how the user defined data is defined for the data
group and how it is arranged using Form Personalization, you can
add some field labels, which would otherwise be unused, to add
additional text or lines on the personalized form.
3-28 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
4
Reporting Incidents
4
4.2 Generating the OSHA 300 Log Report and OSHA 300A Summary
Report
This section provides an overview of the OSHA 300 Log report and the OSHA 300A
Summary report and discusses how to:
4.2.1 Understanding the OSHA 300 Log Report and the OSHA 300A Summary Report
Use the OSHA 300 Log report to classify and report work-related injuries and illnesses,
including what happened, how it happened, and the severity and extent for each case.
Use the OSHA 300A Summary report to total the detailed case information for each
establishment for each calendar year. Employers must post the summary from the
previous year in a place where workers can view the report.
4.2.3 Setting Processing Options for OSHA 300 Log Report (R54HS300)
Processing options enable you to specify the default processing for programs and
reports.
4.2.3.1 Process
1. Enter Reporting Century/Year
Enter the century and year that the system uses for OSHA reports. If you leave this
processing option blank, the system uses the current century and year date.
4-2 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Generating the OSHA 300 Log Report and OSHA 300A Summary Report
Use this form exit to associate a company with an establishment and to define the
establishment type. This information is used when submitting an electronic file to
OSHA for the 300A report.
■ Row Exit Change Reason
Use this row exit to record a reason why you are re-submitting an electronic file to
OSHA. If there is more than one change reason given for the same
establishment/year/report type combination, the re-submitted electronic file will
use the one with the highest sequence number.
4.2.5 Setting Processing Options for OSHA 300A Summary Report (R54HS300A)
Processing options enable you to specify the default processing for programs and
reports.
4.2.5.1 Process
1. Enter Reporting Century/Year
Enter the century and year that the system uses for OSHA reports. If you leave this
processing option blank, the system uses the current century and year date.
2. Specify where safety hours and average number of employees are retrieved from
Specify how the system retrieves the safety hours. Values are:
Blank: Retrieve safety hours and from the Incident Safety Hours table (F54HS20). If
you leave this processing option blank, the system uses safety hour totals from the
F54HS20 table. You need to populate the table with your monthly safety hours for each
year being analyzed for each establishment.
1: Retrieve pay records from the Employee Transaction History table (F0618). If you
select 1, the system uses the payroll records to determine safety hours and from the
F0618 table. The system uses PDBA codes to account for vacation or leave time, which
are not considered part of safety hours.
2: Consider safety hour totals in the Incident Safety Hours table (F54HS20) an override
to pay records in the Employee Transaction History table (F0618). If you select 2, the
system first searches the safety hours in the F54HS20 table to find a record for
establishment unit and year being analyzed. If the system finds a match, it uses the
information in the table. If it does not, the system searches for any data in the F0618
table.
4. Title
Enter the title of the company executive that the system displays on the OSHA 300A
report.
5. Phone Number
Enter the phone number for the company executive that the system displays on the
OSHA 300A report.
6. Date
Enter the date that the system displays on the OSHA 300A report. If you leave this
processing option blank, the system uses the system date.
Note: The file path is a server path when the report is generated on a
server. To specify a local path you need to install the JD Edwards
application locally.
4-4 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Generating the Bureau of Labor Statistics (BLS) Survey Report (R54HS320)
4.3.3 Setting Processing Options for OSHA 301 Injury/Illness Report (R54HS301)
Processing options enable you to specify the default processing for programs and
reports.
4.3.3.1 Process
1. Enter Reporting Century/Year
Enter the century and year that the system uses for OSHA reports. If you leave this
processing option blank, the system uses the current century and year date.
2. Completed By
Enter the name that the system displays on the OSHA 301 report.
3. Title
Enter the title of the person who completed the report. The system displays the tile on
the OSHA 301 report.
4. Phone Number
Enter the phone number for the person who completed the report. The system
displays the phone number on the OSHA 301 report. The system displays the phone
number in Section 4 of the report.
5. Date
Enter the date that the system displays on the OSHA 301 report. If you leave the Date
processing option blank, the system uses the system date.
4.4.3 Setting Processing Options for the BLS Survey Report (R54HS320)
Processing options enable you to specify the default processing for programs and
reports.
4.4.3.1 Process
1. Enter Reporting Century/Year
Enter the century and year that the system uses for the BLS report. If you leave this
processing option blank, the system uses the current century and year.
2. Specify where safety hours and average number of employees are retrieved from
Specify how the system retrieves the safety hours and average number of employees.
This report uses the same logic as the OSHA 300A report (R54HS300A) to retrieve this
information. Values are:
Blank: Incident Safety Hours table (F54HS20)
1: Employee Transaction History table (F0618)
2: Use Incident Safety Hours table (F54HS20) as an override to pay records in the
Employee Transaction History table (F0618)
3. Account Number
Enter the account number assigned to the establishment by the Bureau of Labor
Statistics. The system prints the account number in Section 1 of the Survey of
Occupational Injuries and Illnesses report.
4. Completed By
Enter the name of the person completing the Bureau of Labor Statistics Survey of
Occupational Injuries and Illnesses report. The system displays the name in Section 4
of the report (Name).
5. Title
Enter the title of the person completing the Bureau of Labor Statistics Survey of
Occupational Injuries and Illnesses report. The system displays the title in Section 4 of
the report.
6. Phone Number
Enter the phone number of the person completing the Bureau of Labor Statistics
Survey of Occupational Injuries and Illnesses report. Enter the phone number in the
format that you want the system to display.
7. Phone Extension
Enter the phone extension of the person completing the Bureau of Labor Statistics
Survey of Occupational Injuries and Illnesses report. Enter the phone extension in the
format in which you want it to appear in the report. The system displays the phone
extension in Section 4 of the report.
8. Fax Number
Enter the fax number of the person completing the Bureau of Labor Statistics Survey of
Occupational Injuries and Illnesses report. Enter the fax number in the format in which
you want it to appear in the report. The system displays the fax number in Section 4 of
the report.
4-6 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Generating the Detailed Incident Report
4.5.3.1 Print
1. Print People Information by Incident Role
Specify the role of the person involved in the incident that you want to print in the
Detailed Incident report. Only people with the specified role will print on the report.
Value is:
Blank: Print All People
4-8 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
5
Using One View Reporting to Review Incidents
5
The One View Reporting programs for the JD Edwards EnterpriseOne Health and
Safety Incident Management system enable you to analyze incidents by the people
involved, equipment involved, key incident attributes, incident classifications, costs,
and environmental impact details. You can associate an incident with different types of
records, for example, people records, equipment records, and so on. These records are
associated to the incident in a one-to-many relationship, which means that an incident
can have many people or many equipment records associated with it. These records
are related to the incident, however, they may not be related to each other. You can also
associate an incident with other types of records, such as agencies, tasks,
environmental impact details and costs, in a one-to-many relationship. The One View
Reporting for Health and Safety Incident Management programs facilitate searching
and reporting on incidents, people, equipment, and environmental impact records,
and calculates safety metrics.
To search and report on agencies, tasks, and costs, you can use specialized business
views.
The system stores the each type of incident record in different tables as illustrated in
the following graphic.
5.2 Using Specialized Business Views for Additional One View Reporting
This section provides an overview of the specialized business views for additional One
View Reporting and discusses how to access the specialized business views for
additional One View Reporting.
5.2.1 Understanding Specialized Business Views for Additional One View Reporting
If you want to search across incidents for common agency or costs information, you
can use the additional specialized business views:
■ Incident and Agencies Join - One View business view (V54HS04B)
You can use the V54HS04B business view to search for agencies across all
incidents. For example, you can search for all incidents where a common agency
was involved. The V54HS04B business view has all the columns from the Incident
Master table (F54HS01), excluding the five audit fields and the four media object
fields, and all columns from the Incident Agencies table (F54HS04), excluding the
audit fields.
■ Incident and Costs Join - One View business view (V54HS07B)
You can use the V54HS07B business view to search for costs across all incidents.
For example, you can search for all incidents with the same cost types. The
V54HS07B business view has all of the columns from the Incident Master table
(F54HS01), excluding the five audit fields and the four media object fields, and all
columns from the Incident Costs table (F54HS07), excluding the audit fields.
5-2 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Using Specialized Business Views for Additional One View Reporting
5.2.2 Accessing the Specialized Business Views for Additional One View Reporting
To access the specialized business views, complete the following steps:
1. Enter Databrowser in the Fast Path field to access the Query Selector form.
2. On the Query Selector form, select the By Business View option and click on the
Visual Assist button for the Name field.
3. On the Business View Search & Select form, enter V54HS* in the Object Name
Query By Example (QBE) field and *One View in the Member Description QBE
field. The system displays the business views for the Health and Safety Incident
Management system in the grid.
4. After you select the business view you want, you can see and access all the
records. You can search the business views using the header fields, the Query By
Example (QBE) line, or the Advance Query features. You can export from the grid
using the Tools icon in the toolbar or build custom reports using the One View
icon.
5-4 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
6
Purging Incident Records
6
6.3.1 Process
1. Proof or Final Mode
Specify whether the system runs the Incident Management Purge report in proof or
final mode. Values are:
Blank: Proof mode
1: Final mode
6-2 JD Edwards EnterpriseOne Applications Health and Safety Incident Management Implementation Guide
Glossary
Complex Injury
An injury is complex when a person suffers from more than one injury or illness due
to a single incident.
Establishment
As defined by OSHA, an organization is an establishment if the organization is
involved in the same work activity and therefore exposed to the same risk. An
establishment for OSHA reporting purposes is defined as a single physical location
where like business is conducted or where services or industrial operations are
performed.
Glossary-1
Failure Analysis
Failure Analysis
The process of collecting and analyzing data to determine the cause of a failure.
Incident
An occupational health and safety event that can involve security, environmental
damage or exposure, motor vehicle incident or damage, asset or property damage, and
illness or injury.
Glossary-2
TRIF - Total Recordable Incident Frequency
Privacy Case
A case that is private in nature or the people involved in the case have requested to
keep the details of the case private. Privacy cases are reported without revealing the
person's name and with an alternate, less intimate description of their injury or illness.
Recordable Incident
An incident that has one or more employees injured or ill on the job.
Record Type
A user defined field to classify different uses of the incident master record. This is
useful when analyzing incidents.
Safety Hours
The hours defined as hours that an employee has worked or is available to work.
Glossary-3
Workers Compensation
Workers Compensation
A form of insurance that provides wage replacement and medical benefits to
employees injured in the course of employment. An employer provides this insurance
in exchange for mandatory relinquishment of the employee's right to sue the employer
for negligence.
Glossary-4