TMS – Timeplan

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)DescriptionMandatory / OptionalData transformation/load rulesTimeplan data element (source)Comment
1Property IDID of the property (hotel, restaurant)Mn/a
2Property NameName of the property (hotel, restaurant)Mn/a
3Department IDID of the department within the propertyMn/a
4Department NameName of the department within the propertyMDirectly mapped to source equivalentCostcenter
5DateWorking date (timesheet)MDirectly mapped to source equivalentDate
6TimeCategory IDn/aM
7TimeCategory NameName of the time category (e.g. Fixed Salary, Absence)Mn/a
8JobCategory IDID of the job categoryOn/a
9JobCategory NameName of the job category (e.g. Servers, Managers)ODirectly mapped to source equivalent but is numericAccount
10Staff IDID of the staff (employee)Mn/a
11HoursNumber of hours (on the timesheet)MExists in minutes. Transformation rule: minutes divided by 60 to get number of hours in PMIBalance
12ApprovedIf the hours are approved or notMn/aEverything is treated as approved.

Download an example of the source file format: n/a

Was this article helpful?

Related Articles