SAP Fiori Front-end Server upgrade for Standalone system from SAP FES3.

0 to
SAP Fiori Front-end Server 2020 for SAP S/4HANA
In my all previous S/4HANA upgrade post shared multiple scenarios with Fiori dependencies with
Standalone and Embedded system, it totally depends on the Business usage how you want to
system landscape to be configured.
Sharing recent worked dependencies for Fiori in 4-different customer scenario, during planning of
S4HANA upgrade to 2020.
1) Source system: S/4HANA 1610, with Standalone Fiori FES3.0 in running ASE DB.
Target system: S/4HANA 2020, upgrade Standalone Fiori 2020.

2) Source system: S/4HANA 1709, with Standalone Fiori FES3.0 in running Sybase ASE,
but they want to Embedded into running S/4HANA1709 with upgrade to FES 6.0 and
then testing 200+ Apps before upgrade to latest.
Target system: S/4HANA 2020, with embedded Fiori

3) Source system: S/4HANA 1809 with Fiori running in one application along with HANA but
customer request before upgrade to split the Fiori in separate host running in ASE.
Target system: S/4HANA 2020, with standalone Fiori and its rework  but customer is
Boss in terms of hardware scale up in landscape, testing efforts for migration in new DB
and integration.

4) Source system: S/4HANA along with Fiori running in the initial implementation stage but
due to load or business requirement
Target system: Customer request is to migrate separate into Sybase ASE DB from
HANA.
As you can see FES upgrade also can be different based on the customer business requirement
and initial planning is most important checking all areas with deployment option and system
landscape recommendation as well product availability maintenance.

SAP Fiori Front-End Server

SAP Fiori Front-End Server offers a bundle of technology components that are required to run
SAP Fiori scenarios. It contains the following:

 The UI development toolkit for HTML5 (SAPUI5) framework and the components to run the SAP
Fiori launchpad on the ABAP stack,
 The SAP Gateway core components on the ABAP stack,
 The SAP Fiori Implementation Foundation,
 SAP Fiori Basis Apps (available only with SAP NetWeaver 7.5 or higher).

SAP Fiori Front-end Server does not provide any new technical components. It has been created
to define the exact stacks required for SAP Fiori application versions and thereby simplify
customer consumption.

Deployment Architecture

The deployment architecture of SAP Fiori FES is based on the following main technical
components:

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 1
SAP Fiori Community Wiki Link its going to be retired soon but you gain knowledge once read.

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 2
Important notes:
 As SAP S/4HANA 1511 is only released with SAP FES 2.0, there is no option to just upgrade
SAP FES 2.0 to a higher FES version. An upgrade to a higher SAP S/4HANA release is
recommended.
 SAP FES 2.0 and 4.0, both are out of maintenance since December 31th, 2020. An upgrade
to SAP Fiori front-end server 6.0 is recommended or an upgrade to a higher SAP S/4HANA
release.
 SAP FES 6.0 is the long-term maintenance version and the recommended go-to-version for
SAP FES upgrades for SAP S/4HANA releases lower than 1809.
 SAP Fiori front-end server 2020 for S/4HANA supports only the latest SAP S/4HANA releases
1809/1909/2020. It cannot be used with older SAP S/4HANA releases.
 To consume future SAP Fiori UI innovations also for SAP S/4HANA releases lower than 1809
systems, an upgrade to a higher SAP S/4HANA release is recommended.
 For SAP FES 2020 for S/4HANA, both deployment options - embedded and FES standalone
server - are supported. The embedded deployment is recommended.
 SAP FES 2020 is the last version supporting IE11 as browser, see also this blog post.
Upgrade Recommendations

SAP FES 6.0 is the long-term maintenance version and the recommended go-to-version for SAP Fiori
front-end server upgrades for SAP Business Suite and SAP S/4HANA customers.

This following graph shows the upgrade options of SAP FES for the different SAP S/4HANA releases
in an embedded deployment.

Each SAP S/4HANA release comes with an initial SAP FES version as a minimum version. For
example, for SAP S/4HANA 1709 the minimum version is SAP FES 4.0. It can be upgraded to
SAP FES 5.0 or SAP FES 6.0 independent from SAP S/4HANA software components as shown
in the graph. The recommendation is to upgrade directly to SAP FES 6.0.

SAP FES 3.0 is out of maintenance since 31th of December 2019. An upgrade to SAP FES 6.0
is recommended.

Note: It’s recommended to apply the most recent patch of SAPUI5 after upgrading the SAP_UI
component; for example, apply the latest available SAPUI5 1.71.xx patch after upgrading to
SAP_UI 7.54 SP02 which is included in FES 6.0 SP01. For more information on the latest
available SAPUI5 patches and how to apply, see SAP Notes 2346367 and 2856654 (for SAPUI5
1.71).

Restrictions: Please note, that for specific apps of software component “UI for Basis
Applications” (UIBAS001) there are dependencies to the SAP S/4HANA backend or SAP
NetWeaver version. See also SAP Note 2898376.

SAP Fiori Front-end Server upgrade to 2020 for SAP S/4HANA

In Month May 2021: Additional hints regarding SAP Fiori front-end server maintenance period
according to SAP note 2217489 and restrictions regarding the compatibility of apps of
component UIBAS001 600 with S/4HANA backend releases, as described in SAP note 2436567.

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 3
In February 2021: Release of SAP Fiori front-end server 2020 for SAP S/4HANA SP01 which
includes SAPUI5 1.84 as long-term maintenance version and which also supports SAP Business
Suite in the hub or standalone server deployment

Schedules for Maintenance Deliveries SAP Fiori front-end Server 2021 for SAP S/4HANA

SAP Note: 2436567 - UI for Basis Applications - General Information

While downloading patch from maintenance planner, here is the catch for ignore 2 upgrade if you
are running in lower version. Check how play around to generate and download the patches direct
for SAP FES to 2020.

Also, I tried to provide more information with SAP Notes, Link to refer, Product Maintenance change
in UI components and more.

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 4
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 5
 Select NW: 7.52 SP8

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 6
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 7
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 8
 Extracted SUM at below location:

Starting SUM with root:

Reinstalled host agent and killed old SUM process (ps –ef|grep SUM)

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 9
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 10
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 11
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 12
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 13
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 14
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 15
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 16
 To fix this:

Login to Sybase:
1> sp_configure 'worker'
2> go
Check the parameter value:
1> sp_configure 'number of worker processes',40
2> go

After executing above, we got error on kernel resource memory which has to be increased as
well. It’s also DYNAMIC. So no restart needed.

1> sp_configure 'kernel resource memory'

2> go

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 17
 1> sp_configure 'kernel resource memory',36267
2> go

1> sp_configure 'number of worker processes',40

2> go

2nd Parameter:

1> sp_configure 'lock hashtable'

2> go

1> sp_configure 'lock hashtable size',81920

2> go

This is static parameter. Hence, restart of Sybase DB is needed.

DB Restarted. Moving ahead.

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 18
 Lock the development after communication with Customer

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 19
 Internal inconsistency: Found 1 duplicate index names

Duplicate entry for index '/UI2/PB_C_TMMLPDPR'!

To fix:

Before:

After:

SAP Fiori Front-end Server 2020 for SAP S/4HANA

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 20
 SUM Backup: Taken Back up of SUM.
DB Backup:
BTCTRNS1:

Started Downtime:

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 21
 Both are okay:

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 22
 Both are okay. Proceed.

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 23
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 24
 SGEN:

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 25
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 26
Never Stop Learning, Never Stop Exploring
Jasbir Khanuja
Page | 27
 Difference of two components:

1) UIX01CA1 :

2221151 - Release Information note for SAP Fiori My Inbox 2.0

Important Maintenance Information: The UIX01CA1 200 add-on component ( UI for

Cross Applications 200) delivering the My Inbox Fiori app is in mainstream maintenance
until 31.12.2022. The add-on component has been retrofitted in the UIBAS001
component (UI for Basis Applications ), starting with UIBAS001 400. Please consider
upgrading the version of the SAP Fiori Front-end Server (SAP Fiori front-end Server, Add-
on to AS ABAP, Basis for SAP Fiori Apps) to minimum SAP Fiori front-end server 5.0 or
higher

2676990 - Release Information note for SAP Fiori My Inbox

Please note: New features for My Inbox application will from now on be delivered with
SAP UI FOR BASIS APPLICATIONS component only. If you are a SAP Business Suite
customer and you would like to adopt newly added functionalities for My Inbox
application, you need to upgrade the version of your SAP Fiori Front-End Server to
minimum SAP Front-End Server 5.0.

2) SAPUIFT:

2486528 - Discontinuation of ABAP add-on SAPUIFT (SAP Fiori App Implementation

Foundation)

https://blogs.sap.com/2017/12/06/sap-fiori-front-end-server-in-a-nutshell/

References:

SAP Note: 2935725 - General Information: Installation details of SAP Fiori front-end server 2020
for SAP S/4HANA
SAP Note: 2881803 - FAQ: S/4HANA Fiori Best Practices - Collective Note
SAP Note: 2217489 - Maintenance and Update Strategy for SAP Fiori Front-End Server
SAP Note: 2935911 - SAP FIORI FOR SAP S/4HANA 2020: Release Information Note
SAP Note:2590653 - SAP Fiori front-end server deployment for SAP S/4HANA
Browser Support PAM for SAP S/4HANA 2020 & SAP S/4HANA FOUNDATION 2020
SAP Note: 2919182 - SAP Fiori front-end server 2020 for SAP S/4HANA
Landscape Deployment Recommendation for SAP Fiori front-end server.

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 28
 SAP Note: 2947824 - Composite SAP note: Rapid Activation for SAP Fiori in SAP S/4HANA 2020
How and why to upgrade SAP Fiori for your SAP S/4HANA solution
SAP Fiori deployment options and SAP Fiori front-end server strategy – UPDATE 2020

https://sapui5.hana.ondemand.com/versionoverview.html

Happy Learning – Jasbir Khanuja

Never Stop Learning, Never Stop Exploring
Thank You

Never Stop Learning, Never Stop Exploring

Jasbir Khanuja
Page | 29