Extend SAP Fiori Applications

SAP Fiori Document Version: 1.0 - 2013-08-07

Extend SAP Fiori Applications

Table of Contents 1

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1

Extending SAP Fiori Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2

Gateway Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.1

Gateway Enhancements Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.2

Redefine an App's Gateway Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

2.3

Example of a Gateway Layer Enhancement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.4

Add a New Collection to a Gateway Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3

UI Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.1

UI Enhancements Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.2

Example of a UI Layer Enhancement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3.3

Download and Upload SAP Fiori Application Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.4

Configure Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.5

Test UI Modifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4

Other Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.1

Customizing an SAP Fiori App Login Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2

4.1.1

Customization Search Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

4.1.2

Syntax of Property Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.1.3

Configurable Login Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

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

Extend SAP Fiori Applications Table of Contents

1

Overview

1.1

Extending SAP Fiori Apps

The functionality of an SAP Fiori app can be extended by enhancing its Business Suite, SAP NetWeaver Gateway, and SAPUI5 layers. You might not have to enhance all three layers each time you want to extend an app. The criteria for determining whether or not a layer must be enhanced is described in the following table: Application Layer

When Enhancement is Required

More Information

Business Suite

The backend logic and content required for the app extension does not exist in the Business Suite.

Gateway

The backend logic and content required for the app extension exists in the Business Suite layer but is not exposed in the app's Gateway service.

Gateway Enhancements Workflow [page 4]

UI

The backend logic and content required for the app extension is exposed in the app's Gateway service but the UI does not consume it.

UI Enhancements Workflow [page 9]

The skills required to enhance each application layer are indicated in the following table: Application Layer

ABAP

Business Suite

Business Suite Layer

X

X

Gateway Layer

X

X

UI Layer

Extend SAP Fiori Applications Overview

Gateway

OData

X

X

SAPUI5

HTML5 and JavaScript

X

X


3

2

Gateway Enhancements

2.1

Gateway Enhancements Workflow

Modify an app's Gateway layer when you need to expose backend logic and content to the UI layer. 1.

In SAP NetWeaver Gateway Service Builder, redefine the relevant Gateway service for the app.

2.

Override the relevant service class methods to expose the backend logic and content required for the functionality you are extending to the app.

Note The specific methods you need to override vary by app and by the functionality you are extending to the app. 3.

Call the redefined service from a web browser to verify that new data is being sent over OData. a) Use transaction /IWFND/MAINT_SERVICE to select the redefined service. b) Select OData on the lower left side of the screen. c) Click Call Browser to view the results in an XML file.

Related Links Redefine an App's Gateway Service [page 4] You can use SAP NetWeaver Gateway Service Builder to redefine an SAP Fiori app's Gateway service. Example of a Gateway Layer Enhancement [page 6] This example describes how to extend the My Leave Requests app to include an Urgent field on all leave requests. Add a New Collection to a Gateway Service [page 7] You can extend a Gateway service to consume additional OData by using the Include function to add a new collection to the service.

2.2

Redefine an App's Gateway Service

You can use SAP NetWeaver Gateway Service Builder to redefine an SAP Fiori app's Gateway service. 1.

Log on to SAP NetWeaver Gateway system.

2.

Open transaction SEGW.

3.

In SAP NetWeaver Gateway Service Builder, open the exisitng project you want to redefine or create a new project.

4.

Choose Edit to switch to editing mode.

5.

Right-click on the Data Model folder and choose

6.

In the Wizard Step 1 of 2: Redefine Service screen, enter the technical name of the service you wish to redefine.

Redefine Service

OData Service (GW) .

Note

4


Extend SAP Fiori Applications Gateway Enhancements

If you enter the technical service name from the input help window, the version of the service is automatically populated. If you enter the technical service name manually, you must specify the version. 7.

If the metadata of the selected service resides in another system, select Metadata to be fetched from an external system and enter the RFC destination of the external system.

8.

Click Next.

9.

In the Wizard Step 1 of 2: Redefine Service screen, select the required artifacts.

Note There is a selection logic in the backend, which automatically includes all the entity types that are end types/return type of chosen association/function import. The reverse is not selected. For example, consider the following model: COMPLEX TYPES ○

complex_type_1

○

complex_type_2

ENTITY TYPES ○

entity_type_1

○

entity_type_2

○

entity_type_3

ASSOCIATIONS ○

association_1 (between Entity_type_1 & Entity_type_2)

○

association_2 (between Entity_type_1 & Entity_type_3)

FUNCTION IMPORTS ○

function_import_1

Case1: User selects Entity_Type_1, Entity_Type_2 and Association_1. All these entities are selected and used in the new model. If Entity_Type_1 & Entity_Type_2 uses Complex_Type_1 & Complex_Type_2, they are automatically selected. Case2: User selects Entity_Type_1, Association_2. Since Entity_Type_3 is part of the Association_2, Entity_Type_3 it is selected automatically along with Entity_Type_1 and Association_2. 10. Click Finish. The selected artifacts are transferred to their respective folders in the tree view of the SAP NetWeaver Gateway Service Builder, and a node for the service is added to the Model References folder. 11. In the Model References folder, double-click the node of the service that you want to redefine, to confirm its model reference type is Extend.

Note If the model has been included, then its reference type in the mass maintenance view appears instead as Include. 12. Redefine the model as desired by performing any of the following activities: ○

Delete artifacts

○

Change Node Names and Labels by switching to edit mode and:



5

○

Click Redefine Attribute to edit Node Name and Label fields.

○

Click Undo Redefinition to revert the redefined value to the original value.

○

Click Undo Identical Redefinition to view the fields which have been reverted to their original values in the course of editing.

Note Deleting a label is not a supported redefinition activity, because: ○

Metadata will not reflect the deletion and still show the label.

○

There will be issues in the assignment of text keys to labels in the generated MPC (model provider class), which will lead to incorrect label settings for other artifacts.

13. Generate runtime objects by: Option

Description

Re-using the existing service

During the generation process, a new model needs to be created that includes an MPC (model provider class). This MPC uses the extend_model( ) API and refers to the original model. After the new model has been created, it should be related to the old service.

Note Since the original service has been modified, the service registration for this service on the hub has to be deleted and the service has to be registered again to reflect the changes. Creating a new service

A new service and a new model will be created and registered during the generation process.

After the service has been generated, the MPC classes are stored in the Runtime Artifacts folder

2.3

Example of a Gateway Layer Enhancement

This example describes how to extend the My Leave Requests app to include an Urgent field on all leave requests. Although a backend Urgent field exists in the Business Suite, the developer discovers that the Gateway layer for the My Leave Requests app does not currently expose it to the UI. Here are the best practices the developer can follow to enhance the app's Gateway service with support for the Urgent field: 1.

In SAP NetWeaver Gateway Service Builder, redefine the specific Gateway service for the My Leave Requests app: /GBHCM/S_ELR_LEAVE_REQUEST.

2.

Override the following service class methods to include the Urgent field: Method

6

Override Activity

/GBHCM/IF_ELR_ODC_API~ GET_ENTITYSET_LEAVEREQUEST

Add the Urgent field to the set of data retrieved by the application UI

/GBHCM/IF_ELR_ODC_API~ CREATE_ENTITYSET_LEAVEREQUEST

Add the Urgent field to the set of data created by new leave requests



Method /GBHCM/IF_ELR_ODC_API~ CREATE_ENTITYSET_LEAVEREQUEST

Override Activity Add the Urgent field to the set of data updated when users edit existing leave requests

Note In the My Leave Requests application, the CREATE method includes both CREATE and UPDATE functionality. 3.

Call the redefined service from a web browser to verify that data for the new Urgent field is being sent over OData. a.

Use transaction /IWFND/MAINT_SERVICE to select the redefined service, /GBHCM/ S_ELR_LEAVE_REQUEST.

b.

Select OData on the lower left side of the screen.

c.

Click Call Browser to view the added Urgent data in a leave request collection XML file.

Example LeaveRequestCollection.xml excerpt:

2.4

Add a New Collection to a Gateway Service

You can extend a Gateway service to consume additional OData by using the Include function to add a new collection to the service. A typical use for this would be when an application shows information about a company's employees, but home addresses are not included in the employee details fetched using the relevant BAPI. To display home addresses, you can use a Gateway service Include to add a new data collection that includes employee home addresses. The addresses are then fetched by the "new" BAPI.



7

1.

Create a new Gateway project.

2.

Click the new project to expose the Data Model folder.

3.

Right-click Data Model and choose

4.

In the Include Model from Service dialog, select the relevant Gateway service to link it to the new project.

5.

Open the Data Model folder, right-click on Entity Types and choose Create.

6.

In the Create Entity Type dialog, enter a name for the new entity type and select Create Related Entity Set.

7.

Once created, double-click the new entity type and then double-click its Properties folder.

8.

In the Properties area, click Append Row to add new properties. Each new property relates to a field in the underlying BAPI .

9.

Include

OData Service (GW) .

Option

Description

Name

The name that is exposed in the OData collection

Edm Core Type

The property type (for example, String)

ABAP Field Name

The name you use in the code when you create the Include.

Click Generate Runtime Objects to create the corresponding runtime items, methods, and entity sets.

10. To start implementing the code: a) Double-click the Runtime Artifacts folder and select the generated Data Provider Extension Class. b) Look for the methods (CREATE, DELETE, GET, UPATE) by the entity set name. These are the methods that are automatically generated. (The name of each entity set will be the prefix of the generated methods). c) Implement the relevant code logic in any method that suits the Include you want to add.

8



3

UI Enhancements

3.1

UI Enhancements Workflow

Modify the UI layer when the information required for an app extension is exposed by the app's Gateway service but is not displayed on the UI. Prerequisites are: ●

SAPUI5 Application Development Tool for Eclipse

●

All SAPUI5 plugins are version 1.12 or higher (version numbers appear on the Installed Software tab of the

●

Local Tomcat webserver configured to work with SAPUI5 Eclipse

●

Related ABAP developer authorizations

●

Developer Key and Object Keys to change SAP objects (if using the ABAP report to upload modifications)

Help

About Eclipse

Installation Details

dialog box)

The following checklist lists the tasks to be performed when enhancing an SAP Fiori app UI. Task

Check

Description

More Information

1

❑

Download application code to Eclipse

Download and Upload SAP Fiori Application Code [page 16]

2

❑

Modify UI files as needed

Example of a UI Layer Enhancement [page 10]

3

❑

Configure paths within the app to point to the relevant Gateway system

Configure Paths [page 17] SAPUI5 Developer Guide/API Reference Page, available in the ABAP system at {protocol}://{host name}:{port number}/sap/ public/bc/ui5_ui5/ demokit/

4

❑

Test UI modifications as needed

5

❑

Create a transport request in the ABAP system

6

❑

Test UI Modifications [page 17]

Use the ABAP report /UI5/UI5_REPOSITORY_LOAD to upload the contents of the WebContent folder of your SAPUI5 project back to the application. In the report, enter the BSP system name of the extended SAP Fiori application (for example,

Extend SAP Fiori Applications UI Enhancements


9

Task

Check

Description

More Information

UI5_HCM_LR_CR) and provide the transport request created in task 5 above.

Note To prevent Eclipse from automatically formatting untouched content--causing unintended modifications to SAP-delivered files when you upload your changes--make sure that the Perform the selected actions on save option is deselected in the

Window

Preferences

JavaScript

Editor

Save Actions

screen.

Related Links SAPUI5 Development Toolkit UI Theme Designer

3.2

Example of a UI Layer Enhancement

This example shows how to modify the UI code for the My Leave Requests app so that users can view and modify the Urgent status on their leave requests.

Example Add Urgent Option to New Leave Requests:

1.

Add a checkbox control to the leave request by modifying view\S4.view.html. Inside the checkbox div, add the data-text property that links the field to its translation.

Note

10



The code samples shown throughout this example include comments that explain what is being done in the extended code.

2.

Add the checkbox control label to i18n\i18n.properties:

Note To make it easier to translate the app, the i18n.properties file serves as a central storage area for all of the text strings that appear in the app. When you add or modify strings in i18n.properties, remember to also add or modify them in all language-dependent property files (for example, i18n_en.properties and i18n_de.properties). 3.

In the Create Leave page controller file (view\S4.controller.js ): a.

Add a checkbox control to the onInit method:

b.

Modify the onTapOnDate method that calculates the selected days for the leave request to automatically select the Urgent option when fewer than seven days are left before the start date of the request:



11

c.

Modify the callDialog method to display the Urgent status in the leave request confirmation dialog box:

12



Add Urgent Status to the Leave Requests History List:

1.

In the History view file (view\S3.view.js), add a text field for the Urgent status:

2.

In the History view controller file (view\S3.controller.js), edit the onInit method to add the text field functionality and bind it to the data model:

3.

Change the formatter file (utils\Formatters.js):



13

Add Urgent Status to the Leave Requests History Details:

1.

14

Add the Urgent field to the History Item Details controller (view/S6B.controller.js):



Add and Retrieve the Urgent Value in Leave Requests: 1.

Change the request XML to include the data coming from the checkbox control: a.

In s4.controller.js, add the checkbox value to the post request.

b.

In DirectOData.js, retrieve the state of the checkbox:



15

c.

3.3

Add the checkbox value to the post request:

Download and Upload SAP Fiori Application Code

To download and upload SAPUI5 application code to and from Eclipse and a BSP server, use the ABAP report /UI5/UI5_REPOSITORY_LOAD. Perform the following steps to download code from a BSP server to Eclipse. The steps for uploading code from Eclipse back to the BSP server are similar, but substitute Upload for Download. 1.

Use transaction SE38.

2.

Enter /UI5/UI5_REPOSITORY_LOAD in the Program field and click Execute.

3.

Enter the BSP system name of the SAP Fiori application, select Download, and click Execute.

4.

In the Browse for Folder dialog box, browse to the workspace folder where you want the application to be saved and click OK.

5.

At the bottom of the new file list, click Click here to Download.

6.

In the Enter Parameter for Download from the SAPUI5 ABAP Reporter dialog box, leave the External Codepage field empty and continue.

7.

In Eclipse, create a new SAPUI5 Application Project by clicking New SAPUI5 Application Development and selecting SAPUI5Application Project from the first page of the wizard.

8.

Continue using the wizard to enter a name, location, and target device (select Mobile) for the project, but deselect the Create an Initial View option before clicking Finish.

9.

Copy all files and folders from the SAP Fiori app you downloaded to your file system to the WebContent folder of the new SAPUI5 application project.

16



3.4

Configure Paths

Before you can test your modifications to the UI layer, the paths in the extended app must point to the Gateway service on your local system. For example: ●

The original path: /sap/opu/odata/GBHCM/LEAVEREQUEST

●

The path to your local Gateway service: /sap/opu/odata/sap/ZEXT_LEAVEREQUEST

The following table displays the files containing paths that will need to be modified, and the code to search for in each file in order to replace the paths: File

Locations of Required Path Changes

utils/DirectOData.js

sap.hcm.leaverequest.create.utils.Ajax.fir eHttpPost sap.hcm.leaverequest.create.utils.Ajax.fir eHttpGet sap.hcm.leaverequest.create.utils.Ajax.fir eHttpDelete sap.hcm.leaverequest.create.utils.Ajax.fir eCachedHttpGet

Application.js

In the init() method:

var MODEL_BASE = "" var MODEL_ID = ""

Remember Update the version parameter (""v=") to point to the version you are working on.

view/S4.controller.js

3.5

The onNavigatedTo() method

Test UI Modifications

You can test UI modifications using a Web App Preview or an external web browser. Prerequisites are: ●

The application paths in the extended app point to the correct system.

●

Your Tomcat webserver is configured to work with SAPUI5 Eclipse.

Note



17

When testing locally using real OData data, use the SimpleProxyServlet to avoid cross-domain issues. For more information on configuring the SimpleProxyServlet, including sample XML code, see SAPUI5 Development Tools

Application Development Tools

Developer Guide

Testing a SAPUI5 Application

Simple Proxy

Configuration , available in the ABAP system at {protocol}://{host name}:{port number}/sap/ public/bc/ui5_ui5/demokit. To start testing: 1.

In Eclipse, set Google Chrome as your default web browser: a) Choose

Window

Preferences under General

Web Browser .

b) On the Web Browser tab, select Use external browser and select Chrome in the external browser list.

Note If Chrome does not appear in your external browser list, click New… to add it. 2.

3.

Choose how to test the application: ○

To use a Web App Preview, select

○

To use your Tomcat server, right-click your application project and choose

Run As

Web App Preview Run As

Run on Server

Append the following optional parameters to the URL in your web browser to test different scenarios: URL Parameter

Description

sap-ui-xx-fakeOS

Simulates how the app will look on a mobile device

responderOn=true

Tests against mock data

proxyOn=true

Use when running as a Web App Preview to test against real data provided by the OData service

Related Links Configure Paths [page 17] Before you can test your modifications to the UI layer, the paths in the extended app must point to the Gateway service on your local system.

18



4

Other Customizations

4.1

Customizing an SAP Fiori App Login Screen

The SAP Fiori ICF system login class (/UI2/CL_SRA_LOGIN) allows rich customization of its web pages (login form, password change form, and password change error or success message page). To perform customization at the application level or application group level, publish property files in the MIME repository.

4.1.1

Customization Search Path

Customization is triggered by the existence of a login.properties file in the MIME repository anywhere in the path of the request that triggered the login sequence.

Example Assume a login is triggered by the following request: /my/application/path/request.html The login class will search in order for the following files: 1.

/my/application/path/login.properties

2.

/my/application/login.properties

3.

/my/login.properties

The search stops when a file is found.

SAP UI Applications For SAP UI5 applications accessed through the /sap/bc/ui5_ui5/ path, search will take place under the /sap/bc/bsp/ node. For example, the UI2 launch page /sap/bc/ui5_ui5/ui2/launchpage/index.html can be customized through: ●

/sap/bc/bsp/ui2/launchpage/login.properties

●

/sap/bc/bsp/ui2/login.properties

●

...

Extend SAP Fiori Applications Other Customizations


19

Internationalization Files If a login.properties file is found, the login class will then look for an optional internationalization (i18n) file in the same MIME folder. The I18n file name is login_XX.properties where XX represents the uppercase 2-letter ISO 639-1 code of the language under which the login class executes (for example, login_EN.properties, login_DE.properties…)

4.1.2

Syntax of Property Files

Property files must be UTF-8 encoded text files with Microsoft Windows style line endings (CR + LF). They are processed on a line by line basis. ● ●

Blank lines contain only whitespace characters (spaces, tabs). Comment lines are introduced by a # (hash) sign optionally preceded by any number of whitespace characters.

●

Property definition lines are standard property=value type lines: ○

All whitespace characters before the = (equal) sign are ignored.

○

At most one whitespace character after the = (equal) sign is ignored.

Example # Simple configuration header_visible=true header_title=My Application application_languages=EN,FR,DE

4.1.3

Configurable Login Properties

Table 1: Common Properties Property

Description

Default value

img_favicon

Login page favicon

/sap/public/bc/ui2/logon/img/favicon.ico

img_logo

Login page logo

/sap/public/bc/ui2/logon/img/ sap_logo.png

img_logo_width

Logo width

64

img_background

Background image

/sap/public/bc/ui2/logon/img/ login_background.jpg

img_background_mobile

Background image for mobile portrait

/sap/public/bc/ui2/logon/img/ login_background_mobile.jpg

20



Property

Description

Default value

img_background_mobile_land

Background image for mobile Landscape (SAP Note 1881196)

/sap/public/bc/ui2/logon/img/ login_background_mobile_land.jpg

header_title

Header box title

header_subtitle

Header box subtitle

header_visible

Show header box

false

label_copyright

Copyright notice

Inherited from CL_ICF_SYSTEM_LOGIN

ui5_theme

SAPUI5 CSS theme

sap_bluecrystal

Table 2: Properties for the Login Page Property

Description

Default value

label_title_login

Login page HTML title


label_user

User field label


label_password

Password field label


label_language

Language selection label


label_client

Login button label


label_button_login

Client selection label


label_change_password

Change password button label


text_error_user_initial

Error message for missing user


text_error_pwd_initial

Error message for missing password


text_error_client_initial

Error message for missing client Inherited from CL_ICF_SYSTEM_LOGIN

Table 3: Properties for the Change Password Page Property

Description

Default value

label_title_changepwd

Change password page HTML title


label_current_password

Current password field label


label_new_password

New password field password


label_confirm_password

New password confirmation field label


label_button_change

Password change button label


label_button_cancel

Password change cancellation button label


Table 4: Properties for the Changed Password Page This page is the final step of a change password operation. It is displayed after a successful password change, or instead of the change password form if password change is not possible.



21

Property

Description

Default value

label_title_msg_error

Password change failed HTML title


label_title_msg_info

Password change with info messages HTML title


label_title_msg_ok

Password change success HTML title


script_msg_selfsubmit_error

Message display duration for error status in milliseconds

0 (until user clicks on button)

script_msg_selfsubmit_info

Message display duration for info status in milliseconds

0 (until user clicks on button)

script_msg_selfsubmit_ok

Message display duration for ok status in milliseconds

5000

label_button_msg_error

Continue button for error status Inherited from CL_ICF_SYSTEM_LOGIN

label_button_msg_info

Continue button for info status


label_button_msg_ok

Continue button for ok status


Configuring Language Support If the option to display language selection is active, a control showing all available languages in the NetWeaver system will be added to the login form. If SAP Note 1857070 is installed, it is possible to restrict the list of displayed languages to show only those supported by the application. This is done by setting the application languages property. The value must be a list of comma-separated uppercase 2 letter ISO 639-1 language codes, for example: # Application supported languages application_languages=EN,FR,DE In that case, a language will be available for selection in the login form if the following conditions are both met: ●

It is available in the NetWeaver system

●

It is declared in the application_languages_property

22



www.sap.com/contactsap


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

Extend SAP Fiori Applications

Recommend Documents