Skip to main content

Settings

Settings is the screen that shows how much Xchange processes at the same time, how long Xchange keeps its own data — and what the run that deletes it did last. Why Xchange deletes at all and what stays in the process is described under Retention and reset.

Everything on this screen concerns Xchange itself; the target systems stay untouched. What is deleted here are records that Xchange created.

Permissions​

The screen follows the System permission:

Level on SystemWhat you can do
NoneThe menu item is missing.
Read onlySee all information; the fields are locked.
FullChange parallel processing and the periods.

In the example: M. Brandt has Full and maintains the periods. A. Vogt has no permission on System; for A. Vogt the menu item is missing. What the permissions mean otherwise is described under Permissions.

The Settings screen: parallel processing at the top, below it the five retention periods and the automatic cleanup with the log of the last run.

Layout​

AreaContent
Parallel processinghow many operations Xchange runs at the same time
Retention periodsfive fields in days, above them the warning banner when needed
Automatic cleanupnext and last run, below them the deletion log
Bar at the bottom edgewhether and when the screen last saved

Parallel processing​

One field: Max. concurrent operations — how many calls to target systems Xchange runs at the same time at most, across all routes together. Default: 8.

A batch call counts as one. When a route sends several records in one call, that call takes one place, not one per record.

Routes take turns. When operations of several routes are waiting, Xchange serves them in rotation, so one large route does not crowd out the others. Runs of the types Targeted and Cleanup go before the waiting operations — you start a targeted run with Transfer individually or Reprocess.

A higher value is not automatically faster. Every call to SAP Business One needs a session with the Service Layer. The field therefore shows the Max. Service Layer sessions setting from the Service Hub as a guide: if the limit here is higher, the extra operations wait for a free session.

The field is required and takes a whole number from 1 to 512. For other values it reports Required, Whole numbers only or Value must be between 1 and 512 — and the previous value stays saved. A valid value applies from the next processing pass, without a restart.

Retention periods​

Five fields, each in days. Each field names the state that its period covers — a running record stays, no matter how old it is.

FieldWhat is deleted after expiryDefault
Settled eventsrows of the event queue that have been processed30
Completed operationscompleted jobs and the synchronization runs they belong to90
Resolved clarification casesresolved clarification cases and the permanently failed jobs behind them90
Usage recordsthe record from which billing is answered395
System logthe entries of the system logempty

Two of the five periods each cover two things, and the label names the first one in each case: Completed operations includes the synchronization runs, Resolved clarification cases the failed jobs.

The 395 days of Usage records cover a full billing year. Keep this period at least that long: a deleted record is gone for good.

A number outside the limits suspends the area

A period below 1 or above 36,500 days is saved, and the cleanup run then skips the area entirely — the period that applied before no longer takes effect either. Always fix this finding.

An empty field​

An empty field means: records of this kind are never deleted until someone enters a number. The field then shows never deleted in grey.

System log is the only field that stays empty at setup.

Invalid input​

Each field takes a whole number from 1 to 36,500. While you type, the field stays quiet; a finding appears as soon as you leave the field or press Enter.

MessageWhat is saved
Whole numbers onlythe last valid value — the input exists only on the screen
Value must be between 1 and 36500the input, together with its finding; the area rests as long as it is there

The warning banner when shortening​

Above the fields a banner appears as soon as an entered period is shorter than the previous one:

Shortened periods — older records are deleted on the next cleanup:

Below it there is one row per shortened period with the field name, the old and the new value. The old value reads never deleted when the field was empty before or held a number outside the limits — in both cases nothing had been deleted there so far.

The old value is the state with which you opened the screen, not the last saved one. If you set Completed operations from 90 to 60 and then to 30, the banner names 90 as the old value. If you enter 90 again, the row disappears.

The banner is purely a notice: the change is saved as soon as you have left the field. Deletion nevertheless happens only on the next cleanup run — until then it is enough to raise the value again.

How saving works​

Both field areas save on their own, without a button. An input is saved as soon as you leave the field or press Enter. A changed setting applies immediately and without activation, because it is outside the configuration.

Ctrl+Z undoes the last change, Ctrl+Shift+Z or Ctrl+Y restores it. Both are also saved immediately.

If someone else changes the settings while you have the screen open, it reloads — provided you have entered nothing unsaved. Otherwise the bar reports This record was modified by … when saving, with Reload and Save anyway; both ways are described in Two editors on the same object.

What else the bar shows is described under Configuration Snapshots.

Automatic cleanup​

The second area shows the run that deletes according to the periods. It runs on its own, every night at 2:00 server time. Changing the time or starting a run manually is not possible here.

RowWhat it says
Next runTime of the next run, or Not scheduled
Last runTime of the last run

Not scheduled means: there is no valid schedule, and nothing is deleted.

If the last run deleted nothing, this is stated in the same row after the time: — no records deleted. A run that finds nothing is the normal case on a day on which nothing has become old enough.

When a run ends while the screen is open, the area updates on its own. When the system is halted, deletion rests as well — see Retention and reset.

In the example: Last run 08.10.2026 02:00, Next run 09.10.2026 02:00.

The deletion log​

Below it is what the last run deleted — two columns, Area and Deleted.

The Area column carries the names of the periods. Where a period covers two things, there is therefore a single row, and the number is the sum of both.

The rows are in the order of the fields above. The table shows the periods under which something was deleted: if one is missing, nothing there was old enough — or the field is empty, and there everything stays. In the delivery state System log is therefore always missing.

In the example: Settled events 212, Completed operations 693.

When the run reaches a batch limit​

Per area, a run deletes at most a certain amount at once. When it is reached, a banner above the table says so:

The run reached its batch limit and continues with the next run.

This settles itself: the rest is deleted on the next run, and if needed on the one after that.

When the screen looks half empty​

Three pieces of information appear only once they exist — on a freshly set-up system several of them are therefore missing, and everything is fine.

MissingMeans
Last runNo cleanup run has taken place yet.
the deletion logThe last run deleted nothing.
the banner above the tableThe last run finished in one go.

If the screen does not load at all, a message says so: The settings could not be loaded.

See also​