5 transaction codes every SAPUI5 developer should know

Aside from development, a SAPUI5 developer must know the how to and where to configure SAPUI5 applications. It is a necessary skill to setup and validate the application on client and server side.
And, here are the 5 transaction codes that every SAPUI5 developer should know.

1. ICM

SAP Fiori - Cache Management
SAP Fiori – Cache Management

Transaction:
SMICM

Go to Menu, Go to -> HTTP Plug-in -> Server Cache -> Invalidate Globally

Description:
This transaction clears up the front-end server cache. It is recommended to execute this transaction on every newly deployed SAPUI5 application to the Gateway Server. This assures that the server will return the latest copy of the application.

2. SICF

SICF
SICF

Transaction:
SICF

Description:
SAPUI5 developers usually used SICF to activate and check if the application is deployed successfully to the Gateway Server. You have the capability to test the services here as well. Also, URLs can be configured to have short aliases in this transaction.

3. /IWFND/MAINT_SERVICE

MAINT_SERVICE
MAINT_SERVICE

Transaction:
/IWFND/MAINT_SERVICE

Description:
MAINT_SERVICE is usually used to activate and connect remote services to the Gateway Server. Also, MAINT_SERVICE shows the health status of a service, if the service is active and connecting properly to target system. You also have the access from here to test the service via Gateway Client.

LPD_CUST

LPD_CUST
LPD_CUST

Transaction:
LPD_CUST

Description:
In this transaction, developers can setup the tiles and configure the correct mapping to the target service. This is an alternative way to configure the tiles, aside from the launchpad Fiori Admin configuration panel.

/UI2/SEMOBJ

SEMOBJ
SEMOBJ

Transaction:
/UI2/SEMOBJ

Description:

SEMOBJ is used to map the correct actions/intents to a correct application URL. In here you configure different actions for the application, passing required or optional parameters for run time access.

Honorable mentions:

Below are some of the few transaction codes, you might be interested in:

    • SEGW – Gateway service development
    • PFCG – Role management
    • SE80 – ABAP development and repository browsing
    • SU01 – Transport management
    • /IWFND/CACHE_CLEANUP – Additional service cache, especially for OData
    • /IWFND/ERROR_LOG – Gateway error debugging.

The transaction listed above are just some of the mostly used transaction code for SAPUI5, and there are a lot that you might need. In addition, some of the transactions above can be transported to another system so no need for manual replication. As SAP continuously streamlining the process of deployment, more and more tools are coming up to make it easier for developers to deploy SAPUI5 and Fiori application to customers.

Let me know if there are transaction codes that should make it the list. Leave a comment below and subscribe!

Share this...
Share on Facebook1Tweet about this on TwitterShare on LinkedIn0Email this to someonePrint this page

Leave a Reply