Purpose
This view creates a structured dataset for tracking and analysing employee absence limits. It links employee details (DIM_EMPLOYEE_OL) with their corresponding absence limit information (QFACT_ABSENCE_LIMIT_OVERVI_OL$), presenting the data in JSON format for improved integration and usability.
Use Case
Owner: Luisa Winder
Typical Use Case:
- Employee Data Reporting: Generate JSON data for dashboards or analytical tools focused on absence limits.
- Integration with APIs: Provide structured JSON data for systems requiring absence limit information.
- Compliance and Auditing: Maintain detailed records of absence limits, including usage and remaining values, for auditing purposes.
- HR Analytics: Enable detailed analysis of absence types, limits, and utilisation trends to support workforce planning.
Style: Fact, Each row represents a unique Employee Limit Seq with associated details for absence limits.
Source
QFACT_ABSENCE_LIMIT_OVERVI_OL$DataMart Integration
This view can be utilised across the following DataMarts:
- Company
- Employee
Sample Exec
EXEC get.myView @dataMart = 'Employee', @viewName = 'AbsenceLimit', @token = '<myToken>', @version = '<202404>'Response
Identifiers
COMPANY: The company identifier.EMP_NO: The employee number.EMPLOYEE_SEQ: A JSON object uniquely identifying the employee.
LIMIT
A JSON object detailing the employee’s absence limit, including:
ABS_TYPE: Type of absence associated with the limit.
LIMIT_SEQ:
ABS_TYPE: Absence type ID.SEQ_NO: Sequence number of the absence limit.SESSION: Session ID of the limit record.TYPE: Type of limit (e.g., fixed, rolling).
PERIOD:
START_DATE: Start date of the limit period.END_DATE: End date of the limit period.
VALUE:
DAYS: Total absence days allowed.USED: Absence days used.REMAIN: Remaining absence days.