Managing Third-Party Schedules

This section presents tips for addressing:

• Rejected schedule records.

• Field requirements for transmitting schedule data.

Rejecting Schedule Records

SCH_EXT_LOG is the table containing rows of all rejected scheduled time that did not make it into the PeopleSoft Application tables SCH_EXT_REJ_STG is the staging table for rejected rows that would get sent back to a third party scheduling system.

For both the SCH_EXT_LOG and SCH_EXT_REJ_STG tables, there is a SCH_REJECT_REASON field which explains why the scheduled time is rejected.

SCH_REJECT_REASON codes :

Code	Description
01	Invalid Employee and Employee Record Number
02	Invalid Schedule Source
03	Invalid Schedule Category
04	Invalid Punch Type
05	Invalid Activity
06	Invalid Activity Type
07	Invalid Event
08	Invalid Time Zone
09	Transaction already exists
10	Cannot add, transaction exists
11	Cannot change or delete, transaction exists

Field Requirements for Transmitting Schedule Data

These are tips for working with some field requirements for transmitting schedule data:

• Multiple Shifts

  To send multiple shifts per day, ensure the fields SEQ_NO and SEQNUM are correctly populated.

• SEQ_NO

  Should be populated with the same number for the same shift for the day.

• SEQNUM

  Should be populated with an incremented number for each row for the same shift for the day, and then start over again if another shift exists on the same day.

• Multiple Punch Rows for Punch Shift

  For a punch schedule, if sending PUNCH_TYPE and PUNCH_DTTM fields, do not need to populate START_DATE, END_DATE, START_TIME and END_TIME

• One row for Punch Shift

  To send a summarize row for punch schedule for the day, the fields START_DATE, END_DATE, START_TIME and END_TIME need to be populated, and the system will then split the time into an IN and OUT punch into SCH_ADHOC_DTL table.

  Total punch scheduled hours will be summarized based on the Schedule Total option (INCL_ML_BRK_FLG) on the Configuration tab of the TL Installation component or the Schedule Settings page on the System Settings of Global Payroll and Absence Management. The inclusion of meal and break punches to determine total scheduled hours are the options for this configuration.

• DUR

  DUR should always be populated with the date, whether sending Elapsed or Punch Schedule

• TL_QUANTITY

  Should be populated if sending Elapsed Scheduled Hours.

The following table illustrates field format examples

Field	Format	Example
START_TIME	HH:MM:SS.ssssss	07:00:00.000000
END_TIME	HH:MM:SS.ssssss	13:30:00.000000
START_DATE	YYYY-MM-DD	2004-06-11
END_DATE	YYYY-MM-DD	2004-06-11