Flow Constraints

Internal Table Name: AggregateFlowConstraints

Use this table to define constraints for specific Period-Source-Destination-Product-Mode combinations.

Keep in mind that 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 Shipments for additional information.

Expression

Technology: NO

Table: AggregateFlowConstraints

Internal Name: ExpressionName

Type: Short Text (100)

This is an optional name for the Flow Constraint. You can then use the Flow Constraint in:

• an Expression Constraint by specifying the Expression Name for either the Expression 1 or Expression 2 value. This enables you to combine constraints.
• an Expression Based Cost by using this value in the Expression field. This enables you to defined fixed and variable cost components that are incurred as a result of the constraint.

Period

Technology: NO

Table: AggregateFlowConstraints

Internal Name: PeriodName

Type: Short Text (50)

One of (ALL_Periods) (All), (ALL_Periods) (Each), period name, period group.

Select the period which the constraint will apply to. If there are no Periods specified in the model, you can select (ALL_Periods) (All) to apply the constraint to the planning horizon.

In a multi-period model, if you select no value for Period, it will behave the same as if you select (ALL_Periods) (All) and apply the constraint across the planning horizon. In order to ensure the correct behavior, Coupa recommends that you select the specific period or, when using (ALL_Periods) or another period filter/group, you actively select how to apply the constraint:

• (All) to apply the constraint to the full horizon/group
• (Each) to apply the constraint per period

If you are setting the values outside the Supply Chain Guru X or Modeler user interface, see Controlling Each and All through the model database.

Source

Technology: NO

Table: AggregateFlowConstraints

Internal Name: SourceSite

Type: Short Text (100)

One of (ALL_Sites) (Each), (ALL_Sites) (All), site name, site group.

Select the source site of the transportation lane to which this aggregate flow constraint applies. When this field is set to (ALL_Sites), the constraint applies to all sites that source the specified destination location with specified product through specified mode: "the constraint is aggregated over all source sites". If you use a filter/group, you actively select how to apply the constraint:

• (All) to apply the constraint to the full group
• (Each) to apply the constraint per group member

If you are setting the values outside the Supply Chain Guru X or Modeler user interface, see Controlling Each and All through the model database.

Destination

Technology: NO

Table: AggregateFlowConstraints

Internal Name: DestinationSite

Type: Short Text (100)

One of (ALL_Sites) (Each), (ALL_Sites) (All), (ALL_Customers) (Each), (ALL_Customers) (All), site name, site group, customer name, customer group.

Select the destination site of the transportation lane to which this aggregate flow constraint applies. When this field is set to (ALL_Sites) or (ALL_Customers), the constraint applies to all destination sites or customers respectively that are sourced from the specified source site with specified product through specified mode: "the constraint is aggregated over all destination sites". If you use a filter/group, you actively select how to apply the constraint:

• (All) to apply the constraint to the full group
• (Each) to apply the constraint per group member

If you are setting the values outside the Supply Chain Guru X or Modeler user interface, see Controlling Each and All through the model database.

Product

Technology: NO

Table: AggregateFlowConstraints

Internal Name: ProductName

Type: Short Text (100)

One of (ALL_Products) (Each), (ALL_Products) (All), product name, product group.

Select the product to which the aggregate flow constraint applies. When this field is left blank, the constraint applies to all products that are transported over this lane: "the constraint is aggregated over all products". If you use a filter/group, you actively select how to apply the constraint:

• (All) to apply the constraint to the full group
• (Each) to apply the constraint per group member

If you are setting the values outside the Supply Chain Guru X or Modeler user interface, see Controlling Each and All through the model database.

Mode

Technology: NO

Table: AggregateFlowConstraints

Internal Name: Mode

Type: Short Text (100)

One of (ALL_Modes) (Each), (ALL_Modes) (All), mode name, mode group

Specify which mode of a transportation lane the constraint applies. This field can also be left blank, in which case the constraint is aggregated over all transportation modes with the specified Source Site - Destination Site - Product (in case the constraint is product-specific) combination.

If you do not have Modes defined in your model, leave the Mode field blank. Selecting "(ALL_Modes)" in this case prevents Flow Constraints from being written, as there are no modes to apply the constraint to. If you use a filter/group, you actively select how to apply the constraint:

• (All) to apply the constraint to the full group
• (Each) to apply the constraint per group member

If you are setting the values outside the Supply Chain Guru X or Modeler user interface, see Controlling Each and All through the model database.

Constraint Value

Technology: NO

Table: AggregateFlowConstraints

Internal Name: FlowRequirement

Type: Short Text (100)

Enter the amount of product required for shipment from source site to destination site. 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. Its use is determined by other flow requirement fields listed below; Constraint Type, and Constraint Period. Flow refers to the amount of product moved from source site to destination site in a given time period.

Constraint Type

Technology: NO

Table: AggregateFlowConstraints

Internal Name: FlowRequirementType

Type: Short Text (50)

One of Min, Cond Min, Max, Fixed, Define.

Choose the flow constraint type. This defines how the Constraint Value is used.

• Min – At least X units must flow
• Max – At most X units may flow
• Fixed – X units must flow
• Cond Min – Either flow at least X units or flow none at all
  The conditional minimum flow establishes that, in order to use this source site - destination site combinations for any shipments, a minimum flow is necessary. Essentially this constraint is similar to saying the flow can be 0 or higher than the minimum.
• Define – Network Optimization does not use the Constraint Vaue to satisfy the constraint. Instead, the requirement value is specified in the Expression Constraint. See Considerations for grouped constraints for additional information.

Default: Min

Constraint Period

Technology: NO

Table: AggregateFlowConstraints

Internal Name: FlowRequirementPeriod

Type: Short Text (50)

One of Period Length, Day, Week, Month (30 Day), Quarter (91 Day), Year.

Choose the period over which the Constraint Value is to be established. When this field is left blank the horizon of the optimization will be used as the Constraint Period.

Status

Technology: NO

Table: AggregateFlowConstraints

Internal Name: AggregateFlowConstraintStatus

Type: Short Text (50)

One of Include, Exclude.

Specify whether or not to include the specific constraint in the model.

Default: Include

Notes

Technology: NO

Table: AggregateFlowConstraints

Internal Name: AggregateFlowConstraintsNotes

Type: Memo

Enter optional descriptive notes about the flow constraint.