SAP Fiori deployment options and SAP Fiori front-end server strategy - UPDATE 2023

[Carola1]

**This blog post is updated in February 2024 **
Update February 2024: Release of SAP Fiori front-end server 2023 for SAP S/4HANA SP01 including SAPUI5 1.120 maintenance version. 

Update December 2023: The maintenance period of SAP Fiori front-end server 2020 and 2021 has been extended and is now aligned with the SAP S/4HANA release 2020 and 2021. Many customers asked for this extension.
The upgrade to a newer SAP FES version while keeping the SAP S/4HANA backend on 2020/2021 is now an optional step. It is still recommended to get new UI technology innovations.
Please also refer to the updated SAP Fiori deployment options and system landscape recommendations document, which includes the relevant SAP notes.

Update October 2023: Release of SAP Fiori front-end server 2023 for SAP S/4HANA.
Update on SAP Fiori front-end server strategy beyond 2023.

Update March 2023: SAP Fiori front-end server 2022 is released for SAP S/4HANA 1809/1909 to support the extended maintenance of SAP S/4HANA.

------------------------------------------------------------------------------------------------------------------------------------

This blog post delivers a short summary of the different SAP Fiori front-end server versions and the related deployment options. For more details, please check the document SAP Fiori deployment options and system landscape recommendations.

SAP Fiori front-end server 6.0 is a long-term, stable UI technology foundation for SAP Fiori apps of SAP Business Suite and SAP S/4HANA systems, see also blog post. The end of maintenance of SAP Fiori FES 6.0 (end of 2030) relates directly to the maintenance period of SAP Business Suite.

SAP Fiori front-end server 6.0 - same as the predecessor versions - can be deployed embedded or as a standalone server/hub for SAP S/4HANA and SAP Business Suite systems.
The embedded deployment for SAP S/4HANA systems is the recommended setup.
The standalone server deployment for SAP S/4HANA systems is mainly used by customers due to security aspects for external access scenarios.

In addition, for SAP Business Suite systems, the SAP Fiori front-end server can serve as central hub to offer a single entry point to multiple systems. This is not possible for an SAP S/4HANA system landscape, because of the version dependencies of the SAP Fiori UI components and backend versions.

The SAP Fiori front-end server versions up to 6.0 support all SAP S/4HANA and SAP Business Suite releases, down to SAP NetWeaver 7.40 based installations. This enables customers to consume new UI technology innovations by a selective upgrade of the SAP Fiori front-end server without touching the backend components.
See also SAP note 2217489.

SAP Fiori front-end server 2020 for SAP S/4HANA (SAP FES 2020) was initially dedicated to the SAP S/4HANA product. Due to mandatory legal requirements related to accessibility, also SAP Business Suite apps are released for SAP Fiori front-end server 2020 as of SP01. This allows customers to reach accessibility compliance for SAP Business Suite apps by using the new SAP Fiori front-end server version as a central hub or standalone server.
The end of maintenance of SAP FES 2020 is aligned with the maintenance period of SAP S/4HANA 2020 (end of year 2025).
See also SAP note 2919182

SAP Fiori front-end server 2021 for SAP S/4HANA (SAP FES 2021) has the same deployment recommendations as the predecessor versions (embedded for SAP S/4HANA systems, hub deployment for Business Suite). SAP FES 2021 does not support IE11 browser any more.
The end of maintenance of SAP FES 2021 is aligned with the maintenance period of SAP S/4HANA 2021 (end of year 2026)
See also SAP note 3050199.

SAP Fiori front-end server 2022 for SAP S/4HANA (SAP FES 2022) has the same deployment recommendations as the predecessor versions (embedded or standalone FES server for SAP S/4HANA systems, hub deployment for Business Suite). The end of maintenance of SAP FES 2022 is aligned with the maintenance period of SAP S/4HANA 2022 (end of year 2027).
See also SAP note 3191581.

SAP Fiori front-end server 2023 for SAP S/4HANA (SAP FES 2023) has the same deployment recommendations as the predecessor versions (embedded or standalone FES server for SAP S/4HANA systems, hub deployment for Business Suite). The end of maintenance of SAP FES 2023 is aligned with the maintenance period of SAP Business Suite (end of year 2030).
See also SAP note 3340880.

Stack Definition:

SAP FES 2020 contains the software components SAP_UI 7.55 (including SAPUI5 version 1.84 as long-term maintenance version) and UIBAS001 600.
SAP FES 2021 contains the software components SAP_UI 7.56 (including SAPUI5 1.96 as long-term maintenance version) and UIBAS001 700.
SAP FES 2022 contains software components SAP_UI 7.57 (including SAPUI5 1.108 as long-term maintenance version) and UIBAS001 757.
SAP FES 2023 contains software components SAP_UI 7.58 (including SAPUI5 1.120 as long-term maintenance version) and UIBAS001 758. It's recommended to directly start with the latest available patch level of SAPUI5 1.120.

For more information on planned support packages please refer to Schedule for maintenance deliveries.

Supported Products:

SAP FES 2020 can be used for the SAP S/4HANA releases: 1809, 1909 and 2020 and for SAP Business Suite systems. Lower SAP S/4HANA releases are not supported.
Please note, that there are restrictions regarding the compatibility of UIBAS001 600 apps/components with S/4HANA 1809/1909, see SAP note 2436567.
To resolve this, you can keep the UIBAS001 version to 500 while upgrading SAP_UI to 7.55 during an upgrade to FES 2020 in an SAP S/4HANA 1809 or 1909 installation. For more details, see SAP note 2217489.

SAP FES 2021 supports the S/4HANA releases: 1909, 2020, 2021 and SAP Business Suite systems. There are restrictions regarding the compatibility of UIBAS001 700 apps/components with S/4HANA 1909/2020, see SAP note 2436567.
To resolve this, you can keep the UIBAS001 version to 500 or 600 while upgrading SAP_UI to 7.56 during an upgrade to FES 2021. For more details, see SAP note 2217489.

SAP FES 2022 supports the S/4HANA releases: 1809, 1909, 2020, 2021, 2022 and SAP Business Suite systems. There are restrictions regarding the compatibility of UIBAS001 757 apps/components with S/4HANA releases lower than 2022, see SAP note 2436567. To resolve this, you can keep the UIBAS001 version to 500, 600 or 700 while upgrading SAP_UI to 7.57 during an upgrade to FES 2022. For more details, see SAP note 2217489.

SAP FES 2022 was released also for SAP S/4HANA 1809 and 1909 to support the extended maintenance of SAP S/4HANA 1709/1809/1909 (see also SAP note 3246630).
For SAP S/4HANA 1709, the SAP FES 6.0 is the long-term maintenance front-end server version.

SAP FES 2023 supports only the newest S/4HANA release 2023.
SAP Business Suite systems are still supported with FES 2023 in the hub deployment. In this case the SAP FES hub is based on SAP S/4HANA Foundation 2023 and thus requires a SAP HANA database.
It's the last SAP Fiori front-end server version which can be used as hub or standalone server and in consequence it's the last SAP FES version which supports Business Suite systems. Therefore SAP FES 2023 has a long-term maintenance period until end of SAP Business Suite maintenance.

Deployment Options:

For SAP S/4HANA systems both deployment options - embedded and standalone FES server - are supported. The embedded  deployment  is  the recommended one.
SAP Fiori front-end server cannot serve as central entry point (hub) to multiple S/4HANA systems, see SAP Fiori deployment options and system landscape recommendations.

For SAP Business Suite systems only the hub or standalone server deployment is supported - not the embedded deployment. This is due to the minimum SAP NetWeaver version 7.52 for the FES versions up to FES 2022.

SAP FES 2023 version requires ABAP Platform 2023. Therefore on the front-end server hub SAP S/4HANA Foundation 2023 is required and thus you only can use SAP HANA as database on the hub with the newest SAP FES version.

SAP FES 2023 is the last FES version which supports a hub or standalone server deployment. Beginning with SAP S/4HANA release 2025 the embedded deployment of Fiori UIs will be the only deployment option.

Upgrade Options:

This graph shows the possible upgrade options of the SAP FES with a given SAP S/4HANA release as backend:

 As shown in the graph, up to SAP FES version 2022, you can upgrade the front-end server components without upgrading the S/4HANA product version (delta upgrade). This is valid for the embedded and for a standalone server deployment.

To resolve dependencies of UIBAS001 600/700/757 apps to the S/4HANA backend version (see also SAP note 2436567) you can keep the UIBAS001 version according to the fitting S/4HANA backend version while upgrading the SAP_UI component (including SAPUI5) to the newer version, see SAP note 2217489.

To get innovations delivered with FES 2023, a full-stack SAP S/4HANA 2023 upgrade is required.
There is no FES delta upgrade option to SAP FES 2023 any more. FES 2023 software consumes ABAP Platform 2023 technology features, which are not available on SAP NetWeaver 7.52.
The full-stack upgrade to SAP S/4HANA 2023 can be performed also for lower S/4HANA releases.

SAP Fiori front-end server as of versions 2020, 2021 and 2022 require SAP NetWeaver 7.52 on the hub/standalone server. This is required to be able to consume technology features, such as OData Version 4.0, and thus reduces technical limitations for future UI technology innovations.

For lower SAP S/4HANA releases an upgrade to the long-term maintenance version SAP Fiori front-end server 6.0 is recommended. Please refer also to this blog post.

Please note:
Due to many customer requests the maintenance period of SAP FES 2020 and 2021 is now aligned with the respective S/4HANA release. Therefore the upgrade of the FES components is an optional step, but is still recommended to get new UI technology innovations also for the older S/4HANA releases. Before, in general the SAP Fiori front-end server versions had only a two-years maintenance period.

SAP FES 2022 also has a longer maintenance period until end of 2027 (aligned with SAP S/4HANA 2022), as there is no FES delta upgrade option to SAP FES 2023.

SAP Fiori front-end server with SAP Business Suite - upgrade options

All SAP Fiori front-end server versions up to FES 2023 support SAP Business Suite systems in a hub/standalone server deployment. The scenario with a central front-end server hub with one SAP S/4HANA system and one or several SAP Business Suite systems (the so-called "mixed" scenario) can be realized.

Note:

• SAP S/4HANA Foundation 2023 will not be released as development platform succeeding SAP NetWeaver, but only for specific use cases and products. Further information you find in SAP note 3306766 - SAP S/4HANA Foundation 2023: Release Information.
• In case you want to have IE11 support beyond the end of maintenance of FES 2020, which is end of 2023, you should stay with SAP FES 6.0.

Strategy and future direction

SAP FES 2023 is planned to be the last SAP Fiori front-end server version which can be used as a hub or standalone server.
As of SAP S/4HANA release 2025 the embedded deployment of Fiori UIs will be the only deployment option. Then the Fiori UIs are deployed on the S/4HANA backend system and a "lean hub" could serve as a routing component with the option to run in a different network zone for external access scenarios. This is an optional setup for customers who want to have a dedicated additional server with Edge Authentication and protocol switch (HTTP->RFC) in front of their S/4HANA backend system. The "lean hub" option is NOT meant to be a different SAP Fiori launchpad including Fiori application content, e.g. to define an alternative external access point with reduced Fiori content for the same backend system and same user.
More details on the 'lean hub' option will be available end of year 2024.

On a long-term perspective an SAP Business Technology Platform service as the Unified Gateway could serve as a hub in future.

The front-end server hub as central entry point to multiple systems with UX integration capabilities is covered by the SAP Build Work Zone on SAP Business Technology Platform, which will further evolve over times. For more information see SAP Help and Roadmap for SAP Build Work Zone.

SAP Fiori Deployment Options and System Landscape Recommendations

Please check out the newly updated document SAP Fiori Deployment Options and System Landscape Recommendations  for more detailed information.
Please also checkout the newest update on the SAP S/4HANA release and maintenance strategy.

Further information

Schedule of maintenance deliveries: SAP FES Support Packages

 

[Carola1]

Hello Jens,

1. FES6.0 (including UIBAS001 500) is the minimum front-end server version which is in maintenance. You also could use FES2020 or FES2021 as hub for the Business Suite system.


2. I would say "Yes". Restrictions should be mentioned in this note.


3. Yes.

You are welcome with all the questions 🙂

Kind regards.

Carola

[mathewzdavis]

Hi Carola,

Can we use S/4Hana embedded system as a hub for existing ERP systems?

 

Thanks

[Carola1]

Hi,

even if it's currently technically possible to set it up in this way, this is not a recommended/supported deployment option. It's also not a forward-looking setup, because SAP Business Suite support might be not given for future SAP Fiori front-end server versions.
Kind regards.

Carola

 

[mathewzdavis]

Thank you Carola for the update.

If we are going with mixed/hybrid, like Hub approach for business suites systems and embedded approach for S/4 Hana and  try to call fiori apps of S/4 Hana via URL in Hub launchpad, will it support in-place navigation?

Regards,

Mathew

[raffi1]

Hi altogether,

according to the last questions of Matt D above for that mixed scenario: If we like to have a full on premise scenario (business suite, S/4 and hub gateway in our own data center), there is no way of centralising ERP-S/4- and e.g. HCM-Business-Suite Fiori apps in one launchpad?

If I am reading the PDF document correct, in this mixed scenario, you will add a tile on the central hub Fiori launchpad, besides the HCM business suite Fiori apps tiles. This tile then links to the Fiori launchpad of the embedded S/4-sytem. Is there still no alternative for such a mixed scenario for on prem for a real central Fiori launchpad?

If not on prem: Are Work Zone and Launchpad Service real central alternatives for such a mixed scenario?

thanks and best regards

Christian

[msavchyna]

Dear Carola,

Thanks a lot for your blogs, you are doing great job.

But I’m still not sure with my landscape. Could you please help me?

We have SAP FES 6.0 (SAP_GWFND 750 0022) and SAP Business Suite systems (ERP 6 EHP6, 6 EHP8, CRM) as back-end systems of this FES. One of our ERP (ERP6.0 EHP 6) is migrating to S/4HANA 2021. For security reason we want to keep hub-deployment scenario with one S/4HANA system and Business Suite systems. We want to

• Upgrade FES 6.0 to FES 2021


• Implement embedded scenario for S/4HANA 2021 but in parallel deploy some apps (which should be visible from Internet) in SAP FES 2021


• Remain Business Suite systems (ERP 6 EHP8 and Solman 7.2 CRM) to work with SAP FES 2021

Is it feasible solution?

Thank you!

[Carola1]

Dear Marina,

This is absolutely feasible. Please consider that you need to upgrade the SAP NetWeaver version to 7.52 on the hub as a prerequisite for SAP FES 2021.

Kind regards. Carola

[JaySchwendemann]

Thanks Marina and Carola,

and forgive me to hijack this 🙂 We have a similar situation, but with ERP and HCM as backends, where ERP is moving towards S4H. So my takeaway would be that it is a good idea to select "embedded" setup in Maintenance Planner when planing S4H but one can then selectively provide some apps over the Hub system? So planning with "embedded" would not harm but give you more flexibility if a FES Hub is already existing in the landscape? Any downsides to this approach?

 

Many thanks and kind regards

Jens

[Jocelyn_Dart]

HI Jens

You can always do URL tiles to launch apps in the other FES. This is the fallback for situations like these.

Re downsides: This is not SAP's strategic direction for Hub. So expect some limitations. It's advisable consider SAP Launchpad Service on BTP if you are considering a central hub approach - especially if this may be a longterm direction for your organization.

P.s. You  might also want to look at the direction of HCM - embedding that in S/4HANA may provide you with an alternative to consolidate your landscape - depending on your requirements of course. . Refer to: SAP Human Capital Management for SAP S/4HANA, on-premise edition – Available in Q4 2022 as part of t...

Best

Jocelyn

[Jocelyn_Dart]

Hi Christian, SAP Launchpad Service on SAP BTP is the recommended approach where you need a central hub across multiple systems.  SAP's strategy is cloud-centric and has been for some years now.

Best

Jocelyn

[JaySchwendemann]

If I understood Matt's intention he asked about utilizing an S4H embedded FES as a hub for another ERP system.

If you are talking separate S4H, separate ERP (Business Suite) and separate HCM (also Business Suite) and dedicated separate FES hub (then on SAP DB because of S4H) you should be able to run it as a central launchpad.

There is a rather tight dependency between the S4H and the FES though. If you update the S4H you will need to update the FES also. SAP isn't (at least what I saw) commited to release all ERP / HCM apps for future FES for S4H versions. So there is a certain caveat lingering. Certainly you will need to stick to AS ABAP 7.52 for the FES. You will not get ABAP Foundation in the Hub Scenario.

Cheers

Jens

[hauntedhill]

Dear Carola,

i have a question about the "Strategy 2023 and future direction".

You wrote:

For SAP S/4HANA systems both deployment options (embedded or standalone server) will be possible, but the new SAP FES 2023 version will not support lower SAP S/4HANA releases and thus a pure FES upgrade will not be possible.

This means we cant upgrade our standalone FES to SAP FES2023 without upgrade our backend system to S/4 HANA 2023? Or is this restriction only with an embedded deplyment?

Thanks and Regards

Christian

[former_member252631]

Feature Strategy

Hi Carola,

Thank you for sharing the useful guideline.

Could you expand a little more about the strategy 2023 and feature direction?  It seems that it is recommended to deploy custom SAPUI5 apps onto BTP but not on-premise.

In case SAPUI5 app calls white listed OData on S/4HANA on premise, to where the UI should be deployed: to BTP or on-premise?

Thank you and best regards,

Misako

[Carola1]

Hi Christian,

Yes, in that case you need a full-stack S/4HANA upgrade to 2023.

Please check out also the newest post on SAP S/4HANA release strategy: New SAP S/4HANA Release & Maintenance Strategy | SAP News.

Kind regards. Carola

[Carola1]

Hi Misako,

The SAPUI5 apps can be deployed on the on-premise stack.
From what do you conclude that the apps should be deployed on BTP ?

Kind regards.

Carola

[StephanHeinberg]

Dear Carola,

with the new announced release strategy for SAP S/4HANA 2023, there will be only a mayor release of S/4 every second year.

What happens with the release strategy of the FES for S/4? Will you start to ship a new SAPUI5 version with a Feature Package or will there be new innovations (SAPUI5 release) only every second year?

Thanks,

Stephan

[JaySchwendemann]

Hi Carola,

thanks for the update. I also want to delve into the 2023 and future direction part. You said

SAP’s strategic direction is to evolve powerful alternatives for a SAP Fiori front-end server as a central hub or standalone server with a much lower TCO on customer-side.
A first step might be a “lean hub” where the Fiori UIs are deployed on the backend system and the “lean hub” serves as a routing component with the option to run in a different network zone for external access scenarios. Later a SAP Business Technology Platform service as the Unified Gateway could serve as a hub in future.

Is a "Lean Hub" just a way to deploy the then 2023 or 2024... FES or will it be another product. Is it even available as a way to deploy today?

Is the "Later a SAP BTP service..." a look into the future to a new offering that SAP is coming up with or is it a way to describe a customer's journey with products and offerings already available today (read: BTP Launchpad Services, ...)

 

Background: We are in a  S4H migration project where we will end up with one ERP S4H and maybe one HCM S4H. However, they will not come into place at the same time and we will be in 2024+ when that happens. So there is a need for supporting an S4H system and a business suite system over an FES. We currently opted for FES Hub because of internet facing scenarios. We really want to keep the single launchpad, though.

 

Cheers and many thanks

Jens

[Carola1]

Hi Stephan,

As is the past, with the FSP01 of each SAP S/4HANA release you will also get a new SAPUI5 version which is SAPUI5 maintenance version).  That means with SAP S/4HANA 2023 you will get a new SAPUI5 version in February 2024 with FPS01.

In principle, the SAP S/4HANA feature pack stacks are planned to focus on application innovations using a stable technology stack. Therefore I would not expect that there are major UI technology innovations made available during the later feature stack pack delivery.

Finally, to which extend SAPUI5 innovations will be made available for the SAP S/4HANA feature stack packs is not yet decided.

Kind regards. Carola

[shravandhage]

Dear carola.steinmaier

Good day, thank you for your great & detailed post, which made things quite clear. We had just few queries about understanding before starting our implementation project, as we have multi system scenario, we want to understand which version UIBAS001 we shall keep in SAP FES S42022 while our FES upgrade from 5.0 so it will support multi system scenario where ERP running currently on EHP7 with plan to upgrade to S4HANA 2022 and HR system with from EHP7 to EHP8?

in the SAP Note, it says "600 or 700 or 757", which is not clear, hence would like to understand will 757 will support the requirement for multi system running where current multi systems are running on EHP7 or FES upgrade should plan at the same time of S4HANA conversion of ERP and keep version as 757. 

Appreciate if you could guide.

Thank you in advance.
Best Regards,

SD

[Carola1]

Hello,

The UIBAS component version only has dependencies to the S/4HANA release and not to the ERP.

Therefore, when you upgrade the SAP Fiori front-end server hub to FES 2022 with an S/4HANA 2022  as connected backend, then you should choose UIBAS001 757.
Still the ERP system can stay with the same FES hub.

Kind regards.

Carola

[cperdomo]

Hi Carola,

Thank you very much for all the information provided and I would really appreciate it if you could help me with this scenario. 



Currently in the company they have only sap business suite and they want to implement sap Fiori using the SAP BTP lauchpad as input. In the near future, they do not contemplate upgrading to SAP HANA, so we are studying the alternatives of installing a sap front end server or using an embedded system.

From my point of view, I think that the embedded system is the best option, because the SAP BTP would control the access without affecting the security. I would like you to help me to see if I am correct in thinking that already working with SAP BTP, it is not necessary to install an additional front end server.



Thanks,

[roger_sainsbury]

Hi Carola and colleagues,

I'm still unclear about the guidance on UIBAS001.

My customer is implementing S/4HANA 2020 on RISE. They do not want to upgrade the whole system at the current time, however the FES goes out of maintenance at the end of this year - so that part must be updated.

SAP Note 2436567 explains that only UIBAS001 600 is supported for S/4HANA 2020, for app F1240 (Application Jobs) and all apps which use F2057 (Application Jobs Reuse Library).

This blog explains that:

'you can keep the UIBAS001 version according to the fitting S/4HANA backend version while upgrading the SAP_UI component (including SAPUI5) to the newer version, see SAP note 2217489.'

But I don't see how note 2217489 gives you that conclusion? The only relevant comment I see there is:

'The table shows the default UIBAS001 software component version according to the SAP Maintenance Planner. In some cases (hub/standalone server deployment) alternative versions can be chosen to meet the dependencies to the respective S/4HANA backend release'

As I read it then, upgrading SAP_UI without upgrading UIBAS001 is only possible with a standalone hub FES, not with embedded FES? My customer has an embedded FES, as per SAP's guidance for S/4HANA from 1709 onwards as I recall.

Am I missing something?

thanks, Roger

 

[JaySchwendemann]

Roger,

I could at least confirm that the following is working, albeit we needed two takes on UIBAS

• FES HUB on Fiori Frontend Server for S4H 2021
  
  
  
  • UIBAS001 700 003 (matching S4H 2021)
    
    
    
    • Maintenance Planner gave us initially UIBAS001 500
    
    
    • We then afterwards installed UIBAS001 700 manually (via SPAM)
    
    
    
    
  
  
  
  


• S/4HANA 2021 project landscape backend system attached to FES


• ERP ECC 6.0 EHP 8 maintenance landscape backend system attached to FES

If you are on embedded UIBAS must at minimum match your S4H system, not necesseraly being the one that is shiipped per default with the FES. I'll give you an example (albeit already shown in the blog above)

• Scenario
  
  
  
  • Your customer is currently on S4H 2020 and stays put with S4H but wants to update the embedded FES from FES 2020 to FES 2022
  
  
  
  


• You can then eihter
  
  
  
  • Keep the UIBAS to say UIBAS001 600 --> Matches the S4H 2020, no compatibility issues expected
  
  
  • Or update UIBAS to say UIBAS001 757 --> Comes per default with FES 2022. Compatibility issues with S4H 2020 may occur
  
  
  
  

Makes sense?

Cheer

Jens

[roger_sainsbury]

Hi Jens,

thanks for the reply.

So your example was from a hub deployment, but you're saying the same should work with embedded? E.g. we can retain UIBAS001 600 to avoid the problems with F1240 and F2057 highlighted in Note 2436567, but upgrade the SAP_UI component?

thanks, Roger

[Carola1]

Hi Jens,

for the embedded deployment the maintenance planner proposes the fitting UIBAS version according to the S/4HANA release: SAP S/4HANA 2020 fits to UIBAS001 600.

For the Hub deployment the maintenance planner proposes a lower default version because it's not clear which S/4HANA version is used in combination with the hub (NW 7.52). Then you need to select the appropriate UIBAS version according to your setup/ S/4HANA version.

Kind regards.

Carola

SAP note 2217489

[marcos_antoniomagalhesjun]

Hi Carola

We are planning upgrade FES form 2.0 to 6.0.

We perform Maintenance Planner withou problem for front end Server.

We have facing an difficulty with documentation to check what we need update in backend systems?

How can we check this dependencies?

We believe that is a bit confused.

Regards

Marcos

 

[JaySchwendemann]

Thanks for clarification Carola,

I'm not the OP here but interested anyways. So my takeaway (on behalf of Roger) would be:

• For an embedded FES, MP suggests UIBAS001 600, fitting to S4H 2020


• UIBAS001 600 is also supported for FES 2022, according to note 2217489


• So S4H 2020, UIBAS001 600 and FES 2022 (embedded) is a valid scenario

Correct or wrong?

Cheers

Jens

[cyanezde]

Hello Carola,

We are planning to implement a Fiori Front End Server (FES 6.0) (hub deployment) for our backend system running on EHP8 FOR SAP ERP 6.0.

We were thinking to install the Fiori Front-End Server with MSSQL database, is this possible as we want to use the NW AS ABAP 7.52 version? or it should only be as mentioned even though we are not using S/4 HANA FES  SAP Note https://me.sap.com/notes/2929282 ?

• Running SAP FIORI Fiori front-end server hub deployment, SAP MaxDB, Sybase ASE and SAP HANA Database are supported database systems.

What would be your recommendation?

Thanks in advance

Regards

Claudia

[Carola1]

Hi Claudia,

in case you only use the FES Hub for ERP systems you can use also MSSQL as database. The required SAP DB is only relevant in case you use S/4HANA as backend system.

Kind regards.

Carola

[cyanezde]

Thank you very much.

[cyanezde]

Hi Carola,

We think that going with HANA database will be a better approach for the future. We would like to install: SAP Fiori Front-End Server AS ABAP 7.52 FOR S/4HANA FES 6.0 to be able to connect to our ERP systems in the backend.

Could you give me some guidance if linux is the only OS supported for this? And if the HANA database must be installed on a different server than the application? And for the last question, is the fiori front-end server should be install in the DMZ? Or that only applies to the Web Dispatcher.

Thanks in advance

Best regards

Claudia

[sreekumar86]

Hello Carola,

 

Can you please share the official SAP document publised to support the embedded deployement only for S4HANA 2025 . Highly appeciated !!

Regards,

Sreekumar N

[Toni1]

#1

Product Availability Matrix (PAM) - SAP FIORI FRONT-END SERVER 6.0

• Product Availability Matrix (PAM) - AS ABAP 7.52 FOR S/4HANA FES
  • Operating System Options

#2

1953429

Note: Pay attention to additive sizes and separate SIDs!

#3

Considerations and Recommendations for Internet-facing Fiori apps

my2cents: I recommend you consult an architect.

[Toni1]

FYI: SAP S/4HANA 2023 is the latest.

PAM - SAP S/4HANA 2023

"As of SAP S/4HANA release 2025 the embedded deployment of Fiori UIs will be the only deployment option." is merely an outlook.

[sreekumar86]

tobo yes am aware SAP S/4 HANA 2023 is the latest released , But as per the blog S/4 2025  HANA 2025 Hub deployment will be obsolete . if there is official documentation from SAP it would be great .

[vinnylee]

The Fiori Deployment Options white paper / PDF now has removed the 'Embedded vs Hub' pros and cons Section - reason stated in the Changelog is that Embedded will be the ONLY option for FES 2025. I'm updating my slides as we speak as the messaging to my customers will be different now compared to November 2023 🙂
Keep on Rolling with the Punches 😄

KR,

Vincent (SAP CoE - Fiori MobileUX Team)

[uta_hedemann]

Unfortunately  in version Version 9.2, January 2024 there is now a broken link on page 4:

Alternatively, an SAP S/4HANA system with a dedicated standalone SAP Fiori front-end server (for each SAP S/4HANA system) might be an option for certain use cases. For more details, please refer to section Error! Reference source not found..

I would suggest to review/correct the PDF version 9.2.
IMHO it would be also an option for page 4:

Alternatively, an SAP S/4HANA system with a dedicated standalone SAP Fiori front-end server (for each SAP S/4HANA system) might be an option (for Releases < S4/HANA 2025 ONLY!) for certain use cases. For more details, please refer to section FES Embedded OR Hub deployment – Pros and Cons.

and to keep the chapter FES EMBEDDED OR HUB DEPLOYMENT – PROS AND CONS in the PDF but to add a red marked contra section in "One physical FES"

• SAP FES 2023 is planned to be the last SAP Fiori front-end server version which can be used as a hub or standalone server.As of SAP S/4HANA release 2025 the embedded deployment of Fiori UIs will be the only deployment option.

[Carola1]

Hi Ute,

thanks for the hint. The document is updated and a link is added to the Outlook section.

Kind regards.

Carola

[Carola1]

Hi,
as already mentioned by Vincent, the SAP Fiori deployment document is the official SAP document you can refer to regarding this topic.

Kind regards

Carola

[ALLAMPRABHU]

HI ,

The MP is not give any error while generating the STACK.XML, and it selected target for SAP FIORI for SAP S/4HANA 2022 & SAP FIORI FES 2023 for SAP S/4HANA 2023  as target components, along with 

SAP S4HANA on PRIMISE, ,SAP S/4 HANA FOUNDATION, ,SAP FIORI FES for S/4HANA

ABAP PLATFORM 

The SUM tool deleted the installed FIORI FOR SAP S/4HANA 2022 component from the installed Product version while performing the upgrade.

Root cause of the issue is MP is not generated correctly by MP , even that also SUM should not delete the installed Product version it should carry forward the present component's 

Regards

Allamprabhu 

[Carola1]

Hi Allamprabhu,

Please could you open a ticket on component BC-UPG-MP to clarify you issue?

SAP FIORI FOR SAP S/4HANA 2022 is replaced with SAP FIORI FOR SAP S/4HANA 2023 during an upgrade to S/4HANA 2023.

Many thanks. kind regards. Carola