SAP Note

2482453 - SAP S/4HANA 1709: Release Information Note

Component: XX-SER-REL (Business Suite and SAP S/4HANA Release Information), Version: 59, Released On:
28.02.2024

Symptom
This Release Information Note (RIN) contains information and references to notes for applying Feature Package
(FP)/Support Package (SP) Stacks of product version SAP S/4HANA 1709.
Note: This SAP note is subject to change. Check this note for changes on a regular basis. All important changes are
documented in section "Important Changes after Release of SAP S/4HANA 1709".

GENERAL INFORMATION
SAP S/4HANA 1709 will be in mainstream maintenance until 31.12.2022. For SAP S/4HANA 1709 SAP offers optional
extended maintenance. Please refer to SAP Note 3246630 for further information about extended maintenance for SAP
S/4HANA 1709.
For further information about the customer-specific maintenance please refer to SAP note 52505. For information about the
SAP S/4HANA 2040 maintenance commitment, please refer to SAP note 2900388.
We strongly recommend to upgrade your system to the latest SAP S/4HANA on-premise release.
General / Important Considerations
Please refer to the specific documentation under section product documentation. We recommend setting up your system
to display a dynamic documentation, which reflects the latest Feature or Support Package Stack of this release. If you
want to stay on Feature Package Stack 00 to 02 for a longer period, and if you also want to display the corresponding
documentation for one of these Feature Package Stacks, you will find all necessary information in SAP note 2904379.
For supported application server platforms, please refer to the Product Availability Matrix. When planning your system
landscape(s) for SAP S/4HANA 1709, you may want to take the available application server platforms for the next
releases of SAP S/4HANA into account. Please refer to SAP note 2620910 for details.
SAP S/4HANA 1709 is based on SAP NetWeaver 7.52 for SAP S/4HANA 1709. The supported Kernel version is SAP
KERNEL 7.53 64-BIT UNICODE. For the recommended Kernel versions please refer to note 2083594.
For the specific Front-end/UI for SAP S/4HANA 1709, please refer to note 2482461, which is the release information
note for product version SAP FIORI FOR SAP S/4HANA 1709.
For general restrictions as well as restrictions for the conversion to SAP S/4HANA 1709, please refer to SAP note
2491467.
For process integration capabilities with other SAP on-premise solutions, please refer to note 2495662.
If you have add-ons installed on your system and/or want to use them on product version SAP S/4HANA 1709, please
refer to SAP note 2214409.
Please be aware that SAP S/4HANA 1709 is a Unicode-only release. Non-Unicode systems are not supported
anymore. Hence upgrades of non-Unicode systems without prior Unicode conversion are not possible. For details
see Upgrade of non Unicode systems or service.sap.com/Unicode and SAP note 2033243.
A new inventory data model will be delivered. This new inventory data model has a lot of advantages at S4. With the S4
new inventory data model delta stock quantities instead of total stock quantities are transferred to APO. At APO code
changes need to be implemented to get this delta stock quantities processed. SAP Note 2816388 contains a list of all SAP
Notes to be implemented at APO to realize these code changes.
In case you face issues with Advanced Variant Configuration, please refer to note 2811164.
United Kingdom leaving the EU: For information on how a “hard Brexit” (= a no-deal scenario) would impact your
SAP S/4HANA system, please see SAP Note 2749671.
For the implementation of ELSTER modules using the ERiC libraries and the corresponding impact on platform
support, please see notes 2745249 and 2558316.
For more information regarding LEGAL VAT TAX CHANGE in Germany , please see SAP note 2934992
Installation Information
For the system installation, please refer to the installation guide.
You need at least Software Provisioning Manager (SWPM) Support Package 21 for the installation. Please make sure that
you always use the latest patch level of SWPM available at support.sap.com/software/sltoolset.html.
Upgrade Information
You can upgrade from SAP S/4HANA, on-premise edition 1511 or SAP S/4HANA 1610 to SAP S/4HANA 1709.
For the system upgrade, please refer to the upgrade guide.
 You need at least Software Update Manager 2.0 (SUM) for the upgrade. Please make sure that you always use the latest
patch level of SUM available at support.sap.com/software/sltoolset.html.
SAP HANA database requirements
The minimum required revision is defined in the respective Support or Feature Package Stack note.
Detailed information about SAP HANA 2.0 Revision and Maintenance Strategy can be found in SAP note 2378962.
If you plan to upgrade your SAP HANA database to a newer revision or a newer available SPS level,
Refer to SAP note 1906576 for SAP HANA client and server cross-version compatibility and
Refer to SAP note 2655761 for restrictions and recommendations regarding specific revisions of SAP HANA
database for use in SAP S/4HANA.
Conversion Information
Please note that a system conversion to SAP S/4HANA 1709 is no longer possible or supported for
for newly starting system conversion projects – independently of the Enhancement Package or SP level of
the SAP ERP source system.
for any system which is on the following SAP ERP SP levels or higher: 600 SP30, 602 SP20, 603 SP19, 604 SP20,
605 SP17, 606 SP20, 616 SP12, 617 SP15, 618 SP09
For any system which is below the following SAP ERP SP levels and have to go to S/4HANA 1709, open a message on
CA-TRS-PRCK: 600 SP30, 602 SP20, 603 SP19, 604 SP20, 605 SP17, 606 SP20, 616 SP12, 617 SP15, 618 SP09
You can convert to the successor product versions of SAP S/4HANA.
Support Package Stacks on SAP Support Portal

You will find general information about Support Package Stacks on SAP Support Portal
at support.sap.com/software/patches/stacks.html. The Schedule for Support Package Stacks is available at
support.sap.com/maintenance-schedule.

Other Terms
SAP S/4HANA 1709

Reason and Prerequisites

You want to get additional information about product version SAP S/4HANA 1709.

Solution
SUPPORT PACKAGE STACK 13 (10/2023)
General / Important Considerations
The minimum required revision of SAP HANA 2.0 is SPS 02 Revision 24. SAP generally recommends customers to
implement the highest SAP HANA 2.0 revision available. Please take in account that the minimum required revision is
out of maintenance. For more details, please refer to note 2378962 (SAP HANA 2.0 Revision and Maintenance
Strategy).
Note: The minimum database support package listed in column “Database version” in the product availability matrix
can differ because it only refers to the combination of database and operating system version. However, product versions
on top can have stricter requirements to the minimum database SP
For the specific Front-end/UI for SAP S/4HANA 1709, please refer to note 2482461 which is the release information
note for product version SAP FIORI FOR SAP S/4HANA 1709. Support Package Stack 05 of SAP S/4HANA 1709 in the
back-end requires Support Package Stack 01 or higher of SAP FIORI FOR SAP S/4HANA 1709 on the front-end (and
vice versa).
Installation Requirements
For the system installation, please refer to the installation guide.
You need at least Software Provisioning Manager (SWPM) Support Package 24 for the installation. Please make sure
that you always use the latest patch level of SWPM available at support.sap.com/software/sltoolset.html.
Please refer to SAP note 306695 ('Field EMDST13 is unknown' after installing IS-U/CCS) after installation.
Upgrade Requirements
You can upgrade to SAP S/4HANA 1709 from following source releases:
SAP S/4HANA, on-premise edition 1511 (Please be aware that your software level is not higher than Support
Package Stack 10.)
SAP S/4HANA 1610 (Please be aware that your software level is not higher than Support Package Stack 11.)
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that
all corrections already applied on the source system are also part of the target release Support Package stack so as
not to downgrade the system. If a higher Support Package is already implemented on your source system, you need
to upgrade to a higher Support Package of the target release.
 For the system upgrade, please refer to the upgrade guide.
You need at least Software Update Manager (SUM) 2.0 Support Package 03 for the upgrade. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
If the upgrade aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the upgrade aborts with error DT201 during activation of technical settings, please see note 2683419.
If you use Advanced Compliance Reporting (ACR), please see note 2964762.
Conversion Requirements
Please note that a system conversion to SAP S/4HANA 1809 is no longer possible or supported
for newly starting system conversion projects – independently of the Enhancement Package or SP level of the
SAP ERP source system.
for any system which is below the following SAP ERP SP levels and have to go to S/4HANA 1809, open a message
on CA-TRS-PRCK
for any system which is on the following SAP ERP SP levels or higher: 600 SP30, 602 SP20, 603 SP19, 604 SP20,
605 SP17, 606 SP20, 616 SP12, 617 SP15, 618 SP09.
You can convert to the successor product versions of SAP S/4HANA.
Support Package Update (via Software Update Manager (SUM) or SPAM)
Depending on the SAP_BASIS 752 SP-level in the start system, please ensure that you have applied the following notes
or the respective SAP_BASIS 752 Support Package containing the corrections before you start the Support Package
Stack Update to SAP S/4HANA 1709 Support Package Stack 03:
2513147 - Table logging can be activated even though table is too wide (required for start systems on SAP_BASIS
752 SP00, for further background information please check SAP note 2683419)
2563164 - DD: Activation of DDL view fails without error message (required for start systems on SAP_BASIS 752
SP00 and SP01)
2548843 - DD: data element changes from DEC to CURR, error for dependent VIEWs (required for start systems
on SAP_BASIS 752 SP00, SP01 and SP02)
2603860 - Data Dictionary: Wrong calculation of RC in mass activation (required for start systems on SAP_BASIS
752 SP00, SP01 and SP02)
In case you are using SPAM for the SP-update from FPS02 to SPS03, the SP import might abort during execution of
After-Import methods with errors for After-import method “FDT_AFTER_IMPORT”. Similar aborts can also occur
when importing multiple FP-/SP-Stacks in a single queue (errors might be listed for additional After-import methods
like “SACMDT_AFTER_IMP_DCL”). In both cases, please restart the Feature / Support Package Stack import in SPAM
again.
In case of runtime errors DBSQL_SQL_DEADLOCK_DETECTED, please see note 2705194.

Notes to be applied on top of Support Package Stack 13

SUPPORT PACKAGE STACK 12 (04/2023)
General / Important Considerations
The minimum required revision of SAP HANA 2.0 is SPS 02 Revision 24. SAP generally recommends customers to
implement the highest SAP HANA 2.0 revision available. Please take in account that the minimum required revision is
out of maintenance. For more details, please refer to note 2378962 (SAP HANA 2.0 Revision and Maintenance
Strategy).
For the specific Front-end/UI for SAP S/4HANA 1709, please refer to note 2482461 which is the release information
note for product version SAP FIORI FOR SAP S/4HANA 1709. Support Package Stack 05 of SAP S/4HANA 1709 in the
back-end requires Support Package Stack 01 or higher of SAP FIORI FOR SAP S/4HANA 1709 on the front-end (and
vice versa).
Installation Requirements
For the system installation, please refer to the installation guide.
You need at least Software Provisioning Manager (SWPM) Support Package 24 for the installation. Please make sure
that you always use the latest patch level of SWPM available at support.sap.com/software/sltoolset.html.
Please refer to SAP note 306695 ('Field EMDST13 is unknown' after installing IS-U/CCS) after installation.
Upgrade Requirements
You can upgrade to SAP S/4HANA 1709 from following source releases:
SAP S/4HANA, on-premise edition 1511 (Please be aware that your software level is not higher than Support
Package Stack 10.)
SAP S/4HANA 1610 (Please be aware that your software level is not higher than Support Package Stack 11.)
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that
all corrections already applied on the source system are also part of the target release Support Package stack so as
not to downgrade the system. If a higher Support Package is already implemented on your source system, you need
to upgrade to a higher Support Package of the target release.
For the system upgrade, please refer to the upgrade guide.
You need at least Software Update Manager (SUM) 2.0 Support Package 03 for the upgrade. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
 If the upgrade aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the upgrade aborts with error DT201 during activation of technical settings, please see note 2683419.
If you use Advanced Compliance Reporting (ACR), please see note 2964762.
Conversion Requirements
Please note that a system conversion to SAP S/4HANA 1809 is no longer possible or supported
for newly starting system conversion projects – independently of the Enhancement Package or SP level of the
SAP ERP source system.
for any system which is below the following SAP ERP SP levels and have to go to S/4HANA 1809, open a message
on CA-TRS-PRCK
for any system which is on the following SAP ERP SP levels or higher: 600 SP30, 602 SP20, 603 SP19, 604 SP20,
605 SP17, 606 SP20, 616 SP12, 617 SP15, 618 SP09.
You can convert to the successor product versions of SAP S/4HANA.
Support Package Update (via Software Update Manager (SUM) or SPAM)
Depending on the SAP_BASIS 752 SP-level in the start system, please ensure that you have applied the following notes
or the respective SAP_BASIS 752 Support Package containing the corrections before you start the Support Package
Stack Update to SAP S/4HANA 1709 Support Package Stack 03:
2513147 - Table logging can be activated even though table is too wide (required for start systems on SAP_BASIS
752 SP00, for further background information please check SAP note 2683419)
2563164 - DD: Activation of DDL view fails without error message (required for start systems on SAP_BASIS 752
SP00 and SP01)
2548843 - DD: data element changes from DEC to CURR, error for dependent VIEWs (required for start systems
on SAP_BASIS 752 SP00, SP01 and SP02)
2603860 - Data Dictionary: Wrong calculation of RC in mass activation (required for start systems on SAP_BASIS
752 SP00, SP01 and SP02)
In case you are using SPAM for the SP-update from FPS02 to SPS03, the SP import might abort during execution of
After-Import methods with errors for After-import method “FDT_AFTER_IMPORT”. Similar aborts can also occur
when importing multiple FP-/SP-Stacks in a single queue (errors might be listed for additional After-import methods
like “SACMDT_AFTER_IMP_DCL”). In both cases, please restart the Feature / Support Package Stack import in SPAM
again.
In case of runtime errors DBSQL_SQL_DEADLOCK_DETECTED, please see note 2705194.

Notes to be applied on top of Support Package Stack 12

SUPPORT PACKAGE STACK 11 (10/2022)
General / Important Considerations
The minimum required revision of SAP HANA 2.0 is SPS 02 Revision 24. SAP generally recommends customers to
implement the highest SAP HANA 2.0 revision available. Please take in account that the minimum required revision is
out of maintenance. For more details, please refer to note 2378962 (SAP HANA 2.0 Revision and Maintenance
Strategy).
For the specific Front-end/UI for SAP S/4HANA 1709, please refer to note 2482461 which is the release information
note for product version SAP FIORI FOR SAP S/4HANA 1709. Support Package Stack 05 of SAP S/4HANA 1709 in the
back-end requires Support Package Stack 01 or higher of SAP FIORI FOR SAP S/4HANA 1709 on the front-end (and
vice versa).
Installation Requirements
For the system installation, please refer to the installation guide.
You need at least Software Provisioning Manager (SWPM) Support Package 24 for the installation. Please make sure
that you always use the latest patch level of SWPM available at support.sap.com/software/sltoolset.html.
Please refer to SAP note 306695 ('Field EMDST13 is unknown' after installing IS-U/CCS) after installation.
Upgrade Requirements
You can upgrade to SAP S/4HANA 1709 from following source releases:
SAP S/4HANA, on-premise edition 1511 (Please be aware that your software level is not higher than Support
Package Stack 10.)
SAP S/4HANA 1610 (Please be aware that your software level is not higher than Support Package Stack 11.)
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that
all corrections already applied on the source system are also part of the target release Support Package stack so as
not to downgrade the system. If a higher Support Package is already implemented on your source system, you need
to upgrade to a higher Support Package of the target release.
For the system upgrade, please refer to the upgrade guide.
You need at least Software Update Manager (SUM) 2.0 Support Package 03 for the upgrade. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
If the upgrade aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the upgrade aborts with error DT201 during activation of technical settings, please see note 2683419.
If you use Advanced Compliance Reporting (ACR), please see note 2964762.
Conversion Requirements
Please note that a system conversion to SAP S/4HANA 1809 is no longer possible or supported
for newly starting system conversion projects – independently of the Enhancement Package or SP level of the
SAP ERP source system.
for any system which is below the following SAP ERP SP levels and have to go to S/4HANA 1809, open a message
on CA-TRS-PRCK
for any system which is on the following SAP ERP SP levels or higher: 600 SP30, 602 SP20, 603 SP19, 604 SP20,
605 SP17, 606 SP20, 616 SP12, 617 SP15, 618 SP09.
You can convert to the successor product versions of SAP S/4HANA.
Support Package Update (via Software Update Manager (SUM) or SPAM)
Depending on the SAP_BASIS 752 SP-level in the start system, please ensure that you have applied the following notes
or the respective SAP_BASIS 752 Support Package containing the corrections before you start the Support Package
Stack Update to SAP S/4HANA 1709 Support Package Stack 03:
2513147 - Table logging can be activated even though table is too wide (required for start systems on SAP_BASIS
752 SP00, for further background information please check SAP note 2683419)
2563164 - DD: Activation of DDL view fails without error message (required for start systems on SAP_BASIS 752
SP00 and SP01)
2548843 - DD: data element changes from DEC to CURR, error for dependent VIEWs (required for start systems
on SAP_BASIS 752 SP00, SP01 and SP02)
2603860 - Data Dictionary: Wrong calculation of RC in mass activation (required for start systems on SAP_BASIS
752 SP00, SP01 and SP02)
In case you are using SPAM for the SP-update from FPS02 to SPS03, the SP import might abort during execution of
After-Import methods with errors for After-import method “FDT_AFTER_IMPORT”. Similar aborts can also occur
when importing multiple FP-/SP-Stacks in a single queue (errors might be listed for additional After-import methods
like “SACMDT_AFTER_IMP_DCL”). In both cases, please restart the Feature / Support Package Stack import in SPAM
again.
In case of runtime errors DBSQL_SQL_DEADLOCK_DETECTED, please see note 2705194.

Notes to be applied on top of Support Package Stack 11

SUPPORT PACKAGE STACK 10 (04/2022)
General / Important Considerations
The minimum required revision of SAP HANA 2.0 is SPS 02 Revision 24. SAP generally recommends customers to
implement the highest SAP HANA 2.0 revision available. Please take in account that the minimum required revision is
out of maintenance. For more details, please refer to note 2378962 (SAP HANA 2.0 Revision and Maintenance
Strategy).
For the specific Front-end/UI for SAP S/4HANA 1709, please refer to note 2482461 which is the release information
note for product version SAP FIORI FOR SAP S/4HANA 1709. Support Package Stack 05 of SAP S/4HANA 1709 in the
back-end requires Support Package Stack 01 or higher of SAP FIORI FOR SAP S/4HANA 1709 on the front-end (and
vice versa).
Installation Requirements
For the system installation, please refer to the installation guide.
You need at least Software Provisioning Manager (SWPM) Support Package 24 for the installation. Please make sure
that you always use the latest patch level of SWPM available at support.sap.com/software/sltoolset.html.
Please refer to SAP note 306695 ('Field EMDST13 is unknown' after installing IS-U/CCS) after installation.
Upgrade Requirements
You can upgrade to SAP S/4HANA 1709 from following source releases:
SAP S/4HANA, on-premise edition 1511 (Please be aware that your software level is not higher than Support
Package Stack 10.)
SAP S/4HANA 1610 (Please be aware that your software level is not higher than Support Package Stack 11.)
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that
all corrections already applied on the source system are also part of the target release Support Package stack so as
not to downgrade the system. If a higher Support Package is already implemented on your source system, you need
to upgrade to a higher Support Package of the target release.
For the system upgrade, please refer to the upgrade guide.
You need at least Software Update Manager (SUM) 2.0 Support Package 03 for the upgrade. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
If the upgrade aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the upgrade aborts with error DT201 during activation of technical settings, please see note 2683419.
If you use Advanced Compliance Reporting (ACR), please see note 2964762.
Conversion Requirements
Please note that a system conversion to SAP S/4HANA 1809 is no longer possible or supported
 for newly starting system conversion projects – independently of the Enhancement Package or SP level of the
SAP ERP source system.
for any system which is below the following SAP ERP SP levels and have to go to S/4HANA 1809, open a message
on CA-TRS-PRCK
for any system which is on the following SAP ERP SP levels or higher: 600 SP30, 602 SP20, 603 SP19, 604 SP20,
605 SP17, 606 SP20, 616 SP12, 617 SP15, 618 SP09.
You can convert to the successor product versions of SAP S/4HANA.
Support Package Update (via Software Update Manager (SUM) or SPAM)
Depending on the SAP_BASIS 752 SP-level in the start system, please ensure that you have applied the following notes
or the respective SAP_BASIS 752 Support Package containing the corrections before you start the Support Package
Stack Update to SAP S/4HANA 1709 Support Package Stack 03:
2513147 - Table logging can be activated even though table is too wide (required for start systems on SAP_BASIS
752 SP00, for further background information please check SAP note 2683419)
2563164 - DD: Activation of DDL view fails without error message (required for start systems on SAP_BASIS 752
SP00 and SP01)
2548843 - DD: data element changes from DEC to CURR, error for dependent VIEWs (required for start systems
on SAP_BASIS 752 SP00, SP01 and SP02)
2603860 - Data Dictionary: Wrong calculation of RC in mass activation (required for start systems on SAP_BASIS
752 SP00, SP01 and SP02)
In case you are using SPAM for the SP-update from FPS02 to SPS03, the SP import might abort during execution of
After-Import methods with errors for After-import method “FDT_AFTER_IMPORT”. Similar aborts can also occur
when importing multiple FP-/SP-Stacks in a single queue (errors might be listed for additional After-import methods
like “SACMDT_AFTER_IMP_DCL”). In both cases, please restart the Feature / Support Package Stack import in SPAM
again.
In case of runtime errors DBSQL_SQL_DEADLOCK_DETECTED, please see note 2705194.

Notes to be applied on top of Support Package Stack 10

SAP Not Description Software Compon Manual Activities Added on

e ent required

SUPPORT PACKAGE STACK 09 (10/2021)

General / Important Considerations
The minimum required revision of SAP HANA 2.0 is SPS 02 Revision 24. SAP generally recommends customers to
implement the highest SAP HANA 2.0 revision available. Please take in account that the minimum required revision is
out of maintenance. For more details, please refer to note 2378962 (SAP HANA 2.0 Revision and Maintenance
Strategy).
For the specific Front-end/UI for SAP S/4HANA 1709, please refer to note 2482461 which is the release information
note for product version SAP FIORI FOR SAP S/4HANA 1709. Support Package Stack 05 of SAP S/4HANA 1709 in the
back-end requires Support Package Stack 01 or higher of SAP FIORI FOR SAP S/4HANA 1709 on the front-end (and
vice versa).
Installation Requirements
For the system installation, please refer to the installation guide.
You need at least Software Provisioning Manager (SWPM) Support Package 24 for the installation. Please make sure
that you always use the latest patch level of SWPM available at support.sap.com/software/sltoolset.html.
Please refer to SAP note 306695 ('Field EMDST13 is unknown' after installing IS-U/CCS) after installation.
Upgrade Requirements
You can upgrade to SAP S/4HANA 1709 from following source releases:
SAP S/4HANA, on-premise edition 1511 (Please be aware that your software level is not higher than Support
Package Stack 10.)
SAP S/4HANA 1610 (Please be aware that your software level is not higher than Support Package Stack 11.)
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that
all corrections already applied on the source system are also part of the target release Support Package stack so as
not to downgrade the system. If a higher Support Package is already implemented on your source system, you need
to upgrade to a higher Support Package of the target release.
For the system upgrade, please refer to the upgrade guide.
You need at least Software Update Manager (SUM) 2.0 Support Package 03 for the upgrade. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
If the upgrade aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the upgrade aborts with error DT201 during activation of technical settings, please see note 2683419.
If you use Advanced Compliance Reporting (ACR), please see note 2964762.
Conversion Requirements
 Please note that a system conversion to SAP S/4HANA 1809 is no longer possible or supported
for newly starting system conversion projects – independently of the Enhancement Package or SP level of the
SAP ERP source system.
for any system which is below the following SAP ERP SP levels and have to go to S/4HANA 1809, open a message
on CA-TRS-PRCK
for any system which is on the following SAP ERP SP levels or higher: 600 SP30, 602 SP20, 603 SP19, 604 SP20,
605 SP17, 606 SP20, 616 SP12, 617 SP15, 618 SP09.
You can convert to the successor product versions of SAP S/4HANA.
Support Package Update (via Software Update Manager (SUM) or SPAM)
Depending on the SAP_BASIS 752 SP-level in the start system, please ensure that you have applied the following notes
or the respective SAP_BASIS 752 Support Package containing the corrections before you start the Support Package
Stack Update to SAP S/4HANA 1709 Support Package Stack 03:
2513147 - Table logging can be activated even though table is too wide (required for start systems on SAP_BASIS
752 SP00, for further background information please check SAP note 2683419)
2563164 - DD: Activation of DDL view fails without error message (required for start systems on SAP_BASIS 752
SP00 and SP01)
2548843 - DD: data element changes from DEC to CURR, error for dependent VIEWs (required for start systems
on SAP_BASIS 752 SP00, SP01 and SP02)
2603860 - Data Dictionary: Wrong calculation of RC in mass activation (required for start systems on SAP_BASIS
752 SP00, SP01 and SP02)
In case you are using SPAM for the SP-update from FPS02 to SPS03, the SP import might abort during execution of
After-Import methods with errors for After-import method “FDT_AFTER_IMPORT”. Similar aborts can also occur
when importing multiple FP-/SP-Stacks in a single queue (errors might be listed for additional After-import methods
like “SACMDT_AFTER_IMP_DCL”). In both cases, please restart the Feature / Support Package Stack import in SPAM
again.
In case of runtime errors DBSQL_SQL_DEADLOCK_DETECTED, please see note 2705194.

Notes to be applied on top of Support Package Stack 09

SAP Not Description Software Compon Manual Activities Added on

e ent required

SUPPORT PACKAGE STACK 08 (04/2021)

General / Important Considerations
The minimum required revision of SAP HANA 2.0 is SPS 02 Revision 24. SAP generally recommends customers to
implement the highest SAP HANA 2.0 revision available. Please take in account that the minimum required revision is
out of maintenance. For more details, please refer to note 2378962 (SAP HANA 2.0 Revision and Maintenance
Strategy).
For the specific Front-end/UI for SAP S/4HANA 1709, please refer to note 2482461 which is the release information
note for product version SAP FIORI FOR SAP S/4HANA 1709. Support Package Stack 05 of SAP S/4HANA 1709 in the
back-end requires Support Package Stack 01 or higher of SAP FIORI FOR SAP S/4HANA 1709 on the front-end (and
vice versa).
Installation Requirements
For the system installation, please refer to the installation guide.
You need at least Software Provisioning Manager (SWPM) Support Package 24 for the installation. Please make sure
that you always use the latest patch level of SWPM available at support.sap.com/software/sltoolset.html.
Please refer to SAP note 306695 ('Field EMDST13 is unknown' after installing IS-U/CCS) after installation.
Upgrade Requirements
You can upgrade to SAP S/4HANA 1709 from following source releases:
SAP S/4HANA, on-premise edition 1511 (Please be aware that your software level is not higher than Support
Package Stack 10.)
SAP S/4HANA 1610 (Please be aware that your software level is not higher than Support Package Stack 10.)
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that
all corrections already applied on the source system are also part of the target release Support Package stack so as
not to downgrade the system. If a higher Support Package is already implemented on your source system, you need
to upgrade to a higher Support Package of the target release.
For the system upgrade, please refer to the upgrade guide.
You need at least Software Update Manager (SUM) 2.0 Support Package 03 for the upgrade. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
If the upgrade aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the upgrade aborts with error DT201 during activation of technical settings, please see note 2683419.
If you use Advanced Compliance Reporting (ACR), please see note 2964762.
Conversion Requirements
Please note that a system conversion to SAP S/4HANA 1809 is no longer possible or supported
for newly starting system conversion projects – independently of the Enhancement Package or SP level of the
SAP ERP source system.
for any system which is below the following SAP ERP SP levels and have to go to S/4HANA 1809, open a message
on CA-TRS-PRCK
for any system which is on the following SAP ERP SP levels or higher: 600 SP30, 602 SP20, 603 SP19, 604 SP20,
605 SP17, 606 SP20, 616 SP12, 617 SP15, 618 SP09.
You can convert to the successor product versions of SAP S/4HANA.

Support Package Update (via Software Update Manager (SUM) or SPAM)

Depending on the SAP_BASIS 752 SP-level in the start system, please ensure that you have applied the following notes
or the respective SAP_BASIS 752 Support Package containing the corrections before you start the Support Package
Stack Update to SAP S/4HANA 1709 Support Package Stack 03:
2513147 - Table logging can be activated even though table is too wide (required for start systems on SAP_BASIS
752 SP00, for further background information please check SAP note 2683419)
2563164 - DD: Activation of DDL view fails without error message (required for start systems on SAP_BASIS 752
SP00 and SP01)
2548843 - DD: data element changes from DEC to CURR, error for dependent VIEWs (required for start systems
on SAP_BASIS 752 SP00, SP01 and SP02)
2603860 - Data Dictionary: Wrong calculation of RC in mass activation (required for start systems on SAP_BASIS
752 SP00, SP01 and SP02)
In case you are using SPAM for the SP-update from FPS02 to SPS03, the SP import might abort during execution of
After-Import methods with errors for After-import method “FDT_AFTER_IMPORT”. Similar aborts can also occur
when importing multiple FP-/SP-Stacks in a single queue (errors might be listed for additional After-import methods
like “SACMDT_AFTER_IMP_DCL”). In both cases, please restart the Feature / Support Package Stack import in SPAM
again.
In case of runtime errors DBSQL_SQL_DEADLOCK_DETECTED, please see note 2705194.

Notes to be applied on top of Support Package Stack 08

SAP Not Description Software Compon Manual Activities Added on

e ent required

SUPPORT PACKAGE STACK 07 (10/2020)

General / Important Considerations
The minimum required revision of SAP HANA 2.0 is SPS 02 Revision 24. SAP generally recommends customers to
implement the highest SAP HANA 2.0 revision available. Please take in account that the minimum required revision is
out of maintenance. For more details, please refer to note 2378962 (SAP HANA 2.0 Revision and Maintenance
Strategy).
For the specific Front-end/UI for SAP S/4HANA 1709, please refer to note 2482461 which is the release information
note for product version SAP FIORI FOR SAP S/4HANA 1709. Support Package Stack 05 of SAP S/4HANA 1709 in the
back-end requires Support Package Stack 01 or higher of SAP FIORI FOR SAP S/4HANA 1709 on the front-end (and
vice versa).
Installation Requirements
For the system installation, please refer to the installation guide.
You need at least Software Provisioning Manager (SWPM) Support Package 24 for the installation. Please make sure
that you always use the latest patch level of SWPM available at support.sap.com/software/sltoolset.html.
Please refer to SAP note 306695 ('Field EMDST13 is unknown' after installing IS-U/CCS) after installation.
Upgrade Requirements
You can upgrade to SAP S/4HANA 1709 from following source releases:
SAP S/4HANA, on-premise edition 1511 (Please be aware that your software level is not higher than Support
Package Stack 10.)
SAP S/4HANA 1610 (Please be aware that your software level is not higher than Support Package Stack 08.)
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that
all corrections already applied on the source system are also part of the target release Support Package stack so as
not to downgrade the system. If a higher Support Package is already implemented on your source system, you need
to upgrade to a higher Support Package of the target release.
For the system upgrade, please refer to the upgrade guide.
You need at least Software Update Manager (SUM) 2.0 Support Package 03 for the upgrade. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
If the upgrade aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the upgrade aborts with error DT201 during activation of technical settings, please see note 2683419.
 If you use Advanced Compliance Reporting (ACR), please see note 2964762.
Conversion Requirements
For the system conversion, please refer to the conversion guide and SAP notes 2495992 (Preparation), 2426277 (SUM)
and 2495932 (Follow-on).
You need at least Software Update Manager (SUM) Support Package 03 for the conversion. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
For system conversions from an existing source release, please be aware that your software level is not higher than
SAP ERP 6.0 SP Stack 32
SAP enhancement package 2 for SAP ERP 6.0 SP Stack 22
SAP enhancement package 3 for SAP ERP 6.0 SP Stack 21
SAP enhancement package 4 for SAP ERP 6.0 SP Stack 22
SAP enhancement package 5 for SAP ERP 6.0 SP Stack 19
SAP enhancement package 6 for SAP ERP 6.0 SP Stack 26
SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA SP Stack 14
SAP enhancement package 7 for SAP ERP 6.0 SP Stack 21
SAP enhancement package 8 for SAP ERP 6.0 SP Stack 15
SAP Simple Finance add-on 1.0 for SAP Business Suite powered by SAP HANA SP Stack 18
SAP Simple Finance, on-premise edition 1503 SP Stack 14
SAP S/4HANA Finance 1605 SP Stack 16
The reason is to avoid a violation of the Support Package stack equivalences between the start and target release. Only if there
is an equivalence between the start and target release it can be ensured that all corrections already applied on the source
system are also part of the target release Support Package stack so as not to downgrade the system. If a higher Support
Package stack is already implemented on your source system, you need to upgrade to a higher Support Package stack of the
target release which is maybe not yet available.
The same holds true for the underlying SAP NETWEAVER or ABAP PLATFORM stack. You can find the corresponding SP
equivalence level in SAP note 2532249.
Please note that there are single software components included in the SAP ERP stack which technically can be updated to a
higher Support Package level within the given Support Package stack definition (Example: IS-H). If you decide to implement
higher Support Packages for these software component versions on your source system shortly before a planned upgrade, you
would run into situation which would block your upgrade since the upgrade tools would find that the Support Package stack
equivalences of your source systems are violated. A similar situation could occur for Add-on software component versions
which are installed on top of the SAP ERP system.
Please see SAP notes 2457423, 832594 and https://support.sap.com/en/my-support/software-downloads/support-package-
stacks/support-package-stack-strategy.html for further information.
Support Package Update (via Software Update Manager (SUM) or SPAM)
Depending on the SAP_BASIS 752 SP-level in the start system, please ensure that you have applied the following notes
or the respective SAP_BASIS 752 Support Package containing the corrections before you start the Support Package
Stack Update to SAP S/4HANA 1709 Support Package Stack 03:
2513147 - Table logging can be activated even though table is too wide (required for start systems on SAP_BASIS
752 SP00, for further background information please check SAP note 2683419)
2563164 - DD: Activation of DDL view fails without error message (required for start systems on SAP_BASIS 752
SP00 and SP01)
2548843 - DD: data element changes from DEC to CURR, error for dependent VIEWs (required for start systems
on SAP_BASIS 752 SP00, SP01 and SP02)
2603860 - Data Dictionary: Wrong calculation of RC in mass activation (required for start systems on SAP_BASIS
752 SP00, SP01 and SP02)
In case you are using SPAM for the SP-update from FPS02 to SPS03, the SP import might abort during execution of
After-Import methods with errors for After-import method “FDT_AFTER_IMPORT”. Similar aborts can also occur
when importing multiple FP-/SP-Stacks in a single queue (errors might be listed for additional After-import methods
like “SACMDT_AFTER_IMP_DCL”). In both cases, please restart the Feature / Support Package Stack import in SPAM
again.
In case of runtime errors DBSQL_SQL_DEADLOCK_DETECTED, please see note 2705194.

Notes to be applied on top of Support Package Stack 07

SAP Not Description Software Compon Manual Activities Added on

e ent required

SUPPORT PACKAGE STACK 06 (04/2020)

General / Important Considerations
The minimum required revision of SAP HANA 2.0 is SPS 02 Revision 24. SAP generally recommends customers to
implement the highest SAP HANA 2.0 revision available.
 For the specific Front-end/UI for SAP S/4HANA 1709, please refer to note 2482461 which is the release information
note for product version SAP FIORI FOR SAP S/4HANA 1709. Support Package Stack 05 of SAP S/4HANA 1709 in the
back-end requires Support Package Stack 01 or higher of SAP FIORI FOR SAP S/4HANA 1709 on the front-end (and
vice versa).
Installation Requirements
For the system installation, please refer to the installation guide.
You need at least Software Provisioning Manager (SWPM) Support Package 24 for the installation. Please make sure
that you always use the latest patch level of SWPM available at support.sap.com/software/sltoolset.html.
Please refer to SAP note 306695 ('Field EMDST13 is unknown' after installing IS-U/CCS) after installation.
Upgrade Requirements
You can upgrade to SAP S/4HANA 1709 from following source releases:
SAP S/4HANA, on-premise edition 1511 (Please be aware that your software level is not higher than Support
Package Stack 10.)
SAP S/4HANA 1610 (Please be aware that your software level is not higher than Support Package Stack 08.)
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that
all corrections already applied on the source system are also part of the target release Support Package stack so as
not to downgrade the system. If a higher Support Package is already implemented on your source system, you need
to upgrade to a higher Support Package of the target release.
For the system upgrade, please refer to the upgrade guide.
You need at least Software Update Manager (SUM) 2.0 Support Package 03 for the upgrade. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
If the upgrade aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the upgrade aborts with error DT201 during activation of technical settings, please see note 2683419.
If you use Advanced Compliance Reporting (ACR), please see note 2964762.
Conversion Requirements
For the system conversion, please refer to the conversion guide and SAP notes 2495992 (Preparation), 2426277 (SUM)
and 2495932 (Follow-on).
You need at least Software Update Manager (SUM) Support Package 03 for the conversion. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
For system conversions from an existing source release, please be aware that your software level is not higher than
SAP ERP 6.0 SP Stack 32
SAP enhancement package 2 for SAP ERP 6.0 SP Stack 22
SAP enhancement package 3 for SAP ERP 6.0 SP Stack 21
SAP enhancement package 4 for SAP ERP 6.0 SP Stack 22
SAP enhancement package 5 for SAP ERP 6.0 SP Stack 19
SAP enhancement package 6 for SAP ERP 6.0 SP Stack 25
SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA SP Stack 14
SAP enhancement package 7 for SAP ERP 6.0 SP Stack 20
SAP enhancement package 8 for SAP ERP 6.0 SP Stack 14
SAP Simple Finance add-on 1.0 for SAP Business Suite powered by SAP HANA SP Stack 17
SAP Simple Finance, on-premise edition 1503 SP Stack 13
SAP S/4HANA Finance 1605 SP Stack 15
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that all
corrections already applied on the source system are also part of the target release Support Package stack so as not to
downgrade the system. If a higher Support Package is already implemented on your source system, you need to upgrade to a
higher Support Package of the target release.
If the conversion aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the conversion aborts with error DT201 during activation of technical settings, please see note 2683419.
Support Package Update (via Software Update Manager (SUM) or SPAM)
Depending on the SAP_BASIS 752 SP-level in the start system, please ensure that you have applied the following notes
or the respective SAP_BASIS 752 Support Package containing the corrections before you start the Support Package
Stack Update to SAP S/4HANA 1709 Support Package Stack 03:
2513147 - Table logging can be activated even though table is too wide (required for start systems on SAP_BASIS
752 SP00, for further background information please check SAP note 2683419)
2563164 - DD: Activation of DDL view fails without error message (required for start systems on SAP_BASIS 752
SP00 and SP01)
2548843 - DD: data element changes from DEC to CURR, error for dependent VIEWs (required for start systems
on SAP_BASIS 752 SP00, SP01 and SP02)
2603860 - Data Dictionary: Wrong calculation of RC in mass activation (required for start systems on SAP_BASIS
752 SP00, SP01 and SP02)
In case you are using SPAM for the SP-update from FPS02 to SPS03, the SP import might abort during execution of
After-Import methods with errors for After-import method “FDT_AFTER_IMPORT”. Similar aborts can also occur
when importing multiple FP-/SP-Stacks in a single queue (errors might be listed for additional After-import methods
 like “SACMDT_AFTER_IMP_DCL”). In both cases, please restart the Feature / Support Package Stack import in SPAM
again.
In case of runtime errors DBSQL_SQL_DEADLOCK_DETECTED, please see note 2705194.

Notes to be applied on top of Support Package Stack 06

SAP Not Description Software Compon Manual Activities Added on

e ent required

2880761 Syntax error "VBHDR_G does not exist" in progra ST-A/PI No 2020-04-15
m /SSA/EBT

2880801 Syntax error "VBHDR_G does not exist" in progra ST-A/PI No 2020-04-15
m /SSA/EBP

2886195 Syntax error "VBHDR_G does not exist" in progra ST-A/PI No 2020-04-15
m /SDF/SAPLEWA

SUPPORT PACKAGE STACK 05 (10/2019)

General / Important Considerations
The minimum required revision of SAP HANA 2.0 is SPS 02 Revision 24. SAP generally recommends customers to
implement the highest SAP HANA 2.0 revision available.
For the specific Front-end/UI for SAP S/4HANA 1709, please refer to note 2482461 which is the release information
note for product version SAP FIORI FOR SAP S/4HANA 1709. Support Package Stack 05 of SAP S/4HANA 1709 in the
back-end requires Support Package Stack 01 or higher of SAP FIORI FOR SAP S/4HANA 1709 on the front-end (and
vice versa).
Installation Requirements
For the system installation, please refer to the installation guide.
You need at least Software Provisioning Manager (SWPM) Support Package 24 for the installation. Please make sure
that you always use the latest patch level of SWPM available at support.sap.com/software/sltoolset.html.
Please refer to SAP note 306695 ('Field EMDST13 is unknown' after installing IS-U/CCS) after installation.
Upgrade Requirements
You can upgrade to SAP S/4HANA 1709 from following source releases:
SAP S/4HANA, on-premise edition 1511 (Please be aware that your software level is not higher than Support
Package Stack 09.)
SAP S/4HANA 1610 (Please be aware that your software level is not higher than Support Package Stack 07.)
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that
all corrections already applied on the source system are also part of the target release Support Package stack so as
not to downgrade the system. If a higher Support Package is already implemented on your source system, you need
to upgrade to a higher Support Package of the target release.
For the system upgrade, please refer to the upgrade guide.
You need at least Software Update Manager (SUM) 2.0 Support Package 03 for the upgrade. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
If the upgrade aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the upgrade aborts with error DT201 during activation of technical settings, please see note 2683419.
Conversion Requirements
For the system conversion, please refer to the conversion guide and SAP notes 2495992 (Preparation), 2426277 (SUM)
and 2495932 (Follow-on).
You need at least Software Update Manager (SUM) Support Package 03 for the conversion. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
For system conversions from an existing source release, please be aware that your software level is not higher than
SAP ERP 6.0 SP Stack 31
SAP enhancement package 2 for SAP ERP 6.0 SP Stack 21
SAP enhancement package 3 for SAP ERP 6.0 SP Stack 20
SAP enhancement package 4 for SAP ERP 6.0 SP Stack 21
SAP enhancement package 5 for SAP ERP 6.0 SP Stack 18
SAP enhancement package 6 for SAP ERP 6.0 SP Stack 24
SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA SP Stack 13
SAP enhancement package 7 for SAP ERP 6.0 SP Stack 19
SAP enhancement package 8 for SAP ERP 6.0 SP Stack 13
SAP Simple Finance add-on 1.0 for SAP Business Suite powered by SAP HANA SP Stack 16
SAP Simple Finance, on-premise edition 1503 SP Stack 12
SAP S/4HANA Finance 1605 SP Stack 14
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that all
corrections already applied on the source system are also part of the target release Support Package stack so as not to
downgrade the system. If a higher Support Package is already implemented on your source system, you need to upgrade to a
higher Support Package of the target release.
If the conversion aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the conversion aborts with error DT201 during activation of technical settings, please see note 2683419.
Support Package Update (via Software Update Manager (SUM) or SPAM)
Depending on the SAP_BASIS 752 SP-level in the start system, please ensure that you have applied the following notes
or the respective SAP_BASIS 752 Support Package containing the corrections before you start the Support Package
Stack Update to SAP S/4HANA 1709 Support Package Stack 03:
2513147 - Table logging can be activated even though table is too wide (required for start systems on SAP_BASIS
752 SP00, for further background information please check SAP note 2683419)
2563164 - DD: Activation of DDL view fails without error message (required for start systems on SAP_BASIS 752
SP00 and SP01)
2548843 - DD: data element changes from DEC to CURR, error for dependent VIEWs (required for start systems
on SAP_BASIS 752 SP00, SP01 and SP02)
2603860 - Data Dictionary: Wrong calculation of RC in mass activation (required for start systems on SAP_BASIS
752 SP00, SP01 and SP02)
In case you are using SPAM for the SP-update from FPS02 to SPS03, the SP import might abort during execution of
After-Import methods with errors for After-import method “FDT_AFTER_IMPORT”. Similar aborts can also occur
when importing multiple FP-/SP-Stacks in a single queue (errors might be listed for additional After-import methods
like “SACMDT_AFTER_IMP_DCL”). In both cases, please restart the Feature / Support Package Stack import in SPAM
again.
In case of runtime errors DBSQL_SQL_DEADLOCK_DETECTED, please see note 2705194.

Notes to be applied on top of Support Package Stack 05

SAP Not Description Software Com Manual Activities re Added on

e ponent quired

Important changes made after release of Support Package Stack 05

2020-01-31: United Kingdom leaving the EU:
• For information about the United Kingdom leaving the EU with the Withdrawal Bill and the transition period, please see
SAP note 2885225.
• For information about how a “hard Brexit” (= a no-deal scenario) would impact your SAP S/4HANA system, please see SAP
note 2749671.

SUPPORT PACKAGE STACK 04 (04/2019)

General / Important Considerations
The minimum required revision of SAP HANA 2.0 is SPS 01 Revision 12.04 or SPS 02 Revision 23. SAP generally
recommends customers to implement the highest SAP HANA 2.0 revision available.
For the specific Front-end/UI for SAP S/4HANA 1709, please refer to note 2482461 which is the release information
note for product version SAP FIORI FOR SAP S/4HANA 1709. Support Package Stack 04 of SAP S/4HANA 1709 in the
back-end requires Support Package Stack 01 or higher of SAP FIORI FOR SAP S/4HANA 1709 on the front-end (and
vice versa).
Installation Requirements
For the system installation, please refer to the installation guide.
You need at least Software Provisioning Manager (SWPM) Support Package 24 for the installation. Please make sure
that you always use the latest patch level of SWPM available at support.sap.com/software/sltoolset.html.
Please refer to SAP note 306695 ('Field EMDST13 is unknown' after installing IS-U/CCS) after installation.
Upgrade Requirements
You can upgrade to SAP S/4HANA 1709 from following source releases:
SAP S/4HANA, on-premise edition 1511 (Please be aware that your software level is not higher than Support
Package Stack 08.)
SAP S/4HANA 1610 (Please be aware that your software level is not higher than Support Package Stack 06.)
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that
all corrections already applied on the source system are also part of the target release Support Package stack so as
not to downgrade the system. If a higher Support Package is already implemented on your source system, you need
to upgrade to a higher Support Package of the target release.
 For the system upgrade, please refer to the upgrade guide.
You need at least Software Update Manager (SUM) 2.0 Support Package 03 for the upgrade. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
If the upgrade aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the upgrade aborts with error DT201 during activation of technical settings, please see note 2683419.
Conversion Requirements
For the system conversion, please refer to the conversion guide and SAP notes 2495992 (Preparation), 2426277 (SUM)
and 2495932 (Follow-on).
You need at least Software Update Manager (SUM) Support Package 03 for the conversion. Please make sure that you
always use the latest patch level of SUM available at support.sap.com/software/sltoolset.html.
For system conversions from an existing source release, please be aware that your software level is not higher than
SAP ERP 6.0 SP Stack 31
SAP enhancement package 2 for SAP ERP 6.0 SP Stack 21
SAP enhancement package 3 for SAP ERP 6.0 SP Stack 20
SAP enhancement package 4 for SAP ERP 6.0 SP Stack 21
SAP enhancement package 5 for SAP ERP 6.0 SP Stack 18
SAP enhancement package 6 for SAP ERP 6.0 SP Stack 23
SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA SP Stack 13
SAP enhancement package 7 for SAP ERP 6.0 SP Stack 18
SAP enhancement package 8 for SAP ERP 6.0 SP Stack 12
SAP Simple Finance add-on 1.0 for SAP Business Suite powered by SAP HANA SP Stack 15
SAP Simple Finance, on-premise edition 1503 SP Stack 11
SAP S/4HANA Finance 1605 SP Stack 13
The reason is to maintain the Support Package equivalences between the start and target release. This ensures that all
corrections already applied on the source system are also part of the target release Support Package stack so as not to
downgrade the system. If a higher Support Package is already implemented on your source system, you need to upgrade
to a higher Support Package of the target release.
If the conversion aborts during MAIN_SHDRUN/ACT_UPG, please restart the phase again.
If the conversion aborts with error DT201 during activation of technical settings, please see note 2683419.
Support Package Update (via Software Update Manager (SUM) or SPAM)
Depending on the SAP_BASIS 752 SP-level in the start system, please ensure that you have applied the following notes
or the respective SAP_BASIS 752 Support Package containing the corrections before you start the Support Package
Stack Update to SAP S/4HANA 1709 Support Package Stack 03:
2513147 - Table logging can be activated even though table is too wide (required for start systems on SAP_BASIS
752 SP00, for further background information please check SAP note 2683419)
2563164 - DD: Activation of DDL view fails without error message (required for start systems on SAP_BASIS 752
SP00 and SP01)
2548843 - DD: data element changes from DEC to CURR, error for dependent VIEWs (required for start systems
on SAP_BASIS 752 SP00, SP01 and SP02)
2603860 - Data Dictionary: Wrong calculation of RC in mass activation (required for start systems on SAP_BASIS
752 SP00, SP01 and SP02)
In case you are using SPAM for the SP-update from FPS02 to SPS03, the SP import might abort during execution of
After-Import methods with errors for After-import method “FDT_AFTER_IMPORT”. Similar aborts can also occur
when importing multiple FP-/SP-Stacks in a single queue (errors might be listed for additional After-import methods
like “SACMDT_AFTER_IMP_DCL”). In both cases, please restart the Feature / Support Package Stack import in SPAM
again.
In case of runtime errors DBSQL_SQL_DEADLOCK_DETECTED, please see note 2705194.
Please apply the following notes if you are using the specified features:

SAP Description Feature Software Manual Activ Added on

Note Compon ities require
ent d

26974 TrexViaDbsl: wrong schema na SAP HANA DB Engines SAP_BASI Yes 2018-10-30
05 me is set to temporary objects i S
n TREX_EXT_AGGREGATE

25900 Simulate Configuration Models Advanced Variant Configuratio S4CORE Yes 2018-10-30
64 : Property name harmonization n
, CDS optimization
 ACM: Incorrect item quantity(I Agriculture Contract Managem S4CORE No 2018-10-30
TEM_QTY) displayed in applic ent
26982
ation work center in split to con
66
tract scenario when PO UOM a
nd LDC UOM are different

28111 Advanced Variant Configuratio VCH AFL No 2019-07-04

64 n - AFL installation

Notes to be applied on top of Support Package Stack 04

SAP Not Description Software Com Manual Activities re Added on

e ponent quired

2767837 Dump in CL_POWL_UI_HELPER Exception CX_S SAP_BASIS No 2019-05-07

Y_REF_IS_INITIAL

2810687 SAP HANA error 2617 - DAF migration ... failed - d SAP_BASIS No 2019-07-09
uring freestyle search

2767385 Melted variables showing initial values by mistake SAP_BW No 2019-07-12

2809538 OQ: dimF4-M remove assocation SAP_BW No 2019-07-24

Important changes made after release of Support Package Stack 04

SUPPORT PACKAGE STACK 03 (10 /2018)

Please refer to SAP note 2696358 (SAP S/4HANA 1709 Support Package Stack 03: Additional Release Information), which
contains information and references to notes for applying Support Package Stack 03 of product version SAP S/4HANA 1709.
FEATURE PACKAGE STACK 02 (05/2018)
Please refer to SAP note 2621258 (SAP S/4HANA 1709 Feature Package Stack 02: Additional Release Information), which
contains information and references to notes for applying Feature Package Stack 02 of product version SAP S/4HANA 1709.
FEATURE PACKAGE STACK 01 (01/2018)

Please refer to SAP note 2591578 (SAP S/4HANA 1709 Feature Package Stack 01: Additional Release Information), which
contains information and references to notes for applying Feature Package Stack 01 of product version SAP S/4HANA 1709.
FEATURE PACKAGE STACK 00 (09/2017)

Please refer to SAP note 2526924 (SAP S/4HANA 1709 Feature Package Stack 00: Additional Release Information), which
contains information and references to notes for applying Feature Package Stack 00 of product version SAP S/4HANA 1709.

Important changes made after release of SAP S/4HANA 1709

2020-09-30: Inserted hint and reference for ACR (SAP Note 2964762)
2019-04-01: Inserted:United Kingdom leaving the EU: For information on how a “hard Brexit” (= a no-deal scenario) would
impact your SAP S/4HANA system, please see SAP Note 2749671.
2019-01-31: Inserted: SAP Note 2324448: New inventory data model
2018-11-20: Inserted: SAP S/4HANA 1709 is based on SAP NetWeaver 7.52 for SAP S/4HANA 1709
2018-11-19: Inserted SUPPORT PACKAGE STACK 03 (10 /2018) and deleted supported SAP KERNEL 7.73 64-BIT
UNICODE
2018-07-04: Inserted SAP HANA database requirements
2018-05-18: Inserted FEATURE PACKAGE STACK 02 (05/2018)
2018-03-26: Inserted: For supported application server platforms, please refer to the Product Availability Matrix. When
planning your system landscape(s) for SAP S/4HANA 1709, you may want to take the available application server platforms
for the next releases of SAP S/4HANA into account. Please refer to SAP note 2620910 for details.
2018-01-30: Inserted FEATURE PACKAGE STACK 01 (01/2018)
2811164
2809538 OQ: dimF4-M remove assocation SAP_BW No

Software Components
Software Component From To And subsequent

S4CORE 102 102

This document refers to

SAP Component Title
Note/KBA

2967632 FI-LOC-SRF- SAP S/4HANA 1709: Functionality issues in SAP S/4HANA for advanced compliance reporting
RUN

2964762 FI-LOC-SRF- SAP S/4HANA for Advanced Compliance Reporting : Release Information for Electronic
RUN Submission and Date Formatting

2505082 TM-BF Release Information Note (RIN) for TM in SAP S/4HANA 1709

2493348 XX-SER-REL SAP S/4HANA 1709: Release Information Note for Finance

2480067 FI-LOC-SRF- Replacement of Existing Legal Reports with 'SAP Document and Reporting Compliance -
RUN Statutory Reports'

This document is referenced by

SAP Component Title
Note/KBA

3219611 Support of additional genders for SAP Business Partner

2655761 XX-SER-REL SAP S/4HANA - restrictions and recommendations regarding specific revisions of SAP HANA
database for use in SAP S/4HANA

2620910 BC-OP- SAP S/4HANA 1511, 1610, 1709, 1809 and SAP BW/4HANA 1.0, 2.0: Recommended and released
PLNX Application Server Platforms

2579045 XX-SER-REL SAP S/4HANA for Customer Management 1.0 - Release Information Note

2574967 CM-GF SAP S/4HANA 1709 Feature Package Stack 00: Additional Release Information for Legal Content
Management

2524661 XX-SER-REL SAP S/4HANA 1709 - SAP HANA Database Requirements

2482461 XX-SER-REL SAP FIORI FOR SAP S/4HANA 1709: Release Information Note

2532764 LO-RFM SAP S/4HANA 1709 Feature Package Stack 00: Additional Release Information for Retail and Fashion

2495849 CA-MDG SAP S/4HANA Master Data Governance 1709: Release Information Note

2495932 XX-SER-REL SAP S/4HANA 1709 - application specific notes in system conversion / upgrade follow-on phase

2495992 XX-SER-REL SAP S/4HANA 1709 - application specific notes in system conversion / upgrade preparation phase