Schedule Detail Import Interface logic

Employee schedules are generated or created and over time they are modified or even deleted. The Schedule Detail Import mechanism can handle all these scenarios when used as described in this section.

When the schedule is exported as a CSV file, the file represents a snapshot of the current schedule of employees for a given set of days. Each line in the CSV file belongs to a given employee for a given day. On a given day, an employee can have multiple details, each on a separate line in the CSV file. The first three columns (OP_TYPE, EMP_NAME, and SKD_DATE) on each line are always required. See Schedule Detail Import Interface field specification.

The OP_TYPE field can have a value of I or D. The value I indicates that this line has a detail that needs to be inserted. The value D indicates that on the given day the employee currently has no schedule. Therefore, there can be multiple lines in the file with same employee and date of type I records.

When the Schedule Detail Interface sees a D record, the interface cancels all of the existing schedule details for that employee on the SKD_DATE. If the interface sees one or many I records for a given employee on a given day, the previous detail records are cancelled and the new records reflect the current schedule for that day. For any change in schedule, the export file should include every detail that the employee has for the given day. A schedule for a given day that was exported previously does not need to be exported out unless there is a modification. Any external system that is exporting schedule detail must adhere to this procedure so that new schedules, modified schedules, and schedule deletes can be accommodated through the same interface.

The EMP_NAME is a unique identifier for the employee. This ID is used to map the employee between the HR and scheduling systems and must stay consistent between the systems.

The Team, Job, Time Code, Hour Type, Project, Docket, Skill, and Activity names that are used in the import file are assumed to have existed on the application. Any missing names are not created during the import process.

If the import is trying to assign a detail to an employee and the employee does not belong to the team, a temporary team assignment is created.

The shift detail in the import file does not require a job name for breaks. For the actual details, a job name is required. The employee should already be configured so that the employee is eligible to perform that job. Otherwise, the import transaction fails.

The external system is responsible for sending scheduled breaks as details. While a shift detail and a break detail can overlap, two overlapping shifts are not allowed in the export file.

The order of the shift details in the export file is not important.

Work or clock edits are not affected by the Schedule Detail Import.