Concept: Importing Leave of Absence Events
You can load large volumes of leave of absence events into Workday Absence using Workday
Enterprise Interface Builder (EIB) and SOAP UI for these web services:
- Import Request Leave of Absence
- Import Request Return From Leave of Absence
- Load leave events in Workday from a third-party tool.
- Migrate validated leave events into Workday.
- Load batches of leave events in bulk.
- Correct multiple leave events for multiple workers.
To avoid introducing risks when loading request leave of absence events, Workday recommends
that you don't load these events in the same file:
- Events linked to prior events.
- New events and corrections.
Business Processes
Importing a batch of leave of absence events launches these respective business
processes:
When you migrate large volumes of leave events during deployment,
Workday recommends that your business processes include either:
Business Process | Notes |
|---|---|
Request Leave of Absence
| You can add users to the security groups of the Import Request
Leave of Absence Events initiating action to enable them to load
request leave of absence events in batches. |
Request Return from Leave of Absence
| You can add users to the security groups of the Import Request
Return from Leave of Absence Events initiating action to enable
them to load request return from leave of absence events in
batches. |
- Only theInitiationstep.
- TheCompletionstep as the last step.
When you load leave events using the import web services, Workday automatically completes the
respective business process, then runs subprocesses.
Tips for Entering Data in the EIB Spreadsheet
As you complete the EIB template, consider these fields:
Field | Notes |
|---|---|
Header Key
| Determines the batch for a leave event. Use the same header key to
group all events in a batch. Example: To load events in 2 batches, use
1 for the first 500 rows and 2 for the next 1,000
rows. |
Line Key
| An incremental value for each row within a header key
batch. Example: Use 1 for the first row, 2 for the
second row, 3 for the third row, and so on. Restart the
numbering at 1 for each batch. |
Request Leave of Absence ID
| Workday assigns a value if you don't provide one. This field is
available only on the Import Request Leave of Absence Events EIB
spreadsheet. |
Correction
| Enter Y or N to indicate that you're correcting an
existing leave event. |
Leave of Absence Type
| This field is available only on the Import Request Leave of Absence
Events EIB spreadsheet. |
First Day of Leave
| The first date of a worker's leave. Example:
2020-03-25 .This field is available only on the Import
Request Leave of Absence Events spreadsheet. |
Estimated Last Day of Leave
| The estimated last date of a worker's leave. Example:
2020-04-22 .This field is available only on the Import
Request Leave of Absence Events spreadsheet. |
Row ID
| A unique numerical value for each row. This field is available
only on the Import Request Return from Leave of Absence Events
spreadsheet. |
Request Leave of Absence
| To return a worker from leave, enter the unique Request
Leave of Absence ID of the request leave of absence
event.This field is available only on the Import Request Return
from Leave of Absence Events spreadsheet. |
First Day of Work
| The date a worker returns to work. Example:
2020-04-24
This field is available only on the Import
Request Return from Leave of Absence Events
spreadsheet. |
Actual Last Day of Leave
| The actual last date of a worker's leave. Example:
2020-04-23
This field is available only on the Import
Request Return from Leave of Absence Events
spreadsheet. |
Validating Leave of Absence Events
When you load events using the import web services, Workday validates each leave event.
The import web services ignore validation rules that you've configured on:
- Leave Type.
- Business process.
Once the web services complete importing leave events, you can view the validations for leave
events in Workday.