Workday Adapter Guide

For SAP Integration Suite and SAP Cloud Integration

Version 1.1.0 – April 2024

TABLE OF CONTENTS
1. INTRODUCTION ........................................................................................................................................... 3
1.1 Coding Samples......................................................................................................................................... 3
1.2 Internet Hyperlinks .................................................................................................................................... 3
2. WORKDAY INTEGRATION .......................................................................................................................... 3
2.1 Introduction ................................................................................................................................................ 3
2.2 Workday Adapter ....................................................................................................................................... 3
2.2.1 Features ................................................................................................................................................... 3
2.3 Architecture Overview .............................................................................................................................. 4
3. SUPPORTED SERVICES AND VERSIONS................................................................................................. 5
4. WORKDAY ADAPTER CONFIGURATION .................................................................................................. 8
5. ADAPTER INSTALLATION .......................................................................................................................... 9
6. ECLIPSE PLUG-IN INSTALLATION ............................................................................................................ 9
7. USING THE ECLIPSE PLUG-IN ................................................................................................................... 9
7.1 Configuration of Workday Tenant Login Information .......................................................................... 10
7.2 Generate XSD ........................................................................................................................................... 10
7.2.1 Workday Service ................................................................................................................................... 10
8. CREATING CREDENTIALS AS SECURITY MATERIAL .......................................................................... 13
9. ADAPTER CONFIGURATION .................................................................................................................... 14
9.1 Connection Tab ........................................................................................................................................ 15
9.2 Processing Tab ........................................................................................................................................ 15
10. SAMPLE SCENARIO EXPLAINED .......................................................................................................... 16
11. REFERENCES .......................................................................................................................................... 19
11.1 Finding Workday Address .................................................................................................................... 19
12. SUPPORT AND TROUBLESHOOTING ................................................................................................... 19
12.1 SSL Handshake Exception ................................................................................................................... 20
12.2 Unknown Host Exception ..................................................................................................................... 20
12.3 No Artifact Descriptor Found ............................................................................................................... 20
12.4 Invalid Input XML ................................................................................................................................... 20
12.5 Cannot Produce Target Element .......................................................................................................... 21
12.6 Non-Existing Field ................................................................................................................................. 21

2
1. INTRODUCTION

This is the official guide for the Workday Adapter for SAP Cloud Integration. This guide covers all relevant
information for integration developers to start working with the Workday Adapter. Read this guide carefully
before using the Adapter.

1.1 Coding Samples

Any software coding and/or code lines/strings ("Code") included in this documentation are only examples
and are not intended to be used in a productive system environment. The Code is only intended to better
explain and visualize the syntax and phrasing rules of certain coding. The correctness and completeness of
the Code given herein are not warranted.

1.2 Internet Hyperlinks

The documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as hints
about where to find related information. The availability and correctness of this related information or the
ability of this information to serve a particular purpose are not guaranteed.

2. WORKDAY INTEGRATION

2.1 Introduction

Workday provides an all-in-one cloud solution for businesses to manage finance, human resources, and
planning.

Workday provides the following products: Financial Management, Human Capital Management, Enterprise
Planning, Spend Management, Talent Management, Payroll, and Workforce Management and Analytics and
Reporting.

For more information about Workday and its products, visit the Workday website:
https://www.workday.com

2.2 Workday Adapter

The Workday Receiver Adapter enables an SAP Cloud Integration tenant to accelerate the implementation
time and reduce the complexity of connecting to Workday based on its API.

2.2.1 Features

From a high-level perspective, the following key features are provided by the Workday Adapter:

• Support for multiple versions: The Workday Adapter allows integration with Workday using a preferred
SOAP API version.

At the moment of the publishing of this documentation, the Adapter supports Workday API V34.1,
V34.2, and V35.0.

• Support for multiple operations, including:

o Absence_Management
o Academic_Advising
o Academic_Foundation
o Admissions
o Adoption
o Benefits_Administration
o Campus_Engagement
o Cash_Management
o Compensation

3
 o Compensation_Review
o Dynamic_Document_Generation
o External_Integrations
o Financial_Aid
o Financial_Management
o Human_Resources
o Identity_Management
o Integrations
o Inventory
o Learning
o Moments
o Notification
o Payroll
o Payroll_CAN
o Payroll_FRA
o Payroll_GBR
o Payroll_Interface
o Performance_Management
o Professional_Services_Automation
o Recruiting
o Resource_Management
o Revenue_Management
o Settlement_Services
o Staffing
o Student_Core
o Student_Finance
o Student_Records
o Student_Recruiting
o Talent
o Tenant_Data_Translation
o Time_Tracking
o Workday_Connect
o Workday_Extensibility
o Workforce_Planning

• XSD generation: The Adapter comes equipped with an Eclipse Plug-in which generates XSDs
representing objects in Workday.

2.3 Architecture Overview

From a technical perspective, the Workday Adapter can only be used on the receiver side. This means that
the SAP Cloud Integration is the initiator of the calls. In case the calls toward Workday need to be scheduled,
a Scheduler within the integration flow can be used.

Figure 4.1 shows how the Workday Adapter can be used in a simple Request-Reply scenario. Various
operations can be used in the Adapter – such as Query Data, Delete or Create an entity, etc. These operations
are explained in detail in Section 3.

To learn more about the different adapter operations and their configuration, refer to Section 9.

4
 Figure 2.1 Workday Adapter solutions for SAP Cloud Integration

The mapping step makes mapping to other systems’ message types easier as there are several XSDs created
for the operations that the Workday Adapter supports.

For the Workday plug-in and XSD Generator configuration, please refer to Section 7.

3. SUPPORTED SERVICES AND VERSIONS

Currently, API versions 34.1 and higher are supported by the Adapter.

Table 1 lists the different services that are supported by the Workday Adapter.

Services Description
Absence_Management • The Absence Management Web Service contains operations that expose
absence-related data, including Employee Time Off and Absence Inputs for
time off and accrual adjustments and overrides, and Leave Requests, in
Workday Human Capital Management Business Services.

Academic_Advising • Web Service for retrieving objects related to Academic Advising, such as
Student Academic Requirement Assignments.

Academic_Foundation • Public Web Service for creating, editing, and retrieving the foundational
objects for the Student System, such as Programs of Study, Educational
Institutions, and other objects with cross-module uses.

5
Services Description
Admissions • Web Service for creating, editing, and retrieving objects related to Admissions,
such as Applicants.

Adoption • Adoption Web Service Operations.

Benefits_Administration • The Benefits Administration Web Service contains operations that expose
Workday Human Capital Management Business Services benefits-related
data.

Campus_Engagement • Public Web Service for creating, editing, and retrieving objects related to
planning and organizing communication between Student Prospects and
Recruiters.

Cash_Management • The Cash Management Web Service contains operations that expose
Workday Financials Cash Management data. It includes data relative to
Banking.

Compensation • The Compensation Web Service contains operations that expose Workday
Human Capital Management Business Services compensation-related data.

Compensation_Review • The Compensation Review Web Service contains operations that expose
Workday Human Capital Management Business Services compensation
review-related data.

Dynamic_Document_Generation • Web service for creating, editing, and retrieving objects related to Document
Templates, such as Text Blocks and Text Block Categories.

External_Integrations • The External Integrations Web Service provides an operation that informs
external systems of Integration Events that have been triggered from within
Workday. The WSDL for this service provides the structure that needs to be
implemented by an external system to receive event "Launch" information.

Financial_Aid • This web service is for the Financial Aid module.

Financial_Management • The Financial Management Web Service contains operations that expose
Workday Financials data. It includes data relative to Accounts, Accounting,
Business Plans, Financial Reporting, Tax, Financial Organizations, Basic
Worktags, Related Worktags, and more.

Human_Resources • The Human Resources Web Service contains operations that expose
Workday Human Capital Management Business Services data, including
Employee, Contingent Worker, and Organization information. This Web
Service can be used for integration with enterprise systems including
corporate directories, data analysis tools, email or other provisioning sub-
systems, or any other systems needing Worker and/or Organization data.

Identity_Management • The Identity Management Web Service contains operations that relate to
Workday Identity and Access Management.

Integrations • This Web Service contains operations related to all Integrations within the
Workday system.

Inventory • Submits Interview Feedback for Interviewers on the Interview Schedule. Also,
allows you to move a candidate to the next stage of the business process.
This web service is being retired in a future release. These operations are
available under the Recruiting (Public) web service.

Learning • The Inventory Web Service contains operations that expose Workday
Financials Inventory data.

Moments • The Learning Web Service contains operations for creating, editing and
retrieving Workday Learning-related data such as Courses, Course Offerings,
and Enrollments.

6
Services Description
Notification • Web Service for creating, editing, and retrieving objects related to Workday
Moments.

Payroll • The Notification Web Service provides an operation that informs external
systems of business events that occur within Workday. The WSDL for this
service provides the structure that needs to be implemented by an external
system to receive notifications for their subscribed Workday business events.
Subscriptions and Notification details (i.e. Endpoint and security information)
are defined within the Workday application.

Payroll_CAN • The Workday Payroll Web Service contains operations that expose Workday
Payroll data for integration with third parties (such as time and attendance).

Payroll_FRA • The Workday Payroll CAN Web Service contains operations that expose
Workday Payroll CAN data for integration with third parties (such as time and
attendance).

Payroll_GBR • The Workday Payroll FRA Web Service contains operations that expose
Workday Payroll FRA data for integration with third parties

Payroll_Interface • The Workday Payroll GBR Web Service contains operations that expose
Workday UK Payroll data for integration with third parties.

Performance_Management • The Payroll Interface Web Service contains operations that expose Workday
Human Capital Management Business Services data for integration with
external payroll systems.

Professional_Services_Automation • The Performance Management Web Service contains operations that expose
Workday Employee Performance Management Business Services data. This
Web Service can be used for integration with other employee performance
management systems.

Recruiting • The Professional Services Automation Web Service contains operations that
expose Workday Financials Business Services data for integration with
Professional Services Automation (PSA) systems.

Resource_Management • The Recruiting Web Service contains operations that expose Workday Human
Capital Management Business Services data for integration with Talent
Management and Applicant Tracking systems.

Revenue_Management • The Resource Management Web Service contains operations that expose
Workday Financials Resource Management data. It includes data relative to
Suppliers, Supplier Accounts, Expenses, Business Assets, and Projects.

Settlement_Services • The Revenue Management Web Service contains operations that expose
Workday Financials Revenue Management data. It includes data relative to
Customers, Customer Accounts, Prospects, and Opportunities.

Staffing • Web Service used for settlement management and services.

Student_Core • The Staffing Web Service operations expose Workday Human Capital
Management Business Services and data. These services pertain to staffing
transactions for both employees and contingent workers, such as bringing
employees and contingent workers on board.

Student_Finance • Web Service for creating, editing, and retrieving objects related to students'
personal information, such as Student Documents.

Student_Records • Web service for creating, editing, and retrieving objects related to Student
Finance, such as charges and payments for Students.

Student_Recruiting • Web Service for creating, editing, and retrieving objects related to Student
Records, such as Student Courses, Sections, etc.

7
 Services Description
Talent • Web Service for creating, editing, and retrieving objects related to Student
Recruiting, such as Student Recruiting Events, Campaigns, Cycles,
Recruiters, and Prospects.

Tenant_Data_Translation • This web service consists of operations for interfacing with the Workday
Talent Management web service operations.

Time_Tracking • Public Web Service to export and import translatable tenant data

Workday_Connect • Operations for importing and exporting time and work schedule information.

Workday_Extensibility • Get and put web services used for communication capabilities across
applications.

Workforce_Planning • Public Web Service for extensibility features across applications.

Table 1 Description of Supported Operations

4. WORKDAY ADAPTER CONFIGURATION

To connect SAP Cloud Integration to Workday, an integration user must be created in Workday.

Follow this guide to generate this user type.

1. Login to the Workday tenant with an admin user.

2. In the Workday Portal search for “Create User” and click the task Create Integration System User.

Figure 4.1 Workday Portal

3. In the Account Information form, fill in a Username and a New Password. Leave the Require New
Password at Next Sign In option unchecked, as this user will be logging in programmatically.

4. Leave the Session Timeout Minutes with the default value of 0. This prevents the user's sessions from
timing out prematurely.

5. Finally, select the option Do Not Allow UI Sessions. This provides an added layer of security that
prevents a user with the password of the integration system from logging into Workday.

8
 Figure 4.2 Workday Account Creation

Section Parameter Name Description

User • Username* Provide a username.
Creation • Example: myworkdayuser

• New Password* Set a password.

• Alternatively, check the Generate Random Password checkbox to
generate a password automatically.

• New Password Verify* • Repeat the password.

• Require New Password at • Unchecked

Next Sign In

• Session Timeout Minutes • 0

• Do Not Allow UI Sessions • Checked

Table 2 Workday Account Creation Configuration Details

Note the Username and Password, these are needed to create credentials in the SAP Cloud Integration
tenant.

5. ADAPTER INSTALLATION

Refer to the Workday Adapter Installation Guide included in the package for detailed steps on installing the
Workday Adapter.

6. ECLIPSE PLUG-IN INSTALLATION

Refer to the Eclipse Plug-in Installation Guide included in the package for detailed steps on installing the
Eclipse Plug-in.

7. USING THE ECLIPSE PLUG-IN

The Eclipse Plug-In or Workbench can be used to extract and generate XSDs of the different Workday entities.
These XSDs can then be used in mappings for the request or response messages in the integration scenarios.

The next sections will explain how to use the Plug-In.

9
7.1 Configuration of Workday Tenant Login Information

The Eclipse Plug-In generates the XSDs according to the metadata of the business objects or entities that
are part of a given Workday tenant. To retrieve the metadata, the users need to configure the connection
and authentication information for the target tenant.

To configure the connections and authentications, click on the Window option on the Eclipse menu bar and
select the Preferences menu item.

On the left side of the dialogue box, navigate to the Workday preference page. A page that looks like Figure
7.1 will be shown.

Figure 7.1 Configuring the Connection Details of the Plug-In

On the preference page, the Host field refers to the address of the target Workday tenant.

Example: https://youraccount.workday.com/.

In the Tenant field, the tenant name must be provided.

Note that these fields correspond to the same information required in the Adapter’s Connection Tab. See
Section 9.1 for more information.

After providing these details, click Apply and Close.

7.2 Generate XSD

The Workday XSD generator allows the creation of schemas for all operations. The next sections discuss
how the Plug-In is used.

7.2.1 Workday Service

The Workday Service configuration pane is situated on the left side of the window.

Provide the API Version and the Service as shown in Figure 7.2.

10
 Figure 7.2 Workday Plug-in Configurations

Table 3 provides details for each of these configuration settings.

Services Description
API Version • The version of the Workday API. The workbench supports V34.1 and higher.

Service • Select the Service under which the operation you want is situated.

Operation • Select the Operation for which the XSD needs to be generated.

Throw • Select the checkbox to disable or enable throwing exception in case of a failed response from
Exception on the remote server.
Failure
Table 3 Workday Plug-In Configuration Setting Details
Once the settings are configured per the scenario, click the Generate button to generate XSDs.

On the right side of the screen are three tabs: Request XSD and Response XSD.

The Request XSD tab contains the XSD that represents the properties of the selected entity in Workday.
This XSD can be copied or saved to the local machine.

It can later be used in a mapping of the integration flow, see Figure 7.3.

11
 Figure 7.3 Example Request XSD
Similarly, the Response XSD tab contains the XSD that represents the properties of the selected module.
Note that this XSD only includes properties that are returned in the response of the specified operation.

For example, if the Create operation is selected, the primary key property might not be present in the input
(Request XSD) but will be present in the response XSD. See Figure 7.4 for visualization.

In contrast with the Request XSD tab, the Response XSD tab is always filled for all the operations.

12
 Figure 7.4 Example Response XSD

The generated XSDs can be copied or saved to the local computer using the Save and Copy buttons. See
the bottom left corner of Figure 7.4.

8. CREATING CREDENTIALS AS SECURITY MATERIAL

To follow the best practices and the security policy of SAP Cloud Integration, the Adapter works with
standard security artifacts such as Secure Parameter and User Credentials. These are stored in the SAP
secure store.

This way, credentials can be safely provided to the Adapter using aliases.

To create a Security Material for the Workday Adapter, proceed with the following steps:

1. In SAP Cloud Integration, navigate to the Monitor View.

2. Select Security Material under the Manage Security section.

13
 3. Click on the Create dropdown button at the top right and select User Credential.

4. Provide a name to the Security Material and ensure that User Credential is selected in the Type
dropdown.

5. Supply the Workday username and password.

6. Click on Deploy.

9. ADAPTER CONFIGURATION

This section describes different parameters that can be configured for the Receiver Adapter. The Adapter
has two tabs, Connection, and Processing.

Each is discussed in the next sections. Note that when (*) is present in a property, it indicates that the
property is mandatory.

14
9.1 Connection Tab

The Connection Tab contains parameters that define how the Adapter connects and authenticates with the
Workday tenant.

See an example in Figure 9.1.

Figure 9.1 Example of Filled Connection Tab

The details of each field included in the Connection tab are explained in Table 4.

Tab Parameter Description

Name
Connection • Address* • Specify the recipient's endpoint URL. This is the URL to which you connect to your
Workday tenant.
Example: yourhost.workday.com

• Tenant* • Specify the Workday tenant to be used.

Example: yourhost.workday.com Example: Workday_Tenant

• Credential • Specify the credential name used to authenticate against the server. This represents
Name* the Workday credential name (username-password) pair stored as Security Material.
You created this User Credential in your Cloud Integration (see Section 8).

Table 4 Connection Tab Description

9.2 Processing Tab

In the Processing Tab, specify the type of operation to be performed. Select the version of Workday API to
be used from the API Version dropdown. Note that currently, versions 32.0, 34.1, and 34.2 are supported by
the Adapter.

Service refers to the service desired to be performed, for example, Financial Management, Identity
Management, or Human Resources.

Table 1 provides a full list of all Services supported by the Adapter.

Request Operation Tag refers to the Operation to be executed.

For example, if the Service Financial Management a Request Operation Tag could be for example
Get_Basic_Customers or Put_Cost_Center.
Throw Exception on Failure can be enabled/disabled as per your preference by selecting the checkbox.

Note: Throw Exception on Failure checkbox is enabled by default.

Figure 9.2 illustrates the basic options of the Processing Tab. Selecting a Service automatically fills its
corresponding Request, Operation Tag.

15
 Figure 9.2 Processing Tab, Workday Adapter

10. SAMPLE SCENARIO EXPLAINED

In this chapter, through a business scenario how the Workday Adapter and the Plug-In can be used is
explained.

Figure 10.1 shows an SAP integration flow for requesting Employee information from Workday. This iFlow
can be called from any external system (for example SAP S/4HANA).

Figure 10.1 SAP Cloud Integration Sample Scenario

For simplicity reasons, the integration flow exposes an HTTPS endpoint. This means that the integration
flow needs to be triggered externally via an HTTPS call. This can be tested, for example, through Postman.

To know more about Postman, refer to this link.

To get Employee information, an XSD that contains details about all the fields that describe the structure of
an Employee in Workday is required.

Figure 10.2 SAP Cloud Integration Get_Employee_request XSD

To generate the XSD needed on the Workday side to get the Employee, the Eclipse Plug-In must be used.
This is included in the Workday Adapter package.

16
See Figure 10.3 for an example setup of the plug-in.

Figure 10.3 Workday Plug-in, Example Set Up

To create the XSD, follow these steps:

1. Select the API version, in this case, 34.1.

2. Choose the Service Human Resources.

3. Corresponding operations are displayed. Select “Get_Employee”.

4. Click on the Generate XSD button.

Using the XSD created, a one-to-one mapping can be made. See Figure 10.4 for reference.

Figure 10.4 Workday Plug-in, Mapping

After the mapping is completed the Workday Adapter needs to be configured.

17
 Figure 10.5 Workday Adapter, Connection Tab Details

In the Connection Tab shown in Figure 10.5, supply the Workday tenant details. Credentials previously
deployed for Credential Name are used in the Connection details.

Refer to Section 7 for further instructions on how to deploy these credentials.

Each field of the Connection tab is explained in Section 9.1.

Following the Connection tab, the next step is to configure the Process Tab. An example of the needed
configuration to achieve the integration of the example is shown in Figure 10.6.

Figure 10.6 Workday Adapter, Processing Tab Details

In the Processing Tab, select the API Version. Note that this needs to match the APU version selected when
generating the XSD in the Eclipse Plug-in.

Select Operation as “Human Resources”, Request Operation Tag as “Employee_Get”, and enable/disable
Throw Exception on Failure as per your preference by selecting the checkbox.

Note: Throw Exception on Failure checkbox is enabled by default.

Each field of the Processing tab is explained in Table 3.

Now that all the necessary configurations are made, the integration flow can be deployed and then called
from Postman.

Figure 10.7 shows an example of the input message.

18
 Figure 10.7 Workday Gets Employee Request

As a result, Employee information is retrieved from Workday.

11. REFERENCES

11.1 Finding Workday Address

To find the address that can be used in the Address field of the Connection Tab, log in to the Workday portal
and navigate to the Home Page.

Figure 11.1 Workday Address

From the browser URL, take the tenant name of the Workday instance as highlighted in Figure 11.1.

12. SUPPORT AND TROUBLESHOOTING

In case of errors, the source of the issue can be traced by changing the Log level of the integration flow to
Traces.

Navigate to the Monitor view of SAP Cloud Integration and proceed to the Manage Integration Content page.

Set the Log Level to Trace Log level. This enables the collection of more traces that can be used to
effectively understand the problem. These traces can also be used in a ticket.

19
In the next sections, a few issues that may be encountered and possible solutions are discussed.

12.1 SSL Handshake Exception

Error Message:
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building
failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification
path to requested target, cause: sun.security.provider.certpath.SunCertPathBuilderException: unable
to find valid certification path to requested target.

Possible Solution: This error generally means that an entry for the root certificate of Workday is missing in
the Keystore of SAP Cloud Integration.

At the time this document is published, Workday expects a DigiCert Global Root G2 certificate.

12.2 Unknown Host Exception

Error Message:
java.net.UnknownHostException: xxxxxxx.workday.com

Possible Solution: This error generally indicates that the URL used in the Address field of the Connection
Tab in the Adapter is incorrect. Correct the value of this field.

Refer to Section 11.1 which explains how to find the Workday Address.

12.3 No Artifact Descriptor Found

Error Message:
[CAMEL][IFLOW][CAUSE]: Cause: com.sap.it.nm.types.NodeManagerException:
[CONTENT][CONTENT_DEPLOY][NoArtifactDecriptorFoundForArtifactName]:No artifact descriptor
found for artifactName WorkdayCredentials

Possible Solution: This error generally indicates that the Security Artifact used in the Connection Tab does
not exist. Ensure that the artifact used in the Connection Tab exists as a Security Material.

Refer to Section 8 for guidance on how to create Security Material in SAP Cloud Integration.

12.4 Invalid Input XML

Error Message:

20
 org.apache.camel.CamelException: Invalid input XML. org.apache.camel.CamelException: Invalid
input XML. The root node "request" is missing in the input.

Possible Solution: This error generally indicates that the Adapter is expecting an XML input but is getting the
wrong XML or even another language such as JSON.

12.5 Cannot Produce Target Element

Error Message:
com.sap.xi.mapping.camel.XiMappingException:
com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot produce target element
/request/entry/name. Queue has not enough values in context. Target xsd requires a value for this
element, but target field mapping does not produce one. Probably the xml-instance is not valid to the
source xsd, or the target field mapping does not fulfill the requirement of the target xsd., cause:
com.sap.aii.mappingtool.tf7

Possible Solution: This error generally indicates that the mapping requires a missing mandatory value in the
message body sent when creating or updating an instance of an entity in Workday.

12.6 Non-Existing Field

Error Message:
org.apache.camel.CamelException:org.apache.camel.CamelException:
{"error":"invalid_parameter","error_message":"Non existing field: somefield in module: Accounts"}

Possible Solution: This error usually indicates that a field does not match a known field found for this entity
type.

21
www.sap.com/contactsap

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.