Concept: Importing Time Clock Events

If you use

Put Time Clock Events

to import more than 1,000 time clock transactions, the integration could take a significant time to complete and might hold up other Workday processes. In this case, use the

Import Time Clock Events

web service.

Use the

Import Time Clock Events

web service when you need to import large batches of 1,000 or more time clock events on an infrequent basis. Example: Importing time clock events for implementation testing or loading a single large batch after an integration with a third-party system fails.

Import Time Clock Events

runs as a background process, so it doesn't hold up other Workday tasks running at the same time.

The Import web service pattern enables you to use Workday Enterprise Interface Builder (EIB). To retrieve processing errors after using

Import Time Clock Events

, you can use the:

Get Import Process Messages
web service.
Unprocessed Time Clock Events
report.

Use the

Put Time Clock Events

public web service operation when you need to import time clock events from a third-party system in near real-time. The third-party system should queue up clock events into batches and initiate a call to

Put Time Clock Events

. If Workday is unable to receive a batch, the third-party system must continue to queue time clock events until Workday is available.

When using the

Put Time Clock Events

web service, we recommend that you:

Send time clock events in their raw form (not matched to time blocks or processed in any other way).
Send batches every 2-5 minutes.
Send time clock events in the order that they occurred to ensure Workday matches them into time blocks as accurately as possible.
Don't send a batch with more than 150 time clock transactions. If you have more than 150 time clock transactions to send, break them into smaller batches.

Time clock events imported into Workday must include these details:

Field	Notes
Time Clock Event Date Time	Date and time of the time clock event. If you don't specify a time zone offset, Workday assumes a UTC offset of zero.
Clock Event Type Reference	Workday accepts 4 time clock event types: In , Out , Break , and Meal .
Employee ID
Position ID	Required if the worker has multiple jobs and the time clock event type is In .
Time Clock Event ID	Required for edit and delete transactions so that Workday can identify which time clock event to edit or delete.
Delete Time Clock Event	When flagged, identifies the transaction as a deletion. If you're importing a deletion, the only required fields are: Time Clock Event ID Delete Time Clock Event

All other fields are optional.

Data accepted by the web service operation might still be invalid within Time Tracking. Workday runs a separate set of validations on the data after it has passed through the web service operation and flags invalid time clock transactions. Workday doesn't match invalid time clock transactions to time blocks, but causes them to be in error until you correct the transaction. Use the

Maintain Invalid Time Clock Events

task to view, fix, or ignore transactions that are in error.

Invalid or missing values in these fields cause the time clock event to be in error until corrected:

Employee ID
Position ID
Time Clock Event Date Time
Clock Event Type Reference

The fields below are optional, but if sent, must be valid values in Workday. Invalid values cause the time clock transaction to be in error until corrected. These fields apply to

In

time clock event types only. If the time entry code is blank, Workday applies the default time entry code from the worker's time entry template.

Time Entry Code
Project ID
Task ID
Override Rate
Business Unit
Cost Center
Custom Organization 01 - Custom Organization 10
Custom Worktag 01
-
Custom Worktag 15
Fund
Grant
Job Profile
Location
Program
Region

You can edit or delete time clock events using the

Put Time Clock Events

web service. When importing an edit transaction using the web service, include the time clock event ID in the file. When you import edit transactions, Workday replaces the existing details on the time clock event with the details of the new transaction. Include all of the details that you want to preserve in addition to the edited fields. When importing a delete transaction, set the

Delete Time Clock Event

field to

Y

(for yes).

In addition to importing edits and deletions, you can manage time clock events directly in Workday.