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 SAINT in Client 000
In SAP Frontend Gateway, install the package for Frontend using SAINT in Client 000
Embedded Deployment
This option is only applicable for SAP versions 7.40 or higher
Install the package for Backend using SAINT in Client 000
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. 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.
Transport | Description | Objects |
|---|---|---|
IQPK900724 | Client independent config - FAB v.3.2.0 | Table Contents
|
IQPK900725 | Client dependent config - FAB v.3.2.0 | View Cluster Maintenance: Data
Table Contents
Customizing: Table Contents
View Maintenance
|
IQPK900726 | Client dependent config - OneList v.3.2.0 | Table Contents
|
IQPK900727 | FAB v3.2.0 - Sample applications definition | Table Contents
|
Import Transport Patch for Older SAP Versions
For older SAP versions 7.02 to 7.31, a transport patch should be imported using the Transport Management System (Transaction STMS) to fix the compatibility issues with class /IQX/CL_FAB_MPC.
Transport | Description | Objects |
|---|---|---|
TSTK900053 | FAB_SRV - MPC adjustment for NW prior to 7.40 - v3.2.0 | Class /IQX/CL_FAB_MPC Method (ABAP Objects) DEFINE_ADMINROLEFORM Class /IQX/CL_FORMS_ASSIST Method (ABAP Objects) |
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 /IQX/JSON_EDIT JSON Editor /IQX/MY_FORMS My Forms for Fiori Launchpad |
Post-Installation Configuration and Validation
Perform the following configurations in the order below to completely set up the FAB add-on.
5. Additional Configuration for Older SAP Systems ( < 7.40 )
6. Post Installation Validation
7. Troubleshooting Configuration