/IWFND/MAINT_SERVICE

/IWFND/MAINT_SERVICE, titled "Activate and Maintain Services" and also reachable in SPRO under the SAP Gateway OData Channel settings, manages every OData V2 service registered on the SAP Gateway system. In one screen it:

• registers a backend service on the Gateway system under an external name;
• assigns one or more system aliases that route requests to the implementing backend;
• shows and activates the service's ICF node;
• removes services and their aliases;
• jumps to the SAP Gateway Client, the browser and the error log for a selected service.

/IWFND/MAINT_SERVICE is the switch that turns an implemented OData V2 service into one an SAP Fiori app can actually call.

To activate Alder Manufacturing's custom service ZALDER_SUPPLIER_SRV:

1. Start /IWFND/MAINT_SERVICE and choose Add Service.
2. Enter the backend's system alias (LOCAL in an embedded deployment) and optionally the technical service name, then retrieve the services.
3. Select the service and add it. Enter a package for transport, or a local package for a test.
4. Back on the main screen, select the service and confirm that the ICF node shows a green status; activate it if not.
5. Check the system alias assignment.
6. Test with SAP Gateway Client or the browser call of the service document.
7. Grant start authorization: add the service to the user's PFCG role as a TADIR service (R3TR IWSG, service name plus version suffix) so that S_SERVICE is filled.

Each step stays visible afterwards, so /IWFND/MAINT_SERVICE is the first stop when a service seems missing.

Use /IWFND/MAINT_SERVICE for:

• custom OData V2 services from SEGW projects or CDS views published as V2;
• single SAP-delivered services that a mass activation skipped;
• fixing system aliases and ICF nodes of existing services.

Use something else for:

• OData V4 service groups: /IWFND/V4_ADMIN.
• Many SAP Fiori apps at once: task lists run with STC01 activate a business role's apps and services: SAP_FIORI_CONTENT_ACTIVATION for SAP template roles and SAP_FIORI_FCM_CONTENT_ACTIVATION for customer roles, as named in the SAP S/4HANA 2025 documentation.
• RAP service bindings: publishing the service binding in ABAP Development Tools activates its local service endpoint; the registration details depend on the release and the OData version.

Choosing the right tool by OData version and volume keeps /IWFND/MAINT_SERVICE for targeted fixes rather than bulk work.

Most /IWFND/MAINT_SERVICE problems are registration, alias or authorization gaps, not defects in the service code.

• /IWFND/V4_ADMIN: publishes and manages OData V4 service groups.
• /IWFND/GW_CLIENT: sends and replays requests against the service.
• /IWFND/ERROR_LOG: shows runtime errors after activation.
• SICF: maintains ICF nodes directly, for example the shared V4 node.
• PFCG: adds the service to roles, so users receive the S_SERVICE start authorization.
• SEGW: opens the Service Builder project behind a custom V2 service.
• /IWFND/CACHE_CLEANUP and /IWBEP/CACHE_CLEANUP: clear hub and backend metadata caches.

/IWFND/MAINT_SERVICE activates the service; these transactions prove that it actually works.