Expert Guided Implementation for SAP Mobile: Fiori Day 4 Support from Experts for the implementation of SAP Fiori
Expert Guided Implementation schedule: SAP Fiori UX Day 1
Day 2
Day 3
Day 4
Empowering lesson Step-by-step guide to the installation and configuration of SAP Fiori Applications.
Empowering lesson Launchpad configuration Introduction to theme designer SAP Fiori Client
Empowering lesson Introduction to SAP Web IDE the web based tool for developing and customizing SAPUI5 based applications
Empowering lesson SAP Fiori end to end Extensibility – How to add a Custom field in OData and UI
(Web session, 2 h. in the morning)
(Web session, 2 h. in the morning)
Execution by customer Customer configures SAP Fiori Applications
Execution by customer Configuration of Launchpad and creation of custom themes
(Remote support in the afternoon)
(Remote support in the afternoon)
Execution by customer Customer accesses SAP Web IDE through SAP HANA Cloud Platform
(Web session, 2 h. in the morning)
(Remote support in the afternoon)
(Web session, 2 h. in the morning)
Execution by customer Customer extends an OData service and UI to add a custom field to an standard SAP Fiori Application (Remote support in the afternoon)
Goal of the day Customer has knowledge to configure SAP Fiori Applications
Goal of the day Customer has Launchpad and Theme Designer configured
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Goal of the day Customer enabled to start using SAP Web IDE development environment
Goal of the day Customer has added a custom field to the standard SAP Approve Request app
Customer
2
Introduction
Introduction In this EGI we will show you how to extend currently available Fiori applications that are used on your system. Extending an application means you will not be overwriting any of the applications original code, you will implement an enhancement spot to add an additional field to the existing OData service and creating a BSP application which acts as an extension of the application, such as ‘Approve Purchase Order’. In this EGI you will be extending the ‘Approve Purchase Order’ Fiori application. We will be adding a new label, which will show the Purchasing Group that the Purchase order is attached too. This will involve extending the OData service in the backend to provide the data for the new label and extending the UI frontend to display this data. This extension will be shown in the following slide.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
4
Unit 1: OData Extensibility
OData extensibility Sample scenario
In this example we will show you how to add the “Purchasing Group” field in SAP Fiori Approve Purchase Orders.
© 2012 SAP AG. All rights reserved.
6
OData extensibility OData Implementation is in 3 steps.
1. Extend the corresponding ABAP DDIC Structure by Append Structure 2. Extend the OData Entity in the GW Model Provider by implementing BADI 3. Fill data to the custom fields in the GW Data Provider by implementing BADI Prerequisites •
SAP Fiori Approve Purchase Order is up and running.
•
You have ABAP programming experience.
•
You have UI development experience.
© 2012 SAP AG. All rights reserved.
7
OData extensibility Review the OData service and confirm “Purchasing Group” is not present in the WorkflowTask entity type
In transaction /IWFND/GW_CLIENT enter the following URI and click execute /sap/opu/OData/SAP/GBAPP_POAPPROVAL/$metadata
© 2012 SAP AG. All rights reserved. There is no Property for “Purchasing Group” in Header detail.
8
Step 1. Extend the corresponding ABAP DDIC Structure by Append Structure [ERP] Add the field „Purchasing Group“ in the structure of the Purchase order entity. 1. Open the structure Transaction: SE80 Package: GBAPP_APV_PO Structure: GBAPPS_PO_HEADER_DETAILS_INCL and GBAPPS_PO_WORKFLOW_TASK_INCL
© 2012 SAP AG. All rights reserved.
9
Step 1. Extend the corresponding ABAP DDIC Structure by Append Structure [ERP] Double click the include GBAPPS_PO_HEADER_DETAILS_INCL.
© 2012 SAP AG. All rights reserved.
10
Step 1. Extend the corresponding ABAP DDIC Structure by Append Structure [ERP] Select the „Append Structure...“ button.
© 2012 SAP AG. All rights reserved.
11
Step 1. Extend the corresponding ABAP DDIC Structure by Append Structure [ERP] Enter the Append name: ZPO_H_DETAILS
© 2012 SAP AG. All rights reserved.
12
Step 1. Extend the corresponding ABAP DDIC Structure by Append Structure [ERP] Add field: ZZEKGRP TYPES EKGRP
Activate the Append Structure.
© 2012 SAP AG. All rights reserved.
13
Step 1. Extend the corresponding ABAP DDIC Structure by Append Structure [ERP] Repeat same steps for GBAPPS_PO_WORKFLOW_TASK structure in include GBAPPS_PO_WORKFLOW_TASK_INCL.
© 2012 SAP AG. All rights reserved.
14
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] In the step 2, you are going to implement a BAdI method which adds “Purchasing Group” property in the Model Provider class. You can find the enhancement spot for the App in SE80:
© 2012 SAP AG. All rights reserved.
15
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] You can see which BAdis can be implemented in the app extensibility documentation:
http://help.sap.com/fiori_bs2013/helpdata/en/14/75145367039354E10000000A4450E5/content.htm
© 2012 SAP AG. All rights reserved.
16
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] Go to transaction: SE18
For Enhancement Spot enter: GBAPP_APV_PO Click on Display Enhancement Spot
© 2012 SAP AG. All rights reserved.
17
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] Right click on Implementations under “GBAPP_APV_PO_MDP” and select “Create BAdI Implementation” . You will then be prompted to create an enhancement implementation.
© 2012 SAP AG. All rights reserved.
18
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] Enter a Enhancement Implementation name and Description
Click on the Green tick to continue
Click on Local Object
© 2012 SAP AG. All rights reserved.
19
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] Enter a BAdI Implementation name, Description and Implementing Class name
Click on green tick to continue
© 2012 SAP AG. All rights reserved.
20
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] You have option for copying the sample class. In this example, we will copy the sample class.
Highlight the sample class and click on “Copy Sample Class”
Select Local Object in the next screen
© 2012 SAP AG. All rights reserved.
21
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] Implement the BAdI
Double click the Implementing Class.
© 2012 SAP AG. All rights reserved.
22
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] Double click the method.
You see the sample code with comments.
© 2012 SAP AG. All rights reserved.
23
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] Enter the code:
DATA: lo_property TYPE REF TO /iwbep/if_mgw_OData_property. IF iv_entity_type_name = 'HeaderDetail' OR iv_entity_type_name = 'WorkflowTask'. lo_property = io_entity_type>create_property( iv_property_name = 'ZPurchasingGroup' iv_abap_fieldname = 'ZZEKGRP' ). lo_property->set_nullable( abap_true ). ENDIF.
© 2012 SAP AG. All rights reserved.
24
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] Activate the method
© 2012 SAP AG. All rights reserved.
25
Step 2 . Extend the OData Entity in the GW Model Provider by implementing BAdI [ERP] Activate the method
Select all the objects and click the green tick to continue
© 2012 SAP AG. All rights reserved.
26
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] Go back two screens to the Enhancement Spot screen
Right click on Implementations under GBAPP_APV_PO_RDP and select “Create BAdI Implementation” Select the previously created Enhancement Implementation
© 2012 SAP AG. All rights reserved.
27
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] Enter a BAdI Implementation name, Description and Implementing Class name
Click on green tick to continue
© 2012 SAP AG. All rights reserved.
28
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] Copy the sample class
Select Local Object in the next screen © 2012 SAP AG. All rights reserved.
29
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] Implement the BAdI
Double click the Implementing Class.
© 2012 SAP AG. All rights reserved.
30
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] Double click the method CHANGE_HEADER_DETAILS_INFO_API.
© 2012 SAP AG. All rights reserved.
31
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] You see the sample code with comments.
© 2012 SAP AG. All rights reserved.
32
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] Implement the code
METHOD if_gbapp_ex_apv_po_rdp~change_header_details_info_api. DATA: lv_po_number TYPE ebeln. lv_po_number = cs_header_details_x-po_number. SELECT SINGLE ekgrp FROM ekko INTO cs_header_details_x-zzekgrp WHERE ebeln = lv_po_number . ENDMETHOD.
© 2012 SAP AG. All rights reserved.
33
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] Activate the method
Select “All Objects”
© 2012 SAP AG. All rights reserved.
34
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] Repeat same step for CHANGE_WORKFLOW_TASK_API method.
© 2012 SAP AG. All rights reserved.
35
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] Implement the code
METHOD IF_GBAPP_EX_APV_PO_RDP~CHANGE_WORKFLOW_TASK_API. DATA: lv_po_number TYPE ebeln. FIELD-SYMBOLS: TYPE GBAPPS_PO_WORKFLOW_TASK. LOOP AT CT_WORKFLOW_LIST ASSIGNING . lv_po_number = -po_number. SELECT SINGLE ekgrp FROM ekko INTO zzekgrp WHERE ebeln = lv_po_number . ENDLOOP. ENDMETHOD.
© 2012 SAP AG. All rights reserved.
36
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] Check the OData service Clear the Cache When you changed the Model, you have to clear Gateway cache in both Gateway and ERP backend. Transaction: /IWFND/CACHE_CLEANUP on Gateway server
Transaction: /IWBEP/CACHE_CLEANUP on ERP Server
© 2012 SAP AG. All rights reserved.
37
Step 3. Fill data to the custom fields in the GW Data Provider by implementing BADI [ERP] Test the OData service:
http://t15tdc00.wdf.sap.corp:55080/sap/opu/odata/sap/GBAPP_POAPPROVAL/$metadata
© 2012 SAP AG. All rights reserved.
38
Unit 2: Extend SAP Fiori Application with SAP Web IDE
Agenda •
Prerequisites
•
Downloading Fiori Applications
•
Creating an Extension Project
•
Uploading Applications
•
Making Semantic Objects
•
Creating a Tile for the Extended application
•
Testing the Fiori Application
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
40
Prerequisites for todays demonstration •
An SAP HANA Cloud Platform account https://account.hanatrial.ondemand.com/
•
Download SAP HANA Cloud connector to access backend systems https://tools.hana.ondemand.com/#cloud
•
Further information on above steps: http://scn.sap.com/docs/DOC-55465
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
41
Create a new Extension Project in SAP Web IDE In Web IDE right click on “Local”, then select New > Extension Project
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
42
Create a new Extension Project in SAP Web IDE Select Remote>SAPUI5 ABAP Repository:
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
43
Create a new Extension Project in SAP Web IDE Select your remote system and click “OK”
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
44
Create a new Extension Project in SAP Web IDE Search for Approve Purchase Orders and click OK
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
45
Create a new Extension Project in SAP Web IDE Select “Import parent application” and click “Next”
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
46
Create a new Extension Project in SAP Web IDE Select “Open extension project in extensibility pane”
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
47
Create a new Extension Project in SAP Web IDE The project opens in the extensibility pane
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
48
Replace existing view with custom view Switch to Extensibility mode from the dropdown
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
49
Replace existing view with custom view Select “Show extensible elements” in the extensibility pane on the right
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
50
Replace existing view with custom view Clicking on an element in the preview highlights its corresponding element in the extensibility pane. Here we can see that we have highlighted “S3” view which has extensibility options for the “Header” and “Infoform” elements
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
51
Replace existing view with custom view Highlight the S3 view, and from the Extend menu select “Replace with a copy of the parent view”.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
52
Replace existing view with custom view Select
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
53
Replace existing view with custom view Now we see the “S3Custom.view.xml” view in our Web IDE extension project
Double click on the “S3Custom.view.xml” view to see the source code
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
54
Customize new extension project Now we are going to create a field label in the i18n file to display our text “Purchasing Group”. Right click on the “MM_PO_APVExtension” folder, then click on New > Folder
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
55
Customize new extension project Enter “i18n” and click “OK”.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
56
Customize new extension project In the parent application right click on the file and select “Copy”
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
57
Customize new extension project In the extension project right click on the “i18n” folder and click “paste”
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
58
Customize new extension project Rename the file to “i18n_custom.properties”
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
59
Add new label to internationalization folder After the Company Code label paste our label and then save and close the file: #XFLD: Purchasing Group field label view.PurchaseOrder.purchasingGroupLabel=Purchasing Group
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
60
Add label to custom view Open the S3Custom.view.xml file and paste the following code in the extension point “extInformation” (after line 172) which we saw in the extensibility pane is the extension point for the infoform where we want to add our label:
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
61
Add label to custom view Code to paste after line 172:
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
62
Configure Component.js to reference our internationalization folder Now we have to adjust the “Component.js” file to reference our new i18n_custom.properties file when looking for the text to enter in the label. In the “Component.js” file in the extension project enter the following code:
"sap.ca.i18Nconfigs":{ "bundleName":"ui.s2p.mm.purchorder.approve.MM_PO_APVExtension.i18n.i18n_custom" }
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
63
Test the extended application Select the index.html file and click “Run” to test the application
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
64
Test the extended application Here we can see our label and value from the extended OData service is displayed
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
65
Deploy project to on premise backend system Next we can deploy the extended project to our front end server and add a tile to our Fiori launchpad so we can launch the extended application from the launchpad. Right click on the extension project and select Deploy > Deploy to SAPUI5 ABAP Repository
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
66
Deploy project to on premise backend system Select our system from the drop down list and click Next
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
67
Deploy project to on premise backend system Enter the following details
Name: Z_EXT_APO Description: as shown Package: $TMP Click Next
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
68
Deploy project to on premise backend system Click Finish to deploy the application
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
69
Deploy project to on premise backend system If we go to transaction SE80 and search for our project “Z_EXT_APO” under “BSP Application” we can see our project with our custom view: S3Custom.view.xml
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
70
Adding Extended Application to Launchpad
Agenda Steps to add extended application •
Create a semantic object
•
Create a catalog
•
Creating a Tile and Target Mapping for the Extended application
•
Create new role in LPD_CUST
•
Add role to end user
•
Testing the extended Application
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
72
Adding Extended Application to Launchpad
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
74
Adding Extended Application to Launchpad LPD_CUST Launchpad Designer
Target Mapping
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Tile
Customer
75
Creating a Semantic Object
Create a Semantic Object Open transaction SPRO. Click on SAP Reference IMG.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
77
Create a Semantic Object Expand ‘SAP Customizing Implementation Guide’ Expand ‘ SAP NetWeaver’ Expand ‘UI Technologies’
Expand ‘SAP NetWeaver User Interface Services’ Execute ‘Define Semantic Objects’
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
78
Create a Semantic Object Click New Entries
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
79
Create a Semantic Object Enter the name of your extended app and a name. Z_NEW_SO Click Save.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
80
Creating Tile for the Extended App
Creating Tile for the Extended App Open the Launchpad Designer. http://:/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main. html?sap-client=001?scope=CUST
Click New Catalog.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
82
Creating Tile for the Extended App Enter a title for your Catalog. Eg “Web IDE Apps Catalogue” Enter an ID for your Catalog. Eg “Z_WEB_IDE_CATALOGUE” Click Save
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
83
Creating Tile for the Extended App Select „Target Mapping” and click on „Create Target Mapping”.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
84
Creating Tile for the Extended App Enter the Name of the semantic object you have just created. ( Z_NEW_SO ) Enter the name of your role (ZEG_ROLE)
Enter ‘TRANSACTIONAL’ as the instance. Enter your application alias. ( ZNEW_ALIAS ) Click Save.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
85
Creating Tile for the Extended App „Target Mapping” has been created
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
86
Creating Tile for the Extended App Select the „Tiles” and click New tile.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
87
Creating Tile for the Extended App Click Static Tile.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
88
Creating Tile for the Extended App Click on the blank static tile to change its properties.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
89
Creating Tile for the Extended App Enter the title you wish to call your tile. Ender a sub title. Select an Icon for your application. Enter the semantic object you have just made. (Z_NEW_SO) Enter your action as approve. Click Save
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
90
Creating Tile for the Extended App Now both the tiles are created that are needed to run your extended application.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
91
Create a new role in LPD_CUST
Create a new role in LPD_CUST Open transaction LPD_CUST. Create a new launchpad Role: ZNEW_ROLE Instance: TRANSACTIONAL Description: as shown Click the green tick to continue
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
93
Create a new role in LPD_CUST Click New Application.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
94
Create a new role in LPD_CUST Enter the Link Text: Extended Approve Purchase Orders Select Application type as : URL Enter the URL as path in SICF to our extended application /sap/bc/ui5_ui5/sap/z_ext_apo
Enter the application Alias as entered in new tile: ZNEW_ALIAS In additional information enter: SAPUI5.Component=ui.s2p.mm.purchorder.approve.MM_P O_APVExtension Click Save and exit this screen.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
95
Adding the extended Application to the Launchpad Note The SAPUI5.Component can be found in the Component.js file in SE80
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
96
Creating a role for your Catalog
Creating a Role for your Catalog Open transaction PFCG. Enter a Role Name. eg “z_web_catalogue_role” Click Create single role.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
98
Creating a Role for your Catalog Enter a Role description. Click Save.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
99
Creating a Role for your Catalog Click the User Tab. Enter each of the User ID’s you wish to allow to use the role, click enter and the role will automatically fill in the other columns for you. Click save at the top of the page.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
100
Creating a Role for your Catalog Click the Menu Tab. Click the transaction drop down list. Select „SAP Fiori Tile Catalog”.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
101
Creating a Role for your Catalog Enter the name of the Catalog ID you just made in the SAP Fiori Admin page. Z_WEB_IDE_CATALOGUE The search function can be used. Click the tick.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
102
Creating a Role for your Catalog The catalog has now been added to your role. Click save
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
103
Add extended App to the Launchpad
Add extended App to the Launchpad Select the Menu button in the top left corner and then select the „Title Catalog”
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
105
Add extended App to the Launchpad Now click the Plus button to add the tile to your home or any other group screen. Once added the “+” symbol changes to a tick.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
106
Add extended App to the Launchpad The Tile has now been added to your home screen click it to test the Fiori application.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
107
Add extended App to the Launchpad As you can see the application has loaded and you are able to see the new label that has been added as the extension.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
108
SAP Fiori Extensibility Further information SAP Fiori – Extensibility on SCN http://scn.sap.com/docs/DOC-53177 Extensibility of SAP Fiori Apps http://scn.sap.com/docs/DOC-52539
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
109
Expert Guided Implementation: Checkpoint Day 4 Day 4 Empowering lesson SAP Fiori extensibility
What has been covered by the SAP Expert in the Empowering session:
SAP Fiori app extensibility
(Web session, 2 h. in the morning)
Execution by customer Customer extends the OData and UI of SAP Fiori APP (Remote support in the afternoon)
What the customer will implement in the Execution session: Goal of the day
SAP Fiori app configuration
SAP Fiori app OData extension SAP Fiori app UI extension
Final Goal Customer enabled to install and customize standard SAP Fiori Applications
© 2012 SAP AG. All rights reserved.
110
Expert Guided Implementation How to get help How to get help
Customer
Email:
[email protected]
SAP Expert
During the execution part you have direct access to the Expert via telephone number to solve questions quickly.
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
Customer
111
Thank You!
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
