OSHA 300 Log is not Picking Up Job Transfer or Restriction Days that Fall on the Next Calendar Year

(Doc ID 2304898.1)

Last updated on SEPTEMBER 08, 2017

Applies to:

PeopleSoft Enterprise HCM Human Resources - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

If an Employee had an injury on 12/31/2016, and have job transfer or restriction days recorded for the next calendar year, for example: 1/11/2017-1/27/2017 & 1/4/2017 -1/10/2017. The OSHA 300 Log for 2016 is not picking up this employee.

However, the 24 Restricted Workdays should be listed on the OSHA 300 Log for 2016 since the injury took place in 2016.


The issue can be reproduced at will with the following steps:
1. Enter 2016 Incident, Navigation: Main Menu > Workforce Monitoring > Health and Safety > Obtain Incident Information > Incident Details
2. Enter 2016 Accident and 2017 Restriction days, Navigation: Workforce Monitoring > Health and Safety > Obtain Incident Information > Injury Details
3. Run OSHA 300 Log for 2016, Navigation: Main Menu > Workforce Monitoring > Meet Regulatory Requirements > Regulatory Reports > OSHA 300 Incident Log
4. Note that the employee is missing for an injury that took place in 2016

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms