Comparing Different Approaches

The different tools cover different use cases, and they vary in the way they create OData services.

Use Cases

Target group Use case Suggested tool
ABAP Developer I want to implement an OData service via a SADL mapping. The SADL mapping allows projection of required elements and following associations. Gateway Service Builder using the mapping editor
ABAP Developer I want to expose one or more specific CDS views, associations, actions to OData service. Gateway Service Builder using referenced data sources
ABAP Developer I want to expose one specific CDS view to OData as a canonical OData service. CDS in ABAP Development Tools - Eclipse
UI Developer I want to create a new OData service without any additional backend tooling based on s to be used for SAP UI5 application. SAP Web IDE plugin

Features

Feature SEGW: Mapping editor SEGW: Referenced data source ABAP Development Tools (Eclipse-based IDE)
Supported SADL models CDS views, DIDC tables and views CDS views CDS views
Support of associations and multiple entities (support of complex transactions)

Yes

(0…1; 0...N with additional filter)

Yes Yes (first level associations and composition)
Support of actions Manual mapping and modeling Yes Yes
Support of CDS view parameters Manual mapping and modeling Yes Yes
CDS annotations considered No Yes – derived at runtime Yes – derived at runtime
Value helps Manual mapping and modeling Yes Yes
Text associations Manual mapping and modeling Yes Yes
Mapping (properties and navigation properties) to SADL model Manual mapping and modeling Not necessary – mapping derived at runtime Not necessary – mapping derived at runtime
Support of read (single entities), query (entity sets), and write operations read, query, and write read and query, write for draft infrastructure

read and query,

write for draft infrastructure
Create several OData services based on one SADL model possible Yes Yes No, only 1:1
Change of SADL model supported No, changes of SADL model might invalidate the service runtime Yes – automatically reflected at runtime Yes – automatically reflected at runtime
Change of OData model supported Yes No – 1:1 exposure of SADL model No – 1:1 exposure of SADL model
Field extensibility Yes - derived from extensibility exit in DPC_EXT and MPC_EXT Yes - since OData metadata is dynamically derived from the SADL model Yes - since OData metadata is dynamically derived from the SADL model
Own code exits Yes - in class DPC_EXT and MPC_EXT Yes - in class DPC_EXT and MPC_EXT No