HTTP 503 / SAP service
OData service returns 503 Service Unavailable
Client receives HTTP 503 because the SAP web/Gateway/backend service is temporarily unavailable.
Quick answer
- Most likely cause
- ICM/HTTP service or backend application server is unavailable.
- Check first
- SMICM/ICM status and HTTP service availability.
- First resolution step
- Restore the failing infrastructure/component before retrying application calls.
Likely root causes
- ICM/HTTP service or backend application server is unavailable.
- Reverse proxy, Web Dispatcher or load balancer cannot reach the target.
- Planned outage, overload or connectivity failure affects the service.
What to inspect
- SMICM/ICM status and HTTP service availability.
- Web Dispatcher/proxy health and backend reachability.
- SM21 and system monitoring around the failure time.
- Whether all users/services are affected or only one route.
Resolution path
- Restore the failing infrastructure/component before retrying application calls.
- Use platform retry/backoff only for genuinely transient failures.
- Do not treat a persistent 503 as a business-data problem.
- Validate service health from client through backend after recovery.
Share this diagnosis
Paste a credited summary into a ticket, chat or forum reply. Your pasted input is never included.
ERPClimb is an independent platform and is not affiliated with SAP SE.