a month ago
Hi SAP Gurus,
I'm just after a bit of advice and guidance regarding future state of BSPs in a Private Cloud S/4HANA 2023 FPS2 scenario.
Now the general guidance from SAP is to modernise BSPs and older UIs to Fiori apps or potentially SAP Build Apps, and I fully agree and endorse that, but our organisation has been given specific guidance that BSPs will no longer be supported in S/4HANA.
Now, I know that BSPs deployed in our PoC S/4HANA environment function perfectly fine, and that as part of the ABAP stack they currently should continue to function as intended. BSPs can also be applied to a tile as a URL link and launched from the Fiori Launchpad. That launchpad when federated to Work Zone SE also functions as expected.
Problem is I've not been able to locate any depreciation or sunset notification or notes (with the exception of CL_BSP_LOGIN_APPLICATION), that support the statement that BSPs will not be supported in S/4HANA, so I am after some advice from the community in case I've missed something, as I cannot find any withdrawal of support from SAP for this aging UI technology.
Thanks in advance for any responses.
Request clarification before answering.
Most likely the announcement that BSP is obsolete and should not be used anymore was posted in SDN back in 2006. After 2 decades and I don't know how many migrations on the community you might have a hard time finding how many times this discussion have happened.
Despite exceptions and SAP having a hard time to say that a technology is dead, Web Dynpro was the replacement of BSP. Web Dynpro in 2025 is as old as drinking wine. SAPUI5 was the de facto replacement of Web Dynpro.
That does not mean SAP has tried to rewrite BSP applications into Web Dynpro Applications nor it has tried to rewrite Web Dynpro apps to SAPUI5 applications nor it will somehow rewrite all SAPUI5 freestyle apps with Fiori elements or SAP Build Apps. That does not even make sense. ABAP reports and module pools are still there and SAP found a way to make them accessible in Fiori other than rewriting those apps from scratch.
In other words, when you say:
but our organisation has been given specific guidance that BSPs will no longer be supported in S/4HANA
Your organization should not be creating BSP applications for almost 2 decades right now and that decision should have been taken way before S/4HANA was created in 2015.
Maybe you did not mention some key information here. if your context is in SAP CRM and you are actually referring to CRM Web UI, than I can agree that you might have reasons for still using it despite other new technologies were introduced over the years. Still Fiori/UI5 was the right way to go for at least 1 decade now.
Maybe there is some misunderstanding here when you wrote:
Now, I know that BSPs deployed in our PoC S/4HANA environment function perfectly fine
If you mean a SAPUI5 application which is deployed to an on-premise system and which becomes visible in SE80 by using the "BSP Application" option - then your question is not about BSP at all.
Just to be very clear - this is how BSP code looks like. It's a mix of HTML code together with ABAP code.
<html>
<body>
<h2>Flight List (from SFLIGHT)</h2>
<table border="1">
<tr>
<th>Carrier</th>
<th>Connection</th>
<th>Flight Date</th>
</tr>
<%
DATA: lt_flights TYPE TABLE OF sflight,
ls_flight TYPE sflight.
SELECT * FROM sflight INTO TABLE lt_flights UP TO 10 ROWS.
LOOP AT lt_flights INTO ls_flight.
%>
<tr>
<td><%= ls_flight-carrid %></td>
<td><%= ls_flight-connid %></td>
<td><%= ls_flight-fldate %></td>
</tr>
<%
ENDLOOP.
%>
</table>
</body>
</html>
BSP applications were not "deployed" because they were literally created in SE80 itself.
If that is the case the one to blame is the person who had the idea to reuse existing functionality in SE80 to display SAPUI5 applications just because they are also web applications. Really confusing but that does not mean SAPUI5 apps are BSP apps.
Please clarify this a little bit more if needed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for getting back to me, yes we are visiting old school UI technology, and I recall being trained on BSPs the back in 2004 (still got the SAP manuals) back when SDN was the place to go (guess most content was lost).
Yes just to clarify that these are legacy classic custom BSP apps (mixture of HMTL and ABAP), so yes definitely not SAPUI5, although as you correctly state they both show in SE80 as BSP apps. The apps date from circa 2007.
They appear to still be functional in S/4HANA 2023 and Work Zone, despite the fact as you state this is considered old UI technology and no-one in their right mind today would consider using BSPs.
I assume the correct way forward is to refactor these to Fiori Freestyle using current Fiori design guidelines. The fact this has not happened in the current ECC system prior to now is something of an oversight and before my time at this organisation, but I 'd personally be inclined to refactor as part of S/4HANA transformation activities (WRICEF/TOSL), and on a modern stack, ideally building on the BTP stack, rather than attempt to refactor to SAPUI5 on an ECC system where UI5 libraries, versions and theming are not current. Deploying BTP to ECC stack is not currently an option either.
I suppose the question is if these still run from FLP in S/4HANA private, like WDA or classic GUI reports and transaction also, will SAP at some point stop these legacy UIs from working. I've also been searching for something that clearly expresses that this legacy UI technology is not supported in S/4HANA, but to no avail and my experience suggests that if technology is no longer supported, it broadly continues to function in S/4HANA. I guess given the level of organisations still running these older UI technologies on-prem or in private cloud, and not all legacy standard transactions have suitable Fiori alternatives, that would require an advance communication exercise that should be fairly easy to locate.
Thanks, Steve
Yes, surprisingly there is no reference for BSP under Work Zone restrictions.
Source: Restrictions | SAP Help Portal
But before refactoring anything I suggest actually to review if such apps still make sense or can be replaced by standard apps. Something created in 2007 could have a standard solution in 2025. Do not only check S/4HANA common knowledge but also some hidden business functions.
If still make sense, you can evaluate if it's SAPUI5 freestyle, Fiori Elements, CAP, a mix of them or anything else based on the tools and services available.
User | Count |
---|---|
24 | |
22 | |
8 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.