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.
...
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
...
Install the package for Backend using transaction SAINT in Client 000
Note |
---|
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 transaction
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
...
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 |
---|---|---|
IQPK900847 | Client independent config - FAB v3.3.0 | Table Contents
|
IQPK900848 | Client dependent config - FAB v3.3.0 | View Cluster Maintenance: Data
Table Contents
Customizing: Table Contents
View Maintenance
|
IQPK900849 | Sample applications definition - FAB v3.3.0 | Table Contents
|
IQPK900851 | IQX_MY_FORMS ver.10 - 202307 | Dynamic IQX My Forms application |
IQPK900852 | IQX - OneList Adapter v3.3.0 - Configuration | Table Contents
|
For S4HANA deployment, please apply transport S4HK901471 to adjust changes for S4HANA.
...
Info |
---|
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
...