Quickly Generate and Deploy SAP Fiori Apps from ABAP Development Tools for Eclipse

Estimated read time 8 min read

Last year, SAP Fiori tools added a closer integration with ABAP Development Tools for Eclipse and enabled seamless navigation from ABAP Development Tools for Eclipse to SAP Fiori tools in both SAP Business Application Studio and Visual Studio Code. This enabled you to launch your configured external IDE environment and automatically start the SAP Fiori Application generator directly from the service binding editor in ADT. 

To increase your development productivity even more, this tool integration was now reused for the new Quick Fiori Application generator to create and deploy simple SAP Fiori applications. Like with SAP Fiori Tools in SAP Business Application Studio/Visual Studio Code, you as a developer are now able to generate an application based on SAP Fiori elements annotations and deploy the SAP Fiori UI effortlessly with only few clicks from the service binding editor in ADT. 

Want to know how?

As a developer, create an OData UI Service based on the business object interface or CDS view suitable for UI consumption. OData UI services can be created in ABAP Development Tools for eclipse either manually by creating an OData UI service binding or by utilizing the Generate ABAP Repository Objects wizard. See Creating Service Binding and Generating ABAP Repository Objects.

When creating the OData UI service in ABAP development tools for Eclipse, you must publish the corresponding service binding. For more information, see Using Service Binding Editor for OData V4 Service.

In the service binding editor, select the entity set and choose Create Fiori App… 

 

You now see two creation modes with which you can create SAP Fiori apps and deploy them to SAP BTP ABAP environment. Choose Create SAP Fiori app with Quick Fiori Application generator in ADT and choose Next.

 

Enter the package name and configure the parameter values ensuring the repository name is unique and within 15 characters including namespace. Like in SAP Business Application Studio, the repository name corresponds to the name of the BSP application that gets generated post deployment. 

 

Choose a transport request and choose Finish. The ABAP repository objects will be generated in the background, and you get a popup message once the objects are generated successfully. Choose Open to open or refresh the service binding.

The BSP application and Fiori Launchpad App Descriptor item are generated in the chosen package along with two SICF objects. You now have a basic deployed Fiori app.

In the service binding editor, you now see a clickable Fiori App URL


Note, that the URL won’t work for cloud systems immediately.
To consume services in an SAP Fiori app, you need to complete the following step.

To allow business users to access the Fiori app, you must create an IAM app and link it to a business catalog. After that, your administrator can add your app to SAP Fiori Launchpad.
Important: To make the app visible in the Fiori Launchpad in the end, the Fiori Launchpad App Descriptor Item that was generated after deployment needs to be added to the corresponding field in the IAM App. 


This should automatically populate the OData service under the Services tab: 

That’s it! Easy, right? 

In the project explorer beneath your package, you now see the BSP application, the Launchpad App Descriptor item and the SICF objects along with the IAM app and the business catalog

To summarize, the new Quick Fiori Application generator – available as of SAP BTP ABAP environment 2505 and ABAP development tools for Eclipse client version 3.50 – provides you the ability to quickly generate a productive Fiori app for simple use case (CRUD on tabular data) and configure Fiori Launchpad settings all in one without a tool switch. 

However, the Quick Fiori App generator only supports list report floorplan-based Fiori apps. Besides that, UI development capabilities are limited to backend Fiori elements annotations. For any UI changes, or if you want to delete, redeploy or undeploy the application, you must generate a Fiori project from the deployed application subsequently. As mentioned in the beginning of this blog post, the creation of a Fiori project is also supported via the Create Fiori App… button in the Service Binding editor, from where you then can take over the project to SAP Business Application Studio/Visual Studio Code to perform further actions. Your Quick Fiori app will then be overwritten during deployment. 

We think, the Quick Fiori App generator is a powerful feature that enhances your productivity and enables you as a developer to deliver applications more rapidly and effectively. What do you think of this feature? Let us know in the comments! 

 

​ Last year, SAP Fiori tools added a closer integration with ABAP Development Tools for Eclipse and enabled seamless navigation from ABAP Development Tools for Eclipse to SAP Fiori tools in both SAP Business Application Studio and Visual Studio Code. This enabled you to launch your configured external IDE environment and automatically start the SAP Fiori Application generator directly from the service binding editor in ADT. To increase your development productivity even more, this tool integration was now reused for the new Quick Fiori Application generator to create and deploy simple SAP Fiori applications. Like with SAP Fiori Tools in SAP Business Application Studio/Visual Studio Code, you as a developer are now able to generate an application based on SAP Fiori elements annotations and deploy the SAP Fiori UI effortlessly with only few clicks from the service binding editor in ADT. Want to know how?As a developer, create an OData UI Service based on the business object interface or CDS view suitable for UI consumption. OData UI services can be created in ABAP Development Tools for eclipse either manually by creating an OData UI service binding or by utilizing the Generate ABAP Repository Objects wizard. See Creating Service Binding and Generating ABAP Repository Objects.When creating the OData UI service in ABAP development tools for Eclipse, you must publish the corresponding service binding. For more information, see Using Service Binding Editor for OData V4 Service.In the service binding editor, select the entity set and choose Create Fiori App…  You now see two creation modes with which you can create SAP Fiori apps and deploy them to SAP BTP ABAP environment. Choose Create SAP Fiori app with Quick Fiori Application generator in ADT and choose Next. Enter the package name and configure the parameter values ensuring the repository name is unique and within 15 characters including namespace. Like in SAP Business Application Studio, the repository name corresponds to the name of the BSP application that gets generated post deployment.  Choose a transport request and choose Finish. The ABAP repository objects will be generated in the background, and you get a popup message once the objects are generated successfully. Choose Open to open or refresh the service binding.The BSP application and Fiori Launchpad App Descriptor item are generated in the chosen package along with two SICF objects. You now have a basic deployed Fiori app.In the service binding editor, you now see a clickable Fiori App URL. Note, that the URL won’t work for cloud systems immediately. To consume services in an SAP Fiori app, you need to complete the following step.To allow business users to access the Fiori app, you must create an IAM app and link it to a business catalog. After that, your administrator can add your app to SAP Fiori Launchpad.Important: To make the app visible in the Fiori Launchpad in the end, the Fiori Launchpad App Descriptor Item that was generated after deployment needs to be added to the corresponding field in the IAM App. This should automatically populate the OData service under the Services tab: That’s it! Easy, right? In the project explorer beneath your package, you now see the BSP application, the Launchpad App Descriptor item and the SICF objects along with the IAM app and the business catalog. To summarize, the new Quick Fiori Application generator – available as of SAP BTP ABAP environment 2505 and ABAP development tools for Eclipse client version 3.50 – provides you the ability to quickly generate a productive Fiori app for simple use case (CRUD on tabular data) and configure Fiori Launchpad settings all in one without a tool switch. However, the Quick Fiori App generator only supports list report floorplan-based Fiori apps. Besides that, UI development capabilities are limited to backend Fiori elements annotations. For any UI changes, or if you want to delete, redeploy or undeploy the application, you must generate a Fiori project from the deployed application subsequently. As mentioned in the beginning of this blog post, the creation of a Fiori project is also supported via the Create Fiori App… button in the Service Binding editor, from where you then can take over the project to SAP Business Application Studio/Visual Studio Code to perform further actions. Your Quick Fiori app will then be overwritten during deployment. We think, the Quick Fiori App generator is a powerful feature that enhances your productivity and enables you as a developer to deliver applications more rapidly and effectively. What do you think of this feature? Let us know in the comments!    Read More Application Development and Automation Blog Posts articles 

#SAP

You May Also Like

More From Author