Relationship Constraints
Internal Table Name: RelationshipConstraint
This table enables you to optionally define pairs of entities that must be combined on a route and those that cannot be combined on a route. The primary use case for relationship constraints is to force items to be shipped together or to keep them separate. The following combinations are supported:
| Entity A | Entity B | Relationship |
|
Shipment |
Shipment |
Prevent Note: This combination is not supported for Periodic Scheduling and Balancing (Periodic VRP). |
| Shipment | Transportation Asset | Prevent and Force (a Shipment may request more than one Transportation Asset) |
| Product | Product | Prevent |
| Product | Transportation Asset | Prevent and Force (a Product may request more than one Transportation Asset) |
| Site | Transportation Asset | Prevent and Force (a Site may allow more than one Transportation Asset) |
| Site | Site | Prevent |
| Customer | Transportation Asset | Prevent and Force (a Customer may allow more than one Transportation Asset) |
| Customer | Customer | Prevent |
Relationship
Technology: TO
Table: RelationshipConstraint
Internal Name: Relationship
Type: Short Text (50)
One of Force, Prevent.
Set this to Prevent to indicate that Item A must not be combined on a route with Item B. Set this to Force to indicate that Item A must be combined with Item B on a route.
Default: Force
Type A
Technology: TO
Table: RelationshipConstraint
Internal Name: Type_A
Type: Short Text (50)
One of Customers, Products, Shipments, Sites, Transportation Assets.
Select the type of entity for the first part of the relationship constraint. This value will be one of the following:
- Products
- Shipments
- Sites
- Customers
- Transportation Assets
ID Field A
Technology: TO
Table: RelationshipConstraint
Internal Name: IDField_A
Type: Short Text (100)
Select the Shipment, Product, Site, or Asset to be considered with Item B for the Relationship Constraint.
Type B
Technology: TO
Table: RelationshipConstraint
Internal Name: Type_B
Type: Short Text (50)
One of Customers, Products, Shipments, Sites, Transportation Assets.
Select the type of entity for the second part of the relationship constraint. This value will be one of the following:
- Products
- Shipments
- Sites
- Customers
- Transportation Assets
ID Field B
Technology: TO
Table: RelationshipConstraint
Internal Name: IDField_B
Type: Short Text (100)
Select one or more entities of Type B to be considered with Item A for the Relationship Constraint.
Status
Technology: TO
Table: RelationshipConstraint
Internal Name: Status
Type: Short Text (50)
One of Include, Exclude.
Use this field to determine if Transportation Optimization should consider the Relationship Constraints record.
Default: Include
Notes
Technology: TO
Table: RelationshipConstraint
Internal Name: Notes
Type: Short Text (255)
Use this field to include descriptive information for the relationship constraint record.
Last modified: Wednesday May 15, 2024