CapabilityProtocols & APIsStandard ABAP, read from its artifacts

OData

In ABAP the OData service is built inside the system that holds the data: modelled in the SAP Gateway Service Builder, implemented as ABAP classes, and registered on the Gateway before a client can call it.

Showing artifacts, examples and content with confirmed Standard ABAP applicability. View All ABAP

Overview

SAP SHIPS

No SAP artifact is confirmed here for Standard ABAP.

A Standard ABAP coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS
launchpad-kpi

Ships one generic OData service, Z2UI5_PROXY_KPI_SRV, whose $count on ENTITYCollection creates the ABAP class named in the CLASS filter and returns the value its count method gives back.

open-steamgate

Serves classic code-based SEGW services from a local runtime: the URL parser, $filter mapped to SELECT-OPTIONS, $batch with changesets, navigation, $expand, deep insert, function imports, value helps, MERGE and media entities, all of it ABAP behind one if_http_extension.

A Standard ABAP coverage assessment has not been written. View all flavors

Artifacts4

4 of 4 artifacts
ArtifactSignals
Apps1
open-steamgateLocal ABAP server serving /IWBEP/ OData v2 without an SAP system
Signals
Functional boundary
Build tools1
@root3287/cap-segwCompiler from a CDS service to SEGW model and data provider classes
Signals
Functional boundary
Packages2
launchpad-kpiPuts a number from an abap2UI5 app on a Fiori launchpad tile
Signals
Functional boundary
open-abap-odataOData and Gateway shims serving SEGW-style services on Node.js
Signals
none

Details

Coverage
statecommunity only, ABAP, Standard ABAP, derived
also inCAP
Comparison properties1

These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.

Protocols
For your agent