SAP SuccessFactors Migrating Features PDF
SAP SuccessFactors Migrating Features PDF
SAP SuccessFactors Migrating Features PDF
4 Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1 Universal Upgrade to Fiori User Experience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Universal Migration to the Home Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Universal Migration to the People Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Universal Upgrade to the Fiori User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2 Deprecation of Partner API, SFAPI Adhoc, and SFAPI for Simple Entities. . . . . . . . . . . . . . . . . . . . . . . . .15
API Deprecation FAQs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
4.3 Replacement of Legacy Picklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.4 Replacement of SuccessFactory-XML Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5 Retirement of Bulk Employees Import and Delta Employees Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5 Mobile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.1 Retirement of Android 5.X (OS version) Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.2 Retirement of Apple iOS 11.X (OS version) Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.3 Retirement of the Android SAP SuccessFactors Mobile App from the Amazon Appstore in China. . . . . . . 25
8 Calibration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
8.1 Replacement of Legacy Calibration UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
8.2 Replacement of Calibration V11 Org Chart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
9 Learning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.1 Retirements in SAP SuccessFactors Learning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.2 Replacement of Flash in Learning Administration Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
9.3 Replacement of Learning Catalog 2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
9.4 Replacement of Legacy Supervisor and User Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
9.5 Updating Learning Manager and User Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
10 Recruiting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
10.1 Retirement of Recruiting Dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
10.2 Retirement of Recruiting Marketing Client Admin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
11 Onboarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
11.1 Using the Adobe LiveCycle Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
12 Compensation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
12.1 Retirement of Live Analytics After 1H 2020. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
13 Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
13.1 Event Reason XML Deprecation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
As part of our ongoing commitment to innovation and a great user experience, some of our older features are
getting replaced with newer versions, new technology, or completely new tools.
Each innovation is part of a managed process that includes information available on the SAP Help Portal and the
SAP SuccessFactors Customer and Partner Communities. When we announce an older feature is being replaced,
we start by providing you information on what's replacing it and why. We also include information to help you
prepare for migration and links to further resources. Finally, we include the following key dates:
● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
There is no change in customer support during this phase. Customers are encouraged to start planning their
upgrade for the feature or version.
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
Note
Note
For universal upgrades, where a feature is replaced with a newer version that is pushed to all customers, there
may be no end of maintenance phase.
1H 2020
Added a topic on the retirement of Bulk We will retire Bulk Employees Import and Retirement of Bulk Employees Import
Employees Import and Delta Employees Delta Employees Import in the 2H 2020 and Delta Employees Import [page 22]
Import release.
Added a topic about Live Analytics fea Starting 1H 2020 Release, the Live Ana Retirement of Live Analytics After 1H
ture deprecation in Variable Pay lytics feature in Variable Pay is no longer 2020 [page 51]
supported in any use case or configura
tion.
Added the recommended replacement The retirement date for Execution Map is Retirement of Goal Execution [page 26]
Added topic on Replacement of Plateau Starting in 1H 2020, SuccessFactors is Replacement of Plateau Question Editor
Question Editor with Assessments. ending the maintenance of the legacy with Assessments [page 46]
Plateau Question Editor (PQE) function
ality.
Updated the retirement date for V12 The home page is now enabled in all SAP Universal Migration to the Home Page
Home Page. SuccessFactors systems. The last wave [page 13]
of universal upgrades from V12 Home
Page to the latest Home Page was com
pleted in November 2019.
Added a topic on the retirement of the With the retirement of the Recruiting Retirement of Recruiting Marketing Cli
Recruiting Marketing Client Admin. Dashboard to which it was dependent, ent Admin [page 49]
the Recruiting Marketing Client Admin is
now also retired, as of 1H 2020.
Added a topic about Event Reason XML The XML-based approach to derive event Event Reason XML Deprecation [page
deprecation reasons for Job Information and Com 52]
pensation Information Imports will be
deprecated in the 2H 2020 release.
Added a topic about the replacement of As of Q4 2019, we will retire the Success Replacement of SuccessFactory-XML
the SuccessFactory-XML tool Factory-XML tool. Instead, you can use Tool [page 20]
the Manage Templates tool to create and
modify form templates.
Retirement date and information added The Android SAP SuccessFactors Mobile Retirement of the Android SAP Success
App will be removed from the Amazon Factors Mobile App from the Amazon
Appstore in China on November 1, 2019. Appstore in China [page 25]
Users in China will now use the Tencent
App Store to download the Android app.
Q3 2019
Retirement date and information added Support for Apple iOS 11.X (OS version) Retirement of Apple iOS 11.X (OS ver
will end on December 1, 2019. sion) Support [page 24]
Added a topic about replacement of Cali The Calibration V12 Org Chart is now the Replacement of Calibration V11 Org
bration V11 Org Chart default org chart in Calibration. The re Chart [page 32]
tirement date of V11 Org Chart is in 1H
2020.
Added a topic about the retirement of Starting in 1H 2020, CDP Lite will be au Retirement of CDP Lite [page 30]
CDP Lite tomatically deactivated for all customers
who are using this feature.
Added a topic about the retirement of Using the Adobe LiveCycle Designer
[page 50]
Adobe LiveCycle Designer
Added a topic about the replacement of Starting in 2H 2020, the Plateau Ques
tion Editor (PQE) will be replaced with
Plateau Question Editor (PQE) with As
the Learning Assessments Tool.
sessments
Retirement date and information added Support for Android 5.X (OS version) will Retirement of Android 5.X (OS version)
end on July 15, 2019. Support [page 24]
Q1 2019
Q4 2018
Q3 2018
Terminology changed As part of our overall commitment to in SAP SuccessFactors Migrating Features
novation, we've adopted some new lan [page 4]
guage to better reflect the migration ap
proach to the latest innovations and ver
sions.
Removed features past replacement date This guide will only cover features with a
replacement date in:
Added additional information and links, Many topics have been updated to in
where available clude additional information like: key
benefits of the replacement feature; mi
gration information; and links to addi
tional resources.
Replacement of legacy picklists Added information about the replace Replacement of Legacy Picklists [page
ment of legacy picklists (non-MDF pick
19]
lists managed via CSV import).
Q2 2018
Retirements postponed Career Path v1 has no retirement date set Replacement of Career Path v1 [page
at this time. This is a change from the 29]
original date of Q1 2019. This announce
ment has been moved to Retirement
Date 2nd Half of 2019 in this guide.
Features being replaced by newer versions, new technology, or completely new tools, listed by key dates.
Tip
Standard Customers
vSaaS Customers
Standard Customers
vSaaS Customers
Recruiting
platform
The Fiori User Experience is now enabled in all SAP SuccessFactors systems. The last wave of universal upgrades
was completed in November 2019.
SAP Fiori represents the latest in UI technology and SAP design standards. The Fiori User Experience for SAP
SuccessFactors consists of three separate features that are enabled at the same time:
Together, these three upgrades enable you to take advantage of our latest new features and enhancements and
provide a modern user experience that is consistent throughout the HXM Suite and across other SAP solutions.
Remember
We are completing the migration of all customers to the Fiori User Experience. Soon, it will be enabled in all
customer instances and the older UI versions will no longer be available. Please begin preparing to adopt these
important features.
For the latest dates and announcements, please refer to this post on the Customer Community.
The home page is now enabled in all SAP SuccessFactors systems. The last wave of universal upgrades was
completed in November 2019.
The home page provides a user experience based on SAP Fiori design standards and is recommended for use by all
customers. It is the focus of most new features and enhancements on the home page and will eventually entirely
replace the older v12 home page in all instances.
● The home page is part of the Fiori User Experience. The Fiori User Experience consists of three separate
features that are enabled at the same time: the new home page, the People Profile, and the Fiori User Interface.
● We are completing the migration of all customers to the Fiori User Experience. Soon, it will be enabled in all
customer instances and the older UI versions will no longer be available. Please begin preparing to adopt these
important features. For the latest dates and announcements, please refer to this post on the Customer
Community.
● The home page requires role-based permissions (RBP), which is now required for all customers. We have
migrated all remaining non-RBP instances to role-based permissions in the Q2 2019 release. For more
information, please refer to this post on the Customer Community.
Related Information
People Profile is now enabled in all SAP SuccessFactors systems. The last wave of universal upgrades was
completed in November 2019.
The People Profile provides a user experience based on SAP Fiori design standards and is recommended for use by
all customers. It is the focus of most new features and enhancements on the employee profile and will eventually
entirely replace the older v12 employee profile in all instances.
● People Profile is part of the Fiori User Experience. The Fiori User Experience consists of three separate features
that are enabled at the same time: the new home page, the People Profile, and the Fiori User Interface.
● We are completing the migration of all customers to the Fiori User Experience. Soon, it will be enabled in all
customer instances and the older UI versions will no longer be available. Please begin preparing to adopt these
important features. For the latest dates and announcements, please refer to this post on the Customer
Community.
● The People Profile requires role-based permissions (RBP), which is now required for all customers. We are
migrating all remaining non-RBP instances to role-based permissions in the Q2 2019 release. For more
information, please refer to this post on the Customer Community.
Related Information
The Fiori User Interface is now enabled in all SAP SuccessFactors systems. The last wave of universal upgrades was
completed in November 2019.
The Fiori User Interface applies a consistent SAP Fiori visual design to UI elements on many pages throughout the
SAP SuccessFactors HXM Suite, such as dialog boxes, buttons, icons, menus, and widgets. It is enabled in the
Upgrade Center using the Fiori User Experience 2016 upgrade and requires no additional set up or configuration.
● Fiori User Interface is part of the Fiori User Experience. The Fiori User Experience consists of three separate
features that are enabled at the same time: the new home page, the People Profile, and the Fiori User Interface.
● We are completing the migration of all customers to the Fiori User Experience. Soon, it will be enabled in all
customer instances and the older UI versions will no longer be available. Please begin preparing to adopt these
important features. For the latest dates and announcements, please refer to this post on the Customer
Community.
SAP makes Application Programming Interfaces (APIs) available to developers to access SAP services for the
purpose of extending solutions, integrating them with other solutions, or for building new ones. Please be advised
that the following APIs will be deprecated in favor of OData API:
Deprecation is an industry standard terminology for the initial step of the API end-of-life cycle. Deprecated APIs
may be turned off in newly created tenants by default, but can still be turned on in Provisioning. Deprecation is not
decommissioning. Decommissioning is a possible later stage. It does not mean that an API will be removed from
productive environments.
The stated SFAPIs should not be used for new development as they will be turned off in new tenants by default.
Please note that SFAPI can still be enabled in a tenant via provisioning and Instance Sync will copy API settings to
new tenants. Starting immediately, we encourage the use of new APIs which leverage Open Data Protocol (OData)
technology. These new APIs are available in Provisioning.
Please use the new OData technology for any new API development and consider moving your legacy applications
and integrations to OData API. You can refer to https://help.sap.com for more information about OData API.
If you are going to refactor old integrations, please consider using the Integration Center to realize lower cost of
ownership.
What is an API?
An API is a publicly available programming interface that is exposed as a standard http transaction. In a nutshell,
the only difference between a web page and a web API is that the API is called by a machine while the web page is
accessed by a human.
APIs are used when customers build custom SAP Cloud Extensions, when customers are building integrations with
CPI, Dell Boomi, and other general cases.
The partner API is a very old SOAP API available in our older DC4 and DC8 data centers. It has not been
documented for more than 5 years.
These are very inefficient APIs that rely on creating an adhoc report in our system, scheduling the execution of the
report on our scheduler servers, and waiting for the job to complete. Once complete they provide the ability to
download a CSV file containing the data.
These are APIs that access a single entity such as Person, Employment, etc. Unlike CompoundEmployee, they
cannot provide complex related employee data.
This is an advanced API build on the SFAPI protocol that allows access to a complete set of entities related to the
"Person" entity.
API Deprecation is an announcement that the API should not be used for new development and that SAP reserves
the right to decommission it in the future.
● Deprecation is an announcement. Also, when we deprecate an API we may have it ‘off’ by default in new
tenants and we might even disallow the API in new tenants.
● Decommissioning means the API will be disabled in a tenant; it will no longer be available in productive
environments. At this point, any usage of the API will result in a failure.
● Discourages partners and customers from investing new development on old technology when newer
capabilities are available in OData.
● Our new APIs offer more benefits to customers.
● Allows SuccessFactors to focus on improving OData, not maintaining old APIs.
Will the new APIs, which leverage Open Data Protocol (OData) technology, offer
added benefits?
● OData is the only API for newer functionality including Position Management, CRM, Simplify, Time, Benefits,
Job Profile.
● Basic OData queries are faster than older SFAPI single-entity APIs. For example, we measured a basic,
PerPerson query up to four times faster using OData.
● OData’s new snap shot query feature solves pagination problems that exist in SFAPI.
● OData offers more flexibility in joining related data.
● OData is the only API available in Integration Center.
● Unlike SFAPI-Adhoc, OData does not rely on creating and running reports on a scheduler server. There is no
risk of a scheduler being backed up, etc.
When you run an adhoc report API, it doesn't simply run directly against the data as OData does. Instead, it does
the following:
No. This will only occur when the API is decommissioned and that will occur no sooner than 1 year from the
deprecation announcement date.
Yes, it is listed.
No. We’ll continue to support SFAPI and provide bug fixes during the deprecation period. However, we’ll no longer
develop new functionalities for deprecated APIs, and all support will be stopped when an API is decommissioned.
API deprecation can occur on a single function or data entity as well as an entire class/protocol of APIs.
As of Q2 2019 Release, You can run the SFAPI feature status check (Check ID: SFAPIIsTurnedOn) in the Check Tool
under API > Check SFAPI to see whether SFAPI is turned on in your instance. For more information about the
Check Tool, see Using the Check Tool.
APIs that have been used for more than 24 months may be deprecated to improve the quality and functionality of
our APIs. Our API policy states that:
● We will not deprecate an API sooner than 2 years after initial release;
● We will not decommission an API sooner than 1 year after deprecation; and
● We may announce decommissioning sometime after deprecation and at least 1 year prior to the decommission
date.
Note
We respect our customers and your reliance on API, so we will evaluate the usage of the APIs before we
decommission. The primary goal of deprecation is to stop new development on old APIs and encourage moving
to OData. Currently, we have no set date for decommissioning. But when announced, we will provide at least
one year's notice prior to the decommission date.
We are upgrading administrative tools for picklist management and migrating legacy picklists to the Picklist Center.
This migration will leverage SAP SuccessFactors Metadata Framework (MDF) and provide a simplified approach to
picklists.
● A single location where picklists are managed for Employee Central, Recruiting, Talent, and Employee Profile.
● The ability to make changes directly in the application. You no longer have to export picklists and edit them
offline spreadsheet.
● The ability to make only the change you need. You no longer have to import and update all picklists at once, just
to make a single label change.
● Unique external codes for simplified picklist management across your system. Unique external codes make
picklists and picklist values easier to identify and manage across environments.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
Varies by datacenter. Full migration of all customer systems targeted by end of 1H 2019.
For the latest scheduled dates, please refer to the SAP SuccessFactors Community .
Additional Resources
As of Q4 2019, we will retire the SuccessFactory-XML tool. Instead, you can use the Manage Templates tool in
Admin Center to create and modify form templates for Performance Management, Goal Management, and Career
Development Planning.
The Manage Templates tool allows you to create and modify all kinds of form templates easily and quickly. Using
Manage Templates you can:
Key Dates
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
The SuccessFactory-XML tool has been in end of maintenance since about 5 years ago. No more maintenance
activities are performed for this tool.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
As of Q4 2019, we will retire the SuccessFactory-XML tool.
If your company solely uses the SuccessFactory-XML tool to manage templates, please go through the following
steps to migrate to Manage Templates:
More Information
● Visit the SAP SuccessFactors Customer Community for the latest updates and discussions on retiring the
SuccessFactory-XML tool.
● Visit the SAP Help Portal Configuring Templates Using Admin Center and Configuring 360 Templates Using
Admin Center for the guides on using Manage Templates.
We will retireBulk Employees Import and Delta Employees Import in the Second Half 2020.
Bulk Employees Import and Delta Employees Import are import jobs in the Manage Scheduled JobsDelta Employees
Import tool from Provisioning. We retire them because they are likely to cause database deadlock or other data
issues.
Key Dates
● End of Maintenance
2H 2020 is the last release in which maintenance activities will be applied toBulk Employees Import and Delta
Employees Import .
● Replacement DateDelta Employees: The date after which the feature or version is permanently disabled and
no longer supported.
As of 2H 2020, we will retire Bulk Employees Import and Delta Employees Import.
Replacement Features
We recommend that you useEmployee Import or Basic Import in Admin Center as replacement features. .
Employee Import is used in the instances that don't have Employee Central enabled, while Basic Import in the
instances that have Employee Central enabled. The two import jobs have better stability and allow you to update
user data to the system yourself instead of contacting Support or partners to do it in Provisioning.
Note
● If you are using the Transfer Inbox documents for C-Step users during Bulk User Import (Works only for E,
EM, EX and EP Roles) option in Bulk Employees Import and Delta Employees Import, please note that the
replacement features don't have this option, and you need to wait for further announcement from
Performance Management to see where and how you can continue using this option after the 2H 2020
release.
● In the instances that have Employee Central enabled,if you want to use Automatic Process Owner Change
To New Manager For In-Progress Documents When Old Manager is Process Owner (Only for 360), Automatic
Process Owner Change To New Manager For Completed Documents When Old Manager is Process Owner
(Only for 360), or Remove Inactive Employees' 360 Evaluation Documents , you can consider HRIS Sync
because Basic Import doesn't contain these options.
● Visit Managing Basic User Data by Using a Data File on SAP Help Portal to find how to use Employee Import.
● Visit Employee Data Import Process on SAP Help Portal to find how to use Basic Import.
● Visit Configuring an HRIS Sync Job on SAP Help Portal to find how to use HRIS Sync.
Support for Android 5.X (OS version) will end on July 15, 2019.
Google released Android 9.0 on August 6, 2018; therefore, SAP SuccessFactors Mobile will drop support for
Android 5.X (OS version) on July 15, 2019 due to decreased usage. The following Android OS versions are no longer
supported: 5.0, 5.0.1, 5.0.2, 5.1, 5.1.1. Please work with your IT organization to update your Android 5.X mobile
devices to Android 6.X and above before July 15, 2019.
Important Date
● Retirement Date: The date after which the feature or version is permanently disabled and no longer
supported.
Official Retirement of support for Android 5.X is July 15, 2019.
Support for Apple iOS 11.X (OS version) will end on December 1, 2019.
Apple Inc. has announced the availability of iOS 13 for iPhone and iPadOS 13 for iPad to be released in September
2019; therefore, SAP SuccessFactors Mobile will drop support for iOS 11.X (OS version) on December 1, 2019 due to
decreased usage. Please work with your IT organization to update your iOS 11.X mobile devices to iOS 12.X and
above prior to December 1, 2019.
Important Date
● Retirement Date: The date after which the feature or version is permanently disabled and no longer
supported.
Official Retirement of support for iOS 11.X is December 1, 2019.
The Android SAP SuccessFactors Mobile app will no longer be available for download through the Amazon
Appstore in China as of November 1, 2019. The Tencent App Store is now the only officially sanctioned Android app
store for SAP in China.
Customers in China, who have previously downloaded the Android application from the Amazon Appstore, should
delete the existing app and redownload it through the Tencent App Store. Otherwise, users will not receive any
updates for the Android SAP SuccessFactors Mobile app. All Android app updates will only be available through the
Tencent App Store.
New users should also only use the Tencent App Store in China to download the Android app.
Redownloading the Android app will not impact existing functionality or underlying data.
Important Date
● Retirement Date: The date after which the feature or version is permanently disabled and no longer
supported.
Official Retirement of the Android SAP SuccessFactors Mobile app from the Amazon Appstore in China is
November 1, 2019.
Important Dates
● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
There is no change in customer support during this phase. Customers are encouraged to start planning their
upgrade for the feature or version.
No functional enhancements are being made or planned for the Goal Execution tool. Only high priority or
critical bugs, if reported, will be fixed.
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
The end of maintenance for Goal Execution tool is planned for the second half of 2019.
● Retirement Date: The date after which the feature or version is permanently disabled and no longer
supported.
The retirement date for Execution Map is planned for the second half of 2020.
The retirement date for Status Report and Meeting Agenda is planned for the first half of 2021.
Note
Currently, the end of maintenance and retirement dates are tentative and subject to change.
Migration Information
The recommended replacement for Execution Map is Goal Alignment Chart. For more details about Goal Alignment
Chart, see Goal Alignment Chart.
The recommended replacement for Status Report and Meeting Agenda is Continuous Performance Management.
To learn more about how you can start using this tool, see the Continuous Performance Management guide.
More Information
SAP SuccessFactors Performance Management has enhanced its latest UI version, Performance Management v12
Acceleration, in line with the overall SAP Fiori design standards, and is recommended for use by all customers now.
All major functional gaps between the older (v11, old v12) versions and the v12 Acceleration version were closed
with the Q3 2015 release.
Planning Update
● All major functional gaps between Performance Management v11 and old v12 and Performance Management
v12 Acceleration were closed, as of the Q3 2015 Release.
● No additional functional or feature enhancements will be made to Performance Management v11 and old
Performance Management v12.
Important Dates
● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
There is no change in customer support during this phase. Customers are encouraged to start planning their
upgrade for the feature or version.
Since Q3 2015, functional enhancements are not being made for the old Performance Management v12 and v11
versions.
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
Official End of Maintenance for Performance Management v11 and old Performance Management v12 occurred
with the Q2 2018 Release, and therefore patches can no longer be made.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
The last release in which customers can productively use Performance Management v11 and old Performance
Management v12 is Q1 2019.
As of the Q2 2019 release, we will automatically activate the Performance Management v12 Acceleration form
template for all those customers who have not yet migrated. After the deployment of the Q2 2019 release,
Performance Management v11 and old Performance Management v12 form launches will no longer be
supported.
This significant upgrade brings many features from Performance Management v11 to the Performance
Management v12 look and feel. Performance Management v12 Acceleration will be the version of the Performance
Management product that will continue to be developed with new features and enhancements.
More Information
● Visit the SAP SuccessFactors Customer Community for the latest updates and discussions on migrating to
Performance Management v12 Acceleration.
● If you are using standard configurations, we provide a conversion tool to enable you to convert your templates
for free. See Validating and Updating Existing Performance Management Forms .
Career Development Planning has been enhanced with a newer, more flexible Career Path functionality.
While Career Path v2 does not support role import, due to a difference in architecture, it does support branching
paths and a higher fidelity to real world career paths, making it a more modern and sophisticated tool.
● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
There is no change in customer support during this phase. Customers are encouraged to start planning their
upgrade for the feature or version.
Starting from Q4 2017, functional enhancements will only be made to Career Path v2 or higher.
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
Q4 2017 is the last release in which maintenance activities, such as code fixes, will be applied to versions other
than v2. As of Q1 2018, no more maintenance activities will be performed for Career Path v1.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
At this time, the replacement date for Career Path v1 is not yet set. It will be announced as soon as possible.
Contact SAP Cloud Support or your implementation partner to enable Career Path v2 in your system.
More Information
● Visit the SAP SuccessFactors Customer Community for the latest updates and discussions on migrating to
Career Path v2.
● Refer to the Career Development Planning guide for details on setting up and configuring Career Worksheet
v12.
Starting in Q2 2020, we will automatically deactivate CDP Lite for all customers who are still using this feature.
CDP Lite was a lightweight feature for Performance and Goals customers. It allowed customers to configure
development goals accessible only within Performance Management forms. The feature didn't allow customers to
associate learning activities to development goals, nor did it support competencies associated with development
goals.
CDP Full enables the full version of SAP SuccessFactors Career Development Planning. It has the following
features:
● Development Plan
● Career Worksheet
● Career Path
The full version also supports a full customization for development plans and links to SAP SuccessFactors
Learning.
Key Dates
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
CDP Lite has been in end of maintenance for a while. No more maintenance activities are performed for this
feature.
● Retirement Date: The date after which the feature or version is permanently disabled and no longer
supported.
Q1 2020 is the last release in which customers can productively use CDP Lite. As of Q2 2020, we will
automatically deactivate the feature for all customers who are still using it.
More Information
Visit the SAP SuccessFactors Customer Community for the latest updates and discussions on retiring CDP Lite.
SAP SuccessFactors Calibration has updated its UI in line with the overall SAP Fiori design standards and is
recommended for use by all customers now. There are no major functional gaps between the legacy and the new UI
versions. The new UI version is now the default UI of Calibration.
Important Dates
● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
There is no change in customer support during this phase. Customers are encouraged to start planning their
upgrade for the feature or version.
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
Starting from Q3 2018, no more maintenance activities will be performed for legacy UI. Functional
enhancements will only be made to the new UI version.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
Post Q3 2019, we will automatically activate the new UI version for all those customers who have not yet
enabled the new UI version themselves.
You can toggle between the legacy UI and the new UI version, for now. However, you can no longer use the legacy UI
after Q3 2019.
For more information and the latest updates, go to the SAP SuccessFactors Community.
● Visit the SAP SuccessFactors Customer Community for the latest updates and discussions on migrating to
the latest Calibration UI.
● Refer to the Calibration guide for details on setting up and configuring your system.
SAP SuccessFactors Calibration has updated its UI in line with the overall SAP Fiori design standards, and the latest
UI version is recommended for use by all customers now. The Calibration V12 Org Chart is now the default org chart
in Calibration.
Important Dates
● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
There is no change in customer support during this phase. Customers are encouraged to start planning their
upgrade for the feature or version.
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
Starting from Q4 2019, no more maintenance activities will be performed for Calibration V11 Org Chart.
Functional enhancements will only be made to Calibration V12 Org Chart.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
With the Q2 2020 release, we’ll automatically activate Calibration V12 Org Chart for all those customers who
haven’t yet enabled it.
The Q3 2019 release automatically upgrades the V11 Org Chart to the V12 Org Chart. For now, you still can switch
back to the V11 Org Chart. However, you can no longer use the V11 Org Chart after Q1 2020.
Note
You can also deselect Enable Calibration V12 Org Chart in Provisioning.
More Information
● For all information about required feature updates/migrations, visit Calibration Innovation Alerts .
● To engage and stay current with the latest information about Calibration, visit Calibration Community .
We follow a process for decommissioning and replacment of old features in SAP SuccessFactors Learning.
● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
There is no change in customer support during this phase. Customers are encouraged to start planning their
upgrade for the feature or version.
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
All major browser providers have announced end-of-life for Flash in response to Adobe’s plans to deprecate Flash
and related support after 2020. SuccessFactors Learning Administration currently depends on Flash for menus,
navigational elements, and managing core entities. We’re proactively transitioning SAP SuccessFactors Learning
Administration from Flash to HTML to ensure continuity with latest browser support. This change will be applied to
Preview environments in the first half of 2020.
To provide a smooth transition, time to adapt to these changes, and support your change management activities,
the new interface runs concurrently with the existing Flash interface for two releases. You will be able to navigate in
both old and new modes before the Flash technology is fully retired.
All Learning customers will be impacted by the Flash Replacement in Learning Administration.
Key Dates
For the retirement of Flash in the Learning Administrator interface, the following dates apply:
● Push to Development: In the first half of 2020, the new HTML-based Learning Administration interface will be
automatically applied to Preview environments. Customers will have two releases to use both the Flash and the
new non-Flash version of the Learning Administrator Interface concurrently.
Note
Validated Learning Customers will have the new Learning Administration interface automatically applied to
Preview environments during this time.
● Replacement Date: In the second half of 2020, the Flash-based Learning Administrator interface will no longer
be available in Preview and Production environments. The new HTML-based interface will replace it as the
default interface.
Note
Validated Learning Customers will have the Flash-based Learning Administration interface automatically
removed from Preview environments with the last patch before the Production upgrade. The new Learning
Administration interface will update to Production with the upgrade to the 2020 VSaaS release.
Customers are advised to identify portions of the Learning Administration Interface that are Flash-based, which will
be replaced with the new HTML version.
Customers should also update job aids or training materials. All customer-owned and created Flash-based
Learning materials, such as videos, are the responsibility of the customer to update and change.
Customers will be updated automatically with a universal push of the new, non-Flash-based version of the new
Learning Administrator Interface to Preview and Production.
More Information
● Visit the SAP SuccessFactors Customer Community Product Innovation Page for all the latest updates and
discussions.
Starting in Q1 2019, we will no longer support Learning Catalog 2.0. Please enable Learning Catalog 3.0.
● End of Maintenance: Leading up to the retirement dates below, we won't have any maintenance activities:
patches or fixes for Catalog Search 2.0. This applies to both standard and validated customers.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
We will remove Learning Catalog 2.0 from non-validated LMS customers in the Q1 2019 release. Please watch the
release page on the community for dates.
We will remove Learning Catalog 2.0 from validated customers' sandbox environments in Q3 2019, from preview
environments in October 2019, and production environments in March 2020.
More Information
● Visit the SAP SuccessFactors Customer Community Product Innovation Page for all the latest updates and
discussions.
● Join the conversation on the SAP SuccessFactors Customer Community Learning Page
In the Q1 2019 release, we will no longer support the old supervisor tool for assign and remove learning, record
learning, and register and withdraw users. We will also not support the old user record learning tool. Please update
to the new tools.
For Legacy Supervisor and User Tools the following dates apply:
● End of Maintenance: Leading up to the retirement dates below, we won't have any maintenance activities:
patches or fixes for the legacy tools. This applies to both standard and validated customers.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
We will remove legacy tools from non-validated LMS customers in the Q1 2019 release. Please watch the release
page on the community for dates.
We will remove legacy tools from validated customers' sandbox environments in Q3 2019, from preview
environments in October 2019, and production environments in March 2020.
More Information
● Visit the SAP SuccessFactors Customer Community Product Innovation Page for all the latest updates and
discussions.
● Join the conversation on the SAP SuccessFactors Customer Community Learning Page
Update Learning manager and user tools to take advantage of new functionality and experiences for users and
managers when they add learning history and when managers register or withdraw users or assign or remove
learning from users.
Procedure
We recommend the default setting of true because we also recommend that you do not collect sensitive
personal data in the registration forms. If you do not collect sensitive personal data in the custom columns,
then you can give managers the confidence of assisting their teams when registering them. In addition, a
minority of customers uses custom data in registration forms.
6. To change the number of employees that a manager can withdraw in one action, change
supervisorMaxUserRegisterWithdrawLimit.
We don’t recommend changing this value from its default because we set it at a reasonable number for the
managers' experience. If you set it too high, it becomes difficult for managers to understand who they’re
withdrawing without a benefit and with a potential drawback. Managers rarely need to withdraw more than 50
users at once, and if you allow them to withdraw a high number to solve an edge case, they won't batch their
withdraws and might end up withdrawing a user that they didn’t mean to withdraw. In the rare case that
managers need to withdraw users over the limit, they can still do it, they just need to batch the users.
7. Click Apply Changes.
Starting in Q3 2019, SAP SuccessFactors will no longer support some Learning Administration features. We will
remove them in Q1 2020.
The power search bar is at the top of the Learning Administration environment.
The recommended next and guide me modes show administrators next steps when next steps are in a different
area of the application.
Recommended Next
Guide me mode is an optional selection that administrators could disable. On some objects, when they are
available on the home page, administrators could see the actions in a list when the actions were in different parts of
the application.
You will no longer be able to change the order of the tabs for important parts of Learning. You currently do this in
System Admin Configuration Record Configuration .
Administrators will no longer be able to personalize their view of fields by adding or removing fields from their view.
We are retiring parts of the Learning application that are handled by Employee Central.
For customers using the commerce functions of Learning, we are removing the purchasing assistant and
chargeback adjustment tools that you currently access in Commerce Tools .
Stand alone SAP SuccessFactors Learning implementations will no longer be supported after Q3 2018.
Beginning with the acquisition of Plateau in 2011, we have worked to integrate Learning into all aspects of the SAP
SuccessFactors suite and we will continue to do so in the future. As Learning becomes more tightly integrated with
the SAP SuccessFactors platform, we introduce dependencies that may make new features unavailable and limit
the functionality of features in environments that do not include the platform.
As a result, we no longer support stand alone Learning environments (environments where Learning is not being
used in conjunction with the SAP SuccessFactors platform) after Q3 2018. As of Q3 2018, all SAP SuccessFactors
Learning customers (both validated and non-validated) are required to be running the Learning Management
System (LMS) in an integrated environment with the SAP SuccessFactors platform enabled.
This change affects a small percentage of our customers because 99% of our customers are already using SAP
SuccessFactors Learning in an integrated environment. For those who are not, your Customer Engagement
Executive will contact you to explain the benefits of using SAP SuccessFactors Learning in an integrated
environment and to help you formulate a plan for transition.
Between Q3 2018 and Q3 2020, the following native login configurations are supported. All others are not
supported.
For the time between Q3 2018 and Q3 2020, we support a few cases of native user login - users who can log in
without going through SAP SuccessFactors platform. These narrow cases are to allow customers time to migrate to
new methods. All other cases of native user login aren’t supported as of Q3 2018.
Note
Not supported means: we don't provide any guidance or help through customer support channels because the
application isn’t certified for unsupported configurations.
We support users who have the shopping cart type of external. You can check users' shopping cart types by logging
into SAP SuccessFactors Learning Administration and then going to People Users . Find and open the user,
and then go to Finance. You see the user's shopping account type.
Users with shopping account type of external are members of your extended enterprise. For example, if you have a
dealership model, and employees of dealerships log on to their own learning sites to consume your training, those
employees of the dealerships are external users and they have external shopping accounts. We address defects
related to these types of users who have trouble signing in.
If a user has shopping account type of internal, we don’t support that user's ability to log in natively. The user must
log in through platform. We don't address defects related to these types of users who have trouble signing in
directly to Learning.
Learning Administrators
Because we have some cases, particularly during implementation, when administrators must sign in directly to
Learning, we still support it, but it’s discouraged. We encourage administrators to log in through standard means:
SAP SuccessFactors platform.
We don't support dual sign-in: Administrators who sometimes sign in through SAP SuccessFactors platform and
sometimes directly into Learning.
In H2 2020, native Learning users will no longer be supported in any use case or configuration.
Until H2 2020, we might continue to support some cases of native Learning users. In H2 2020 and later, we stop
support for all native Learning users. All users of any configuration must use standard SAP SuccessFactors sign in
management. That includes, for example:
● No support for any type of native sign-in: Administrators, end-users, external, or internal.
● No support for any type of native user functions. We won’t address defects related to native learning
functionality.
In H2 2020 or soon after H2 2020, we’ll actively remove parts of our product that relate to native users.
Note
If you still have native users, please engage with professional services to be prepared for the transition.
Starting in 1H 2020, SuccessFactors is ending the maintenance of the legacy Plateau Question Editor (PQE)
functionality. Use the enhanced Learning Assessments Tool to create exams and questions.
SAP SuccessFactors Learning first released the Learning Assessments Tool in Q3 2017 to provides more options for
different types of assessments. We continue to enhance the Assessment tool further with enriched functionalities.
Benefits of Assessments
Key Dates
Key Dates
● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
If you’re still using PQE, you must plan to move to Assessments now to ensure that you’re using Assessments fully
by the time PQE is no longer available.
More Information
● Visit the SAP SuccessFactors Customer Community Learning Product Innovation page for all the latest
updates and discussions.
● Join the conversation on the SAP SuccessFactors Customer Community for Learning specifically for this
migration of PQE to Assessments.
As the deprecation date for Adobe Flash approaches, we've moved the core features of Recruiting Dashboard to
SAP SuccessFactors Recruiting Management and continue to invest in features to provide you with a streamlined
recruiting experience.
All major browser providers have announced end-of-life for Flash in response to the announcement by Adobe of
plans to deprecate Flash and any related support after 2020.
In SAP SuccessFactors Recruiting Marketing, the Recruiting Dashboard depends on Flash for the user experience.
In preparation for these changes, we've continued our efforts to evolve our Recruiting solutions with functionality
like Candidate Relationship Management, Candidate Account Simplification, and Career Site Builder. Our goal is to
provide a simplified recruiting product and actionable data to streamline your recruiting activities and aid you in
making informed decisions.
Recruiting Solutions
Recruiting Dashboard Functionality Solution
Source reporting Source Report and Source Tracker in Job Marketing; Advanced
Analytics
Talent Community and Talent Community Marketing Candidate Account Simplification; Email Campaigns in Candi
date Relationship Management
Key Dates
● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
There is no change in customer support during this phase. Customers are encouraged to start planning their
upgrade for the feature or version.
As of this announcement, in Q4 2018, no further enhancements are being made to the Recruiting Dashboard.
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
Q4 2018 marks the end of maintenance for Recruiting Dashboard.
● Retirement Date: The date after which the feature or version is permanently disabled and no longer
supported.
More Information
You can safely ignore any references or configuration settings in Command Center to the dashboard. Selecting
them has no effect, and they do not generate errors.
Visit the SAP SuccessFactors Customer Community Recruiting Resources Blog for all the latest updates and
discussions.
Due to the retirement of the Recruiting Dashboard and replacement of the Candidate SSO, the SAP SuccessFactors
Recruiting Marketing client admin has been retired.
The client admin was designed to accommodate candidates who had an account in Recruiting Marketing without a
corresponding account in Recruiting Management in the following circumstances:
If you recently moved from Candidate SSO to Candidate Account Simplification (CAS) and you still have some
users in your system that only have Recruiting Marketing accounts, CAS will automatically merge their accounts
with Recruiting Management accounts when they log back in.
If you are a Recruiting Marketing customer using client admin, contact your implementation partner for a
customized solution or to implement the Career Site Builder tool.
Use the Adobe LiveCycle Designer to provide your own form templates for the SAP Forms by Adobe REST API.
Adobe LiveCycle Designer supports you in creating templates for interactive and print forms by providing a wide set
of design functions.
Find more information in this section how to install and use the Adobe LiveCycle Designer.
To download and install or update the Adobe LiveCycle Designer, follow the instructions in SAP note 2187332
(download and installation of version 11.0).
Related Information
Starting 1H 2020 Release, the Live Analytics feature in Variable Pay is no longer supported in any use case or
configuration.
For the retirement of Live Analytics in the Variable Pay Administrator interface, the following dates apply:
● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements are delivered and only high priority bug fixes are considered. There’s
no change in customer support during this phase. Customers are encouraged to start planning their upgrade
for the feature or version.
Official End of Development for Live Analytics is planned for the Q3 2019 Release.
● End of Maintenance: The date after which no further bug fixes or patches are delivered for the feature or
version. Customer support is limited to how-to help.
Official End of Maintenance for Live Analytics is planned for the Q4 2019 Release.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
Official Replacement Date for Live Analytics is planned for the 1H 2020 Release.
What's Next?
● How to upgrade?
No upgrade is required.
To know more about product and feature retirements, visit the SAP SuccessFactors Customer Community .
As of 2020 2H release, the XML-based approach to derive event reason for Job Information and Compensation
Information imports is deprecated from your system.
The existing process of using XML-based rules in the Succession Data Model to derive the event reasons for
changes to Job Information and Compensation Information of employees is no longer supported. You can now
employ business rules to achieve the same purpose.
Existing rules in XML will be migrated into onSave business rules automatically. All the migrated rules will start with
the postfix 'migratedRule'. Example: compInfoModel_ERD_migrated_rule
If there are multiple rule conditions in your XML data model, the migration process will combine all of them into a
single business rule, which will be available for Job Information and Compensation Information alike.
Example
XML Rule:
Sample Code
<rule id="rule-PT1">
<trueoutput>POS_XFR</trueoutput>
<conditions>
<and>ch
<equal id="jobInfo.pay-grade" inverse="true"/>
<equal id="jobInfo.position" value="" inverse="true"/>
<equal id="jobInfo.cost-center" value="63000" />
</and>
</conditions>
</rule>
<rule id="rule-PT2">
<trueoutput>POS_XFR</trueoutput>
<conditions>
<and>
<equal id="jobInfo.job-code" inverse="true"/>
<equal id="jobInfo.position" value="" inverse="true"/>
<equal id="jobInfo.cost-center" value="63000" />
</and>
</conditions>
</rule>
<rule id="rule-PR1">
<trueoutput>POS_RECLASS</trueoutput>
<conditions>
<and>
<equal id="jobInfo.business-unit" inverse="true"/>
<equal id="jobInfo.position" value="" inverse="true"/>
<equal id="jobInfo.cost-center" value="63000" />
</and>
</conditions>
</rule><rule id="rule-23">
<!-- Catch all-->
<trueoutput>DATACHG</trueoutput>
<conditions>
</or>
</conditions>
</rule>
Note
In the migrated business rule, there’s an initial condition to check whether the event reason value is blank or
null. Ensure that you don't modify or remove this condition.
The new business rules will be automatically assigned to both Job Information and Compensation Information
HRIS elements, and can be found both in the data model and the Business Configuration UI (added as a first trigger
rule).
To create rules for deriving event reasons with Job Information and Compensation Information imports, you can
use the Event Reason Derivation rule scenario under Employee Central Core rule category on the Configure Business
Rules page. These rules must be executed during events when data is saved (onSave). You no longer need to submit
support tickets to adjust the XML.
● The removal of the legacy Enable youCalc rules engine for HRIS switch.
● Decoupling of two switches, Enable Business Rules for Workflow Derivation and Enable Business Rules for Event
Reason Derivation. The behavior of these two switches are as follows:
○ If Enable Business Rules for Workflow Derivation is enabled, workflows will be derived using business rules.
Otherwise, workflow derivation happens from the XML model.
○ If Enable Business Rules for Event Reason Derivation is enabled, event reasons will be derived using
business rules. Otherwise, event reason derivation will be disabled.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you're no longer working with an implementation partner, contact SAP Cloud
Support.
Important Dates
● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
There is no change in customer support during this phase. Customers are encouraged to start planning their
upgrade for the feature or version.
From Q4 2019, functional enhancements haven’t been made for the Event Reason XML template.
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
Official End of Maintenance for the Event Reason XML Template occurred with the 2020 1H release, and
therefore patches can no longer be made.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
The last release in which customers can productively use Event Reason XML Template is 2020 1H.
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use genderspecific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
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.