A tour of the UI
The tour shows what is where, so that you know later where to look.
What you see here is a system in operation: Cambira Sanitärtechnik GmbH on Thursday, October 8, 2026, shortly after nine. Nine routes are running, version 7 of the configuration is active, and a draft sits next to it.
The header

The header looks the same on every screen and answers four questions, right where you are:
- Which snapshot is running, which one is being built. Active v7 and Draft v8 · Validated.
- How the system is doing. Here Operational.
- Whether anything is open. The notification icon appears only when there is something to report; its number counts the rows in the Action required block of the overview — here one, the two waiting clarifications.
- Where the help is. The question mark always leads to the page of this documentation that belongs to the screen you are on.
The menu

Ten entries, one overview and three groups. The groups separate what you set up (Configuration), what runs (Operations) and what concerns the system itself.
What you see depends on your rights: the menu shows only the entries you have a permission for. If your menu is shorter than the one shown here, that is why. More on this: Permissions.
Overview

Xchange starts on the overview. It shows the state of all routes at a glance. The picture shows two blocks:
- Action required — what someone has to take care of, here two jobs waiting for clarification. Each row leads to the place where it can be taken care of. If nothing is open, the block disappears, and Nothing to clarify appears at the top right.
- Key figures — jobs, error rate and runtime per job over the last 24 hours, plus the backlog.
Two more blocks are not in the picture. Running now appears between the two only while a run is working. At the very bottom, Operations — last 24 hours shows as a column chart how many jobs there were in each of these hours.
Every field of this screen: Overview.
Configuration
Here you define what Xchange transfers: with which systems, which data and when. Changes are always made in a draft, and it goes into operation only when it is activated.

Configuration Snapshots. The active snapshot, the draft and the archive of earlier snapshots — and the buttons that validate and activate a draft. You come here when you want to put what you built into operation or go back to an earlier snapshot. → Configuration Snapshots
Connections. The systems Xchange talks to — in the example, the webshop, the sister company in Austria and the logistics partner. Here you find the address, the sign-in and the result of the last connection test. You come here before a route can be created, and later when credentials need to be changed. → Connections
Routes. Each route is one transfer — from where, to where, what and when. The list shows all nine; behind it, each route has an editor with several tabs for source data, mapping, automation and, for dispatch routes, dispatch. You come here for everything that concerns the content of a transfer. → Routes
Value Tables. Translation lists for values that have different names in the source and the
target system — in the example, the table "Zahlungsarten Webshop", which turns paypal into PP.
You come here when a value has to be translated for the mapping. → Value Tables
Operations
Here you see what Xchange is transferring and has transferred, and you step in where needed — the same nine routes, but seen from the operations side.

Execution. Per route: its state, open clarifications, when it last ran, when it runs next and whether the automation is switched on. From here, a run is started by hand or cancelled, or a single record is pushed. You come here when something should run now or stop now. → Execution
Clarification. The jobs that got stuck and need a decision — in the example, an order without a customer number and a status message that no dispatch rule matched. You come here when the overview reports a clarification. → Clarification
History. Every single job Xchange has processed, with object, route, status and duration — and behind it, what was received, what was sent and what came back as a response. You come here to prove what happened to a particular record. → History
System
This is about Xchange itself, not about a single integration.

Settings. How long Xchange keeps its own data, e.g. completed jobs and resolved clarification cases, and what the automatic cleanup deleted last. You come here when a retention period no longer fits. → Settings
System Status. Whether Xchange is working and, in case of a halt, what causes it and what to do. Plus license, database, field structure and version details. You come here when the header shows anything other than Operational. → System Status
When a message appears instead of the overview
Sometimes, when you open the tile or in the middle of your work, a full-screen message appears. You will come across five of them in daily work:
| Message | What happened | What you do |
|---|---|---|
| Sign-In Expired | Your SAP Business One sign-in has ended, e.g. because nobody worked in the tile for a long time or you signed out in another tab. As long as you work in the tile, the sign-in stays alive. | Click Reload Page and sign in if the Web Client asks you to. Input you have not saved yet is lost. |
| Xchange Unreachable | The Xchange service is stopped or is restarting, e.g. after an update. | Wait — Xchange retries on its own and shows the overview as soon as the service responds. |
| Connection to Xchange Blocked | The browser loaded the Web Client page from its cache, without the permission through which the tile reaches Xchange. | Reload the page. If the message remains, the cause lies in the setup of the Web Client — contact your administration. |
| Service and UI Do Not Match | The Xchange service and the UI are at different levels, e.g. because only one of them was updated. The message names both versions and says which side is too old. | If the UI is too old, reload the page. If the service is too old or the message remains, contact your representative and give both versions. As soon as both match, Xchange reloads on its own. |
| Session Could Not Be Renewed | The SAP Business One sign-in service was briefly unreachable. This message appears as a window over the screen you are on. | Wait — as soon as the sign-in service responds again, work continues on its own. |
If the message says something else, it tells you itself what to do; usually it refers you to your administration.
What comes next
You know the areas of the app; next, you connect the first system: The first connection.
See also
- The basic model (core concept) — how connection, route and configuration snapshot fit together
- Permissions (core concept) — why your menu can be shorter than the one shown here