FAB Installation and Upgrade Packages
This section explains the SAP-related activities that require attention for Fiori App Builder setup.
Please note that for the installation packages:
FE refers to Front end server
BE refers to Back end server
Installation Packages
The FAB Product is deployed in the development packages /IQX/FAB, /IQX/FAB_COMMON, /IQX/FAB_NON_GW, /IQX/FAB_APP_GEN, /IQX/FAB_INTERACTIVE (only available for SAP NW 7.4 and above). Regardless of the selected deployment option as described in section 1 (see above), FAB is always delivered in targeted packages for the Backend or Frontend servers.
The deployment of the FAB environment (development package /IQX/FAB) consists of:
BE Installation Package contains all of the Backend objects in the /IQX/FAB package.
For 740 and higher
ECC_740_K-YYYCOINIQX.SAR where YYY = FAB VersionFor 7.02 to 7.31
ECC_702_K-YYYOIINIQX.SAR where YYY = FAB Version
FE Installation Package contains all of the Front end objects in the /IQX/FAB package.
For SAP NetWeaver 7.40 and higher
GW_ 740_K-YYYCOINIQX.SAR where YYY = FAB VersionFor SAP NetWeaver 7.02 to 7.31
GW_702_K-YYYOIINIQX.SAR where YYY = FAB Version
Upgrade Packages
The upgrade packages consist of the same development packages as the Installation but for upgrading from older FAB version to the latest version.
The upgrade deployment consists of:
BE Installation Package contains all of the Backend objects in the /IQX/FAB package.
For 740 and higher
ECC_740_K-YYYCHINIQX.SAR where YYY = FAB VersionFor 7.02 to 7.31
ECC_702_K-YYYOUINIQX.SAR where YYY = FAB Version
FE Installation Package contains all of the Front end objects in the /IQX/FAB package.
For SAP NetWeaver 7.40 and higher
GW_ 740_K-YYYCHINIQX.SAR where YYY = FAB VersionFor SAP NetWeaver 7.02 to 7.31
GW_702_K-YYYOUINIQX.SAR where YYY = FAB Version
Patch Packages
The patch packages contain objects that have been modified specifically for the patch release. However, they cannot be installed on its own. Customers must first install the base installation or upgrade packages before incorporating these file changes. Patch installation can be carried out through the SPAM transaction.
The patch files can be separated by:
BE Patch File for Backend objects modified in the /IQX/FAB package.
K-YYYB1INIQX.SAR where YYY = FAB VersionFE Patch File for Front end objects modified in the /IQX/FAB package.
K-YYYF1INIQX.SAR where YYY = FAB Version
Customization Transports
Following the SAINT Installation/Upgrade procedure, the following transports, customizing ones, should be imported into both Front-end and Backend environment:
This list only contains the customization transports for the latest FAB release version 3.3.2.
Transport | Description |
---|---|
IQPK900866 | Client independent config - FAB v3.3.2 |
IQPK900867 | Client-dependent config - FAB v3.3.2 |
IQPK900849 | Sample applications definition - FAB v3.3.0 |
IQPK900863 | IQX_MY_FORMS ver.10 - 202401 |
IQPK900868 | IQX - OneList Adapter v3.3.2 - Configuration |
Customer Specific Development Object
It is recommended that a new package is created for customer-specific FAB development. This will be required when the FAB provided superclass is extended (inherited).
We recommend naming this class ZFAB for consistency. Please set up your own custom package for FAB extensions in both the Front end and back end SAP systems. This package will hold your custom extensions and development to support the Apps that you develop using FAB.
The package will also hold any additional gateway services that you may require for your custom app development.