Quantcast
Channel: SAPUI5 Developer Center
Viewing all articles
Browse latest Browse all 789

Extend a Fiori Application with SAP Web IDE Part 1

$
0
0

In this blog, I will show you how to extend a standard SAP Fiori application (here: Purchase Order Approval)  using a SAP Web IDE. The different possibilities of extending a Fiori app view are shown:

Part 1: hide a control,

Part 2: extend by implementing an extension point & replace a view

Part 3: replace a service

 

 

 

 

 

Start creating a new Extension Project


Start SAP Web IDE from your browser

 

Click on Local folder and start by creating a new extension project (File> New > Extension Project)

01.png

 

From step 1 in the wizard, click Remote..., and select SAPUI5 ABAP Repository to access the remote SAP Gateway system which has the
standard SAP Fiori PO Approval application deployed.

02.png

 

 

In the Select Application from SAPUI5 ABAP Repository dialog, select your SAP Gateway System.

NOTE: Please be aware that the server used in this blog is just an example, thus you may not have granted access to it.

03.png

 

All available applications on you system are shown.

04.png

 

Search for "purchase" to show search and filter capabilities

05.png


Select MM_PO_APV Approve Purchase Orders and click OK.

06.png


You may change the proposed project name to e.g. POApprovalExtended or leave it as proposed by SAP Web IDE ‘MM_PO_APVExtension’ Then click Next.

07.png

 

Click Finish.  An extension project is created in your workspace

08.png

 

If authentication is required, enter User Name and PW for your SAP Gateway system.

 

The application Preview Pane automatically opens in Preview Mode. Once the application is loaded and the data has been fetched from the backend, you can see that the application is fully running.

09.PNG

 

Explore the features of the preview. Display the app in the different screen sizes. When in Small size, change the orientation.

At the end, go back to Large or Medium size.

10.png.


In the application Outline, select the Show property Extensible Elements in the drop down list

11.png


Toggle to Extensibility Mode by clicking Preview Mode down arrow. Notice that the app gets a shadow.
Hover the mouse of the controls in the app. Notice how views are highlighted and the scrolling occurs automatically.

12.png

 

Extend the app by hiding an existing control


In the app, navigate to the view S4 by scrolling down in the detail view until you see the Items table, click on an item.

Note:  You may need to toggle off Extensibility Mode, because in Extensibility Mode you cannot navigate to other views.

13.png


We are going to hide the Pricing Conditions in the view S4.

Make sure you are in Extensibility Mode.

Select the Pricing Condition at the bottom of the view. To highlight the control you need to point the mouse pointer to the right or left side of the table.
Alternatively, you may select in the Outline the PricingCondTable under S4.

14.PNG

 

Select Hide Control in the drop-down of Possible Extensions and click OK to hide it - busy indicator appears, followed by a popup message saying the extension was added successfully.

15.png 


Alternatively, you can right-click on PricingCondTable in the Outline and select Hide Control

16.png


A pop-up window appears to indicate that the control is successfully hidden.  Click Yes to refresh the application.

17.png

 

Navigate to S4 view and show the control was hidden

18.png

 

In Outline section, under Show field, drop down to select Extended Elements.  Now, you can see that under S4 element PricingCondTable is listed as Hidden.

19_1.png

 

Close the Extensibility Pane by clicking on the X on the top right

19.png

 

In the next part I will show you how you can extend an Fiori App by implementing an extension point and how you can replace a view.

 

More Web IDE stuff published by Technology RIG

 

 

See you

Claudi


Viewing all articles
Browse latest Browse all 789

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>