How to setup My Inbox 2.

0
app
UI for Cross Applications 2.0 SP06

Joaquin Fornas © 2018 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP

Konstantia Zerva-Spanou 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
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be
construed as constituting an additional warranty.
Document History

Document Version Authored By Description Date Created

1.0 Joaquin Fornas Fiori White Paper January 16, 2017

1.0 Konstantia Zerva-Spanou Fiori White Paper January 16, 2017

1.0 Ali Chalhoub Fiori White Paper January 16, 2017

1.1 Joaquin Fornas Small fixes March 21, 2017

1.2 Joaquin Fornas Update to SP06 December 19, 2018

Document Version Reviewer Description Date Created

1.0 Bruno Pietrantonio Review Documentation January 29, 2017

2.0 Bruno Pietrantonio Review Update December 19, 2018

2
How to Setup My Inbox 2.0
www.sap.com

TABLE OF CONTENTS

Document History ...................................................................................................................................................... 2

ABSTRACT .....................................................................................................................................................5
Chapter 1 – Configuring UI for Cross Applications .................................................................................................... 5
Chapter 2 – Creating Inbox Specific System Alias ...................................................................................................... 5
Chapter 3 - Activating and testing OData Service...................................................................................................... 5
Chapter 4 – Activating UI5 Service ............................................................................................................................ 5
Chapter 5 – Activating the Task Filter ........................................................................................................................ 5
Chapter 6 – Workflow Customizing ........................................................................................................................... 5
Chapter 7 – Customizing Task Names........................................................................................................................ 5
Chapter 8 – Defining Gateway Scenario .................................................................................................................... 5
Chapter 9 – Create a Tile for the Task Definition Scenario........................................................................................ 5
CHAPTER 1 CONFIGURING UI FOR CROSS APPLICATIONS ................................................................................6
Installing MyInbox 2.0 app ........................................................................................................................................ 6
IW_PGW 100 ........................................................................................................................................................... 10
Component IW_PGW 100 will be out of maintenance as of 31.12.2025 ................................................................ 11
CHAPTER 2 CREATING INBOX SPECIFIC SYSTEM ALIAS .................................................................................. 12
Creating the new SAP System Alias ......................................................................................................................... 12
CHAPTER 3 ACTIVATING AND TESTING ODATA SERVICE ............................................................................... 14
Service TASKPROCESSING ........................................................................................................................................ 14
Adding TASKPROCESSING to the Gateway .............................................................................................................. 14
Change the system alias for service TASKPROCESSING version 2 ........................................................................... 16
Check the system alias and user consistency .......................................................................................................... 17
CHAPTER 4 ACTIVATING UI5 SERVICE ........................................................................................................... 19
Transaction SICF ...................................................................................................................................................... 19
Activating service CA_FIORI_INBOX ........................................................................................................................ 19
Testing Service URL.................................................................................................................................................. 21
Creating Business Role............................................................................................................................................. 22
CHAPTER 5 ACTIVATING THE TASK FILTER ..................................................................................................... 25
Task Filter................................................................................................................................................................. 25
Customizing the Task Filter...................................................................................................................................... 25
CHAPTER 6 WORKFLOW CUSTOMIZING ........................................................................................................ 27
Automatic Workflow Customizing ........................................................................................................................... 27
Assigning agents to the tasks................................................................................................................................... 29
Testing the workflow ............................................................................................................................................... 34
CHAPTER 7 CUSTOMIZING TASK NAMES ....................................................................................................... 36
Maintain Task Names .............................................................................................................................................. 36
Customizing the Decision Keys ................................................................................................................................ 38
CHAPTER 8 .................................................................................................................................................. 40
DEFINING GATEWAY SCENARIO ................................................................................................................... 40
Scenarios.................................................................................................................................................................. 40
Customizing the Scenario ........................................................................................................................................ 40
Task Definition for Scenario..................................................................................................................................... 41
CHAPTER 9 CREATING A TILE FOR THE TASK DEFINITION SCENARIO ............................................................... 43
Creating a Catalog in the Launchpad Designer ........................................................................................................ 43
Creating a new dynamic tile .................................................................................................................................... 48
Assigning the catalog to a user ................................................................................................................................ 49
Creating a group and assigning it to the user .......................................................................................................... 52
Final Result .............................................................................................................................................................. 57
My Inbox 2.0 User Icon ............................................................................................................................................ 59

4
Abstract
Chapter 1 – Configuring UI for Cross Applications
1.1. Configuring the connection to the NetWeaver Gateway server
1.2. Creating a user
1.3. Creating a role
1.4. Assign the user to a role

Chapter 2 – Creating Inbox Specific System Alias

2.1. Creating the new SAP System Alias

Chapter 3 - Activating and testing OData Service

3.1 Service TASKPROCESSING
3.2 Adding TASKPROCESSING to the Gateway
3.3 Linking Technical Service to System Alias
3.4 Check the system alias and user consistency

Chapter 4 – Activating UI5 Service

4.1. Transaction SICF
4.2. Activating service CA_FIORI_INBOX
4.3. Service URL

Chapter 5 – Activating the Task Filter

5.1. Task Filter
5.2. Customizing the Task Filter

Chapter 6 – Workflow Customizing

6.1 Automatic Workflow Customizing
6.2 Assigning Agents to the Tasks
6.3 Testing the Workflow

Chapter 7 – Customizing Task Names

7.1 Maintain Task Names
7.2 Customizing the Decision Keys

Chapter 8 – Defining Gateway Scenario

8.1 Scenarios
8.2 Customizing the Scenario
8.3 Task Definition for Scenario

Chapter 9 – Create a Tile for the Task Definition Scenario

9.1 Creating a Catalog in the Launchpad Designer
9.2 Creating a new dynamic tile
9.3 Assigning the catalog to a user
9.4 Creating a group and assigning it to the user
9.5 Final Result
9.6 My Inbox 2.0 User Icon

5
 Chapter 1
Configuring UI for Cross Applications

This document contains all the information you’ll need to install Fiori app My Inbox 2.0 and adding
a tile to your Fiori Launchpad.

• This document will relate to a Frontend (NetWeaver Gateway system 7.50) and
Note a Backend S4HANA system. For each step, it is specified if the action should be
performed on the Frontend or in the Backend.

• Install and configure NetWeaver 7.5 or higher. NetWeaver 7.5 already comes
with SAP Gateway, SAP_GWFND 7.5, and SAP_UI 7.5
Requirement • Windows 7, 8.1, or 10 for development and configuration
• Install the SAP Logon utility.
• Having a Fiori Launchpad properly configured.

Installing MyInbox 2.0 app

The main Software Component for My Inbox 2.0 is UI for Cross Applications (200 SAPK-
200AGINUIX01CA1). These components are installed in the Front-End.
The following instances contain UI for Cross Applications Software component:
Name of Object Name of Activated Instance
FIORI APPROVE REQUESTS X1 2.0 Approve Requests UI 2.0
FIORI APPROVE REQUESTS X1 2.0 Approve Requests UI 2.0 > 7.50
HCP WORKFLOW 1.0 MyInbox Cloud Deployment
SAP ACS 1.2 FOR SAP S/4HANA UI for ACS
SAP ACS 1.2 FOR SAP S/4HANA UI for ACS on NW 7.5
SAP ACS 1.3 FOR SAP S/4HANA UI for ACS
SAP ASSURANCE & COMPLIANCE 1.2 UI ACS on NW 7.51 and NW 7.52

6
 SAP ASSURANCE & COMPLIANCE 1.2 UI Assurance and Compliance
SAP ASSURANCE & COMPLIANCE 1.3 UI ACS
SAP FIORI FOR SAP ERP TRV 1.0 UI for ERP TRV
SAP FIORI FOR SAP S/4HANA 1511 UI for Approve Requests
SAP FIORI FOR SAP S/4HANA 1610 UI for Approve Requests
SAP FIORI FOR SAP S/4HANA 1610 UI for HCM (Fiori 2.0)
SAP FIORI FOR SAP S/4HANA 1610 UI for SAP S/4HANA
SAP FIORI FOR SAP S/4HANA 1610 UI for TRV
SAP FIORI FOR SAP S/4HANA 1709 UI for Approve Requests
SAP FIORI FOR SAP S/4HANA 1709 UI for HCM (Fiori 2.0)
SAP FIORI FOR SAP S/4HANA 1709 UI for SAP S/4HANA
SAP FIORI FOR SAP S/4HANA 1709 UI for TRV
SAP HYBRIS MARKETING 1.2 Hybris Marketing
SAP HYBRIS MARKETING 1709 Hybris Marketing

For other instances, you can download this component in the SAP Support Launchpad:

7
Figure 1 MyInbox Component

Note Always check SAP Note 2221151 after installing My Inbox

components or patches

In addition to the main component, it is highly recommended to apply the support packages in
order to have the latest corrections available:

8
Figure 2 Support Packages

In this document, we will download until SP06.

After all the imports, Imported Support Packages in transaction SPAM in the frontend system should
look like this:

Figure 3 Support Packages' Summary

9
IW_PGW 100

1. Go to this URL: https://launchpad.support.sap.com/#/softwarecenter/search/IW_PGW

2. Download SAPK-100AGINIWPGW
IW_PGW 100: Add-On Installation

Figure 4 Downloading IW_PGW 100 Add-On

3. Next download all the SPs which they are SP01-SP09 as shown below:

Figure 5 IW_PGW SPsxx

IW_PGW is contained in SAP_GWFND from SAP_GWFND 7.51

Note release, so there is no need of any installation for releases above
7.51. See KBA 2462396 for further information

10
 Component IW_PGW 100 will be out of maintenance as of
Note
31.12.2025

4. Once Everything is downloaded and installed, you should confirm in the Front-End you
have the following:

11
 Chapter 2
Creating Inbox specific System Alias

When using an OData service, it is needed to define a System Alias. These aliases refer to an RFC
connection that will consume the backend services in the Front-End.

Creating the new SAP System Alias

In the Front-End NetWeaver Gateway System, Execute the following:

1. Transaction code SPRO
2. SAP Customizing Implementation Guide
3. SAP NetWeaver
4. SAP Gateway
5. OData Channel
6. Configuration
7. Connection Settings
8. SAP Gateway to SAP System
9. Manage SAP System Aliases

Figure 6 SPRO Managing SAP System Aliases

12
10. Create a new entry in this table with the following parameters:

Figure 7 Manage SAP System Aliases - Overview

SAP System Alias: Your SAP System Alias name

Description: The description you want to create
For Local App: Mark this flag. By marking this flag you inform the system that you are using
the software component IW_BEP( Remember this SW component is already included in
SAP_GWFND)
RFC Destination: The RFC you want to connect to when using the Inbox services
Software Version: /IWPGW/BWF. This means that you are using specifically My Inbox app.
System ID: Your target system ID
Client: Your target client

Only fill the “Software Version” column if you are using the
Note system alias for My Inbox app. Other Fiori apps do not use BWF,
so this column must remain blank in this case. This issue is
addressed in SAP Knowledge Base Article 2348671

You can find more information related to the flags in the following note:
2249736 - FAQ related to the System Alias and Gateway flags

13
 Chapter 3
Activating and testing OData Service

Service TASKPROCESSING

The OData service that My Inbox 2.0 uses is TASKPROCESSING version 2. In this section, we will
import the service to our Gateway system, add the Technical service in order to consume the
service and assign a system alias so the service is consumed in the right system and client. These
settings are performed in the frontend system, although the service resides in the backend.

Adding TASKPROCESSING to the Gateway

Go to your Gateway system and execute transaction /n/IWFND/MAINT_SERVICE. You will see a list
of OData services that belong to the backend and are currently consumed in the frontend:

Click on button “Add Service” on the top button bar:

1. Choose the system alias created in Chapter 1 and service /IWPGW/TASKPROCESSING. Click
on “Get Services”

14
 Figure 8 Getting TASKPROCESSING Service

2. Once the service is found and the Version is 2, select the service and click on button “Add Selected
Services”

Figure 9 Adding the service

In the “Add Service” dialog enter:

- Technical Service Name: The name of the service you will consume
- Technical Model Name: The name of the model that the Gateway service will execute
- Package Assignment: The package where you will export the service

Note It is important that you enter the right transportation package so

you can export your setting to other clients. In this example, we

15
 set the package to a temporary one ($TMP), but don’t do that if
you plan to transport the service.

If everything goes fine, you will receive a success message:

Change the system alias for service TASKPROCESSING version 2

1. Execute the transaction code: /n/IWFND/MAINT_SERVICE

2. Select ZTASKPROCESSING version 2 as shown below:

Figure 10 Selecting TASKPROCESSING OData service

16
 3. On the recently added service, click on “Add System Alias” and enter the following values:
- Service Doc. Identifier: ZTASKPROCESSING_0002
- SAP System Alias: The alias you defined in chapter 1
- Default System: Mark the checkbox
- Technical Service Name: The technical service name you entered in the previous
step
- External Service Name: TASKPROCESSING
- Version: 2

Figure 11 Assigning System Aliases to OData Service

4. After this step, the service should look like this:

Figure 12 System Alias has been assigned to the OData Service

Do not use version 1 of OData service TASKPROCESSING. If you do so, you

Note may run into inconsistencies. If you downloaded software component
UIX01CA1 200, you must configure only version 2 of service
TASKPROCESSING and leave the other version blank.

Check the system alias and user consistency

In order to check that the RFC works properly and the users are consistent in both systems
1. double click on the SAP System Alias

17
 Figure 13 Checking System Alias

2. Click on the “Remote Logon” button. If the initial screen for the backend system is shown,
the RFC connection works fine:

Figure 14 Back-End System Remote screen

18
 Chapter 4
Activating UI5 Service

Transaction SICF

In addition to the OData services, SAP Fiori needs to activate the generic Internet Communication
Framework (ICF) services, which are available in an inactive state for security reasons. After the
installation, you have to activate the corresponding service for my inbox, which is called
CA_FIORI_INBOX. This service resides in the Front-End system.
Activating service CA_FIORI_INBOX

1. Go to transaction code SICF or /nSICF

2. Search for service CA_FIORI_INBOX
3. Click on Execute (F8) or Press F8 keyboard function

Figure 15 SICF activating CA_FIORI_INBOX

19
4. Look for UI5 service CA_FIORI_INBOX under ui5_ui5 and right click on it and choose
“Activate Service” option and confirm

Figure 16 Activating SICF service ca_fiori_inbox

20
 5. You should see the following screen below:

Figure 17 Activate the service

There is another service called CA_FIORI_INBOX that points to the old BSP
Note application. Do not activate that service unless you are using a BSP non
UI5 based service

Testing Service URL

Right click on the service again and choose ‘Test’. Of course the browser will not open the page
since this service is not designed to work by itself. But keep the service path since it will be used in
a later stage when defining the My Inbox Tile.

21
Figure 18 Testing the service

Check the service path as it will be used in a later stage.

Creating Business Role

Next step is to assign the Business Role SAP_FND_BC_MANAGER_T the user

22
1. Go to PFCG which is the Role Maintenance in your Gateway Front-End system and type
SAP_FND_BCR_MANAGER_T as shown below:

Figure 19 PFCG Role Maintenance

2. Click on the Pencil Icon to in order to add your user ID to this Role

Figure 20 Changing the Role

23
3. Next click on the User tab to add the user to it

4. Type the user name and click on Save

24
 Chapter 5
Activating the Task Filter

Task Filter

You can activate or deactivate the task filter so that the only tasks configured in the Maintain Task
Names and Decision Options IMG activity or the Workflow Pattern Customization IMG activity are
seen in My Inbox. By default, the filter is deactivated.
When the task filter is set to Active:
Sending Notifications: Only notifications of items that were configured using the Maintain Task
Names and Decision Options IMG activity or the Workflow Pattern Customization IMG activity are
sent.
The SAP Gateway Workflow service only receives items that were configured using the Maintain
Task Names and Decision Options IMG activity or the Workflow Pattern Customization IMG
activity.
When the task filter is not set to Active:
• All notifications are sent.
• All items are read.

Customizing the Task Filter

1. Go to the following customizing path in SPRO transaction in your frontend system

2. SAP Customizing Implementation Guide
3. SAP NetWeaver
4. SAP Gateway Service Enablement
5. Content
6. Workflow Settings
7. Enable Task Filter

25
Figure 21 Enabling Task Filter

Task filter must be ACTIVE in your Gateway system

Task filter must be INACTIVE in your Backend system. Otherwise, you
Note could not see all the tasks in your inbox. This is explained in SAP
Knowledge Base Article 2415738
If your system architecture is embedded, task filter must remain
INACTIVE.

26
 Chapter 6
Workflow Customizing

In this section we will explain the basic workflow customizing needed to make My Inbox app work.
If you already can see your items in transaction SBWP, you can skip this section. All these settings
are done in the backend system.

Automatic Workflow Customizing

To setup a Workflow environment, the easiest way is executing the Automatic Workflow
Customizing. You can execute this in transaction SWU3:

Figure 22 Automatic Workflow Customizing

For release S/4HANA OnPremise 1709 and above, the workflow system user and workflow have
been changed. The workflow system user is called SAP_WFRT now instead of WF-BATCH. The
workflow system jobs start with SAP_WORKFLOW now and are scheduled automatically by
"Technical Job Repository", transaction SJOBREPO.

27
 For more detail about the new workflow system user and jobs,
Note
check SAP note 2568271. In this note, we detail the steps to
follow when upgrading to S/4HANA release.

For releases prior to S/4HANA OnPremise 1709, the only action to do in this transaction is
executing the automatic customizing (F9 or the button). The system performs the tasks shown
in the folders and will show a green check if the task was successful.

Not all the tasks have to be in green status. There are certain
Note
tasks that may not be needed in your business scenario and may
have the red icon.

In this transaction, you can also execute the verification workflow. This is a test workflow that will

Click on F5 (or the icon) to start the verification workflow. This will launch workflow 30100051

Figure 23 Verification of workflow started

Go to SAP Business Workplace (transaction SBWP or icon ) and check that the verification task
was sent successfully:

Figure 24 Inbox transaction SBWP

See here for more information about transaction SWU3

28
Assigning agents to the tasks

Once the workflow environment is ready, the next step consists of assigning the workflow tasks to
the corresponding agents.
My Inbox app will only show the tasks assigned to the corresponding agent, so it is important to do
a proper agent assignment in all tasks of our workflow.
For this example, we will do the customizing on the “Process Notification of Absence” workflow.
Note that you must do this customizing for all the workflows you want to display on My Inbox app.
Go to transaction PFTC, enter Workflow Template 30000015 and click on Display (F7)

Figure 25 choose your task in transaction PFTC

The first step to perform is making sure that the triggering event of the workflow is activated.
Every time the triggering event happens, the workflow will be triggered.

29
 1. Go to the “Triggering events” tab and make sure that the event is activated (green light):

Figure 26 Activating the Workflow Event

The activation of the triggering event of a workflow is

Note
transported between systems, so make sure that you use the
corresponding customizing request before saving

30
2. The next step consists of assigning the agents to the workflow tasks. Go to “Basic Data” tab
and choose the “Workflow Builder” tab:

Figure 27 Accessing Workflow Builder

3. After this, you will see all the workflow steps:

Figure 28 Workflow Builder steps

31
4. Look for the tasks that require agent assignment. Double click on the task and check if the
“Agent Assignment” icon is green:

Figure 29 Agent assignment in the Task

5. Click on the icon next to “Agent Assignment”. Here you will see the tasks groups that are
assigned to this workflow. Click on “Create Agent Assignment” (F5 or icon):

Figure 30 Creation of Agent Assignment

32
6. Choose “User” and enter the ID of the agent you want to receive the tasks:

Figure 31 Choosing an Agent

Figure 32 choosing a user

7. The agent appears in the list:

33
 8. You don’t need to save, just update the index (Shift+F1).

Note Do not forget to update the index (Shift+F1 or icon) every

time you do any modification in the agent assignment of the
workflow

Testing the workflow

The last step consists of launching the workflow and making sure that the tasks arrive in the
Business Workplace.
The workflow is launched when the triggering event happens in the system. Another option, used
only for test purposes, is going to transaction SWUS and simulating the triggering event:

Figure 33 Transaction SWUS

34
1. Enter the workflow number and click on “Execute”:

Figure 34 Testing Workflow

2. If everything goes fine, you will receive a success message

Depending on the workflow you are launching, you may need to

Note enter the object for which you want to launch the workflow. For
example, a purchase order approval workflow will require a
purchase order number in order to be triggered.

3. Go to the business workplace and check that the task was successfully received

Figure 35 Business workplace (transaction SBWP)

35
 Chapter 7
Customizing Task Names

Maintain Task Names

The next step in the configuration for My Inbox is customizing the task that will be displayed in the
application. Here you will assign the tasks that will be displayed in My Inbox app and the decisions
that can be taken via the buttons.
1. Go to SPRO path, Backend system
• SAP NetWeaver
• SAP Gateway Service Enablement
• Content
• Workflow Settings
• Maintain Task Names and Decision Options

Figure 36 Maintain Task Names and Decision

36
2. The entries were the following:

Figure 37 Change View "Step Name": Overview

- Workflow ID: Is the workflow for which you want to display tasks. In this example,
we will choose Workflow template WS30000015
- Step description: The description you want to provide.

- Step ID: You can find this identifier in the backend. Go to transaction PFCT, enter
your workflow and click on display:

Figure 38 Workflow Builder

37
 3. In the “Navigation Area” section, you will find the Step ID:

Figure 39 Step ID

Note This customizing is described in SAP Knowledge Base Article

2421360

Customizing the Decision Keys

1. In the same customizing view shown in the previous section, click on the “Decision Keys”
sub-dialog :

Figure 40 Decision Keys

2. Add and define your decision options in the Decision Keys table as described below and
save your entries:
• Key: Enter the decision key.

Decision keys are numeric and sequential and correspond to the position of decision
options in the Workflow Builder. Enter the first decision option with key 1, the second
decision option with key 2, and so on.
38
• Icon Mime Repository Path: Leave this field blank.
• Decision Text: Define the label of the decision option.
This name is displayed on the application screen as a button label. The proposed length
of the decision text is maximum 14 characters. Decision texts longer than 14 characters
will not fit to the device screen.
• Comment On: If you want to make it mandatory for the user to add a comment when
executing a decision, select this checkbox.
• Nature: Here you have the following options:
- Select POSITIVE for the approve type decision option.
The decision option is displayed either as a green pushbutton or in a gray popover
(depending on the space available) on the detail screen of the application.
- Select NEGATIVE for the reject type decision option.
The decision option is displayed either as a red pushbutton or in a gray popover
(depending on the space available) on the detail screen of the application.
- Leave the field empty for multiple decision options.
The decision options are displayed either as gray pushbuttons or in a gray popover
(depending on the space available) on the detail screen of the application.
If you cannot see the Approve and Reject buttons in My Inbox app, apply SAP note
2365275. Do not forget to invalidate all caches afterwards as explained here. It is
recommended to upgrade to My Inbox 2.0 SP03.

39
 Chapter 8

Defining Gateway Scenario

Scenarios

The next step is defining a scenario for the Inbox app. Scenarios contain the list of tasks that each
user will see.

Customizing the Scenario

1. Go to the following SPRO path in your Gateway system:

• SAP NetWeaver
• SAP Gateway Service Enablement
• Content
• Task Gateway
• Task Gateway Service
• Scenario Definition

Figure 41 Defining Scenario

2. Create a new entry with the following fields:

40
 - Scenario Identifier: The name of your scenario
- Scenario Display Name: My Inbox Scenario
- Technical Service Name: /IWPGW/TASKPROCESSING
- Version: 2
- EntitySet External Name: Task
- Property External Name: TaskDefinitionID
- Default Sort by Property: CreatedOn (or the default sort order for the incoming items)
- Mass Action: ‘X’ if you want to allow mass approval/rejection of items

Figure 38 Customizing the Scenario Definition

3. Choose your scenario and click on folder “Assign Consumer Type”. Here you choose on
which device you will display My Inbox app. In this example, I choose the three consumer
types available:

Figure 42 New Entries Overview of Added Entries

Tablet is mandatory in this sub-dialog. All other Consumer Types are optional.

Task Definition for Scenario

Click on subfolder Task Definition for Scenario and enter:

- SAP System Alias: The system alias where your backend system is located. This was defined
when defining the TASKPROCESSING service
- Task Type: The tasks you want to display on My Inbox app
41
Figure 43 TASKPROCESSING Service

42
 Chapter 9
Creating a Tile for the Task Definition Scenario

Next step will be creating a new Tile in the Fiori Launchpad and assigning it to the corresponding
user and its scenario.

Creating a Catalog in the Launchpad Designer

1. Log in to the Launchpad Designer. You can either launch the Launchpad Designer URL:
http(s)://host:port/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html#
Or use t-code /n/UI2/FLPD_CUST or logon via the customizing path:
• SAP Customizing Implementation Guide
• SAP NetWeaver
• UI Technologies
• SAP Fiori
• Configuring Launchpad Content
• Adding Apps to SAP Fiori Launchpad
• Configure Target Mappings and Tiles
2. SAP Fiori Launchpad Designer (Current Client)

Figure 44 Accessing Fiori Designer

3. You can either create a new catalog so you can group your tiles. My Inbox tile is included in
the existing standard Business Catalog SAP_CA_BC_MYINBOX for S/4HANA 1610, but it is
not recommended to use the standard catalogs. The recommendation is copying the
standard catalog into your own one and transporting your own catalog between
envinronments.

Note If you are using another product version you can find the
standard catalog in Fiori Library here.

43
4. In order to create a new catalog, click on the ‘+’ sign at the bottom of the catalog list:

Figure 45 Creating Catalog

44
5. Provide a title to your catalog and click on “Save”:

Figure 46 Creating My Inbox Catalog

6. Inside the catalog, a target mapping and a tile must be created. In the target mapping we
provide the information on what is the application we are going to launch. Technically this
is called “Semantic Object” and “Action”. Click on “Create Target Mapping” and provide the
corresponding fields.

45
 Figure 47 Accessing target mapping

7. For inbox, the configuration is as follows:

a. Semantic object: WorkflowTask
b. Action: display
c. Application Type: SAPUI5 Fiori App
d. Title: Your Title
e. URL: /sap/bc/ui5_ui5/sap/ca_fiori_inbox in case you are using the standard
CA_FIORI_INBOX service. In case you are using a copy, you can get the URL by going
to transaction SICF and testing your inbox service

46
 Figure 48 Getting the URL of My Inbox application

- ID: cross.fnd.fiori.inbox (as explained in SAP Note 2178368).

Figure 49 Target mapping

47
Creating a new dynamic tile

Next step is consuming that target mapping in a Dynamic tile. Dynamic tiles calculate in real time
the amount of items available in the app.
1. Go to the Launchpad Designer and click on the ‘+’ button

Figure 50 Adding a tile

2. Choose a dynamic tile so we can see the amount of items in the inbox:

Figure 51 Adding a dynamic tile

3. Create the tile with the following fields:

- Title: Choose the title you want to display on the App
- Service URL: Will be the URL you want to call your OData service. Generically speaking,
it s hould be like this:
/sap/opu/odata/IWPGW/TASKPROCESSING;v=2;mo/TaskCollection/$count/?$filter=Sta

48
 tus eq 'READY' or Status eq 'RESERVED' or Status eq 'IN_PROGRESS' or Status eq
'EXECUTED'
- Semantic Object: WorkflowTask
- Action: Display
Parameters: If you want to see all items in the inbox, just type allItems=true. If you want to
display the items according to the scenario defined in previous step, type scenarioId=XXX
(your scenario ID defined in the customizing).

Figure 52 Dynamic tile configuration

After doing this, there are two options: Assigning the catalog to the user or creating a group,
assigning the tile to the group and assigning the group to the user.

Assigning the catalog to a user

If you follow this procedure, you leave the users the option to
Note add the tile to their Launchpad or not. In this case, the users may
not be able to get newly updated tiles. You should follow one or
another method depending on your company policies.

At this point, the catalog is not assigned to any user, so we have to provide the agents with access
to the recently created My Inbox Tile
1. Go to transaction PFCG and create a new single role

Figure 53 Adding a Role

49
2. Go to the “Menu” tab and choose SAP Fiori Tile Catalog:

Figure 54 Configuring the ZINBOX_ROLE

3. Assign the Fiori Launchpad Catalog created in the previous step:

50
 Figure 55 Assigning the Catalog

4. Go to the User tab and assign the users for which you want to see the catalog:

Figure 56 Assigning the user to the Role

5. Save and go to the Fiori Launchpad

51
 6. Click on the pencil icon to access the new created catalog
7. Click on “Add Group”:

Figure 57 Adding the Group to the catalog

8. Add the recently created My Inbox catalog and save:

Figure 58 Adding Group in the Fiori Launchpad

Creating a group and assigning it to the user

1. Go to the Fiori Launchpad Designer

2. Click on the Group tab on the top left area

Figure 59 Creating Groups in the Launchpad Designer

3. Click on the “+” sign on the bottom of the list

52
 Figure 60 Creating the new group

Leave the “Enable users to personalize their group” if you want to give the users
personalization privileges.

4. Now add the new tile to the group. Click on the “+” sign in the Show as Tiles section

Figure 61 Creating a new tile in a group

5. Search for the catalog created in the prior section

53
 Figure 62 Adding the catalog to the group

6. Go to your frontend system and execute transaction PFCG

7. Create a new single role

Figure 63 Creating a new catalog role in transaction PFCG

8. Go to the “Menu” tab and choose SAP Fiori Tile Group:

54
Figure 64 Assigning the group to the role

9. Assign the Fiori Launchpad Group created in the previous step:

Figure 65 Assigning the Group

10. Go to the User tab and assign the users for which you want to see the group:

55
 Figure 66 Assigning the user to the Role

11. Save your entries

12. Go to the Fiori Launchpad and add the tile in the new group by clicking on the “+” button:

Figure 67 Once in the Fiori Launchpad, add the tile to the group

56
 Figure 68 Adding the Tile into the catalog

Final Result

In either case, My Inbox can be seen in the Fiori Launchpad

57
Figure 69 My Inbox Demo

58
Click on the Tile. You will be able to see the app with all the items

Figure 70 My Inbox App

My Inbox 2.0 User Icon

Once you setup the Inbox app, you can see the available options for My Inbox by clicking on the user icon on the
top left corner of the screen:

Figure 71 Choose the User Icon

The options are the following:

59
Figure 72: Available Options in the User Icon

- App Finder: Here you can find the available apps in your Fiori Launchpad. You can find more
information here
- Settings: The generic settings of the Fiori Launchpad.
- Manage My Substitutes and Substitute For: These buttons are used to manage substitutions in My
Inbox. You can find information on how to configure this feature in KBA 2447316
- Support Information: Shows technical information about the selected task such as the workflow
task ID, the scenario or the selected sort sequence.

60
Figure 73 Support Information Screen

- About: Shows generic information about the app such as Inbox version, SAPUI5 version or the
Target Mapping ID.

61
Figure 74: About My Inbox 2.0

Note For more information on how to display My Inbox version, check KBA 2557477

62