TMS – Kronos

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.
Because the Time interfaces are still maintained in the old import structure, their name starts with: ‘I_T7_DD_’.

Interface name incl. versionComment
I_T7_DD_KRONOS_TIME_V002File name pattern: Kronos_pmitime*
#PMI data element (target)DescriptionMandatory / OptionalData transformation/load rulesData element (source)Comment
1Property NameName of the property (hotel, restaurant)MDirectly mapped from source fileLABORLEVELDSC1Property name is used to validate if the row needs to be imported (hard coded).
2Department NameName of the department within the propertyMDirectly mapped from source fileLABORLEVELDSC2
3DateWorking date (timesheet)MDirectly mapped from source fileAPPLYDATE
4TimeCategoryName of the time categoryMDirectly mapped from source filePAYCODENAME
5JobCategoryName of the job/task categoryMDirectly mapped from source fileLABORLEVELDSC3
6Staff IDID of the staff (employee)MDirectly mapped from source filePERSONNUM
7HoursNumber of hours (on the timesheet)MDirectly mapped from source fileTIMEINSECONDSOriginal header: sum( cast( [TIMEINSECONDS] as decimal ) / 3600 )
8ApprovedIf the hours are approved or notOApproved and to-be-approved hours exist. Loading rule: only import approved hoursNot in source fileAll hours included in the file are approved

Download an example of the source file format: File:I T7 DD KRONOS TIME

Was this article helpful?

Related Articles