Key user profiles:
HR [can we be more specific - which role, which teams?]
Managers
VERSION | DATE | MODIFIED BY | DESCRIPTION |
0.01 | 25.09.2023 | Emma Glasson | Initial draft |
| Data Product Type |
|
| Technologies |
|
Data Sources Note: list of all applications and various environment |
|
2.0 Business Process
Every year, employees have to meet objectives that they have registered themselves in collaboration with their managers. These objectives are then used to carry out their end-of-year assessment. Once this assessment has been completed, management assigns them a performance grade ranging from 1 to 5.
To help them improve, company employees can also ask their colleagues for feedback on their work, and send feedback to colleagues who have asked for it.
All these actions took place between 2018 and 2020 in a tool called YOU. It was an HR tool, helping to monitor performance and assist talent management. It also contained information on employee mobility, such as geographical changes or changes of position within the company.
Since 2021, the tool has been decommissioned and the same actions are carried out on the Success Factor tool.
what is the report used for? who uses it? what is the output? does this link report is input for something?
3.0 Application Feature Overview
| Reports | Definition | Prompts | BW Workbook Query | Query Technical Name |
|---|---|---|---|---|
| Certification Complexion Details | Functional roles Calendar Year / Month Employee Class Category | n.a | BW_QRY_CPHRLS003_0001 | |
| Course Completion Details | BW_QRY_CPHRLS001_0001 | |||
| Curriculum Completion Details | BW_QRY_CPHRLS002_0001 | |||
| Learning Forecast | Functional roles Calendar Year / Month | BW_QRY_CPHRLS001_0002 | ||
| Training Management (Historic) | ORGUNIT Year | BW_QRY_CPHRLHST_0001 |
mandatory field
4.0 Functional Specification
4.1 General Data/Calculations
Please find bellow general dimension, commun to all BW HR reports:
| Dimension | Definition |
Company Code | Company code to which an employee belongs on the time period selected in the report |
Country of the company | Country of company where the employee has his employment contract |
Calendar | Time dimensions available: Day, Month, Year, Year/Month |
Division (Entity) | Division (former entity) to which an employee belongs on the time period selected in the report |
Employee NR (NS) Employee PERN | Employee payroll number |
Employee status | Active, Active Leave, Inactive Leave Dormant, reported No Show Terminated, Inactive |
Employment status | Valid for historical data - the period before 1 November 2020. Equivalent to the current dimension Employee status |
Employee sub-group grouping (Gr) | Identification of employee by:
The employee sub-group grouping is a grouping definition of the employment type. |
Location Grp (Site) | Employee’s site |
Person ID | Unique identifier code for an employee. EC number. (person name available in the text option for this dimension) |
User Name | User account name (to access system/tool) |
4.2 Process Detail
4.2.1. Report/Process Definition
| Domain | Human Resources (HR) |
|---|---|
| Application | BW Learning Queries |
| Provider | CPHRLS |
| Existing Documentation |
4.2.2. KPI's/Calculations/Indicators
Report Certification Complexion Details:
Indicators/KPI's | Definition | Calculation/Extraction of data |
|---|---|---|
Report Course Completion Details:
Indicators/KPI's | Definition | Calculation/Extraction of data |
|---|---|---|
Report Curriculum Completion Details:
Indicators/KPI's | Definition | Calculation/Extraction of data |
|---|---|---|
Report Learning Forecast:
Indicators/KPI's | Definition | Calculation/Extraction of data |
|---|---|---|
Report Training Management (Historic):
Indicators/KPI's | Definition | Calculation/Extraction of data |
|---|---|---|
5.0 Non-functional Descriptions
5.1 Usability
as per standards
5.2 Regulatory Compliance
GDPR compliant. Report that contain confidential data but no sensitive data.
5.3 Security
- Only authorised Users be able to access data.
- Data will be split between either SCO or ECO, and Users will only have authority to one Entity data.
5.4 Performance
as per standards
5.5 Reliability
as per standards
5.6 Scalability
as per standards
5.7 Compatibility
as per standards
5.8 Availability
as per standards