If we have a look at the add-on/software component structure of SAP Gateway as of SAP NetWeaver 740, it turns out that the total number of add-ons/software components that are mandatory and thus not uninstallable has been reduced to two add-ons, while up to six add-ons are now uninstallable.

 

In addition to the uninstallable add-ons mentioned above, the SAP NetWeaver 7.40–specific add-on IW_FNDGC can be uninstalled as well.

 

Please note that IW_PGW is used for SAP Fiori applications such as MyInbox, and is included in software component SAP_GWFND as of 7.51.

 

 

In releases prior to 7.40, while the SAP Gateway server or hub functionality required that software components GW_CORE and IW_FND were deployed on the server system, the SAP Gateway back-end enablement functionality required that the software component IW_BEP was deployed.

 

As of SAP NetWeaver 7.40, it is not necessary to decide where to put the SAP Gateway core components. This is because component SAP_GWFND is installed as standard with 7.40 and includes the functional scope of IW_BEP, GW_CORE, and IW_FND, along with IW_HDB. Therefore, every system running on top of SAP NetWeaver 7.40 can act as a gateway server for the SAP Gateway back end. This means the deployment options no longer depend on the deployment of the add-ons.

 

New Add-On Structure in 7.40

With SAP NetWeaver 7.40, the functionality of SAP Gateway 2.0 is part of the SAP Basis. The main functionality of the four SAP Gateway 2.0 add-ons—IW_BEP, GW_CORE, IW_FND, and IW_HDB—became part of the software component SAP_GWFND.

 

Some legacy functionality (which we do not recommend) has been moved to a separate add-on, IW_FNDGC, which can still be deployed on top of 7.40 for backward compatibility, but has to be uninstalled if the system is to be migrated to SAP S/4HANA.

 

 

SAP Gateway 2.0 SP to NetWeaver 7.40 Mapping

 

The figure outlines which SP level on 7.40 is equivalent to which SP level of SAP Gateway 2.0 running on a release prior to 7.4. This table is maintained at SAP Note 1942072. Since SAP Gateway is shipped with 7.40 as part of the basis, the shipment is bound to the delivery of basis SPs in 7.40. This means that the number of the SP that contains the same functionality in SAP Gateway 2.0 and SAP NetWeaver 7.40 differs.

 

For example, if you want to use an SAP Gateway hub running on top of SAP NetWeaver 7.40 SP8 and you are using an SAP back end running on top of SAP NetWeaver 7.31, your SAP Gateway 2.0 add-ons should have SP level SP9.

 

SAP Gateway Components since SAP NetWeaver Application Server for ABAP 7.51

As of SAP NetWeaver AS 7.51 the add-on structure becomes even simpler. This is because the add-on IW_PGW that is used for SAP Fiori applications such as the My Inbox, is now included in the software component SAP_GWFND.In addition, most of the legacy SAP Gateway add-ons IW_SCS 200, IW_CNT 200, IW_CBS 200, and IW_SPI 100 are not supported for SAP S/4HANA.

 

This leaves us to two remaining addons that are supported for SAP S/4HANA:

• IW_FNDGC
  
• IW_GIL 100

 

 

SAP Gateway 2.0 SP to NetWeaver 7.51 Mapping

Starting with SAP NetWeaver 7.52 SP01 it has been decided to down port the following structure packages and their sub-packages of the SAP Gateway Foundation framework to SAP NetWeaver 7.51:

• /IWFND/FRAMEWORK
• /IWBEP/FRAMEWORK
• /IWCOR/TD_CSI

 

This includes the latest development for the SAP Gateway foundation framework for OData version 4 (V4) as well as for OData version 2 (V2). It does however not include the components of the Notification Channel.

Please note that

1. in certain use-cases there might be slight variations in the functionality.
2. not all functionalities have been down-ported (see list of down-ported software packages above).

As a result, the above-mentioned sub-packages of the SAP Gateway framework in SAP NetWeaver 7.52 SP01 are equivalent to their counterparts in the SAP Gateway framework in SAP NetWeaver 7.51 SP05 and SAP NetWeaver 7.50 SP11.