Diagnosis
The external transfer &V1& has already been used in the internaltransfer &V2& of &V3&.
This transfer however can no longer be assigned to this IDoc.

System Response
The IDoc is assigned to a new internal transfer number. For reasons ofsecurity, this transfer is deactivated so that the processing stepcannot be executed. You should now check if the transfer was really senttwice.
The process, if this is an example of a transfer that has NOT been senttwice (duplicate) is described below.

Procedure
Check whether this is an example of a duplicate.
If not, you can make settings for the "Duplicate check" in Customizing(transaction OVD5) so that this is only executed for a specific time inthe past. This is intended if the EDI partner resets external transfernumbers each year.
In the case that there is no duplicate transfer (the external transfernumber was used last year for example, and now leads to a "false"duplicate result), you have to proceed as follows:

• Set the transfer to active with the function "Set transfer active".


• Start the verification step again. The error message that a duplicate
exists, no longer appears.

• Eliminate other possible verification errors and then start the
processing step.