Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

OData is a standard for reading and changing data through an API. Versions 2 and 4 have different conventions, so clients must use the service’s actual protocol version.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

An API lets one program use another program’s data or operations. OData defines conventions for doing this over HTTP, including reading entities and sending supported updates.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for OData V2 versus V4 in SAP: Confirm the protocol before reusing client code
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

General OData V2 versus V4.0-style JSON/query semantics with explicitly scoped SAP SuccessFactors and SAPUI5 client examples. Actual provider capabilities and UI5 release determine support.

Primary documentation reviewed on 14 November 2026 using readable full text and official indexed excerpts. Official indexed SAP/OData/OASIS excerpts reviewed; V4 JSON collection/navigation sections opened as readable full text. No provider endpoint, migration or update was executed. Examples use V4.0 conventions and do not imply support for every later revision.

A MANUFACTURING EXAMPLE

Reuse a plant integration against the correct protocol

Match the client to the protocol

Service A: OData V2. Service B: OData V4. Business entity: Orders. Client behavior: Use matching conventions
What to notice: The same entity name does not make V2 and V4 request and response conventions interchangeable.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Service A
OData V2
Service B
OData V4
Business entity
Orders
Client behavior
Use matching conventions

A REAL SCREEN TO RECOGNIZE

An SAP workshop service-binding editor in ABAP Development Tools. The binding type identifies the exposed service protocol. This example is OData V4; it is not a screenshot of a V2 service.

An SAP workshop service-binding editor in ABAP Development Tools. The binding type identifies the exposed service protocol. This example is OData V4; it is not a screenshot of a V2 service.

View the original SAP example ↗ · License

© 2025 SAP SE or an SAP affiliate company and abap-platform-rap110 contributors. Apache-2.0 (repository REUSE annotation). Reproduced unchanged for educational commentary. This is a source example, not a capture of your system.
Words you’ll meet in this guide
HTTP
The request-and-response protocol used by web services.
Entity
A business-data type or record exposed by a service.
Status code
A numeric summary of an HTTP response.
RAP
ABAP RESTful Application Programming Model: a way to build business objects and services.
OData
A standard for reading and updating data through a web API.
API
A defined interface through which programs exchange data or request actions.
ETag
A resource-version identifier used in checks that can prevent overwriting a concurrent change.
CSRF
Cross-Site Request Forgery. A CSRF token helps a service reject unwanted cross-site write requests.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Service metadata → Protocol version → Compatible client request. Conceptual diagram for OData V2 versus V4 in SAP: Confirm the protocol before reusing client code.
Apply the idea: A manufacturer connects an operational client to an SAP OData service and needs to distinguish V2 and V4 behavior.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Reuse a plant integration against the correct protocol

    A manufacturer connects an operational client to an SAP OData service and needs to distinguish V2 and V4 behavior.

  2. Treat V2 and V4 as different service contracts

    OData V2 and V4 share the idea of typed entities exposed through HTTP, but their payloads, query conventions, type systems and client programming models are not interchangeable.

  3. Scope the comparison and avoid product-specific generalizations

    The original SAP source compares SuccessFactors APIs.

  4. Worked case: three Orders, two returned in the first page

    A fictional old V2 service and replacement V4 service both expose O100, O200 and O300.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.