OData console

The tab at a glance

Open the OData tab in the DevTools panel or the side panel and use the app. Every OData request appears as a row; a $batch expands into its parts. The narrow side panel only hides the time and size columns.

1. Four views of the same log: Requests, Collections, Metadata and Diagram.
2. Pause stops recording, Clear empties the log, Preserve log keeps it across reloads.
3. Filter by path, entity set, status and error text – inside batch parts, too. To the right: status (All, Errors, successful), method and service.
4. A $batch with its number of parts. A click expands it.
5. A batch part: clickable like a request of its own.
6. A failed request: red light, 200 → 400 means “envelope 200, part 400”, the error text below.

Above the table you see whether capture runs from page start, and the measured overhead per request. The Record on … checkbox switches recording off or on for this host; it takes effect from the next page load. The exports are below the table.

Read errors: message, transaction ID, error log

1. Click the red row in the table. For a $batch, the failed part opens.
2. In the details, choose the Error tab.
3. Read message, code, transaction ID and resolution hints. For Gateway errors, Open in Gateway error log leads to /IWFND/ERROR_LOG.

1. Simulate error for this request turns the request into a Fault simulation rule from Pro.
2. Save as known error stores the solution for next time, see Known errors.
3. Message from the error body, with code, target and details below.
4. Transaction ID and timestamp for the search in the backend.
5. Open in Gateway error log: a plain link to /IWFND/ERROR_LOG on the same system, in a new tab (SAP GUI for HTML).

The console understands Gateway V2 as JSON and XML, V4 from RAP and CAP, ICF error pages as HTML and the sap-message and sap-messages headers. A change set that fails as a whole marks all its parts as change set failed; missing answers are marked as no answer.

With from Pro the AI entries sit above the error, such as explaining the error – with your own key, see AI assistant. With from Enterprise the Backend jump card leads to the analysis transactions of the same SAP system, see Backend jump.

Replay: edit, preview, send

1. Select the request in the table and open the Replay tab in the details.
2. Adjust method, URL, headers (one per line, Name: value) and body. Explain headers describes every header.
3. For changing requests, tick Fetch CSRF token first.
4. Click Preview. It shows the exact request including the token fetch: “This request is sent from the page, with the session of the page”.
5. Click Send request. The response appears below, and the request shows in the log marked Replay.

1. The request’s URL – only the page’s origin is allowed.
2. Fetch CSRF token first: a HEAD with x-csrf-token: Fetch to the service beforehand.
3. Preview shows the request that would be sent. No preview, no sending.
4. Save to collection keeps the request for later, see collections.
5. Send request sends it with the page’s session. Reset restores the original.

Export without secrets

Exports are created locally as files and contain neither cookies nor Authorization nor CSRF tokens; the files fetch a token first.

Saved filters and collections

To the left above the table is the Saved filters menu (initially Standard). Save, Save as and Manage store filter sets of status, service, method and text. Make default for this system applies a filter whenever the console opens for this origin.

The Collections view holds saved requests. Before saving, FrontTailor removes cookies, tokens, Authorization and CSRF headers; the URL is stored relative to the service, so the request runs on every system with this service. A saved request runs like a replay: preview first, then send. Import and Export all exchange collections as a JSON file. Filters and collections from team packages appear in a group of their own with from Team, see Team packages.

Metadata: search the service

1. Choose the service – every service whose $metadata was recorded.
2. The summary: OData version, entity sets, entity types, operations, annotations.
3. Search entity sets, types, properties, actions and annotations (including external annotation files).
4. The matches. Controls shows which controls on the page bind an element.

If a service is missing, its $metadata was not recorded: reload the app while recording is on.

Diagram: entities and navigations

1. Search by type, entity set or property (key /). Next to it the neighbourhood (1 or 2 hops), Annotations and Layers (operations, complex & enum types, hide draft).
2. Path finder: choose from and to type, Copy $expand returns the navigation path.
3. Export: SVG or PNG of the current view, or copy a Mermaid erDiagram.
4. Open in full view shows the diagram in a window of its own.

What is recorded

The console hooks into the page’s XMLHttpRequest and fetch, but changes no request and sets no header. It does not even look at UI5 resources such as .js or .properties. Cookies are removed; Authorization, CSRF tokens and other secrets are replaced by [redacted] while still in the page. Per tab, the log holds up to 2,000 requests or 50 MB, bodies up to 512 KB (request) and 1 MB (response). It is deleted when the tab closes and cleared on reload unless Preserve log is on.

Typical problems