Contents

What data is synced from Time & Attendance to Auto-Rostering?

Kellie Oxley Updated by Kellie Oxley

Time & Attendance to Auto-Rostering

The following data is synchronised from your Time & Attendance application to Auto-Rostering.

Employees

Every Time & Attendance employee which is selected in the Time & Attendance Auto-Rostering setup wizard is created in Auto-Rostering (Provisioned) and the following data is synchronised from Time & Attendance into Auto-Rostering.

T&A entity

Events

Comments

Employee

Created

Updated

Deleted

Employee deletion is a hard delete and will be removed from Time & Attendance and Auto-Rostering.

Employee-contract

Updated

eg; Employee Leave date changed

Employee-organisation

Updated

eg; Employee Department changed

Employee-job

Updated

eg; Employee Job title changed

Employee Data (Lookups)

Every T&A Organisation-lookup (LOCATION) is provisioned and the following synced:

T&A entity

T&A DB field

Rostering field

Events

Comments

Organisation-lookup (LOCATION)

LUORG.Code + LUORG.Description

Location value

Created

Updated

Deleted

Every T&A Organisation-Lookup (LOCATION) is provisioned to Auto-Rostering

Organisation-lookup (DEPARTMENT)

LUORG.Code + LUORG.Description

Department value

Created

Updated

Deleted

Every T&A Organisation-lookup (DEPARTMENT) is provisioned.

Organisation-lookup (COSTCODE)

LUORG.Code + LUORG.Description

Costcode value

Created

Updated

Deleted

Every T&A Organisation-lookup (COSTCODE) is provisioned

Organisation-lookup (DIVISION)

LUORG.Code + LUORG.Description

Division value

Created

Updated

Deleted

Every T&A Organisation-lookup (DIVISION) is provisioned

Loopup (JOBTITLE)

LOOKUP.Code + LOOKUP.Description

Job Title

Created

Updated

Deleted

Every T&A Lookup (JOBTITLE) is provisioned

Employee details

Rostering field

T&A entity

T&A DB field

Comments

Username

Employee

TMSEMP.EmpRef

Required, unique

First Name

Employee

TMSEMP.FirstNames

Required

Last Name

Employee

TMSEMP.Surname

Required

Email

Employee

TMSEMP.Email

Required, unique

Start Date

Employee-contract

CE.StartDate

Required, must be before leave date

Leave Date

Employee-contract

CE.LeaveDate

-

Location

Employee-organisation

OD.Location

[Employee Data (Lookups) entity mapping]

Department

Employee-job

JD.JobTitle

Job Titles linked to Per.UseJobAndJobDef preference are not supported.

[Employee Data (Lookups) entity mapping]

Weekly hours

Employee-contract

CE.WeeklyHours

-

Absence Codes

Every T&A Absence-hours-code is provisioned to Auto-Rostering.

Rostering field

T&A entity

T&A BD field

Comments

Name

Absence-hours-code

TMSAC.Descrip

Required, unique

Colour

Absence-hours-code

Hardcoded as #dc4405 (red-orange)

Employee Absences

From T&A employee planned absence, the following are provisioned and synced:

Rostering field

T&A entity

Event

T&A BD field

Comments

Absence Code

Employee-planned-absence

Created

Deleted

TMSFC.Code

Required. [Absence Code entity mapping]

Absence Start

Employee-planned-absence

Created

Deleted

TMSFC.StartDate

Required.

Absence Start Time

Employee-planned-absence

Created

Deleted

TMSFC.StartTime

If using T&A Non-rostered absence functionality

Absence End

Employee-planned-absence

Created

Deleted

TMSFC.EndDate

Required.

Absence End Time

Employee-planned-absence

Created

Deleted

TMSFC.EndTime

If using T&A Non-rostered absence functionality

Absence Hours

Employee-planned-absence

Created

Deleted

TMSFC.Hours

Note: Employee-planned-absence does not have a unique ID so updates are performed by deleting and re-adding.

From T&A general absence instance for employee, the following are provisioned:

Rostering field

T&A entity

T&A BD field

Comments

Absence Code

General-absence

Code

Required. [Absence Code entity mapping]

Absence Start

General-absence

StartDate

Required

Absence End

General-absence

EndDate

Required

Absence Hours

General-absence

Hours

Note: General-absences are not yet included in sync (they are transferred during provision only)

Skill Codes

Every T&A Skill-code is provisioned and the following events synced:

Rostering field

T&A entity

Events

T&A BD field

Comments

Name

Skill-Code

Created

Updated

Deleted

TMSCSKLL.Code

Required, Unique

Description

Skill-Code

Created

Updated

Deleted

TMSCSKLL.Descrip

Employee Skills

From T&A skill, the following are provisioned and synced:

All Employee-skills are provisioned

Rostering field

T&A entity

Events

T&A BD field

Comments

Skill Code

Employee-skill

Created

Deleted

TMSEMPSK.SkillCode

Required [Skill Code entity mapping]

From T&A qualification (dependent on configuration) the following are provisioned:

All Employee-qualifications are provisioned

Rostering field

T&A entity

T&A BD field

Comments

Skill Code

Employee-qualification

QUAL. *

[Skill Code entity mapping]

Note: Employee-qualifications are not yet included in sync

From T&A training record (dependent on configuration) the following are provisioned:

All Employee-training-record are provisioned

Rostering field

T&A entity

T&A BD field

Comments

Skill Code

Employee-training-record

**

[Skill Code entity mapping]

Note: Employee-training-record are not yet included in sync
Note: Skills are not treated as an entity when provisioned/synced (i.e. a link is not kept between the T&A and Rostering records). Skill Codes are simply assigned and unassigned from employees.

Shifts (shift definitions)

Every T&A ‘named shift’ is provisioned (personalised shifts are not provisioned) and synced as follows:

Rostering field

T&A entity

Events

T&A BD field

Comments

Group

Shift

Created

Updated

Deleted

-

Hardcoded as 'T&A'

Code

Shift

Created

Updated

Deleted

TMSWS.Ref

Required

Description

Shift

Created

Updated

Deleted

TMSWS.Descrip

Start Time

Shift

Created

Updated

Deleted

TMSWS.StartDay

Required. No time zone offset applied

End Time

Shift

Created

Updated

Deleted

TMSWS.EndDay

Required. No time zone offset applied

Hours

Shift

Created

Updated

Deleted

TMSWS.StdHours

Required

Auto-Rostering to Time & Attendance

Nothing is provisioned from Auto-Rostering to Time & Attendance, however the following details below highlight the on going transfer of data that is synchronised from Auto-Rostering to Time & Attendance in response to certain events.

Rostering entity

Event

Example

Comments

Schedule publish

Created

User selects 'Publish' for date range within a schedule

Created event is triggered and schedule sync request is created with state 'Pending'

Created Event:

  • Any previously created planned shifts for the same Auto-Rostering schedule within the Schedule publish date range are deleted in T&A.
  • For each job assignment in the Schedule publish;
    • An employee planned shift (read-only) is created in T&A and every field in the relevant Field mapping table is populated.
    • An error is logged if employee planned shift cannot be created in T&A.
    • An info message is logged if employee planned shift is successfully created in T&A.
    • If a ‘Rostered job’ TAS category (unvalidated type) is defined for ‘Job Type’, then a planned rostered job is created for the duration of the Shift, as per Field mapping table.
    • For each custom data value for the job;
      • If a ‘Rostered job’ TAS category (lookup type) is defined for matching lookup, then a planned rostered job is created for the duration of the Shift, as per Field mapping table.
      • An error is logged if Rostered job cannot be created in T&A.
  • Result is sent back to Auto-Rostering containing;
    • The status of the Schedule publish - 'Success' or 'Error'.
    • A message for each job assignment with status 'Error' including a message

Schedule publish (Job assignments)

Assignment for job shift selected ('Shift job') are provisioned:

Rostering field

T&A entity

T&A BD field

Comments

Employee

Employee-planned-shift

TMSFC.EmpRef

[Employee entity mapping]

Shift

Employee-planned-shift

TMFC.Code

[Shift entity mapping]

Start Date

Employee-planned-shift

TMSFC.StartDate

Assignment for job without shift selected ('Time job') are provisioned:

Rostering field

T&A entity

T&A BD field

Comments

-

Shift (personalised)

TMSWS.Ref

Generated

Start Time

Shift (personalised)

TMSWS.StartDay

End Time

Shift (personalised)

TMSWS.EndDay

Hours

Shift (personalised)

TMSWS.StdHours

Employee

Employee-planned-shift

TMSFC.EmpRef

[Employee entity mapping]

-

Employee-planned-shift

TMSFC.Code

Matching generated TMSWS.Ref

Start Date

Employee-planned-shift

TMSFC.StartDate

Job Type for job (optional) are provisioned:

Rostering field

T&A entity

T&A BD field

Comments

-

Rostered-job

TMSWSJOBS.EmpRef

As per TMSFC.EmpRef for Employee-planned-shift

-

Rostered-job

TMSWSJOBS.WsRef

As per TMSFC.Code for Employee-planned-shift

-

Rostered-job

TMSWSJOBS.WsDate

As per TMSFC.StartDate for Employee-planned-shift

-

Rostered-job

TMSWSJOBS.TasCode

Mapped to unvalidated TAS category selected for Job Type from Time & Attendance 'rostered jobs' configuration in Auto-Rostering setup wizard

Job Type

Rostered-job

TMSWSJOBS.TasValue

Text description of Job Type from Auto-Rostering

Custom data value for job (optional) are provisioned:

Rostering field

T&A entity

T&A BD field

Comments

-

Rostered-job

TMSWSJOBS.EmpRef

As per TMSFC.EmpRef for Employee-planned-shift

-

Rostered-job

TMSWSJOBS.WsRef

As per TMSFC.Code for Employee-planned-shift

-

Rostered-job

TMSWSJOBS.WsDate

As per TMSFC.StartDate for Employee-planned-shift

Custom data type

Rostered-job

TMSWSJOBS.TasCode

Mapped to TAS category with matching lookup from Time & Attendance 'rostered jobs' configuration in Auto-Rosrering setup wizard

Was this article useful?

Auto-Rostering overview

Schedule Setup

Contact