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