Building Block Configuration Guide sap fiori apps rapid-deployment solution



Download 392.93 Kb.
Page1/7
Date09.01.2017
Size392.93 Kb.
#8088
  1   2   3   4   5   6   7












Building Block Configuration Guide

SAP Fiori apps rapid-deployment solution

Document Version: 1.0 – 2015-12-15


Customer

SAP Fiori App Extensibility

(MF8)




Typographic Conventions


Type Style

Description

Example

Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Textual cross-references to other documents.



Example

Emphasized words or expressions.

EXAMPLE

Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example

Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.



Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE

Keys on the keyboard, for example, F2 or ENTER.


Document History


Version

Date

Change

1.0

2014-09-26

Initial version.

2.0

2014-11-28

Second Version: first scenario using SAP WebIDE Development environment

Table of Contents


Typographic Conventions 2

Document History 3

Table of Contents 4

Purpose 6

Extend SAP-Delivered Standard Fiori Applications using SAP Web IDE 7

Prerequisites 7

Check and Activate HTTP Service in SAP Gateway System 8

Configure SAP Web IDE 8

Extend Track Purchase Orders App 9

Create Extension Project for Track Purchase Orders App 10

Hide Title Field 10

Hide Field on SAP Fiori Screen by Code Modifications 12

Change Label (Usage of Language File) 14

Change Label (View Replacement) 16

Add Field Showing Item Type Description 18

Replace View 21

Test your Extension in SAP Web IDE 23

Deploy Extension Project 24

Extend SAP-Delivered Standard Fiori Applications using Eclipse IDE 26

Prerequisites 26

Download the SAP-Delivered Standard Fiori Application from the ABAP System 27

Retrieving the Fiori App Name 27

Retrieving the Fiori App 28

Import the SAP-Delivered Standard Fiori Application on Eclipse 29

Create the Application Project 29

Import the Downloaded Application to the Eclipse Project 30

Extend OData Service 30

Extend ABAP DDIC Structure Using an Append Structure 32

Extend OData Service 34

Test the Extended OData Service 38

Extend SAP-Delivered Standard Application 38

Create the Extension Application Project 38

Change a Field Label 40

Hide a Field 43

Implement the View Extension (Add Fields) 45

Implement a View Replacement 50

Upload the Custom Application to the ABAP System 53

Upload the Fiori App 53

Configure the Custom Application on the Fiori Launchpad 56

Create a New Launchpad 56

Create a New Catalog 58

Create a New Tile in the Catalog 59

Create a New Role for the Catalog 62

Add a New Tile to the Launchpad 63

Additional Information 64



Purpose


The purpose of this document is to describe the general configuration steps required to extend an SAP Fiori app. It is not a development tutorial but, with the selected apps

Track Purchase Orders for SAP Web IDE,

My Quotation for Eclipse IDE,

As examples, it explains easy to understand use cases how an SAP Fiori app can be extended.

Basically there are two different IDEs covered by this document. SAP Web IDE basically is the default option to be used. However –there might be project-specific reasons not to use the SAP WEB IDE – then Eclipse IDE can be used instead.

In this version, the following use cases are described:

change a field label

hide a field

add a field to the UI – including the required extensions on backend and frontend server (ODATA extensions).

change the sequence of fields

hide a screen area

In future versions of this document, additional use cases may be added.

The above mentioned use cases can be carried out independently from each other meaning you can pick the one you are interested in and skip the others.

 Note

The document is clustered in three main areas:



  • Extend SAP-Delivered Standard Fiori Applications using SAP Web IDE

  • Extend SAP-Delivered Standard Fiori Applications using Eclipse IDE

  • Configure the Custom Application on the Fiori Launchpad

No matter on which way you extend the SAP delivered Fiori app you need to run through the chapter ‘Configure the Custom Application on the Fiori Launchpad’ in both cases.

Within the chapter ‘Extend OData Service’ the sub chapter ‘Extend SAP-Delivered Standard Fiori Applications using Eclipse IDE’ is describing how to extend an OData Service. This chapter might be relevant as well in case you extend your SAP delivered Fiori app via SAP Web IDE adding new fields that are not covered by the ODATA service yet.




Download 392.93 Kb.

Share with your friends:
  1   2   3   4   5   6   7




The database is protected by copyright ©ininet.org 2024
send message

    Main page