In our previous article on SAP Fiori, we learned how to configure and implement two standard Fiori Apps. By now we are confident that you understand the jargons like Hub System and Embedded System. We also believe that you can differentiate between the front end UI Service and backend OData Service.
Today, we would present you just three flow charts. These are teasers to raise your curiosity to learn more about the enhancement of SAP standard Fiori App. In our next article, we would explain the detailed step by step to enhance the Fiori frontend and backend.
In every Fiori enhancement projects, you would have one or all of the below three requirements.
- Hide existing screen elements or add new screen elements in the frontend UI screen.
- To meet requirement 1 above, we need to add more fields in the Entity Type of the backend OData service.
- Make the UI Project point to newly enhanced backend OData service which has additional fields and logic.
Business Requirement: Enhance the standard Approve Timesheets Fiori App.
- Add a new column with header text called Ext Source (External Source) and its item column as a check box.
- If the user id of the user who creates the time starts with Ext then mark this column as ‘X’, else leave it blank. ‘X’ means time created from an External system.
- Remove the Reject button. Business do not want to reject from the frontend.
The above three enhancement of the Fiori App is a genuine business requirement of a real client.
Go to SAP Fiori Library to get the details about Approve Timesheets App.
Flow Chart 1:
If the frontend UI screen needs to show additional fields on the screen which already exist in the OData Entity Type, then we do NOT need to enhance the backend OData Service. Most of the video tutorials show how to display/hide elements in frontend assuming all fields/properties would always be there in OData Entity Type. But more often than not, you would need to add additional custom fields in the OData Entity Type and make them visible in the frontend UI. In such scenarios, we need to enhance the standard OData service and put the additional properties.
Flow Chart 2:
If there is a need to make any single change in the standard frontend UI, we need to enhance/extend the standard project. For our tutorial, we would do the enhancement using SAP WebIDE (not eclipse). Standard extension points are provided by SAP (just like enhancement spot/badi/exit) which can be used for doing the modification as shown in the flow chart below.
Flow Chart 3:
If you have made the change in the backend OData, then it is imperative that you would want to consume the enhanced OData rather than the standard OData from the frontend. In flow chart 2, we just enhanced the UI part. Nowhere did we change the setting to make the UI pull data using new OData service. Please follow the below quick steps to make the let your UI project know which OData to use going forward and replace the old standard OData service with the new redefined OData Service.
I am sure, it might not have been 100 percent clear as to how the business requirement can be met. The idea was to give you the high-level overview of the steps. At least after going through the above 3 flow charts, you know that there are three things to be done. When I first started learning, I was not aware of flow chart 3 and always wondered how would I make the UI point to the new OData. We have written this post to build up the environment for our next post where we would present in front of you the whole buffet.
Please stay tuned. We have pledged to make ourself Fiori ready and also make you Fiori ready. Together we can learn and grow.
If you GENUINELY like our articles then it would be a HUGE help if you shared, subscribed and liked us on facebook. It might seem insignificant, but it helps more than you might think.
Check Step by Step Tutorials on SAP Fiori
- SAP Fiori Tutorial. Part I. System Check, Installation and Configuration
- SAP Fiori Tutorial. Part II. End to End Implementation of Fiori App
- SAP Fiori Tutorial. Part III. Flow Chart to Enhance Standard SAP Fiori App
- SAP Fiori Tutorial. Part IV. How to change non-English Default Language in Fiori Launch Pad?
Also, check HANA-ABAP Tutorials
- ABAP on SAP HANA. Part I. First Program in ABAP HANA
- ABAP on SAP HANA. Part II. ADT Eclipse and HANA Studio
- ABAP on SAP HANA. Part III. Debugging in ADT
- ABAP on SAP HANA. Part IV. Core Data Services
- ABAP on SAP HANA. Part V. Deep Dive into CDS Views
- ABAP on SAP HANA. Part VI. New Age Open SQL ABAP 740
- ABAP on SAP HANA. Part VII. SQL Script and SAP HANA Stored Procedure
- ABAP on SAP HANA. Part VIII. ADBC – ABAP DataBase Connectivity
- ABAP on SAP HANA. Part IX. AMDP – ABAP Managed Database Procedure
- ABAP on SAP HANA. Part X. AMDP with SELECT OPTIONS
- ABAP on SAP HANA. Part XI. Are Native SQL and Open SQL Competitors?
- ABAP on SAP HANA. Part XII. Open SQL, CDS or AMDP, which Code to Data Technique to use?
- ABAP on SAP HANA. Part XIII. Sample Functional Specification of HANA Project
- ABAP on SAP HANA: Part XIV. HANA Ready, HANA-tization & HANA Plus
- ABAP on SAP HANA: Part XV. Expose CDS Views as OData Service through Annotation
- ABAP on SAP HANA: Part XVI. HANAtization
- ABAP on SAP HANA: Part XVII. ATC – ABAP Test Cockpit Setup & Exemption Process
- SAP ABAP on HANA: Part XVIII. SALV IDA (Integrated Data Access)
We have a very active Telegram SAP Technical Group. Please join it using below link.
Telegram SAP Technical Discuss Group.
WhatsApp had the limitation of 256 members per group and we were finding a hard time syncing and maintaining information in multiple WhatsApp group. Therefore we have moved to Telegram as it can accommodate more than 10,000 users. Please join.