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.
NB.This import uses the HIDXXX folder structure and the hard coded “siteId” to determine the property. This means that the property needs to be defined in the TimeSystem_Properties_External table.
|#||PMI data element (target)||Description||Mandatory / Optional||Data transformation/load rules||Timeplan data element (source)||Comment|
|1||Property ID||ID of the property (hotel, restaurant)||M||n/a|
|2||Property Name||Name of the property (hotel, restaurant)||M||n/a|
|3||Department ID||ID of the department within the property||M||n/a|
|4||Department Name||Name of the department within the property||M||Directly mapped to source equivalent||Costcenter|
|5||Date||Working date (timesheet)||M||Directly mapped to source equivalent||Date|
|7||TimeCategory Name||Name of the time category (e.g. Fixed Salary, Absence)||M||n/a|
|8||JobCategory ID||ID of the job category||O||n/a|
|9||JobCategory Name||Name of the job category (e.g. Servers, Managers)||O||Directly mapped to source equivalent but is numeric||Account|
|10||Staff ID||ID of the staff (employee)||M||n/a|
|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||Balance|
|12||Approved||If the hours are approved or not||M||n/a||Everything is treated as approved.|
Download an example of the source file format: n/a