odata

Expose ABAP business objects as OData services via RAP and SEGW.

49|15|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/likweitan/abap-skills --skill odata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odata
Source: https://github.com/likweitan/abap-skills/tree/main/skills/odata
Command: npx skills add https://github.com/likweitan/abap-skills --skill odata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ABAP developers need a clear, end-to-end guide to exposing ABAP business logic as OData services, including RAP-based (V4 and V2) and SEGW-based approaches, service bindings, and annotations.

Core Features & Use Cases

  • OData service development using RAP (V4/V2) and classic SEGW (V2)
  • Define service bindings, apply OData annotations, and consume external OData sources
  • Troubleshoot common OData errors and integration scenarios

Quick Start

Define a new OData service using RAP or SEGW workflows and bind it to an OData endpoint, then validate with a simple UI or API client.

Frequently Asked Questions about odata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I expose ABAP business objects as OData services?

To expose ABAP business objects as OData services, you define service definitions and apply CDS annotations using RAP-based OData V4 and V2 or classic SEGW-based V2 workflows. You then bind these definitions to an OData endpoint for UI and API consumption.

What is the difference between RAP and SEGW for OData service development?

RAP supports modern OData V4 and V2 service development using CDS annotations and service definitions, while classic SEGW supports traditional OData V2 service creation. Both approaches allow you to define service bindings and expose ABAP logic to UI or API workflows.

Can I consume external OData services using an ABAP HTTP client?

Yes, you can consume external OData sources using OData client proxies and ABAP HTTP client usage. This allows your ABAP environment to integrate external OData service workflows seamlessly without needing to build native RAP or SEGW services.

Why is my ABAP OData service binding not returning data?

Troubleshooting OData service binding errors involves validating your CDS annotations, checking service definitions, and ensuring proper RAP or SEGW configurations. Common OData errors often stem from incorrect service binding setups or missing behavior definitions in the ABAP backend.

Do I need CDS annotations to build an OData V4 service in ABAP?

Yes, CDS annotations are essential for building RAP-based OData V4 services in ABAP. They define the service semantics, UI presentation, and behavior, which are then exposed through service definitions and bindings to create the final OData endpoint.