🧾 Overview This view provides attribute-level values related to employee absence and leave entitlements, enabling structured DataMart-level analysis across both transactional absence events and annual entitlement summaries. 📚 Description The Employee Item Codes Absence view translates raw absence and entitlement data into attribute-coded rows that support dimensional modelling. Each row identifies: 🏗️ Source Tables 📦 … Read more
Purpose This view is part of the Common Data Standard, following an item and codes style table structure, ensuring consistency in data modelling across financial and operational datasets.The Employee Item Codes Expense view provides structured details on the various codes associated with employee expense items. It captures key attributes such as expense type, cost centre, … Read more
Purpose This view is part of the Common Data Standard, following an item and values style table structure, ensuring consistency in data modelling across financial and operational datasets.The Employee Item Value Expense view provides detailed information about individual expense items attributed to employees. It captures various expense attributes, including expense type, gross pay amount, and … Read more
In its most basic definition, sensitive data is a specific set of “special categories”: Article 9 of the GDPR prohibits special category data from being processed unless you can rely on an exemption.
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 WinderTypical Use Case: Style: Fact, Each row represents a unique Employee Limit Seq with … Read more
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 WinderTypical Use Case: Style: Fact, Each row represents a unique Employee Absence Seq with … Read more
Purpose: The purpose of this DataMart view is to provide a comprehensive timeline overview of a project’s key dates, from its creation to completion. It consolidates important project milestones such as planned and actual start and finish dates, delivery estimates, and project modifications. This view is designed to help stakeholders monitor project timelines, identify delays, … Read more
Purpose: The purpose of this DataMart view is to provide a clear snapshot of an employee’s current and historical employment status within a company. It captures essential details such as employment dates, employment type, and agreement, with a focus on determining whether an employee is currently active or not. This view is useful for HR … Read more
Purpose The Employee Leave Entitlement fact table is designed to display quantitative data related to employees. This table integrates with dimension tables, such as employee_details_plus, to provide detailed insights into various aspects of employee performance, compensation, and other metrics. The primary purpose is to support data-driven decision-making across the organisation. Use Case Owner: Sam Jopson-WhiteTypical … Read more
Purpose The Common View for Resource Details, excluding dates or measures, acts as a unified and reliable source for data on project resources. It is accessible to different departments and systems across the organisation. This view supports integration with fact tables for reporting and analysis and provides a limited set of dimension attributes. Use Case … Read more