TMS – Mirus

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.

#PMI data element (target)DescriptionMandatory / OptionalData transformation/load rulesMirus data element (source)Comment
1Property IDID of the property (hotel, restaurant)MDoes not exist in file. ID provided by local PMI agentN/A
2Property NameName of the property (hotel, restaurant)MDoes not exist in file. ID provided by local PMI agentN/A
3Department IDID of the department within the propertyM3rd column (from left in the file)3rd column
4Department NameName of the department within the propertyMDoes not exist in fileN/A
5DateWorking date (timesheet)M1st column (from left in the file)1st column
6TimeCategory IDID of the time categoryM4th column (from left in the file)4th column
7TimeCategory NameName of the time category (e.g. Fixed Salary, Absence)MDoes not exist in the fileN/A
8JobCategory IDID of the job categoryODoes not exist in the fileN/A
9JobCategory NameName of the job category (e.g. Servers, Managers)ODoes not exist in the fileN/A
10Staff IDID of the staff (employee)M2nd column (from left in the file)2nd
11HoursNumber of hours (on the timesheet)M5th column (from left in the file)5th column
12ApprovedIf the hours are approved or notMDoes not existN/AAll hours in the file are approved hours. Non-approved hours are excluded in the export setting in Mirus.

Download an example of the source file format: File:EXPORT MIRUS.zip

Was this article helpful?

Related Articles