PMI Knowledge base

Back to Knowledge base

More results...

Generic filters
Exact matches only
Search in title
Search in content
Search in excerpt
Filter by Custom Post Type
PMI Knowledge Base
Article contents (TOC)
Print

TMS – Tidsbanken

June 1, 2020
UpdatedJune 1, 2023
ByAndreas Engkvist
Views1721
Please Share Your Feedback
How Can We Improve This Article?

The table below shows the data relationship between PMI data elements/fields (target) and corresponding source data elements/fields (source).

You will find the transformation/load rules meant to explain any programmatic manipulation and calculation applied in the adapter to get the desired data format and/or result in the PMI staging table where such have been applicable.

An example of the source file data, format and structure is also attached below the table.

This table will be updated whenever the source file or the adapter in question are changed throughout the interface life-cycle.

1
2
3
4
5
6
7
8
9
10
11
12
PMI data element (target)
Property ID
Property Name
Department ID
Department Name
Date
TimeCategory ID
TimeCategory Name
JobCategory ID
JobCategory Name
Staff ID
Hours
Approved
Description
ID of the property (hotel, restaurant)
Name of the property (hotel, restaurant)
ID of the department within the property
Name of the department within the property
Working date (timesheet)
ID of the time category
Name of the time category (e.g. Fixed Salary, Absence)
ID of the job category
Name of the job category (e.g. Servers, Managers)
ID of the staff (employee)
Number of hours (on the timesheet)
If the hours are approved or not
Mandatory / Optional
Mandatory
Mandatory
Mandatory
Mandatory
Mandatory
Mandatory
Mandatory
Optional
Optional
Mandatory
Mandatory
Mandatory
Data transformation/load rules
Exists but not used. See Property Name below
Directly mapped to source equivalent
Exists but not used. See Department Name below
Directly mapped to source equivalent
Derived from date and time string
Exists but not used. See TimeCategory Name below
Mapped to PMI equivalent
Exists but not used. See JobCategory Name below
Directly mapped to source equivalent
Exists but not used
Exists in minutes. Transformation rule: minutes divided by 60 to get number of hours in PMI
Approved and to-be-approved hours exist. Loading rule: only import approved hours
Planday data element (source)
PortalId
PortalName
DepartmentId
DepartmentName
Start
TimesheetTypeID
TimesheetTypeName
EmployeeGroupID
EmployeeGroupName
EmployeeID
Minutes
TimeSheetApproved
Comment
This is needed to separate productive and non-productive hours
Not presented at staff level, but at job category and date level
All hours included in the file are approved in Planday