Shipments

Internal Table Name: Shipments

When using shipments with Network Optimization, Flow Constraints with a Constraint Type of "Min" are generated based on the Source values. The Destination for the flow constraint will be set to "(ALL)". See information in the field definitions for this behavior.

Name

Technology: NO TO

Table: Shipments

Internal Name: ShipmentName

Type: Short Text (150)

Enter the Name for the Shipment.

Transportation Optimization: The Name is used throughout the Transportation Optimization process, specifically:

  • In the Relationship Constraints Builder
  • In the Shipment Constraints table
  • Reported in all Transportation Optimization output tables

If you do not populate Name for Shipments, Transportation Optimization will generate a name in the format <source>_<destination>_<xxxxx> where xxxxx is a unique number. However, it is recommended that you populate the Name to better track the Shipments throughout Transportation Optimization.

Source

Technology: NO TO

Table: Shipments

Internal Name: SourceSite

Type: Short Text (100)

Enter the location (Site or Customer) or location group that will be shipping the product.

Customers are supported as Source values for Transportation Optimization only.

Network Optimization: If the Source is an existing Site and the Destination is a Customer, this shipment is considered as an additional demand point for the customer. However, a flow constraint is created from the Source to a destination of "(ALL)".

Destination

Technology: NO TO

Table: Shipments

Internal Name: DestinationSite

Type: Short Text (100)

Enter the location (Site or Customer) or location group that will be receiving the product.

Network Optimization: If the Source is an existing Site and the Destination is a Customer, this shipment is considered as an additional demand point for the customer. However, a flow constraint is created from the Source to a destination of "(ALL)". If the Destination is an existing Site (not a Customer), the actual destination is considered "(ALL)" in the constraint as well.

Product

Technology: NO TO

Table: Shipments

Internal Name: ProductName

Type: Short Text (100)

Enter the name of the product or product group to be shipped.

Class Name

Technology: TO

Table: Shipments

Internal Name: ClassName

Type: Short Text (100)

Enter a value to classify the shipment when applying Shipment-Based Rate values. The Class Name is used only in conjunction with the Shipment-Based Rate table to identify shipments for which each shipment-based rate should be applied.

In the Shipment-Based Rate table, you define Per Unit Cost and Discount Rate values based on unique combinations of Asset-Source-Destination-Class. These rates are applied at the shipment level, rather than applying route-based values.

Mode

Technology: NO IO S

Table: Shipments

Internal Name: Mode

Type: Short Text (100)

Enter the mode for this shipment.

Quantity

Technology: NO TO

Table: Shipments

Internal Name: Quantity

Type: Short Text (50)

Enter the amount of product to be shipped. Enter a value, then optionally select a quantity, weight or volume unit of measure. If you do not select a unit of measure, the default Quantity Unit Of Measure from Model Settings is used. You can also specify a probability distribution.

For Simulation, Coupa recommends using Occurrences = 0 when you want to exclude certain records in the Production and Shipments tables.

Default: 1

Weight

Technology: All

Table: Shipments

Internal Name: UnitWeight

Type: Short Text (50)

Enter the weight of one unit of product in this shipment. Enter a value, then optionally select a weight unit of measure. If you do not select a unit of measure, the default Weight Unit Of Measure from Model Settings is used. If this field is left blank during Simulation, the Unit Weight from the Products table is used.

When using Transportation Optimization, the Weight is the weight of the shipment. If this field is left blank during Transportation Optimization, the associated value from the Products table is not used.

Volume

Technology: All

Table: Shipments

Internal Name: UnitCubic

Type: Short Text (50)

Enter the volume of one unit of product in this shipment. Enter a value, then optionally select a volume unit of measure. If you do not select a unit of measure, the default Volume Unit Of Measure from Model Settings is used. If this field is left blank during Simulation, the Unit Volume from the Products table is used.

When using Transportation Optimization, the Volume is the volume of the shipment. If this field is left blank during Transportation Optimization, the associated value from the Products table is not used.

Unit Price Override

Technology: NO IO S

Table: Shipments

Internal Name: UnitPrice

Type: Short Text (50)

Enter the price to ship one unit of product in the shipment during shipment. If this field is left blank, the Price from the Products table is used.

For Transportation Optimization, the Unit Price Override in the Shipments table is not used.

Order Date

Technology: NO TO S

Table: Shipments

Internal Name: ArrivalTime

Type: Date/Time

Enter the date when this shipment will occur. The shipment can occur on a certain date or after a certain time period. To specify the time period, use Order Date Formula.

If you populate both Order Date and Order Date Formula, Order Date Formula is used when running Optimization or Simulation.

For Transportation Optimization, this field specifies the start of the delivery time window for the shipment. The end of the delivery time window is defined using Due Date.

Order Date Formula

Technology: NOS

Table: Shipments

Internal Name: ArrivalTimeFormula

Type: Short Text (50)

Enter a number or distribution that defines when the shipment will occur. Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used. You can enter probability factors or time units for shipment time.

Due Date

Technology: NO TO S

Table: Shipments

Internal Name: DueDate

Type: Date/Time

Used to specify the date by which a shipment must be completed.

If you populate both Due Date and Service Level, Service Level is used when running Optimization or Simulation.

For Transportation Optimization, this field specifies the end of the delivery time window for the shipment. The start of the delivery time window is defined using Order Time.

Service Level

Technology: NOS

Table: Shipments

Internal Name: DueDateFormula

Type: Short Text (50)

Enter the number or distribution that defines when a shipment must be completed. Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

The default Service Level unit is DAY. If you do not enter a date, the software assumes the Service Level is measured in days. If Service Level is left blank, the software assumes the order is due immediately when a shipment occurs.
If you populate both Due Date and Service Level, Service Level is used when running Optimization or Simulation.

Due Date examples are shown below:

If you want the Due Date to occur: Enter:
As soon as a production begins 0 or leave blank
1 day after the production begins 1
On a particular day Use the Due Date field

Occurrences

Technology: NO IO S

Table: Shipments

Internal Name: Occurences

Type: Short Text (50)

Enter how many times this shipment will occur. A shipment must occur at least once. When you enter a number greater than one, shipments will occur multiple times.

If you want the Occurrence to take place: Enter:
1 time 1
10 times 10
As long as the simulation runs INF
For Simulation, Coupa recommends using Occurrences = 0 when you want to exclude certain records in the Production and Shipments tables.

Default: 1

Shipment Frequency

Technology: NO IO S

Table: Shipments

Internal Name: InterArrivalTime

Type: Short Text (50)

For Simulation, enter how much time must pass between each recurring order. Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used. It is directly connected with the Occurrences. For example, Shipment Frequency can be 24 Hour, meaning that shipment must recur every 24 hours.

For Optimization, the Shipment Frequency is ignored. The total shipment size based on Quantity and Occurrences is put into the period for which the shipment is specified based on the Order Date or Order Date Formula field.

You must enter data in this field if the Occurrences are greater than 1. If you do not enter Shipment Frequency and shipments recurs, the software will assume that shipments happen once a day.

Shipment Frequency examples are shown below:

If you want: Enter
Recurring daily shipment 1 DAY or leave blank
Occurrences: INF
Randomly occurring shipments according to a triangular distribution T(1,3,4) DAY
Occurrences: INF

Tracking ID

Technology: S

Table: Shipments

Internal Name: TrackingID

Type: Short Text (50)

When creating a Transportation Optimization baseline model, enter the Tracking ID to which the shipment should be assigned. The order of the shipments on the route is determined by the value you enter for Pickup Sequence or Delivery Sequence.

Priority

Technology: TO S

Table: Shipments

Internal Name: Priority

Type: Short Text (50)

Enter the priority level of the shipment.

Simulation: This field can be called in a script during simulation.

Cancel If Late

Technology: S

Table: Shipments

Internal Name: CancelIfLate

Type: Short Text (5)

One of Yes, No.

In the drop-down menu, select if the shipment will be canceled if it is late at the moment of order processing. Refer to Cancel If Late in the Customer Demand table for additional explanation including information about output.

Default: No

Direct Shipping Cost

Technology: All

Table: Shipments

Internal Name: LTLCost

Type: Short Text (100)

Defines the cost to make the shipment using standard direct shipping (often LTL) rates. If specified, the optimization can look to consolidate multiple direct shipments into a truckload shipment to save money.

Transportation Optimization: The cost from the last pool site or hubs in the network to the customer location, if using direct ship (such as LTL/small package) shipping method. If Direct Shipping Cost is lower than the cost to route the shipment, then Transportation Optimization picks direct shipping over routing the shipment. Both route cost and tour cost (transportation asset cost) are considered when the solver is deciding whether to route or direct ship the shipment.

If this value is null or 0, direct shipping is not considered for this shipment.

Fixed Service Time

Technology: TO

Table: Shipments

Internal Name: ServiceTime

Type: Short Text (50)

This field defines the fixed service time for the shipment at all stops. Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Fixed Service Time Load

Technology: TO

Table: Shipments

Internal Name: FixedServiceTimeLoad

Type: Short Text (50)

This field defines the fixed service time for loading the shipment at the origin location. The total service time at a pickup stop =

Fixed Service Time + Fixed Service Time Load + (Variable Service Time Load x total Quantity/Weight/Volume value),

Quantity/Weight/Volume is defined by the Key Unit of Measure in Transportation Optimization Options (default is Quantity).

Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Fixed Service Time Unload

Technology: TO

Table: Shipments

Internal Name: FixedServiceTimeUnload

Type: Short Text (50)

This field defines the fixed service time for unloading the shipment at the destination location. The total service time at a delivery stop =

Fixed Service Time + Fixed Service Time Unload + (Variable Service Time Unload x total Quantity/Weight/Volume value),

Quantity/Weight/Volume is defined by the Key Unit of Measure in Transportation Optimization Options (default is Quantity).

Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Variable Service Time Load

Technology: TO

Table: Shipments

Internal Name: VariableServiceTimeLoad

Type: Short Text (50)

This field defines the variable service time for loading the shipment at the origin location. The total service time at a pickup stop =

Fixed Service Time + Fixed Service Time Load + (Variable Service Time Load x total Quantity/Weight/Volume value),

Quantity/Weight/Volume is defined by the Key Unit of Measure in Transportation Optimization Options (default is Quantity).

Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Variable Service Time Unload

Technology: TO

Table: Shipments

Internal Name: VariableServiceTimeUnload

Type: Short Text (50)

This field defines the variable service time for unloading the shipment at the destination location. The total service time at a delivery stop =

Fixed Service Time + Fixed Service Time Unload + (Variable Service Time Unload x total Quantity/Weight/Volume value),

Quantity/Weight/Volume is defined by the Key Unit of Measure in Transportation Optimization Options (default is Quantity).

Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Variable Service Time Basis

Technology: TO

Table: Shipments

Internal Name: VariableServiceTimeBasis

Type: Short Text (50)

Select the Unit of Measure by which variable service time is assessed. Select one of Quantity, Weight or Volume, then select the specific unit of measure. If you do not select a unit of measure, the default Quantity unit of measure is used.

Earliest Pickup Date

Technology: TO

Table: Shipments

Internal Name: EarliestPickupDate

Type: Date/Time

This field determines the earliest pickup date and time for the shipment. If no value is specified, Transportation Optimization uses the Begin Time Horizon parameter (defaults to Model Horizon Start Date).

Latest Pickup Date

Technology: TO

Table: Shipments

Internal Name: LatestPickupDate

Type: Date/Time

This field determines the latest pickup date and time for the shipment. If no value is specified, Transportation Optimization uses the End Time Horizon parameter (defaults to Model Horizon End Date).

Comp2 Quantity

Technology: TO

Table: Shipments

Internal Name: Comp2Quantity

Type: Short Text (100)

Enter the quantity of product to be shipped in the second compartment of the selected transportation asset. Enter a value, then optionally select a quantity unit of measure. If you do not select a unit of measure, the default Quantity Unit Of Measure from Model Settings is used. Shipments that have Comp2 Quantity values populated can be loaded into the second compartment of the asset during Transportation Optimization.

Comp2 Weight

Technology: TO

Table: Shipments

Internal Name: Comp2Weight

Type: Short Text (100)

Enter the weight of product to be shipped in the second compartment of the selected transportation asset. Enter a value, then optionally select a weight unit of measure. If you do not select a unit of measure, the default Weight Unit Of Measure from Model Settings is used. Shipments that have Comp2 Weight values populated can be loaded into the second compartment of the asset during Transportation Optimization.

Comp2 Volume

Technology: TO

Table: Shipments

Internal Name: Comp2Cubic

Type: Short Text (100)

Enter the volume of product to be shipped in the second compartment of the selected transportation asset. Enter a value, then optionally select a volume unit of measure. If you do not select a unit of measure, the default Volume Unit Of Measure from Model Settings is used. Shipments that have Comp2 Volume values populated can be loaded into the second compartment of the asset during Transportation Optimization.

Seed

Technology: S

Table: Shipments

Internal Name: Seed

Type: Number (Long Integer)

Use this field to control the pattern used for shipments. For example, if you have customers that should follow the same shipment pattern, you can populate the Seed value with the same value in the shipments records for these customers. By default, this field is not populated and the seed value is determined based on the order in which the shipment is processed. As a result, it is somewhat random in its results.

Status

Technology: All

Table: Shipments

Internal Name: Status

Type: Short Text (50)

One of Include, Exclude.

This field determines whether or not the shipment will be included when you run Transportation Optimization.

Default: Include

Notes

Technology: All

Table: Shipments

Internal Name: ShipmentNotes

Type: Memo

Enter optional descriptive notes about the shipment.

Last modified: Friday May 12, 2023

Is this useful?