User Productivity Improvement in TM 9.0: Cross Document Time Check
There is a new cool feature, that was introduced in the area of freight order management with TM 9.0.
It is called 'Cross document time check'.
The feature is about preceding & subsequent execution documents for the same transporation demand (FU) based on the stages of such a demand.
For example for the pre-, main- and on-carriage of a sales order or forwarding order.
So the feature is available independent on where the demand is coming from (forwarding order, sales order, purchase order, delivery, ...).
The business challenge nowadays is, that different planners may work on multiple stages independently and do not have any indicator that there is a time conflict with predecessor or successor documents that are planned by other planners.
The big advantage of the new feature is, that planners now can work by exception as they can easyly find out which documents have a time conflict based on a POWL selection.
How does this the whole process work?
1. There are 3 orders planned for a transportation demand on multiple stages.
2. Now one of the planners changes the planned arrival time of the pre-carriage.
3. The result will be, that for the pre-carriage and the main carriage document there is a time conflict for the documents.
How does that look in the system?
1. The origin demand document is a forwarding order. There are 3 documents planned that cover the transportation demand (One freight order for customer pickup, one freight order for transfer from local warehouse to regional warehouse & and a freight booking from the regional warehouse (gateway) to another regional warehouse (gateway)).
As stated above the whole process also works for other demands e.g. sales orders, ...
2. Now the departure date of the aircraft is changes to an earlier date.
3. Subsequently, when the cross document check is executed in the booking, the check result changes to 'Warning' in order to indicate that there is a time conflict. The check can either be executed manually or is automatically executed on changing the document.
4. The time conflict check result is also automatically propagated and visible in the affected predecessor document.
5. The arrival date of the affected freight order is (local warehouse --> regional warehouse) changed to resolve the time conflict.
6. The cross document check is removed by manually checking the FO (in the freight order) or on save (for both for the freight order and the origin booking).
7. To enable planners to work by exception, it is possible to select bookings and freight orders in the respective POWLs and also display the check result in the result list.
8. Of course planners mainly work in the transportation cockpit. Therefore the indicator for cross-document check is as well visible in the TC: