Show TOC

SAP Gateway Service BuilderLocate this document in the navigation structure

SAP Gateway Service Builder (transaction SEGW) is a design-time environment, which provides developers an easy-to-use set of tools for creating services. The Code-based OData Channel consumes it and supports developers throughout the development life cycle of a service.

If your system has SAP Gateway Service Builder 7.40 or higher version, system must have the core component SAP_GWFND installed as standard and must include the functional scope of IW_BEP.

For more information about deployment options and scenarios, see .

SAP Gateway

Service Builder caters need of both experienced and less experienced developers for exposing the data for an easy consumption, using a variety of platforms, frameworks, and devices, in a single transaction. While experienced developers have maximum flexibility to define a new service and integrate their own source code, less experienced developers can reduce the time and effort involved in creating services by importing existing definition files and implementing content generators.

Service Builder provides an OData-compliant modeling environment for creation and maintenance of OData services without any need for programming. Service Builder visualizes all the development artifacts that developers need to create a service including:

  • SAP Gateway runtime artifacts such as model provider class (MPC), data provider class (DPC) model, annotation provider class (APC) and service
  • OData artifacts such as entity set, entity type, and properties
Project-Based Service Development
Service Builder introduces a new service development concept, which is organized around projects. Projects are used to store all the artifacts that developers need, to create a service and model together in one place. As projects consolidate all related data, developers can easily work on multiple projects in parallel and reuse the data between projects before generating and activating the actual service. Consequently, projects provide developers the freedom to interrupt the service development and modeling process at any time, without obliging to runtime artifacts and risk of losing data. Organizing service development and modeling process in projects has the advantage that entire project data can be transported easily between the systems for maximum efficiency and reuse.