Embed Size (px)
Citation preview
© 2016 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products
and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and other
countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal
Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business
Objects products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of Business Objects Software
Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and
other Sybase products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of Sybase Inc.
Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered
trademarks of Crossgate AG in Germany and other countries. Crossgate is an
SAP company.
All other product and service names mentioned are the trademarks of their
respective companies. Data contained in this document serves informational
purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are
provided by SAP AG and its affiliated companies ("SAP Group") for
informational purposes only, without representation or warranty of any
kind, and SAP Group shall not be liable for errors or omissions with respect
to the materials. The only warranties for SAP Group products and services
How to Transport KPI Tile Application Step-by-Step Guide in S/4HANA 1610-1809 On-Premise S4H – Gateway
Ali Chalhoub
Shilpa Shankar
2
Document History
Document Version Authored By Description Date Created
1.0 Ali Chalhoub
Shilpa Shankar
First release of this whitepaper Oct 25, 2018
Document Version Reviewer Description
How to Setup a Fiori Tile Step-by-Step Using Web IDE
www.sap.com
TABLE OF CONTENTS
Document History ...................................................................................................................................................... 2
ABSTRACT .....................................................................................................................................................5
Chapter 1 – Requirement .......................................................................................................................................... 5
Chapter 2 – Creating Transports and Packages ......................................................................................................... 5
Chapter 3 – Configuring Fiori Launchpad .................................................................................................................. 5
Chapter 4 – Configuring a KPI Tile ............................................................................................................................. 5
Chapter 5 – Troubleshooting ..................................................................................................................................... 5
CHAPTER 1 INTRODUCTION ...........................................................................................................................6
Overview of the Architecture .................................................................................................................................... 6
Overview of what type of transports are needed ..................................................................................................... 8
Overview of what type of packages are needed ....................................................................................................... 9
Overview of what type of role is needed for the KPI Design ..................................................................................... 9
CHAPTER 2 CREATING TRANSPORTS AND PACKAGES................................................................................... 10
Creating Transports and Package in the Frontend system ...................................................................................... 10
Creating Transports and Package in the Backend system ....................................................................................... 17
CHAPTER 3 CONFIGURING FIORI LAUNCHPAD .............................................................................................. 26
Configuring Fiori Launchpad Designer with Transport Requests ............................................................................ 26
Creating Catalog and Group in Fiori Launchpad Designer ....................................................................................... 31
Configuring and Assigning Catalog and Group to Role ............................................................................................ 37
CHAPTER 5 CONFIGURING A KPI TILE ............................................................................................................ 44
Creating a KPI Tile .................................................................................................................................................... 44
Assigning the KPI Tile to a Group ............................................................................................................................. 60
Verify the KPI Tile is working in Fiori Launchpad ..................................................................................................... 64
Verify the App Variant and Catalog are locked in the Transport Request............................................................... 65
Transporting to Production ..................................................................................................................................... 71
4
Post Transport what other operation to-do ............................................................................................................ 71
CHAPTER 5 TROUBLESHOOTING .................................................................................................................. 73
Tile failed to display ................................................................................................................................................. 73
How to Access App Variant from the SAP Gateway frontend system? ................................................................... 73
Unspecified error when activating Evaluation ........................................................................................................ 75
5
Abstract
Chapter 1 – Requirement 1.1. Introduction
1.2. Overview of the Architecture
1.3. Overview of what type of transports are needed
1.4. Overview of what type of packages are needed
1.5. Overview of what type of role is needed for the KPI Design
Chapter 2 – Creating Transports and Packages 2.1. Creating Transports and Package in the Frontend system
2.2. Creating Transports and Package in the Backend system
2.3. Configuring Fiori Launchpad Designer with Transport Requests
Chapter 3 – Configuring Fiori Launchpad
3.1. Configuring Fiori Launchpad Designer with Transports
3.2. Creating Catalog and Group in Fiori Launchpad Designer
3.3. Configuring and Assigning Catalog and Group to Role
Chapter 4 – Configuring a KPI Tile 4.1. Creating a KPI Tile
4.2. Assigning the KPI Tile to a Group
4.3. Verify the App Variant and Catalog are locked in the Transport Request
4.4. Verify the KPI Tile is working in Fiori Launchpad
4.5. Transporting to Production
4.6. Post Transport what other operation to-do
Chapter 5 – Troubleshooting 5.1. Tile failed to display
5.2. How to Access App Variant from the SAP Gateway frontend system?
5.3. Unspecified error when activating Evaluation
6
Chapter 1 Introduction
Welcome to How to Transport KPI Tile Application Step-by-Step Guide in S/4HANA. In this white paper we will
introduce you to all the requirement needed in order to transport a KPI tile from one system to another system.
In this whitepaper we will discuss and show the user how to create and configure:
• A quick KPI tile
• What type of transports are needed
• How to configure KPI Design and Fiori Launchpad to capture the data in order to transport them to
another system
• What needs to be transported
Note
• This whitepaper covers the following versions of S/4HANA
a) 1610
b) 1709
c) 1809
Overview of the Architecture
Before we can start our configuration, we need to look at the Architecture that this whitepaper will address. This
whitepaper will cover the following scenario:
1. A development Central Hub Deployment Environment. Meaning:
a) A Gateway frontend system
b) A backend S/4HANA system
2. Transported to production Central Hub Deployment environment:
a) A Gateway frontend system
b) A backend S/4HANA system
7
Development/Quality:
Production
Frontend
GWD
S/4HANA
(Backend)
S4D RFC
TRANSPORT
Frontend
GWP
S/4HANA
(Backend)
S4P
RFC
8
Overview of what type of transports are needed
System Type/ID Environment Transport Request Description
Gateway Frontend
(GWD)
Dev/Quality
CUSTOMIZING REQUEST
Is needed to store the tile and
target mapping configuration
Gateway Frontend
(GWD)
Dev/Quality
WORKBENCH REQUEST
To store the App Variant.
What is an App Variant?
• App Variant will have
what component to
load which
represents the App
configuration of the
BSP UI5 application
• Without the App
Variant, the
application will hang
because it will not
know what todo
S4H Backend
(S4D)
Dev/Quality
CUSTOMIZING REQUEST
To store all Smart Business
Artifacts such as KPI,
Evaluation, Association.
S4H Backend
(S4D)
Dev/Quality
WORKBENCH REQUEST
• Is needed to store
the Annotation
model while
activating Evaluation
• This is needed in
order to store details
about the evaluation
such as data source
and service
• Without the
Annotation will the
KPI will not know
what to load and
hence the tile will fail
to load.
9
Overview of what type of packages are needed
• A package for the Gateway frontend system. This is required for the Workbench request
• A package for the S/4HANA backend system. This is required for the Workbench request
Summary
• We need in the frontend
a) Customization Request
b) Workbench Request
c) A package
• We need in the backend
a) Customization Request
b) Workbench Request
c) A package
Overview of what type of role is needed for the KPI Design
In order to have access to the KPI Design in Fiori Launchpad, the user must have the following role,
SAP_BR_ANALYTICS_SPECIALIST, assigned to them.
Note
• This white paper assumes the user already
a) Configured Smart Business in the system
b) Already assigned to the Administrator the appropriate
roles to have Smart Business Accessible in Fiori
Launchpad
• For more details information about how to install and configure
Smart Business Designer, refer to the following whitepaper,
https://wiki.scn.sap.com/wiki/x/9xLeGw
10
Chapter 2
Creating Transports and Packages
Creating Transports and Package in the Frontend system
The Administrator must create the transports in the frontend and backend systems before creating the
• KPI tile
• Evaluation
• Fiori Catalog
• Fiori Group
Warning
If Fiori tile, catalog and group got created before assigning the transport
request to Fiori Launchpad designer, Fiori tile, catalog, and group will not
be locked in the transport. Therefore; it is a requirement to first create all
the transport requests and assign them to Fiori Launchpad Designer and
then configure KPI tile. All this will be explained below.
Development/Quality Frontend system:
Frist we need to login to the SAP Gateway frontend system to create three things:
• Customization Request
• Workbench Request
• And a package
To do that, do the following:
1. Login to the SAP Gateway frontend system
11
2. We need to go to Transport Organizer by executing tCode SE09
Figure 1 Transport Organizer
3. Click on the New button to create a new Customizing Request as shown below in the yellow highlighted
icon
Figure 2 Creating new transport request
12
4. Select Customizing Request and click on the confirm button as shown below
Figure 3 Creating Customizing Request
5. Fill-in the required information
Figure 4 Providing request information
6. After filling the required information, click on Save
Note: Short Description it can be anything the user likes
Summary
We have created our first customization request in the SAP Gateway
frontend system that will be used when we create Fiori tile, catalog, group
and target mapping.
13
Creating Workbench Request
As we mentioned before, this is needed to store the App Variant. Without it, when the user tries to access the
application after transport, the application will not load. It will spin forever.
To create a Workbench Request, do the following:
1. Login to the SAP Gateway frontend system
2. Execute tCode SE09
3. Click on the New button as it was described in the previous section
4. Now select Workbench request
Figure 5 Creating Workbench request
14
5. Fill-in the needed information and click on Save
Figure 6 Adding Transport request information
6. Click on Display as shown below to list your transports
Figure 7 Click display to see the list of transports
15
Creating Package in the SAP Gateway frontend system
To create a package in the frontend system, do the following:
1. Execute tCode /nSE80 or SE80
2. Select Package from the dropdown list under Repository Browser
3. Enter the name of the package, in our example we are using ZSSB_APPVARIANT
Figure 8 SE80 to create package
4. If the package does not exist, a popup message will be displayed to confirm the creation of the package
Figure 9 Confirmation dialog
5. Click on Yes
6. Fill-in the required information
Figure 10 Creation of a Package
7. Click on the check button to create the package
16
8. A prompt will be displayed requesting a Workbench request to be specified. Click on the Own Requests
Figure 11 Providing a Workbench request
9. Select the same Workbench request that we have created previously to store the App Variant as shown
below and click on the green check icon:
Figure 12 List of Transports
10. Once the Workbench requested has been selected, click on OK as shown below:
Figure 13 Package creation
17
11. Now we have our package in the SAP Gateway frontend system
Figure 14 Displaying package in SE80
Creating Transports and Package in the Backend system
Now that we have created the Customization Request and workbench in the frontend, we need to create the
Customization and Workbench Request in the backend.
Development/Quality Backend system:
We need to login to the S/4HANA backend system to create three things:
• Customization Request
• Workbench Request
• And a package
Creating Customization Request
To do that, do the following:
1. Login to S/4H backend system
18
2. We need to go Transport Organizer by executing tCode SE09
Figure 15 Transport Organizer
3. Click on the New button to create a new Customizing Request as shown below in the yellow highlighted
icon
Figure 16 Creating a new Transport request
19
4. Select Customizing Request and click on the confirm button as shown below
Figure 17 Creating Customizing Request
5. Fill-in the required information
Figure 18 Creation of Request
6. After filling the information, click on Save button.
Note: Short Description it can be anything the user likes
Summary
We have created our first customization request in the S/4HANA backend
system that will be used when we create and activate the KPI.
20
Creating Workbench Request
As we mentioned before, this is needed to store the Annotation model while activating the Evaluation.
To create a Workbench Request, do the following:
1. Login to the S/4HANA backend system
2. Execute tCode SE09
3. Click on the New button as it was described in the previous section
4. Now select Workbench request
5. Fill-in the required information
Figure 19 Creating Transport Request for Annotation
21
6. Click on Save
7. Click on Display to list the Transports that got created so far, the following is displayed
Figure 20 Displaying the list of Transports
8. The following display, lists the two transport requests that got created
Figure 21 List of Transports
22
Creating Package in the SAP S/4HANA backend system
To create a package in the backend system, do the following:
1. Execute tCode /nSE80 or SE80
2. Select Package from the dropdown list under Repository Browser
3. Enter the name of the package, in our example we are using ZSSB_ANNOTATION
Figure 22 Creating Package in the backend
4. If the package does not exist, a popup message will be displayed to confirm the creation of the package
Figure 23 Confirmation dialog
23
5. Click on Yes
Figure 24 Providing Package information
6. Click on the check button to create the package
7. A prompt will be displayed requesting a Workbench request to be specified. Click on the Own Requests
Figure 25 Prompt for Workbench Request
24
8. Select the Workbench Request Annotation that got created in the previous steps and click on the green
check icon as shown below:
Figure 26 Selecting Workbench Request
9. Once the Workbench requested has been selected, click on green check icon as shown below:
Figure 27 Assigning a Workbench Request
25
10. Now we have our package in the SAP S/4HANA backend system
Figure 28 SE80 displaying package
By now we should have three things created in each system
• Two transport Requests and one package in the frontend
• Two transport Requests and one package in the backend
Next step is to configure Fiori Launchpad before we start creating the KPI.
26
Chapter 3 Configuring Fiori Launchpad
In this chapter we will focus on how to configure Fiori Launchpad Designer in order to lock tile, catalog, group,
and App Variant into the transports.
Configuring Fiori Launchpad Designer with Transport Requests
There two things we need to do here:
1. Configure Fiori Launchpad Designer at the CONF layer in order to store the App Variant information
2. Second configure Fiori Launchpad Designer at the CUST layer in order to store catalog, tile and group
information
Configuring Fiori Launchpad Designer with CONF Layer
1. Login to Fiori Launchpad Designer using Chrome or IE and type the following URL:
HTTP(S)://<HOST>:<PORT>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?scope=CONF&sap-
language=EN
Note: Make sure in the URL you have scope=CONF
CONF is a case sensitive, so it has to be upper case.
2. To confirm the user is logged in to CONF layer, the following indication should be displayed on the on
the top right of the browser:
Figure 29 Scope is CONF in Fiori Launchpad Designer
27
3. Click on Settings as shown below
Figure 30 Opening Settings window
4. Select the Workbench of the SAP Gateway frontend system as shown below:
Note: Your screen may be different than ours if you have more than one Workbench request
Figure 31 Assign Transport
28
5. After selecting the Workbench request that we have created previously, click on OK
6. Next, we need to provide the package name that we have created in the SAP Gateway frontend system
as shown below:
Figure 32 Assigning Workbench Request
7. We are done with the CONF layer
Configuring Fiori Launchpad Designer with CUST Layer
Now that we have configured Fiori Launchpad Designer under the CONF layer with a Workbench request, next
we need to configure Fiori Launchpad Designer with the Customization Request. To do that, do the following:
1. Login to Fiori Launchpad Designer using Chrome or IE and type the following URL:
HTTP(S)://<HOST>:<PORT>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?scope=CUST&sap-
language=EN
29
Note: Make sure in the URL you have scope=CUST
2. Once logged in, the client number will be displayed on the top right of the Fiori Launchpad Designer as
shown below:
Figure 33 Scope is CUST in Fori Launchpad Designer
Note: If the user still see Client:All still showing, that means you are still logged in to the CONF layer.
3. Once logged in to the CUST layer, click on settings as shown below:
Figure 34 Accessing Settings information
4. By default None(Local Object) is selected as shown below:
Figure 35 Assigning a Transport
30
5. We need to uncheck it and select our SAP Gateway Frontend Customization Request as shown below:
Figure 36 Selecting Customizing Request
6. Once the Customization Request is selected, click on OK
Figure 37 Assigning Customizing Transport Request
31
Creating Catalog and Group in Fiori Launchpad Designer Now that we Fiori Launchpad Designer is configured with our transports on both layers, we need to create few
things:
1. First the Catalog where we are going to store our Fiori KPI Tile
2. Second the Group that is going to display our KPI Tile
Creating Fiori Catalog
1. Login to Fiori Launchpad Designer under the CUST layer
2. Click on the Catalogs tab as shown below:
Figure 38 Creating Fiori Catalog
32
3. Click on the + icon as shown below to create a catalog
Figure 39 Adding a Catalog
33
4. Fill-in the needed information by providing the catalog name and an ID
Figure 40 Creation of Catalog Note: Make sure the ID is unique in your system.
34
5. Click on Save
6. Now we have a catalog created in our Fiori Launchpad Designer as shown below:
Figure 41 Catalog has been created
Creating Fiori Group
Now that we have a catalog to hold our tile, next we need to create a group that will display our tile in Fiori
Launchpad
To create a group, do the following:
1. In Fiori Launchpad Designer under the CUST layer, click on the Group tab
Figure 42 Creation of Fiori Group
35
2. Next click on the + sign on the bottom to create a Group
Figure 43 Creation of Fiori Group
36
3. Fill-in the required information. For example, our Group is called SS KPI Group
Figure 44 Saving Group information
4. Click on Save
5. Now we have a Group created as shown below:
Figure 45 Displaying Group
37
Configuring and Assigning Catalog and Group to Role
Now that we have a Catalog and Group created, next we need to create a Role or use an existing Role and assign
the Catalog and Group to this Role and finally assign it to the user who wants to access this Catalog and Group.
To create a Role, do the following:
1. Login to SAP Gateway frontend system
2. Execute tCode /nPFCG or PFCG
3. Enter the name of the Role you want to create or if there is one already exist, you can provide it there
and click on the display icon. In our example, we are creating new one. Our Role name is ZSSB_KPI
Figure 46 Creating Role in PFCG
4. Click on Single Role
5. Fill-in the information by providing a description to the Role and click on Menu
Figure 47 Accessing Menu of the Role
38
6. The system will ask you to save the Role. Click on Save
Figure 48 Saving the Role
7. Under Menu now click on the dropdown list and select SAP Fiori Tile Catalog as shown below:
Figure 49 Assigning Fiori Tile Catalog to a Role
8. Enter the Catalog ID not the Catalog name from the previous step and click the green check button:
Figure 50 Adding SSB_KPI Catalog
39
9. If the following warning message is displayed, just click on Cancel
Figure 51 Warning message
10. Now the Catalog is assigned to the Role
Figure 52 Catalog assignment
40
11. Click on the Menu again so we can select the Group to add
Figure 53 Assigning Fiori Group
12. Enter the Group ID as shown below and click on the green check icon
Figure 54 Assigning Group ID
41
13. Now we should have the following:
Figure 55 Adding Group to the user menu
42
14. Finally, we need to assign this Role to our User ID. Click on the User Tab
15. Assign your User ID and click on Save as shown below:
Figure 56 Assigning a Role to a user
16. Note: For Smart Business you do not need S_SCOPE Authorization Object. This can be deactivated.
a. Go to Authorizations tab in edit mode
43
b. Click on Expert Mode for Profile Generation
Figure 57 Expert Mode for Profile Generation
c. Expand the Authorizations. Select S_SCOPE. Click on Deactivate as shown below:
Figure 58 Deactivate S_SCOPE
d. Save the changes and generate the profile
44
Chapter 4 Configuring a KPI Tile
Now that we prepared our system and created all the transports that are required as well as the Catalog, Group
and Role, we are now ready to create our KPI tile
Creating a KPI Tile
To create a KPI Tile, we need to do the following:
1. Login to Fiori Launchpad
2. Click on KPI Design Group
Note: If the KPI Design Group cannot be shown, check and verify of the Role,
SAP_BR_ANALYTICS_SPECIALIST , is assigned to your user ID
3. Click on Create KPI Tile as shown below:
Figure 59 Accessing Create KPI Tile
45
4. KPI creation dialog is displayed, enter the following information or if you have your own specific
information:
Figure 60 Configuring the KPI Tile
5. Scroll down in the KPI screen to the Data Source section as shown below:
Figure 61 Configuring Data Source
46
6. Fill-in the required information as shown below starting with the CDS View first:
Figure 62 Adding CDS View and OData Service
7. Click on Activate and Add Evaluation as shown below:
Figure 63 Activating KPI and creating an Evaluation
8. Now we need provide our SAP S/4HANA Customization Request that we have created in the backend:
Figure 64 Assigning a Customization Request
47
9. Click on the Customizing Request dropdown list and select the Customization Request from the backend
Figure 65 Selecting a Customizing Request
10. Now click on OK
Figure 66 Confirming the assignment
48
11. Now the KPI has been created and Activated. Next, we need to create an Activate the Evaluation. Enter
the Evaluation information
Figure 67 Creating an Evaluation
12. Now that we have provided the Evaluation information, click on Activate and Configure Tile as shown
below:
Figure 68 Activating the Evaluation and Creating a Tile
49
13. The user will be presented now with a dialog to provide the Workbench Request from the SAP S/4HANA
backend system
Figure 69 Selecting a Workbench Request
14. Enter the information as follows assuming your Workbench Request and Package are the same names
as the one in this whitepaper
Figure 70 Saving the Transport information
50
15. Click OK
16. While the system is creating and activating the Evaluation, you can login to the backend S/4HANA
system and check what got written to the transport requests as shown below:
Figure 71 Viewing the Transport lists
51
17. Back to Fiori Launchpad, we should see the following screen after the activation of the Evaluation:
Figure 72 Configuring KPI Fiori Tile
52
18. First, we need to assign the KPI Tile that we are about to create to a Catalog, click on the Value Help
beside the Catalog field as shown below:
Figure 73 Selecting a Catalog
53
19. Select the Catalog we have created previously
Figure 74 Selecting Fiori Catalog
20. Once the Catalog has been selected, we should see the following screen:
Figure 75 Catalog assigned
54
21. Accepting the default of the Navigation section, click on Save and Configure Drill-Down as shown
below:
Figure 76 Saving and configuring Drill-Down
55
22. We are now in the Drill-Down Configuration Details. Click on Configure and make sure your Evaluation is
selected as shown below:
Figure 77 Drill-Down created
56
23. Select your Dimension. In our example we are selecting Purchase Order and PO Item
Figure 78 Selecting Dimension
57
24. Next Select a Measure as shown below and click on OK
Figure 79 Selecting Measure
58
25. Now configure you Chart Type as shown below:
Figure 80 Configuring Drill-Down View
26. Click OK
27. Now click on Save Configuration as shown below:
Figure 81 Saving the Drill-Down configuration Note: If the SAP S/4HANA has backend data, it will be displayed, otherwise, it will show no data.
59
28. If everything works successfully, we should see the following screen below:
Figure 82 Drill-Down details
60
Assigning the KPI Tile to a Group
Now the KPI and Evaluation has been created and the Fiori Tile has been configured. It is time now to add the
KPI Tile to our Group that we have created from before. To do that, do the following:
1. Login back to Fiori Launchpad Designer CUST layer. By default, if not scope is provided in the URL, it will
log you into the CUST layer
2. Select the Catalog we have created before as shown below. Notice our KPI Tile is now available in the
Catalog
Figure 83 Verifying the Tile in the Catalog
3. Click on the Target Mapping
Figure 84 Accessing Target Mapping
61
4. Select the Target Mapping PurchaseOrderOverdue and click on the Configure as shown below:
Figure 85 Accessing the Configuration of the Target Mapping
62
5. Here we will get access to the Semantic Object and application ID. We are interested in making a copy of
the ID under the Target section as shown below.
Figure 86 Accessing the Application Target ID
6. Make copy of the ID because we need it later because this ID represents the App. Variant
7. Next we need to click on the Group to add our Tile as shown below:
Figure 87 Accessing Fiori Group
63
8. Click on the + sign on the right under Show as Tiles:
Figure 88 Adding the Tile to the Group
9. Select your SS KPI Catalog as shown below and click on the + sign to add it to the group
Figure 89 Accessing the Catalog in order to access the Tile
64
10. Tile has been added to the Group:
Figure 90 Tile has been added to the Group
Verify the KPI Tile is working in Fiori Launchpad
1. Login to Fiori Launchpad
2. Look for the Group SSB KPI Group
3. You should see the following:
Figure 91 Fiori Launchpad
65
4. Click on the Tile
5. We should see the following:
Figure 92 Fiori KPI Tile
Verify the App Variant and Catalog are locked in the Transport Request
Now that the tiles and catalogs all configured, let confirm this by login into the SAP Gateway System frontend
system.
1. Login to SAP Gateway frontend system
2. Execute tCode SE09
Figure 93 Transport Organizer
66
3. Click on Display. As we can see below, our configuration is locked in the transport
Figure 94 List of Transports
67
4. Next we need to verify if everything is logged in the App. Variant. Open your Web Browser
5. Enter the following URL
HTTP(S)://<HOST>:<PORT>/sap/public/bc/ui5_ui5/resources/sap/ui/fl/support/apps/contentbrowser/in
dex.html?#
6. The following LREP will be displayed. Click on the CUSTOMER layer
Figure 95 LREP Layers
68
7. Click on app
Figure 96 Accessing apps under the LREP layer
8. Search for Smart in the search box
Figure 97 Accessing Smart Business layer
69
9. Click on AppVariants
Figure 98 Accessing AppVariants
10. Search for the App Variant that we copied from before under the section “Assigning the KPI Tile to a
Group” as shown below:
Figure 99 Customer appVariants
70
11. Click on the AppVariant, customer.kxxxx
Figure 100 Accessing the manifest
12. Click on manifest. We will see all the configuration about the KPI tile
Figure 101 Displaying the content of the manifest
Note: In the manifest we can see all the details about what Annotation and what is the AppVariant that
is needed in order to load the tile
13. If we click on the Metadata icon as shown below, we can see all the details about if the AppVariant is
recorded in the transport and which layer it is. As we can see below it is CUSTOMER layer which is what
71
we are looking for in regard to custom KPI Tile:
Figure 102 Checking the Metadata
Transporting to Production
Now that everything is confirmed and configured. We are ready to Transport to production from Dev or Quality.
Your BASIS Administrator needs to transport the following:
• From the SAP Gateway frontend System:
o The Customization Request
o The Workbench Request
o PFCG role that holds the Fiori Catalog and Groups needs to be transported as well
For example in this white paper we used ZSSB_KPI role. This role needs to be transported.
• From the SAP S/4HANA backend system
o The Customization Request
o The Workbench Request
Post Transport what other operation to-do
72
After the transport is successfully done to production, the user should be able to access the Tile through the
same Group and Catalog. If the user experienced hanging problem or the Title is not displayed, or the Tile failed
to load, check the Troubleshooting Chapter for the resolution.
73
Chapter 5 Troubleshooting
Tile failed to display
After transporting the Tile failed to load.
Resolution:
If the tile failed to display after transport, then do the following:
1. In the destination and in the frontend, execute tCode SE38
2. Execute the following report: /UI2/INVALIDATE_GLOBAL_CACHES
3. Execute the following report: /UI5/APP_INDEX_CALCULATE
4. Select Single SAPUI5 Repository Only
5. Enter the SAPUI5 Repository application name for Smart Business it is sbrt_appss1
6. Execute
7. SAP Smart Business tile should be displayed
For more information , refer to the following KBA: 2662463 - KPI activation fails when transport request is used
How to Access App Variant from the SAP Gateway frontend system?
If the user is not able to access the LREPk through the browser in order to access the App. Variant, then follow
the resolution section below:
Resolution:
1. Login to SAP Gateway frontend system
2. Execute tCode SE38
3. Under Program type /UIF/GET_FILES_4_NS
4. Click Execute
74
5. Under the Namespace type the App Variant ID as shown below surrounded by *
Figure 103 AppVarient through report
6. Click on Execute
7. We should see the following two records with Layer Type says CUSTOMER
Figure 104 List of AppVariant
8. If we need to display the content, we will highlight the record with CUSTOMER layer type and click on
display content as shown below:
Figure 105 Accessing the content
75
9. User can see the content:
Figure 106 Displaying the content of manifest
Unspecified error when activating Evaluation
After creating a KPI successfully, an error is generated when activating the Evaluation:
ERROR_INFO Unspecified error occurred. See Error Context and Call Stack for details
Resolution:
Please refer to the following KBA: 2537540 - Unspecified error when activating Evaluation
