Configuring SAP GUI Transaction in Fiori Launchpad
SAP Fiori applies modern design ideas to deliver a consistent and holistic user experience (UX) for SAP products. The SAP Fiori UX is used to create a customised, responsive, and simple user experience in SAP systems.
However, not all standard applications have yet been moved to Fiori, and it will be some time before all Apps are available in the Fiori Library.
SAP has built a provision to setup these applications on the Fiori Launchpad to give a consistent user experience and a common entry point to launch any standard or bespoke applications.
The procedures below will help any application developer complete system verification before creating any Fiori app, understand the prerequisites for setting up Fiori apps, and configure any normal SAP GUI transaction in the Fiori launchpad when standard Apps are not accessible.
Did you know that every SAPUI5 app that follows the 5 Fiori principles qualifies as a Fiori app rather than a UI5 app? In the post below, you'll find five principles to consider.
Design Principles for Fiori Apps
A step-by-step guide on setting basic Fiori Launchpad transactions.
Verification of the System
Before we can build individual Apps, we must first set up the SAP Fiori System Landscape and configure the SAP Fiori Infrastructure.
SAP Fiori can be used with Business Suite (any DB or HANA) and S/4HANA, therefore check if the following components are installed in your landscape, depending on your system instance and deployment options.
Front-end components (which provide the user interface and connect to the back end) and back-end components are required for SAP Fiori apps (providing the data).
Both the front-end and back-end components are offered as distinct products and must be installed in the SAP Fiori-enabled system landscape.
| Deployment Option | Development | SAP NetWeaver Release | Installed in SAP Gateway Hub | Installed in SAP Business Suite / S4 |
| Embedded | SAP Business Suite Backend System | 7.0, 7.01, 7.02, 7.03, 7.31 | – | IW_FND GW_CORE IW_BEP |
| 7.40 or 7.50 and higher | SAP_GWFND | SAP_GWFND | ||
| Central Hub | SAP Business Suite Backend System | 7.0, 7.01, 7.02, 7.03, 7.31 | IW_FND GW_CORE | IW_BEP |
| 7.40 or 7.50 and higher | SAP_GWFND | SAP_GWFND | ||
| SAP Gateway System | 7.0, 7.01, 7.02, 7.03, 7.31 | IW_FND GW_CORE IW_BEP | You can combine this deployment scenario with an installation of IW_BEP in the backend system. | |
| 7.40 or 7.50 and higher | SAP_GWFND | SAP_GWFND |
Because NetWeaver version 7.4 does not have a separate front-end server, this is an embedded instance (no separate front-end server). The “SAP GWFND” component is present on the back end system, which is where the development and gateway registration takes place.
Note that because we are setting a basic GUI transaction, no further UI components are necessary; otherwise, we must use the Fiori library to install front end UI components.
Also see Part I of the SAP Fiori Tutorial: System Check, Installation, and Configuration.
Embedded Deployment Tasks List (Configure SAP Gateway and SAP Fiori on the same client where the ERP system is located.)
Basic Configuration of SAP Gateway (SAP GATEWAY BASIC CONFIG)
(Choose UI Technologies -> SAP Fiori Initial Setup -> Connection Settings (Front-End Server to ABAP Back-End Server) -> Activate SAP Gateway in Customizing for SAP NetWeaver.
Configure Fiori Launchpad (SAP FIORI LAUNCHPAD INIT SETUP).
The SAP Fiori launchpad is a desktop and mobile device access point for SAP Fiori apps. The SAP Fiori launchpad must be configured so that users can access the apps that have been assigned to their roles.
To get the SAP Fiori launchpad and the SAP Fiori launchpad designer up and running, you'll need to activate the OData and ICF services.
SAP Gateway – Activate OData Services (SAP_GATEWAY_ACTIVATE_ODATA_SERV)
Register the following services in the transaction "/n/IWFND/MAINT SERVICE."
- /UI2/PAGE_BUILDER_CONF
- /UI2/PAGE_BUILDER_PERS
- /UI2/PAGE_BUILDER_CUST
- /UI2/INTEROP
- /UI2/TRANSPORT
We can also maintain any other services.
Check out the SAP Fiori Tutorial as well. Part II: Fiori App Implementation from Start to Finish
SAP Basis – Activate HTTP Services (SICF) (SAP_BASIS_ACTIVATE_ICF_NODES)
Maintain Services by running the transaction (SICF). Activate the services under the following sub trees in the menu under -> Service/host -> Activate:
To activate all child nodes under a service, select Yes with the hierarchy symbol in the Activation of ICF Services dialogue box.
- /DEFAULT HOST/SAP/BC/UI2/NWBC/ – NetWeaver Business Client
- /DEFAULT_HOST/SAP/BC/UI2/START_UP – Provides data that is needed at frontend shell start-up
- /DEFAULT_HOST/SAP/BC/UI5_UI5/SAP/AR_SRVC_LAUNCH – Launch tile application
- /DEFAULT_HOST/SAP/BC/UI5_UI5/SAP/AR_SRVC_NEWS – News tile application
- /DEFAULT_HOST/SAP/BC/UI5_UI5/SAP/ARSRVC_UPB_ADMN – Unified Shell Page Builder Administration Page
- /DEFAULT_HOST/SAP/BC/UI5_UI5/UI2/USHELL – Unified Shell
- /DEFAULT_HOST/SAP/PUBLIC/BC/UI2 – Entry Point for UI2 Services
- /DEFAULT_HOST/SAP/PUBLIC/BC/UI5_UI5 – SAPUI5 library called via HTTP out of MIME repository
How to set up a Fiori Launchpad GUI transaction
Check to see if the Fiori library has any standard Apps. If the standard App is available, setup it; otherwise, proceed to the instructions below.
In this case, as the GUI transaction is being configured for a Business Suite system on a non-HANA DB, check to see if any Apps for transaction ‘MM01' exist under “Fiori apps for Business Suite.”
Create a Semantic Object to identify the Application
Navigate to transaction /n/UI2/SEMOBJ_SAP to create a semantic object.
To create a Launchpad role, go to transaction "LPD CUST." This is necessary in order to keep target mapping in the next stage.
Multiple Applications can be connected with a single Launchpad Role (1:N).
(For example, this job can be linked to multiple transactions, each with its own application alias.)
Create a Catalog in Fiori Launchpad Designer.
Make sure to assign it to a transport request.
Add a Tile and specify the Target Mapping.
Because we aren't using an Analytical App, choose Static Tile.
As indicated below, specify the Tile specifics.
Specify the Tile's Target Mapping.
When the user clicks on the tile, this is required to launch the proper programme.
Create a Group to include the Tile.
In the PFCG transaction, create a new role and assign Catalog and Group to the business user.
Assign the User a Role
Finally, in Fiori Launchpad, you can see the Standard Transaction. You can now run your App and enjoy the Fiori App's user experience.
Important: Not all SAP Transactions can be translated to the SAP Fiori App at this time. A requirement for exposing a standard SAP T-Code using Fiori Launchpad is that the transaction has SAPGUI for HTML enabled. T-code SE93 can be used to check this.
The t-code for our case is MM01. Go to t-code SE93, enter MM01 as the transaction code, then press show.
On mobile or desktop devices, SAP Fiori Launchpad is the entry point to Fiori Apps. However, not all conventional apps or transactions are now available in the Fiori library, thus some users may need to utilise SAP to access both new Fiori apps (through launchpad) and old GUI operations (via back end). When we have to transition from a mobile device to a desktop to access GUI-based transactions, this can be inefficient. Traditional GUI transactions can be implemented in Fiori launchpad to provide a single entry point to access all SAP apps, whether from mobile or desktop devices, to solve this. The look and feel would be quite similar to Fiori apps for GUI transactions in this situation, but they are not transformed to Fiori apps and continue to function as transitional GUI based transactions.
No comments:
Post a Comment