
If we go back to year 2007 the SAP UI word had simply related to SAP GUI. Since then the SAP UI has evolved into Web UI which is an essential part of their business suite products (SRM, CRM, PLM, SCM).
SAP User Experience initiative known as SAP UX also came into play while SAP revised it’s UI strategy in year 2011. This strategy addresses simplifying UI at one end while making custom UI development easier for its customers.
From the end user perspective, SRM UI that comes with SRM core release is still considered complex due to many elements or fields. SAP addressed this problem by providing SAP SRM UI 1.0, a simplified shopping UI which is best suited for casual users. This new UI is developed using ABAP add-on and HTML5 as a base technology.
For SRM 7.0 this new add-on level delivery does make sense as it provides new user interaction without disrupting the underlying business application.
We will have to start understanding the UI evolution to start with SAP GUI. For consultants with MM background its very easy to observe the new Enjoy UI (ME23n) that was delivered with ME23n which can be accessed in SAP R3 4.6 onwards. It was a classic example of decoupling the UI development from Business Application.
This decoupling UI trend went into the technical concept of decoupling the Dynpro business logic from the UI logic of the app using web HTML technology - so the SAP Internet Transaction Server (ITS) was developed. The main purpose of ITS was to transform the SAP GUI to Web UI.
SAP Web Dynpro as propriety framework was the next development for integrated Web UI development. SRM 7.0 (SRM core) has UI Logic developed in WebDynpro ABAP.
Today the need is more to connect devices, environment and platforms to SAP system. To Achive this SAP has delivered new technology called NetWeaver Gateway. This framework specifically targets decoupling data from SAP backend systems and enabling easier consumption based on OData.
Then comes the SAP UI Add-on built on top of the Gateway infrastructure as an SAP UI package of specific components, while being decoupled from the backend of the application.
SAP FLORI is recent development, these are ready to use application suites available from SAP. There are more than 5 SRM ready to use UI apps available in SRM EHP 3 (SRM 7.03)
SRM UI 1.0 is the simplified shopping UI available through series of UI components as shown in the simple architecture diagram below:
SAP NetWeaver Gateway offers connectivity to SAP applications using any programming language or model without the need for SAP knowledge by leveraging REST services and OData/ATOM protocols.
The following shopping cart features are in scope for SAP SRM User Interface Add-on 1.0:
SRM UI 1.0 | SRM UI 1.0 SP03 onwards | SRM UI 1.0 SP05 onwards |
|
|
|
Key steps for SRM UI 1.0 set up are as follows:
1) Install SAP NetWeaver Gateway on SRM server, Set up local connectivity, Activate the Gateway services for SRM UI Add-on,
2) Assign SRM UI 1.0 specific role (e.g. /SRMNXP/EMPLOYEE)
3) Business Configuratoin: Setting up of number ranges for temporary shopping carts
4) Activate UI5 service in transaction SICF
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.