Baseline Output Shipments

Supply Chain Guru X Help

Home >

Submit Search

A new home for the Coupa Supply Chain documentation

Starting with Supply Chain 42, our documentation will be located on Coupa Compass. The help here will continue to be accessible for the foreseeable future, but will no longer be updated. If you need a Compass user account, contact your company’s Designated Support Contact (DSC).

You can access new and updated Supply Chain documentation in the following location on Compass:

https://compass.coupa.com/en-us/products/supply-chain-design-and-planning

Baseline Output Shipments

Internal Table Name: VRPOutputBaselineShipments

The Baseline Output Shipments output table displays those shipments that have been placed on baseline routes.

For all models, whether you have specifically defined baseline shipments or not, the Baseline Output Shipments table is populated when you run Transportation Optimization. The routed shipments are assigned to a Baseline Solution of “1”. If the solution includes shipments that are cheaper to deliver with direct shipping (based on the Direct Shipping Cost in the Shipments table), these shipments are assigned to a Baseline Solution of “0”.

If you have defined records in the Shipment Constraints table, you can specify the Baseline Solution value.

Scenario

Table: VRPOutputBaselineShipments

Internal Name: Not Applicable (Scenario column not in table)

The scenario for which the output data was generated.

Baseline Solution

Table: VRPOutputBaselineShipments

Internal Name: BaselineSolutionID

The Baseline Solution from the Shipment Constraints input table. Use this field to identify sets of baseline shipments.

If you have not defined a Baseline Solution in the Shipment Constraints table, or if there are no Shipment Constraints defined, the routed shipments are assigned to a Baseline Solution of “1”. If the solution includes shipments that are cheaper to deliver with direct shipping (based on the Direct Shipping Cost in the Shipments table), these shipments are assigned to a Baseline Solution of “0”.

Shipment

Table: VRPOutputBaselineShipments

Internal Name: ShipmentID

The identifier of the baseline shipment.

Route ID

Table: VRPOutputBaselineShipments

Internal Name: RouteID

The identifier of the route used by the shipment, from the Route table.

Route Start Date

Table: VRPOutputBaselineShipments

Internal Name: RouteStartDate

Displays the start date and time of the route on which the baseline shipment is routed.

Pickup Sequence

Table: VRPOutputBaselineShipments

Internal Name: PickupSequenceId

Displays the pickup sequence number of the baseline shipment on the route.

Delivery Sequence

Table: VRPOutputBaselineShipments

Internal Name: DeliverySequenceId

Displays the delivery sequence number of the baseline shipment on the route.

Asset Name

Table: VRPOutputBaselineShipments

Internal Name: AssetName

The name of the asset used for route on which the baseline shipment is routed.

Asset Site Name

Table: VRPOutputBaselineShipments

Internal Name: AssetSiteName

Displays the name of the site at which the asset used for the route was located.

Tour

Table: VRPOutputBaselineShipments

Internal Name: TourId

The name of the tour on which the baseline shipment is routed.

Route Sequence

Table: VRPOutputBaselineShipments

Internal Name: RouteSequenceId

Displays the sequence number of the route as defined on the Tour.

Force Ship Direct

Table: VRPOutputBaselineShipments

Internal Name: ForceShipDirect

Indicates whether or not the baseline shipment was defined with Force Ship Direct. When this field is Yes, it means the solver forced the shipment to use the Direct Shipping Method. When set to No, the solver used a multi-stop routing method. This field is also set to Yes for regular shipments that are cheaper to send direct based on the Direct Shipping Cost in the Shipments table.

Linehaul Route

Table: VRPOutputBaselineShipments

Internal Name: LinehaulRouteId

If you used the Hub Optimization problem type, this field displays the route ID for the linehaul route into or out of the hub.

Hub

Table: VRPOutputBaselineShipments

Internal Name: HubID

If you used the Hub Optimization problem type, this field displays the name of the hub through which the baseline shipment is routed.

Pickup Location

Table: VRPOutputBaselineShipments

Internal Name: PickupLocationID

Displays the location at which the baseline shipment was picked up.

Delivery Location

Table: VRPOutputBaselineShipments

Internal Name: DeliveryLocationID

Displays the location at which the baseline shipment was delivered.

Scenario ID

Table: VRPOutputBaselineShipments

Internal Name: ScenarioID

The identifier of the scenario for which the output data was generated.

Sub-Scenario ID

Table: VRPOutputBaselineShipments

Internal Name: StepNumber

The identifier of the sub-scenario, if applicable, for which the output data was generated.

Last modified: Wednesday May 15, 2024

Is this useful?

Yes No