跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
效率与协作

odata

Help with OData service development in ABAP including OData V2 and V4 services via RAP service bindings, SEGW-based services, service definitions, service bindings, OData annotations, consumption of external OData services, and troubleshooting common OData errors. Use when users ask about OData, OData V2, OData V4, service binding, service definition, SEGW, OData annotations, OData consumption, OData client proxy, HTTP client, communication arrangement, external API consumption, /IWBEP/ errors, or exposing a RAP BO as OData. Triggers include "create OData service", "expose RAP BO", "service binding", "OData V4", "consume external OData", "OData annotations", "SEGW service", or "OData error".

likweitan · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add likweitan/abap-skills --skill odata

技能说明


name: odata description: Help with OData service development in ABAP including OData V2 and V4 services via RAP service bindings, SEGW-based services, service definitions, service bindings, OData annotations, consumption of external OData services, and troubleshooting common OData errors. Use when users ask about OData, OData V2, OData V4, service binding, service definition, SEGW, OData annotations, OData consumption, OData client proxy, HTTP client, communication arrangement, external API consumption, /IWBEP/ errors, or exposing a RAP BO as OData. Triggers include "create OData service", "expose RAP BO", "service binding", "OData V4", "consume external OData", "OData annotations", "SEGW service", or "OData error".

OData Service Development

Guide for creating and consuming OData services in ABAP, covering both RAP-based (V4/V2) and SEGW-based (V2) approaches.

Workflow

  1. Determine the user's goal:

    • Exposing a RAP BO as an OData service (recommended approach)
    • Creating a classic SEGW-based OData V2 service
    • Consuming an external OData service from ABAP
    • Adding OData annotations for Fiori UIs
    • Troubleshooting OData errors
  2. Identify the approach:

    • RAP-based service (preferred for ABAP Cloud)
    • SEGW-based service (classic, Standard ABAP only)
    • OData consumption (client proxy)
  3. Guide implementation following SAP best practices

RAP-Based OData Services (Recommended)

Architecture Flow

CDS View Entity → Behavior Definition → Service Definition → Service Binding
                                                                    ↓
                                                              OData V4/V2 Endpoint

Service Definition

Exposes CDS entities and their behaviors as a named service:

@EndUserText.label: 'Travel Service'
define service ZUI_TRAVEL_O4 {
  expose ZC_Travel as Travel;
  expose ZC_Booking as Booking;
  expose I_Currency as Currency;
  expose I_Country as Country;
}

Key Rules

  • Expose projection CDS views (C_ prefix by convention), not root views
  • Include value help CDS views (I_* views) the UI needs
  • Alias names become OData entity set names
  • One service definition can be bound to multiple protocols

Service Binding

Binds a service definition to a specific OData protocol and provides a URL:

Binding TypeProtocolUse Case
OData V4 - UIV4SAP Fiori Elements apps
OData V2 - UIV2Legacy Fiori apps, older frontends
OData V4 - Web APIV4API consumption (A2X scenarios)
OData V2 - Web APIV2API consumption (legacy)
InA - UIInAAnalytical scenarios

Creating a Service Binding

  1. In ADT: New → Other ABAP Repository Object → Business Services → Service Binding
  2. Select the service definition
  3. Choose binding type (e.g., OData V4 - UI)
  4. Activate
  5. Click Publish to register the service
  6. Click Preview to open the Fiori Elements preview

OData V4 vs V2

FeatureOData V4OData V2
ProtocolJSON by defaultXML (Atom) default, JSON option
Batch$batch with JSON$batch with multipart
Deep operationsDeep create/update supportedLimited
Actions/FunctionsBound and unboundFunction imports
Filtering$filter with lambda$filter basic
DraftFull supportSupported via extensions
Aggregation$apply transformationNot natively supported
RecommendationPreferred for new developmentMaintain existing only

SEGW-Based OData V2 Services (Classic)

For Standard ABAP only (not available in ABAP Cloud):

Architecture

SEGW Project → Data Model (Entity Types, Sets, Associations)
             → Service Implementation (MPC/DPC classes)
             → Register & Activate in /IWFND/MAINT_SERVICE

Steps

  1. Create project in SEGW transaction
  2. Define data model: Entity types, properties, navigation properties
  3. Generate runtime artifacts (MPC/DPC classes)
  4. Implement DPC extension methods: GET_ENTITYSET, GET_ENTITY, CREATE_ENTITY, etc.
  5. Register service in /IWFND/MAINT_SERVICE
  6. Test via /IWFND/GW_CLIENT or browser

DPC Method Implementation Example

METHOD travelset_get_entityset.
  SELECT * FROM ztravel_tab
    INTO TABLE @DATA(lt_travel)
    UP TO 100 ROWS.

  et_entityset = CORRESPONDING #( lt_travel ).
ENDMETHOD.

Consuming External OData Services

In ABAP Cloud (using HTTP Client and Communication Arrangements)

"1. Get HTTP client via communication arrangement
DATA(lo_dest) = cl_http_destination_provider=>create_by_comm_arrangement(
  comm_scenario  = 'Z_MY_OUTBOUND_SCENARIO'
  service_id     = 'Z_MY_HTTP_SERVICE' ).

DATA(lo_client) = cl_web_http_client_manager=>create_by_http_destination( lo_dest ).

"2. Build request
DATA(lo_request) = lo_client->get_http_request( ).
lo_request->set_uri_path( '/sap/opu/odata4/sap/api_business_partner/srvd_a2x/sap/api_business_partner/0001/A_BusinessPartner?$top=10' ).

"3. Execute and parse response
DATA(lo_response) = lo_client->execute( if_web_http_client=>get ).
DATA(lv_json) = lo_response->get_text( ).
lo_client->close( ).

Using OData Client Proxy (V2/V4)

"Create OData client proxy for V4
DATA(lo_proxy) = /iwbep/cl_cp_client_proxy_fact=>create_v4_remote_proxy(
  iv_service_definition_name = 'Z_MY_ODAT
阅读完整来源 ↗