You can schedule a cleanup job to periodically clean up application state records that have not been accessed for a long time.
The SAP Fiori launchpad uses application states to shorten long URLs and to enable users to navigate back in the browser history.
An application state is described by a list of parameters that define a specific point in an application to which a user has navigated. For example, these parameters may include filter values or application URL parameters.
The list of parameters defining an application state is stored on the front-end server, together with a unique key. To address an application state, the launchpad includes this unique key in the URL that is displayed in the browser's address bar. This makes it possible to have short URLs that reference huge numbers of parameters containing huge numbers of characters.
If a link containing an application state is shared or bookmarked, it can only be restored if the application state is still available on the server.
To avoid that too much storage space is consumed, you should regularly clean up application states using the program Cleanup Layered Repository Files (transaction /UIF/CLEAN_LREP). Since the last access and the total number of accesses are monitored, you can use these criteria to clean up application states which have never been restored or which have not been restored for a long time, for example within the last year.
You create a background job to run the cleanup program periodically on the front-end server. For more information, see Customizing for SAP NetWeaver, and choose
.A list with the application state records that were deleted is shown.
A summary can be found in the Application Log: Display Logs (transaction SLG1) using object /UI2/BE (UI2 Backend Enablement: Application log).