Search Results per_work_incidents

Overview

The PER_WORK_INCIDENTS table is a core data object within the Oracle E-Business Suite Human Resources (PER) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary repository for recording occupational health and safety incidents. As indicated by its description, the table is designed to hold information on incidents that occur at work or en route to work, such as industrial accidents. This functionality is critical for organizations, particularly in industrial and manufacturing environments, to manage compliance, track safety performance, and administer related employee benefits and medical assessments. The table's role is integral to the system's ability to support workplace safety management and regulatory reporting requirements.

Key Information Stored

The table's primary key is the INCIDENT_ID, a unique identifier for each recorded incident. A notable structural feature is the presence of a self-referencing foreign key via the RELATED_INCIDENT_ID column, which allows for linking incidents that are related to one another. While the full column list is not detailed in the provided metadata, based on its purpose, the table typically stores data such as the incident date and time, location, description, severity, the involved employee's identifier (likely PERSON_ID), the nature of injury or illness, whether it was work-related, and status fields for investigation and closure. The foreign key relationships confirm it stores the foundational data for associated disabilities and medical assessments.

Common Use Cases and Queries

This table is central to industrial safety management and reporting. Common use cases include logging a new accident for an employee in an industrial engineering role, investigating the root cause, and tracking subsequent medical treatments and disability claims. For reporting, organizations generate metrics like Total Recordable Incident Rate (TRIR) or analyze trends by department or job role. A typical query might retrieve all incidents for a specific work location or employee within a date range. For example: SELECT incident_id, incident_date, description FROM hr.per_work_incidents WHERE person_id = 12345 ORDER BY incident_date DESC; Another common pattern involves joining with the PER_ALL_PEOPLE_F table to get employee names and details for comprehensive safety reports, ensuring compliance with occupational health regulations relevant to "gestión industrial."

Related Objects

PER_WORK_INCIDENTS has defined relationships with several other key HR tables, forming a cohesive data model for incident management. The primary foreign key dependencies are:

• PER_DISABILITIES_F: References PER_WORK_INCIDENTS.INCIDENT_ID, linking an incident to any resulting long-term or temporary disability records for the employee.
• PER_MEDICAL_ASSESSMENTS: References PER_WORK_INCIDENTS.INCIDENT_ID, connecting the incident to subsequent medical evaluations and treatments.
• Self-Reference: The table references itself via PER_WORK_INCIDENTS.RELATED_INCIDENT_ID, enabling the grouping of connected incidents.

These relationships ensure data integrity and facilitate comprehensive tracking from the initial incident through its medical and administrative consequences.