SAP Mobility
SAP Project Fiori Launchpad Program
Provided by Customer Experience Group
Migration of SAP Fiori Apps from SAP Fiori 1.0
(based on SAP Fiori Launch Page) to SAP Fiori
Apps based on SAP Fiori Launchpad
Applicable Releases:
25 transactional apps for SAP ERP and SAP SRM that were first delivered in May 2013, and use the SAP Fiori Launch Page.
Objects Software Ltd. Business Objects is an SAP company. additional information, clarification or support, please refer to SAP Consulting.
Any software coding and/or code lines / strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.
Disclaimer
Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.
Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.
Document History
Document Version Description
Example Text Words or characters quoted
from the screen. These include field names, screen titles, pushbutton labels, menu names, menu paths, and menu options.
Cross-references to other documentation
Example text Emphasized words or phrases in body text, graphic titles, and table titles
Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation,
upgrade and database tools.
Example text User entry texts. These are
words or characters that you enter in the system exactly as they appear in the documentation.
<Example text>
Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.
EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.
Caution
Note or Important Example
Table of Contents
1. Getting Started ... 1
1.1 Prerequisites ... 1
1.2 Background ... 1
1.2.1 SAP Fiori 1.0 (based on SAP Fiori launch page) ... 1
1.2.2 SAP Fiori Principal Apps (based on SAP Fiori launchpad) ... 2
2. What’s New? ... 3
2.1 Unified Shell and SAP Fiori Launchpad ... 3
2.2 New UI Extensibility Concept ... 5
3. Migration Options ...7
3.1 Migrate the SAP Fiori 1.0 Apps to the SAP Fiori Principal App Environment ... 8
3.1.1 Installation ... 9
3.1.2 Configuration ... 9
3.1.3 Special Case: Approval Applications - Customizing...15
3.2 Migrate modified SAP Fiori 1.0 Apps to SAP Fiori Principal App Environment... 17
1.
Getting Started
This document covers migrating your SAP Fiori 1.0 apps (based on SAP Fiori launch page) to the new versions of these apps (based on SAP Fiori launchpad). The new versions of these apps are delivered with the SAP Fiori productsSAP Fiori principal apps for SAP ERP, SAP Fiori principal apps for SAP SRM, and SAP Fiori for Request Approvals 1.0.
The following chapters cover app components, the new SAP Fiori launchpad, and what you have to consider when migrating.
1.1
Prerequisites
You have an up-and-running SAP Fiori 1.0 app (based on SAP Fiori launch page) and you want to use the benefits of the new version of this apps based on SAP Fiori launchpad.
1.2
Background
This section explains the difference between SAP Fiori 1.0 apps (based on SAP Fiori launch page), and the new versions of these apps (based on SAP Fiori launchpad), called “principal apps”.
1.2.1
SAP Fiori 1.0 (based on SAP Fiori launch page)
There are 25 transactional apps for SAP ERP and SAP SRM that use the SAP Fiori launch page. These apps were first delivered in May 2013 as separate products.
The SAP Fiori launch page is a home page where users can launch applications on desktop or mobile devices. For more information,seehttp://help.sap.com/nw-uiaddon Application Help English Administration Guide Content Administration SAP Fiori Launch Page
Here the list of the official product names and product versions: My Timesheet
My Shopping Cart Track Shopping Carts My Travel Requests My Leave Requests My Paystubs My Benefits My Spend Approve Requests Approve Leave Requests Approve Shopping Carts Approve Travel Expenses Approve Travel Requests Approve Timesheets Approve Requisitions Approve Purchase Orders Check Price and Availability Create Sales Orders Change Sales Orders Track Sales Orders Track Shipments Customer Invoices
Approve Purchase Contracts Order from Requisitions Track Purchase Order
Fiori 2.0 Custom Application Migration Overview
November 2013 2
1.2.2
SAP Fiori Principal Apps (based on SAP Fiori launchpad)
As of November 2013, all SAP Fiori apps are based on the new SAP Fiori launchpad.
The 25 apps originally delivered with the SAP Fiori 1.0 (based on SAP Fiori launch page) have been redeveloped to run on the new SAP Fiori launchpad. These new app versions are delivered with the SAP Fiori productsSAP Fiori principal apps for SAP ERP, SAP Fiori principal apps for SAP SRM, and SAP Fiori for Request Approvals 1.0 .
Only the UI layer of the apps has been redeveloped. The back-end OData services used in SAP Fiori 1.0 are used for SAP Fiori principal apps as well.
SAP recommends implementing the new app versions based on the SAP Fiori launchpad. The SAP Fiori launchpad offers an enhanced set of features, and is now the standard launch environment for all SAP Fiori apps. Also, since the SAP Fiori launchpad is a shell, it provides shell services, such as navigation and personalization. Primarily, the shell is used to show tiles for SAP Fiori apps and to personalize users’ experience. Besides that, it comes with a search mechanism to allow searching for content.
For more information, seehttp://help.sap.com/nw-uiaddon Application Help English SAP Fiori Launchpad
Caution:
We do not recommend running the original apps that were designed for the SAP Fiori launch page within the new SAP Fiori launchpad until you have fully installed and customized the redeveloped SAP Fiori apps for the SAP Fiori launchpad.2. What’s New?
As of November 2013, all SAP Fiori apps come with a new SAP Fiori launchpad. Over 100 apps use the new launchpad, and the 25 apps originally delivered with the SAP Fiori 1.0 based on the SAP Fiori launch page have been redeveloped to run on the new SAP Fiori launchpad.
In the first SAP Fiori delivery in May 2013, an application template (skeleton) was only available for the approval applications. Now, all SAP Fiori Apps are based on a new standard SAP Fiori template. This template consists of a reference project and metadata, and enables, for example, integration with SAP Fiori launchpad and services such as navigation behavior.
2.1
Unified Shell and SAP Fiori Launchpad
The Unified Shell aims at harmonizing UI technologies and combining entry points. It will serve as the single entry point for end users to SAP Business Applications.
The Unified Shell is the out-of-the-box thin (html) client providing the technical environment for SAP Fiori launchpad.
SAP Fiori launchpad focuses on SAPUI5 and the Fiori experience, but it also supports fallback to different UIs, such as Web Dynpro ABAP and GUI for HTML. It offers a consistent and harmonized access point for Fiori Applications. Its capabilities and supported technologies will be extended in the future.
Image 1: Unified Shell (Web UIF and other UI technology not yet supported)
Since the SAP Fiori launchpad is a shell, it provides shell services like navigation and personalization. Primarily, the shell is used to show tiles for SAP Fiori applications and to
personalize users’ experience. Besides that, it comes with a search mechanism to allow searching for content.
Capabilities and Features
Personalization: The new SAP Fiori launchpad comes with a default home page containing predefined content depending on your role. You can then personalize your home page by adding new tiles from the tile catalog, or by grouping or deleting tiles.
Fiori 2.0 Custom Application Migration Overview
November 2013 4
Responsiveness: SAP Fiori launchpad runs on both mobile and desktop devices. Its visual design adapts automatically to the respective screen size.
Search: SAP Fiori launchpad contains a search entry field which allows you to search for business objects as well as SAP Fiori applications.
Single Sign On and Single Logout: You will be signed on to the respective system when launching content with a single sign-on mechanism. . In addition, you can log out all sessions with a single tap (mobile) / mouse click (desktop).
Theming and Branding support: The theme can be adapted with respect to the desired user experience.
Image 2 Unified Shell - Feature Highlights
Canvas supports
SAP UI5 for Fiori in first wave, now
it supports major technologies like
WebDynpro ABAP,
SAPGUI for html
Capabilities like
Search, Feeds and
Collaboration in
first wave
Others planned for
future versions
Completely role based with
one common role
definition
Stable URLs for
bookmarking and sharing
Theming and
branding
Personalization
Out-of-the-box client
supporting different
platforms
ABAP
HANA
Java
2.2
New UI Extensibility Concept
The new extensibility concept, which comes withSAP Fiori principal apps for SAP ERP, SAP Fiori principal apps for SAP SRM, and SAP Fiori for Request Approvals 1.0 allows a customer to perform modification-free extensions for some extensibility use cases. A modification-free application extension requires no modifications in the SAP-delivered standard application. This protects customer investment and also allows SAP upgrades to run without interfering with the custom application. The concept uses the extension possibilities of SAPUI5 components and JavaScript classes.
Migrating Extended Apps
The code differences the between SAP Fiori 1.0 apps (based on SAP Fiori launch page), and the new versions of these apps (based on SAP Fiori launchpad) mean that it is not possible to migrate using copy & paste between the old and the new applications. The reasons include the following:
All view files are now based on an XML structure – not HTML
New application structure with new files (such as Component.js and Configuration.js) New extensibility concept
This means that neither out-of-the-box migration nor copy & paste are possible.
Note:
If you have extended any SAP Fiori 1.0 applications, you need to recreate all your code changes for SAP Fiori launchpad using the new extensibility concept.The official extensibility documentation forSAP Fiori principal apps for SAP ERP and SAP Fiori principal apps for SAP SRM can be found here:
http://help.sap.com/fiori Extensibility Information for SAP Fiori
The extensibility concept provides a very high flexibility of extensions. However, flexibility leads to complexities. There are different extension options. You should therefore always look for specific places where SAP has enabled extension points. Check if the extension requirements can be met using one of the following options:
i18n Resource Extension View Modification View Extension
Controller Extension using a Hook
If these options cannot achieve a given requirement, the following options can be used View Replacement
Controller Extension Custom View
Use these options only as a last resort for achieving extensibility use cases. Extension Points
Each application has their respective extension points where the UI can be enhanced. For details of the extension points, see the app-specific documentation.
http://help.sap.com/fiori SAP Fiori Apps
For example, to find out the extension points for the Approve Requests app, go to:SAP Fiori Cross Apps Approve Requests App Extensibility: Approve Requests
Fiori 2.0 Custom Application Migration Overview
November 2013 6
Note:
The official SAP UI5 documentation, with code samples and API references, can be found here:3. Migration Options
If you use a SAP Fiori 1.0 apps (based on SAP Fiori launch page) landscape, there are two
mandatory steps and one optional step to migrate your system to a SAP Fiori launchpad landscape: 1. Installation (new add-ons and SAP Notes)
2. Configuration of SAP Fiori launchpad
The following step is only needed if you are using the new SAP Fiori launchpad with modified SAP Fiori 1.0 (based on SAP Fiori launch page) applications.
3. Migrate modified SAP Fiori 1.0 Apps to SAP Fiori Principal App Environment Additionally, if you use the Approval Applications, please also seeSpecial Case: Approval Applications - Customizing below.
Steps Backend (Business Suite) Frontend Server
Installation The integration add-ons from Fiori 1.0 are used for SAP Fiori principal apps as well. You need to apply the minimum support package of each add-on integration product version as described in the documentation.
Install the new UI add-ons delivered with SAP Fiori principal apps / SAP Fiori for requests approval
Configuration Configure the roles and perform the Customizing activities for all
approval apps
Configure the SAP Fiord launchpad, configure the principal apps.
Extend Application
(*) UI5/JavaScript
Post-Migration n.a. Uninstalling SAP Fiori UI Add-Ons
* Your modifications in the backend (for example, OData Service) are still working and will not be modified through the migration
Note:
You can run the old SAP Fiori launch page with the SAP Fiori 1.0 applications in parallel with the new SAP Fiori launchpad and the SAP Fiori Principal Apps (based on SAP Fiori launchpad) on the same system.This is a good interim solution which allows for step-by-step migration of old applications to the new environment without any downtime.
Fiori 2.0 Custom Application Migration Overview
November 2013 8
3.1
Migrate the SAP Fiori 1.0 Apps to the SAP Fiori
Principal App Environment
Background
You have an existing SAP Fiori 1.0 (based on SAP Fiori launch page) environment and you want to use the new SAP Fiori principal apps (based on SAP Fiori launchpad).
Solution
The new SAP Fiori principal apps (based on SAP Fiori launchpad) come as new add-ons, not as updates to old applications. The advantage of this is that you can run the SAP Fiori 1.0 applications in parallel with the new SAP Fiori principal apps (based on SAP Fiori launchpad). However, this means that the new applications will have a different URL to the old ones.
Therefore, during the setup of the SAP Fiori principal apps (based on SAP Fiori launchpad)
environment, you have to set up the new SAP Fiori launchpad with the new SAP Fiori principal apps (based on SAP Fiori launchpad) URLs – not with the URLs of the old SAP Fiori 1.0 apps (based on SAP Fiori launch page). You also have to create catalogs and new groups for the SAP Fiori principal apps (based on SAP Fiori launchpad), so that users assigned to these catalogs/groups can see it on the new SAP Fiori launchpad.
ABAP Backend Server
(ECC 600 or higher , SRM 7.00 or higher
ABAP Frontend Server
Product-specific UI Add-Ons UI for SAP Business Suite ERP
MM, SD, LE , FIN Travel HCM
UI Infrastructure
SAP Netweaver Gateway 2.0
Stable Business Suite Backend Core Component RUNTIME DESIGN TIME
HANA/ANY DB
OData Integration Add -Ons (NON-MODIFYING) per App SRM Approve Req.
Appro val SRM
3.1.1
Installation
The standard system requirements you can find here:
http://help.sap.com/fiori System Landscape Required for SAP Fiori
Here you can also find the information which add-ons you will need to install. For the new versions of the SAP Fiori 1.0 applications (based on SAP Fiori launch page), you will need these packages:
UIX01CA1 100 UIX01EAP 100 UIX01HCM 100 UIX01TRV 100 UIX01SRM 100
You can find the system requirements for each application in the application-specific
documentation. You can also find the SAP Notes which need to be applied in the same place: http://help.sap.com/fiori SAP Fiori Apps SAP Fiori Apps by Area
3.1.2
Configuration
Details about how to configure SAP Fiori principal apps can be found here: http://help.sap.com/fiori :
Configuration of SAP Fiori Infrastructure App Implementation for SAP Fiori
The SAP Fiori launchpad documentation can be found here:
For more information, seehttp://help.sap.com/nw-uiaddon Application Help English SAP Fiori Launchpad
3.1.2.1
Steps
For the new SAP Fiori launchpad, you have to perform the following configuration steps:
For Administrators
Maintaining SAP NetWeaver Gateway OData Services: The system alias of these services must point to the local system (frontend) rather than the backend system
For more information, see:http://help.sap.com/nw-uiaddon Application Help English Administration Guide Content Administration SAP Fiori Launchpad Initial Launchpad Configuration Maintaining SAP Gateway OData Services
Fiori 2.0 Custom Application Migration Overview
November 2013 10
http://help.sap.com/nw-uiaddon Application Help English Administration Guide
Content Administration SAP Fiori Launchpad Initial Launchpad Configuration Configuring Authorization Roles
To maintain the roles, you have to copy the authorizations:
http://help.sap.com/nw-uiaddon Application Help English Security Guide Authorizations
Implement SAP Note 1944725 for the authorization defaults
If you are not on SP07 or higher, please install SAP Note 1943138 to make the catalogs/groups visible on the Launchpad
Normally, if you start the Launchpad in the browser, you will see the SAP Logon Screen and not the Fiori Logon Screen. The authorization for SAP Fiori principal apps is controlled by the configuration of /sap/bc/ui5_ui5/ui2/ushell ICF node. There you must change the system logon configuration to use the user-specific /UI2/CL_SRA_LOGIN class:
PFCG Roles on the Frontend-Server (Gateway)
These roles are mandatory for Launchpad configuration!
In SAP Fiori 1.0 (based on SAP Fiori launch page), each application has a PFCG role. Now in SAP Fiori principal apps (based on SAP Fiori launchpad), each group of applications has a PFCG role. In the table below, you can see the mapping of these roles:
Application old PFCG Roles PFCG-Role for BC
Business Role PFCG-Role for TCTechnical Role
Approve Purchase Requisition SAP_APP001_MM_PR_AP R SAP_MM_BCR_Buyer_X1 SAP_MM_TCR_T_X 1 Approve Purchase Order SAP_APP002_MM_PO_A PR Approve Purchase Contract SAP_SRA001_MM_PC_AP V Track Purchase Order SAP_SRA020_MM_PO_T R Order from Requisitions SAP_SRA013_MM_PR_CR My Paystubs SAP_SRA006_HCM_PS_ MON SAP_HCM_BCR_Employee_X1 SAP_HCM_TCR_T_ X1 My Timesheets SAP_SRA002_HCM_TS_ MAN My Benefits SAP_SRA007_HCM_BEN _OVW My Leave Request SAP_HCM002_HCM_LVR Q_CR Approve Timesheets SAP_SRA010_HCM_TS_A PV SAP_HCM_BCR_Manager_X1 SAP_HCM_TCR_T_ X1 Approve Leave Requests SAP_HCM003_HCM_LVR Q_APR Approve Shopping Carts SAP_SRM001_SRM_SHO P_APR SAP_SRM_BCR_BUYER_X1 SAP_SRM_TCR_T_ X1 My Shopping Cart SAP_SRA014_SRM_SC_C R
Fiori 2.0 Custom Application Migration Overview November 2013 12 Track Shopping Carts SAP_SRA011_SRM_SC_M ON Check Price and Availability SAP_SRA016_SD_PRAV_ MON SAP_SD_BCR_FIELDSALESRE P_X1 SAP_SD_TCR_T_X1
Sales Order SAP_SRA017_SD_SO_CR Customer Invoices SAP_SRA021_SD_INV_M ON Change Sales Order SAP_SRA003_SD_SO_CH G Track Sales Order SAP_SRA018_SD_SO_MO N My Spend SAP_SRA012_CO_SPE_M ON SAP_FIN_BCR_CostManager_ X1 SAP_FIN_TCR_T_X 1 My Travel Requests SAP_SRA004_FI_TRREQ_ CR SAP_TRAVEL_BCR_EMPLOYE E_X1 SAP_TRAVEL_TCR _T_X1 Approve Travel Requests SAP_SRA009_FI_TRREQ_ AP SAP_TRAVEL_BCR_MANAGER _X1 SAP_TRAVEL_TCR _T_X1 Approve Travel Expenses SAP_SRA008_FI_TREX_A PV Track Shipments SAP_SRA019_SD_SHIP_ MON SAP_LE_BCR_TRANSPSPECIA LIST_X1 SAP_LE_TCR_T_X1
Technical catalogs (TCs) contain all target mappings and app launcher tiles relevant for an
application component (inside a software component). As an administrator, you can use them as a repository to create your own role-specific business catalogs.
Business catalogs (BCs) contain a sample collection of target mappings and app launcher tiles relevant for a business role. The content of the business catalog is a subset of the content of the technical catalog. This subset reflects the authorization requirements of a certain business user. Business catalog groups, which fill the initial screen, are filled by applications from the business catalogs. Both the business catalogs and the business groups have to be assigned to a PFCG-Business-Role, and then they can be assigned to a user.
Image 5 Roles for Fiori
For more information, see:http://help.sap.com/fiori App Implementation for SAP Fiori Implementation Information App Implementation for Transactional Apps User Management Concept Setup of Catalogs, Groups, and Roles in the Fiori Launchpad
New PFCG Roles on the backend server
In SAP Fiori 1.0 (based on SAP Fiori launch page), only a few applications come equipped with a backend PFCG Role. Now, in SAP Fiori principal apps (based on SAP Fiori launchpad), all applications come with such a role.
If you have created backend authorizations (a Z-role) in SAP Fiori 1.0 (based on SAP Fiori launch page), then a migration of these roles is not mandatory. The old roles will not overwrite the new ones. However, there are also new roles because of the naming convention which applies to SAP Fiori principal apps (based on SAP Fiori launchpad).
In the table below you can see the new PFCG backend roles:
Application New Back-End PFCG Role
Approve PurchaseRequisition SAP_MM_PR_APV_APP
Approve PurchaseOrder SAP_MM_PO_APV_APP
Approve PurchaseContract SAP_MM_PC_APV_APP
Track PurchaseOrder SAP_MM_PURORD_TPO_APP
Order from Requisitions SAP_MM_PURORD_OR_APP
My Paystubs SAP_HCM_PS_MON_APP
My Timesheets SAP_HCM_TS_CRE_APP
My Benefits SAP_HCM_BEN_MON_APP
Fiori 2.0 Custom Application Migration Overview
November 2013 14
Approve Timesheets SAP_HCM_TS_APV_APP
Approve Leave Requests SAP_HCM_LR_APV_APP Approve Shopping Carts SAP_SRM_SC_APV_APP
My Shopping Cart SAP_SRM_SC_CREATE_APP
Track Shopping Carts SAP_SRM_SC_TRACK_APP
Check Price and Availability SAP_SD_PRAV_MON_APP
SalesOrder SAP_SD_SO_CRE_APP
Customer Invoices SAP_SD_INV_MON_APP
Change Sales Order SAP_SD_SO_MAN_APP
Track Sales Order SAP_SD_SO_MON_APP
My Spend SAP_FIN_SPE_MON_APP
My Travel Requests SAP_FIN_TR_CRE_APP
Approve Travel Requests SAP_FIN_TR_APV_APP Approve Travel Expenses SAP_FIN_TE_APV_APP
Track Shipments SAP_LE_SHIP_MON_APP
Information about all SAP Fiori principal apps (based on SAP Fiori launchpad) frontend and backend roles can be found in the app-specific documentation.
Note:
For End Users:On the SAP Fiori launch page, the apps are instantly visible to the end user on the UI if the corresponding roles are assigned. Now, in SAP Fiori principal apps (based on SAP Fiori launchpad), the end user might not see the apps on the SAP Fiori launchpad by default. Instead, they probably need to manually add them to their homepage.
New Launchpad URL is
https://<host>.<domain>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap /FioriLaunchpad.html?sap-client=<client>
Note:
For Administrators:New Launchpad Designer URL is https://
<host>.<domain>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.ht ml?sap-client=<client>?scope=CUST
3.1.3
Special Case: Approval Applications - Customizing
Background
In your SAP Fiori 1.0 (based on SAP Fiori launch page) environment you used the Approval
Applications, and now you want to migrate to the new SAP Fiori principal apps (based on SAP Fiori launchpad) environment.
Solution
Be aware that for all Approval Applications, Customizing settings must be moved from the Gateway (front-end) server to the back end (SRM, ERP).
That means that you have to replicate your customizing settings on the backend for the following Approval Applications:
Approve Purchase Orders Approve Requisitions
Approve Purchase Contracts Approve Shopping Carts
This step is not needed for the following Approval Applications, because you have already done it in your SAP Fiori 1.0 (based on SAP Fiori launch page) setup:
Approve Leave Requests Approve Timesheets Approve Travel Requests Approve Travel Expenses
In SAP Fiori 1.0 (based on SAP Fiori launch page) you have customized your Approval workflow in theTask Gateway Service Scenario Definition (SPRO).
Now you have to provide the customizing settings for the Approval Applications in the backend, for which you have to enter the Task Type (i.e. for APO):
Fiori 2.0 Custom Application Migration Overview
November 2013 16
Here are the paths to all four Approval Applications for which this step is needed:
Approve Purchase Orders: Materials Management Purchase Order Approve Purchase Orders App Specify Workflow Task IDs for Approve Purchase Orders App
Approve Requisitions: Materials Management Purchasing Purchase Requisition Approve Requisitions App Specify Workflow Task IDs for Approve Requisitions App.
Approve Purchase Contracts: Materials Management Purchasing Contract Approve Purchase Contracts App Specify Workflow Task IDs for Approve Purchase Contracts App.
Approve Shopping Carts: Supplier Relationship Management SRM Server Define Task Types for Approve Shopping Carts
For more information about the new Customizing steps for Approval Applications, please see the online documentation.
For example, for Approve Purchase Orders:
http://help.sap.com/fiori SAP Fiori Apps App Documentation Structured by Area SAP Fiori Apps for SAP ERP Apps for Logistic s Material Management (MM) Approve Purchase Orders App Implementation: Approve Purchase Orders Configuration
3.2
Migrate modified SAP Fiori 1.0 Apps to SAP Fiori
Principal App Environment
Background
You have modified some of the SAP Fiori 1.0 (based on SAP Fiori launch page) applications and you want to migrate to the new SAP Fiori principal apps (based on SAP Fiori launchpad) – without losing your changes.
Solution
As described in theUI Extensibility Concept, an out-of-the-box migration isn’t possible. Please use the new Fiori extensibility concept to extend your new SAP Fiori principal apps (based on SAP Fiori launchpad).
3.3
Uninstalling SAP Fiori UI Add-Ons
You can uninstall UI add-ons in transaction SAINT. On the entry screen, there is a tab under which you can find the components available for uninstallation.
For more information about prerequisites for and about the actual process of uninstalling, see SAP Note 2034588.
www.sap.com/contactsap
