Status Templates Transportation
General
This page contains an overview of the Status Templates applicable on the 3PL Dynamics Module: TMS.
The following diagram shows the relations between the various statustemplates on TMS Documents. The statusses marked with the dotted lines are statusses that do not always apply. Only on specific situations these statusses will be applicable.
Functionality
Default Status Flows
For the default status flow on a customer see: Status Flow Customer.
Order Status Flow
The following default flow is applicable on the Order.
| Status | Description | Remarks | ||
|---|---|---|---|---|
| 05-IMPORT | A automaticly created Order. | This status is applicable on Orders created via a Data Integration, WebPortal or Excel Import. | ||
| 06-CHECKAUTO | A check is done on the (un)load addresses. | If the check is succesfully, the status will be set to 15-CALCULATE, if not to 06-CHECKMANUALLY | The address determination cannot be complete automatically | A user will has to check and correct the (un)loadingaddress. |
| 06-CHECKMANUALLY | The address deterination or other check has failed | The user will manually has to check and edit the Order. | ||
| 10-NEW | The status when an Order is created manualy | The User has to click on Next-status to go to the status: 15-CALCULATE. | ||
| 15-CALCULATE | Several checks, kilometercalculation and Contract Strategy are performed. | Kilometers and revenues will appear on the Order. | ||
| 20-RELEASED | Section(s) and an Estimated Calculation will be created. | Functionsets can be applied to add Conditions automatically. | ||
| 30-PLANNEDPARTLY | When not all related Sections are planned on a Trip. | - | ||
| 35-PLANNED | When all related Sections have been planned on a Trip. | |||
| 50-LOADED | When the load-action on the first related Section is finished. | Changing the status of a Planned Loading Activity on a Trip automatically updates the status on the Section and consequently, the status on the Order. | ||
| 55-UNLOADED | When the unload-action on the last related Section is finished. | Changing the status of a Planned Unloading Activity on a Trip automatically updates the status on the Section and consequently, the status on the Order. | ||
| 59-WAITONPOD | When no POD has been attached to the Order. | A JobQueue containing the task: Job Queue Status will check periodically if the POD has been added and a status-change is required. | ||
| 60-TOCHECK | The Order is ready for a User to be checked. | - | ||
| 70-TOINVOICE | The Order is ready to be invoiced. | The final Calculation on the Order will be updated. | ||
| 80-INVOICED | The revenues on the Order have been invoiced. | |||
| 90-CANCEL | The Order has been canceled by an User | The status of the related Sections, revenues and Calculations will be updated. | ||
| 91-TOPOST | Orders in this status can be posted. | For more info: See Posting and Job Queue Posting TMS Documents. |
Grouped Order Flow
The following default flow is applicable on the Grouped Order.
| Status | Description | Remarks |
|---|---|---|
| 10-NEW | The status when Orders have been created an automatically linked to a Grouped Order. | - |
| 20-RELEASED | All suborders have the status: 20-RELEASED. | Status changes are made automatically based on the status-change of the related Orders. |
| 60-TOCHECK | A related suborder has the status: 60-TOCHECK. | Status changes are made automatically based on the status-change of the related Orders. |
| 70-TOINVOICE | All related suborders have the status: 70-TOINVOICE. | Status changes are made automatically based on the status-change of the related Orders. |
| 75-PARTLYINVOICED | The related suborders contain both the status: 70-TOINVOIC and 70-INVOICED. | Status changes are made automatically based on the status-change of the related Orders. |
| 80-INVOICED | All related suborders have the status: 80-INVOICED. | Status changes are made automatically based on the status-change of the related Orders. |
| 90-CANCEL | All related suborders have the status: 90-CANCELED | Status changes are made automatically based on the status-change of the related Orders. |
| 90-TOPOST | All related suborders have the status: 90-TOPOST | Status changes are made automatically based on the status-change of the related Orders. |
Section Flow
The following default flow is applicable on the Section.
| Status | Description | Remarks |
|---|---|---|
| 10-NEW | The status when Section is created. | Sections are created automatically when an Order is in status 10-NEW. |
| 20-RELEASED | When the status of an Order is changed to 20-RELEASED. | The Section is ready to be planned on a Trip |
| 30-PLANNED | When the Section is planned on a Trip | - |
| 50-LOADED | When the load-action on the Section is finished. | Status changes are made automatically based on the status-change of the related Planned Load Activity on a Trip. |
| 55-UNLOADED | When the unload-action on the Section is finished. | Status changes are made automatically based on the status-change of the related Planned Unload Activity on a Trip. |
| 90-CANCELED | When an Order has been changed to the status: 90-CANCEL | - |
| 95-TOPOST | Sections in this status can be posted. | For more info: See Posting and Job Queue Posting TMS Documents. |
Planned Activity
The following default flow is applicable on the Planned Activities.
| Status | Description | Remarks |
|---|---|---|
| 30-PLANNED | The inital status when Planned Activity is planned on a Trip. | - |
| 34-CANCEL | When a Planned Section is deassigned from the Trip the status of the related Planned Activites will change to 34-CANCEL. | A Cancel message will be send to the boardcomputer if applicable. |
| 35-SEND | The Planned Activity is send to a boardcomputer. | - |
| 40-SENT | The Planned Activity is received on the boardcomputer-portal. | - |
| 50-INPROGRESS | The Planned Activity has been started. | - |
| 55-FINISHED | The Planned Activity has been completed. | - |
| 90-CANCEL | The Planned Activity has been canceled. | - |
Trip Flow
The following default flow is applicable on the Trip.
| Status | Description | Remarks |
|---|---|---|
| 10-NEW | The inital status when a Trip is created. | - |
| 20-RELEASED | A User has approved the Trip, it is ready to be executed. | Several checks, kilometercalculation and Contract Strategy are performed. An Estimated Calculation will be added. |
| 30-SEND | The Trip had been send to the boardcomputer. | - |
| 31-SENDCANCEL | A cancel message has been send to the boardcomputer. | - |
| 31-SENDERROR | An error has occured when sending a (cancel)message to the boardcoomputer. | An User has to resolve the error and resend the Trip. |
| 40-SENT | The Trip is received on the boardcomputer-portal. | - |
| 51-CHANGE | A change has been made on the Trip, the trip has to be send to the boardcomputer. | The User has to apply a status-change when all modification have been completed. |
| 55-FINISHED | All activities on the Trip have been completed | - |
| 60-CHECK | The Trip is ready for a User to be checked. | - |
| 70-CHECKED | The Trip has been checked and approved by a User. | A Final Calculation will be added. |
| 90-CANCEL | The Trip has been canceled by a User. | - |
| 95-POST | The Trip is ready to be posted. | For more info: See Posting and Job Queue Posting TMS Documents. |