If you do not want to make changes (for example, implement new application coding) in your SAP Business Suite system and remote interfaces exist in the SAP Business Suite system that fulfill your requirements, you can install the relevant SAP Gateway components and develop SAP Gateway content in an SAP Gateway hub system. This is referred to as hub deployment.
If the SAP Gateway hub system in which you want to develop content is based on:
SAP NetWeaver 7.02, 7.03, or 7.31, you need to install the component IW_BEP .
SAP NetWeaver 7.40 or higher, the SAP Gateway core component SAP_GWFND is installed as standard (includes the same functional scope as IW_BEP) and no further installation is required.
Before deciding whether or not hub deployment is the most appropriate development setup for you, consider the following aspects that affect system performance in a remote setup:
Number of round-trips to exchange data between the systems.
Volume of data which needs to be transferred between the systems.
Function scope you want to utilize in a particular system.
In a system landscape with hub deployment, communication between systems is handled by system aliases (RFC destinations). If the remote interface fits your use case and permits the exchange of metadata such as filtering, paging, searching or sorting statements then a development approach with a hub deployment might be the most ideal solution. It is best suited if data can be accessed with a low number of round-trips between the SAP Gateway system and the SAP Business Suite system.
To facilitate communication, the IMG activity Manage SAP System Aliases has been extended to include the field For Local App (For Local Application).
You can find the configuration activities for developing content on the OData Channel with an IW_BEP installation in the SAP Implementation Guide (IMG). In your SAP Gateway hub system, start transaction SPRO open the SAP Reference IMG and navigate to .