How to Configure Custom Fiori App for SAP Transaction Code (On-Premise) on Central Hub

[former_member206749]

Dear Community,

 

While most of the business users are enjoying the SAP Fiori Apps, we have come across a situation, where standard Fiori apps are not available for some transaction codes or reports, or business users are interested to access the custom transactions/reports via Fiori Launchpad.

 

I am writing this blog post to explain how to build custom Fiori apps. I am hoping the detailed steps in this blog will help you to build a custom app for Fiori Launchpad.

 

Activities to be performed in S/4 (Backend) System

 

1. Go to transaction SE93and verify whether the transaction is marked as SAP GUI for HTML

 

2. Launch T-code /UI2/SEMOBJ_SAP

 

Go into change mode, and click on New Entries

Define the Semantic Object, Semantic Object Name and Semantic Object Description of your Own Choice, and choose the Application Component specific to the transaction

Once you save the entries, system will prompt to capture the changes in Workbench Transport Request.

3. Now Launch SPRO, to create Application Descriptors

Path: SPRO → IMG → SAP NetWeaver → UI Technologies → SAP Fiori → Configuring Launchpad Content → Adding Apps to SAP Fiori Launchpad → Prepare Backend Catalogs for Reuse → Mass Maintenance Tool for App Descriptors

It will launch in web, here define Catalog ID and enter the Semantic Object created in previous step:

Click on Continue, as the Catalog ID is newly being created, click on OK to continue in the pop-up message

Click on Insert Button

The System will prompt you to save the changes in a package (create a custom package via SE80 transaction), and mention the Workbench Request that was created in the previous steps.

Now enter the below details:

Semantic Action	Create (or choose based on the nature of transaction, you may choose it from the F4 help options)
App Type	GUI Transaction
Transaction Name	Z-TCode (It could be any transaction for which you are creating the Tile)
Reuse Text	Maintain Check-box (to inherit the transaction text in Title and Tile keywords, if you uncheck then define the Title and Tile Keywords of your own choice)

 

The details will appear as below, where parameters and Tile parameters are optional, then click on Save

 

To test the application, how it looks on HTML, you may click on the Launch button.

 

 

 

Activities to be performed in Fiori (Frontend) System:

 

1. Go to SM30, to maintain the Alias Mapping for the backend Catalog ID (that we created in backend system) in /UI2/V_ALIASCAT

Click on New Entries

Enter the same Catalog ID created in the backend system, then maintain the Alias Name and define the Catalog Title

Once you save the entries, system will prompt you to save the changes in Workbench Request:

2. Now, go to SA38 and run an Extractor Report- /UI2/GET_APP_DESCR_REMOTE_DEV to extract the backend application descriptors and replicate them to the Frontend Technical Catalog:

Mention the Alias and the Custom Catalog ID created in the backend:

As the test run was successful, now run the report removing test mode check:

 

3. Once Extraction is completed, you would be able to find the Catalog in Fiori Designer:

 

 

4. Now copy the Catalog to reference catalog, you may do it just by click on the existing catalog and drag it, you will see the option to create a New Catalog with References, then define the Title and ID:

 

5. Then create a custom group:

Click on + (Add) button:

Then add the Tiles proving the Reference Catalog ID created in the previous step:

 

 

Finally, you have custom Catalog and Group to add it in PFCG Roles.

 

Conclusion

 

There is no stop, we can create the custom apps for our custom transactions and improve user experience with Fiori Apps.

 

I hope you like this blog post and be valuable to our community.

 

[sanjeev-kumar-soni]

Hi Ravi,

Will the above method work if I have ECC backend - EHP8 ( instead of S/4),

with on premise central hub deployment to run Fiori apps.

 

Regards,

Sanjeev

[sanjeev-kumar-soni]

Hi Ravi,

To add to my earlier question, if possible, will the deployed custom app be able to  run on mobile or only form factor desktop will be possible.

Regards,

Sanjeev.

[former_member206749]

Hi Sanjeev,

 

I have not tried with normal ECC in backend, as this is basic configuration I believe it should work, happy to help you if you are facing any issues.

 

To fir the app for mobile/tab screens you will require additional UI configuration, as this configuration enables only HTML view.

Regards,

Ravi Kumar

[former_member337865]

Hi Ravi

 

I have followed all the steps and have created a customized fiori app for SAP standard Transaction UKM_CASE. I have successfully created the Catalogue and the group and i could see the FIORI tile on the Launchpad but when i click on the tile, it takes me to a new page and within a fraction of seconds i get a message saying Transaction UKM_CASE is unknown. Can you please help me on the said error

 

Thanks

Anand

[former_member677117]

1. Launch T-code /UI2/SEMOBJ_SAP. ...


2. Define the Semantic Object, Semantic Object Name and Semantic Object Description of your Own Choice, and choose the Application Component specific to the transaction mcdvoice

[hussain_multhazim]

Hi Ravi,

 

Do we need SAP Web IDE License for this method?

 

Thanks

Hussain

 

[former_member743419]

Your article is very detailed and easy to understand, This is a must for readers who need advanced knowledge like me, thanks!

[former_member683575]

Hi Hussain,

 

This does not require Web IDE license.

 

Regards,

Ravi Kumar

[former_member294387]

Hi Ravi,

 

I am trying to Activate Standard GUI App to FIORI Tile When we try to select the right sematic object and catalog i can see No data found in Mass Maintenance Tool for App Descriptors, But when i check same in Different system in Landscape i can see Default entries for those combination, Can you please let me know how can i get the missed Default entries in Mass Maintenance Tool for App Descriptors for the combination of standard catalog and Sematic Object.

 

 

[former_member206749]

Hi Raghavendra,

 

Validate whether the defined Semantic object is appearing in backend system table - /UI2/V_SEMOBJ, the same value should reflect in 'Mass Maintenance Tool for App Descriptors'.

As per step 3 in backend system activities, Catalog needs to be defined after launching 'Mass Maintenance Tool for App Descriptors'.

 

Please share the screenshots and steps if you are facing different issue.

 

Regards,

Ravi Kumar

[ChristyQ]

Hello Ravi,

I do not have this menu path within my SPRO instance.  We are on S4HANA FSP01.  Are you able to direct me based on a transaction code that would be associated with MASS MAINTENANCE FOR APP DESCRIPTORS.

[former_member795597]

Hi,

 

In my opinion this document is incomplete.

 

Few Comments

 

Where is the option to check how the custom app will look in launchpad?

You need to add Business catalog into a role, does the app created will bring authorization automatically? Not clear

Do we need to add Tcode manually into the role?

I created semantic object for TCODE MCXA

Created the role with Custom App, it did not work, I had to add tcode MCXA manually. Is this the correct approach

 

[former_member774998]

Segui los pasos, igualmente ya cree el rol de negocio para asignar la TRX, en el sistema DEV funcino correctamente, pero al pasar la OT a QAS y probar no carga ¿Algo más hay que hacer?

[former_member834013]

Launch T-code /UI2/SEMOBJ_SAP. ...
Define the Semantic Object, Semantic Object Name and Semantic Object Description of your Own Choice, and choose the Application Component specific to the transaction mcdvoice

 

I'm not able to resolve it? can you please guide me as well?

[krushii]

Dear Ravi Kumar Chikatla,

 

when i am try to follow stem 3 "spro" process, when its redirect on browser then the error comes as shown in image,

 

Also no error found in error log as well as authorization problem

 

 

 

 

[krushii]

facing same issue,

 

I have followed all the steps and have created a customized fiori app for SAP standard Transaction UKM_CASE. I have successfully created the Catalogue and the group and i could see the FIORI tile on the Launchpad but when i click on the tile, it takes me to a new page and within a fraction of seconds i get a error "https redirect to http and http is blocked"

did you got any solution?

[terryvoice]

Configuring a custom Fiori app for an SAP transaction code (on-premise) on a Central Hub involves several steps. Below is a high-level overview of the process. Please note that the specific steps and tools might vary based on your SAP landscape and version. Always refer to the official SAP documentation for your SAP version for the most accurate and up-to-date information.

1. Create Custom Transaction Code:

   • In SAP GUI, create or identify the SAP transaction code that you want to expose through the Fiori Launchpad.

2. Activate OData Services:

   • Ensure that the necessary OData services are activated for the SAP transaction. You may need to activate standard or custom OData services using the SAP Gateway Service Builder (transaction SEGW).

3. Configure SAP Fiori Launchpad:

   • Access the Fiori Launchpad Designer (transaction /UI2/FLP) in the SAP GUI.
   • Create a new catalog and a new group or use existing ones.
   • Add a new tile for your custom app, specifying the necessary details like the target URL and tile type.

4. Configure Target Mapping:

   • Define a target mapping for your custom app. The target mapping specifies how the target system (SAP GUI) is accessed.

5. Create Custom App:

   • Develop a custom Fiori app using SAP Fiori Elements or SAPUI5, depending on your requirements. This app should be able to call the SAP transaction using the OData service.

6. Deploy and Register the App:

   • Deploy your custom Fiori app to the SAP Fiori launchpad system.
   • Register the app in the SAP Fiori Launchpad by creating a corresponding entry in the Fiori Launchpad Designer.

7. Assign Roles and Authorizations:

   • Ensure that the user roles have the necessary authorizations to access the custom Fiori app and execute the associated SAP transaction.

8. Testing:

   • Test the configuration by accessing the Fiori Launchpad and launching the custom app. Verify that it correctly triggers the associated SAP transaction.

9. Troubleshooting and Monitoring:

   • Monitor the SAP Fiori Launchpad and Gateway logs for any errors or issues.
   • Use tools like SAP Fiori Launchpad and Gateway troubleshooting apps to diagnose and troubleshoot problems.

10. Documentation:

    • Document your configuration, including the steps taken, app details, and any custom developments.

It's important to note that the details of these steps might vary based on your SAP version, and you may need to involve your SAP Basis and SAP Fiori development teams for assistance. Always refer to the official SAP documentation and follow best practices for Fiori app development in your specific SAP environment.