𝗦𝗔𝗣 𝗔𝗕𝗔𝗣 𝗼𝗻 𝗛𝗔𝗡𝗔 | 𝗦𝗘𝗚𝗪 𝘃𝘀 𝗦𝗜𝗖𝗙 — 𝗪𝗵𝘆 𝗱𝗼 𝘄𝗲 𝗻𝗲𝗲𝗱 𝗯𝗼𝘁𝗵?

Ruhani Garg

3 min read

·

Sep 22, 2026

--

Listen

Share

A common question among SAP Gateway developers is:

“If we already create our OData service in SEGW, why do we need SICF?”

The simple answer is:

SEGW helps us build the OData service, while SICF provides the HTTP infrastructure through which the request reaches the Gateway runtime.

Let’s understand this with a simple example :

1. SEGW — Where we BUILD the OData Service

SEGW (Service Builder) is the development environment used to create our OData service.

In SEGW, we typically:

1. Create the OData project
2. Define Entity Types
3. Define Entity Sets
4. Define properties and relationships
5. Generate Runtime Objects
6. Implement business logic in the DPC extension class

For example, suppose we create: ZEMPLOYEE_SRV

with an Entity Set: EmployeeSet

We may implement methods such as:

GET_ENTITYSET
GET_ENTITY
CREATE_ENTITY
UPDATE_ENTITY
DELETE_ENTITY

So, think of SEGW as the place where we BUILD the service.

2. /IWFND/MAINT_SERVICE — Where we REGISTER the Service