Production Count Constraints

Internal Table Name: AggregateProductionCountConstraints

Expression

Technology: NO

Table: AggregateProductionCountConstraints

Internal Name: ExpressionName

Type: Short Text (100)

This is an optional name for the Production Count Constraint. You can then use the Production 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.

Period

Technology: NO

Table: AggregateProductionCountConstraints

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 or when this field is set to (ALL_Periods) (All), the constraint will apply 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.

Site

Technology: NO

Table: AggregateProductionCountConstraints

Internal Name: SiteName

Type: Short Text (100)

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

Select the site to which this aggregate production constraint applies. If this field is left blank, the constraint applies to all sites that produce product: “the constraint is then aggregated over all 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: AggregateProductionCountConstraints

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 production count constraint applies. When this field is left blank, the constraint applies to all products that are made in production at this site: "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.

Constraint Value

Technology: NO

Table: AggregateProductionCountConstraints

Internal Name: CountValue

Type: Number (Integer)

Enter the number of different Period – Site – Product combinations for production, based on the values entered for Period, Site and Product . Its use is determined by the constraint type. 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 Site 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 Site value:

If Product 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 Product value:

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

Constraint Type

Technology: NO

Table: AggregateProductionCountConstraints

Internal Name: CountType

Type: Short Text (50)

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

Choose the production 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.

Site Aggregated

Technology: NO

Table: AggregateProductionCountConstraints

Internal Name: SiteAggregated

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 Site Aggregated to “No”, only one Site is used.

At least one of the “Aggregated” fields in the Production 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: AggregateProductionCountConstraints

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 Production 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: AggregateProductionCountConstraints

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 Production 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: AggregateProductionCountConstraints

Internal Name: AggregateProductionCountConstraintStatus

Type: Short Text (25)

One of Include, Exclude.

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

Notes

Technology: NO

Table: AggregateProductionCountConstraints

Internal Name: AggregateProductionCountConstraintsNotes

Type: Memo

Enter optional descriptive notes about the production count constraint.