# SAP Gateway OData Service Activation and Transport Checklist > Source: https://netray.co/tools/sap-gateway-odata-service-activation-transport-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Step by step checks to activate, test and transport an OData service on SAP Gateway, embedded or hub, V2 or V4. ## Category sap ## Erp SAP NetWeaver / Basis ## Audience - SAP Basis administrator - ABAP developer - SAP Fiori developer ## Tool **Kind:** checklist **Groups:** #### 1. Prerequisites **Items:** **Text:** Gateway is activated: SPRO > SAP NetWeaver > SAP Gateway > OData Channel > Configuration > Activate or Deactivate SAP Gateway (this fixes the 'SAP Gateway has been deactivated' error) **Critical:** true Deployment type is known: embedded (Gateway and backend in one system) or hub (separate front-end server) **Text:** System alias defined in SPRO > SAP Gateway > OData Channel > Configuration > Connection Settings > SAP Gateway to SAP System > Manage SAP System Aliases **Critical:** true For hub: RFC destination to the backend in SM59 tested (trusted RFC where single sign on is required) ICF node /sap/opu/odata (and /sap/opu/odata4 for V4) active in SICF Developer or admin role includes the Gateway admin transactions; end user roles will need S_SERVICE for the service #### 2. Activation **Items:** **Text:** OData V2: /IWFND/MAINT_SERVICE > Add Service, enter the system alias, find the technical service name and version **Critical:** true **Text:** Choose the package: $TMP for a local test only, or a transportable package so the registration is recorded in a request **Critical:** true Confirm the ICF node for the service is created and active after registration Assign the system alias to the service in the Service Catalog (alias list at the bottom of /IWFND/MAINT_SERVICE) OData V4: publish the service group in /IWFND/V4_ADMIN and assign the system alias to the group Check the backend registration in /IWBEP/REG_SERVICE if the service does not appear in the Add Service list #### 3. Testing **Items:** **Text:** In /IWFND/GW_CLIENT run GET .../$metadata and confirm HTTP 200 **Critical:** true GET an entity set with $top=5 and $format=json to check data and authorizations For POST, PUT or DELETE first send GET with header x-csrf-token: Fetch, then reuse the returned token **Text:** Read errors in /IWFND/ERROR_LOG (front end) and /IWBEP/ERROR_LOG (backend) **Critical:** true After a model change, clear metadata caches with /IWFND/CACHE_CLEANUP on the front end and /IWBEP/CACHE_CLEANUP on the backend Test with a real end user, not a developer user with SAP_ALL #### 4. Transport **Items:** **Text:** SEGW project (R3TR IWPR) and generated MPC, DPC and _EXT classes are in a workbench request **Critical:** true Backend model and service registration objects (R3TR IWMO, R3TR IWSV) are in the same request **Text:** Front end registration from /IWFND/MAINT_SERVICE recorded as R3TR IWSG and R3TR IWOM, plus the ICF node as R3TR SICF **Critical:** true System aliases are maintained per system (they are client specific customizing and point to different backends), so plan to set them in QA and production PFCG roles with the S_SERVICE entries are transported separately and profiles generated in the target Import order: backend objects before front end registration; clear caches in the target after import #### 5. Go-live **Items:** **Text:** Payload traces in /IWFND/TRACES switched off for the service and users **Critical:** true Error log monitoring assigned to someone, with a clean up job for old log entries Authorization tested for each business role with test users Response time checked for the largest entity set with realistic $filter and paging Service documented: technical name, version, system alias, request numbers **Scoring Note:** Menu paths are for SAP Gateway Foundation on NetWeaver 7.50 and ABAP Platform; wording can differ slightly by release. Object types listed are those Gateway records on registration; check your request in SE09 after activation. ## Content **Intro:** This checklist covers the full life of an OData service on SAP Gateway: switching Gateway on, defining the system alias, registering the service, testing it in the Gateway client and moving it through the landscape. It works for embedded and hub deployments and covers both V2 and V4 registration. **Sections:** #### How to use it **Body:** Run group 1 once per system, then groups 2 to 4 per service. The order matters: a service will not show in Add Service if the system alias or backend registration is missing, and a test fails with misleading errors if the ICF node is inactive. When something fails, the two error logs are the fastest diagnosis: /IWFND/ERROR_LOG on the Gateway side and /IWBEP/ERROR_LOG on the backend side. Export the list per service so the transport and go-live checks are signed off with the request numbers. #### Where this lives in the system **Body:** /IWFND/MAINT_SERVICE is the service catalog for V2 services: it registers the service, creates the ICF node and holds the system alias assignment. V4 services are managed as service groups in /IWFND/V4_ADMIN. SEGW is the Gateway Service Builder where the model and runtime classes are generated. /IWFND/GW_CLIENT is the built in HTTP client for testing, and the cache cleanup transactions remove stale metadata after a model change, which is the usual reason a new field is missing in the response. **Bullets:** - Embedded: system alias usually LOCAL. - Hub: alias points to the backend RFC destination. - V4: publish service group, not individual service. #### Transport gotchas **Body:** If the service was registered in $TMP in development, nothing about the registration reaches QA; you must register again with a transportable package or register manually in each system. Many teams register services manually in each system on purpose, because the system alias differs. Either way, the SEGW project and classes are ordinary workbench objects. After import, an outdated metadata cache in the target is the most common cause of 'it worked in DEV'. Roles are separate: a transported service without S_SERVICE in the user's role returns a 403. #### How to check the result **Body:** Open the request in SE09 after activation and confirm the R3TR IWSG, IWOM and SICF entries are there. In QA, call $metadata in /IWFND/GW_CLIENT as a test user, then read the entity set. If the response is 'No service found for namespace', the registration or ICF node is missing; if it is an authorization error, check S_SERVICE in SU53 for the user. **Cta:** If you want a private AI assistant that reads your SAP data through governed OData services on your own servers, we can design the service layer with you. **Faq:** #### How do I fix 'SAP Gateway has been deactivated'? **Answer:** Activate Gateway in SPRO under SAP NetWeaver > SAP Gateway > OData Channel > Configuration > Activate or Deactivate SAP Gateway, then choose Activate. It is a one time switch per system. Retest the service in /IWFND/GW_CLIENT afterwards. #### How do I transport an OData service in SAP? **Answer:** Put the SEGW project and its classes in a workbench request, and register the service in /IWFND/MAINT_SERVICE with a transportable package so the IWSG, IWOM and SICF objects are recorded. Maintain the system alias in each target system, transport the roles, and clear the metadata caches after import. #### How do I test an OData service in SAP Gateway? **Answer:** Use /IWFND/GW_CLIENT, or the SAP Gateway Client button in /IWFND/MAINT_SERVICE. Start with $metadata, then GET an entity set with $top. For writes, fetch a CSRF token with a GET first. Errors are logged in /IWFND/ERROR_LOG and /IWBEP/ERROR_LOG. #### Is the system alias transported? **Answer:** Treat it as per system configuration. The alias points to a backend and RFC destination that differ between DEV, QA and production, so most landscapes maintain it locally in each system and only transport the service registration and development objects. ## Search terms how to activate odata services in sap, how to transport odata service in sap, transport sap gateway odata service system alias, sap gateway has been deactivated in odata, how to test odata service in sap gateway, sap gateway activate odata service, iwfnd maint_service --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json