SAP FIORI FOR SAP ERP 1.0PDF download from SAP Help Portal:http://help.sap.com/saphelp_fiori_erp_100/helpdata/en/fb/b34f52f10a5c64e10000000a423f68/frameset.htm

Created on February 13, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

NoteThis PDF document contains the selected topic and its subtopics (max. 150) in the selected structure.Subtopics from other structures are not included.The selected structure has more than 150 subtopics. This download contains only the first 150 subtopics. Youcan manually download the missing subtopics.

© 2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG. The information contained herein may be changed without priornotice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other softwarevendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAPGroup") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in theexpress warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting anadditional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of SAP AG in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 1 of 78

TABLE OF CONTENT1 SAP Fiori for SAP ERP 1.01.1 SAP Fiori1.1.1 SAP Fiori App Types and Database Requirements1.1.2 Implementation Overview1.2 Central Implementation Information1.2.1 Installation1.2.1.1 System Landscape1.2.1.1.1 Deployment of SAP NetWeaver Gateway1.2.1.2 Installation Overview1.2.1.2.1 Installation of SAP NetWeaver Gateway on Front-End Server1.2.1.2.2 Installation of UI Add-Ons1.2.1.2.3 Important SAP Notes (Transactional Apps and Fact Sheets1.2.2 Configuration1.2.2.1 Configuring SAP Fiori Search (Fact Sheets)1.2.2.2 Configuring SAP NetWeaver Gateway1.2.2.2.1 Connect SAP NetWeaver Gateway to SAP Business Suite (Trusted RFC1.2.2.2.2 Create System Alias for Applications1.2.2.2.3 Activate OData Services1.2.2.2.4 Specify Language Settings1.2.2.3 Configuration of Central UI Add-On1.2.2.3.1 Setup of SAP Fiori Launchpad1.2.2.4 Configuration of Product-Specific UI Add-On1.2.2.4.1 Activate ICF Services1.2.2.4.2 Setup of Catalogs, Groups, and Roles in the Fiori Launchpad1.2.2.4.2.1 Creating Custom Catalog1.2.2.4.2.2 Creating Custom Group1.2.2.4.2.3 Creating PFCG Role and Assigning Catalogs and Groups1.2.2.5 Roles, Users, and Authorizations on Back-End Server (Transaction1.2.2.5.1 Copying and Adjusting Roles (Transactional Apps and Fact Sheet)1.2.2.5.2 Assigning User to Role (Transactional Apps and Fact Sheet)1.2.3 Security1.2.3.1 User Administration1.2.3.1.1 User Management Concept1.2.3.1.1.1 Users in ABAP Front-End System1.2.3.1.1.2 Users in ABAP Back-End System1.2.3.1.1.3 Users in SAP HANA System1.2.3.1.2 User Authentication and Single Sign-On1.2.3.1.2.1 Maintaining Single Sign-On for SAP HANA XS Applications1.2.3.1.2.1.1 Maintaining SAP HANA Trust Stores1.2.3.1.2.1.2 Configuring the SAP Web Dispatcher Profile1.2.3.1.2.1.3 Maintaining SSO with X.509 Authentication for SAP HANA XS Applic1.2.3.1.2.1.4 Maintaining SSO with SAP Logon Tickets for SAP HANA XS Applicati1.2.3.1.3 Authorizations1.2.3.1.3.1 Authorizations and Roles for Transactional Apps and Fact Sheets1.2.3.1.3.2 Authorizations and Roles for SAP Fiori Launchpad1.2.3.1.3.3 Authorizations and Roles for Analytical Apps and SAP Smart Busin1.2.3.2 Session Security Protection1.2.3.2.1 ABAP Server Session Security1.2.3.2.2 SAP HANA XS Session Security1.2.3.2.3 Logout from Multiple Systems1.2.3.2.4 Cross-Site Request Forgery Protection (CSRF)1.2.3.3 Network and Communication Security1.2.3.3.1 Communication Channel Security1.2.3.3.2 Network Security1.2.3.3.2.1 Configuring SAP Web Dispatcher1.2.3.3.2.2 Rewriting URLs1.2.3.3.2.3 Internet-Facing Deployment1.2.3.4 Internet Communication Framework Security1.2.4 Operations1.2.4.1 Monitoring SAP Fiori Apps1.2.5 Extensibility1.2.5.1 Extending SAP Fiori Applications1.2.5.1.1 Architecture Overview1.2.5.1.2 Application Types1.2.5.1.3 Content Layer Considerations1.2.5.1.4 Extending Content Layers1.2.5.2 Extending the SAP NetWeaver Gateway Layer1.2.5.2.1 OData Extensibility1.2.5.2.1.1 OData Extensibility in Gateway1.2.5.3 Extending the SAP HANA Layer1.2.5.4 Extending the UI Layer1.2.5.4.1 Custom Application Extensibility1.2.5.4.2 UI Extensibility Workflow1.2.5.4.2.1 Download the SAP-Delivered Standard Application from the ABAP Sy1.2.5.4.2.2 Testing the SAP-Delivered Standard Application1.2.5.4.2.3 Creating a Custom Application1.2.5.4.2.4 Checking the SAP-Enabled Extension Options1.2.5.4.2.5 Defining Extensions Metadata1.2.5.4.2.6 Testing the Custom Application1.2.5.4.2.7 Uploading the Custom Application to SAPUI5 Repository

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 2 of 78

1.2.5.4.2.8 Smoke-Testing the Custom Application on the ABAP System1.2.5.4.2.9 Configuring the Custom Application on the Fiori Launchpad1.2.5.4.2.10 Testing the Custom Application on the Fiori Launchpad1.2.5.4.3 UI Extensibility for Analytical Apps using Smart Business1.2.5.5 Extending the Search Model Layer1.2.5.5.1 Fact Sheet Extensibility1.2.5.5.1.1 Extending a Search Model1.2.5.5.1.2 Checking the Properties of an OData Service1.2.5.5.1.3 Annotation File1.2.5.5.1.3.1 Using Annotation Tags1.2.5.5.1.3.1.1 Adding a New Field to a Fact Sheet1.2.5.5.1.3.1.2 Adding Key Figures to a Fact Sheet1.2.5.5.1.3.1.2.1 Adding Internal Key Figures to a Fact Sheet1.2.5.5.1.3.1.2.2 Adding External Key Figures to a Fact Sheet1.2.5.5.1.4 Register a BSP Application in Launchpad Customizing1.2.5.6 Additional References1.3 SAP Fiori Apps for SAP ERP1.3.1 Apps for Accounting1.3.1.1 Financials (FIN)1.3.1.1.1 Implementing Apps in Financials (FIN)1.3.1.1.2 My Spend1.3.1.1.2.1 App Implementation: My Spend1.3.1.1.3 Accounting Document1.3.1.1.4 Activity Type1.3.1.1.5 Bank1.3.1.1.6 Controlling Document1.3.1.1.7 Cost Center1.3.1.1.8 Cost Center Group1.3.1.1.9 Cost Element1.3.1.1.10 Customer Accounting Document1.3.1.1.11 Fixed Asset1.3.1.1.12 GL Account1.3.1.1.13 HouseBank1.3.1.1.14 House Bank Account1.3.1.1.15 Internal Order1.3.1.1.16 Profit Center1.3.1.1.17 Vendor Accounting Document1.3.1.2 Travel Management1.3.1.2.1 Approve Travel Expenses1.3.1.2.1.1 App Implementation: Approve Travel Expenses1.3.1.2.2 Approve Travel Requests1.3.1.2.2.1 App Implementation: Approve Travel Requests1.3.1.2.3 My Travel Requests1.3.1.2.3.1 App Implementation: My Travel Requests1.3.2 Apps for Logistics1.3.2.1 Implementing Apps in Logistics (LO)1.3.2.2 Production Planning and Control (PP)1.3.2.2.1 Implementing Apps in Production Planning and Control (PP)1.3.2.2.2 Confirm Production Orders1.3.2.2.2.1 App Implementation: Confirm Production Orders1.3.2.2.3 Confirm Production Operations1.3.2.2.3.1 App Implementation: Confirm Production Operations1.3.2.2.4 Release Production Orders1.3.2.2.5 Production Order1.3.2.2.6 Planned Order1.3.2.2.7 Process Order1.3.2.2.8 Resource1.3.2.2.9 Work Center1.3.2.3 Project System (PS)1.3.2.3.1 Implementing Apps in Project System (PS)1.3.2.3.2 Confirm Network Activity1.3.2.3.2.1 Implementation Information for Confirm Network Activity1.3.2.3.3 Confirm Project Milestone1.3.2.3.3.1 Implementation Information for Confirm Project Milestone1.3.2.3.4 Change WBS Element Status1.3.2.3.4.1 Implementation Information for Change WBS Element Status1.3.2.3.5 Project Definition1.3.2.3.6 WBS Element1.3.2.3.7 Network1.3.2.3.8 Network Activity

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 3 of 78

1 SAP Fiori for SAP ERP 1.0

Product InformationProduct SAP Fiori for SAP ERPRelease 1.0Based on SAP enhancement package 7 for SAP ERP 6.0, SPS 02Documentation published November 2013

1.1 SAP Fiori SAP Fiori is a collection of apps that represent the new SAP user experience paradigm. These apps speak a consistent designlanguage and make use of a common technical infrastructure. By blurring traditional computing boundaries and by using interactiveand attractive UI elements, they provide a consistent end-to-end user experience and can be used across all device types withoutcreating additional implementation effort.Organized by user role, the SAP Fiori launchpad is the central entry hub to all Fiori apps, where users access apps via tiles. Within thelaunchpad are services for navigation, personalization, single sign-on, and search. The launchpad and the tiles are flexible and can beadapted to your needs. You can use the search in the SAP Fiori launchpad to perform a cross-entity search through core SAP BusinessSuite applications. The search uses the SAP NetWeaver Embedded Search technology on a SAP HANA database. New SAP HANA-enabled search models are delivered for core business objects.The Fiori apps focus on the most critical and common activities and are designed around how people work:

Role-based: Fiori apps decompose complex applications into a task-based experience with one central entry point for each user.Responsive: Fiori apps adapt to all sizes, devices, versions, and channels to provide a common user experience across allchannels.Simple: Fiori apps follow the 1-1-3 experience (1 user, 1 scenario, 3 screens). They know and provide the right context andmeaningful data integration.Coherent: user experience with apps that speak the same design language. This implies coherence for common activities as well ascoherence for your brand.Instant value: with a low barrier to adoption, enabling customers to adapt and users to personalize.

All UIs are built using state-of-the-art technology such as HTML5 and SAP UI5 mobile. Fiori apps allow you to access the most recentversion of your back-end data via OData services. Through previously defined roles and authorizations you can specify which apps andwhich data a user is allowed to access.

Please note that you might need additional licences to run SAP Fiori apps.

More InformationFor more information about how to set up and implement SAP Fiori apps and the search in the SAP Fiori launchpad, seeImplementation Overview, Installation Overview and Configuration .For more information about the SAP Fiori Launchpad, see SAP Library for User Interface Add-On 1.0 for SAP NetWeaver on SAP HelpPortal at http://help.sap.com/nw-uiaddon. In SAP Library, choose Administration Guide Content Administration SAPFiori Launchpad .You can find an up-to-date list of the delivered HANA-enabled search models for the search in the SAP Fiori launchpad in SAP Note1861013. The SAP Note also provides further information about search models, such as possible restrictions.

1.1.1 SAP Fiori App Types and Database Requirements SAP Fiori has three app types, each distinguished by their focus and infrastructure requirements:

Transactional appsFact sheetsAnalytical apps

When installing Fiori apps, we recommend separating the front-end components with the UI layer from the back-end components thatcontain the business logic and the back-end data. For more information about this deployment option, see Implementation Overview.All Fiori apps can be accessed internally via the intranet. The transactional apps can also be accessed externally via the internet.We recommend to use SAP Web dispatcher as reverse proxy server. Other options are possible but will not be described in thedocumentation.

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 4 of 78

Transactional AppsThese apps let you perform transactional tasks, such as creating a leave request for an employee. They represent simplified views andinteraction with existing business processes and solutions. They run best on an SAP HANA database, but can also be ported to otherdatabases with acceptable performance.The figure below shows an overview of the architecture for the transactional apps.

Transactional Apps

For the transactional apps, the ABAP front-end server contains the UI layer with the necessary product-specific UI components for therespective products (for example, ERP Financials (ERP-FIN), Customer Relationship Management (CRM), Supply Chain Management(SCM) and so on) as well as the infrastructure components. The infrastructure comprises the central UI component with the SAP UI5control library and the SAP Fiori launchpad as well as SAP NetWeaver Gateway with the OData enablement.These front-end components have access through a trusted RFC connection to the ABAP back-end server containing the business logic.The underlying database can be an SAP HANA database, or any database, and can be accessed from the back-end server.The SAP Web dispatcher is the entry point for HTTP(s) requests into your system. It can reject or accept connections. When it acceptsa connection, it selects and appropriate application server and balances the load to ensure an even distribution across the servers.

Fact SheetsThese apps display contextual information about central objects used in your business operations. Fact sheets are designed to beintuitive and harmonized. From a fact sheet area (tile), you can drill down into its details. You can easily navigate from one fact sheet toits related fact sheets. For example, you can navigate from a document to the related business partner or to the master data.From fact sheets, you can also access related transactions in operational systems. For example, from a document fact sheet, you canaccess the back-end system to display document details or to edit the document.You can call up the fact sheets from these locations: from the search results displayed in the launchpad, from other fact sheets, or fromtransactional or analytical apps. The displayed data is consumed immediately from the SAP HANA database, mainly through searchmodels.Fact sheets run only on an SAP HANA database and require an ABAP stack. They cannot be ported to the SAP HANA live (2-tier)architecture.The following figure shows an architectural overview of the fact sheets.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 5 of 78

Fact Sheets

For the fact sheets, the ABAP front-end server contains the UI layer with the central UI component and the necessary product-specific UIcomponents for the respective products used (for example, ERP-FIN, CRM, SCM and so on) as well as SAP NetWeaver Gateway. Thecentral UI component contains for example the SAP UI5 control library and the SAP Fiori launchpad.The front-end server has read access to the ABAP back-end server through a trusted RFC connection. The ABAP back-end servercontains the SAP Business Suite with the business logic, search models, OData services, and the model provider.The SAP Web dispatcher selects the appropriate server for HTTP(s) requests, for example for the INA search protocol requests to thesearch models in the ABAP back-end server.

Analytical AppsThese apps let you get a role-based insight into real-time operations of your business by collecting and displaying key figures directly inyour browser. They can be SAP Smart Business applications but can also be other analytical, predictive, and planning applications.Analytical apps combine the data and analytical power of SAP HANA with the integration and interface components of SAP BusinessSuite. They provide real-time information on large volume data in a simplified front end for enterprise control. With SAP Smart Business,you can closely monitor your most important key performance indicators (KPIs) in real time and react immediately on changes in marketconditions or operations.To do this, you can easily use the pre-delivered KPIs and insight-to-action scenarios or define your own ones based on the KPI modelertool. For more information on the KPI modeler, see SAP Library for SAP Smart Business 1.0 on SAP Help Portal at http://help.sap.com/ssb Application Help Tools SAP Smart Business, Component for KPI Modeling .These apps run only on an SAP HANA database following the SAP HANA live (2-tier) architecture using virtual data models (VDM).The following figure shows an architectural overview of the analytical apps.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 6 of 78

Analytical Apps

The ABAP front-end server contains the UI layer with the infrastructure and the necessary product-specific UI components for therespective products used (for example, ERP-FIN, CRM, SCM and so on). The infrastructure comprises SAP NetWeaver Gateway withthe OData enablement and the central UI component with the SAP UI5 control library and the SAP Fiori launchpad.These front-end components have access through a trusted RFC connection to the ABAP back-end server with the business logic. Theunderlying database can only be an SAP HANA database. The HANA XS Engine also contains the SAP Fiori app content for thedifferent Business Suite products and the SAP Smart Business component with the KPI modeler and the generic drill-down app as wellas the Virtual Data Model (VDM) reuse content.The SAP Web dispatcher selects the appropriate server for HTTP(s) requests, for example for the OData calls to the ABAP front-endserver or the HANA XS Engine.

1.1.2 Implementation Overview To use the SAP Fiori apps, you need to install the necessary front-end components and the Gateway services to make a connection tothe back end possible.We recommend separating the business logic and the back-end data from the UI layer for the following strategic advantages:

Decoupling the lifecycle of the UI apps from the back end, especially for the apps also that run on any database, which has theseadvantages:

Faster iterations for the UI appsChanges to the UI are possible without having development authorizations in the back end.

Single point of maintenance for UI issues, such as browser support and updated versions of SAP UI5 librariesCentral place for theming and branding SAP Fiori apps

To separate back-end from front-end components, set up SAP NetWeaver Gateway with the deployment option Central HubDeployment. This means you must install SAP NetWeaver Gateway independent of consumer technologies in a standalone system,either behind or in front of the firewall, depending on whether you want to enable users to consume the Fiori apps only internally or alsoexternally.In this scenario, the complete UI layer consisting of the central UI component, the product-specific UI components and the SAPNetWeaver Gateway is contained in the ABAP front-end server. The central UI component contains the SAP UI5 control library andthe SAP Fiori launchpad. In addition, the product-specific UI components contain the UI developments for the respective BusinessSuite product, such as ERP-FIN, ERP-SD, ERP-MM, CRM or SCM. SAP NetWeaver Gateway is a development framework, whichoffers development and generation tools to create OData services to a variety of client development tools. Put simply, it establishes aconnection between SAP Business Suite data and target clients, platforms, and programming framework.The ABAP back-end server contains the business logic and the back-end data.The SAP Web dispatcher is the entry point for HTTP(s) requests. It can reject or accept connections. When it accepts a connection, itselects an appropriate application server and balances the load to ensure an even distribution across the servers.The figure below shows an overview of the necessary steps that need to be completed to install and configure Fiori apps.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 7 of 78

Overview of Necessary Implementation Steps

All the steps to install and configure a Fiori app from the figure above are explained in the table below.Activity Transactional Apps Fact Sheets Analytical AppsCheck Prerequisites Not relevant Not relevant SAP HANA liveInstall SAP NetWeaverGateway Components (FrontEnd)

Yes Yes Yes

Install Central and Product-Specific UI Components (FrontEnd)

Yes Yes YesFor SAP Smart Business apps:install KPI framework in addition

Configure Enterprise Search(Back End)

Not relevant Yes Not relevant

Configure SAP NetWeaverGateway (Front End)

Yes Yes Yes

Configure Central UIComponent (Front End)

Yes Yes Yes

Configure Product-specific UIComponents (Front End)

Yes Yes Yes

Configure Back End (Back End) Copy and adjust deliveredback-end roles and assignusers to them.For more information, seeInstallation and Configuration.

Copy and adjust deliveredback-end roles and assignusers to them.For more information, seeInstallation and Configuration.

Configure the PFCG roles in theABAP back end system and theprivileges in SAP HANA live.For more information, see SAPSmart Business 1.0 on SAPHelp Portal at http://help.sap.com/ssb Administrator’s Guide .

The installation requirements for the analytical apps are slightly more complex because the distribution of the requests is morecomplex in a 2–tier architecture.

More InformationFor more information about the installation, configuration and operation of Fiori apps, see Installation Overview and Configuration.For more information about security, see Security.For more information about extensibility of Fiori apps (such as adding new fields or layout options), see Extending SAP FioriApplications.For more information about the installation and configuration of SAP HANA live, see SAP HANA Live for SAP Business Suite 1.0 on SAPHelp Portal at http://help.sap.com/hba Administrator’s Guide .For more information about the installation of SAP Smart Business, see SAP Smart Business 1.0 on SAP Help Portal at http://help.sap.com/ssb Administrator’s Guide .For more information about the individual Fiori apps (such as the names of the PFCG roles for each app, the name of the gatewayservice, the system prerequisites), see the functional description and the implementation documentation for each app in the productdocumentation for the respective product (CRM, ERP, SCM and so on).For more information about SAP NetWeaver Gateway deployment options, see SAP Library for SAP NetWeaver Gateway 2.0 SPS07on SAP Help Portal at http://help.sap.com/nwgateway20 Application Help Support Package 07 SAP NetWeaver SAPNetWeaver Gateway Master Guide Deployment Options, and Embedded Versus Hub Deployment .

1.2 Central Implementation Information

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 8 of 78

1.2.1 Installation This document covers the general steps to take when installing SAP Fiori apps. Where necessary, these instructions refer to app-specific documentation.

1.2.1.1 System Landscape The following graphics shows the detailed system landscape for SAP Fiori transactional apps and fact sheets. For more information,see SAP Fiori App Types and Database Requirements.

We recommend that you use the SAP Web Dispatcher. However, another reverse proxy server may be used too.

Transactional App Landscape

System Landscape for Transactional Apps

Fact Sheet Landscape

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 9 of 78

Landscape for Fact Sheets

1.2.1.1.1 Deployment of SAP NetWeaver Gateway For running SAP Fiori apps, we recommend that you use a Central Hub Deployment of SAP NetWeaver Gateway. This means youinstall SAP NetWeaver Gateway independent of consumer technologies in a standalone system, either behind or in front of the firewall.You therefore separate back-end components from front-end components.We do not recommend the Embedded Deployment option. This document is entirely based on the Central Hub Deployment option.For more information about SAP NetWeaver Gateway deployment options, see SAP Library for SAP NetWeaver Gateway 2.0 SP06 onSAP Help Portal at http://help.sap.com/nwgateway20 Application Help Support Package 06 SAP NetWeaverGateway Master Guide Deployment Options/Embedded Versus Hub Deployment .

1.2.1.2 Installation Overview Setting up your system landscape with the Central Hub Deployment option means that you separate business content from front-endcontent. You therefore have to install components on a back-end server and a front-end server.

PrerequisitesThe following software versions are required:Software VersionDatabase HANA 1.0 SPS 6 Revision 69SAP NetWeaver Back-end server:

SAP NetWeaver 7.40 SPS04Front-end server:SAP NetWeaver 7.31 SPS04 or 7.40 SPS04

Respective Business Suite product: SAP enhancement package 7 for SAP ERP 6.0 SPS02SAP enhancement package 7 for SAP SCM 7.0 SPS02SAP enhancement package 7 for SAP CRM 7.0 SPS02SAP enhancement package 7 for SAP SRM 7.0 SPS02SAP Portfolio and Project Management 6.0 SPS01SAP Access Control 10.1 SPS03

Depending on the SAP NetWeaver Gateway release on your front-end server, you either need to install specific UI components or toensure that these UI components are in place. You can find a list of these components under Installation of SAP NetWeaver

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 10 of 78

Gateway.

Installation TasksThe table lists the installation tasks required for SAP Fiori apps:Step Task Details1 Check or install the required SAP

NetWeaver Gateway componentsSee Installation of SAP NetWeaverGateway

2 Front-End ServerInstall product-specific UI Add-Onaccording to used Business Suite product:

ERPUI for EHP7 for SAP ERP 6.0SRMUI for EHP3 for SAP SRM 7.0SCMSAP SNC USABILITY 1.0CRMUI for EHP3 for SAP CRM 7.0PORTF AND PROJ MGMTUI for SAP PORTF PROJ MGMT 6.0GRCUI for SAP ACCESS CONTROL 10.1SP3

See Installation of UI Add-Ons

3 Install SAP Notes See Important SAP Notes

Installation ToolWe recommend that you use Software Update Manager in combination with Maintenance Optimizer to install the components. Thisfacilitates SAP NetWeaver-based application system upgrades, enhancement package updates, and support package installation,while offering a harmonized UI. Software Update Manageris shipped as part of the software logistics toolset (SL Toolset) 1.0 -independently of the applications.You can download Software Update Manager from the Download Center on SAP Service Marketplace at http://service.sap.com/swdc SAP Software Download Center Search for Software Downloads Software UpdateManager .Maintenance Optimizerin SAP Solution Manager is the central point of access for all maintenance activities. It supports the installation ofupdates and upgrades and completely manages the maintenance activities for your whole solution, and is centrally accessible frominside SAP Solution Manager. You can find more information under https://service.sap.com/mopz.

Alternatively, you can use the add-on installation tool (transaction SAINT) for the installation. For more information about SAINT,see Add-On Installation Tool.

1.2.1.2.1 Installation of SAP NetWeaver Gateway on Front-EndServer On your front-end server, some components have to be available as part of your SAP NetWeaver Gateway installation:

If you run SAP NetWeaver 7.31 SPS04 on your front-end server, you have to install the listed components.If you run SAP NetWeaver 7.40 SPS04 on your front-end server, the listed components are automatically installed with your SAPNetWeaver installation. Ensure that they are in place.

Required SAP NetWeaver Gateway Components

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 11 of 78

Product Version Required SAP NW Gateway Installation Components automatically installed with SAPNW Gateway

EHP3 FOR SAP NETWEAVER 7.0 (ASABAP)

SAP NETWEAVER GATEWAY 2.0 SPS07(Gateway Server Core NW 703/731)

GW_CORE 200SAP IW FND 250SAP WEB UIF 731

If you wish to install approval apps, youadditionally have to install:SAP NETWEAVER GATEWAY 2.0 SPS07(Gateway PGW)

IW_BEP 200

SAP NETWEAVER 7.4 (AS ABAP), SAPNETWEAVER 7.4 FOR SUITE (AS ABAP)

All required components are included in the SAP NetWeaver installation.If you wish to install approval apps, you additionally have to install:SAP NETWEAVER GATEWAY 2.0 SPS07 (Gateway PGW NW 740)

Installation of Central UI ComponentsIf you run your front-end server on SAP NetWeaver 7.31, you need to install the listed central UI Add-Ons containing the followingcomponents:SAP NW Release Required Central UI Add-On Software Component NamesEHP3 FOR SAP NETWEAVER 7.0 (ASABAP) (SPS 04 as minimum)

UI ADD-ON 1.0 FOR NW 7.03 (SPS 06 asminimum)

SAP UI ADD-ON INFRA V1.0SAP UI2 SERVICES V1.0SAPUI5 CLIENT RT AS ABAP 1.00SAP IW BEP 200SAP UI2 FOUNDATION V1.0SAP UI2 IMPL. FOR NW 7.00 V1.0SAP UI2 IMPL. FOR NW 7.01 V1.0SAP UI2 IMPL. FOR NW 7.02 V1.0SAP UI2 IMPL. FOR NW 7.31 V1.0

SAP NETWEAVER 7.4 (AS ABAP), SAPNETWEAVER 7.4 FOR SUITE (AS ABAP)(SPS 04 and component SAP UI 7.40SP05 for both as miminum)

All required components are included in the SAP NetWeaver 7.4 installation. Ensure thatthe above-mentioned required components are in place.

You can find details on the installation of SAP NetWeaver Gateway in the SAP Library for SAP NetWeaver Gateway 2.0 SP06 on SAPHelp Portal, at http://help.sap.com/nwgateway20 Application Help Support Package 06 SAP NetWeaver Gateway SAP NetWeaver Gateway Installation Guide .

1.2.1.2.2 Installation of UI Add-Ons Depending on the Business Suite product(s) you use, you need to install the applicable UI Add-On(s) on your front-end server.Business Suite Product Required UI Add-OnSAP ERP UI FOR EhP7 FOR SAPERP6.0SAP SCM SAP SNC USABILITY 1.0SAP CRM UI FOR EhP3 FOR SAPCRM7.0SAP SRM UI FOR EhP3 FOR SAPSRM7.0SAP GRC UI FOR SAP ACCESS CONTROL 10.1SAP PORTF AND PROJ MGMT UI FOR SAP PORTF PROJ MGMT 6.0

You can download the UI Add-Ons from SAP Service Marketplace.

1.2.1.2.3 Important SAP Notes (Transactional Apps and FactSheets Here are the most important central SAP Notes

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 12 of 78

SAP Note Number Description1931156 General Information: SAP Netweaver Gateway 2.01931157 General Information: UI Infrastructure Components1927731 Corrections in UI Add-On for SAP NetWeaver SP06Fact sheets only (Search)1930487 Fiori Search: Release and Information Note1933191 Release Information Note for SAP NetWeaver Embedded Search

in Fiori

Product-specific Release Information Notes (RIN)Product SAP Note Number DescriptionERP 1737650 EHP7 for SAP ERP 6.0 SP Stacks -

Release & Information Note1914499 Release Information Note: UI FOR EHP7

FOR SAP ERP 6.0CRM 1737725 EHP3 for SAP CRM 7.0 SP stacks -

Release Information Note1914501 Release Information Note: UI FOR EHP3

FOR SAP CRM 7.0SRM 1818517 EHP3 for SAP SRM 7.0 SP stacks -

Release Information Note1914502 Release Information Note: UI FOR EHP3

FOR SAP SRM 7.0PPM 1826383 PPM 6.0: Support package information,

notes, and schedule1928934 Release Information Note: UI FOR SAP

PORTF PROJ MGMT 6.0SCM 1907850 SAP SNC USABILITY EXT 1.0: Release

Information Note1914553 Rel. Info for Mobile UI ext. for SAP SNC

USABILITY EXT 1.0GRC 1870233 Release Information Note for SAP Access

Control 10.11929930 Release Information Note for UI for Access

Control 10.1

1.2.2 Configuration Once the complete infrastructure for SAP Fiori apps has been installed, you must perform the required configuration activities on yourback-end and front-end servers. This table gives an overview of configuration tasks on your back-end and front-end servers:Server TasksBack-end server Configuring SAP Fiori search (fact sheets)Front-end server Configuring SAP NetWeaver Gateway

Connect SAP NetWeaver Gateway to SAP Business Suite(trusted RFC)Create system alias for applicationsActivate OData servicesSpecify language settings

Configuration of central UI add-onSetup of SAP Fiori Launchpad

Configuration of product-specific UI add-onActivate ICF servicesSetup of catalogs, groups, and roles in the Fiori Launchpad

Back-end server (transactional apps and fact sheets) Roles, users, and authorizations on the back-end serverCopying and adjusting rolesAssigning users to roles

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 13 of 78

1.2.2.1 Configuring SAP Fiori Search (Fact Sheets) You must perform the following configuration activities to use both the SAP Fiori search and the fact sheets. The search modelsdelivered for central business objects are the basis for the fact sheets, which display contextual information about these businessobjects. For more information about fact sheets, see SAP Fiori App Types and Database Requirements.You can find an up-to-date list of the delivered search models in SAP Note 1861013. The SAP Note also provides further informationabout search models, such as possible restrictions.

Activities

Configuring Enterprise Search in the Back EndYou must have set up the Embedded Search technology. For more information, enter the key phrase Setting Up Embedded Search inthe documentation of SAP NetWeaver under http://help.sap.com. There, you find a documentation of the following steps required to setup the embedded search:

Activating UI ServicesCreating a Connection Between Embedded Search and SAP HANA or TREX/BWACreating ConnectorsStarting Indexing of Connectors

Activate Search and Fact Sheet in SAP Business Suite FoundationYou must have activated the following business functions in Customizing for your SAP Business Suite application under ActivateBusiness Functions:

To enable SAP Fiori search and fact sheets: SAP HANA Search for SAP Business Suite (BSESH_HANA_SEARCH)To enable fact sheets: SAP HANA Navigation for SAP Business Suite (BSCBN_HANA_NAV)

Furthermore, the activities under Cross-Application Components General Application Functions HANA-Based Search for SAPBusiness Suite are relevant in Customizing for your SAP Business Suite product.

1.2.2.2 Configuring SAP NetWeaver Gateway On your front-end server, you must configure SAP NetWeaver Gateway.For an overview of SAP NetWeaver Gateway, see SAP Library for SAP NetWeaver Gateway on SAP Help Portal at http://help.sap.com/nwgateway20 Application Help Support Package 07 SAP NetWeaver Gateway SAP NetWeaverGateway Configuration Guide .

1.2.2.2.1 Connect SAP NetWeaver Gateway to SAP BusinessSuite (Trusted RFC) You must set up a connection between SAP NetWeaver Gateway on your front-end server and your existing SAP Business Suitesystem on your back-end server.For detailed steps, see Defining Trust between the SAP NetWeaver Gateway Host and Your SAP Systems for Type 3 Connections.

1.2.2.2.2 Create System Alias for Applications The next step is to specify the SAP system alias.For detailed steps, see Creating the SAP System Alias for Applications.

1.2.2.2.3 Activate OData Services

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 14 of 78

In SAP NetWeaver Gateway, entities are defined and connected using data models. These data models can be exposed as ODataservices during runtime. Runtime processing is handled by data provider classes (DPCs) that are assigned to the object models.For each SAP Fiori app, a corresponding OData service is delivered. For security reasons, these OData Services are delivered in aninactive state. After installation, you must activate the OData Services for the apps you want to use.For more information, see SAP Library for User Interface Add-On 1.0 for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw-uiaddon . In SAP Library, choose User Interface Add-On for SAP NetWeaver Administrator’sGuide Activating OData Services .For general information on OData Services, see SAP NetWeaver Gateway.

1.2.2.2.4 Specify Language Settings You must specify the settings for supported languages in the SAP NetWeaver Gateway system. Settings include default and logonlanguages.

The default language of the SAP NetWeaver Gateway system must be the same as the default language of the back-end system,for example, English. If this is not the case, ensure that the SAP NetWeaver Gateway system contains a subset of the languages ofthe back-end system.

The logon language for the ABAP Application Server is set according to the following process:If the Mandatory Logon Data indicator has been activated for a service in transaction SICF, the system uses the language that wasentered there.If this is not the case, but the HTTP request contains the language in the HTTP header (as a header or a form field), you log onto thesystem using this language.The browser settings of the calling client are then used. The system selects as the logon language the first language from the list that ismaintained in the browser, and which is also installed in the SAP system. The language list is specified using the HTTP header fieldaccept-language.

With Internet Explorer, you can for example set the language you require by choosing Tools Internet Options Languages .

If no language is defined by this process, the classic SAP system mechanisms are used. The logon language is based on the usersettings (in transaction SU01) and if nothing is entered here, the default language of the SAP system is used automatically.

For more information, see SAP Library for SAP NetWeaver Gateway on SAP Help Portal at http://help.sap.com/nwgateway20 Application Help Support Package 06 SAP NetWeaver Gateway ConfigurationGuide Basic Configuration Settings Language Settings .

1.2.2.3 Configuration of Central UI Add-On The central UI Add-On contains the components that comprise the common infrastructure for all SAP Fiori apps, including the SAP FioriLaunchpad.

1.2.2.3.1 Setup of SAP Fiori Launchpad The SAP Fiori Launchpad is the entry point to the apps, from desktop and mobile devices. You need to configure the SAP FioriLaunchpad so that users can access those apps that have been assigned to his their role.For detailed information about the configuration tasks for the Fiori Launchpad, see http://help.sap.com SAP NetWeaver User Interface Add-On 1.0 for SAP NetWeaver Administrator’s Guide Content Administration Setting Up the SAP Fiori LaunchPage .

SAP Fiori SearchFor more information about enabling the search for business objects in the Fiori launchpad, enter the key words SAP Web DispatcherConfiguration for the Search in the documentation of SAP NetWeaver under http://help.sap.com.

Note

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 15 of 78

1.2.2.4 Configuration of Product-Specific UI Add-On The product-specific UI add-ons contain those components that are required for specific apps. You have to configure some of theseapp-specific components and adjust them according to your needs.

1.2.2.4.1 Activate ICF Services You must activate the central services relevant for all SAP Fiori apps, as well as the services relevant for the apps you want to use. Thisis because, for security reasons, all Internet Communication Framework (ICF) services are made available in an inactive state.

For security reasons, we recommend that you only activate the services for the apps you wish to use.

For each app, you can find the technical name of the corresponding ICF service in the App Implementation documentation under Technical Data Front-End Components UI5 Application .To activate an ICF service, proceed as follows:1. Choose transaction SICF.2. Select the respective service under default_host sap bc ui5_ui5 sap .3. To activate the service, choose Service/host Activate .

1.2.2.4.2 Setup of Catalogs, Groups, and Roles in the FioriLaunchpad The Fiori Launchpad is the access point to apps on mobile or desktop devices. The apps are displayed via tiles. These tiles provideaccess to the single apps. The apps are organized through the following entities:

Catalog: Set of apps you want to make available for one role. Depending on the role and the catalog assigned to the role, the usercan browse through the catalog and choose apps from this catalog displayed on the entry page of the Fiori Launchpad.Group: Subset of catalog which contains the apps visible on the Fiori Launchpad entry page. Which tiles are displayed on a user’sentry page depends on the group assigned to the user’s role. In addition, the user can personalize the entry page by adding orremoving apps to pre-delivered groups or self-defined groups.Roles (PFCG): Provides access to the assigned groups and catalogs.

SAP delivers predefined technical objects for the Fiori Launchpad which you can copy to set up your own catalogs for the roleswithin your company.For catalogs, groups and roles SAP delivers technical content as well as business content. The business content, for example,business roles and business catalogs, can be used as showcases of how you can design roles, catalogs, and groups.When you create your own catalogs, groups, and roles, use the technical content as a basis. The technical catalogs as part of thistechnical content contain the apps for a product area. You can identify technical catalogs through *_TC_*in the technical name. Thetechnical roles per area to which the technical catalogs are assigned contain *_TCR_* in their technical name.

Features1. Create a custom catalog.

For more information, see Creating Custom Catalog2. Create a group.

For more information, see Creating Custom Group.3. Create your custom PFCG role and assign your catalog and group.

For more information, see Creating PFCG Role and Assigning Catalogs and Groups.4. Assign your PFCG role to the users.

For more information, see SAP Library for User Interface Add-On 1.0 for SAP NetWeaver on SAP Help Portal athttp://help.sap.com/nw-uiaddon. In SAP Library, choose Administration Guide Content Administration FioriLaunchpad Setting Up the Launchpad and Launchpad Designer Assigning Roles to Administrators and Users .

Note

Recommendation

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 16 of 78

1.2.2.4.2.1 Creating Custom Catalog To group the apps needed by a role, you create your custom catalog.

SAP recommends to use the delivered technical catalog as repository to create your custom catalog as the technical catalogcontains all apps belonging to your area.

Procedure1. Create the catalog based on the delivered technical catalog.

For more information, see SAP Library for User Interface Add-On 1.0 for SAP NetWeaver on SAP Help Portal athttp://help.sap.com/nw-uiaddon. In SAP Library, choose Administration Guide Content Administration FioriLaunchpad Launchpad Designer Creating and Removing Catalog .

1.2.2.4.2.2 Creating Custom Group To make apps available on the entry page of the Fiori Launchpad, you create a group and assign apps from your custom catalog to thisgroup. The user can then modify the group in the Fiori Launchpad and add or remove apps.

Procedure1. Create a custom group and assign apps from your custom catalog.For more information, see SAP Library for User Interface Add-On 1.0 for SAP NetWeaver on SAP Help Portal athttp://help.sap.com/nw-uiaddon. In SAP Library, choose Administration Guide Content Administration Fiori LaunchpadLaunchpad Designer Creating and Removing Group .

1.2.2.4.2.3 Creating PFCG Role and Assigning Catalogs andGroups To make your custom catalog and group available to the users, you create a PFCG role and assign catalog and group to this role.

Procedure1. Create a PFCG role.2. Assign your custom catalog and group to the role.

For more information, see SAP Library for User Interface Add-On 1.0 for SAP NetWeaver on SAP Help Portal athttp://help.sap.com/nw-uiaddon. In SAP Library, choose Administration Guide Content Administration FioriLaunchpad Setting Up the Launchpad and Launchpad Designer Assigning Catalogs and Groups to Roles .

1.2.2.5 Roles, Users, and Authorizations on Back-End Server(Transactional Apps and Fact Sheet) For transactional applications and fact sheets, back-end users with specific granted authorizations are necessary.In most cases, users in the back-end system are already existing and do have application-specific authorizations assigned.SAP delivers back-end PFCG roles for every transactional app and fact sheet. Theses delivered roles comprise references to thecorresponding OData services which are required to use the applications. Based on the OData service reference, authorizationproposals of the OData service can be used to create authorization profiles.Back-end PFCG roles for fact sheets comprise the authorizations to use the underlying search models and to display the business datafrom the back end. For more information about authorizations for search models, see the Authorizations section in the Security Guidefor Search and Operational Analytics. Enter the key words Security Guide for Search and Operational Analytics in the documentation

Recommendation

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 17 of 78

of SAP NetWeaver under http://help.sap.com.

FeaturesYou can copy the delivered role and adjust the authorizations. For more information, see Copying and Adjusting Roles.You can assign the application users to the adjusted roles. For more information, see, Assigning Users to Roles.

1.2.2.5.1 Copying and Adjusting Roles (Transactional Appsand Fact Sheet) SAP delivers back-end roles for each transactional app and fact sheet as templates for customer-specific roles. For every role,authorizations must be granted according to the customer-specific roles and authorization concept.For more information about the delivered roles, see the documentation of the related application.

PrerequisitesAfter a release installation or upgrade, you can compare the default check indicators and the field values of the previous and newreleases using transaction SU25.For more information see the documentation at http://help.sap.com SAP NetWeaver 7.3 Including Enhancement Package1 Application Help Function-Oriented View Security Identity Management User and Role Administration of Application ServerABAP Configuration of User and Role Concept :

First Installation Procedure Comparing Check Indicators/Field Values After Upgrade

Procedure1. Copy the role to your name space.2. Create and adjust the authorizations in transaction PFCG according to your roles and authorization concept.

For more information, see the documentation at http://help.sap.com SAP NetWeaver 7.3 Including EnhancementPackage 1 Application Help Function-Oriented View Security Identity Management User and Role Administration ofApplication Server ABAP AS ABAP Authorization Concept .

1.2.2.5.2 Assigning User to Role (Transactional Apps and FactSheet) You assign your application users to your adjusted roles.

Ensure that the users on the front-end server are identical to the users on the back-end server as there is not mapping available. Youcan use the Central User Administration (CUA) or your existing identity management system to ensure user names on both systemsmatch.

PrerequisitesYou have adjusted the delivered roles according to your roles and authorization concept. For more information, see the documentationat http://help.sap.com SAP NetWeaver 7.3 Including Enhancement Package 1 Application Help Function-Oriented View Security Identity Management User and Role Administration of Application Server ABAP AS ABAP Authorization Concept .

Procedure1. Assign your application users to your adjusted roles in transaction SU01 or PFCG.

For more information, see the documentation at http://help.sap.com SAP NetWeaver 7.3 Including EnhancementPackage 1 Application Help Function-Oriented View Security Identity Management User and Role Administration ofApplication Server ABAP Configuration of User and Role Administration Role Administration .

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 18 of 78

1.2.3 Security When running your SAP Business Suite system, you must ensure that your data and processes support your business needs withoutallowing unauthorized access to critical information. User errors, negligence, or attempted manipulation of your system must not result inloss of information or processing time. These security requirements apply equally to SAP Fiori applications.This chapter provides security-relevant information applicable to SAP Fiori applications. The system landscape for SAP Fioriapplications is built from multiple components, so the following component security guides also apply:For SAP Fiori transactional apps and fact sheets, the following component security guides apply:

SAP Enterprise Resource Planning (ERP)SAP Customer Relationship Management (CRM)SAP NetWeaver Gateway

For SAP Fiori analytical apps, the following component security guides apply:SAP Enterprise Resource Planning (ERP)SAP Customer Relationship Management (CRM)SAP NetWeaver GatewaySAP HANA Live

Furthermore, for SAP Fiori fact sheets, the Security Guide for Search and Operational Analytics applies. For more information, enter thekey words Security Guide for Search and Operational Analytics in the documentation of SAP NetWeaver underhttp://help.sap.com.

1.2.3.1 User Administration SAP Fiori apps adopt the user management and authentication mechanisms provided by SAP NetWeaver ABAP and SAP HANAplatform (analytical apps and SAP Smart Business apps only).Therefore, the security recommendations and guidelines for user administration and authentication as described in the SAP NetWeaverApplication Server ABAP Security Guide and SAP HANA Security Guide also apply to the applications.The following sections comprise information about user administration and authentication that specifically applies to SAP Fiori apps.

1.2.3.1.1 User Management Concept SAP Fiori apps are based on the following user management concept.For transactional apps and fact sheets, the following users are required

Users in SAP NetWeaver Gateway / ABAP front-end serverUser in ABAP back-end server

For analytical apps, the following users are required:Users in SAP NetWeaver Gateway / ABAP front-end serverUser in ABAP back-end systemSAP HANA database users

1.2.3.1.1.1 Users in ABAP Front-End System SAP Fiori application users need a user in SAP NetWeaver Gateway. They must have the same user name as the users in the ABAPback-end system. The user requires certain authorizations that allow the services of the application to be triggered in the back end.

1.2.3.1.1.2 Users in ABAP Back-End System Existing users are relevant for the ABAP back-end system. The authorizations required for a particular application are provided using aPFCG role delivered for each application.You can use the Central User Administration (CUA) or your existing identity management system to synchronize users in the back-endand the front-end system to ensure user names on both systems match.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 19 of 78

1.2.3.1.1.3 Users in SAP HANA System SAP Fiori analytical apps and SAP Smart Business applications can access an SAP HANA database on behalf of an individual user toretrieve data according to the user’s authorizations.

Users on SAP HANA must have the same user name as the users in the ABAP systems.User names in SAP HANA have to comply with the following syntactical rules:

User names have to start with a letter.User names can contain letters (Aa-Zz), digits, and underscores (“_”).Other characters like dots or minus are not allowed.

User names in SAP ABAP can contain characters that are not allowed in SAP HANA. If you use SAP HANA and SAP ABAP, ensurethat your ABAP users also comply with the SAP HANA rules.

Information about synchronizing ABAP users with SAP HANA users is included in the guides for SAP Smart Business apps and SAP Fiorianalytical apps.

1.2.3.1.2 User Authentication and Single Sign-On

Initial AuthenticationWhen a user launches an SAP Fiori app, the launch request is sent from the client to the ABAP front-end server by the SAP FioriLaunchpad. During launch, the ABAP front-end server authenticates the user. To authenticate the user, the ABAP front-end server usesthe authentication and single sign-on (SSO) mechanisms provided by SAP NetWeaver, in particular:

X.509 certificatesIf you have implemented a PKI infrastructure for user authentication in your organization, you can use X.509 certificates by configuringthe required back-end systems (ABAP or SAP HANA) to accept X.509 certificates.SAP logon ticketsFor SAP logon tickets, you must configure the ABAP front-end server to issue SAP logon tickets. Alternatively, you can use an existingsystem, such as a portal, in your landscape that already issues logon tickets. In addition, you must configure the required back-endsystems (ABAP or SAP HANA) to accept SAP logon tickets. You must also ensure that users in the ABAP system have the same usernames as the database users in SAP HANA; user mapping is not supported.SAML 2.0If you have have implemented the security assertion markup language (SAML) version 2.0 as the method of SSO within yourorganization, you can configure the ABAP front-end server for use with SAML 2.0.

Authentication for Requests in the Back-End SystemsAfter initial authentication on the ABAP front-end server, the SAP Fiori apps and the SAP Fiori Launchpad can send requests to theABAP back-end server and to SAP HANA. How these requests are authenticated depends on the type of app.

Transactional apps and Factsheet appsThese apps send OData requests through the ABAP front-end server towards the ABAP back-end server. After initial authentication, asecurity session is established between the client and the ABAP front-end server. OData requests towards the ABAP back-end serverare then communicated securely by trusted RFC.

You must set up a trusted RFC between SAP NetWeaver Gateway and the ABAP back-end system.

Analytical apps and SAP Smart Business appsThese apps send OData requests from the client to SAP HANA Extended Services (XS). These requests can be authenticated witheither SAP logon tickets or X.509 certificates. You can configure the ABAP front-end server to issue SAP logon tickets after initialauthentication, or you can use your existing portal to do so.To configure user authentication methods for SAP HANA XS, you use theXS Applications tool of the Web-based SAP HANA XSAdministration Tool. We recommend configuring user authentication methods for the following packages, which contain the contentnecessary for the applications:sap.hba.appssap.hba.r

The authentication methods specified for these packages also apply to any subpackages.

Caution

Note

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 20 of 78

Search in SAP Fiori LaunchpadSearch in SAP Fiori Launchpad sends http/InA requests from the client to the ABAP back-end server. These requests can beauthenticated either with SAP logon tickets or X.509 client certificates. You can configure the ABAP front-end server to issue SAPlogon tickets after initial authentication, or you can use your existing portal to do so.

More InformationFor information about how to set up a trusted RFC, see http://help.sap.com/nw731/ Security Guide Security Guides forConnectivity and Interoperability Technologies RFC/ICF Security Guide RFC Scenarios .For information about configuring user authentication and SSO on the ABAP front-end server, see http://help.sap.com/nw702 Application Help Function-Oriented View Security User Authentication and Single Sign-On Authentication on the AS ABAP .For information about configuring SSO for SAP HANA XS, see Maintaining Single Sign-On for SAP HANA XS Applications.

1.2.3.1.2.1 Maintaining Single Sign-On for SAP HANA XSApplications You can configure SAP HANA applications to use single sign-on (SSO) authentication to confirm the logon credentials of a user calling anapplication service. For SAP Fiori and SAP Smart Business applications, SAP HANA supports SSO certificates based on SAP LogonTickets or X.509. If you want your the SAP HANA XS applications to use an SSO certificate based on SAP Logon Tickets or X.509 as thelogon authentication method, you must perform the following high-level steps:

Maintain the SAP HANA trust store.Install the encryption software, for example, the SAP cryptographic library libsapcrypto.so and utility sapgenpse and maintain the truststore for SAP HANA.Maintain the internal SAP Web Dispatcher for SAP HANA XSEdit the SAP Web Dispatcher profile sapwebdisp.pfl, for example, to enable SSL and HTTPS.

The SAP Web Dispatcher referred to here is internal to SAP HANA XS and not the SAP Web Dispatcher included in the SAP Fiori /SAP Smart Business system landscape.

Choose the SSO authentication method and configure the trust relationships:SSO with X.509 certificatesAdd the root certificate authority (CA) for the trusted X.509 certificates to both the SAP HANA trust store and the trust store for theSAP Web Dispatcher.SSO with SAP Logon TicketsMaintain the trust store that contains the SAP logon tickets and specify the server that issues the SAP logon tickets.

Maintain the SSO provider for SAP HANA XS.Maintain a runtime configuration for the SAP HANA application, which indicates that user authentication is by means of SSOcertificates based on either SAP Logon Tickets or X.509.

1.2.3.1.2.1.1 Maintaining SAP HANA Trust Stores The SAP HANA trust store contains the root certificate authority (CA) that is used to sign the trusted certificates required for SSOauthentication.

PrerequisitesTo maintain the trust stores for SAP HANA and the SAP Web Dispatcher, you need the following libraries and utilities, which you candownload from the SAP Service Marketplace (SMP):

The SAP encryption library libsapcrypto.soThe SAP trust store generation utility sapgenpse

The SAP Web Dispatcher referred to here is internal to SAP HANA XS and not the SAP Web Dispatcher included in the SAP Fiori /SAP Smart Business system landscape.

Procedure1. Install the SAP HANA encryption library.

Note

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 21 of 78

Put the encryption library libsapcrypto.so in the following location on your SAP HANA server:/usr/sap/<SAPHANAInstance>/SYS/global/security/lib2.

2. Install the SAP HANA trust store utility.Put the trust store utility sapgenpse in the following location on your SAP HANA server:/usr/sap/<SAPHANAInstance>/SYS/global/security/lib3.

3. Create the trust store files.You need to set up several trust stores, for example, for SAP HANA and for the SAP Web Dispatcher.1. Set up the SAP HANA trust store sapsrv.pse../sapgenpse gen_pse -p /usr/sap/<SAPHANAInstance>/HBD<InstNo>/<Hostname>/sec/sapsrv.pse

Do not define a personal identification number (PIN) for the trust store (press twice when prompted for the PIN). For theDistinguished name of PSE owner type CN=<yourhostname>, where <yourhostname> is the host name of theSAP HANA server.

2. Set up the SAP Web Dispatcher trust store SAPSSL.pse../sapgenpse gen_pse -p /usr/sap/<SAPHANAInstance>/HBD<InstNo>/<Hostname>/sec/SAPSSL.pse

3. Set up the trust store sapcli.pse../sapgenpse gen_pse -p /usr/sap/<SAPHANAInstance>/HBD<InstNo>/<Hostname>/sec/sapcli.pse

4. Have the trust store (.pse files) signed by a CA.All the trust stores you create in this step are self-signed. In a productive environment, you must have the trust store files signed by aCA.

1.2.3.1.2.1.2 Configuring the SAP Web Dispatcher Profile To enable SAP HANA applications to use SSL/HTTPS to secure both incoming and outgoing connections, you must maintain the SAPWeb Dispatcher profile sapwebdisp.pfl.

The SAP Web Dispatcher referred to here is internal to SAP HANA XS and not the SAP Web Dispatcher included in the SAP Fiori /SAP Smart Business system landscape.

PrerequisitesTo configure the SAP Web Dispatcher to enable SSL/HTTPS for SAP HANA applications, note the following prerequisites:

You need root/administrator access to the SAP HANA system hosting the SAP Web Dispatcher service.The SAP encryption library libsapcrypto.so is installed and available.The trust store utility sapgenpse is available.The SAP Web Dispatcher trust store (SAPSSL.pse) is available.

You use the SAP Web Dispatcher profile to specify, among other things, the location of the encryption library (libsapcrypt.so) andthe SAP Web Dispatcher trust store (SAPSSL.pse).

Procedure1. On the SAP HANA server, open the SAP Web Dispatcher profile in your favorite text editor.

By default, the SAP Web Dispatcher profile sapwebdisp.pfl is located in the following directory:/usr/sap/<SAPHANAInstance>/HDB<InstNo>/<Hostname>/wdisp/sapwebdisp.pfl

2. Maintain the following values in the SAP Web Dispatcher profile sapwebdisp.pfl:

1. wdisp/ssl_encrypt = 0ssl/ssl_lib = /usr/sap/<SAPHANAInstance>/SYS/global/security/lib/libsapcrypto.sossl/server_pse = SAPSSL.pseicm/HTTPS/verify_client = 1icm/HTTPS/forward_ccert_as_header = true

3. Restart the SAP HANA XS engine.1. In the SAP HANA studio’s Administrator editor, open the Landscape Services tab for the SAP HANA system where you want

to restart the XS Engine service.2. Right-click the service and choose the required option:

Stop...The service is stopped normally and then typically restarted.Kill...The service is stopped immediately and then typically restarted.

NoteENTER

Note

Syntax

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 22 of 78

Reconfigure Service...The service is reconfigured; any changes made to parameters in the system configuration files are applied.

4. Restart the SAP Web Dispatcher.

1. sapcontrol -nr <instanceNr> -function SendSignal <pid> <signal>

For example, to restart the SAP Web Dispatcher 00 with the process ID 28155, run the following command:

1. sap control -nr 00 function SendSignal 28155 2

5. Test HTTPS calls to the SAP HANA Web server.In a Web browser, call the SAP HANA XS Web server at the following URL:https://<SAPHANA_WebServer_Hostname>:43SAPHANAInstNo>

1.2.3.1.2.1.3 Maintaining SSO with X.509 Authentication forSAP HANA XS Applications SAP HANA applications can use single sign-on (SSO) authentication with X.509 certificates to confirm the logon credentials of a usercalling an application service.

PrerequisitesTo configure SAP HANA to use trusted X.509 certificates for user authentication with SSO, note the following prerequisites:

You need root/administrator access to the SAP HANA system hosting the SAP Web Dispatcher service.

To maintain security and authentication settings for SAP HANA XS applications, the user also needs the privileges granted by theSAP HANA XS role RuntimeConfAdministrator.

The SAP encryption library libsapcrypto.so is installed and available.The trust store utility sapgenpse is available.The SAP Web Dispatcher trust store (SAPSSL.pse) is available.

The SAP Web Dispatcher referred to here is internal to SAP HANA XS and not the SAP Web Dispatcher included in the SAP Fiori /SAP Smart Business system landscape.

The SAP HANA trust store (sapsrv.pse) is available.

ProcedureTo enable SAP HANA applications to use single sign-on (SSO) authentication with X.509 certificates to confirm the logon credentials of auser, you need to add the root CA of the trusted X.509 certificates to both the SAP HANA trust store (sapsrv.pse) and the trust storeof the SAP Web Dispatcher SAPSSL.pse.1. Add the root CA of the trusted X.509 certificates to the SAP HANA trust store (sapsrv.pse).

1. ./sapgenpse maintain_pk -p /usr/sap/<SAPHANAInstance>/HDB/<InstNo>/<Hostname>/sec/sapsrv.pse -a SSO_CA.der

2. Add the root CA of the trusted X.509 certificates to the SAP Web Dispatcher SAPSSL.pse.

1. ./sapgenpse maintain_pk -p /usr/sap/<SAPHANAInstance>/HDB<InstNo>/<Hostname>/sec/SAPSSL.pse -a SSO_CA.der

3. Reload the new trust store configuration.Whenever you import a new certificate into the trust store, you must restart the corresponding trust-store process, for example:

SAP HANA trust store (sapsrv.pse)hdbxsengine and hdbindexserver

Syntax

Syntax

Note

Note

Syntax

Syntax

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 23 of 78

SAP Web Dispatcher trust store (SAPSSL.pse)sapwebdisp_hdb

4. Maintain the authentication settings in the runtime configuration for your SAP HANA XS application.You can use the Web-based SAP HANA XS Administration Tool to complete this step. The tool is available on the SAP HANA XSWeb server at the following URL: http://<WebServerHost>80<SAPHANAInstance>/sap/hana/xs/admin/.

5. Create a database user whose identity is defined in an X.509 certificate.1. Create a new user in the SAP HANA database based on the details specified in an existing X.509 certificate.

The following example shows how to use the SQL statement CREATE USER WITH IDENTITY to create the database user“MyUserName” and the corresponding X.509 certificate:

1. CREATE USER MyUserName WITH IDENTITY 'CN=MyUserName, O=SAP-AG, C=DE' ISSUER 'CN=SSO_CA, O=SAP-AG, C=DE' FOR X509

2. Import into the Web browser the X.509 certificate that is to be used to authenticate the new database user.6. Use a Web browser to test the logon authentication settings for the SAP HANA application.

When you enter the URL for your application in the Web browser, the Web browser prompts you to select a certificate, whichenables you to log on without supplying logon credentials manually.

1.2.3.1.2.1.4 Maintaining SSO with SAP Logon Tickets for SAPHANA XS Applications SAP HANA applications can use single sign-on (SSO) authentication with SAP logon tickets to confirm the logon credentials of the usercalling an application service.To enable SAP HANA applications to use single sign-on (SSO) authentication with SAP logon tickets to confirm the logon credentials of auser requesting an application service, you must ensure that an SAP server is available that can issue SAP Logon tickets. You alsoneed to maintain the trust store saplogon.pse, which holds the SAP logon tickets that are presented when a user logs on to the SAPHANA XS application.

PrerequisitesTo configure SAP HANA to use SAP logon tickets authenticate users who log on with SSO, note the following prerequisites:

You need administrator access to the SAP HANA system hosting the applications to which you want to enable access with SAP logontickets.

To maintain security and authentication settings for SAP HANA XS applications, the user also needs the privileges granted by theSAP HANA XS role RuntimeConfAdministrator.

Administrator access to an ABAP system where you need to maintain the trust store used for the SAP logon ticketsThe SAP encryption library libsapcrypto.so is installed and available.The SAP logon trust store (saplogon.pse) is available on the SAP HANA system.

Procedure1. Maintain the trust store that contains the SAP logon tickets.

The trust store saplogon.pse is used to hold the SAP logon tickets; you maintain this trust store with the ABAP transactionSTRUST, rename the trust store and copy the resulting saplogon.pse file to the SAP HANA directory/usr/sap/<SAPHANAInstance>/HDB<InstNo>/<Hostname>/sec/.1. Logon to the ABAP system as <SID>adm and start the Trust Manager with the transaction STRUST2. Create a trust store.

Choose System PSE Veri.PSE .3. Add your own certificate to the new trust store.

In the Trust Manager dialog, choose Yes.4. Name the new trust store for the SAP logon tickets.

In the Personal Security Environment dialog, enter saplogon in the File name field and choose Save.

Make sure you save the saplogon trust store as file type PSE (.pse).

5. Save the new trust store to a location of your choice.2. In SAP HANA, maintain details of the server that issues SAP logon tickets.

1. Start SAP HANA studio and open the Administration perspective.2. In the Configuration tab, expand (or add) the section xsengine.ini authentication .3. Set (or add) the parameter: logonticket_redirect_url. Enter the following URL:

Syntax

Note

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 24 of 78

https://<SAPHANAhostname>:44333/sap/bc/zredirectwlogon?sap-client=<SAPClientNr>.3. Maintain the runtime configuration for the application that you want to use SAP logon tickets to authenticate users.

You can use the Web-based SAP HANA XS Administration Tool to complete this step. The tool is available on the SAP HANA XSWeb server at the following URL: http://<WebServerHost>:80<SAPHANAInstance>/sap/hana/xs/admin/.

1.2.3.1.3 Authorizations The authorization concepts of SAP Fiori applications are based on the authorization mechanisms provided by the SAP NetWeaverABAP and SAP HANA platform. Therefore, the recommendations and guidelines for user and role administration and authorization forSAP NetWeaver Application Server ABAP as well as the security guidelines for SAP HANA must be adhered to.In addition to these general authorization concepts, each type of SAP Fiori app has additional authorization and role concepts to befollowed.

1.2.3.1.3.1 Authorizations and Roles for Transactional Appsand Fact Sheets The authorization and role concept for transactional apps and fact sheets consists of authorizations and roles in SAP NetWeaverGateway and the ABAP back-end server.

Authorizations and Roles in SAP NetWeaver GatewayFiori applications communicate with the ABAP back end through OData services, which must be activated during system installation. Inaddition to authorization in the back-end system, users must be granted authorization to access the HTML 5-based Fiori applicationsand the OData services in SAP NetWeaver Gateway. Fiori applications therefore require users and roles in SAP NetWeaver Gateway.A Gateway PFCG role contains start authorizations for OData Services. SAP will not deliver these roles to customers.To enable back-end OData service execution of the Fiori application, a role with authorization object S_SERVICE (Check at Start ofExternal Services) with the corresponding service name has to be created and assigned to the user in SAP NetWeaver Gateway.1. Activate the app-specific OData service while configuring SAP NetWeaver Gateway.

The name of the activated service is required later to maintain the authorization.2. In transaction PFCG, create a service-specific or app-specific role with authorization object S_SERVICE. Do not specify further

authorization values. Exit authorization maintenance.3. On the menu tab, insert a node into the role menu by choosing Authorization Default TADIR Service. Enter the following values:

R3TRIWSG<activated service name>

4. Generate the profile in authorization maintenance.5. Assign the new role to the SAP Fiori app user.After you create the SAP NetWeaver Gateway PFCG roles, you must identify the corresponding roles in the ABAP back-end server forexecution of the OData services and define the corresponding profiles for the SAP NetWeaver Gateway roles.

Authorizations and Roles in the ABAP Back-End ServerFor transactional applications and fact sheets, ABAP back-end users with corresponding roles and authorizations are necessary. SAPdelivers back-end PFCG roles for every transactional application and fact sheet.Theses roles provide authorizations for the OData service of the apps. Observe that the roles for the transactional apps do notcomprise authorizations for business data to be displayed in the app. It is assumed that these authorizations will be provided by thecustomer.The back-end roles for fact sheets contain authorizations to display business data, and furthermore they include the search modelsrelated to the fact sheets.SAP delivers back-end roles for each transactional application and fact sheet. For every role, authorizations need to be grantedaccording to the customer’s roles and authorization concept.To copy and adjust the roles delivered by SAP and to assign users to these roles the following steps, proceed as follows:1. Execute transaction SU25 to transfer information about the relevant OData services from SU22 to SU24.

This step is required to prevent data overwriting during import of updates.2. Copy the application specific roles with the corresponding business authorizations to your namespace.3. Adapt the authorizations of the roles in transaction PFCG according to your authorization concept.4. Assign application users to these adapted roles in transaction SU01.

User names in the ABAP back-end server must be identical to the corresponding user names in the ABAP front-end server. Usermapping is not supported. For this purpose, you can use Central User Administration (CUA) or identity management systems.

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 25 of 78

More InformationFor information about authorizations in SAP NetWeaver Gateway, see http://help.sap.com/nwgateway Configuration andDeployment Information Configuration Guide OData Channel Configuration User, Developer and Administrator Authorizations .For information about authorizations and roles required for the ABAP front-end server, see Setup of Catalogs, Groups, and Roles in theFiori Launchpad.For information about authorizations and roles required for the ABAP back-end server (SAP Fiori Design transactional apps andFactsheet apps), see Roles, Users, and Authorizations on ABAP Back-End Server (Transa.

1.2.3.1.3.2 Authorizations and Roles for SAP Fiori Launchpad The basic ingredients for the authorization concept for SAP Fiori Launchpad are the authorizations in the ABAP back-end server and theauthorizations to access the OData services in the SAP NetWeaver Gateway in the ABAP front-end server.All SAP Fiori apps are launched via SAP Fiori Launchpad. The SAP Fiori apps are delivered with SAP Fiori Launchpad catalogs and UIPFCG roles. A user is offered catalogs of applications in SAP Fiori Launchpad based on the UI PFCG role assigned to the user. Thefront-end user with the according UI PFCG role may then select a group of favorite apps from of the catalogs.

The catalog of SAP Fiori apps with provides information about the specific UI PFCG Role required for each app.

In addition, a technical role is needed for the SAP Fiori Launchpad. SAP delivers a predefined set of technical objects for the SAP FioriLaunchpad, in particular the required profiles, which you can copy to set up your own catalogs for the roles within your companyIn order to use the SAP Fiori apps, corresponding back-end PFCG roles are provided and adjusted. The UI PFCG roles bundle all front-end privileges required for execution of the apps. Through the user assignment to back-end roles, additional privileges are provided toexecute the application or OData service.Fact sheets additionally require authorization roles in the front end, which grant the users authorizations for the ICF services andbusiness server pages (BSP) for the fact sheets.

More InformationFor more information about authorizations and role for SAP Fiori Launchpad, see SAP Library for User Interface Add-On 1.0 for SAPNetWeaver on SAP Help Portal at http://help.sap.com/nw-uiaddon Administration Guide Content Administration SAPFiori Launchpad .

1.2.3.1.3.3 Authorizations and Roles for Analytical Apps andSAP Smart Business Apps SAP Fiori analytical apps and SAP Smart Business apps are based on SAP HANA. These apps generate OData requests that exposecertain views in SAP HANA. Therefore, these apps follow the authorization mechanisms provided by SAP HANA.In particular, a user of one of these apps must have a matching SAP HANA database user through which access to SAP HANAdatabase content is controlled. Therefore, the user’s roles in the app and the user’s privileges in SAP HANA have to be alignedaccordingly.

More InformationFor information about setting up the required authorizations and roles, see the corresponding Configuration sections of the SAP Fiori forSAP Business Suite documentation and the Administration Guide for SAP Smart Business Applications.

1.2.3.2 Session Security Protection You must establish session security protection for the ABAP front-end server and, if part of the system landscape, SAP HANA ExtendedApplication Services (SAP HANA XS).

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 26 of 78

1.2.3.2.1 ABAP Server Session Security For the ABAP front-end server and the ABAP back-end server running Enterprise Search, you must activate HTTP security sessionmanagement by using the transaction SICF_SESSIONS. When you activate HTTP security session management, we recommend youactivate the following extra protection for security-related cookies:HttpOnlyThis attribute instructs the browser to deny access to the cookie through client side script. As a result, even if a cross-site scripting(XSS) flaw exists and a user accidentally accesses a link that exploits this flaw, the browser will not reveal the cookie to a third party.SecureThis attribute instructs the browser to send the cookie only if the request is being sent over a secure channel such as HTTPS. Thishelps protect the cookie from being passed over unencrypted requests.

In addition, we recommend configuring HTTP session expiration with a reasonable timeout. To configure this, you use the profileparameter http/security_session_timeout.

More InformationFor more information about activating HTTP security session management, see http://help.sap.com/nw73 Function-Oriented View Security User Authentication and Single Sign-On Authentication Infrastructure AS ABAP AuthenticationInfrastructure Activating HTTP Security Session Management on AS ABAP .For more information about session security protection for SAP NetWeaver Gateway, see http://help.sap.com/nwgatewaySecurity Information Security Guide Session Security Protection .

1.2.3.2.2 SAP HANA XS Session Security For session security, SAP HANA XS automatically configures the session cookie xsSessionId with the attribute HttpOnly.However, the attribute secure is not supported. If you use a reverse proxy (instead of SAP Web Dispatcher) in your systemlandscape, you can add this attribute by configuring the reverse proxy with a header rewrite rule on the Set-Cookie header.

More InformationFor more information about defining access to individual application packages in SAP HANA XS, see http://help.sap.com/hana_platform Development Information Developer Guide Setting Up Your Application Creatingthe Application Descriptors The Application-Access File .

1.2.3.2.3 Logout from Multiple Systems SAP Fiori apps only support logout with the ABAP front-end server and a single SAP HANA XS. If additional SAP Netweaver Gatewaysystems or SAP HANA XS systems are deployed (for example, to distribute OData services across multiple server farms), thecorresponding http sessions are not closed when the user logs out. In this case, it is important to have session expiration configured.

1.2.3.2.4 Cross-Site Request Forgery Protection (CSRF) A token-based protection against CSRF is active by default in SAP Netweaver Gateway and SAP HANA XS Fiori OData services. Itprotects all modifying requests.

1.2.3.3 Network and Communication Security Your network infrastructure is extremely important in protecting your system, and must support the communication necessary for yourbusiness needs without allowing unauthorized access. A well-defined network topology can eliminate many security threats resulting

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 27 of 78

from software flaws or network attacks.If users cannot log on to your application or database servers at the operating system or database layer, there is no way for intruders tocompromise the machines and gain access to the SAP system’s database or files. Additionally, if users cannot connect to the serverlocal area network (LAN), they cannot exploit well-known bugs and security holes in network services on the server machines.The network topology for SAP Fiori components is based on the topology used by SAP NetWeaver Gateway, SAP NetWeaver andSAP HANA. Therefore, the security guidelines and recommendations described in the corresponding security guides also apply to SAPFiori components.

1.2.3.3.1 Communication Channel Security

Communication PathsThe following table shows the communication channels used by the SAP Fiori apps, the protocol used for the connections, and the typeof data transferred:Communication Path Protocol Used Type of Data TransferredWeb browser to SAP Web Dispatcher OData

HTTP/HTTPSApplication data and security credentials

SAP Web Dispatcher to ABAP front-endserver (SAP NetWeaver Gateway)

ODataHTTP/HTTPS

Application data and security credentials

SAP Web Dispatcher to HANA XS ODataHTTP/HTTPS

Application data and security credentials

SAP Web Dispatcher to ABAP back-endserver (ERP, CRM, SRM, SCM)

INAHTTP/HTTPS

Application data and security credentials(for search and back-end transactions)

ABAP front-end server to ABAP back-endserver (ERP, CRM, SRM, SCM)

RFC Application data and security credentials

ABAP back-end server to SAP HANA / anyDB

SQL Application data and security credentials

Communication EncryptionTo ensure confidentiality and integrity of data, we recommend encrypting all communication channels as follows:

Protect HTTP connections by using Transport Layer Security (TLS) or Secure Sockets Layer (SSL).Protect RFC connections by using Secure Network Communications (SNC).Protect SQL connections by using Secure Sockets Layer (SSL) or Transport Layer Security (TLS).

More InformationFor information about setting up communication encryption for SAP NetWeaver, see http://help.sap.com/nw74/ SecurityInformation Security Guide Network and Communication Security Transport Layer Security .For information about setting up communication encryption for SAP HANA, see http://help.sap.com/hana_platform Security Information SAP HANA Security Guide SAP HANA Network and Communication Security Securing Data Communication .

1.2.3.3.2 Network Security

1.2.3.3.2.1 Configuring SAP Web Dispatcher SAP Fiori client applications are HTML5 applications that access multiple back-end systems. However, JavaScript code is constrainedby the Same Origin Policy. For this reason, all systems are exposed to the browser through the SAP Web Dispatcher (or a reverseproxy), which brings them into a common origin (combination of protocol, hostname, and port).In addition to solving the same origin problem, this enables you to control which services are effectively exposed to the client, reducingthe system attack surface.We recommend that only those requests corresponding to the services required for the applications that you want to use should berouted to the application servers. To do this, you can configure URL filtering / routing at the SAP Web Dispatcher or reverse proxy levelbased on the type of apps you implement.

Transactional apps

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 28 of 78

For transactional apps, it is particularly important to control which services are exposed to the client because transactional appsallow for Internet-facing scenarios.Analytical apps and SAP Smart Business appsAnalytical apps consume OData Services exposed by SAP HANA. We recommend explicitly restricting access to those ODataServices actively used by configuring respective redirection rules in SAP Web Dispatcher or the reverse proxy of your choice. Formore information about configuring SAP Web Dispatcher for analytical apps, see the Configuration section of the SAP Fioridocumentation.Search in SAP Fiori LaunchpadSearching in the SAP Fiori Launchpad triggers requests towards the ABAP back-end server. You can enable or disable the search byconfiguring access to the corresponding services under /sap/es/. For example, you can switch off search access from outside thecorporate intranet by disabling the path to /sap/es/ in your SAP Web Dispatcher or reverse proxy configuration.For more information, enter the key words SAP Web Dispatcher Configuration for the Search in the documentation of the UserInterface Add-On for SAP NetWeaver under http://help.sap.com.

More InformationFor more information about using SAP Web Dispatcher as a URL filter, see http://help.sap.com/nw73 Application Help Function-Oriented View Application Server Application Server Infrastructure SAP Web Dispatcher Administration of the SAP WebDispatcher SAP Web Dispatcher as a URL Filter .

1.2.3.3.2.2 Rewriting URLs SAP NetWeaver Gateway and SAP HANA XS OData services may return some absolute URLs. When these services are accessedthrough a reverse proxy, these URLs may be invalid and/or disclose system information (protocols, hostname, and port numbers).Therefore, we recommend configuring URL rewrite rules at the reverse proxy level. The data to process can be identified through itsContent-Type HTTP header. The following content should be processed:

Text/HTMLApplication/XMLApplication/JSON

1.2.3.3.2.3 Internet-Facing Deployment Only transactional SAP Fiori apps are supported for consumption by Internet clients. This can include mobile devices that are notconnected to the corporate intranet, for example when a user is travelling.We recommend keeping the SAP Web Dispatcher for SAP Fiori and the SAP NetWeaver Gateway in the intranet zone and deployingan additional SAP Web Dispatcher (or another reverse proxy) in the DMZ. This additional SAP Web Dispatcher should allow onlyrequests that will be routed to the common ICF services or to the apps that must be exposed.In particular, we recommend blocking all requests to the following:/sap/hba/* (SAP HANA XS)/sap/es/* (Enterprise Search)

More InformationFor more information about using multiple network zones, see http://help.sap.com/nw731 SAP NetWeaver Security GuideNetwork and Communication Security Using Multiple Network Zones .

1.2.3.4 Internet Communication Framework Security SAP Fiori transactional applications and fact sheets consist of SAP NetWeaver Gateway OData services and HTML5/SAP UI5-basedWeb-enabled content managed by the Internet Communication Framework (ICF). You must use the transaction SICF to activate the ICFservices required for the applications that you want to use.The following anonymous ICF services are common to all SAP Fiori apps and must be activated:/sap/public/bc/ui5_ui5/sap/public/bc/ui2This ICF service is only required if you use SAP Fiori ICF system logon class /UI2/CL_SRA_LOGIN for form-based authentication.

The following authenticated ICF services are common to all SAP Fiori apps and must be activated:/sap/bc/ui2/start_up

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 29 of 78

/sap/bc/ui5_ui5/ui2/ushell/sap/bc/ui2/iframe_logon/sap/opu/odata/UI2/PAGE_BUILDER_PERS

For further required ICF services for individual applications, see the app-specific SAP Fiori documentation.

If your firewalls use URL filtering, also note the URLs used for the services and adjust your firewall settings accordingly.

Services for the Embedded SearchTo enable the search in the SAP Fiori launchpad and to enable the fact sheets, you need to activate the ICF services for the EmbeddedSearch in the back end. For more information, enter the key phrase Setting Up Embedded Search in the documentation of SAPNetWeaver under http://help.sap.com. The relevant ICF services are listed under Activating UI Services.

More InformationFor more information about activating ICF services, see Activate ICF Services.For information about activating OData services, which are required for ICF services, see Activate OData Services.

1.2.4 Operations This guide covers the general steps to take when operating SAP Fiori apps. Where necessary, these instructions refer to app-specificdocumentation.

1.2.4.1 Monitoring SAP Fiori Apps SAP NetWeaver Gateway plays an important role within the system landscape for SAP Fiori apps. Therefore, monitoring SAPNetWeaver Gateway is essential for monitoring SAP Fiori apps.SAP Solution Manager 7.1 SP04 or higher supports a root-cause analysis for SAP NetWeaver Gateway. For more information, see https://service.sap.com/support SAP Solution Manager Run SAP like a Factory Application Operations End-to-EndRoot Cause Analysis . Also, see SAP Note 1478974.For more information on monitoring SAP NetWeaver Gateway, see SAP NetWeaver Gateway Technical Operations Guide.

1.2.5 Extensibility This guide covers the general steps to take when extending SAP Fiori apps. It focuses on UI extensibility, and ontains references to thedocumentation for extension of other layers.

If you want to change the branding of an SAP Fiori app, use Theme Designer. For more information, see the documentation.

Target GroupThis guide is aimed at the following:

Solution ConsultantsDevelopment Consultants

1.2.5.1 Extending SAP Fiori Applications

Note

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 30 of 78

Extending SAP Fiori apps involves extending certain content layers. You might not have to extend all layers each time you want toenhance an application. To view the criteria for whether or not a layer must be extended see Content Layer Considerations.

1.2.5.1.1 Architecture Overview SAP Business Suite on HANA features an ABAP engine, which is used for transactional applications, and an XS Engine, which is usedfor analytical applications running on the same HANA database instance. Back-end application artifacts and application content arestored in the HANA database, as illustrated in the figure below.In addition, the UI apps are deployed on a central SAP ABAP NetWeaver server, which also contains the UI Service Add-on for the shellservices and the Gateway Add-on for the OData enablement of the ABAP-based Suite system.The SAP HANA XS Engine provides a separate OData channel. The Web Dispatcher routes the HTML and OData requests.

SAP Fiori Architecture

Fiori apps are created using HTML5 and SAPUI5. For some extensions, the underlying jQuery JS library may be used. All supportedform factors and operating systems are supported with one development project and a single code line per user interface app.

1.2.5.1.2 Application Types There are three different application types delivered with SAP Fiori. They are Transactional apps, Analytical apps, and Fact Sheets.

Transactional AppsThese apps run best on HANA, but can also run with any database.

Analytical AppsThese are purely analytical apps that will run only on HANA following the HANA Live (2-tier) architecture and using virtual data models(VDM). Typical representatives are Smart Business KPI Cockpits but also include other analytical, predictive, and planning applications.These apps are not ported to any other database (AnyDB). They either use Smart Business KPI Framework or HANA Live and XSOData.

Fact SheetsFact sheet apps run on HANA and the ABAP stack. These scenarios are not ported to any other databases (AnyDB).

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 31 of 78

1.2.5.1.3 Content Layer Considerations You can extend the functionality of SAP Fiori apps by enhancing some of the content layers. The criteria for determining whether or notyou need to enhance a layer are described in the following table:Content Layer When an Extension is Required RelevanceBusiness Suite The back-end logic and content required

for the application enhancement does notexist in the Business Suite.

Relevant for transactional apps.Extensions in this layer are not coveredhere. Consult the app-specificdocumentation.

Gateway The back-end logic and content requiredfor the app extension exists in the BusinessSuite layer, but is not exposed in the app'sGateway service.

Relevant for transactional and analyticalapps.Extensions in this layer are not coveredhere in detail. For more information, seeExtending the SAP NetWeaver GatewayLayer.

HANA The back-end content required for the appextension exists in the HANA models, butis not exposed in the app's OData service.

Relevant for analytical apps.Extensions in this layer are not coveredhere in detail. For more information, seeExtending the SAP HANA Layer.

UI The back-end logic and content requiredfor the app extension exists in the Gatewaylayer, but is not exposed in the app's UI.

Relevant for transactional and analyticalapps.This is covered in detail. See Extending theUI Layer.

Search Model The back-end logic is not exposed in theapplication’s Gateway service.

Relevant for fact sheets.Extensions in this layer are not coveredhere in detail. For more information, seeExtending the Search Model Layer.

1.2.5.1.4 Extending Content Layers The knowledge required to extend each content layer is indicated in the following table:Content Layer ABAP Business Suite SAP NetWeaver

GatewayHANA NativeDevelopment

SAPUI5 OData ProtocolHTML5,JavaScript

Fiori specific UIDevelopment

Business Suite X XGateway X XHANA XUI X X XSearch Model X X

The tools required to extend each content layer are indicated in the following table:Content Layer ABAP Object

Navigator (se80)ABAP Dictionary(se11)

ABAPCustomizing(spro)

HANA Studio SAP NetWeaverGatewayService Builder(segw)

Eclipse withABAPRepositoryTeam Provider

Smart BusinessModeler

Business Suite X XGateway X X XHANA XUI forTransactionalapps

X

UI forAnalytical type(a)

X

UI forAnalytical type(b)

X

UI forFactsheets

X

Search Model X

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 32 of 78

1.2.5.2 Extending the SAP NetWeaver Gateway Layer You extend an app’s Gateway layer when you need to expose back-end logic and content to the UI layer.

1.2.5.2.1 OData Extensibility You can achieve modification-free extensibility by using the Redefine Gateway Service function. For more information, see RedefiningOData Services (GW).By extending an OData service you are creating a custom OData service, or OData project, that redefines an SAP-delivered one.

Redefinition of SAP-Delivered OData Project

1.2.5.2.1.1 OData Extensibility in Gateway You extend an app's Gateway layer when you need to expose back-end logic and content to the UI layer. In SAP NetWeaver GatewayService Builder (transaction SEGW), redefine the relevant Gateway service for the app.To get the name of your BSP application, refer to the application-specific documentation.Refer to SAP Note Number 1919388 for details of how to extend an OData service.For more information, see Extending an OData Service Using Service Builder and Redefining Services.Using this approach leads to runtime artifacts where the Customer Data Provider Class (DPC) class is a subclass of the SAP-deliveredclass.You can check this by examining the superclass of the Customer’s DPC classes.

To avoid collisions between customer-specific and SAP-specific names, ensure you create the names in the customer namespace.Alternatively, use prefixes, such as Y or Z. This is relevant for OData properties, entity types, navigation properties, associations,entity sets, and method.

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 33 of 78

1.2.5.3 Extending the SAP HANA Layer When you need to expose back-end fields to the UI layer, you modify an app’s HANA layer. The HANA objects that you want to modifycan be of different types, such as HANA views and HANA .xsodata files. You copy the SAP-delivered objects into the customer-specificpackage, and then you modify the customer objects.For more information, see the SAP HANA Developer Guide at http://help.sap.com SAP In-Memory Computing SAP HANA SAP HANA Platform Development Information SAP HANA Developer Guide .

1.2.5.4 Extending the UI Layer When the back-end logic and content required for the app extension exists in the Gateway layer, but is not exposed in the app’s UI, thenyou need to extend the app’s UI layer.This section covers three cases. The first involves modification-free extensibility. For more information, see Custom ApplicationExtensibility.The second covers extending the UI for transactional apps and for analytical apps that use HANA Live and XS OData. For the detailedworkflow, see UI Extensibility Workflow.The third covers analytical apps that use the Smart Business KPI Framework. For more information, see UI Extensibility for AnalyticalApps using Smart Business.

1.2.5.4.1 Custom Application Extensibility The extensibility concept allows you to create modification-free extensions for certain extensibility use cases. A modification-freeapplication requires no modifications in the SAP-delivered standard application. This protects the customer investment and at the sametime allows SAP upgrades to perform without interfering with the custom application.The concept uses the extension capabilities of the UI components and the JavaScript classes.A typical SAP-delivered standard application consists of bootstrap files, views, view controllers, and internationalization files. A customapplication extends an SAP-delivered standard application and consists of the bootstrap file Component.js, which extends theComponent.js of the SAP standard application, internationalization file, view fragments, views, and view controllers.Modification-free extensions are possible in the following cases:

View extensionsView modificationsView replacementsConfiguration for overriding or extending the navigation routesController extensionController replacementExtending the internationalization (i18n) stringsOverriding or adding OData service URLs

When the custom application is started, at runtime, the resources of both the SAP-delivered standard application and the customapplication are merged to create a single runtime artifact. The Component.js in the custom application is merged withComponent.js in the SAP-delivered standard application at runtime.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 34 of 78

Representation of View Extensions

For more information on Creating an SAP UI5 Application, please refer to the documentation at http://help.sap.com/netweaver User Interface Add-On for SAP NetWeaver Application Help Developer Guide Getting Started Create Your First SAPUI5 Application .

ResultAt the end of all the steps to create a custom application that extends an SAP-delivered standard application, the SAP Fiori end-usergets to see a custom tile on the SAP Fiori Launchpad, as shown below.

New Custom Tile on Launchpad

1.2.5.4.2 UI Extensibility Workflow

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 35 of 78

When the back-end logic and content required for the app extension exists in the Gateway layer, but is not exposed in the app’s UI, thenyou follow this workflow.

PrerequisitesBefore beginning, you should complete the following steps:

Install ABAP Development Tools for SAP Netweaver.Refer to https://tools.hana.ondemand.com/#abap for setting up ABAP Team ProviderInstall the SAPUI5 Application Development Tool for Eclipse.Refer to SAP Note 1747308 for the Installation of UI development toolkit for HTML5 (SAPUI5)Ensure that all SAPUI5 plugins are version 1.16.2 or higherVersion numbers appear on the Installed Software tab. See Help About Eclipse Installation Details .Ensure the local Tomcat webserver is configured to work with SAPUI5 Eclipse

In case the ABAP system where the UI application is deployed is based on NW 7.31, then you can use the ABAP Repository TeamProvider. For releases lower than NW 7.31, you can use SAPUI5 Application Development plug-in of Eclipse and use theupload/download mechanisms described in the linkhttps://sapui5.hana.ondemand.com/sdk/#docs/guide/UI5BSPRepository.html

ProcessThese are the steps in the process for extending the UI of SAP Fiori Design applications.Task Definition1 Download the SAP-delivered standard application from the ABAP

system2 Test the SAP-delivered standard application in the local

Launchpad sandbox environment3 Create a custom application that extends an SAP-delivered

standard application4 Check the SAP-enabled extension options5 Define the extensions metadata6 Test the custom application on the local Launchpad sandbox

environment7 Upload the custom application to the ABAP system8 Smoke-test the custom application on the ABAP system9 Configure the custom application on Fiori Launchpad10 Test the custom application on Fiori Launchpad

1.2.5.4.2.1 Download the SAP-Delivered Standard Applicationfrom the ABAP System

PrerequisitesBefore doing this step, you should know the following:1. The BSP Application Name of the app you want to extend2. The OData service URL that contains the required extensionsIn order to get the BSP Application Name for a given SAP Fiori app, please refer to the app-specific documentation.

Downloading SAP UI 5 Application ProjectFor detailed steps, see the chapter Retrieving the SAPUI5 Application Project from the SAPUI5 Repository in the Developer Guide forUser Interface Add-On at http://help.sap.com/nw-uiaddon Development Information Developer’s Guide

The project name in Eclipse for the SAP-delivered standard application should be same as the BSP application service name on theserver. Use transaction SICF on the ABAP server to get the service name.

Note

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 36 of 78

1.2.5.4.2.2 Testing the SAP-Delivered Standard Application For Tomcat and Eclipse configuration details, see the chapter Test Your SAPUI5 Application on a Java Web Server in the DeveloperGuide for User Interface Add-On at http://help.sap.com/nw-uiaddon Development Information Developer’s Guide To use the proxy, you need to change the OData service URL of the SAP-delivered standard application. First, look for the ODataservice URL in the Configuration.js file inside the WebContent folder. Inside the file, look for an object called serviceList and a propertycalled serviceUrl. Then change it to what is shown below.

01. insert code grab

To configure the application on the local sandbox environment for the Launchpad, use this link:https://proddps.prod.jpaas.sapbydesign.com/dps/d/preview/67986e4c1e4b41bc8f2b9eb4b7ecf972/1.06/en-US/frameset.htm?896efc419d994463a7c148b6904760a8.html.

1.2.5.4.2.3 Creating a Custom Application To create a custom application, perform the following steps:1. In Eclipse, create a new SAPUI5 Application Project.2. Create component.js and define the extension metadata.3. Implement extension by creating the views, controllers, and i18n properties.

In order that there are no collisions between customer and SAP names in the Properties/Methods of the controllers, ensure that youname them in the customer namespace.

In order that there are no collisions between customer and SAP names in the view Control IDs, ensure that you name them in thecustomer namespace.

Although collisions may not occur in the current version, they may occur after SAP ships new versions.

1.2.5.4.2.4 Checking the SAP-Enabled Extension Options The extensibility concept provides a very high flexibility of extensions. However, flexibility leads to complexities. There are differentextension options. You should look for specific places where SAP has enabled extension points. Check if you can meet the extensionrequirements by using one of the following options:

i18n Resource ExtensionView ModificationView ExtensionController Extension using a Hook

Where these options are not sufficient to achieve a given requirement, check the following options:View ReplacementController ExtensionCustom View

Only use these options as a last resort for achieving extensibility use cases.

1.2.5.4.2.5 Defining Extensions Metadata

Syntax

Note

Note

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 37 of 78

The extensions metadata is defined in the Component.js file of the custom project. The Component.js file has an json objectcalled metadata. The object metadata contains the following objects: routing, config, and customizing.Object Name Useconfig Used to define metadata for the following:

Custom OData URLCustom i18N bundle name

customizing Used to define metadata for the following:View extensionsView modificationsView replacementsController extensions

routing Used to define metadata for new navigation routes in the followingcases:

Customer views are addedCustomer wants to change a navigation route

The object customizing supports the following objects and their usages are mentioned in the table below:Object Name Usesap.ui.viewExtensions Used to add a new view element to the standard view at the

defined extension points.sap.ui.viewModifications Used to change the property value of a control in the view.sap.ui.viewReplacements Used to replace a standard view with a view in the custom

application.sap.ui.controllerExtensions Used to extend the functionality of the base controller.

The object config supports the following objects and their usages are mentioned in the table below. Refer tohttps://sapui5.netweaver.ondemand.com/sdk/#docs/guide/Customization.html for more details.Object Name Usesap.ca.i18Nconfigs Used to replace or augment the internationalization strings with

strings defined in the custom application.sap.ca.serviceConfigs Used to add or change the oData Service definition with oData

service defined in the custom application.

For more information about the usage of the object routing. see Refer tohttps://sapui5.netweaver.ondemand.com/sdk/#docs/guide/Navigation.html for the usage of object “routing”.For examples and more information about the object json, see http://www.w3schools.com/json/.

1.2.5.4.2.6 Testing the Custom Application To test the custom application, see the section Run Your Own Applications in the Sandbox athttps://proddps.prod.jpaas.sapbydesign.com/dps/d/preview/67986e4c1e4b41bc8f2b9eb4b7ecf972/1.06/en-US/frameset.htm?896efc419d994463a7c148b6904760a8.html.

1.2.5.4.2.7 Uploading the Custom Application to SAPUI5Repository You then need to upload the custom application to the SAPUI5 repository. For detailed steps, see the chapter Sharing the SAPUI5Application Project with the SAPUI5 Repository in the Developer Guide for User Interface Add-On at http://help.sap.com/nw-uiaddon Development Information Developer’s Guide .

1.2.5.4.2.8 Smoke-Testing the Custom Application on theABAP System For detailed steps in smoke-testing the custom application, see the chapter Test Your SAPUI5 Application on an ABAP Server in the

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 38 of 78

Developer Guide for User Interface Add-On at http://help.sap.com/nw-uiaddon Development Information Developer’sGuide .

1.2.5.4.2.9 Configuring the Custom Application on the FioriLaunchpad Now you need to set up the custom application on the SAP Fiori Launchpad. For detailed steps, see Setting up Navigation athttp://help.sap.com/nw-uiaddon. In SAP Library, choose Administration Guide Content Administration SAP FioriLaunchpad .

1.2.5.4.2.10 Testing the Custom Application on the FioriLaunchpad Launch the SAP Fiori Launchpad, and then click the custom application tile.

1.2.5.4.3 UI Extensibility for Analytical Apps using SmartBusiness To extend or customize analytical apps that run using the Smart Business Framework, see the KPI Modeler documentation, specificallythe section Managing Visualizations, at http://help.sap.com/in_memory SAP HANA Innovations for SAP Business SuiteSAP Hana Live for Smart Business Applications Smart Business Applications .

It is also possible to change the appearance of the SAP Fiori Launchpad. For detailed steps, see Adjusting the Visual Appearance ofthe Launchpad at http://help.sap.com/nw-uiaddon. In SAP Library, choose Administration Guide Content AdministrationSAP Fiori Launchpad .

1.2.5.5 Extending the Search Model Layer When the back-end logic is not exposed in the application’s Gateway service, you extend the Search Model layer.

1.2.5.5.1 Fact Sheet Extensibility If the fact sheets delivered by SAP do not meet your requirements, you can extend them by a new field, for example a new object suchas an additional date, or an internal, or external key figure. New fields are delivered by an appropriately extended search model to theSAP NetWeaver Gateway in an OData service. The OData service provides the back-end information to the UI.A fact sheet is created generically based on the semantic and object structure information coming from an annotation file. Technically, afact sheet is represented by a combination of:

A search modelPotentially some enhancementsAn OData service derived from the enhancementsA BSP application with an annotation file that defines the link between the OData service, and a generic user interface

ActivitiesTo extend a fact sheet, the following steps are necessary:1. Extend the search model with the required fields.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 39 of 78

The corresponding OData service is enhanced automatically.2. In SE80, search for the suitable BSP application with *BSCBN_ANF*.3. Copy the content of the attached annotation file into another editor, and make your changes in the annotation file.4. Create your own BSP application.5. Copy the content of the extended annotation file to the new BSP application.6. Register the BSP application in the Launchpad Customizing (LPD_CUST).

More InformationExtending a Search ModelAnnotation FileConfiguring Enterprise Search (Search and Fact Sheets)SAP Fiori Design Types and Database RequirementsFor more information about Launchpad Customizing, see SAP Help Portal at http://help.sap.com/nw-uiaddon Application Help Content Administration Fiori Launchpad Fiori Launchpad Navigation Customizing Navigation Targets .

1.2.5.5.1.1 Extending a Search Model If the search models delivered by SAP do not meet your requirements, you can change existing search models. You can extend thesearch model by an additional field to be searched for.

More InformationFor more information about creating and changing search models, see SAP Help Portal at http://help.sap.com SAPNetWeaver SAP NetWeaver Platform 7.3 Embedded Search Developer’s Guide Creating or Enhancing Search Models .SAP Fiori Design Types and Database RequirementsConfiguring Enterprise Search (Search and Fact Sheets)

1.2.5.5.1.2 Checking the Properties of an OData Service In the SAP NetWeaver Gateway, you can check all generated properties, that is all fields existing in the back-end system and deliveredby the search model to the OData service.

Activities1. To get an overview of all generated properties, that is all fields existing in the back-end system and delivered by the search model,

open the SAP NetWeaver Gateway via transaction /IWFND/MAINT_SERVICE.2. Search for services named *CB*SRV*, and choose the service that corresponds to your needs.3. Choose Gateway Client, and the Add URI Option pushbutton.

Choose a URI Option. The system checks the fields coming from the back end and generates a URI that you can use to call theOData service.

4. Choose Set Meta Data.The system provides all fields selected by the search model in the back end.

More InformationUsing Annotation TagsFact Sheet ExtensibilityExtending a Search ModelConfiguring SAP NetWeaver Gateway

1.2.5.5.1.3 Annotation File An annotation file is a semantic description of an OData service. It delivers semantic information to properties and entity types deliveredby the OData service, which can be used for a generic rendering for a fact sheet. The description is defined by a sequentiality ofannotations that are tags following a special syntax. Annotation tags use terms that are defined in vocabularies, either OData core ordelivered by SAP.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 40 of 78

<Annotation Term="UI.LineItem">The term UI.LineItem is defined in the vocabulary as <Term Name="LineItem"Type="Collection(UI.DataFieldAbstract)" AppliesTo="EntityType">

An annotation file consists of:A setup area that references the vocabularies, the XML name spaces, and one or several OData services, which provide data to theannotation file.A vocabulary is a set of semantic and structuring term definitions. Vocabularies are delivered by SAP.

01. <edmx:Reference Uri="/sap/bc/ui5_ui5/ui2/ushell/resources/sap/ushell/components/factsheet/vocabularies/Communication.xml"><edmx:Include Namespace="com.sap.vocabularies.Communication.v1" Alias="vCard"/></edmx:Reference>

An annotation area that provides a semantic description of the OData service referencing the entity types and properties of thecorresponding OData service.An annotation file always refers one or several targets. Each annotation has a target, which refers an entity type or a property of theOData service used.

01. <Annotations Target="EPMModel.Product">02. <Annotation Term="UI.HeaderInfo">03. <Record>04. <PropertyValue Property="TypeName" String="Product" />05. <PropertyValue Property="TypeNamePlural" String="Products" />06. <PropertyValue Property="TypeImageUrl" String="/sap/bc/ui5_ui5/ui2/ushell/resources/sap/ushell/componen

ts/factsheet/vocabularies/Communication.xml" />07. <PropertyValue Property="ImageUrl" Path="ImageUrl" />08. <PropertyValue Property="Title">09. <Record>10. <PropertyValue Property="Label" String="Product" />11. <PropertyValue Property="Value" Path="Name" />12. </Record>13. </PropertyValue>14. <PropertyValue Property="Description">15. <Record>16. <PropertyValue Property="Label" String="Description" />17. <PropertyValue Property="Value" Path="Description" />18. </Record>19. </PropertyValue>20. </Record>21. </Annotation>

Each annotation refers to a term of a vocabulary. The features of annotations are:Mapping properties of an OData service to the terms of a vocabulary, that is, the entity types and properties of the correspondingOData service are referenced in the properties of annotation terms.Defining semantic terms, such as header, identification, or line item.Defining areas on the UI, such as facets.With a facet, you define a structure in your annotation file, where you can refer annotations defined before, such as header,identification, or line item.

More InformationFact Sheet ExtensibilityExtending a Search ModelUsing Annotation TagsAdding a New Field to a Fact SheetAdding Key Figures to a Fact Sheet

1.2.5.5.1.3.1 Using Annotation Tags With annotation tags, you provide semantic information for properties and entity types of an OData service. For example, you define thesemantic description of the identification area, or the UI structure by facets. As a prerequisite, the corresponding OData serviceretrieves data from the back-end system via a search model. You can use the data provided by the OData service in your annotationfile.

Example

Syntax

Syntax

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 41 of 78

IntegrationThe following table provides an overview how an extended search model is reflected in an OData service.Search Model OData ServiceField Property of an Entity TypeModel Response Entity Type

The following table provides an overview how entity types of an OData service are reflected in annotation files with their tags.OData Service Annotation TagProperty of an Entity Type Property with PropertyValue

Annotations TargetEntity Type Annotations Target

FeaturesIn an annotation file, the following tags are available:

For the identification of the object to be displayed on the UI:The Annotations Target="‘Entity Type of the OData service’“> references the entity type provided by the OData service.For the semantic description of the entity types and properties of an Odata service:<Annotation Term="‘Vocabulary Alias’.HeaderInfo">Defines the header information, which must be defined for all objects of the corresponding OData service. It shows language-dependent object information.<Annotation Term="‘Vocabulary Alias’.Identification">Defines the header information, plus a set of attributes identifying the object.<Annotation Term="‘Vocabulary Alias’.Badge">Defines a business card view, with the most important properties and data fields of the object.<Annotation Term="‘Vocabulary Alias’.LineItem">Defines detailed information for the object, which can be linked and displayed in a separate screen, as a table. Line items can besorted, grouped, or filtered.<Annotation Term="‘Vocabulary Alias’.FieldGroup">Defines a group of fields belonging together semantically, and references an entity type of the corresponding OData service.<Annotation Term="‘Vocabulary Alias’.DataPoint">Defines key figures for the object, which are provided by the corresponding OData service, or any other OData service, that is froman SAP HANA database.<Annotation Term=“‘Vocabulary Alias’.Importance”EnumType=”Vocabulary Alias.Priority/High”/>Combined with the Identification, or LineItem term, the Importance term defines whether a field is displayed with priority Low,Medium, or High.

For the definition of a UI area, such as a facet:<Annotation Term="‘Vocabulary Alias’.Facet">Defines a segmentation of content for the object. Facets can reference existing terms, such as identification, or line item. TheGeneral facet cannot be changed.

For the definition of single fields with their properties:<Record Type="‘Vocabulary Alias’.DataField">Defines a label-value pair that refers a property of the OData service used.<Record Type="‘Vocabulary Alias’.DataFieldWithNavigation">Defines a label-value pair that refers a property of the OData service used. The definition consists a link to navigate to a new target,based on a navigation property provided by the OData service, or defined in the annotation file.<Record Type="‘Vocabulary Alias’.DataFieldWithURL">Defines a label–value pair that refers a property of the OData service used. The definition consists a URL to navigate to a newtarget, that is a URL.<PropertyValue Property="Label" String="‘xxx’"/>Defines that the label of a record is displayed as a string on the UI.<PropertyValue Property="Value" Path="‘xxx’"/>Defines that the value is retrieved from a property of the OData service used.

More InformationAdding Key Figures to a Fact SheetAnnotation File

1.2.5.5.1.3.1.1 Adding a New Field to a Fact Sheet To use a new field in your fact sheet, you can change the corresponding annotation file by copying the suitable lines and replace theproperties of the relevant annotation with new properties provided by the OData service.

Example

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 42 of 78

The following example describes how an additional data field of the OData service can be added to the LineItem annotation:

01. <Annotation Term="UI.LineItem"> <Collection> <Record Type="UI.DataField"> <PropertyValue Property="Importance" EnumMember="UI.Priority.Low"/> <PropertyValue Property="Value" Path="CompanyCode"/> </Record> <Record Type="UI.DataField"> <PropertyValue Property="Importance" EnumMember="UI.Priority.Low"/> <PropertyValue Property="Value" Path="Currency"/> </Record> <Record Type="UI.DataField"> <PropertyValue Property="Importance" EnumMember="UI.Priority.Low"/> <PropertyValue Property="Value" Path="TaxCode"/> </Record>

<Record Type="UI.DataField"> <PropertyValue Property="Importance" EnumMember="UI.Priority.High"/> <PropertyValue Property="Value" Path="ZSalesUnit"/> </Record>

<Record Type="UI.DataField"> <PropertyValue Property="Importance" EnumMember="UI.Priority.Low"/> <PropertyValue Property="Value" Path="IsReconciliationAccount"/> </Record>

<Record Type="UI.DataField"> <PropertyValue Property="Importance" EnumMember="UI.Priority.High"/> <PropertyValue Property="Value"> <Apply Function="odata.concat"> <Path>ChartOfAccounts</Path> <String>&#160;</String> <Path>ChartOfAccountsName</Path> </Apply> </PropertyValue> </Record>

<Record Type="UI.DataField"> <PropertyValue Property="Importance" EnumMember="UI.Priority.Low"/> <PropertyValue Property="Value" Path="IsOpenItemManaged"/> </Record> </Collection> </Annotation>

As a prerequisite, the corresponding OData service contains the fields ZSalesUnit, ChartOfAccounts, andChartOfAccountsName.On the fact sheet, the system provides these additional fields defined by <PropertyValue Property="Value"Path="ZSalesUnit"/>, <Path>ChartOfAccounts</Path>, and <Path>ChartOfAccountsName</Path> in the line itemview, which is determined by the first row <Annotation Term="UI.LineItem">.

PrerequisitesYou have extended the search model with the required field.The field to extend the fact sheet is provided by an OData service.You have found the appropriate BSP application in your system, in transaction SE80.

ActivitiesTo adapt your fact sheet according to your needs, you change the annotation file as follows:1. Copy the complete annotation file into any editor.

Check the OData service for the required new fields for your fact sheet in the SAP NetWeaver Gateway, in parallel.For more information, see Checking the Properties of an OData Service.

2. In the copied annotation file, search for the appropriate area to extend it with a new field.For example, you can search for the entity type found in the OData service.

3. Duplicate the lines of the annotation file, which you want to adapt, tat is the lines defining the Record of the search model field.4. Replace the Path, or several paths in case you want to concatenate fields, of the copy according to your requirements.

For example, copy one <Record Type=”UI.DataField”>.....</Record> area and change the Path toPath="ZSalesUnit" to display the additional field ZSalesUnit on the fact sheet.

5. Save the annotation file.

ResultThe new annotation file is ready to be attached to your own BSP application.

Syntax

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 43 of 78

More InformationUsing Annotation TagsFact Sheet ExtensibilityExtending a Search ModelChecking the Properties of an OData Service

1.2.5.5.1.3.1.2 Adding Key Figures to a Fact Sheet In a fact sheet, three key figures can be displayed. You can add the following types of key figures:

Internal key figures that are derived from the corresponding OData serviceExternal key figures that are derived from other OData services, from an OData service provider for external key figures, such asSAP HANA Live

A key figure is represented as DataPoint annotation term in the annotation file. To add an additional key figure, or replace an existingone, you adapt the annotation file.

PrerequisitesFor internal key figures:

The key figures are provided by the search model to the SAP NetWeaver Gateway, and are delivered to the UI by the relatedOData service.

For external key figures:The key figures are provided by the search model to the SAP NetWeaver Gateway, and are delivered to the UI by an ODataservice for external key figures.The key figures are defined in the system of an external key figure data provider

More InformationExtending a Search ModelAdding Internal Key Figures to a Fact SheetAdding External Key Figures to a Fact Sheet

1.2.5.5.1.3.1.2.1 Adding Internal Key Figures to a Fact Sheet

ActivitiesTo integrate an internal key figure, you change the annotation file as follows:1. In the annotation file, search for the term DataPoint, or add a new DataPoint term as described in the following example.2. Copy the complete annotation that contains the DataPoint description.3. Change the necessary properties.4. Save your changes.

ExampleYou add a second key figure to your fact sheet. For the latest version of the annotation file, see:

01. </Annotation>02. <Annotation Term="UI.DataPoint" Qualifier="01">03. <Record>04. <PropertyValue Property="Title" String="<%= otr(/SAPSRM/CH_WD_UI_BO/TARGET_VALUE)%>"/>05. <PropertyValue Property="Value" Path="TOTAL_VALUE"/>06. <PropertyValue Property="NumberFormat07. <Record>08. <PropertyValue Property="NumberOfFractionalDigits" Int="1" />09. </Record>10. </PropertyValue>11. </Record>12. </Annotation>

The DataPoint term defines a key figure as follows:With a label that is described by an OTR alias (/SAPSRM/CH_WD_UI_BO/TARGET_VALUE) coming from the back-end system.The value of the key figure is derived from the field TOTAL_VALUE of the corresponding OData service.

Syntax

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 44 of 78

The value is displayed as a number (Number Format), with one digit (NumberOfFractionalDigits" Int="1").You adapt the annotation file by changing the following properties:

Replace the qualifier with <Annotation Term="UI.DataPoint" Qualifier="nnn">, for the second key figure. nnn represents any name.Change the OTR alias to replace the label of the key figure.The value of the key figure can be derived from a different field of the OData service, such as NET_VALUE.Change the number of digits to 2 by NumberOfFractionalDigits" Int="2".

More InformationExtending a Search ModelAdding Key Figures to a Fact Sheet

1.2.5.5.1.3.1.2.2 Adding External Key Figures to a Fact Sheet To integrate an external key figure to your fact sheet, you pass the key figure from an OData service provider for external key figures tothe DataPoint term in your annotation file by changing the relevant property value.

ActivitiesTo integrate an external calculated key figure, you change the annotation file as follows:1. Add an edmx reference to the external data provider system. Enter the URL to the OData service that retrieves the metadata to the

OData service providing the key figure. Additionally, a namespace and an alias must be assigned, for example:

1. </edmx:Reference>2. <edmx:Reference Uri="'any server'/HANA/ODATA/IWFND/RMTSAMPLEFLIGHT/$metadata">3. <edmx:Include Namespace="RMTSAMPLEFLIGHT" Alias="FLIGHT"/>4. </edmx:Reference>

2. Declare a term name.The term name must be added within the schema section. The term name must point to the relevant result type of the OData service,such as a Entity, Entity Set, or Property.

<Term Name="FlightCosts" Type="FLIGHT.Flight" />In this example, the term name FlightCosts points to the Entity Set FLIGHT.Flight of the corresponding OData service.

3. Define an annotation referring to the OData service that provides the key figure, such as an SAP HANA Live OData service.The annotation consists of the annotation file’s alias and the newly defined term. The URL to the external data provider query mustbe embedded with the tag <UrlRef> and entered as <String>.

4. Optionally, you can retrieve values from the fact sheet OData service to restrict the OData service provider query for external keyfigures.Use the function odata.fillUriTemplate.Values that are referenced from a labeled element of the annotation file must be marked with braces, that is:<Queryparameter>= {LabeledElement}.

1. <Annotation Term="CB_SALES_ORDER_SRVAnnotation.FlightCosts">2. <UrlRef>3. <Apply Function="odata.fillUriTemplate">4. <String>/HANA/ODATA/IWFND/RMTSAMPLEFLIGHT/FlightCostsQuery( P_ExchangeRateType='M',P_TargetCurrency='{Cur

rency}')/Results?%24select%3DCriticalAmountInDisplayCrcy</String>5. <LabeledElement Name="Currency">6. <Apply Function="odata.UriEncode">7. <Path>Currency</Path>8. </Apply>9. </LabeledElement>

10. </Apply>11. </UrlRef>12. </Annotation>

5. In the annotation file, search for the term <Alias>.DataPoint, or add a new DataPoint term as described in the following example.6. Copy the complete annotation section that contains the <Alias>.DataPoint description.7. Change the necessary properties.

The key figure from an external data provider can be addressed with @+ ‘<annotation> ’ + ‘/’+ <Key Figure>

Syntax

Example

Syntax

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 45 of 78

<PropertyValue Property="Value"Path="@CB_SALES_ORDER_SRVAnnotation.FlightCosts/CriticalAmountInDisplayCrcy">.In this example, the key figure CriticalAmountInDisplayCrcy is addressed with@CB_SALES_ORDER_SRVAnnotation.FlightCosts/CriticalAmountInDisplayCrcy">.

8. Save your changes.

ExampleYou add an external key figure to the annotation file. The key figure is passed to the DataPoint term as follows:

With a title that is as an OTR text /SAPSRM/CH_WD_UI_BO/COST_OF_FLIGHT.With a description that is structured as follows:

A label coming from an OTR text /SAPSRM/CH_WD_UI_BO/FLIGHT_DESCRIPTION.A value that is concatenated from the fields CARRID for the airline, and CONNID for the flight number.

With the key figure CriticalAmountInDisplayCrcy that is addressed with@CB_SALES_ORDER_SRVAnnotation.FlightCosts/CriticalAmountInDisplayCrcy">.

01. <Annotation Term="UI.DataPoint" Qualifier="FlightCosts">02. <Record>03. <PropertyValue Property="Title" String="<%= otr(/SAPSRM/CH_WD_UI_BO/COST_OF_FLIGHT)%>"/>04. <PropertyValue Property="Description">05. <Record>06. <PropertyValue Property="Label" String="<%= otr(/SAPSRM/CH_WD_UI_BO/FLIGHT_DESCRIPTION)%>"/> 07. <PropertyValue Property="Value">08. <Apply Function="odata.concat">09. <String>Flight</String>10. <Path>CARRID</Path>11. <String>Number</String>12. <Path>CONNID</Path>13. </Apply>14. </PropertyValue>15. </Record>16. </PropertyValue>17. <PropertyValue Property="Value" Path="@CB_SALES_ORDER_SRVAnnotation.FlightCosts/CriticalAmountInDisplayCr

cy">18. <Annotation Term="CQP.ISOCurrency" String="USD" />19. </PropertyValue>20. <PropertyValue Property="ValueFormat">21. <Record Type="UI.NumberFormat">22. <PropertyValue Property="ScaleFactor" Decimal="1"/>23. <PropertyValue Property="NumberOfFractionalDigits" Int="2" />24. </Record>25. </PropertyValue>26. </Record>27. </Annotation>

More InformationAdding Key Figures to a Fact SheetExtending a Search Model

1.2.5.5.1.4 Register a BSP Application in LaunchpadCustomizing You have enhanced your fact sheet and created a new BSP application with a modified annotation file. To make the fact sheet availablein the Fiori Launchpad, you register the BSP application in transaction LPD_CUST.

More InformationFor more information about Launchpad Customizing, see SAP Help Portal at http://help.sap.com/nw-uiaddon Application Help Administration Guide Content Administration Fiori Launchpad .

Example

Syntax

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 46 of 78

1.2.5.6 Additional References The below table contains useful links to other documentsTopic LinkSAP Theme Designer http://help.sap.com/nw-uiaddon Application Help

UI Theme Designer SAP Netweaver UI Addon http://help.sap.com/nw-uiaddonSAP Netweaver UI Addon Developer API Reference https://sapui5.netweaver.ondemand.com/sdk/#d

ocs/api/symbols/sap.ui.htmlSAP UI Development Toolkit for HTML5 (SAPUI5) https://tools.hana.ondemand.com/#sapui5SAP UI5 Wiki https://sapui5.hana.ondemand.com/sdk/SAP UI5 Community http://scn.sap.com/community/developer-

center/front-end

1.3 SAP Fiori Apps for SAP ERP

1.3.1 Apps for Accounting

1.3.1.1 Financials (FIN)

1.3.1.1.1 Implementing Apps in Financials (FIN) This information relates to Transactional Apps and Fact Sheets.

Technical DataThe following tables list the technical objects specific for Financials.

Front-End Authorization Role for Fact SheetsYou must assign the following role to your users to enable them to use the fact sheets for Financials. This authorization role grantsauthorizations for the ICF services and business server pages (BSP) for the fact sheets.In addition, you must also assign an authorization role to your users that grants permission to use the OData service and the searchmodels, and to display the business data from the back end. This authorization role is delivered per fact sheet. You can find theinformation about the delivered authorization roles for the OData services in the documentation for the respective fact sheet.Component Technical NameAuthorization Role (PFCG Role) SAP_FIN_TCR_FSA

For more information about how to implement these technical objects, see Central Implementation Information.

1.3.1.1.2 My Spend Type: Transactional app

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 47 of 78

DescriptionWith My Spend, you can track the budget and spending status of your departments and projects, anywhere and anytime. This appconsolidates budget and spending information and visualizes it in an easy-to-consume way.

Key FeaturesView budget and actual spending data of your departments and projectsDisplay the overview of a specific area, including the budgeted and actual spendingDrill down by various dimensions and to the corresponding accounts

Technical RequirementsSAP ERP:

SAP ERP 6.0 SP15 or higherSAP enhancement package 2 of SAP ERP 6.0 SP06 or higherSAP enhancement package 3 of SAP ERP 6.0 SP05 or higherSAP enhancement package 4 of SAP ERP 6.0 SP05 or higherSAP enhancement package 5 of SAP ERP 6.0 SP03 or higherSAP enhancement package 6 of SAP ERP 6.0 SP01 or higherSAP enhancement package 7 of SAP ERP 6.0 SP01 or higher

FIORI ERP APPLICATIONS X1 1.0For more information, see App Implementation: My Spend.

Component for customer messagesMOB-UIA-FI-MS

1.3.1.1.2.1 App Implementation: My Spend

Technical DataThe following tables list technical objects specific for My Spend:

Back-End ComponentsOData Service (Version Number) Authorization Role (PFCG Role)SRA012_SPEND_SRV (1) SAP_FIN_SPE_MON_APP

Front-End ComponentsComponent Technical NameUI5 Application FIN_SPE_MONBusiness Role SAP_FIN_BCR_CostManager_X1Business Catalog SAP_FIN_BC_CostManager_X1Business Catalog Group SAP_FIN_BCG_CostManager_X1

For more information about how to implement these technical objects, see Central Implementation Information.

ConfigurationTo enable My Spend, you must perform the following configuration tasks:

Assigning PFCG role to user:Authorization must be explicitly given to a user to run a certain Fiori application.Configuration of personalization data:Personalization for the user must be completed using transaction FPB_MAINTAIN_PERS_S. Personalization dialogsDIA_CCMONITOR and DIA_IOMONITOR must be processed for the user. For DIA_CCMONITOR, Controlling Area, Cost CenterGroup, and Cost Element Group must be maintained. For DIA_IOMONITOR, Controlling Area, Order Group, and CostElement Group must be maintained.

Extensibility

Extension PointsTo extend the app, you can also use the following extension points:extColumnHeaders in ListTreeTable.view.xmlextColumnValues in ListTreeTable.view.xml

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 48 of 78

1.3.1.1.3 Accounting Document Type: Fact sheet

DescriptionThe fact sheet Accounting Document displays contextual information about the Accounting Document. You can navigate to its relatedentities and you can access related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

Purchase Order;Incoming Invoice;Sales Order;Billing Document;Controlling Document;Cost Center;Profit Center;Internal Order;Fixed Asset;Vendor;Customer

TransactionsYou can access the following transactions, for example:

FB03 – Display Accounting Document

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Accounting Document:Backend Components Technical NameOData service CB_ACCOUNTING_DOCUMENT_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_ACCOUNTINGDOCUMENT_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesFI_GL

1.3.1.1.4 Activity Type Type: Fact sheet

DescriptionThe fact sheet Activity Type displays contextual information about the Activity Type. You can navigate to its related entities and you canaccess related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

Cost ElementCost CenterControlling Document

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 49 of 78

Internal OrderWBS Element

TransactionsYou can access the following transactions:KL03 – Display Activity Type

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Activity Type:Backend Components Technical NameOData service CB_ACTIVITY_TYPE_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_ACTIVITY_TYPE_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Extensibility (optional)Class: CL_ACTIVITY_TYPE_DPMethod: /IWBEP/IF_MGW_APPL_SRV_RUNTIME~GET_ENTITYMethod: /IWBEP/IF_MGW_APPL_SRV_RUNTIME~GET_ENTITYSETClass: CL_ACTIVITY_TYPE_MPMethod: DEFINEMethod: IF_CBN_ESH_GW_MED_LOAD~GET_ES_TEMPLATE_ID

Component for Customer MessagesCO-OM

1.3.1.1.5 Bank Type: Fact sheet

DescriptionThe fact sheet Bank displays contextual information about the Bank. You can navigate to its related entities and you can access relatedtransactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

HouseBank

TransactionsYou can access the following transactions, for example:

FI03 – Display Bank

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Bank:Backend Components Technical NameOData service CB_BANK_SRV

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 50 of 78

Roles Technical NamePFCG role in back-end system SAP_FIN_BANK_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesFIN-FSCM-CLM

1.3.1.1.6 Controlling Document Type: Fact sheet

DescriptionThe fact sheet Controlling Document displays contextual information about the Controlling Document. You can navigate to its relatedentities and you can access related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

Cost ElementCost CenterAccounting Document

TransactionsYou can access the following transactions:KSB5 – Display Actual Cost Document

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Controlling Document:Backend Components Technical NameOData service CB_CONTROLLINGDOCUMENT_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_CONTROLLING_DOC_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Extensibility (optional)Class: CL_CONTROLLINGDOCUMENT_DPMethod: /IWBEP/IF_MGW_APPL_SRV_RUNTIME~GET_ENTITY

Component for Customer MessagesCO-OM

1.3.1.1.7 Cost Center Type: Fact sheet

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 51 of 78

DescriptionThe fact sheet Cost Center displays contextual information about the Cost Center. You can navigate to its related entities and you canaccess related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsTest Link:https://dewdfgwd01082.wdf.sap.corp:4080/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=001=EN#CostCenter-displayFactSheet?CostCenter=0000047111=0001You can navigate to the following apps, for example:

Internal OrderControlling DocumentInvoiceActivity TypeCost Center GroupPurchase OrderFixed AssetStatistical Key Figure

TransactionsYou can access the following transactions, for example:

KS03– Display Cost Center

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Cost Center:Backend Components Technical NameOData service CB_COST_CENTER_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_COSTCENTER_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesCO-OM

1.3.1.1.8 Cost Center Group Type: Fact sheet

DescriptionThe fact sheet Cost Center Group displays contextual information about the Cost Center Group. You can navigate to its related entitiesand you can access related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

Cost Center GroupCost Center

TransactionsYou can access the following transactions, for example:

KSH3 – Display Order

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 52 of 78

UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Cost Center Group:Backend Components Technical NameOData service CB_COST_CENTER_GRP_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_COSTCENTERGROUP_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesCO-OM

1.3.1.1.9 Cost Element Type: Fact sheet

DescriptionThe fact sheet Cost Element displays contextual information about the cost element. You can navigate to its related entities and you canaccess related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

Controlling DocumentCost Element Group

TransactionsYou can access the following transactions:KA01 – Create Primary Cost ElementKA02 – Change Cost ElementKA03 – Display Cost Element

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Cost Element:Backend Components Technical NameOData service CB_COST_ELEMENT_SRV

Roles Technical NamePFCG role in back-end system SAP_COST_ELEMENT_HBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesCO-OM

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 53 of 78

1.3.1.1.10 Customer Accounting Document Type: Fact sheet

DescriptionThe fact sheet Customer Accounting Document displays contextual information about the Customer Accounting Document. You cannavigate to its related entities and you can access related transactions in operational systems, or you can navigate to relatedtransactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

Customer Accounting Document - Related Document:CustomerGL AccountsSales Order

TransactionsYou can access the following transactions:FB03 – Display Document: initial screen

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Customer Accounting Document:Backend Components Technical NameOData service CB_CUSTOMER_ACC_DOC_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_CUSTOMER_ACC_DOC_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesFI-AR

1.3.1.1.11 Fixed Asset Type: Fact sheet

DescriptionThe fact sheet Fixed Asset displays contextual information about the Fixed Asset. You can navigate to its related entities and you canaccess related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps:

Accounting DocumentCost Center

TransactionsYou can access the following transactions:

AS03 – display asset: initial screen

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 54 of 78

Technical DataThe following table lists technical objects specific for Fixed Asset:Backend Components Technical NameOData service CB_FIXED_ASSET_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_FIXED_ASSET_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesFI-AA

1.3.1.1.12 GL Account Type: Fact sheet

DescriptionThe fact sheet GL Account displays contextual information about the G/L Account. You can navigate to its related entities and you canaccess related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

Accounting Document

TransactionsYou can access the following transactions, for example:

FSP0 – Edit G/L Account Chart of accts data

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for GL Account:Backend Components Technical NameOData service CB_GL_ACCOUNT_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_GLACCOUNT_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesFI-GL

1.3.1.1.13 HouseBank Type: Fact sheet

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 55 of 78

DescriptionThe fact sheet House Bank displays contextual information about the House Bank. You can navigate to its related entities and you canaccess related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

HouseBankAccount

TransactionsYou can access the following transactions, for example:

FIBHS – Display House Bank

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for House Bank:Backend Components Technical NameOData service CB_HOUSE_BANK_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_HOUSEBANK_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesFIN-FSCM-CLM

1.3.1.1.14 House Bank Account Type: Fact sheet

DescriptionThe fact sheet House Bank Account displays contextual information about the House Bank Account. You can navigate to its relatedentities and you can access related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

House BankBankGL Account

TransactionsN/A

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for House Bank Account:Backend Components Technical NameOData service CB_HOUSE_BANK_ACCOUNT_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_HOUSEBANKACCOUNT_APPBusiness role (PFCG) on front-end server N/A

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 56 of 78

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesFIN-FSCM-CLM

1.3.1.1.15 Internal Order Type: Fact sheet

DescriptionThe fact sheet Internal Order displays contextual information about the Internal Order. You can navigate to its related entities and youcan access related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

Controlling DocumentFixed AssetCost CenterSales OrderCustomerWBS ElementProfit CenterCost ElementGL Account

TransactionsYou can access the following transactions:KO03 – Display Order

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Internal Order:Backend Components Technical NameOData service CB_INTERNAL_ORDER_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_INTERNALORDER_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesCO-OM

1.3.1.1.16 Profit Center Type: Fact sheet

Description

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 57 of 78

The fact sheet profit center displays the detail information of profit center and some related business objects. You can navigate torelated BO and you can find their general information in factsheet of profit center. Also you can navigate to the related t-code in SAPGUI.

Navigational TransactionsYou can navigate to the following apps, for example:

Cost Centers;Internal Orders;Sales Orders;WBS Elements;Accounting documents

TransactionsYou can access the following transactions:KXX3 – Display Profit Center

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Profit Center:Backend Components Technical NameOData service CB_PROFIT_CENTER_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_PROFIT_CENTER_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Extensibility (optional)Class: CL_PROFIT_CENTER_DPMethod: /IWBEP/IF_MGW_APPL_SRV_RUNTIME~GET_ENTITYSETClass: CL_PROFIT_CENTER_MPMethod: IF_CBN_ESH_GW_MED_LOAD~GET_ES_TEMPLATE_IDDEFINE

Component for Customer MessagesFI-GL

1.3.1.1.17 Vendor Accounting Document Type: Fact sheet

DescriptionThe fact sheet Vendor Accounting Document displays contextual information about the Vendor Accounting Document. You can navigateto its related entities and you can access related transactions in operational systems, or you can navigate to related transactional apps.

Navigational TransactionsYou can navigate to the following apps, for example:

Vendor;Purchase Order;Payment/Credit Memo;

TransactionsN/A

Technical RequirementsBack-end System: EHP7 for SAP ERP 6.0 SP02

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 58 of 78

UI Add-on: UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Vendor Accounting Document:Backend Components Technical NameOData service CB_VENDOR_ACC_DOC_SRV

Roles Technical NamePFCG role in back-end system SAP_FIN_VENDOR_ACC_DOC_APPBusiness role (PFCG) on front-end server N/A

Launchpad Components Technical NameBusiness catalog (Fiori Launchpad) N/A

For more information on how to implement these technical objects, refer to the Central Implementation Information.

Component for Customer MessagesFI-AP

1.3.1.2 Travel Management

1.3.1.2.1 Approve Travel Expenses Type: Transactional app

DescriptionWith Approve Travel Expenses, you can review and approve employees' travel expenses on the go or in the office. The app providesdetails on each receipt, and alerts you if expenses exceed the budget limits defined in your company's travel policy. You can alsoforward requests to another employee for approval.

Key FeaturesBrowse all approval requests in a personalized worklistDisplay details for a trip (cost assignment, settlement summary, individual receipts per trip)Display details for individual receipts (payment details, notes from requester)Identify travel policy violations – automatic alerts appear when expenses exceed set budget limitsApprove travel expensesReject travel expenses (with note to requester)Forward the approval request to another employee

Technical RequirementsSAP ERP

SAP ERP 6.0 SP15 or higherSAP enhancement package 2 of SAP ERP 6.0 SP06 or higherSAP enhancement package 3 of SAP ERP 6.0 SP05 or higherSAP enhancement package 4 of SAP ERP 6.0 SP05 or higherSAP enhancement package 5 of SAP ERP 6.0 SP03 or higherSAP enhancement package 6 of SAP ERP 6.0 SP01 or higherSAP enhancement package 7 of SAP ERP 6.0 SP01 or higher

FIORI ERP APPLICATIONS X1 1.0User Interface Add-On 1.0 for SAP NetWeaver, SPS 06

For more information, see App Implementation: Approve Travel Expenses.

Related AppsApprove Travel RequestsMy Travel Requests

Component for Customer Messages

MOB-UIA-FI-ATE Approve Travel Expenses

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 59 of 78

1.3.1.2.1.1 App Implementation: Approve Travel Expenses

Required SAP NotesFor Approve Travel Expenses, the following SAP Notes must be available on the back-end or front-end server:Back-End/Front-End Server SAP Note Number DescriptionFor more information, see the collectiveSAP Note.

1931024 Collective SAP Note listing all relevant SAPNotes for this app.

Technical DataThe following table lists technical objects specific for Approve Travel Expenses:

Back-End Components

OData Service (Version Number) Authorization Role (PFCG Role)SRA008_SRV (1) SAP_FIN_TE_APV_APP

Front-End Components

Component Technical NameUI5 Application FIN_TE_APVBusiness Role SAP_TRAVEL_BCR_MANAGER_X1Business Catalog SAP_TRAVEL_BC_MANAGER_X1Business Catalog Group SAP_TRAVEL_BCG_MANAGER_X1

For more information on how to implement these technical objects, refer to Central Implementation Information.

Prerequisites for ConfigurationThere are no app-specific prerequisites.

ConfigurationTo enable Approve Travel Expenses, you must perform the following configuration tasks:

Ensure that the SRA008_T_CONFIG configuration table is maintained:The table must be maintained for a workflow decision key in case of a custom workflow for travel expense approval. A node for thistask is provided in Customizing.Ensure that the SRA008_T_TASKTYP configuration table is maintained:The table must be maintained for the task type used for approving the travel expense. A node for this task is provided in Customizing.Ensure that the Travel Management module is installed and configured:As the app relies on configuration data available for the Travel Management module, the module must be installed and configured.In the standard workflow (Approve Trip), there is a two-step approval process for travel expenses. The Approve Travel Expensesapp is used to perform only one approval process.You can enable one of three workflow tasks in this app:

Check Trip FactsApprove Trip Facts (by default, this is used to approve travel expenses)Custom workflow

Extensibility (Optional)

Extension Points

To extend Approve Travel Expenses, you can use the following extension points:Name: extTabAttachmentsLocation: S3.view.app.xmlPurpose: Add a new tab to the tab containerName: AdditionalbuttonsLocation: S3.controller.jsPurpose: Add buttons to the footer toolbarName: CustomerExtensionForReceiptDetailsLocation: S4.view.app.xmlPurpose: Customize the Receipt Details area

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 60 of 78

1.3.1.2.2 Approve Travel Requests Type: Transactional app

DescriptionWith Approve Travel Requests, you can approve or reject travel requests in real time using your desktop or mobile device. The appprovides details on each request and also allows you to view all of an employee’s past requests.

Key FeaturesBrowse all pending travel requests from your employeesView details of a travel requestApprove travel requestsReject travel requestsView the history (approved and rejected) of an employee's travel requests

Technical RequirementsSAP ERP

SAP ERP 6.0 SP15 or higherSAP enhancement package 2 of SAP ERP 6.0 SP06 or higherSAP enhancement package 3 of SAP ERP 6.0 SP05 or higherSAP enhancement package 4 of SAP ERP 6.0 SP05 or higherSAP enhancement package 5 of SAP ERP 6.0 SP03 or higherSAP enhancement package 6 of SAP ERP 6.0 SP01 or higherSAP enhancement package 7 of SAP ERP 6.0 SP01 or higher

FIORI ERP APPLICATIONS X1 1.0User Interface Add-On 1.0 for SAP NetWeaver, SPS 06

For more information, see App Implementation: Approve Travel Requests.

Related AppsApprove Travel ExpensesMy Travel Requests

Component for Customer Messages

MOB-UIA-FI-ATR Approve Travel Requests

1.3.1.2.2.1 App Implementation: Approve Travel Requests

Required SAP NotesFor Approve Travel Requests, the following SAP Notes must be available on the back-end or front-end server:Back-End/Front-End Server SAP Note Number DescriptionFor more information, see the collectiveSAP Note.

1931025 Collective SAP Note listing all relevant SAPNotes for this app.

Technical DataThe following table lists technical objects specific for Approve Travel Requests:

Back-End Components

OData Service (Version Number) Authorization Role (PFCG Role)SRA009_SRV (1) SAP_FIN_TR_APV_APP

Front-End Components

Component Technical NameUI5 Application FIN_TR_APVBusiness Role SAP_TRAVEL_BCR_MANAGER_X1Business Catalog SAP_TRAVEL_BC_MANAGER_X1Business Catalog Group SAP_TRAVEL_BCG_MANAGER_X1

For more information on how to implement these technical objects, refer to Central Implementation Information.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 61 of 78

Prerequisites for ConfigurationThere are no app-specific prerequisites.

ConfigurationTo enable Approve Travel Requests, you must perform the following configuration tasks:

Ensure that the SRA009_T_CONFIG configuration table is maintained.The table must be maintained for a workflow decision key in case of a custom workflow for travel request approval. A node for thistask is provided in Customizing.Ensure that the SRA009_T_TASKTYP configuration table is maintained.The table must be maintained for the task type used for approving the travel request. A node for this task is provided in Customizing.

Extensibility (Optional)

Extension Points

To extend Approve Travel Requests, you can use the following extension points:Name: extInfoAdditionalDataLocation: details.view.app.xmlPurpose: Add data to the information tabName: extTabsLocation: details.view.app.xmlPurpose: Add a new tab to the tab containerName: AdditionalbuttonsLocation: details.controller.jsPurpose: Add buttons to the footer toolbar

1.3.1.2.3 My Travel Requests Type: Transactional app

DescriptionWith My Travel Requests, you can manage your own travel requests in real time using your desktop or mobile device. The app allowsyou to create, edit, submit, and delete requests. You can also check the status of a particular request at any time.

Key FeaturesCreate a new travel requestSubmit travel requests to your organizational managerBrowse existing travel requests in detailEdit existing travel requests and resubmitDelete existing travel requests

Technical RequirementsSAP ERP

SAP ERP 6.0 SP15 or higherSAP enhancement package 2 of SAP ERP 6.0 SP06 or higherSAP enhancement package 3 of SAP ERP 6.0 SP05 or higherSAP enhancement package 4 of SAP ERP 6.0 SP05 or higherSAP enhancement package 5 of SAP ERP 6.0 SP03 or higherSAP enhancement package 6 of SAP ERP 6.0 SP01 or higherSAP enhancement package 7 of SAP ERP 6.0 SP01 or higher

FIORI ERP APPLICATIONS X1 1.0User Interface Add-On 1.0 for SAP NetWeaver, SPS 06

For more information, see App Implementation: My Travel Requests.

Related AppsApprove Travel ExpensesApprove Travel Requests

Component for Customer Messages

MOB-UIA-FI-MTR My Travel Requests

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 62 of 78

1.3.1.2.3.1 App Implementation: My Travel Requests

Required SAP NotesFor My Travel Requests, the following SAP Notes must be available on the back-end or front-end server:Back-End/Front-End Server SAP Note Number DescriptionFor more information, see the collectiveSAP Note.

1931027 Collective SAP Note listing all relevant SAPNotes for this app.

Technical DataThe following table lists technical objects specific for My Travel Requests:

Back-End Components

OData Service (Version Number) Authorization Role (PFCG Role)SRA004_SRV (1) SAP_FIN_TR_CRE_APP

Front-End Components

Component Technical NameUI5 Application FIN_TR_CREBusiness Role SAP_TRAVEL_BCR_EMPLOYEE_X1Business Catalog SAP_TRAVEL_BC_EMPLOYEE_X1Business Catalog Group SAP_TRAVEL_BCG_EMPLOYEE_X1

For more information on how to implement these technical objects, refer to Central Implementation Information.

Prerequisites for ConfigurationThere are no app-specific prerequisites.

ConfigurationThere are no app-specific configuration tasks.

Extensibility (Optional)

Extension Points

To extend My Travel Requests, you can use the following extension points:Name: extInfoAdditionalDataLocation: detail.view.app.xmlPurpose: Add data to the information tabName: extTabsLocation: detail.view.app.xmlPurpose: Add a new tab to the tab containerName: AdditionalbuttonsLocation: detail.controller.jsPurpose: Add buttons to the footer toolbar

1.3.2 Apps for Logistics

1.3.2.1 Implementing Apps in Logistics (LO) This information relates to Transactional Apps and Fact Sheets.

Technical DataThe following tables list the technical objects specific for Logistics.

Front-End Authorization Role for Fact Sheets

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 63 of 78

You must assign the following role to your users to enable them to use the fact sheets for Logistics. This authorization role grantsauthorizations for the ICF services and business server pages (BSP) for the fact sheets.In addition, you must also assign an authorization role to your users that grants permission to use the OData service and the searchmodels, and to display the business data from the back end. This authorization role is delivered per fact sheet. You can find theinformation about the delivered authorization roles for the OData services in the documentation for the respective fact sheet.Component Technical NameAuthorization Role (PFCG Role) SAP_LO_TCR_FSA

Front-End Menu RolesComponent Technical NameLPD_CUST UIEAAP01Technical Roles SAP_ISR_LO_TCR_TTechnical Catalogs SAP_ISR_LO_TC_F

For more information about how to implement these technical objects, see Central Implementation Information.

1.3.2.2 Production Planning and Control (PP)

1.3.2.2.1 Implementing Apps in Production Planning andControl (PP) This information relates to Transactional Apps and Fact Sheets.

Technical DataThe following tables list the technical objects specific for Product Planning and Control.

Front-End Authorization Role for Fact SheetsYou must assign the following role to your users to enable them to use the fact sheets for Product Planning and Control. Thisauthorization role grants authorizations for the ICF services and business server pages (BSP) for the fact sheets.In addition, you must also assign an authorization role to your users that grants permission to use the OData service and the searchmodels, and to display the business data from the back end. This authorization role is delivered per fact sheet. You can find theinformation about the delivered authorization roles for the OData services in the documentation for the respective fact sheet.Component Technical NameAuthorization Role (PFCG Role) SAP_PP_TCR_FSA

Front-End Menu RolesComponent Technical NameLPD_CUST UIAPPP01Technical Roles SAP_PP_TCR_TTechnical Catalogs SAP_PP_TC_T

For more information about how to implement these technical objects, see Central Implementation Information.

1.3.2.2.2 Confirm Production Orders Type: Transactional app

DescriptionWith Confirm Production Orders you can allocate a production order by entering or scanning its number. This app allows a productionworker to perform partial or final confirmations for production orders through a simplified and intuitive UI. The app allows fast order inputand simplified order confirmation procedures that are available on devices such as desktop, tablet, and mobile.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 64 of 78

Key FeaturesSearch for a production order by its numberPerform partial or final confirmation for an orderGraphical progress bar to view confirmed quantitiesRuns on SAP HANA and also on other databasesWeb-based application that can be easily enhanced using HTML5Direct navigation to Material fact sheetIntuitive and user-friendly navigation

Technical RequirementsBack-end system SAP ERP EHP 7 SP02User Interface Add-On UI for EHP7 for SAP ERP 6.0Supported Browsers: Apple Safari for iOS 6.1.3, Android 4.1.2 and Android Chrome Browser for Android 4.2.2, Microsoft InternetExplorer 9.0 or higher

Related AppsConfirm Production OperationsMaterial Fact Sheet

For more information, see App Implementation: Confirm Production Orders

Component for Customer MessagesPP-SFC

1.3.2.2.2.1 App Implementation: Confirm Production Orders

Required SAP NotesFor Confirm Production Orders, the following SAP notes must be available on the servers:Back-End/Front-End Server SAP Note Number DescriptionBack-End 1893788 Conversions in SAP NetWeaver Gateway

Framework

Ensure that this note is implementedbefore SAP Notes 1916405 and1916406 mentioned below.

Back-End 1916405 Back-End Correction - Fiori app ConfirmProduction Operations

Ensure that this note is implementedbefore SAP Note 1916406 mentionedbelow.

Back-End 1916406 Back-End Correction - Fiori app ConfirmProduction Orders

Technical DataThe following table lists technical objects specific for Confirm Production Orders:

Back-End Components

OData Service (Version Number) Authorization Role (PFCG Role)PP_PRODORD_CONFIRM (1) SAP_PP_PROD_ORD_CONF_APP

Front-End Components

Note

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 65 of 78

Component Technical NameUI5 Application PP_PRODORD_CNFBusiness Role SAP_PP_BCR_WorkerBusiness Catalog SAP_PP_BC_WorkerBusiness Catalog Group SAP_PP_BCG_ Worker

For more information on how to implement these technical objects, refer to Central Implementation Information.

ExtensibilityTo extend Confirm Production Orders, you can use the following extension points:View Name Extension PointS2.view.xml extPtWCObjectListItemNewAttributeS3.view.xml extPtOperationDetailsContentS3.view.xml extPtOperationDetailDatesContentS3.view.xml extPtOperationDetailFooterButtonS4.view.xml extPtConfirmationQuantitiesContentS4.view.xml extPtConfirmationFooterButtonS5.view.xml extPtOrderOperationObjectListItemNewAttributeS5.view.xml extPtOrderOperationFooterButton

1.3.2.2.3 Confirm Production Operations Type: Transactional app

DescriptionWith Confirm Production Operations, production workers can view order-operations released to their work centers. They can search forthe next order-operation to confirm by its number or confirmation number. They can use various sorting and filtering options that enablequick confirmations. They can partially or finally confirm a production order-operation anytime and from any place using various mobiledevices.

Key FeaturesDisplay order-operation based on the user’s work centerSearch for a production order-operation by its number or confirmation numberPerform partial or final confirmation for an order-operationSort and filter by status and datesGraphical progress bar to view confirmed quantitiesRuns on SAP HANA, and also on other databasesWeb-based application that can be easily enhanced using HTML5Direct navigation to Material fact sheetProvides intuitive and user-friendly navigation

Technical RequirementsBack-end system SAP ERP EHP 7 SP02User Interface Add-On UI for EHP7 for SAP ERP 6.0Supported Browsers: Apple Safari for iOS 6.1.3, Android 4.1.2 and Android Chrome Browser for Android 4.2.2, Microsoft InternetExplorer 9.0 or higher

For more information, see App Implementation: Confirm Production Operations

Related AppsConfirm Production OrdersMaterial Fact Sheet

Component for Customer MessagesPP-SFC

1.3.2.2.3.1 App Implementation: Confirm Production

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 66 of 78

1.3.2.2.3.1 App Implementation: Confirm ProductionOperations

Required SAP NotesFor Confirm Production Operations, the following SAP notes must be available on the servers:Back-End/Front-End Server SAP Note Number DescriptionBack-End 1893788 Conversions in SAP NetWeaver Gateway

Framework

Ensure that this note is implementedbefore SAP Note 1916405 mentionedbelow.

Back-End 1916405 Back-End Correction - Fiori app ConfirmProduction Operations

Technical DataThe following table lists technical objects specific for Confirm Production Operations:

Back-End Components

OData Service (Version Number) Authorization Role (PFCG Role)PP_PRODOPS_CONFIRM_SRV (1) SAP_PP_PROD_OPS_CONF_APP

Front-End Components

Component Technical NameUI5 Application PP_PRODOPS_CNFBusiness Role SAP_PP_BCR_WorkerBusiness Catalog SAP_PP_BC_WorkerBusiness Catalog Group SAP_PP_BCG_ Worker

For more information on how to implement these technical objects, refer to Central Implementation Information.

Prerequisites for ConfigurationBefore implementing the app, you must ensure the following:

Personnel number is entered under Human Resources.To do this, from the SAP Easy Access screen, choose Human Resources Personnel Management Administration HR MasterData Personnel Actions . You can also use the transaction code PA40 to create a personnel number.SAP name is assigned to the personnel number.To do this, from the SAP Easy Access screen, choose Human Resources Personnel Management Administration HR MasterData Maintain . In the Direct Selection section, in the Infotype field enter 105 and in the STy field enter 0001 as the subtype.Personnel number is assigned to work center under Logistics.To do this, from the SAP Easy Access screen, choose Logistics Production Master Data Work Centers . You can also use thetransaction code cr01 to create a work center and transaction code cr02 to change a work center.After you create or change a work center, choose Basic Data HRMS to assign the personnel number to the work center.

Extensibility

Extension Points

To extend Confirm Production Operations, you can use the following extension points:View Name Extension PointS2.view.xml extPtOrderDetailDatesContentS2.view.xml extPtOrderDetailFooterButtonS2.view.xml extPtOrderDetailDetailsContentS3.view.xml extPtConfirmationInputContentS3.view.xml extPtConfirmationFooterButton

1.3.2.2.4 Release Production Orders

Note

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 67 of 78

Type: Transactional App

DescriptionWith Release Production Orders, production supervisors can release production orders using a highly intuitive and user-friendlyapplication. The browser based application supports desktop, tablet and mobile devices.

Key FeaturesProvides an overview of production orders to be released based on individual variantsGives end users immediate overview of missing partsDetailed screen that provides end users with decision-critical information (date and time, system and user status, relevant workcenters, missing part information for operations, etc.)Search engine to identify and filter production orders

Technical RequirementsSAP ERP 6.0 SP15 or higherUser Interface Add-On UI for EHP7 for SAP ERP 6.0For more information see:App Implementation: Release Production Orders

Component for customer messagesPP-SFC

1.3.2.2.5 Production Order Type: Fact sheet

DescriptionThis fact sheet displays contextual information about the Production Order. You can navigate to its related entities and you can accessrelated transactions in operational systems.

Navigation TargetsYou can navigate to the following apps, for example:

Release Production OrderConfirm Production OrderSales OrderMaterialCustomerWBS ElementWork Center

TransactionsYou can access the following transactions, for example:

Display Production OrderPegged Requirements Production Order

Technical RequirementsSAP enhancement package 7 for SAP ERP 6.0 SP02UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Production Order:Back-End ComponentsOData Service (Version Number) Authorization Role (PFCG Role)CB_PRODUCTION_ORDER_SRV (1) SAP_PP_TCR_T

Front-End ComponentsComponent Technical NameUI5 Application BCSBN_PRODUCTIONORDER_ANNO.XMLBusiness Role SAP_PP_BCR_PRODSUPERVISORBusiness Catalog SAP_PP_BC_PRODUCTIONSUPERVISORBusiness Catalog Group –

For more information on how to implement these technical objects, refer to Central Implementation Information.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 68 of 78

Component for Customer MessagesIf required, create customer messages on the OSS component PP-SFC.

1.3.2.2.6 Planned Order Type: Fact sheet

DescriptionThis fact sheet displays contextual information about the Planned Order. You can navigate to its related entities and you can accessrelated transactions in operational systems, or you can navigate to related transactional applications.

Navigation TargetsYou can navigate to the following apps, for example:

Sales OrderMaterialCustomerWBS Element

TransactionsYou can access the following transactions, for example:

Convert to Production OrderConvert to Purchase RequisitionConvert to Process OrderDisplay Planned Order

Technical RequirementsSAP enhancement package 7 for SAP ERP 6.0 SP02UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Production Order:Back-End ComponentsOData Service (Version Number) Authorization Role (PFCG Role)CB_PLANNED_ORDER_SRV (1) SAP_PP_TCR_T

Front-End ComponentsComponent Technical NameUI5 Application CB_PLANNED_ORDER_SRV_ANNO.XMLBusiness Role SAP_PP_BCR_PRODSUPERVISORBusiness Catalog SAP_PP_BC_PRODUCTIONSUPERVISORBusiness Catalog Group –

For more information on how to implement these technical objects, refer to Central Implementation Information.

Component for Customer MessagesIf required, create customer messages on the OSS component PP-MRP_BD.

1.3.2.2.7 Process Order Type: Fact sheet

DescriptionThis fact sheet displays contextual information about the Process Order. You can navigate to its related entities and you can accessrelated transactions in operational systems, or you can navigate to related transactional applications.

Navigation TargetsYou can navigate to the following apps, for example:

Sales Order

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 69 of 78

MaterialCustomerWBS ElementResource

TransactionsYou can access the following transactions, for example:

Display Process OrderPegged Requirements Process Order

Technical RequirementsSAP enhancement package 7 for SAP ERP 6.0 SP02UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Production Order:Back-End ComponentsOData Service (Version Number) Authorization Role (PFCG Role)CB_PROCESS_ORDER_SRV (1) SAP_PP_TCR_T

Front-End ComponentsComponent Technical NameUI5 Application CB_PROCESS_ORDER_SRV_ANNO.XMLBusiness Role SAP_PP_BCR_PRODSUPERVISORBusiness Catalog SAP_PP_BC_PRODUCTIONSUPERVISORBusiness Catalog Group –

For more information on how to implement these technical objects, refer to Central Implementation Information.

Component for Customer MessagesIf required, create customer messages on the OSS component PP-PI-POR.

1.3.2.2.8 Resource Type: Fact sheet

DescriptionThis fact sheet displays contextual information about the Resource. You can navigate to its related entities and you can access relatedtransactions in operational systems, or you can navigate to related transactional applications.

TransactionsYou can access the following transactions, for example:

Display Resource

Technical RequirementsSAP enhancement package 7 for SAP ERP 6.0 SP02UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Production Order:Back-End ComponentsOData Service (Version Number) Authorization Role (PFCG Role)CB_RESOURCE_SRV (1) SAP_PP_TCR_T

Front-End ComponentsComponent Technical NameUI5 Application CB_RESOURCE_SRV_ANNO.XMLBusiness Role SAP_PP_BCR_PRODSUPERVISORBusiness Catalog SAP_PP_BC_PRODUCTIONSUPERVISORBusiness Catalog Group –

For more information on how to implement these technical objects, refer to Central Implementation Information.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 70 of 78

Component for Customer MessagesIf required, create customer messages on the OSS component PP-BD-WKC.

1.3.2.2.9 Work Center Type: Fact sheet

DescriptionThis fact sheet displays contextual information about the Work Center. You can navigate to its related entities and you can accessrelated transactions in operational systems, or you can navigate to related transactional applications.

Navigation TargetsYou can navigate to the following apps, for example:

Cost Center

TransactionsYou can access the following transactions, for example:

Display Work Center

Technical RequirementsSAP enhancement package 7 for SAP ERP 6.0 SP02UI for EHP7 for SAP ERP 6.0

Technical DataThe following table lists technical objects specific for Production Order:Back-End ComponentsOData Service (Version Number) Authorization Role (PFCG Role)CB_WORK_CENTER_SRV (1) SAP_PP_TCR_T

Front-End ComponentsComponent Technical NameUI5 Application CB_WORK_CENTER_SRV_ANNO.XMLBusiness Role SAP_PP_BCR_PRODSUPERVISORBusiness Catalog SAP_PP_BC_PRODUCTIONSUPERVISORBusiness Catalog Group –

For more information on how to implement these technical objects, refer to Central Implementation Information.

Component for Customer MessagesIf required, create customer messages on the OSS component PP-BD-WKC.

1.3.2.3 Project System (PS)

1.3.2.3.1 Implementing Apps in Project System (PS) This information relates to Transactional Apps and Fact Sheets.

Technical DataThe following tables list the technical objects specific for Project Systems.

Front-End Authorization Role for Fact SheetsYou must assign the following role to your users to enable them to use the fact sheets for Project Systems. This authorization role grantsauthorizations for the ICF services and business server pages (BSP) for the fact sheets.

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 71 of 78

In addition, you must also assign an authorization role to your users that grants permission to use the OData service and the searchmodels, and to display the business data from the back end. This authorization role is delivered per fact sheet. You can find theinformation about the delivered authorization roles for the OData services in the documentation for the respective fact sheet.Component Technical NameAuthorization Role (PFCG Role) SAP_PS_TCR_FSA

Front-End Menu RolesComponent Technical NameLPD_CUST UIAPPS01Technical Roles SAP_PS_TCR_TTechnical Catalogs SAP_PS_TC_T

SAP_PS_TC_F

For more information about how to implement these technical objects, see Central Implementation Information.

Prerequisites for ConfigurationBefore implementing the fact sheets for Project Systems, you must ensure the following:1. Run the report REPS_PSEXT_ID_CONV.2. Run the report REPS_PSSTXH_KEYS

ConfigurationThe following example implementations are available for the fact sheets of Projects Systems:

Example Implementation CL_EX_PROJECTDEF_UPDATE of BAdI PROJECTDEF_UPDATEExample Implementation CL_EX_WORKBREAKDOWN_UPDATE of BAdI WORKBREAKDOWN_UPDATEExample Implementation CL_EX_WORKORDER_UPDATE of BAdI WORKORDER_UPDATE

1.3.2.3.2 Confirm Network Activity Type: Transactional app

DescriptionWith the Confirm Network Activity app, you can confirm the processing of an activity within a network.

Key FeaturesA network activity confirmation documents the state of processing for activities and activity elements in a network, and can be used toforecast progress in the future.

Technical RequirementsProduct Version: SAP Enhancement Package 7 for SAP ERP 6.0Product Version UI: UI for EHP7 FOR SAP ERP 6.0

For more information, see Implementation Information for Confirm Network Activity

Component for Customer MessagesPS-STPS-ST-OPR

1.3.2.3.2.1 Implementation Information for Confirm NetworkActivity

Required SAP NotesFor Confirm Network Activity, the following SAP note must be available on the back-end server:SAP Note Description1916394 Confirm Network Activity

Technical Data

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 72 of 78

The following table lists technical objects specific for Confirm Network Activity:Back-end ComponentsOData Service (Version Number) Authorization Role (PFCG Role)PS_ACTIVITY_CONFIRM (1) SAP_PS_ACTY_CONF_APP

Front-end ComponentsComponent Technical NameUI5 Application PS_ACTY_CONFBusiness Role SAP_PS_BCR_PROJECTMANAGERBusiness Catalog SAP_PS_BC_ProjectManagerBusiness Catalog Group SAP_PS_BCG_PROJECTMANAGER

For more information on how to implement these technical objects, refer to Central Implementation Information

Extending the AppTo extend Confirm Network Activity, you can use the following Business Add-In:BADI_PS_ODATA_ACTY_CONFIRMYou can use this BAdI to add attributes to the existing application. For more information on this BAdI for OData services, see SAPCustomizing Implementation Guide Project System Structures Operative Structures Business Add-Ins for OData Services BAdI: Activity OData Service

Extension PointsTo extend Confirm Network Activity, you can use the following extension points:View Name Extension PointS3.view.xml extDetailContent

1.3.2.3.3 Confirm Project Milestone Type: Transactional app

DescriptionWith the Confirm Project Milestone app, you can confirm the milestones defined in a project.

Key FeaturesA milestone is used to mark the transition between various phases. If you have completed such milestones in the course of a project,you can confirm them by using this app.

Technical RequirementsProduct Version: SAP Enhancement Package 7 for SAP ERP 6.0Product Version UI: UI for EHP7 FOR SAP ERP 6.0

For more information, see Implementation Information for Confirm Project Milestone

Component for Customer MessagesPS-STPS-ST-OPR

1.3.2.3.3.1 Implementation Information for Confirm ProjectMilestone

Required SAP NotesFor Confirm Project Milestone, the following SAP note must be available on the back-end server:SAP Note Description1916423 Confirm Project Milestone

Technical DataThe following table lists technical objects specific for Confirm Project Milestone:Back-end Components

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 73 of 78

OData Service (Version Number) Authorization Role (PFCG Role)PS_MILESTONE_CONFIRM SAP_PS_MLST_CONF_APP

Front-end ComponentsComponent Technical NameUI5 Application PS_MLST_CONFBusiness Role SAP_PS_BCR_PROJECTMANAGERBusiness Catalog SAP_PS_BC_ProjectManagerBusiness Catalog Group SAP_PS_BCG_PROJECTMANAGER

For more information on how to implement these technical objects, refer to Central Implementation Information

Extending the AppTo extend Confirm Project Milestone, you can use the following Business Add-In:BADI_PS_ODATA_MLST_CONFIRMYou can use this BAdI to add attributes to the existing application. For more information on this BAdI for OData services, see SAPCustomizing Implementation Guide Project System Structures Operative Structures Business Add-Ins for OData Services BAdI: Milestone OData Service

Extension PointsTo extend Confirm Project Milestone, you can use the following extension points:View Name Extension PointS3.view.xml extDetailContent

1.3.2.3.4 Change WBS Element Status Type: Transactional app

DescriptionWith the Change WBS Element Status app, you can change the system and user status of a work breakdown structure element. Youcan inherit a user status (which does not have a system status assigned) to all sub-objects of a WBS element.

Technical RequirementsProduct Version: SAP Enhancement Package 7 for SAP ERP 6.0Product Version UI: UI for EHP7 FOR SAP ERP 6.0

For more information, see Implementation Information for Change WBS Element Status

Component for Customer MessagesPS-STPS-ST-OPR

1.3.2.3.4.1 Implementation Information for Change WBSElement Status

Required SAP NotesFor Change WBS Element Status, the following SAP note must be available on the back-end server:SAP Note Description1916348 Change WBS Element Status1931387 Change WBS Element Status

Technical DataThe following table lists technical objects specific for Change WBS Element Status:Back-end ComponentsOData Service (Version Number) Authorization Role (PFCG Role)PS_WBSELEMENTSTATUSCHANGE_SRV (1) SAP_PS_WBSELSTS_CHG_APP

Front-end Components

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 74 of 78

Component Technical NameUI5 Application PS_WBSELSTS_CHGBusiness Role SAP_PS_BCR_PROJECTMANAGERBusiness Catalog SAP_PS_BC_ProjectManagerBusiness Catalog Group SAP_PS_BCG_PROJECTMANAGER

For more information on how to implement these technical objects, refer to Central Implementation Information

ExtensibilityBusiness Add-InsTo extend Change WBS Element Status, you can use the following Business Add-In:BADI_PS_ODATA_WBS_STATUS_CHGYou can use this BAdI to add attributes to the existing application. For more information on this BAdI for OData services, see SAPCustomizing Implementation Guide Project System Structures Operative Structures Business Add-Ins for OData Services BAdI: WBS Element OData Service

Extension PointsTo extend Change WBS Element Status, you can use the following extension points:View Name Extension PointS3.view.xml extSystemStatusTabContentS3.view.xml extUserStatusTabContent

1.3.2.3.5 Project Definition Type: Fact sheet

DescriptionThe fact sheet Project Definition displays contextual information about a project in a Project System (PS) structure. You can navigate toits related entities and you can access related transactions in operational systems.

Navigation TargetsYou can navigate to the following apps, for example:

NetworkWBS Element (Displays the WBS Element corresponding to the first hierarchy level)

TransactionsYou can access the following transactions, for example:CJ2A (Structure Planning)

Technical RequirementsProduct Version: SAP enhancement package 7 for SAP ERP 6.0Product Version UI: UI for EHP7 for SAP ERP 6.0HANA Version: SAP HANA SPS06 Revision 68 or higher

Technical DataThe following table lists technical objects specific for Project Definition:Back-end ComponentsOData Service (Version Number) Authorization Role (PFCG Role)CB_PROJECT_SRV (1) SAP_PS_PROJECT_APP

Front-end ComponentsComponent Technical NameUI5 Application BSCBN_ANF_PS

For more information on how to implement these technical objects, refer to Central Implementation Information

Component for Customer MessagesPS-STPS-ST-OPR

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 75 of 78

1.3.2.3.6 WBS Element Type: Fact sheet

DescriptionThe fact sheet WBS Element displays contextual information about a work breakdown structure (WBS) element in a project structure.You can navigate to its related entities and you can access related transactions in operational systems.

Navigation TargetsYou can navigate to the following apps, for example:

Project DefinitionProject MilestoneNetwork ActivityProject ClaimProduction OrderPlanned OrderPurchase Requisition ItemInternal OrderMaintenance Order

TransactionsYou can access the following transactions, for example:CJ2A (Structure Planning)

Technical RequirementsProduct Version: SAP enhancement package 7 for SAP ERP 6.0Product Version UI: UI for EHP7 for SAP ERP 6.0HANA Version: SAP HANA SPS06 Revision 68 or higher

Technical DataThe following table lists technical objects specific for WBS Element:Back-end ComponentsOData Service (Version Number) Authorization Role (PFCG Role)CB_WBSELEMENT_SRV (1) SAP_PS_WBSELEMENT_APP

Front-end ComponentsComponent Technical NameUI5 Application BSCBN_ANF_PS

For more information on how to implement these technical objects, refer to Central Implementation Information

Component for Customer MessagesPS-STPS-ST-OPR

1.3.2.3.7 Network Type: Fact sheet

DescriptionThe fact sheet Network displays contextual information about a network in a project. You can navigate to its related entities and you canaccess related transactions in operational systems.

Navigation TargetsYou can navigate to the following apps, for example:

Project DefinitionWBS ElementNetwork Activity

TransactionsYou can access the following transactions, for example:CN23 (Network)

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 76 of 78

Technical RequirementsProduct Version: SAP enhancement package 7 for SAP ERP 6.0Product Version UI: UI for EHP7 for SAP ERP 6.0HANA Version: SAP HANA SPS06 Revision 68 or higher

Technical DataThe following table lists technical objects specific for Network:Back-end ComponentsOData Service (Version Number) Authorization Role (PFCG Role)CB_PROJECT_NETWORK_SRV (1) SAP_PS_PROJECTNETWORK_APP

Front-end ComponentsComponent Technical NameUI5 Application BSCBN_ANF_PS

For more information on how to implement these technical objects, refer to Central Implementation Information

Component for Customer MessagesPS-STPS-ST-OPR

1.3.2.3.8 Network Activity Type: Fact sheet

DescriptionThe fact sheet Network Activity displays contextual information about a network activity in a project. You can navigate to its relatedentities and you can access related transactions in operational systems.

Navigation TargetsYou can navigate to the following apps, for example:

Project DefinitionWBS ElementNetworkActivity ConfirmationProject Milestone

TransactionsYou can access the following transactions, for example:CN23 (Network)

Technical RequirementsProduct Version: SAP enhancement package 7 for SAP ERP 6.0Product Version UI: UI for EHP7 for SAP ERP 6.0HANA Version: SAP HANA SPS06 Revision 68 or higher

Technical DataThe following table lists technical objects specific for Network Activity:Back-end ComponentsOData Service (Version Number) Authorization Role (PFCG Role)CB_NETWORK_ACTIVITY_SRV (1) SAP_PS_NETWORKACTIVITY_APP

Front-end ComponentsComponent Technical NameUI5 Application BSCBN_ANF_PS

For more information on how to implement these technical objects, refer to Central Implementation Information

Component for Customer MessagesPS-STPS-ST-OPR

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 77 of 78

PUBLIC© 2013 SAP AG or an SAP affiliate company. All rights reserved.

Page 78 of 78