BeyondERP.Newsletter
Menu

Setup step on the OSHA 300 log prep report page · Human resources

Prepare the OSHA 300 log per establishment

Prepare the OSHA record from complete incident cases (US only).

Business process
Audit workplace for safety
Menu item
HcmOSHA300LogPrepReport
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA report that gives the data needed to prepare the OSHA 300 log of workplace injuries and illnesses (USA).
What you do hereUse this report to collect recorded injury and illness incidents for a period and workplace location so you can fill in the OSHA 300 log.
ExampleFor example, for its US warehouse establishment BEAT runs the report for 1 January to 31 December 2026 and gets the 4 recordable cases to enter in the OSHA 300 log.
OSHA 300 log prep report page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

When to run it

When to run itWhen you prepare or update the OSHA 300 log of recordable workplace injuries and illnesses for a US establishment.
How oftenOn demand, whenever a recordable case is added, and at year end before you prepare the annual summary.
What the output showsThe recorded injury and illness cases for one establishment and period, with the data you need for the OSHA 300 log. A missing case usually has the wrong establishment or an incident date outside the period.

Source: Microsoft Learn

Setup steps on this page

Prepare the OSHA 300 log per establishment

Prepare the OSHA record from complete incident cases (US only).

Steps from Microsoft

  1. Go to Human resources > Workers > Injury and illness > OSHA 300 log prep report.
  2. Under Parameters, set the From date and To date of the reporting period, usually the calendar year of the log.
  3. Select the Regulatory establishment, the workplace location the log is for. Run the report once for each establishment.
  4. Use Case number to include one case or a range of case numbers when you only need part of the log.
  5. Copy the case data into the OSHA 300 log and compare the number of cases with your incident list for the establishment.

Source: Microsoft Learn

Fields on the page

FieldWhat it means
From dateThe first date of the reporting period.Microsoft Learn
To dateThe last date of the reporting period.Microsoft Learn
Regulatory establishmentThe workplace location the report is for.Microsoft Learn
Case numberA case number or range of case numbers to include.Microsoft Learn

Common errors and fixes

MessageWhat to do
A case with a known number isn't on the reportWhen both dates and case numbers are entered, only cases matching both are found. Widen the dates or clear the case number range. Microsoft Learn
Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Prepare the OSHA 300 log per establishmentRun it per regulatory establishment for the calendar year, and again whenever a recordable case is added.The report collects the incidents with worker, position, injury type, outcome and body part for one establishment, the data the OSHA 300 log needs.How is the OSHA 300 log kept?Combining a date range with a case number range that doesn't fall inside it: such a case isn't found.Test: Prepare the OSHA 300 log per establishment

Feature management and licence

Licence or add-inHR and safety staff of US legal entities prepare OSHA records from these reports. No Feature management feature is needed for this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyPer company data, US only: the OSHA reports read injury or illness incidents, which Data management lists as not shared, and are run per regulatory establishment, the workplace location (Data management lists Regulatory establishments as shared). Checked in Dynamics 365
Can it be undoneNothing to undo: The report only reads data.
Feature or countryUS
If you change it laterThe report reads the incidents, workers, positions, employments, injury types, outcomes, body parts and the regulatory establishment, so a change to any of them shows on the next run. Microsoft Learn
Technical architect

6Technical

Menu itemHcmOSHA300LogPrepReport Checked in Dynamics 365
FormSysOperationTemplateForm Checked in Dynamics 365
Roles to set it up and use itTo use itHuman resource manager HcmHumanResourceManagerHuman resource assistant HcmHumanResourceAssistantCompensation and benefits manager HcmCompensationAndBenefitsManagerGive people one of these roles. On this system, 3 roles can run this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=HcmOSHA300LogPrepReport
Data migrationLoad order: The OSHA 300 log prep report has no data entity in Data management, so it can't be loaded from a file or a configuration template. It reads the incidents, workers and regulatory establishments; load those and run the report in each environment.Microsoft Learn
Everyone

8Sources

To cite this step: HR-RWRK-160, Prepare the OSHA 300 log per establishment. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/HR-RWRK-160