Integrations: What is WECI in Workday Integrations ?

WECI

WECI, Worker Effective Change Interface, to detect the effective change events of worker. 

The Worker Effective Change Interface is an outbound integration that sends a full effective stack of worker data to third party systems. In addition to the already delivered functionality of corrections, rescinds, indirect, future and retro transactions, there are additional data sections and enhancements customers need in order to fulfill their third party system requirements.

Additional data sections will reduce customer effort in mapping fields required for the downstream system. Adding attributes will increase the flexibility of the connector so that customers can tailor the data extracted to the third party system.

Because of the resource-intensive nature of a WECI event, it is not an appropriate solution for frequent runs or for near real-time integrations, and because WECI returns the full stack of transactions, frequent runs are not necessary. In general, WECI should not be run more than once per day per supervisory org.

Unlike PECI, WECI includes contingent workers in it's output. It will run for the entire active worker population or can be restricted by the "Restrict Results By Orgs" launch parameter. Note that only supervisory orgs can be entered in this launch parameter.

WECI is not designed for time periods of inordinate lengths. Although WECI does not restrict effective and entry date ranges to pre-defined limits, WECI time periods should typically not be longer than a month. Extended time periods of several months or years, will likely cause issues when attempting to process excessive future-or-historic data for which WECI was neither designed nor tested. Restrict time periods to common sense intervals required to feed downstream endpoints.

These are the use cases of WECI:

• Non Payroll Applications i.e. that require full effective stack changes like Data Warehouses, Data Hubs or Compensation Planning applications.
• For Payroll Applications, WECI could serve as a bolt on to PECI in case where PECI has a given limitation for a specific use case of an industry or client that WECI can address.

Common Issues: 

Issue: 

Fields marked as "Include in Output" are not coming through in the output file, even when changed.

Resolution:

Ensure that in the parent section the desired output sections are checked "Include in Output". Selecting child elements does not automatically select the parent element to include in output.

Issue:

The following unexpected error has occurred: Multiple Worker Effective Change Interface - Summary DIS documents found! Should only be one!

Resolution:

Do not orchestrate multiple WECI integrations off of a single BP.

Issue:

A completed hire event is reported and a subsequent effective change updates a value required by the downstream system, such as National ID.

Resolution: 

CCW would only report a single transaction with all the values for transactions subsequent to the hire, so an updated National ID would be automatically included in the HIRE transaction. However with WECI, each transaction is reported independently, therefore there will be separate HIRE and DTA transactions for the HIRE event and subsequent change to National ID. The post-processing transform will need to detect the HIRE event and inspect the following effective changes for values that need to be included on the HIRE event transmitted to the payroll vendor

Issue:

Multiple contact data changes are not consolidated by WECI.

Resolution:

For example suppose there are two contact data changes in an effective date range on different effective dates. On the first date the employee changes their home address, and on the second effective date, their email address changes. The payroll vendor only supports a single row for changes to contact information. In this case all changes containing data for the single row required by the vendor need to be detected during the transform and consolidated in a single row before being transmitted to the vendor.