Troubleshooting
The workbench usually says itself what is wrong. Here are the most common messages and what helps.
- Messages
- in plain words, with cause
- Gateway
- diagnosis from the error message
- Help
- in person via the contact form
The service won’t load
| Message | What helps |
|---|---|
| The system asks for a sign-in. | Choose Sign in in a tab, sign in, then Load again. With SAML or SSO, opening the Fiori app once in the same browser is often enough. |
| Without access to …, ODataTailor cannot load the service. | The browser’s question about access was declined. Load again and agree. |
| Access denied (403). | Your user may not read the service – in SAP systems usually a missing role. Cross-check with the Fiori app. |
| There is no service at this address (404). | Check the URL. For SAP Gateway the workbench names the cause: service not active (/IWFND/MAINT_SERVICE), no system alias or ICF node inactive (SICF). |
| The answer is not $metadata. | Usually a sign-in page came back. Sign in and load again – or give the $metadata URL directly. |
| The system reports an error (500). | An error in the backend. For Gateway, the Way out names the transaction for the error log and the transaction ID. |
No access to the system? Opening the $metadata as a file always works – see Opening a service.
Changing doesn’t work
- “Blocked: … is a production system.” – The system is marked Production in the “Systems” dialog or listed in IT’s policy. That is on purpose. If it is not a production system, turn the switch off; if it says “company policy”, IT decides.
- “The session has expired.” – Sign in in a tab, then send again.
- 412 Precondition Failed – The ETag no longer fits; someone has changed the record in the meantime. Load ETag and send again.
- Draft cannot be created – Someone else holds the record. Drafts and locks shows who.
The capture stays empty
- DevTools must be open before the app makes its requests. Open the panel, then reload the page.
- If it says “Paused” at the top, click Record.
- The panel recognises OData by URL and answer. If the app goes through a proxy of its own with a different format, nothing appears.
- If a service lacks “$metadata captured”, the app loads its metadata from the cache. Reload with an empty cache (in DevTools: right-click on reload).
Report a bug
If none of this helps, write to us via the contact form: browser and version, ODataTailor version, what you wanted to do and which message appeared. Please send no credentials, tokens or customer data. We answer in person.
See also
- Help from people Report a bug
- Docs Opening a service
- Docs Changing, draft and $batch
- Docs Capture
- Sources Opening1 · Errors2 · PROD lock3