Flow Count Constraints

Internal Table Name: AggregateFlowCountConstraints

Expression

Technology: NO

Table: AggregateFlowCountConstraints

Internal Name: ExpressionName

Type: Short Text (100)

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

• an Expression Constraint by specifying the Expression 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.
  When you use a group name for fields such as Source, Destination and Product, unique expression names are generated when the model is run.

Period

Technology: NO

Table: AggregateFlowCountConstraints

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: AggregateFlowCountConstraints

Internal Name: SourceSite

Type: Short Text (100)

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

Select the source site 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 site 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: AggregateFlowCountConstraints

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 to which this aggregate flow constraint applies. When this field is set to (ALL_Sites) or (ALL_Customers), the constraint applies to all destinations 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: AggregateFlowCountConstraints

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 count constraint applies. When this field is left blank, the constraint applies to all products that flow between the source and destination: "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: AggregateFlowCountConstraints

Internal Name: Mode

Type: Short Text (100)

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

Select the mode to which this aggregate flow constraint applies. 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: AggregateFlowCountConstraints

Internal Name: CountValue

Type: Number (Integer)

Enter the number of different Period – Source – Destination – Product combinations for product flow, based on the values entered for Period, Source, Destination and Product. Its use is determined by the count type. Count refers to the number of individual values for those fields where “Aggregated” is “No”. For example, assume you have the following records:

You set the Constraint Type to Max and the Constraint Value to 1.

If Source Aggregated is the only “aggregated” field set to “No” (all others are “Yes”), the results could be like the following (depending on costs and other constraints) - there is only one unique Source value:

If Destination Aggregated is the only “aggregated” field set to “No” (all others are “Yes”), the results could be like the following - there is only one unique Destination value:

If both Source Aggregated and Destination Aggregated are set to “No”, the results could be like the following, with only one unique Source and one unique Destination:

Additionally, you can control the aggregation at the Product, Mode and Period Name level as needed.

Constraint Type

Technology: NO

Table: AggregateFlowCountConstraints

Internal Name: CountType

Type: Short Text (50)

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

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

• Min
• Max
• Fixed
• Cond Min
• Define – Network Optimization does not use the Constraint Value to satisfy the constraint. Instead, the requirement value is specified in the Expression Constraint. See Considerations for grouped constraints for additional information.

Source Aggregated

Technology: NO

Table: AggregateFlowCountConstraints

Internal Name: SourceSiteAggregated

Type: Bit

One of Yes, No. (Actual database values are 1,0.)

When deciding how to set the “Aggregated” fields, for fields you want to use for the Count Value, set those to “No”. The binary decision variable is created for the fields that are not aggregated. For example, if the Count Value = 1 and you set Source Aggregated to “No”, only one Source is used.

At least one of the “Aggregated” fields in the Flow Count Constraint must be set to Yes and at least one of the “Aggregated” fields must be set to No for the constraint to be applied.

Default: Yes

Destination Aggregated

Technology: NO

Table: AggregateFlowCountConstraints

Internal Name: DestinationSiteAggregated

Type: Bit

One of Yes, No. (Actual database values are 1,0.)

When deciding how to set the “Aggregated” fields, for fields you want to use for the Count Value, set those to “No”. The binary decision variable is created for the fields that are not aggregated. For example, if the Count Value = 1 and you set Destination Aggregated to “No”, only one Destination is used.

At least one of the “Aggregated” fields in the Flow Count Constraint must be set to Yes and at least one of the “Aggregated” fields must be set to No for the constraint to be applied.

Default: Yes

Product Aggregated

Technology: NO

Table: AggregateFlowCountConstraints

Internal Name: ProductAggregated

Type: Bit

One of Yes, No. (Actual database values are 1,0.)

When deciding how to set the “Aggregated” fields, for fields you want to use for the Count Value, set those to “No”. The binary decision variable is created for the fields that are not aggregated. For example, if the Count Value = 1 and you set Product Aggregated to “No”, only one Product is used.

At least one of the “Aggregated” fields in the Flow Count Constraint must be set to Yes and at least one of the “Aggregated” fields must be set to No for the constraint to be applied.

Default: Yes

Mode Aggregated

Technology: NO

Table: AggregateFlowCountConstraints

Internal Name: ModeAggregated

Type: Bit

One of Yes, No. (Actual database values are 1,0.)

When deciding how to set the “Aggregated” fields, for fields you want to use for the Count Value, set those to “No”. The binary decision variable is created for the fields that are not aggregated. For example, if the Count Value = 1 and you set Mode Aggregated to “No”, only one Mode is used.

At least one of the “Aggregated” fields in the Flow Count Constraint must be set to Yes and at least one of the “Aggregated” fields must be set to No for the constraint to be applied.

Default: Yes

Period Aggregated

Technology: NO

Table: AggregateFlowCountConstraints

Internal Name: PeriodAggregated

Type: Bit

One of Yes, No. (Actual database values are 1,0.)

When deciding how to set the “Aggregated” fields, for fields you want to use for the Count Value, set those to “No”. The binary decision variable is created for the fields that are not aggregated. For example, if the Count Value = 1 and you set Period Aggregated to “No”, only one Period is used.

At least one of the “Aggregated” fields in the Flow Count Constraint must be set to Yes and at least one of the “Aggregated” fields must be set to No for the constraint to be applied.

Default: Yes

Status

Technology: NO

Table: AggregateFlowCountConstraints

Internal Name: AggregateFlowCountConstraintStatus

Type: Short Text (25)

One of Include, Exclude.

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

Default: Include

Notes

Technology: NO

Table: AggregateFlowCountConstraints

Internal Name: AggregateFlowCountConstraintsNotes

Type: Memo

Enter optional descriptive notes about the flow count constraint.