Regarding the interface mapping documentation between RoutOptimiser and the Axylog API, the "documentDate" corresponds to "Tour.StartDate".
This is accurate only for the initial handover from ROST to Axylog. If the trip schedule is adjusted within ROST and the trip is subsequently resent to Axylog, the document date will remain unchanged.
There are both technical and logical reasons for this behavior. Technically, the date serves as a key identifier for the document. Logically, the DocumentDate reflects the date the shipping order was placed. Consequently, it pertains directly to the receipt of the shipping request and does not influence the planning or execution phases.
Comments
0 comments
Please sign in to leave a comment.