SAP to Workday Employee Migration

Moves a large set of employees from SAP to Workday. It is triggered by an HTTP call either manually or programmatically. Employees are upserted so that the migration can be run multiple times without worrying about creating duplicates. This template uses batch to efficiently process many records at a time.

Template Requirements

Install Workday HCM - Human Resources and Workday HCM - Staffing modules that you can find on the Workday connector page.

License Agreement

This template is subject to the conditions of the MuleSoft License Agreement. Review the terms of the license before downloading and using this template. You can use this template for free with the Mule Enterprise Edition, CloudHub, or as a trial in Anypoint Studio.

Use Case

As a SAP admin I want to migrate employees to Workday.

This template helps you migrate employees from a SAP instance to Workday, and specifying available filtering criteria and desired behavior when an employee already exists in the destination system.

This template leverages the Mule batch module. The batch job is divided into Process and On Complete stages.

Before the Process stage the template goes to SAP and queries all the employees that match the filtering criteria. The criteria is based on available filtering fields for the standard BAPI BAPI_EMPLOYEE_GETDATA value.

During the Process stage the template checks if there is an employee with such an ID in Workday and if present, the template updates it using Change_Preferred_Name function, if the ID isn't in Workday, the template creates it using HIRE_EMPLOYEE function call.

Finally during the On Complete stage the template logs output statistics data in the console and sends a notification email with the results of the batch execution.

Considerations

To make this template run, there are certain preconditions that must be considered for the preparations in both source and destination systems, that must be made for the template to run smoothly. Failing to do so could lead to unexpected behavior of the template.

Disclaimer

This template uses a few private Maven dependencies from MuleSoft to work. If you intend to run this template with Maven support, you need to add extra dependencies for SAP to the pom.xml file.

SAP Considerations

Here's what you need to know to get this template to work with SAP.

As a Data Source

The SAP backend system is used as a source of data. The SAP connector is used to send and receive data from the SAP backend. The connector can either use RFC calls of BAPI functions and/or IDoc messages for data exchange, and needs to be properly customized per the "Properties to Configure" section.

Workday Considerations

The following sections provide more info.

As a Data Destination

There are no considerations with using Workday as a data destination.

Run it!

Simple steps to get this template running.

Running On Premises

In this section we help you run this template on your computer.

Where to Download Anypoint Studio and the Mule Runtime

If you are new to Mule, download this software:

• Download Anypoint Studio
• Download Mule runtime

Note: Anypoint Studio requires JDK 8.

Importing a Template into Studio

In Studio, click the Exchange X icon in the upper left of the taskbar, log in with your Anypoint Platform credentials, search for the template, and click Open.

Running on Studio

After you import your template into Anypoint Studio, follow these steps to run it:

1. Locate the properties file mule.dev.properties, in src/main/resources.
2. Complete all the properties required as per the examples in the "Properties to Configure" section.
3. Right click the template project folder.
4. Hover your mouse over Run as.
5. Click Mule Application (configure).
6. Inside the dialog, select Environment and set the variable mule.env to the value dev.
7. Click Run.

For this template to run in Anypoint Studio, you need to install SAP libraries. See Install SAP Libraries.

Running on Mule Standalone

Update the properties in one of the property files, for example in mule.prod.properties, and run your app with a corresponding environment variable. In this example, use mule.env=prod.

After this, to trigger the use case you just need to browse to the local HTTP Listener with the port you configured in the properties file. If this is, for instance, 9090 then you should browse to: http://localhost:9090/migrateemployees. Browsing to this URL causes the application to output the summary report and send it in the email.

Running on CloudHub

When creating your application in CloudHub, go to Runtime Manager > Manage Application > Properties to set the environment variables listed in "Properties to Configure" as well as the mule.env value.

Once your app is all set and started, if you choose sapemployeemigration as the domain name to trigger the use case, you just need to browse to http://sapemployeemigration.cloudhub.io/migrateemployees and the report is sent to the email you configured.

Deploying a Template in CloudHub

In Studio, right click your project name in Package Explorer and select Anypoint Platform > Deploy on CloudHub.

Properties to Configure

To use this template, configure properties such as credentials, configurations, etc.) in the properties file or in CloudHub from Runtime Manager > Manage Application > Properties. The sections that follow list example values.

Application Configuration

• http.port 9090
• page.size 100

Workday Connector Configuration

• wday.username user
• wday.tenant tenant
• wday.password secret
• wday.host https://impl-cc.workday.com/...
• wday.system.id system id
• wday.country USA
• wday.state USA-CA
• wday.organization SUPERVISORY_ORGANIZATION-6-235
• wday.jobprofileId 39905
• wday.postalCode 90001
• wday.city San Francisco
• wday.location San_Francisco_Site
• wday.address New York
• wday.currency USD
• wday.testuser.id test user id
• wday.system.id System id
• wday.email john.doe@aol.com

SAP Connector Configuration

• sap.jco.user user
• sap.jco.passwd secret
• sap.jco.sysnr 14
• sap.jco.client 800
• sap.jco.lang EN
• sap.jco.ashost example.domain.com

SMTP Services Configuration

• smtp.host smtp.gmail.com
• smtp.port 587
• smtp.user sender%40gmail.com
• smtp.password secret

Email Details

• mail.from mail.from@example.com
• mail.to info@examplecom
• mail.subject Employee Migration Report

API Calls

There are no special considerations regarding API calls.

Customize It!

This brief guide provides a high level understanding of how this template is built and how you can change it according to your needs. As Mule applications are based on XML files, this page describes the XML files used with this template. More files are available such as test classes and Mule application files, but to keep it simple, we focus on these XML files:

• config.xml
• businessLogic.xml
• endpoints.xml
• errorHandling.xml

config.xml

This file provides the configuration for connectors and configuration properties. Only change this file to make core changes to the connector processing logic. Otherwise, all parameters that can be modified should instead be in a properties file, which is the recommended place to make changes.

businessLogic.xml

Functionals aspect of the template are implemented in this XML file, which is directed by a batch job and is responsible for creates and updates. The several message processors constitute these high level actions that fully implement the logic of this template:

1. Job execution is invoked from triggerFlow (endpoints.xml).
2. During the Process stage, each employee is filtered depending on whether a matching employee exists in the Workday instance. The matching is performed by querying a Workday instance for an entry with each External Reference ID.
3. Inserts a new record in the Workday instance if the employee wasn't found in the previous step, or updates it if there is a matching employee.
4. During the On Complete stage the template logs output statistics data into the console and sends report to an email you choose.

endpoints.xml

For the purpose of this particular template, the triggerFlow executes the Batch Job in businessLogic.xml which handles all the logic of it.

Inbound Flow

HTTP Inbound Endpoint - Start Report Generation

• ${http.port} is set as a property to be defined either on a property file or in CloudHub environment variables.
• The path configured by default is migrateemployees, which you are free to change to one you prefer.
• The host name for all endpoints in your CloudHub configuration should be defined as localhost. CloudHub routes requests from your application domain URL to the endpoint.
• The endpoint is configured as a request-response since as a result of calling it, the response is the total of employees migrated and filtered by the criteria specified.

errorHandling.xml

This file handles how your integration reacts depending on the different exceptions. This file provides error handling that is referenced by the main flow in the business logic.