Avoid and investigate duplicates
The suspicion always comes in the same form: a job has ended without a clean completion, and now the question is whether the record was already created in the target system anyway. A second attempt could create it a second time.
Look first, then act. Almost every clarification you open in Clarification you settle with Reprocess in one click. For the three causes further down, look in the target system before that click.
In the example, three orders from the webshop run through the page. WS-2026-104877 went
through cleanly on Thursday morning and shows what normally prevents a second document.
WS-2026-104812 from Tuesday and WS-2026-104850 from Wednesday are two clarification cases that
A. Vogt closed this week after looking.
What you need
- The Clarification permission, level Full. With Read only you can read every case; Reprocess and Close require the level Full. See Permissions.
- Access to the target system. Whether the record is there can only be answered by the target system: Xchange knows that it wrote, and the target system knows what happened afterwards.
- The key value of the job. It is in the clarification and in History; you use it to search in the target system.
What normally prevents a second document
The route "Bestellungen Webshop" carries two settings on the Mapping tab that together form the protection:
| Field | Value |
|---|---|
| Key source | Target system lookup |
| Write intent | Create or update |
So Xchange looks up the key in the target system before writing. If the same order
WS-2026-104877 comes in a second time, the lookup finds the document from before and updates it.
It stays one document.
This protection is a setting of the route. It applies as long as there is a lookup. If the write intent is Create, every job creates a document. Whether your route is protected you see at a glance under Routes on the Mapping tab; which combinations exist and what they mean is covered under Routes — Mapping, and why there is a lookup before writing, under Writing to the target system.
If the source already carries the target system's key, the address protects. With the Key source Mapping or source and Create or update, Xchange first reads the record under the Item endpoint. If it exists, it is changed; if the target system answers that it does not exist, it is created. On any other answer Xchange creates nothing.
The lines are protected by the key of the list. So that a second delivery of the same order does not append a line twice, Xchange also finds the lines in the existing document again. How to set this up is covered under Map header and lines when the target splits differently.
A duplicate has arisen — or might have
The three causes for which you look first
In Clarification, each case names its cause. Three of them say, in substance, the same thing: Whether it arrived is open.
| Cause | Cause group | What it says about the target system |
|---|---|---|
| Aborted after the write | Internal error | The record was created; only the completion could not be recorded. |
| Deadline exceeded | Target system | No answer within the deadline. The record may already have arrived there. |
| Divergent redelivery | For decision | The same message came a second time, with different content. |
The three are in three different cause groups. A filter on one group thus catches at most one of them; go through the three causes one by one.
For the first two, Xchange states the caveat on the detail page itself. WS-2026-104812
came into clarification on Tuesday at 2:37 PM with Aborted after the write, after five
retries:

What counts is the sentence below the short label; the Message below it is Xchange's own technical note.
For all other causes, the normal way applies from Resolve a clarification: where the mapping aborted or the target system rejected, nothing has been created in the target system.
Looking in the target system
Take the key value from the clarification and search the target system with it — for an order from the webshop, that is the order number in the field the mapping writes it to. Three results are possible:
- Nothing found. The record is missing from the target system. Reprocess is the right way.
- Found exactly once, complete. The record is there. A new attempt would, with the write intent Create, produce the second one — close the case instead.
- Found, but incomplete. Here the write intent of the route decides: with Create or update, a new attempt completes the existing record; with Create, it creates a second one. Look at the Mapping tab before you click.
In the example, A. Vogt searches SAP Business One for the sales order with WS-2026-104812 in the field
NumAtCard, to which the route writes the order number. The order is there once and
complete. At 3:02 PM, A. Vogt closes the case.
What the UI records about the job itself — which step got how far, what went out — you find via Find and trace a single job.
With Divergent redelivery, the comparison is already there
For this case, Xchange does the searching for you: it has kept both versions. On the detail page, the Contents section is added and places them side by side.
In the example, the message msg-7d14a2 for WS-2026-104850 came on Wednesday at 11:03 AM and was
processed. At 11:48 AM it came a second time, with a different quantity:

The first delivery has already been processed and stays unchanged. You decide only one thing: whether the divergent content should be processed as well. Read the differences, and decide on the business side — does the second version correct the first, or is it a mistake of the source system?
In the example, checking back with the shop reveals a mistake: in the customer account, the quantity had been changed and the change discarded again before submitting, but the shop sent the discarded version anyway. The first version holds, and A. Vogt closes the case at 12:20 PM.
Cleaning up in the target system
If a duplicate has arisen, clean it up in the target system itself. Xchange writes only what a route requests; you delete a duplicate record or merge two of them where they are.
Close takes the case out of the work queue and records that you have seen and decided it. That is exactly right when the record is already correct in the target. What a closed case says about the record is covered under Clarification.
When two systems trigger each other
A second occasion for duplicates: two systems that send each other their changes. Xchange writes to SAP Business One, this triggers an event, the opposite direction carries it back — and round again.
What you see when this happens: in History, jobs appear as Skipped (echo detected). That is the brake, and it works by itself: for each field, Xchange remembers which system the value came from. If a value would only go back there, it is dropped. One round, then it stops.
The brake decides per mapping row. A field a system sets itself on saving — a timestamp or a running number — did not come from the opposite direction and is transferred. If such a field travels along, the transfers keep running. The sign of this is a route that creates jobs continuously with no apparent reason.
The remedy is the route's own means: cut the mapping so that the traveling fields stay out when writing back, or narrow down the opposite direction with a data filter. Both are a change to the route; until it is active, Take a route out of operation helps further.
What comes next
- The case was not one after all, and the job should run again: Retry failed jobs.
- There are several cases of the same kind: Resolve a clarification shows how to work through them together — for these three causes, check each one individually, because the answer is in the target system.
- You want to prevent it from happening again: Routes — Mapping, the section on key source and write intent.
See also
- Clarification (reference) — all causes, cause groups and sections of the detail page.
- Routes — Mapping (reference) — key, key source and write intent in detail.
- History (reference) — where you find a single job and its outcome again.
- Writing to the target system (core concept) — why there is a lookup before writing and what a key in the target achieves.