IQX Add-On Installation

FAB is a certified SAP Add-on that is packaged using the SAP Add-On Assembly Kit (AAK). The FAB add-on consists of a series of transport requests grouped together as a delivery package. When imported, the FAB add-on is registered as an additional software component in the system. Instead of sending transport requests to customers, new features and bug fixes are installed in the SAP system as a package. The transaction SAINT (SAP Add-On Installation Tool) is used in a fresh installation of the FAB add-on or for a major version upgrade. On the other hand, the transaction SPAM (Support Package Manager) is used to install minor updates in support packages (patch). The following steps are relevant for a fresh FAB Add-On installation or when upgrading an existing FAB Add-On to the latest version.

Package Installation

Installation Packages will be provided by IQX depending on the deployment method and version of the SAP system. It will be labeled as either Frontend or Backend.

Central Hub Deployment

In SAP Backend, install the package for Backend using transaction SAINT in Client 000
In SAP Frontend Gateway, install the package for Frontend using transaction SAINT in Client 000

Embedded Deployment

This option is only applicable for SAP versions 7.40 or higher

Install the package for Backend using transaction SAINT in Client 000

When disassembling the OCS Packages, you may encounter the warning message that says The OCS Package is not digitally signed.

This message is expected as the signature is automatically turned on when using SAINT version 66 with SAPNOTE 2520826.

Installation Steps via SAINT/SPAM transaction

Fresh Installation Excluding Any Patch Release

Login to client 000, go to transaction SAINT
Load Installation Packages

Decompress file as necessary.

Once package is uploaded, click on START to begin the installation process.

Select the installable IQX component and click on CONTINUE.

Choose on Target Support Package if available. Click on CONTINUE to proceed.

CONTINUE on Calculated installation queue.

Confirm on processing mode.

Wait while SAP is in progress installing.

Once Add-On was successfully imported, you may click on LOGS to display transport messages or FINISH to proceed on SAINT Runtime Analysis.

View Runtime Analysis

Fresh Installation Including a Patch Release

Login to client 000, go to transaction SAINT.
Load Installation Packages. We need to include two (2) different files:
1. Base installation file with pattern ECC_VVV_K-YYYCOINIQX.SAR where VVV is the minimum SAP version required and YYY is the FAB version release.
2. Patch installation file with pattern K-YYYB1INIQX.SAR where YYY is the FAB version release.

Please note that filenames and the number of patch files may vary based on your deployment option and patch version. For example, FAB version 3.3.1 includes only one (1) patch file, FAB version 3.3.2 includes two (2) patch files, and so on.

*Customers may also opt to upload the files in their EPS Inbox. In this case, packages must be loaded from their application server.

Decompress files as necessary. Repeat this process for both the base installation package and the patch package.

Once packages are uploaded, click on START to begin the installation process.

Select the installable IQX component and click on CONTINUE.

Choose on Target Support Package if available. Click on CONTINUE to proceed.

CONTINUE on Calculated installation queue.

Confirm on modification adjustment added by the patch package. Then, click on CONTINUE.

Confirm on processing mode.

Wait while SAP is in progress installing.

Please note that these warnings are to be expected. Click on IGNORE button at the top part.

Once Add-On was successfully imported, you may click on LOGS to display transport messages or FINISH to proceed on SAINT Runtime Analysis.

View Runtime Analysis

Upgrade Installation Including a Patch Release

The steps required for an upgrade installation with a patch release are identical to those for a fresh installation, including a patch release, except for the files to be uploaded. Please follow the steps outlined for a Fresh Installation Including a Patch Release but utilize the file packages listed below.

Upgrade installation file with pattern ECC_VVV_K-YYYCHINIQX.SAR where VVV is the minimum SAP version required and YYY is the FAB version release.
Patch installation file with pattern K-YYYB1INIQX.SAR where YYY is the FAB version release.

Please note that filenames and the number of patch files may vary based on your deployment option and patch version. For example, FAB version 3.3.1 includes only one (1) patch file, FAB version 3.3.2 includes two (2) patch files, and so on.

Patch Installation for Customers on latest major FAB release version (3.3.2)

Patch packages cannot be installed independently unless you are on the latest major release, FAB v3.3.0, or higher. If you are not on this version, follow the steps for Fresh or Upgrade Installation Including Patch Release above.

Login to client 000, go to transaction SPAM.
Load Patch installation file with pattern K-YYYB1INIQX.SAR where YYY is the FAB version release.

Please note that filenames and the number of patch files may vary based on your deployment option and patch version. For example, FAB version 3.3.1 includes only one (1) patch file, FAB version 3.3.2 includes two (2) patch files, and so on.

*Customers may also opt to upload the files in their EPS Inbox. In this case, packages must be loaded from their application server.

Decompress file as necessary.

Choose the Component that is to be upgraded. Choose the Highest level that is available in the Queue.

Choose Support Package-> Import Queue from Menu. Choose to execute in background.
Confirm the Queue by choosing the Menu Support package->Confirm Queue.
Once Add-On patch was successfully imported, you may verify it in the installed software components in SPAM.

Post-installation steps

Import Table Contents

The Transport Requests for the FAB Sample Applications and the Table Contents are packaged in 3 additional ZIP files. In some scenarios, extra customizing transports are needed for related FAB functionalities. These objects are required for the FAB Workbench configuration and layout and should be imported using the Transport Management System (Transaction STMS) in all active SAP Clients where FAB is being used for development and testing which may include Development, Testing, Sandbox, Quality, and Productive clients.

This list only contains the customization transports for the latest FAB release version 3.3.2.

Transport	Description	Objects
IQPK900866	Client independent config - FAB v3.3.2	Table Contents /IQX/FAB_LIC_CFG /IQX/FAB_WB_CFGA /IQX/FAB_WB_CFGB /IQX/FAB_WB_CFGC /IQX/FAB_WB_CFGD /IQX/FAB_WB_CFGE /IQX/FAB_WB_CFGF /IQX/FAB_WB_CFGG /IQX/FAB_WB_CFGH /IQX/FAB_WB_X4A /IQX/FAB_WB_X4A2 /IQX/FAB_WB_X4B /IQX/FAB_WB_X4C /IQX/FAB_WB_X4D /IQX/FAB_WB_X4E /IQX/FAB_WB_X6A /IQX/FAB_WB_X6A2 /IQX/FAB_WB_X6B /IQX/FAB_WB_X6B2 /IQX/FAB_WB_X6E /IQX/FAB_WB_X6E2 BAPIF4T
IQPK900867	Client dependent config - FAB v3.3.2	View Cluster Maintenance: Data /IQX/FAB_CONFIG_TABLES Table Contents /IQX/ACT_STATUS /IQX/FAB_WF /IQX/FORMS_CFG_I /IQX/FORMS_WIDG /IQX/FORM_ENTIT /IQX/FORM_ESCAL /IQX/FORM_RECOR /IQX/OL_INT_ACT /IQX/STATUS_ACT /IQX/WIDGETHD /IQX/WIDGET_WF /IQX/WIDG_DATA TDDAT TVDIR Customizing: Table Contents LT_VARIANT View Maintenance SWFDVEVTY2 V_BRG_54
IQPK900849	Sample applications definition - FAB v3.3.0	Table Contents /IQX/ACT_STATUS /IQX/FAB_SCRIPT /IQX/FAB_WF /IQX/FAB_XML /IQX/FORMHD /IQX/FORMS_CFG_I /IQX/FORMS_DATA /IQX/FORMS_ELEM /IQX/FORM_ENTITY /IQX/FORM_ESCAL /IQX/FORM_RECORD /IQX/STATUS_ACT
IQPK900863	IQX_MY_FORMS ver.10 - 202401	Dynamic IQX My Forms application Standalone IQX My Forms aaplication
IQPK900868	IQX - OneList Adapter v3.3.2 - Configuration	Report Program Application Variant Report /IQX/ONELIST_SCHEDULER, variant NO_OPS_JOB Report /IQX/ONELIST_SCHEDULER, variant WITH_OPS_JOB View Cluster Maintenance: Data /IQX/OL_CONFIG Table Contents /IQX/OL_INT_ACT View Maintenance: Data /IQX/V_ACT_CAT V_BRG_54

For S4HANA deployment, please apply transport S4HK901471 to adjust changes for S4HANA.

Index Calculation

The SAPUI5 application index provides an indexing and caching mechanism for information related to apps, components, and libraries in the SAPUI5 ABAP repository and related to components and libraries in the SAPUI5 distribution layer. The index is calculated by the report Calculation of SAPUI5 Application Index for SAPUI5 Repositories (/UI5/APP_INDEX_CALCULATE). The report /UI5/APP_INDEX_CALCULATE has to be executed in the system where the FAB service is running whenever the content of the SAPUI5 ABAP repository has been changed.

Failure to execute this step may result in the browser console showing a message such as ‘REQUESTED RESOURCE OUTDATED’.

Step 1

Go to transaction SE38 and Execute the report /UI5/APP_INDEX_CALCULATE.

Step 2

Go to the Single SAPUI5 Repository Only tab and enter each of the following SAPUI5 Repository, then click Execute.

/IQX/FAB2 Fiori App Builder V2

/IQX/FAB_ICONS FAB Icon Picker

/IQX/PROCESS_EDIT IQX FAB Process Editor _{*use for older versions of FAB below version 3.3.1}

/IQX/PROCESS_EDIT2 IQX FAB Process Editor 2 _{*only available for FAB 3.3.1 and higher}

/IQX/JSON_EDIT JSON Editor

/IQX/MY_FORMS My Forms for Fiori Launchpad

Once the installation is finished, the OData metadata, model cache need clearing. In addition, the UI5 application index also needs recalculating. Please follow the instruction of clearing cache at the following link: How to Refresh Cache on Gateway and ECC.