The List of Events displays a subset of the Events that can be generated in Transportation Manager. The Events that are included on this list are pre-determined.
Each Event is linked to one or more Entity Statuses. This List of Statuses for (an) Event represents the set of Entity Statuses at which this Event could occur. This list is also pre-determined.
Each Event / Status combination is linked to a list of available Reason Codes. This list is partially pre-determined (System Provided Reason Codes are provided and cannot be altered).
However, when User Reason Codes are allowed for an Event / Status combination:
The usage of each Reason Code (whether System Provided or User Defined) can be configured based on User Group Type (Employee, Carrier, Customer). This is done by setting the appropriate controls for Employee Usage, Carrier Usage and Customer Usage to one of the three supported values: Available, Available and UI Default, Unavailable.
The usage rules configured here will be respected throughout Transportation Manager wherever the user is permitted to explicitly provide a Reason Code in conjunction with an Event.
Include in Percentage Constraints flag allows you to determine if the associated resources are considered for percentage based constraints when a load, trip, or booking tender is canceled or rejected. This option is only editable for events related to load/trip/booking tender cancel and tender reject. This flag is only applicable when Carrier Assignment Recognition in Global Settings is not “Currently Assigned and Tendered”.
For many events (for example, Load Impacted by Shipment Change), a pseudo status has been created such that "All Applicable Statuses" can be treated as a single status when configuring User Defined Reason Codes. This is a very helpful shortcut as it means that the set of Reason Codes available to these events can be configured once yet utilized across multiple statuses.
In some cases, Reason Code configuration can also be shared between events. For events where an Event Group Code has been defined, Reason Codes configuration will be shared with other events that refer to the same Event Group Code. For example, the Reason Codes for the Load/Stop Return to In Transit event are shared by the Shipment Leg Return to In Transit event.
List
By default, the List of Events is sorted in ascending order by Event Name.
For information on icons and functionalities available on the list pages, see Web Interface lists.
Note: If Status Type is used as a filter criterion from the Search for Events screen, list will include Events where at least one of the designated Statuses if applicable for the Event.
Note: If Entity Type is used as a filter criterion from the Search for Events screen, list will include Events where at least one of the selected Entity Types is applicable for at least one Status for the Event.
Note: If Reason Code is used as a filter criterion from the Search for Events screen, list will include Events where at least one of the designated Reason Codes has been enabled for at least one Status for the Event.
Similarly, the List of Statuses associated with an Event is sorted (by default) in ascending order by Status ID.
Finally, the set of Reason Codes for a selected Event / Status combination are displayed in an editable grid. These are presented in ascending order by Reason Code.
Properties
For each Event, you can access a list of statuses configured for this Event.
For each Event / Status combination, you can access a list of available Reason Codes. From here, you can update the usage rules associated with existing Reason Codes. If User Reason Codes are allowed for the Event / Status combination, you can also add new User Defined Reason Codes or delete User Defined Reason Codes that are not required.
This Reason Code configuration will be applied at every point in Transportation Manager that you can provide a Reason Code in conjunction with an Event (the list of Reason Codes from which you can select are dynamically built based on the associated Event / Status combination).