Ansicht
Dokumentation

/SDF/FIORI_ANALYSIS - Analysis of FIORI Services

/SDF/FIORI_ANALYSIS - Analysis of FIORI Services

BAL Application Log Documentation   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

The report collects data concerning UI5 (Fiori) applications, verifies if the most relevant application files are available, checks if the application related services are active, and displays the information. For that the report collects the UI5 applications from the BSP repository. The relevant data are retrieved from the application files. The files which are scanned for these data are Configuration.js, Component.js, index.html, manifest.json and Application.js.

BSP apps, their names and attributes (like creation and change information) are read from tables O2APPLT and O2PAGDIR. Only UI5 applications are displayed. A BSP app is considered as an UI5 app if:

  • the app includes the Component.js file
  • the file index.html contains ‘sap-ui-core.js’.

Description of Fields

  • App Validation: yellow if Component.js and Metadata are both green; green if also ODATA service is active
  • Application Name: Technical name of the UI5 application. You can use that name to open the (BSP) application in SE80
  • PACKAGE / IN_TRANSPORT: Indication whether the app is a local object or correctly assigned to a package and transported. Read from tables TADIR and E071.
  • Software Component / Release: Software component and release of the app read from TADIR.
  • Application Hirarchy Component (ACH): the apps are like all other development objects assigned to an application. The applications are organized in a tree structure (ACH).
  • ICF Service Active / ODATA Service Active: Traffic light indicators whether the ICF service of the UI5 application is active or not. For the ODATA service, a red light is only displayed in case the service can be found in table /IWFND/I_MED_SRH.
  • ID / Name space: The namespace can be found in the Component.js file
  • Current Version: App version in the Component.js file
  • Index.html: the app includes an (existing) file Index.html
  • Component.js: the app includes a file Component.js
  • Component-preload.js: the app includes a file Component-preload.js
  • Metadata: data regarding the OData metadata in the Component.js file exist. METADATA AS FILE indicates data are found in a file manifest.json. The metadata traffic light summarizes both:
  • green if METADATA and METADATA AS FILE are both true.

  • yellow if only the flag METADATA is true.

  • red if both flags are false.

  • OData URL: Displays the OData Service path as in SICF. Collected from the content of the application files like Configuration.js, Applications.js, Component.js, index.html and manifest.json.
  • System Alias(es): System alias which is a name for an RFC connection.
  • FIORI ID: the ID in the FIORI app library.
  • FIORI Name: the app name as defined in the language independent configuration file (typically identical to the english app name).
  • HTTP Response Code: Shows the HTTP response code of the OData call if tested. Min. UI5 version: Displays the minimum SAPUI5 version specified in the manifest.json file
  • Dependencies: the SAPUI5 sub libraries used by the application. This inf can be found in the files index.html, Component.js, or manifest.json
  • # .js Files: JS files in the application which are not one of the following: Component-preload.js, Configuration.js, Component.js or Application.js
  • # .xml Files: XML files in the application
  • # .css Files: CSS files in the application
  • Vendor: “Customer” or “SAP”

Prerequisites

Features

Selection

The processing can be limited to a particular app by specifying its name in the corresponding input field. The option to check a single app must be checked.

By default the option to skip some non-FIORI apps is checked. In the text field, the filter criteria for skipping specific apps can be specified as follows: You can define filters on arbitrary columns of the result table. Supply the column name followed by the seperator '@' and a regular expression. If the regular expression is found in the column, this row of the result table is deleted. Further pairs of '@@' can be appended. The search is done ignoring case in a string variable, allowing to use '$' for the end of line.

All the filter criteria are applied after processing the apps (this means they are analyzed and afterwards removed from the output). Only for the app name as filter criterion it is possible to filter before processing (all other columns are only known after the analysis). There is a special convention for this: with the the (artificial) column name APP, the filter is performed on column APPL_NAME before processing. APP can be specified several times in the format '@APP@'.

The language in which the short text describing the apps is read, is determined according to the following priority:

  • - the language specified on the entry screen
  • - english
  • - any language in which the text exits

If the check box 'Text ODATA Service(s)' is marked, a HTTP test call is performed against this service and the result is displayed in column 'HTTP Reponse'. The test call is only valid for services called locally, i.e. invalid for services configured to be executed on a target system.

You can use the service maintenance transaction /IWFND/MAINT_SERVICE for a test call for any service: in the transaction select the service with a double click. In the lower left box the button 'SAP Gateway Client' opens transaction /IWFND/GW_CLIENT with the URL pre-configured. With 'Execute', a test call is performed.

Standard Variants

Output

Activities

  • Related information is found in metering tables /IWFND/L_MET_DAT and /IWFND/L_MET_COL.
  • Utilization data is found in the workload monitor transaction ST03.
  • With the application name more details can be seen in transaction SE80 (choose BSP Application).
  • Transaction /IWFND/GW_CLIENT is suitable to get details related to the response code.
  • Transaction /IWFND/MAINT_SERVICE allows to check the activation of ODATA services and to jump to /IWFND/GW_CLIENT for a test call.
  • Transaction SICF shows service details.
  • Transaction /IWFND/ROUTING shows the ALIASes defined.

Example






TXBHW - Original Tax Base Amount in Local Currency   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 7659 Date: 20240328 Time: 141952     sap01-206 ( 110 ms )