Approach to develop & deliver custom Fiori app along with ABAP back-end logic and objects

[former_member478571]

Hello experts,

I guess questions below are very high-lvl and relate to a good practice, but as I couldn't obtain any concrete answers I'm hoping community could help.

As title states, we are developing Fiori app from the scratch along with all (ABAP) back-end functionality - tables, FMs, Gateway OData services etc. At this time, back-end system for ABAP is S/4 on-premise and Fiori app it self should be deployed on both ABAP repository and SAP Fiori Cloud as custom app (if I understood this requirement correctly).

What I'm wondering here is, how should a FIori app with all of it's belonging back-end functionalities, Launchpad configuration be delivered and installed on a potential customer's system. There are a lot of elements in play Fiori app, Launchpad configuration, ABAP objects, Gateway services, is it's even possible for it to be deployed as a single installation or should it be like a separate deployment for Fiori part, separate installation of ABAP dictionary objects etc?

Also, regarding Fiori part, it is relatively complex app with many different functionalities with their own screens. what is the best setup of the app in this case (or SAP's recommendation even?) - many smaller apps (each reflecting single functionality) or create one big app with navigation capabilities? I assume it's the first one..

Many Thanks,

Mijodrag

[gregorw]

Dear Mijodrag,

I would suggest you orient your packaging on the approach that SAP has chosen. Ship the backend part in a separate software component as the frontend part. When it is developed as a product you should also have your registered namespace that you can get via the SAP Service Marketplace. For the deployment to the SAP Fiori Launchpad on the SAP Cloud Portal Service I would suggest that you do an automatic creation of an MTA (one for Neo and one for the Cloud Foundry Environment) using a Continuous Integration Pipeline.

Best regards
Gregor