Dock Commitment fields

Load

Load ID: The handling for Load ID (and Stop Number) impacts many of the other fields on the Dock Commitment Properties page. Load ID will be editable in Create Mode and in Edit mode for an unassociated dock commitment.
Any Load ID that is specified must satisfy the following requirements:
- Operational Status for the designated load must not be Canceled, Completed or Closed.
- If operation is being performed by a carrier, the designated load must refer to the user's Carrier ID.
Tracking Number: Always read only. This field will present the Tracking Number for the applicable load.
Stop Number: The handling for Stop Number (and Load ID) impacts many of the other fields on the Dock Commitment Properties page. Stop Number will be editable in Create Mode and in Edit mode for an unassociated dock commitment.
Once a Load ID has been defaulted or selected, the combo box for Stop Number will present the stops from the designated load where that satisfy these requirements:
- Stop Number corresponds to a stop where docks have been configured.
- If the page from which the New or Properties operation was itself triggered from the perspective of a specific shipping location, the combo box will only include stops from the load where the Shipping Location ID and Type for the stop are equal to the “current” Shipping Location ID and Type (that is, the values that appear in the Location section).
- Stop cannot be confirmed or delivered.
- A dock commitment must not already refer to the Stop Number.
If there is just one stop for the load that satisfies these requirements, it will be established as the default. If there are no stops for the load that meet these requirements, an error situation exists.

Logistics Grouping

Division: The Division for the dock commitment. It is mandatory. It can be overridden only when a user that is not restricted to a specific division creates an unassociated dock commitment (that is, dock commitment that does not refer to a Load ID and Stop Number). Otherwise, it will be controlled by the system.

In Create mode, if the Dock Commitment Properties page was accessed from the perspective of a specific stop, the Division for the applicable load will be used as the default. Otherwise, the default will be based on the user’s profile.

If a Load ID is assigned to an unassociated dock commitment in Edit mode (that is, so that it will become associated to a load and stop), the Division for the dock commitment must match the Division for the selected load.

Any load referenced by a division-restricted user must refer to the Division in the user’s profile.

Logistics Group: The Logistics Group for the dock commitment. It is mandatory. It can be overridden only when a user that is not restricted to a specific Logistics Group creates an unassociated dock commitment (that is, dock commitment that does not refer to a Load ID and Stop Number). Otherwise, it will be controlled by the system.

In Create mode, if the Dock Commitment Properties page was accessed from the perspective of a specific stop, the Logistics Group for the applicable load will be used as the default. Otherwise, the default will be based on the user’s profile.

If a Load ID is assigned to an unassociated dock commitment in Edit mode (that is, so that it will become associated to a load and stop), the Logistics Group for the dock commitment must match the Logistics Group for the selected load.

Any load referenced by a logistics group-restricted user must refer to the Logistics Group in the user’s profile.

Note: In Create mode, the values for the designated load will supersede any existing values for Division and Logistics Group, regardless of whether they were system defaults or input by the user.

Carrier

Carrier ID: Carrier is editable for unassociated dock commitments unless the user is restricted by Carrier ID.
In Create mode:
- When a carrier type user creates an unassociated dock commitment, the user's Carrier ID will be the default.
- If a Load ID has been selected, the Carrier ID for the load will be used as the default (potentially superseding a value supplied by the user).
- If the Dock Commitment Properties page was accessed from the perspective of a specific stop, the Carrier ID for the corresponding load will be used as the default.

In Edit mode, if a Load ID is specified for an unassociated dock commitment:

If Carrier ID for the dock commitment is already populated, the load’s carrier will not replace the existing carrier. A populated Carrier ID for the dock commitment and a null Carrier ID for the load will trigger an error condition. A populated Carrier ID for the dock commitment and a different populated Carrier ID from the load will also be invalid.
If the Carrier ID field for the dock commitment is blank, then the load’s Carrier ID will be used to populate the Carrier ID. A null Carrier ID for the dock commitment and a populated Carrier ID for the load will be a legal scenario.

Carrier Name: The name for the carrier. This will always be read-only and will be refreshed when the Carrier ID is modified.

Location

Location Type and Location ID: Location Type and Location ID are mandatory. If the user accessed Dock Scheduling via the List of Locations with Docks (Carrier) or accessed this page via the List of Commitments for Dock (Carrier), the applicable Location Type and Location ID will be established as defaults and will be view only. Otherwise, location can be controlled only when creating or editing an unassociated dock commitment in which case there must be at least one dock configured for the designated location. In Create mode, Location ID and Location Type will default from the context of the applicable stop. When creating an associated dock commitment or when linking an existing unassociated dock commitment to a stop, the location for the stop must be equal to the location for the dock commitment.
Location Name: The name for the shipping location. This will always be read-only and will be refreshed when the Location Type and/or Location ID is modified.

Dock

Dock ID: Dock ID can be maintained in Create and Edit modes for both associated and unassociated dock commitments. In Create mode, if the user triggered the operation from the List of Commitments for Dock (Carrier), the applicable Dock ID will be established as a default and overrides will be allowed. Secondary search will present docks for the applicable shipping location.
Description: The description for the dock. This will always be read-only and will be refreshed when the Dock ID is modified.
Dock Type: Possible values for Dock Type are: Inbound Only, Outbound Only, Both. Dock Type will always be read-only and will be refreshed when the Dock ID is modified.

Time Slot

Start Date: Mandatory. When the Dock Commitment Properties page is accessed in Create mode using the New operation, once a load and stop have been established, a default will be provided using the date portion of the Last Computed Scheduled Arrival Date for the applicable stop. Start Date will also be populated any time the Load ID and Stop Number combination is modified.

When the Dock Commitment page is accessed in Create mode by double-clicking a cell on the Dock Commitment Gantt Chart, the applicable date for the cell will be established as the default, even if the Dock Commitment Gant Chart was accessed from the context of a specific stop.

If Dock Commitment Date/Time Access for the user group for the current user is Start Time Only and a load and stop have been specified, the Start Date for the Dock Commitment must be equal to the Last Computed Scheduled Arrival Date for the stop. There will be no corresponding limitation regarding Start Date when these users maintain an unassociated dock commitment, assuming they are authorized to this type of dock commitment.

Start Time: Mandatory. Will be editable in Create and Edit modes. If the Restricted Start Times for Dock Commitments flag in the global settings is True, Start Time can be supplied via text box or combo box, else only via text box. See Start times for a dock commitment.

Default logic for Start Date also applies to Start Time. Also, the defaulted Start Time for a dock commitment will not take the Dock’s “Dock Commitment Eligible Start Time” into consideration, and validation will identify incorrect times if global setting is configured to Restrict Start Times for Dock Commitments. If an error condition exists with the default Start Time, user can decide whether to round up or round down the time.

Duration: If Dock Commitment Date/Time Access for the user group for the current user is Start Time Only or Start Date/Time Only, the Duration will be presented as read-only text even in Create and Edit modes. For unassociated dock commitments, default will be provided by identifying the Fixed Loading/Unloading Time for the dock; if this is not defined, the Fixed Loading/Unloading Time for the applicable shipping location will be established as the default. For associated dock commitments, initial default will be established using the first value from the following list that is available:
- Difference between Last Computed Scheduled Arrival and Departure Dates/Times for the applicable stop
- Fixed Loading/Unloading Time for the dock
- Fixed Loading/Unloading Time for the shipping location
End Date / Time: If Dock Commitment Date/Time Access for the user group for the current user is Start Time Only or Start Date/Time Only, End Date and End Time will be presented as read-only text even in Create and Edit modes. Default will be established once Start Date, Start Time and Duration have been provided.

External Identifier

External ID: The External Identifier can be used to cross-reference the dock commitment to a transaction in another application. It can be maintained by carriers and employees in Create and Edit modes for both associated and unassociated dock commitments.

Event

Last Reason Code: The Event Reason Code assigned to the most recent event for this dock commitment. This reason code could have been supplied when performing any of these operations: Create, Edit, Swap, or Generate Event.
Reason Code: This combo box will contain Event Reason Codes enabled for the applicable operation (that is, Create / Edit). If will be captured as the Last Reason Code for the dock commitment and will be included in the Event Notification message generated for the operation, if applicable.
Reported Date/Time: Mandatory. Must refer to a valid date/time. This will be included in the Event Notification message generated for the operation, if applicable.

Recap of Validation

The following validation will be performed when attempting to create or update a dock commitment. Some of the following statements repeat text associated with individual fields:

User must be authorized to update the dock commitment. See Restrictions by user group.
If the user is restricted to a Division or Logistics Group, the dock commitment must refer to the user’s restricted values.
If the dock commitment refers to a load and stop (or would refer to a load and stop if the operation were to be allowed to complete):
- Operational Status for the designated load must not be Canceled, Completed or Closed.
- The designated stop cannot be confirmed or delivered. A stop is confirmed when there is at least one shipment leg being picked at the stop and the Stop Confirmed flag is True. A stop is delivered when there is at least one shipment leg being delivered at the stop and the Delivery Arrival Date/Time is not null and not zero.
- There cannot be a different dock commitment that already refers to the designated load and stop.
- Shipping Location ID associated with the stop must be equal to the Shipping Location ID for the dock associated with the dock commitment.
- Division and Logistics Group for the load must be equal to the Division and Logistics Group for the dock commitment.
- If a Carrier ID is defined for the dock commitment, the load must also refer to this same Carrier ID.
- If the Dock Commitment Date/Time Access for the user group for the current user is Start Time Only, the date portion of the Start Date/Time for an associated dock commitment must be equal to the date portion of the Last Computed Scheduled Arrival Date for the applicable stop, if a value exists; if this date does not exist for the stop, a user with these restrictions will not be allowed to perform this operation.