Reference Number Visibility Configuration can be used to define up to Thirty (30) Reference Number Types for each of the following entities in Transportation Manager:
This information is used in three different ways:
Note: There is no audit table for dock commitments.
List
By default, the list displays the five active entity types, which are, the Loads, Shipments, Trips, Bookings, or Dock commitments supported by Transportation Manager. Users can alter the Search criteria to include previous versions of the Reference Number Visibility Configurations.
For information on icons and functionalities available on the list pages, see Web Interface lists.
Properties
This page presents a grid of Reference Number Types representing a version of the load, shipment, trip, booking, or dock commitment reference number visibility configuration. The grid will support a maximum of 30 rows, corresponding to the 30 Reference Number Types that can be configured as being visible at any given time.
The page will be accessed in edit mode only for active versions; page will be accessed in view mode for inactive versions. A new version of the Reference Number Visibility Configuration is generated each time the configuration is modified. The version representing the current configuration will be active while archived versions representing previous configurations will be inactive.
Note: A Reference Number Type can only be assigned to one of the thirty Reference Number Types when a Reference Number Type is not currently defined in that position. To replace any of the thirty values, a two step process must be followed: 1) Remove the existing Reference Number Type and click Submit to apply updates 2) When batch process triggered by step 1 is complete, assign desired value to Reference Number Type and again click Submit to apply updates.
Notes
A maximum of thirty (30) Reference Number Types can be associated with each entity type (that is, load, shipment, trip, booking, or dock commitment) at any given time.
When updates are applied for the Entity Type "SHIPMENT", it will trigger a data base process to replicate Shipment Reference Numbers from the Reference Number table to the Shipment table. Additional changes cannot be applied to the "SHIPMENT" Entity Type until this data base process concludes.
When updates are applied for the Entity Type "LOAD", it will trigger a data base process to replicate Load Reference Numbers from the Reference Number table to the Load table. Additional changes cannot be applied to the "LOAD" Entity Type until this data base process concludes.
When updates are applied for the Entity Type "TRIP", it will trigger a data base process to replicate Trip Reference Numbers from the Reference Number table to the Trip table. Additional changes cannot be applied to the "TRIP" Entity Type until this data base process concludes.
When updates are applied for the Entity Type "BOOKING", it will trigger a data base process to replicate Booking Reference Numbers from the Reference Number table to the Booking table. Additional changes cannot be applied to the "BOOKING" Entity Type until this data base process concludes.
When updates are applied for the Entity Type "DOCK_COMMITMENT”, it will trigger a data base process to replicate Dock Commitment Reference Numbers from the Reference Number table to the Dock Commitment table. Additional changes cannot be applied to the "DOCK_COMMITMENT" Entity Type until this data base process concludes.
The data base processes for Loads, Shipments, Trips, Bookings, and Dock commitments can potentially take a long time to complete. The actual amount of time required will vary based on the size of the Load, Shipment, Trip, Booking, Dock commitment and Reference Number tables as well as hardware configuration.
It is recommended that the Log Level for the Business Objects (BObj) Server be set to a minimum of 1 before triggering the data base process for shipments.
Depending on configuration, the screen may time out before the data base process for load, shipment, trip, booking, or dock commitment completes.