This Document Contains a list of All Transaction Codes Required for SAP Fiori Development[Front-End,Back-End and Gateway]. For utilization of Workflows in Custom SAP Fiori Apps,Workflow related transactions would be used.Some of these will be available in Frontend[SAP Gateway] and Some will be for SAP Back-End, in case of Central HUB deployment of SAP Gateway. In case you have an Embedded Gateway Deployment,both Back-End and Front-End Transactions would be available in a single system.

The list of T-codes is based on the following system:

EHP7 for SAP ERP 6.0(Release = EHP7 FOR SAP ERP 6.0)

SAP ERP(Release = 2005(SAP ERP 6.0))

SAP Netweaver(Release = 7.4)

and the following Software Components:

SAP_BASIS    Release = 740  SPLevel =  0010    Support Package = SAPKB74010    SAP Basis Component

SAP_ABA    Release = 740    SPLevel = 0010    Support Package = SAPKA74010    Cross-Application Component

SAP_GWFND    Release = 740    SPLevel = 0013    Support Package = SAPK-74013INSAPGWFND    SAP Gateway Foundation 7.40

[Note:]

This list is divided into 3 columns.

(01)T-code

(02)Description of T-code

(03)Alternate T-code called,for example in case of Front-End and Back-End Transaction Codes.

(04)Overview Description of commonly used Transaction codes is provided[New]

[Note:]

Standard T-codes Required:

Odata Service Development T-codes:

SEGW    Gateway Service Builder

[Description = Used for Testing SAP Fiori Apps Odata services and also used for enhancing Odata Service like redefining a standard method in the DPC class of the relevant Standard Odata Service. Best way to enhance a standard applications,as all changes are recorded in one project].

Administrative T-codes:

SU01    User Maintenance

[Description = Used for creating users and assigning them roles,especially useful when creating copies of Fiori based roles based on standard template roles].

PFCG    Profile Generator

[Description = Used for creating roles,especially useful when creating copies of Fiori based roles based on standard template roles].

SICF    Maintain Services

[Description = For Testing and Activating Services associated with the Standard Fiori Framework Services as well as Standard and Custom Fiori Applications].

LPD_CUST    Launchpad

[Description = Provides a list of all Fiori Launchpads(Standard[] and the custom[] created ones) containing Fiori app URLs,copy,edit,Transport,provided System Alias etc.].

SMLG    CCMS: Maitain Logon Groups

SM59    RFC Destinations (Display/Maintain)

[Description = This is where all Trusted RFC(TRFC's) for communication between SAP Gateway system and ECC system are setup,with the ability to test them as well].

_____

SPRO    Customizing - Edit Project

Would require access to the following nodes in IMG(Implementation Guide):

SAP Customizing Implementation Guide > SAP Netweaver > SAP Gateway

SAP Customizing Implementation Guide > SAP Netweaver > SAP Gateway Service Enablement

SAP Customizing Implementation Guide > SAP Netweaver > UI Technologies

Figure 01 : SPRO Nodes Specific to SAP Fiori

_____

RZ10    Maintain Profile Parameters

RZ20    CCMS Monitoring

RSRT    Start of the report monitor

PTARQ    Test Environment for Leaves

[Description = This is a Suite of Apps,especially for testing and configuring Leave based Scenarios. Pertains to both the Leave based HCM Fiori apps such as 'My Leave Requests'(For Employees) and 'Approve Leave Requests'(For Manager)].

EXTID_DN    External Identification Type DN

SPAM    Support Package Manager

[Description = This tool is used by the Basis Consultant during Fiori Landscape setup].

SMICM    ICM Monitor

ABAP Related Backend Development T-Codes:

SE93    Maintain Transaction Codes

SE01    Transport Organizer (Extended)

SE80    Object Navigator

SE11    ABAP Dictionary Maintenance

SE18    Business Add-Ins: Definitions

[Description = This tool is used if BADI's are provided for a Fiori Apps,instead of creating a project in SEGW(Gateway Builder) e.g: 'HCM_B_PEP_PROF' for People Profile Fiori App].

SE24    ABAP Class Builder

[Description = Used when editing or redefining methods of DPC(Data Provider Class) and MPC(Model Provider Class) classes associated with a Gateway Builder Project for the given Fiori App in Transaction SEGW].

ST22    ABAP Dump Analysis

SE63    Translation Editor

SE43    Maintain Area Menu

SE38    Abap Editor

SBWP    SAP Business Workplace

SM30    Call View Maintenance

____

Note:

Authorization for SM30 is required when accessing or configuring Configuration tables for example

creation of Semantic Objects using T-code '/UI2/SEMOBJ' which makes use of Maintenance Tables.

____

Workflow related T-codes:

SWDD    Workflow Builder

SWIA    WI Administration Report

SWDC    Workflow Definition: Administration

PFTC    General Task Maintenance

/IWWRK/WF_FILTER    Handle Activation of WF item filter

For Front End SAP UI5 Development:

All Transaction code starting with '/UI2/' and '/UI5/'.

Transaction Codes starting with '/UI2/':

/UI2/73000001    Register POWL APPLID    SICF_INST

/UI2/73000003    Maintenance view for SAP GUI Tags(user defined tags)    SICF_INST

/UI2/73000004    NWBC Configuration - Define Parameter Names(Customer)    /UI2/NWBC_CFG_P_CUST

/UI2/73000005    NWBC Configuration - Define Parameter Names(Customer)    /UI2/SAPLNWBC_CFG

/UI2/73000007    NWBC Configuration - Define Parameter Names(Customer)

/UI2/73000008    Maintain Services    SICF

/UI2/73000009    Trust Manager    STRUST

/UI2/73000010

/UI2/73000011    Trust Manager    STRUST

/UI2/73000012

/UI2/73000013

/UI2/73000014    Server Communications    CLB2_PLATF

/UI2/73000015    Application Server Assignment    CLB2_APPLI_PLATF

/UI2/73000016    badi Creation    SE18

/UI2/73000017    Semantic Objects

/UI2/73000019    SAPLS_CUS_IMG_ACTIVITY(Catalog)

/UI2/73000020    Catalogs

/UI2/73000021    Catalogs

/UI2/73000022

/UI2/73000023    Configuration of RFC Connections

/UI2/73000024

/UI2/73000025    Manage SAP System Aliases    /UI2/GW_SYS_ALIAS

/UI2/73000026    Activate and Maintain Services    /IWFND/MAINT_SERVICE

/UI2/73000027

/UI2/73000028    Maintain Services    SICF

/UI2/73000029    Role Maintenance    PFCG

/UI2/73000030    Data Browser    SE16

/UI2/73000031    Semantic Objects

/UI2/73000032    Launchpads    LPD_CUST

/UI2/73000033    Fiori Launchpad Checks    /UI2/FLC

/UI2/73000034    SAP Netweaver gateway Application Log Viewer    /IWFND/APPS_LOG

/UI2/73000035    SAP Netweaver gateway Application Log Viewer    /IWFND/APPS_LOG

/UI2/73000036    Odata Services

/UI2/73000037    Fiori Launchpad Intent Resolution Analysis

/UI2/73000038    Not runnin

/UI2/73000039    badi Creation    SE18

/UI2/73000040    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000041    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000042    SAPLS_CUS_IMG_ACTIVITY    PFCG

/UI2/73000043    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000044    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000045    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000046    Collaboration Tunnel Service    CLB2_TUNNEL

/UI2/73000047    Define Background Job    SM36

/UI2/73000048    Simple Job Selection    SM37

/UI2/73000050

/UI2/73000051    bgRFC Configuration    SBGRFCCONF

/UI2/73000053    Odata Service Settings for Notifications

/UI2/73000054    UI2 Global Cache Invalidation

/UI2/73000055    /UI2/USER_FEEDBACK_Setup    /UI2/FEEDBACK_SETUP

/UI2/73000056    CCMS(maintain Logon Groups)

/UI2/73000057    Badi Creation    SE18

/UI2/73000058    Badi Creation    SE18

/UI2/73000059    Events for Change Document    SWEC

/UI2/73000060    Collaboration Service    CLB2_SERVICE_C

/UI2/CACHE    Register service for UI2 cache us

/UI2/CACHE_DEL    Delete cache entries

/UI2/CHIP    Chip Registration

/UI2/CUST    Customizing of UI Technologies

/UI2/FEEDBACK_SETUP    UI2 Setup User Feedback Service    /UI2/FEEDBACK_SETUP

/UI2/FLC    Fiori Launchpad Checks

/UI2/FLIA    Fiori Launchpad Intent Analyis

/UI2/FLP    SAP Fiori Launchpad

/UI2/FLP_CONTCHECK    Fiori Launchpad - Content Checks

/UI2/FLP_INTENTCHEC    Fiori Launchpad - Intent Checks

/UI2/FLPD_CONF    Fiori Lpd. Designer (cross-client

/UI2/FLPD_CUST    Fiori Lpd. Designer (client-spec.

/UI2/GW_ACTIVATE    Gateway - Activation    /IWFND/IWF_ACTIVATE

/UI2/GW_APPS_LOG    Gateway - Application Log

/UI2/GW_ERR_LOG    Gateway - Error Log

/UI2/GW_MAINT_SRV    Gateway - Service Maintenance

/UI2/GW_SYS_ALIAS    Gateway - Manage SAP System Alias    /UI2/GW_SYS_ALIAS

/UI2/INVAL_CACHES    Global Invalidation of UI2 chache

/UI2/NAV    Register navigation objects

/UI2/NAVPROV    Define navigation provider

/UI2/NWBC    Start UI2 NWBC

/UI2/NWBC_CFG_CUST    NWBC Configuration (Customer)

/UI2/NWBC_CFG_P_CUST    NWBC Config: Define Parameter (Cust)

/UI2/NWBC_CFG_P_SAP    NWBC Config: Define Parameter (SAP)

/UI2/NWBC_CFG_SAP    NWBC Configuration (SAP)

/UI2/PERS_DEL    Cleanup Personalisatation Service

/UI2/POWL    Register POWL for OData consumption

/UI2/SEMOBJ    Define Semantic Object - Customer

/UI2/SEMOBJ_SAP    Define Semantic Object - SAP

Transaction Codes starting with '/UI5/':

/UI5/78000001    ICF: Report for Activating Special Service During Installation    SICF_INST

/UI5/78000002    ICF: Report for Activating Special Service During Installation    SICF_INST

/UI5/THEME_DESIGNER    UI Theme Designer

/UI5/THEME_TOOL    UI Theme Tool

SAP Fiori Front End  Specific T-codes:

/IWFND/32000004    Role Maintenance    PFCG

/IWFND/32000011    Activate/Deactivate Metadata cache    /IWFND/MED_ACTIVATE

/IWFND/32000012    Cleanup of Model Cache    /IWFND/CACHE_CLEANUP

/IWFND/32000013    Activate and Maintain Services    /IWFND/MAINT_SERVICE

/IWFND/32000017    Assign Data Provider to data model

/IWFND/32000018    Change View Assign SAP System Aliases to Odata Service

/IWFND/32000020    IMG Activity not found for transaction /IWFND/32000020

/IWFND/32000021    IMG Activity not found for transaction /IWFND/32000021

/IWFND/32000022    IMG Activity not found for transaction /IWFND/32000022

/IWFND/32000023    IMG Activity not found for transaction /IWFND/32000023

/IWFND/32000024    IMG Activity not found for transaction /IWFND/32000024

/IWFND/50000001    Choose Activity

/IWFND/50000003    SAP Netweaver Activation code    /IWFND/IWF_ACTIVATE

/IWFND/50000004    Manage SAP System Aliases

/IWFND/50000005    Configuration of RFC connections    SM59

/IWFND/50000006    SAP gateway client

/IWFND/50000007    SRT_WS_IDP_CUSTOMIZE[Shedule Switch]

/IWFND/50000008    There are no executable transactions assigned to the IMG activity

/IWFND/50000009    Define Background job    SM36

/IWFND/50000010    cleanup for SAP Netweaver gateway Cache and Persistency Frameworks    /IWFND/CLEANUP

/IWFND/50000011    Simple Job Selection    SM37

/IWFND/50000013    There are no executable transactions assigned to the IMG activity

/IWFND/50000014    Role Maintenance    PFCG

/IWFND/50000015    Role Maintenance    PFCG

/IWFND/50000018    Logon Ticket Administration for Single Sign-On    SS02

/IWFND/50000019    There are no executable transactions assigned to the IMG activity

/IWFND/50000022    Deactivate Logging of Variables T100 Messages

/IWFND/50000027    maintaince dialog is incomplete or not defined

/IWFND/50000031    Registration in System Landscape Directory    R70

/IWFND/50000038    IMG Activity not found for transaction /IWFND/50000038

/IWFND/50000039    IMG Activity not found for transaction /IWFND/50000039

/IWFND/50000040    IMG Activity not found for transaction /IWFND/50000040

/IWFND/50000043    the maintenance dialog for /iwfnd/v_coobgr

/IWFND/50000044    There are no executables assigned to this

/IWFND/50000045    There are no executables assigned to this

/IWFND/50000046    Class Builder    SE24

/IWFND/50000051    Configuration of RFC Connections    SM59

/IWFND/50000052    bgRFC Configuration    SBGRFCCONF

/IWFND/50000053    Consumer Activation

/IWFND/50000054    Maintenance view for the GW CCMS Structure

/IWFND/50000055

/IWFND/50000056    Enter Correct SNC Names in Table View VUSREXTID(from SAP R/3 4.5)    /IWFND/BULK_USER_MAP

/IWFND/50000057    Change View Logical File Path Definition    FILE

/IWFND/50000058

/IWFND/50000059

/IWFND/50000060

/IWFND/50000061    No transaction found

/IWFND/50000062    Role Maintenance    PFCG

/IWFND/50000063    SAP gateway client

/IWFND/50000065    WSS_SETUP    /IWFND/WSS_SETUP

/IWFND/50000066    User Maintenance    SU01

/IWFND/50000068    Badi /IWFND/BD_DCS_PROCESS_PLUGIN

/IWFND/50000071    IMG Activity not found for transaction /IWFND/50000071

/IWFND/50000072    SAP Netweaver Gateway Log Level

/IWFND/50000073    Configuration of RFC Connections    SM59

/IWFND/50000074    Trust Manager:Display    STRUST

/IWFND/50000075    bgRFC Configuation    SBGRFCCONF

/IWFND/50000076    bgRFC Monitor    SBGRFCMON

/IWFND/50000077    Business Communication Services - Administration    SCOT

/IWFND/50000078    Directory Service Connection    LDAP

/IWFND/59000010    Cleanup Notifications    /IWFND/NOTIF_CLEANUP

/IWFND/59000011    SAP Netweaver Gateway Virus Scan Profile Configuration    /IWFND/VIRUS_SCAN

/IWFND/59000012    Creating Badi    SE18

/IWFND/59000013    Creating Badi    SE18

/IWFND/59000018    SAP Netweaver gateway : Error Log    /IWFND/ERROR_LOG

/IWFND/59000019    SAP Netweaver gateway:Tracing Tools    /IWFND/TRACES

/IWFND/59000020    SAP Netweaver Gateway Application Log Viewer    /IWFND/APPS_LOG

/IWFND/59000021    Simple Job Selection    SM37

/IWFND/59000022    Creating Badi    SE18

/IWFND/59000023    Context based SAP System Alias Configuration

/IWFND/59000024    (BADI Implementation)(Implementations for Badi Definition

/IWFND/59000025    Parallelization for Multiple Origin Composition    /IWFND/MOC_PARALLEL

/IWFND/59000026

/IWFND/59000027

/IWFND/99000004

/IWFND/99000005

/IWFND/99000006    Enable or Disable Soft State

/IWFND/APPS_LOG    SAP Gateway Application Log Viewer

/IWFND/BULK_USER_MAP    Transaction to Perform Bulk User M

/IWFND/CACHE_CLEANUP    Cleanup of Model Cache

/IWFND/CLEANUP    Execute Cleanup

/IWFND/CLEANUP_JOBS    Manage cleanup jobs

/IWFND/CRE_DEF_JOBS    Create Default Cleanup Jobs

/IWFND/ERROR_LOG    SAP Gateway Error Log

/IWFND/ERROR_LOG_E2E    SAP Gateway Error Log - E2E

/IWFND/EXPLORER    Service Explorer

/IWFND/GW_CLIENT    SAP Gateway Client

/IWFND/INIT_CCMS    Initialize SAP Gateway CCMS Contex

/IWFND/IWF_ACTIVATE    Activate / Deactivate SAP Gateway

/IWFND/MAINT_SERVICE    Activate and Maintain Services

/IWFND/MED_ACTIVATE    Activate/Deactivate Metadata Cache

/IWFND/MED_SA_ACTIV    Activate system alias based cachin

/IWFND/MOC_PARALLEL    Parallelize Multi-Origin Compositi

/IWFND/NOTIF_CLEANUP    Cleanup Notifications

/IWFND/NOTIF_MONITOR    Notification Monitor

/IWFND/SERVICE_TEST    Service Explorer

/IWFND/SOFTSTATE    Enable or Disable Soft State

/IWFND/STATS    SAP Gateway Statistics

/IWFND/TRACES    SAP Gateway Traces

/IWFND/V4_PUBLISH    SAP Gateway Service Publication

/IWFND/VIEW_LOG    SAP Gateway Application Log Viewer

/IWFND/VIRUS_SCAN    Configuration of SAP GW Virus Scan

/IWFND/WF_WEBGUI    WebGUI For Executing Workflow Item

/IWFND/WSS_SETUP    Configure WS Message-Based

SAP BackEnd  Specific T-codes:

/IWBEP/57000001    Configuration of RFC Connections    SM59

/IWBEP/57000002    Gateway Settings

/IWBEP/57000004    Event Definition

/IWBEP/57000005    Choose Activity

/IWBEP/57000006    Event Type Linkages

/IWBEP/57000007    bgRFC Configuration    SBGRFCCONF

/IWBEP/57000008    bgRFC Monitor    SBGRFCMON

/IWBEP/57000009    Check Configuration Report    /IWBEP/CONFIG_CHECK

/IWBEP/92000002    Maintain Model    /IWBEP/REG_MODEL

/IWBEP/92000003    Maintain Service    /IWBEP/REG_SERVICE

/IWBEP/92000004    Simple Job Selection    SM37

/IWBEP/92000005    SAP Netweaver Application Log Viewer    /IWBEP/VIEW_LOG

/IWBEP/92000006    Clean Up of Model Cache    /IWBEP/CACHE_CLEANUP

/IWBEP/92000007    BADI Creation    SE18

/IWBEP/92000009    Program SRT_WS_IDP_CUSTOMIZE    WSIDPADMIN

/IWBEP/92000012    BADI Creation    SE18

/IWBEP/92000013    Implementation for BADI Definition    SE18

/IWBEP/92000014    BADI Creation    SE18

/IWBEP/92000015    BADI Creation    SE18

/IWBEP/92000016    User Request Management - Application Configuration

/IWBEP/92000018    User Request Management - Cleanup Report    /IWBEP/UR_CLEANUP

/IWBEP/92000019    User Request Management - User Category

/IWBEP/92000020    Role Maintenance    PFCG

/IWBEP/92000021    Role Maintenance    PFCG

/IWBEP/92000022    Role Maintenance    PFCG

/IWBEP/92000023    Maintain Annotation Models    /IWBEP/REG_VOCAN

/IWBEP/92000024    User Self Service Remote Destination Configuration

/IWBEP/92000025    Range Maintenance : GW User Self Service    /IWBEP/UM_NR_INT

/IWBEP/92000026    Parallelization of Batch Queries    /IWBEP/BATCH_CONFIG

/IWBEP/97000002    Display Models

/IWBEP/97000003    Gateway Log Level for the Application Log

/IWBEP/97000004    User Maintenance    SU01

/IWBEP/97000005    Structure of the GW CCMS Context

/IWBEP/97000007    Generate ODATA Channel Implementation    /IWBEP/IMPORT_MODEL

/IWBEP/99000004    Program /IWBEP/R_COS_CLNUP_JOB_CREATE    /IWBEP/CRE_DEF_JOBS

/IWBEP/99000005    Simple Job Selection    SM37

/IWBEP/ANA_SRV_GEN    Analytics Service Generator

/IWBEP/BATCH_CONFIG    Batch Parallelization

/IWBEP/CACHE_CLEANUP    Cleanup of Model Cache

/IWBEP/CLEANUP_JOBS    Manage Cleanup Jobs    SM37

/IWBEP/CONF_SERVICE    Configuration for IWBEP services

/IWBEP/CONFIG_CHECK    Check Configuration of BEP

/IWBEP/CRE_DEF_JOBS    Create Default SAP GW Cleanup Jobs

/IWBEP/ERROR_LOG    SAP GW Backend Error Log

/IWBEP/ERROR_LOG_E2E    SAP GW Backend Error Log - E2E

/IWBEP/IMPORT_MODEL    Service Description File Importer

/IWBEP/NOTIF_MONITOR    SAP GW Backend Notification Monitor

/IWBEP/OCI_SRV_GEN    OData Srvc.(SAPGW)Generator for OSCI

/IWBEP/REG_MODEL    Maintain Model

/IWBEP/REG_SERVICE    Maintain Service

/IWBEP/REG_VOCAN    Maintain Vocabulary Annotations

/IWBEP/RFC_BOP_DEL    OData Channel : Delete RFC BOP

/IWBEP/RFC_BOP_GEN    OData Channel : Generate RFC BOP

/IWBEP/SB    SAP Gateway Service Builder

/IWBEP/SBS    SAP Gateway Service Builder Setup

/IWBEP/TRACES    SAP GW Backend Traces

/IWBEP/UM_NR_INT    MGW Number Range Interval

/IWBEP/UR_CLEANUP    User Request Clean Up

/IWBEP/V4_REGISTER    SAP Gateway Service Registration

/IWBEP/VIEW_LOG    SAP Gateway Log Viewer

/IWBEP/WS_BOP_DEL    OData Channel : Delete WS BOP

/IWBEP/WS_BOP_GEN    OData Channel : Generate WS BOP

[Note:]

    > While running T-codes starting with a Forward Slash '/',append '/n' before them to run the transaction

        code.

[Note:]

    > You can also create an Area Menu with these T-codes and organize them into folders,using T-code

        'SE43'(Maintain Area Menu).

Figure : All SAP Fiori T-codes organized into an Area Menu

[Note:]

    > Many of the T-codes are repeated,as they are referenced through another t-code.

    > Many of the T-codes are also referenced in the IMG Implementation Guide[SPRO] based nodes as provided earlier in the document.

Extras:

(01)How to Access SAP Fiori Launchpad and other Browser based Transactions in an SAP Fiori Deployment?:

click the link below to access the document:

How to Access SAP Fiori Launchpad and other Browser based Transactions in an SAP Fiori Deployment?

(02)How to Make Customizations in the SAP Fiori Logon Landing(Launch) Page?:

click the link below to access the document:

How to Make Customizations in the SAP Fiori Logon Landing(Launch) Page[Doc]?

(03)How to assign Fiori Launchpage to Fiori Launchpad and redirecting to it when logging off from Fiori Launchpad:

click the link below to access the document:

How to assign Fiori Launchpage to Fiori Launchpad and redirecting to it when logging off from Fiori Launchpad[Doc]?

[Note: This list will be further categorized and updated in the future]

My Travel and Expenses Fiori app was released on October 20, 2014.

Overview material

Overview presentation on all Travel Fiori apps

Detailed presentation on My Travel and Expenses app

Video My Travel and Expenses

What's new documentation - January 2015 release

Documentation on SAP Fiori app extensibility

Documentation on the SAP Help Portal

The app My Travel and Expenses enables you to create, display and submit your travel expenses. The documentation of the app on SAP Help Portal includes detailed information on key features, system landscape requirements, implementation and extensibility options.

You can also find information on UI controller hookshere.

Related apps:

With the app My Travel Requests, you can manage your own travel requests in real time using your desktop or mobile device. The app allows you to create, edit, submit, and delete requests. You can also check the status of a particular request at any time. (Documentation of the app on SAP Help Portal / Video)

The app Approve Travel Requests enables you to approve or reject travel requests in real time using your desktop or mobile device. The app provides details on each request and also allows you to view all of an employee's past requests. (Documentation of the app on SAP Help Portal / Video)

With the app Approve Travel Expenses, you can review and approve employees' travel expenses on the go or in the office. The app provides details on each receipt, and alerts you if expenses exceed the budget limits defined in your company's travel policy. You can also forward requests to another employee for approval. (Documentation of the app on SAP Help Portal / Video)

Prerequisites

Fiori infrastructure (Gateway frontend/backend, Fiori Launchpad, etc.) has already been set up.

Back-End Components Delivered with (Product Version Stack): SAP enhancement package 7 for SAP ERP 6.0 SPS07

Front-End Components Delivered with (Product Version Stack): SAP Fiori for SAP ERP 1.0 SPS05

Important: Please check SAP notes for updated information about support packages and UI builds! (also see Important Notes below)

Download the My Travel and Expenses app

Go to SAP Software Download Center -> Installation and Upgrades -> Find your software -> A-Z index -> select F -> SAP Fiori -> SAP Fiori for Suite -> select the respective app

Info about the installation and configuration can be found in the SAP Fiori apps library.

Important SAP Notes

Please make sure you have the following notes installed:

A drive through

SAP FIORI APPS

Ankit Garg

[removed by Moderator]

Contents

• Overview of SAP Fiori

• Architecture of SAP Fiori

• Types of SAP Fiori apps

• Transactional apps – Overview

• Analytical apps – Overview

• Factsheets – Overview

• Useful links

What are SAP Fiori apps?

SAP Fioriis the new user experience (UX) for SAP software. It applies modern design principles for a completely reimagined user experience. SAP Fiori represents a personalized, responsive and simple user experience across devices and deployment options.

When combined with the power of the SAP HANA platform, SAP Fiori delivers unmatched responsiveness. SAP Business Suite applications, use SAP Fiori UX to provide a personalized and role-based user experience for enterprise-wide engagement across lines of business. It provides optimal usability on multiple devices for the best business interactions and ease of use. Now SAP users can enjoy the real-time user experience.

SAP Fiori is a package of Apps designed for various LoB, scenarios. These Apps are simple to use, interactive, explanative, easy-to-navigate, and platform-friendly. These SAP Fiori Apps can be accessed by any device like Desktops, Tablets, Cellphones etc.

SAP has delivered Standard Fiori Apps for almost all possible business process. User can also configure Customized apps, if standard ones do not fulfill their requirement.

Design Principles of SAP Fiori

Components of System Landscape     

Architecture of SAP Fiori

Database

SAP HANA is an in-memory database platform that you can use to analyze large volumes of data in real-time. It was previously called High Performance Analytic Appliance. It stores data using columnar storage technique, which makes it perfect for on-the-fly reporting.

However, Transactional apps (discussed below) can be deployed on any DB, while Analytic apps and Fact sheet apps require HANA DB only. For best performance, SAP Fiori should be deployed with HANA DB.

ABAP back-end Server

The back-end server is based on SAP NetWeaver. In the ABAP back-end server, the SAP Business Suite products are installed, which provide the business logic and the back-end data, including users, roles, and authorizations.

This Server contains Virtual Data Models (VDM) or HANA LIVE, Data Providers from which data will be retrieved for the Fiori apps. This Server is directly connected to HANA DB. An RFC connection (system alias) is to be established between Back-end and Front-end Server for communication.

ABAP front-end Server

It is SAP NetWeaver Gateway having SAP UI5 and SAP Fiori add-ons. SAP Gateway is the back-bone of FIORI apps. NetWeaver Gateway is a set of ABAP add-ons to your existing SAP ERP system that provides easy access to your business information in a simple, people-centric manner and lowers the data consumption barrier to the point that no prior knowledge of an SAP system's internal workings is required.

SAP Gateway handles the communication between the web dispatcher and the SAP Business Suite back end. SAP Gateway uses OData services to provide back-end data and functions, and processes HTTPS requests for OData services. End-users access the SAP Fiori apps from the SAP Fiori Launchpad (web dispatcher). The specific UIs for the apps are delivered as SAP Business Suite product-specific UI add-on products, which must be additionally installed on the front-end server.

Web Dispatcher

It is the Fiori Launchpad where Fiori apps can be accessed by End-user through “Tiles”. It is designed using SAP UI5 framework. This Dispatcher is accessed through Web Browser using a URL. If this URL is accessed outside corporate network, make sure that connection is secure.

SAP Fiori apps are processed as follows: First, Fiori Launchpad loads the UIs for the SAP Fiori apps. Second, while running, the app consumes data from the SAP Business Suite back-end systems.

Standard browsers have a “SAME ORIGIN” policy, that is, HTTPS requests for the UI data and the back-end data must communicate with just one web address.

To meet this requirement, a reverse proxy server between Dispatcher and the SAP system must be installed. The reverse proxy server acts as the only point of entry for all HTTPS requests. Depending on the requests that the app sends, the reverse proxy server selects the appropriate application server, the ABAP front-end serve or SAP Gateway server.

Types of SAP Fiori Apps

SAP Fiori has three app types, each distinguished by their application and infrastructure requirements:

1. Transactional apps
2. Fact sheets
3. Analytical apps

Transactional Apps

These apps let you perform transactional tasks, such as creating a leave request for an employee. They represent simplified views and interaction with existing business processes and solutions. They run best on an SAP HANA database, but can also be ported to other databases with acceptable performance.

For the transactional apps, the ABAP front-end server comprises of SoH (Suite on HANA) ,which contains the UI layer with the necessary product-specific UI components for the respective products (for example, ERP Financials (ERP-FIN), CRM, SCM and so on) as well as the infrastructure components. The infrastructure comprises the central UI component comprising add-ons as SAP UI5 control library and the SAP Fiori launchpad as well as SAP NetWeaver Gateway with the OData enablement.

The front-end components have access through a trusted RFC connection to the ABAP back-end server containing the business logic in the form of VDM or Data Providers.

The SAP Web dispatcher is the entry point for HTTP(s) requests into your system. The underlying database can be an SAP HANA database, or any database.

Analytical Apps

These apps let you get a role-based insight into real-time operations by displaying key figures directly in your browser. Analytical apps combine the data and analytical power of SAP HANA with the integration and interface components of SAP Business Suite. They provide real-time information on large volume data in a simplified front end for enterprise control. With analytical apps, you can closely monitor your most important key performance indicators (KPIs) in real time and react immediately on changes in market conditions or operations. These are also known as Smart Business or KPI apps.

The ABAP front-end server contains the UI layer with the infrastructure and the necessary product-specific UI components for the respective products used. The underlying database can only be an SAP HANA database. Back-end Server contains VDM and Data Providers from which data will be retrieved.

These front-end components have access through a trusted RFC connection to the ABAP back-end server with the business logic. KPI framework includes some roles which have to be assigned in order to configure KPI Modeler. Generally a separate user is created to configure KPI apps to which KPI roles are assigned. Once this is done, you can configure Analytic apps through web dispatcher in your browser.

HANA XS is a small-footprint application server, web server, and basis for an application development platform - that lives inside SAP HANA. The HANA XS Engine also contains the SAP Fiori app content for the different Business Suite products and the SAP Smart Business component with the KPI modeler as well as the Virtual Data Model (VDM) reuse content.

SAP has provided a feature of “Drilldowns” in order to analyze business based on By region, By Country, By Company Code, By Customers etc. In addition to it, you can restrict users to see specific apps. One or more Datsources can be used for single Analytical app.

SAP Analytical Apps Landscape

Factsheets

These apps display contextual information about central objects used in your business operations. Fact Sheets display master data or business documents in display mode. Fact Sheets are accessed from other apps like Analytical Apps by using app-to-app navigation in Fiori launchpad. Also you can search master data or business documents in the Fiori launchpad like google search. Facts Sheet is displayed by selecting the search result.

The architecture is somewhat similar to other apps. In addition, Factsheets require ABAP stack and Fiori Search enablement. For implementation, please follow links in the end of this document. This search is like google search which displays records when searched for a specific data, which is directly retrieved from SAP HANA.

For example, if you search material no. “CH003”, in search bar of Fiori launchpad, all documents (Business Objects) containing this material no. will be displayed. Select a particular entry, you can drill down to know underlying information such as locations where this material is sold, name of Top 10 buyers of it etc.

The ABAP front-end server contains the UI layer with the infrastructure and the necessary product-specific UI components for the respective products used. These front-end components have access through a trusted RFC connection to the ABAP back-end server with the business logic. These apps works only with HANA DB. Search models make Business Objects searchable during Fiori Search. For this, Software component has to be enabled, the steps are mentioned in the Useful links.

The SAP Web dispatcher selects the appropriate server for HTTP(s) requests by means of proxy server and request the search models from back-end server.

SAP Factsheets Apps Landscape

Useful links

https://support.sap.com/content/dam/library/SAP%20Support%20Portal/support-programs-services/solution-manager/integrated-tools/sap-fiori-for-sap-tdms1.0/tdms-fiori-config-quickgude.pdf

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/

http://help.sap.com/fiori_bs2013/helpdata/en/12/af5252b10d5a64e10000000a423f68/content.htm?frameset=/en/25/4a4c52eea9c871e10000000a44176d/frameset.htm

http://help.sap.com/fiori_bs2013/helpdata/en/de/f9b152d7d3215ce10000000a44538d/content.htm?frameset=/en/89/3449526f7fd030e10000000a44538d/frameset.htm

https://help.sap.com/saphelp_nw73/helpdata/en/b6/e51604ca9a480bb8d58111a837b4ae/content.htm

Hy,

i had the requirement to remove the number from a Fiori Launchpad Tile. I haven't found a working solution in the standard dynamic tile component.

what i did to get the result:

- implemented custom tile type

- in xml view - generic tile - numeric content - set property nullifyValue to false.

- oData service implementation with NW GW for dynamic data url customizing in the launchpad admin.

<core:View xmlns:core="sap.ui.core" xmlns:mvc="sap.ui.core.mvc" xmlns="sap.suite.ui.commons"  controllerName=".main" xmlns:html="http://www.w3.org/1999/xhtml">  <GenericTile  header="{/data/display_title_text}"  subheader="{/data/display_subtitle_text}"  size="M"  frameType="OneByOne"  press="onPress">  <tileContent>  <TileContent footer="{/data/display_info_text}" size="M">  <content>  <NumericContent nullifyValue="false" size="M" value="" icon="{/data/display_icon_url}" />  </content>  </TileContent>  </tileContent>  </GenericTile></core:View>

Is there a better solution within the standard dynamic tile?

Thanks for your comments & improvements.

I'm looking forward to get input from the community.

Have a nice day.

Regards,

Michael

Introduction : The documents gives a quick insight into services used by Launchpad and Launchpad Designer the respective user and admin roles. I noticed that there is a overlap between the services used by Launchpad and Launchpad Designer the respective user and admin roles, so collated the information in a single view for quick and easy reference.

Target Audience : SAP Fiori Consultants

Date Published : 22 Jan 2016

The below table gives a very quick insight into the services used by Fiori Launchpad, Fiori Launchpad Designer, SAP_UI2_USER_700 role and SAP_UI2_ADMIN_700 role.

Please note that the /UI2/INTEROP service is used both the Launchpad and the Launchpad designer.

SAP_UI2_ADMIN_700 role as seen in PFCG transaction

With this role administrators can execute the SAP Fiori launchpad designer.

SAP_UI2_USER_700 role as seen in PFCG transaction.

With this role the user can execute the SAP Fiori launchpad on the Personalization level.

For example, users have the following options:

• Adding tiles
• Deleting tiles
• Navigation
• Create groups
• Personalize tile position

With this role the user does not have any authorization to execute the SAP Fiori launchpad designer.

SAP_UI2_ADMIN is a composite role containing the following release-dependent roles:

• SAP_UI2_ADMIN_700 for SAP NetWeaver 7.0
• SAP_UI2_ADMIN_702 for SAP NetWeaver 7.0 enhancement package 2
• SAP_UI2_ADMIN_731 for SAP NetWeaver 7.0 enhancement package 3 and SAP NetWeaver 7.3 EHP 1

The services have to be activated through SICF transaction when required.

Right click on the service and activate.

Miscellaneous

SICF services that need to be activated for SAP Fiori Launchpad :

• /default_host/sap/bc/ui2/start_up
• /default_host/sap/bc/ui5_ui5/ui2/ushell
• /default_host/sap/bc/ui5_ui5/sap/arsrvc_upb_admn
• /default_host/sap/bc/ui5_ui5/sap/ar_srvc_news
• /default_host/sap/bc/ui5_ui5/sap/ar_srvc_launch
• /default_host/sap/public/bc/ui5_ui5/
• /default_host/sap/public/bc/ui2/
• /default_host/sap/bc/ui2/nwbc/ for NWBC for HTML

Links

Authorizations

http://help.sap.com/saphelp_nw74/helpdata/en/86/fa207d3edd4ed987e66b547d1b3025/frameset.htm

Activating OData Services

http://help.sap.com/saphelp_uiaddon10/helpdata/en/84/33ff5551a349c4bb4df90c2fcfd96f/content.htm

SICF Services that need to be activated for SAP Fiori Launchpad

http://help.sap.com/saphelp_uiaddon10/helpdata/en/3b/794d91f25a4bf9a93e432a41896641/content.htm

Introduction : Recently I have been reading a lot of SAP Documentation (SAPX03, SAPX11 etc) and found a lot of TCODEs scattered across the documents, so thought of collating them in a single place for reference and share with you too. The document presents a collection of  TCODEs that are used at different points during SAP Fiori Administration and related activities.

Target Audience : SAP Fiori Consultants

Date published : 1 Feb 2016

Note for readers : Please do let me know if any mistake has crept in or if you would like to see any more TCODEs added to the list via your comments.

Administration related

PFCG : role maintenance administration to manage roles and authorization data. Also assign catalogues and groups to a role etc

SICF : activate ICF services

SM59 : define RFC connection towards target system to be enabled as trusted in source system

SICF_SESSIONS : activate HTTP security session management

SAPUI5 related

SE38 -> /UI5/UI5_REPOSITORY_LOAD : Upload/Download SAP UI5 applications

LPD_CUST : register a UI5 application

SAP Gateway/OData Services related

SE11 : ABAP data dictionary, you may have to include structure to extend an OData service

SE80 : Access BSP applications that contain SAPUI5 applications

SEGW : Generate Odata services from DDIC, BOR or RFCs

/IWFND/GW_CLIENT : execute OData Services

/IWFND/MAINT_SERVICE : register newly created custom OData service

/IWFND/CACHE_CLEANUP : clear Gateway cache on changing model

/IWBEP/CACHE_CLEANUP : clear Gateway cache on changing model

/IWFND/MED_ACTIVATE : to activate or deactivate the cache. Caching should be disabled in Development systems and enabled in Production systems

Semantic Objects related

/UI2/SEMOBJ_SAP : list of all sematic objects

/UI2/FLIA : display semantic objects and action pairs in use

Theme Designer related

/UI5/THEME_TOOL : tool for Customer Themes Maintenance

/UI5/THEME_DESIGNER : launch Theme Designer

Troubleshooting related

/IWFND/APPS_LOG : find structure that causes problem

/IWFND/ERROR_LOG: error logs related to OData service

SITSPMON : clear ITS cache

Connector Cockpit related

ESH_COCKPIT : launches connector administration cockpit

How to assign Fiori Launchpage to Fiori Launchpad and redirecting to it when logging off from Fiori Launchpad:

> The best way to access SAP Fiori Launchpad by the end user should be through the Fiori Login Launchpage. If this is not set,you will get an error message as given below.

Figure : Error Page when logging off from Fiori Launchpad

Before we proceed with list of steps that are to be done,first have a look at the flow of accessing and logging off from the Fiori Launchpad diagram below.

Illustration : Fiori Launchpad Access Flow

In order to set its access through Fiori launchpage,we need to access the Fiori Launchpad Service,which can be found in the following path in SICF:

     default_host > sap > bc > ui2 > flp

Double click the 'flp' service and you will be in the 'Create/Change a Service' screen. Click the 'Error Pages' tab and then in the sub tab 'Logon Errors',select the radio button 'System Logon'

Figure : Configuring the Launch page service 'FLP' in Fiori LaunchPad in transaction SICF

and click the 'Configuration' button[]. A 'System Logon Configuration' pop-up will show up.

Figure : Setting Up the Logon class '/UI2/CL_SRA_LOGIN' in custom configuration

Select the 'Define Service-Specific Settings' radio button and the select the 'Custom Implementation' radio button and provide the following class in the ABAP Class input field '/UI2/CL_SRA_LOGIN' and then click the 'save' button[] to save the changes. you will be prompted for saving it to a Workbench Transport request.

For Log off page,we can do the same using the following path in SICF:

    default_host/sap/public/bc/icf/logoff

the service name here is 'logoff'

The first step of assigning system logon configuration in the Error Pages tab is the same as done for 'flp' class given above.

Additionally In the 'Error Pages' tab and under the sub-tab 'Logoff Page',select the radio button 'Redirect to URL' and provide the following URL in the 'Redirect' Input field '/sap/bc/ui5_ui5/ui2/ushell/shells/abap/Fiorilaunchpad.html'

Figure : Setting Up Landing Page Redirection on 'logoff' Service in SICF

This way when the user logs off the Fiori Launchpad,it will show the Fiori Launch page,instead of the error message.

[Note:]

To make customization in the Fiori Launchpage itself and for a complementary document to this one,refer to the following link:

How to Make Customizations in the SAP Fiori Logon Landing(Launch) Page?

[Note:]

Understand what it takes to extend Fiori My Inbox; how to get the most from the Extensibility Cookbook; and learn from our missteps.

Fiori My Inbox - The Challenge

Murali Shanmugham and I wanted to share our experiences in implementing and extending My Inbox for a Proof of Concept at one of the Australian public sector agencies.

What we did: We extended the Fiori My Inbox App to include line items for both ECC FI Journals (preliminary posting docs) and SRM Shopping  Cart Approvals.

Why we did it: This provided a one stop mobile approvals user experience for managers who need to be able to approve anywhere anytime.  The managers in the pilot group were particularly mobile.  They were reported to be at their desks less than 1 hour per day.  In addition many of these approvals were urgent - purchases were often reactive to rapidly changing circumstances.  So success criteria included:

• Speed (minimum clicks & good performance);
• Simple "don't make me think" user interface;
• Phone/tablet/desktop responsive.

What we want you to know: It also turned out to be a great example of how to get the most from the Extensibility Cookbook for Fiori My Inbox.  And also how to approach extending My Inbox from a UX (User Experience) - not just a UI (User Interface) - perspective, even when the conditions aren't ideal.

As an added bonus we were able to extend Fiori My Inbox WITHOUT CHANGING THE CUSTOM WORKFLOWS AT ALL!  That was a huge winas it meant no significant change for business or IT support staff - reducing risk and change management costs.

What we'll show you: 

• The difference between My Inbox Out of the Box (OOTB) and our final extended version
• How we approached the project - making sure we considered UX not just a UI
• The major steps: Installation, Configuration, Extension
• Lessons learned and what we'd do differently next time

Fiori My Inbox OOTB: Custom Workflows from Multiple Systems

The below screen capture shows the look and feel of the standard Fiori My Inbox app out of the box.  In this screenshot you can see this is a custom workflow.

Yes that's correct - Fiori My Inbox does support custom workflows right out of the box! 

It also provides out of the box support for workflows from multiple backend systems as well. This was good news for our scenario as we were working with ECC and SRM backend systems.  The subject, long description, due/created dates, status, priority, and previous processor are all shown much as in any workflow inbox.

A particularly nice feature is the green ("Positive") and red ("Negative") colouring to reinforce approve/reject buttons.  This is very simple to set up via the standard My Inbox configuration.

The final icon button is used to send an email.  We kept this as a contact the author or contact support feature.  It dragged the subject text and a few other details into the email - enough to make it useful.

In the same button toolbar that holds the Approve all Items and Reject all Items buttons, note the "Open Task" icon button which applies the standard task launch. The standard task launch is typically whatever is configured in transaction SWFVISU - Task Visualization for the relevant task.  Now this could go to any web-capable user interface such as SAPGUI for HTML or Web Dynpro ABAP or SAPUI5.  But not all of the SWFVISU options are suitable for tablet and smartphone use.

To make the inbox suitable for tablet and smartphone, we need to extend the inbox to override the Open Task button with a more responsive design.

Fiori My Inbox - Extended

The following screen shots show our final extended version.

What we changed:

• Master List - include additional info such as amount
• Group By/Filter/Sort by additional info in the master list
• Specific Task Detail user interfaces for each task
• For Journals - configured standard approve/reject options
• For Shopping Carts - extended the Task Detail to enable line item approval
• Remove unnecessary icon tabs - such as processing log and history
• Remove unnecessary workflow features - such as Release Forward, Suspend
• Added mass approval/reject options using the standard Multi-Select button on the master list

First the Journal work items. The approver can see the essential journal details including all the journal line items directly in the task details pane.  We've even aligned the debit and credit columns so the approver can see at a glance how the journal is balanced. We've also removed unnecessary tabs and action buttons.  The underlying task in the custom workflow was a User Decision.

Now with financial journals there are always lots of number codes - for G/L accounts, cost centres, funds, tax codes, project (WBS) codes, etc.  The users told us that over time they became very familiar with their codes. But of course for newbies they can be hard to remember.  So we have provided the line item expand ">" option to let them check what all those codes mean. And in the top right hand you can see the up/down arrows so they can move from one item to the next/previous without having to go back to the main journal display.

We also added a new task detail display for the Shopping Cart approvals. 

Here the My Inbox Extensibility Cookbook was especially helpful because it uses the shopping cart as an example - including showing how to do the line item approval. 

We took it to the next level by: removing unnecessary tabs and actions, and adding the line item expand ">" option to show the accounting information which might be to single or multiple cost objects.

Here again there are potentially a lot of cost objects. One line item can even be assigned to multiple cost objects.  So again we pushed the detail out to an optional user interface accessed by expanding the line item via the ">" symbol at the end of each item.

If you look closely at the screenshots you will also see we adjusted the master list itself.  Because the managers primarily approved financial information it made sense to add the value of the journal or shopping cart into the master list. For instance we allowed the manager to filter by value.

We also completely reworked the subject text - there's a standard BADI provided as part of the My Inbox solution for this purpose. We added some additional attributes to the master list to make it even more useful - the blurred section is the name of the person submitting the journal or shopping cart.

Where we started: Treat it as UX not UI

We were keen to make this a User Experience project - not just a User Interface project - to achieve the best possible result. 

So even given tight timeframes and a small team, we worked at approaching it from a UX perspective to ensure we maximized success for the end users and the business outcomes.  So we followed the UXaaS Discover > Design > Deliver lifecycle as seemed appropriate to the scope, context and audience - including allowing for some iteration.

Now we are not saying the UXaaS lifecycle flow was ideal - there was no design thinking; no low fidelity wireframes; limited solution validation; and no access to the UXaaS tools provided by HCP.  Culturally UXaaS wasn't on the radar of the organisation yet either. Sometimes that's just the way it is when you are doing a proof of concept.  But despite these challenges were able to draw on the UX approach as much as we deemed appropriate to the circumstances.

It is our belief that approaching the problem from a holistic User Experience perspective made all the difference in getting the Proof of Concept to the next stage of consideration. 

In fact taking the UX perspective changed not just what we designed and delivered - it changed our whole view of the problem. 

Discover: Existing Problems and Challenges

From the beginning the current user experience pain was clear.  Both business and IT support raised numerous challenges.

The existing solution was web-based and ostensibly created to be simple - but it was fairly evident that somewhere along the line the voice of the end user had been left out.

Most important pain points to overcome to improve the user experience were:

• Undesirable delays - part of the solution included an overnight replication of some of the data - this meant that same day approvals were sometimes impossible as the data wasn't there to support it
• Poor performance - a summary icon button that caused a spinning wheel of death for any shopping carts with a large number of items
• Information overload - too many buttons, too many features, too much poorly understood technology

There were also some serious support challenges.  IT Support reported that they were often requested to manipulate the org structure to find alternative approvers. Sometimes they were also asked to reassign work to alternate approvers. The org structure manipulation caused undesirable impacts on other workflows such as the same alternate approvers being accidentally identified as the approver of other workflows.

So how did we approach the problem? First target was getting the voice of the end user back into the solution.

Discover: the End User Voice is Critical to Solving the Right Problem

A bedrock of User Experience is to deliberately consider the perspective of the end users themselves.  As this was a proof of concept and the UX perspective was new to the organisation, access to end users was limited. Even so we took every opportunity to listen to and observe as many users as possible.  Where we couldn't reach the end users themselves we talked to people who had met with them in their workplace.  We even talked to some users over the phone.

Any contact with end users is better than none.  In fact if we hadn't talked to the end users we might have solved the wrong problem!

Initially we had talked to the IT Support team about the type of support incidents that were being raised and the impact of the user behaviours they had seen.  We also conducted workshops with key stakeholders and business analysts to understand the initial requirements. That helped us identify the workflows, tasks and people affected; and the gaps in the standard solution. We identified the different task types to be shown in the My Inbox app; and worked through what information needed to be shown to the approver.

But even our limited contact with end users gave us a very different view of the problem and much greater insight into their user experience.

Observing end users makes the difference between understanding the symptoms and the cause. 

The challenges the IT Support team and Business reported were valid - but we quickly realised those challenges were mostly symptoms rather than causes.  To get to the causes we needed to look to the current user experience of end users.

For instance, IT Support saw lots of examples of users trying to twist the system into knots to set up alternate approvers for their workflows.  When we talked to the users why they were doing this became clear. The end users weren't really interested in finding alternate approvers - they were just trying to get their journals and shopping carts approved - many of which were urgent. The real problem was that the current solution was desktop based, but the managers who needed to approve journals and shopping carts were extremely mobile.  They simply weren't at their desk often enough to deal with all the approvals in a timely manner.

That critical understanding changed our whole view of the user experience.

For starters it was clear that a mobile solution was crucial to a good user experience.  It also opened up opportunities to suggest features which had not initially come out of the workshops.  Such as the adjustments we made to the master list to make it easier for the approver to prioritise their work on the fly.

Design: Agree on the UI design.. and be Prepared to Iterate

One of the nice things about starting with existing Fiori apps is that you have a baseline for the design.  In our scenario we actually looked to two existing Fiori apps - Fiori My Inbox and Approve Shopping Carts.  What was needed was one central inbox for all approvals, but with the Task Detail screens extended for each task.  The Fiori My Inbox extensibility cookbook in SAP Note 2118812 - How to extend Fiori My Inbox shows the extension options.

Particularly useful for communicating within our own team was Appendix D - which shows what can be customized without extension - just using the normal configuration.  We also had some screen shots highlighting in a similar way what can be changed in Fiori My Inbox.  These we were able to source from conference presentations  on My Inbox - but they are pretty easy to draw up yourself.

NOTE: We considered it important that we not to distinguish between configuration or extension for workshop participants - many of whom were our stakeholders. We just needed to be clear what could be changed and what would stay the same.

So from a design perspective we ran our workshop this way:

1. Here's the standard Fiori My Inbox functionality and where we can extend it
2. Here's an example of a tailored screen for approving shopping carts
3. Let's talk about how we merge these together
4. Let's talk about what you would need to see for approving journals
5. What else needs to be added or removed to make the inbox useful and as simple as possible

Granted this is not a full start-from-scratch UX design - but it is a valid approach when adapting existing apps.

We came out with a set of mock up slides showing our design.  Essentially a high fidelity prototype.

We did iterate our design... Part the way through our delivery we realised that making the changes was going to be easier than we first thought, and we looked for further improvements we could add into scope.   A number of changes to the master list came about during the iteration.

We used MS PowerPoint (PPT) at the time to create mock up screens and validate the design. It was too early to get access to BUILD then... but we would have loved to use it instead - PPT worked but was a little tedious.  And being able to distribute the design as a user study would have made the feedback process easier.

Deliver: Verify your Fiori app installation

Early on we realised we needed to install both a Fiori landscape - Gateway, Fiori Launchpad, etc. -  and two Fiori apps.

Even though we were only going to give the users one end result it was still useful to provide the Fiori Launchpad to explain how the UX would scale over time.  The FLP is also handy for showing how you will integrate apps into existing Portal, Business Client, or other entry point.

Why two (2) apps? By installing both Fiori My Inbox and Fiori Approve Shopping Carts we were able to reuse some of the underlying components from the OData Services of Approve Shopping Carts in building our final solution. It was also very helpful to have both OOTB versions of the apps working as a comparison to our final runtime app.  If it worked in the original app but not in our final version yet, then we had something to guide us in our troubleshooting.

Later the approve shopping cart apps also gave us a pattern for creating the task details for the financial journals - for which there were no OData Services available.

Before we started we verified the software components were being installed are in the right version. As per recommended practice for Fiori we set up the Gateway in hub mode as the Fiori frontend system, connected to our two backend systems ECC and SRM.

Most importantly, we implemented all the relevant SAP notes both for the Fiori Apps and also the related SAPUI5 framework. This meant applying SAP Notes to both the Gateway and in some cases to the backend systems.  Much better to get the apps and the framework in the best possible state from the beginning, than waste time rediscovering problems that had already been fixed in standard.

A starting point for this is SAP Note 2106212 Release Information Note for SAP Fiori My Inbox.  This note consolidates a lot of the fixes for My Inbox.

NOTE: As we were aiming for a mobile responsive solution another note that was important was SAP Note 1935915 Fiori for Business Suite: Browser / Devices / OS Information. We didn't need to wait for the mobile configuration to be completed to verify our installation.  A lot of the mobile set up was done in parallel with configuration and extension.

We followed the standard guides and instructions to register the /IWPGW/TASKPROCESSING (version 2) OData service and activate the standard Fiori My Inbox App.

Once everything was installed and before making any changes or doing anything more than the absolute minimum configuration we verified the standard apps were working as intended OOTB.   For My Inbox minimum configuration primarily involves setting up the connection from the Task Processing Services in the Gateway to the two backend systems. You don't even need to configure the workflows and tasks at this point.

My Inbox is great for this OOTB verification approach because the moment you configure the My Inbox app to connect to the backend systems all the work items of the user are immediately brought into the inbox. If your workflows are already running in the backend system, they will start working straight away after configuring the MyInbox App. It doesn’t matter if they are SAP Standard Workflows or custom workflows.

We tried all the standard features to confirm they were working as expected.  That also helped us reconfirm the changes we needed to make based on our agreed Design.

We recommend the SCN collaborative document on SAP Fiori - My Inbox as it highlighted several other SAP Notes we should look at to maximise the OOTB functionality.

Good notes to look at include:

• Any SAP Note mentioning the keywords "Task Gateway" - these relate to the OData Services in Gateway that support handling of Business Workflow, BPM and 3rd party provider tasks
• Any SAP Note mentioning CL_WAPI_MOBILE_INBOX - this is the underlying ABAP Class used to flexibly extract workflow and work items in a lightweight manner
• Any SAP Note mentioning the keywords "My Inbox" - these include backend workflow system adjustments to ensure data is passed correctly to/from the Task Gateway
  
• Notes in the Fiori My Inbox application component CA-INB-FIO
  

Jocelyn's personal tip here is to track the list of SAP Notes you are applying somewhere... there can be quite a few and having to find the note you are looking for in the SNOTE browser is not fun.  Similarly we tracked what OOTB features and functions we tested before and after the initial installation, configuration, and extension.   A simple spreadsheet or project task schedule highlighting what's working and what's not helps you coordinate team efforts on what still needs to be done.

Don't forget to capture your URL links for accessing the app(s) directly and the Fiori Launchpad itself internally and externally.  These are a pain to keep typing in, especially on mobile devices.  Much easier to copy and paste into an email or dropbox or similar and share them between desktop and device that way.

Deliver: Maximise use of the delivered Fiori app

It’s important to understand that most of the functionality provided by MyInbox App is out of the box.

Even OOTB, an Approver can see all their work items in the inbox and action them.  That includes adding notes and attachments and all the other usual workflow features that My Inbox supports.

We made the most of the available configuration including the BADI exits.  Just using the configuration we were able to significantly adjust the inbox in the following ways:

• Assign positive/green and negative/red colours to certain buttons
• Adjust the subject text of the work items using a BADI
  
• Create a Submit button for the Approve Shopping Cart tasks
• Assign an action to buttons we wanted to support in Multi-Select mode - such as Mass Approval for financial journals and for shopping carts

Mass approval is OOTB for User Decision tasks such as the Approve Financial Journal.  Even the buttons are created automatically.

For Shopping carts we needed to use the BADI to associate the underlying code with the relevant button.  Because we had implemented the Approve Shopping Carts app we were able to largely reuse one of its functions for this.  We created Approve All Items and Reject All Items buttons for multiselect mode of Shopping Carts.  We also added a Submit button that we would later use to submit the line item approvals for the extension.

All the available BADI’s are listed in Fiori My Inbox extensibility help  It’s easier to use the  logic in these BADI’s to customize the UI rather than changing them either in the OData service methods or the SAPUI5 project.

BADI (/IWPGW/BADI_TGW_TASK_DATA) let's you change the Task subject. 

BADI (/IWWRK/BADI_WF_BEFORE_UPD_IB) lets you add code against the multiselect actions for Tasks.

We recommend the SCN collaborative document on SAP Fiori - My Inbox was very useful in supporting the official SAP Library and Fiori Apps Reference Library help for the My Inbox app. Between these resources it is easy to find both instructions and examples of configurations.

Make the most of the My Inbox Extensibility Cookbook and Extension Guides

The My Inbox Extensibility Cookbook can be found in SAP Note 2118812 How to Extend SAP Fiori My Inbox.

The cookbook uses Shopping Cart Approvals as an example - showing how to tailor the Task Detail screen to add item approvals. We used the Cookbook both as a starting point and as a reference. The cookbook even shows how to reuse some of the APIs from the Approve Shopping Cart app.

For example, we had to show Shopping Cart Items in the Task Detail of an Approve Shopping Cart task complete with options to approve or reject individual items.  The information we need to show was a subset of the information seen in the specific Approve Shopping Cart app.  We actually needed to show more than was given in the My Inbox Extensibility Cookbook, but less than the Approve Shopping Cart app.  So it was good to see how the details were exposed in the OData Services behind both apps to guide our final solution.

We used a similar approach for adjusting the financial journals display.

One big lesson learned here was to look under the covers of the existing OData Services for best practice clues.

First iteration of the financial journals we used a function module to get the work item details.  When we cross-checked with the Approve Shopping Carts OData Services we realised we should instead use classes such as CL_WAPI_MOBILE_API and CL_WAPI_MOBILE_INBOX.  These classes allowed us to apply some of the secondary features efficiently - such as filter/sort/group by.

We didn’t have to change any of the existing custom workflows or do any sort of changes in how the workflow found the end users as recipients.

The workflows had already been running successfully for many months.  We were able to extract what we needed to show, or to derive what we needed to show, from the existing container elements of the work item.  Because this information was already a part of the workflows we didn’t need to modify any of the workflows.

In the end we really didn’t add much functionality apart from the Task-specific detail displays, the item level approval, and the master list changes.  Based on the design workshops it was more important to simplify the inbox by hiding buttons and tabs that were superfluous to requirements.  We removed most of the buttons and only kept Accept/Reject/Submit buttons we had configured and the out of the box Send email button.

Since there is an extension required for the Standard My Inbox App, create a custom OData service redefining the standard service and likewise create a custom SAPUI5 project which extends the standard My Inbox App. There are plenty of resources available on SCN which will help you in extending standard Apps.

It’s very important to plan how you extend the Fiori App. Since MyInbox App can handle multiple task types from several systems, you need to come up with an elegant way of extending it. That's important to make sure the app remains easy to support and maintain as more task types are added. Below is the approach we took based on the cookbook recommendations, but there are other ways of achieving the same ends.  We would have liked more time to explore some alternative approaches - already some of the latest information on Smart Templates and Annotations shows promise.

For each Task type, we created a separate detail view. Based on the type of Task selected in the master list (S2), the corresponding set of views are loaded in the detail section using the routing rules.  In other words every time you add new task type you create a Task-specific detail view for the new Task type.  The Task-specific detail view is displayed when the a matching task is selected in the master list (S2).

Test the application across devices through the eyes of a real user

Once the My Inbox app configuration and extension is complete, make sure you test it in various browsers and devices which are allowed for the user base.

Test the app in each device as if you were the end user. 

In our first iteration since we had been extending the app and testing it using a desktop, the layouts were not perfect when viewed on a mobile phone.  So we added responsive features to few element to ensure that the most important fields are shown properly.

For example, on the detail screen we had a table with 5 columns. When using a mobile device in portrait mode, the table becomes responsive and shows only those columns which are important. You can reference how to add table popins from SAP Help

Other Tips and Lessons Learned

Consider disabling calls which are not required to improve performance.  This may include calls in both the frontend Gateway OData Services and in the backend business logic called by the OData Services. For example, if you are hiding the icon tab Processing logs, it’s very easy to hide the control. But most of us forget to disable the calls related to the Processing logs tab. Remembering to comment out or skip unneeded calls improves the performance of the app significantly.

Understand your stakeholders.It’s easy to scuttle a project - especially a proof of concept - by having the wrong conversation with the right people.

• End users don’t need proof of how much you have done to take it from standard inbox to extension – that just makes it look hard. The conversation with end users should be about whether it fits the need.

• Business stakeholders need to understand how the solution delivers on the promise of business outcomes - such as numbers of clicks saved and reduced training needs.

• IT stakeholders needs to know what’s involved in the technical architecture and how to support it.

If we had our time over ... what would we do differently

Number one priority is: More time with more end users.  We would love to have explored ways to make the accounting objects more comfortable for casual users in particular.  This is something we added into planning for the next stage.

Add metrics to measure UX success. Its easy enough to gather statistics such as the number of button clicks before/after, but we would have liked to quantify these similar to how this is done in the UX Value Calculator.

Better prototyping tools definitely.  Doing it in PPT was workable but rather tedious.  We would have loved to use BUILD if we had had access to it at the time.  If you are keen to know more about BUILD, you can find it at https://experiencesplash.com .  There are also blogs on SCN such as How to build a UI5 prototype with BUILD and publish to SAP WebIDE and on the SAP UX Design site at  https://experience.sap.com/tag/build/

Rethink the Gateway Service Design. If there's one area where we think the Extensibility Cookbook could be improved, it's in a more scalable Gateway Service Design. Some of the latest information coming out with respect to Smart Templates and Annotations would have been very helpful.  The way we did it worked... but if you had a lot more tasks to implement a better Gateway Service Design would be beneficial in scaling the solution to even more tasks.

And of course now Fiori My Inbox 2.0 is here SAP Fiori My Inbox 2.0 : Features... we would love to have added that functionality as well ...

Ah well.. you always have to leave something to look forward to. 

We hope we have inspired you to give it a go and wish you all the best for your Fiori My Inbox project!

Hi Folks, reason behind to create this document is I struggle lot to get the clear picture on Additional Information parameter and  Component parameter in Source of Navigation Target in Launchpad Designer.

First thing, how to deploy Custom SAPUI5/FIORI app into Fiori Launchpad. We have great and best document created by Babu Ganesh V(listed in sources list in below).As a viewer of this document am not able to provide the information in "Additional Information" parameter. And same as well as "Component" parameter. Why am specially talking about Component parameter in this LPD_CUST role. Actually we can bring the Custom SAPUI5/FIORI app into Fiori Launchpad with out creating an entry in the LPD_CUST. I have tried both, in both ways these two parameters are mandatory without specifying these parameters app will not run through Fiori Launchpad even we cannot save the configuration.

Before going to conclusion i need to brief out on which basis am concluding this solution.

I followed below sources, please go through the sources

How to get your SAP UI 5 apps to work like SAP Fiori Apps in SAP Fiori Launchpad

How To Deploy an SAPUI5 App On Fiori Launchpad

How to Deploy a custom SAPUI5 on Fiori Launchpad

at last when I was struggling with this issue I found one thread(Re: Could not start the app due to an internal error) in our community, after read all these sources I  came to know we need to provide namespace(name of the project) in either "Additional Information" or "Component" parameters. Please find below images for the reference.

Actual Image:

Example Image:

if you see the "Example Image" there I marked my application Namespace.

For example,

your developing one custom SAPUI5/FIORI app, while creating this app definitely we need to provide project name/namespace. Once you created the project open the Component.js file(I hope developed know about this js file) inside the file you can find the code as shown in above images from that code you come to know what exactly you need to provide in the either "Additional Information" or "Component" parameters.

Thank You.......

Best Regards,

Kiran.

Hi All,

Cache issues are very common in Fiori app development. Please make sure to follow all below steps to verify all crictical changes.

There are various modules involved in Fiori development and we need to make sure that cache in all these components have been cleared to avoid to any issues.

1. 1.Clear the server http cache

Go to the transaction SMICM. Goto -> HTTP plugin -> Server cache -> Invalidate Locally and Globally.

1. 2. Clear metadata cache

Transaction: /IWFND/CACHE_CLEANUP on Gateway (oData cache clearing)

Transaction: /IWBEP/CACHE_CLEANUP on Backend and Gateway (oData cache clearing)

1. 3. Synchronize chip cache

Run the report /UI2/CHIP_SYNCHRONIZE_CACHE. Make sure there is no error in the table /UI2/CHIP_CHDR

Run the report /UI2/DELETE_CACHE_AFTER_IMP.

/UI2/DELETE_CACHE

1. 4. Run cache buster

Run the report /UI5/UPDATE_CACHEBUSTER.

1. 5. Clear local browser cache - to avoid views and resources being displayed from local browser cache or else implement cache buster

     1.6  UI2 Cache

     Run report /UI2/INVALIDATE_GLOBAL_CACHES. This cache clearing is mandatory especially to verify the translations integrated for ex tiles,groups,catalogs in Launchpad admin

     1.7 Fiori client app is capable of handling local cache whenever new resources are available in the server so no need of manual cache management implementation

Please make sure that you follow all above cache maintenance techniques wherever and whenever required.

Thanks for reading my post.

Regards,

Arun.

Category: Fiori Technology

This is a collaborative document to share lessons learned content for the SAP Fiori Overview Page in the community SAP Fiori.

Please feel free to insert the link of your document or blog by selecting the edit button from Actions.  You can also search information and open a discussion if you can't find required information. Please don't forget to put the tag fiori.

SAP Fiori Overview Page (OVP) provides a new interaction within SAP Fiori UX. The OVP can be seen as a step between the basic information on the SAP Fiori launchpad and the full blown information within the SAP Fiori applications. While simultaneously presenting the big picture in a glance, business users can focus on the most important tasks enabling faster decision making as well as immediate action.

New and Updated:

• YYYY-MM-DD Please share your documents and blogs.
• 2015-12-17 SAP Fiori Overview Page - Frequently Asked Questions - New version 2016-02-22
• 2016-02-05 How to make your OData entities work with the Fiori Overview Page and Cards leveraging the new SAP Web IDE annotation modeler by Frank Schuler
• 2016-01-29 Steps to Create Analytic card on overview page using northwind odata service (V3) in web ide.   by  abhishek lohiya
• 2016-01-11 SAP Overview Page List Cards Examples by Dusan Sacha
• 2015-11-16 SAP Fiori Overview Page - What's Available with the First Release?
• 2015-10-25 Introducing SAP Fiori Overview Page: Card-based Information Visualization by Raz Korn
• 2015-10-19 Customer Influence: Enroll to SAP Fiori Overview Page CEI
• 2015-10-15 The SAP Fiori Overview Page has been added to the UX Explorer! by Raz Korn

Introduction Video:

Getting Started with SAP Fiori Overview Page:

• SAP Fiori Overview Page - Frequently Asked Questions
• SAP Fiori Overview Page online help
• SAP Fiori Overview Page Web IDE plugin online help
  • Prerequisite: HCP account with SAP Web IDE - For more information: SAP Web IDE - Enablement

SAP Documents:

• SAP Fiori Overview Page - Frequently Asked Questions
• Introducing SAP Fiori Overview Page: Card-based Information Visualization
• UX Explorer: SAP Fiori Overview Page
• SAP Fiori Overview Page for Developers - Architecture Overview

How to Guides:

• How to setup the SAP Fiori Overview Page
• SAP Overview Page List Cards Examples by Dusan Sacha
• Steps to Create Analytic card on overview page using northwind odata service (V3) in web ide. by abhishek lohiya
• How to make your OData entities work with the Fiori Overview Page and Cards leveraging the new SAP Web IDE annotation modeler by Frank Schuler

Learning:

• SAP Fiori Overview Page Overview

This Document Contains a list of All Transaction Codes Required for SAP Fiori Development[Front-End,Back-End and Gateway]. For utilization of Workflows in Custom SAP Fiori Apps,Workflow related transactions would be used.Some of these will be available in Frontend[SAP Gateway] and Some will be for SAP Back-End, in case of Central HUB deployment of SAP Gateway. In case you have an Embedded Gateway Deployment,both Back-End and Front-End Transactions would be available in a single system.

The list of T-codes is based on the following system:

EHP7 for SAP ERP 6.0(Release = EHP7 FOR SAP ERP 6.0)

SAP ERP(Release = 2005(SAP ERP 6.0))

SAP Netweaver(Release = 7.4)

and the following Software Components:

SAP_BASIS    Release = 740  SPLevel =  0010    Support Package = SAPKB74010    SAP Basis Component

SAP_ABA    Release = 740    SPLevel = 0010    Support Package = SAPKA74010    Cross-Application Component

SAP_GWFND    Release = 740    SPLevel = 0013    Support Package = SAPK-74013INSAPGWFND    SAP Gateway Foundation 7.40

[Note:]

This list is divided into 3 columns.

(01)T-code

(02)Description of T-code

(03)Alternate T-code called,for example in case of Front-End and Back-End Transaction Codes.

(04)Overview Description of commonly used Transaction codes is provided[New]

[Note:]

Standard T-codes Required:

Odata Service Development T-codes:

SEGW    Gateway Service Builder

[Description = Used for Testing SAP Fiori Apps Odata services and also used for enhancing Odata Service like redefining a standard method in the DPC class of the relevant Standard Odata Service. Best way to enhance a standard applications,as all changes are recorded in one project].

Administrative T-codes:

SU01    User Maintenance

[Description = Used for creating users and assigning them roles,especially useful when creating copies of Fiori based roles based on standard template roles].

PFCG    Profile Generator

[Description = Used for creating roles,especially useful when creating copies of Fiori based roles based on standard template roles].

SICF    Maintain Services

[Description = For Testing and Activating Services associated with the Standard Fiori Framework Services as well as Standard and Custom Fiori Applications].

LPD_CUST    Launchpad

[Description = Provides a list of all Fiori Launchpads(Standard[] and the custom[] created ones) containing Fiori app URLs,copy,edit,Transport,provided System Alias etc.].

SMLG    CCMS: Maitain Logon Groups

SM59    RFC Destinations (Display/Maintain)

[Description = This is where all Trusted RFC(TRFC's) for communication between SAP Gateway system and ECC system are setup,with the ability to test them as well].

_____

SPRO    Customizing - Edit Project

Would require access to the following nodes in IMG(Implementation Guide):

SAP Customizing Implementation Guide > SAP Netweaver > SAP Gateway

SAP Customizing Implementation Guide > SAP Netweaver > SAP Gateway Service Enablement

SAP Customizing Implementation Guide > SAP Netweaver > UI Technologies

Figure 01 : SPRO Nodes Specific to SAP Fiori

_____

RZ10    Maintain Profile Parameters

RZ20    CCMS Monitoring

RSRT    Start of the report monitor

PTARQ    Test Environment for Leaves

[Description = This is a Suite of Apps,especially for testing and configuring Leave based Scenarios. Pertains to both the Leave based HCM Fiori apps such as 'My Leave Requests'(For Employees) and 'Approve Leave Requests'(For Manager)].

EXTID_DN    External Identification Type DN

SPAM    Support Package Manager

[Description = This tool is used by the Basis Consultant during Fiori Landscape setup].

SMICM    ICM Monitor

ABAP Related Backend Development T-Codes:

SE93    Maintain Transaction Codes

SE01    Transport Organizer (Extended)

SE80    Object Navigator

SE11    ABAP Dictionary Maintenance

SE18    Business Add-Ins: Definitions

[Description = This tool is used if BADI's are provided for a Fiori Apps,instead of creating a project in SEGW(Gateway Builder) e.g: 'HCM_B_PEP_PROF' for People Profile Fiori App].

SE24    ABAP Class Builder

[Description = Used when editing or redefining methods of DPC(Data Provider Class) and MPC(Model Provider Class) classes associated with a Gateway Builder Project for the given Fiori App in Transaction SEGW].

ST22    ABAP Dump Analysis

SE63    Translation Editor

SE43    Maintain Area Menu

SE38    Abap Editor

SBWP    SAP Business Workplace

SM30    Call View Maintenance

____

Note:

Authorization for SM30 is required when accessing or configuring Configuration tables for example

creation of Semantic Objects using T-code '/UI2/SEMOBJ' which makes use of Maintenance Tables.

____

Workflow related T-codes:

SWDD    Workflow Builder

SWIA    WI Administration Report

SWDC    Workflow Definition: Administration

PFTC    General Task Maintenance

/IWWRK/WF_FILTER    Handle Activation of WF item filter

For Front End SAP UI5 Development:

All Transaction code starting with '/UI2/' and '/UI5/'.

Transaction Codes starting with '/UI2/':

/UI2/73000001    Register POWL APPLID    SICF_INST

/UI2/73000003    Maintenance view for SAP GUI Tags(user defined tags)    SICF_INST

/UI2/73000004    NWBC Configuration - Define Parameter Names(Customer)    /UI2/NWBC_CFG_P_CUST

/UI2/73000005    NWBC Configuration - Define Parameter Names(Customer)    /UI2/SAPLNWBC_CFG

/UI2/73000007    NWBC Configuration - Define Parameter Names(Customer)

/UI2/73000008    Maintain Services    SICF

/UI2/73000009    Trust Manager    STRUST

/UI2/73000010

/UI2/73000011    Trust Manager    STRUST

/UI2/73000012

/UI2/73000013

/UI2/73000014    Server Communications    CLB2_PLATF

/UI2/73000015    Application Server Assignment    CLB2_APPLI_PLATF

/UI2/73000016    badi Creation    SE18

/UI2/73000017    Semantic Objects

/UI2/73000019    SAPLS_CUS_IMG_ACTIVITY(Catalog)

/UI2/73000020    Catalogs

/UI2/73000021    Catalogs

/UI2/73000022

/UI2/73000023    Configuration of RFC Connections

/UI2/73000024

/UI2/73000025    Manage SAP System Aliases    /UI2/GW_SYS_ALIAS

/UI2/73000026    Activate and Maintain Services    /IWFND/MAINT_SERVICE

/UI2/73000027

/UI2/73000028    Maintain Services    SICF

/UI2/73000029    Role Maintenance    PFCG

/UI2/73000030    Data Browser    SE16

/UI2/73000031    Semantic Objects

/UI2/73000032    Launchpads    LPD_CUST

/UI2/73000033    Fiori Launchpad Checks    /UI2/FLC

/UI2/73000034    SAP Netweaver gateway Application Log Viewer    /IWFND/APPS_LOG

/UI2/73000035    SAP Netweaver gateway Application Log Viewer    /IWFND/APPS_LOG

/UI2/73000036    Odata Services

/UI2/73000037    Fiori Launchpad Intent Resolution Analysis

/UI2/73000038    Not runnin

/UI2/73000039    badi Creation    SE18

/UI2/73000040    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000041    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000042    SAPLS_CUS_IMG_ACTIVITY    PFCG

/UI2/73000043    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000044    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000045    SAPLS_CUS_IMG_ACTIVITY

/UI2/73000046    Collaboration Tunnel Service    CLB2_TUNNEL

/UI2/73000047    Define Background Job    SM36

/UI2/73000048    Simple Job Selection    SM37

/UI2/73000050

/UI2/73000051    bgRFC Configuration    SBGRFCCONF

/UI2/73000053    Odata Service Settings for Notifications

/UI2/73000054    UI2 Global Cache Invalidation

/UI2/73000055    /UI2/USER_FEEDBACK_Setup    /UI2/FEEDBACK_SETUP

/UI2/73000056    CCMS(maintain Logon Groups)

/UI2/73000057    Badi Creation    SE18

/UI2/73000058    Badi Creation    SE18

/UI2/73000059    Events for Change Document    SWEC

/UI2/73000060    Collaboration Service    CLB2_SERVICE_C

/UI2/CACHE    Register service for UI2 cache us

/UI2/CACHE_DEL    Delete cache entries

/UI2/CHIP    Chip Registration

/UI2/CUST    Customizing of UI Technologies

/UI2/FEEDBACK_SETUP    UI2 Setup User Feedback Service    /UI2/FEEDBACK_SETUP

/UI2/FLC    Fiori Launchpad Checks

/UI2/FLIA    Fiori Launchpad Intent Analyis

/UI2/FLP    SAP Fiori Launchpad

/UI2/FLP_CONTCHECK    Fiori Launchpad - Content Checks

/UI2/FLP_INTENTCHEC    Fiori Launchpad - Intent Checks

/UI2/FLPD_CONF    Fiori Lpd. Designer (cross-client

/UI2/FLPD_CUST    Fiori Lpd. Designer (client-spec.

/UI2/GW_ACTIVATE    Gateway - Activation    /IWFND/IWF_ACTIVATE

/UI2/GW_APPS_LOG    Gateway - Application Log

/UI2/GW_ERR_LOG    Gateway - Error Log

/UI2/GW_MAINT_SRV    Gateway - Service Maintenance

/UI2/GW_SYS_ALIAS    Gateway - Manage SAP System Alias    /UI2/GW_SYS_ALIAS

/UI2/INVAL_CACHES    Global Invalidation of UI2 chache

/UI2/NAV    Register navigation objects

/UI2/NAVPROV    Define navigation provider

/UI2/NWBC    Start UI2 NWBC

/UI2/NWBC_CFG_CUST    NWBC Configuration (Customer)

/UI2/NWBC_CFG_P_CUST    NWBC Config: Define Parameter (Cust)

/UI2/NWBC_CFG_P_SAP    NWBC Config: Define Parameter (SAP)

/UI2/NWBC_CFG_SAP    NWBC Configuration (SAP)

/UI2/PERS_DEL    Cleanup Personalisatation Service

/UI2/POWL    Register POWL for OData consumption

/UI2/SEMOBJ    Define Semantic Object - Customer

/UI2/SEMOBJ_SAP    Define Semantic Object - SAP

Transaction Codes starting with '/UI5/':

/UI5/78000001    ICF: Report for Activating Special Service During Installation    SICF_INST

/UI5/78000002    ICF: Report for Activating Special Service During Installation    SICF_INST

/UI5/THEME_DESIGNER    UI Theme Designer

/UI5/THEME_TOOL    UI Theme Tool

SAP Fiori Front End  Specific T-codes:

/IWFND/32000004    Role Maintenance    PFCG

/IWFND/32000011    Activate/Deactivate Metadata cache    /IWFND/MED_ACTIVATE

/IWFND/32000012    Cleanup of Model Cache    /IWFND/CACHE_CLEANUP

/IWFND/32000013    Activate and Maintain Services    /IWFND/MAINT_SERVICE

/IWFND/32000017    Assign Data Provider to data model

/IWFND/32000018    Change View Assign SAP System Aliases to Odata Service

/IWFND/32000020    IMG Activity not found for transaction /IWFND/32000020

/IWFND/32000021    IMG Activity not found for transaction /IWFND/32000021

/IWFND/32000022    IMG Activity not found for transaction /IWFND/32000022

/IWFND/32000023    IMG Activity not found for transaction /IWFND/32000023

/IWFND/32000024    IMG Activity not found for transaction /IWFND/32000024

/IWFND/50000001    Choose Activity

/IWFND/50000003    SAP Netweaver Activation code    /IWFND/IWF_ACTIVATE

/IWFND/50000004    Manage SAP System Aliases

/IWFND/50000005    Configuration of RFC connections    SM59

/IWFND/50000006    SAP gateway client

/IWFND/50000007    SRT_WS_IDP_CUSTOMIZE[Shedule Switch]

/IWFND/50000008    There are no executable transactions assigned to the IMG activity

/IWFND/50000009    Define Background job    SM36

/IWFND/50000010    cleanup for SAP Netweaver gateway Cache and Persistency Frameworks    /IWFND/CLEANUP

/IWFND/50000011    Simple Job Selection    SM37

/IWFND/50000013    There are no executable transactions assigned to the IMG activity

/IWFND/50000014    Role Maintenance    PFCG

/IWFND/50000015    Role Maintenance    PFCG

/IWFND/50000018    Logon Ticket Administration for Single Sign-On    SS02

/IWFND/50000019    There are no executable transactions assigned to the IMG activity

/IWFND/50000022    Deactivate Logging of Variables T100 Messages

/IWFND/50000027    maintaince dialog is incomplete or not defined

/IWFND/50000031    Registration in System Landscape Directory    R70

/IWFND/50000038    IMG Activity not found for transaction /IWFND/50000038

/IWFND/50000039    IMG Activity not found for transaction /IWFND/50000039

/IWFND/50000040    IMG Activity not found for transaction /IWFND/50000040

/IWFND/50000043    the maintenance dialog for /iwfnd/v_coobgr

/IWFND/50000044    There are no executables assigned to this

/IWFND/50000045    There are no executables assigned to this

/IWFND/50000046    Class Builder    SE24

/IWFND/50000051    Configuration of RFC Connections    SM59

/IWFND/50000052    bgRFC Configuration    SBGRFCCONF

/IWFND/50000053    Consumer Activation

/IWFND/50000054    Maintenance view for the GW CCMS Structure

/IWFND/50000055

/IWFND/50000056    Enter Correct SNC Names in Table View VUSREXTID(from SAP R/3 4.5)    /IWFND/BULK_USER_MAP

/IWFND/50000057    Change View Logical File Path Definition    FILE

/IWFND/50000058

/IWFND/50000059

/IWFND/50000060

/IWFND/50000061    No transaction found

/IWFND/50000062    Role Maintenance    PFCG

/IWFND/50000063    SAP gateway client

/IWFND/50000065    WSS_SETUP    /IWFND/WSS_SETUP

/IWFND/50000066    User Maintenance    SU01

/IWFND/50000068    Badi /IWFND/BD_DCS_PROCESS_PLUGIN

/IWFND/50000071    IMG Activity not found for transaction /IWFND/50000071

/IWFND/50000072    SAP Netweaver Gateway Log Level

/IWFND/50000073    Configuration of RFC Connections    SM59

/IWFND/50000074    Trust Manager:Display    STRUST

/IWFND/50000075    bgRFC Configuation    SBGRFCCONF

/IWFND/50000076    bgRFC Monitor    SBGRFCMON

/IWFND/50000077    Business Communication Services - Administration    SCOT

/IWFND/50000078    Directory Service Connection    LDAP

/IWFND/59000010    Cleanup Notifications    /IWFND/NOTIF_CLEANUP

/IWFND/59000011    SAP Netweaver Gateway Virus Scan Profile Configuration    /IWFND/VIRUS_SCAN

/IWFND/59000012    Creating Badi    SE18

/IWFND/59000013    Creating Badi    SE18

/IWFND/59000018    SAP Netweaver gateway : Error Log    /IWFND/ERROR_LOG

/IWFND/59000019    SAP Netweaver gateway:Tracing Tools    /IWFND/TRACES

/IWFND/59000020    SAP Netweaver Gateway Application Log Viewer    /IWFND/APPS_LOG

/IWFND/59000021    Simple Job Selection    SM37

/IWFND/59000022    Creating Badi    SE18

/IWFND/59000023    Context based SAP System Alias Configuration

/IWFND/59000024    (BADI Implementation)(Implementations for Badi Definition

/IWFND/59000025    Parallelization for Multiple Origin Composition    /IWFND/MOC_PARALLEL

/IWFND/59000026

/IWFND/59000027

/IWFND/99000004

/IWFND/99000005

/IWFND/99000006    Enable or Disable Soft State

/IWFND/APPS_LOG    SAP Gateway Application Log Viewer

/IWFND/BULK_USER_MAP    Transaction to Perform Bulk User M

/IWFND/CACHE_CLEANUP    Cleanup of Model Cache

/IWFND/CLEANUP    Execute Cleanup

/IWFND/CLEANUP_JOBS    Manage cleanup jobs

/IWFND/CRE_DEF_JOBS    Create Default Cleanup Jobs

/IWFND/ERROR_LOG    SAP Gateway Error Log

/IWFND/ERROR_LOG_E2E    SAP Gateway Error Log - E2E

/IWFND/EXPLORER    Service Explorer

/IWFND/GW_CLIENT    SAP Gateway Client

/IWFND/INIT_CCMS    Initialize SAP Gateway CCMS Contex

/IWFND/IWF_ACTIVATE    Activate / Deactivate SAP Gateway

/IWFND/MAINT_SERVICE    Activate and Maintain Services

/IWFND/MED_ACTIVATE    Activate/Deactivate Metadata Cache

/IWFND/MED_SA_ACTIV    Activate system alias based cachin

/IWFND/MOC_PARALLEL    Parallelize Multi-Origin Compositi

/IWFND/NOTIF_CLEANUP    Cleanup Notifications

/IWFND/NOTIF_MONITOR    Notification Monitor

/IWFND/SERVICE_TEST    Service Explorer

/IWFND/SOFTSTATE    Enable or Disable Soft State

/IWFND/STATS    SAP Gateway Statistics

/IWFND/TRACES    SAP Gateway Traces

/IWFND/V4_PUBLISH    SAP Gateway Service Publication

/IWFND/VIEW_LOG    SAP Gateway Application Log Viewer

/IWFND/VIRUS_SCAN    Configuration of SAP GW Virus Scan

/IWFND/WF_WEBGUI    WebGUI For Executing Workflow Item

/IWFND/WSS_SETUP    Configure WS Message-Based

SAP BackEnd  Specific T-codes:

/IWBEP/57000001    Configuration of RFC Connections    SM59

/IWBEP/57000002    Gateway Settings

/IWBEP/57000004    Event Definition

/IWBEP/57000005    Choose Activity

/IWBEP/57000006    Event Type Linkages

/IWBEP/57000007    bgRFC Configuration    SBGRFCCONF

/IWBEP/57000008    bgRFC Monitor    SBGRFCMON

/IWBEP/57000009    Check Configuration Report    /IWBEP/CONFIG_CHECK

/IWBEP/92000002    Maintain Model    /IWBEP/REG_MODEL

/IWBEP/92000003    Maintain Service    /IWBEP/REG_SERVICE

/IWBEP/92000004    Simple Job Selection    SM37

/IWBEP/92000005    SAP Netweaver Application Log Viewer    /IWBEP/VIEW_LOG

/IWBEP/92000006    Clean Up of Model Cache    /IWBEP/CACHE_CLEANUP

/IWBEP/92000007    BADI Creation    SE18

/IWBEP/92000009    Program SRT_WS_IDP_CUSTOMIZE    WSIDPADMIN

/IWBEP/92000012    BADI Creation    SE18

/IWBEP/92000013    Implementation for BADI Definition    SE18

/IWBEP/92000014    BADI Creation    SE18

/IWBEP/92000015    BADI Creation    SE18

/IWBEP/92000016    User Request Management - Application Configuration

/IWBEP/92000018    User Request Management - Cleanup Report    /IWBEP/UR_CLEANUP

/IWBEP/92000019    User Request Management - User Category

/IWBEP/92000020    Role Maintenance    PFCG

/IWBEP/92000021    Role Maintenance    PFCG

/IWBEP/92000022    Role Maintenance    PFCG

/IWBEP/92000023    Maintain Annotation Models    /IWBEP/REG_VOCAN

/IWBEP/92000024    User Self Service Remote Destination Configuration

/IWBEP/92000025    Range Maintenance : GW User Self Service    /IWBEP/UM_NR_INT

/IWBEP/92000026    Parallelization of Batch Queries    /IWBEP/BATCH_CONFIG

/IWBEP/97000002    Display Models

/IWBEP/97000003    Gateway Log Level for the Application Log

/IWBEP/97000004    User Maintenance    SU01

/IWBEP/97000005    Structure of the GW CCMS Context

/IWBEP/97000007    Generate ODATA Channel Implementation    /IWBEP/IMPORT_MODEL

/IWBEP/99000004    Program /IWBEP/R_COS_CLNUP_JOB_CREATE    /IWBEP/CRE_DEF_JOBS

/IWBEP/99000005    Simple Job Selection    SM37

/IWBEP/ANA_SRV_GEN    Analytics Service Generator

/IWBEP/BATCH_CONFIG    Batch Parallelization

/IWBEP/CACHE_CLEANUP    Cleanup of Model Cache

/IWBEP/CLEANUP_JOBS    Manage Cleanup Jobs    SM37

/IWBEP/CONF_SERVICE    Configuration for IWBEP services

/IWBEP/CONFIG_CHECK    Check Configuration of BEP

/IWBEP/CRE_DEF_JOBS    Create Default SAP GW Cleanup Jobs

/IWBEP/ERROR_LOG    SAP GW Backend Error Log

/IWBEP/ERROR_LOG_E2E    SAP GW Backend Error Log - E2E

/IWBEP/IMPORT_MODEL    Service Description File Importer

/IWBEP/NOTIF_MONITOR    SAP GW Backend Notification Monitor

/IWBEP/OCI_SRV_GEN    OData Srvc.(SAPGW)Generator for OSCI

/IWBEP/REG_MODEL    Maintain Model

/IWBEP/REG_SERVICE    Maintain Service

/IWBEP/REG_VOCAN    Maintain Vocabulary Annotations

/IWBEP/RFC_BOP_DEL    OData Channel : Delete RFC BOP

/IWBEP/RFC_BOP_GEN    OData Channel : Generate RFC BOP

/IWBEP/SB    SAP Gateway Service Builder

/IWBEP/SBS    SAP Gateway Service Builder Setup

/IWBEP/TRACES    SAP GW Backend Traces

/IWBEP/UM_NR_INT    MGW Number Range Interval

/IWBEP/UR_CLEANUP    User Request Clean Up

/IWBEP/V4_REGISTER    SAP Gateway Service Registration

/IWBEP/VIEW_LOG    SAP Gateway Log Viewer

/IWBEP/WS_BOP_DEL    OData Channel : Delete WS BOP

/IWBEP/WS_BOP_GEN    OData Channel : Generate WS BOP

[Note:]

    > While running T-codes starting with a Forward Slash '/',append '/n' before them to run the transaction

        code.

[Note:]

    > You can also create an Area Menu with these T-codes and organize them into folders,using T-code

        'SE43'(Maintain Area Menu).

Figure : All SAP Fiori T-codes organized into an Area Menu

[Note:]

    > Many of the T-codes are repeated,as they are referenced through another t-code.

    > Many of the T-codes are also referenced in the IMG Implementation Guide[SPRO] based nodes as provided earlier in the document.

Extras:

(01)How to Access SAP Fiori Launchpad and other Browser based Transactions in an SAP Fiori Deployment?:

click the link below to access the document:

How to Access SAP Fiori Launchpad and other Browser based Transactions in an SAP Fiori Deployment?

(02)How to Make Customizations in the SAP Fiori Logon Landing(Launch) Page?:

click the link below to access the document:

How to Make Customizations in the SAP Fiori Logon Landing(Launch) Page[Doc]?

(03)How to assign Fiori Launchpage to Fiori Launchpad and redirecting to it when logging off from Fiori Launchpad:

click the link below to access the document:

How to assign Fiori Launchpage to Fiori Launchpad and redirecting to it when logging off from Fiori Launchpad[Doc]?

[Note: This list will be further categorized and updated in the future]

My Travel and Expenses Fiori app was released on October 20, 2014.

Overview material

Overview presentation on all Travel Fiori apps

Detailed presentation on My Travel and Expenses app

Video My Travel and Expenses

What's new documentation - January 2015 release

Documentation on SAP Fiori app extensibility

Documentation on the SAP Help Portal

The app My Travel and Expenses enables you to create, display and submit your travel expenses. The documentation of the app on SAP Help Portal includes detailed information on key features, system landscape requirements, implementation and extensibility options.

You can also find information on UI controller hookshere.

Related apps:

With the app My Travel Requests, you can manage your own travel requests in real time using your desktop or mobile device. The app allows you to create, edit, submit, and delete requests. You can also check the status of a particular request at any time. (Documentation of the app on SAP Help Portal / Video)

The app Approve Travel Requests enables you to approve or reject travel requests in real time using your desktop or mobile device. The app provides details on each request and also allows you to view all of an employee's past requests. (Documentation of the app on SAP Help Portal / Video)

With the app Approve Travel Expenses, you can review and approve employees' travel expenses on the go or in the office. The app provides details on each receipt, and alerts you if expenses exceed the budget limits defined in your company's travel policy. You can also forward requests to another employee for approval. (Documentation of the app on SAP Help Portal / Video)

Prerequisites

Fiori infrastructure (Gateway frontend/backend, Fiori Launchpad, etc.) has already been set up.

Back-End Components Delivered with (Product Version Stack): SAP enhancement package 7 for SAP ERP 6.0 SPS07

Front-End Components Delivered with (Product Version Stack): SAP Fiori for SAP ERP 1.0 SPS05

Important: Please check SAP notes for updated information about support packages and UI builds! (also see Important Notes below)

Download the My Travel and Expenses app

Go to SAP Software Download Center -> Installation and Upgrades -> Find your software -> A-Z index -> select F -> SAP Fiori -> SAP Fiori for Suite -> select the respective app

Info about the installation and configuration can be found in the SAP Fiori apps library.

Important SAP Notes

Please make sure you have the following notes installed: