Service Processing Mode in ODATA Service



This is the default processing mode. The SAP Gateway system uses the routing configuration for this service and passes the OData request using RFC to one or more remote backend systems (several backend systems are available in case of Multiple Origin Composition) or using a direct call to the local system (RFC bypassing).

By now, the RFC bypassing implementation saves the RFC and network overhead but is not optimized for data transfer and for database accesses in the local system.

Co-deployed only:

The optimization for service processing in a co-deployed system is realized for a fast data transfer between the SAP Gateway system and the IW_BEP component on the local system. Using this processing mode, the routing configuration is not used and the OData request is directly passed to the IW_BEP component.

As the routing information is not used for the processing mode “Co-deployed only”, no additional system aliases can be assigned to this service using transaction /IWFND/MAINT_SERVICE.

When some more system aliases are added to a service using a transport, they are ignored during the service processing at runtime. In this case, the /IWFND/MAINT_SERVICE transaction displays a popup to inform the administrators and require either to change the processing mode back to “Routing-based” or to remove the needless system aliases.


In the service composition, you can set the inherited service to this processing mode to indicate that the service is used by another service. A service with inherited processing mode cannot have any system alias and therefore contains no routing information. It uses the routing information of the caller service instead.


Choose the processing mode ‘Co-Deployed only’ to improve the service processing performance if this service is registered and published in a co-deployed system only.

You May Also Like

Leave a Reply?