Skip to Content

In part 1 of this Blog I outlined the different technologies from SAP that could be used when SAPGUI is not delighting your users.

The table below shows a matrix of these technologies with some common use-cases for UI/UX renovation with my personal preference for a specific screen, as noted in the first part of this blog, a specific end to end use case may (and probably will) use different technologies at different points in the process :

  • Green = My preferred technology if the use-case is as simple as described.
  • Orange = Technologies I would consider if certain other conditions are included in the use-case – these conditions are noted in the text below.
  • Red = Technologies I would personally avoid for that use-case

USE CASE

SAP UI5

WebDynpro ABAP

Personas

Gateway*

SUP/Syclo

Process Orchestration

SAP NetWeaver Cloud

HANA

Too Complex

Use if modern HTML5 UI on many browsers and devices required that is supported by SAP.

Strength in consumption oriented scenarios with limited transactional character (stateless).

Use if you want SAPGUI robustness with tight ABAP Integration.

Strength in transactional stateful applications.

Limited touch controls but will render on most browsers.

Use if you have an existing, working transaction and want to improve its look & feel and ease of use (skip pages, carry values over, combine tabs etc) and Silverlight OK for UI

Use if you want to engage non-SAP UI developers and/or want the same UI in several technologies. If SAP support key use UI5.

Not recommended to use Gateway and WDA.

Use if you need  data sync and syndication / device security

Use if you have approval requirements prior to data hitting SAP backend

Use if you want a cloud based application that can “talks” to your on premise SAP system, if you want SAP support use UI5

Use with SLT (for near real-time replication of data from SAP ABAP) if you have data related performance issues, use UI5 as UI for SAP support

Unsupported Device

Use if modern HTML5 UI on many browsers and devices required that is supported by SAP.

Strength in consumption oriented scenarios with limited transactional character (stateless).

Avoid

Avoid

Use if you want to engage non-SAP UI developers and/or want the same UI in several technologies. If SAP support key use UI5.

Not recommended to use Gateway and WDA.

Use if you need  data sync and syndication / device security

Use if you have approval requirements prior to data hitting SAP backend, use UI5 as UI

Use if you want a cloud based application that can “talks” to your on premise SAP system, if you want SAP support use UI5

Use with SLT (for near real-time replication of data from SAP ABAP) if you have data related performance issues, use UI5 as UI for SAP support

Missing Business Logic

Use if modern HTML5 UI on many browsers and devices required that is supported by SAP.

Strength in consumption oriented scenarios with limited transactional character (stateless).

Use if you want SAPGUI robustness with tight ABAP Integration.

Strength in transactional stateful applications.

Limited touch controls but will render on most browsers.

Avoid

Use if you want to engage non-SAP UI developers and/or want the same UI in several technologies. If SAP support key use UI5. (extra logic could be in ABAP or UI devs technology).Not recommended to use Gateway and WDA.

Use if you need  data sync and syndication / device security

Use if you have approval requirements prior to data hitting SAP backend or you want additional logic in an SAP system but not in the core (SOA), use UI5 as UI

Use if you want a cloud based application that can “talks” to your on premise SAP system, if you want SAP support use UI5

Use with SLT (for near real-time replication of data from SAP ABAP) if you have data related performance issues, use UI5 as UI for SAP support

Wrong Screen Flow

Use if modern HTML5 UI on many browsers and devices required that is supported by SAP.

Strength in consumption oriented scenarios with limited transactional character (stateless).

Use if you want SAPGUI robustness with tight ABAP Integration.

Strength in transactional stateful applications.

Limited touch controls but will render on most browsers.

Use if you have an existing, working transaction and want to improve its look & feel and ease of use (skip pages, carry values over, combine tabs etc) and Silverlight OK for UI

Use if you want to engage non-SAP UI developers and/or want the same UI in several technologies. If SAP support key use UI5. (extra logic could be in ABAP or UI devs technology).Not recommended to use Gateway and WDA.

Use if you need  data sync and syndication / device security

Use if you have approval requirements prior to data hitting SAP backend or you want additional logic in an SAP system but not in the core (SOA), use UI5 as UI

Use if you want a cloud based application that can “talks” to your on premise SAP system, if you want SAP support use UI5

Use with SLT (for near real-time replication of data from SAP ABAP) if you have data related performance issues, use UI5 as UI for SAP support

*Note : I have not rated DUET Enterprise in the table above as the reason for usage would be similar to Gateway if SharePoint/Office is your only target enviornment.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply