Looks like this topic hits both TourIDs and OrderIDs.Long story short: as Joost explained it is caused by buffer overflow of the integers and produces an exception (Order ID) or a "replacement" (TourID).

For those (SAP based) users who ran into the issue: you need a mapping between your IDs (however they aber based) and some valid INTs.

The xTour2 API deals with string based IDs instead of INTs, so the problem won't occur anymore.

Besr regards,Bernd

PS: your depot has more than 1000 intervals covering a period of 3.4 years. A bit weird if you ask me