Purpose
This view combines employee data (DIM_EMPLOYEE_OL) with absence details (QFACT_ABSENCE_DETAILS_OL$) to facilitate the creation of a dataset used for tracking and analysing employee absences in detail. It generates structured JSON data for efficient reporting, compliance, and analytical purposes.
Use Case
Owner: Luisa Winder
Typical Use Case:
- Employee Data Reporting: Generate JSON data for dashboards or analytical tools focused on employee absences.
- Integration with APIs: Provide structured JSON data for external systems or applications that require employee and absence information.
- Compliance and Auditing: Create detailed absence records for auditing and compliance purposes.
- HR Analytics: Analyse trends such as absence durations or illness patterns at a granular level.
Style: Fact, Each row represents a unique Employee Absence Seq with associated dates.
Source
QFACT_ABSENCE_DETAILS_OL$DataMart Integration
This view can be utilised across the following DataMarts:
- Employee
- Company
Sample Exec
For sample data execution, use the code:
EXEC get.myView @dataMart = 'Employee', @viewName = 'Absence', @token = '<myToken>', @version = '<202404>'Response
Identifiers
COMPANY: The company identifier.EMP_NO: The employee number.EMPLOYEE_SEQ: A JSON object that uniquely identifies the employee.
Absence
A JSON object detailing the employee’s absence, including:
DURATION: Total duration of the absence.PERIOD_NO: The period number associated with the absence.ABSENCE_ID: Unique ID of the absence.START_DATEandEND_DATE: The dates defining the absence period.ILLNESS CODE: Code related to illness, if applicable.
SQL
To access the full SQL structure, refer to…
BMT-DWH-DEV/Employee_Absence.sql