Production Constraints

Internal Table Name: AggregateProductionConstraints

Expression

Technology: NO

Table: AggregateProductionConstraints

Internal Name: ExpressionName

Type: Short Text (100)

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

Internal Name: PeriodName

Type: Short Text (50)

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

Select the period to 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: AggregateProductionConstraints

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 will apply to. 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: AggregateProductionConstraints

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 Constraint applies. When this field is left blank, the constraint applies to all products that are being produced at this particular site(s): “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.

BOM

Technology: NO

Table: AggregateProductionConstraints

Internal Name: BOMName

Type: Short Text (100)

One of (ALL_BOMs) (Each), (ALL_BOMs) (All), bom name, bom group.

Select the Bill Of Material to which the Aggregate Production Constraint applies. When this field is left blank, the constraint applies to all BOMs that are being used at this particular site: “the constraint is aggregated over all bills of materials”. 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: AggregateProductionConstraints

Internal Name: ProductionRequirement

Type: Short Text (100)

Enter the amount of product required to be produced. 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 Production Constraint Type and Production Constraint Period.

Constraint Type

Technology: NO

Table: AggregateProductionConstraints

Internal Name: ProductionRequirementType

Type: Short Text (50)

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

Enter the type of production constraint placed, based on the Constraint Value specified:

• Min – At least X must be produced
• Max – At most X may be produced
• Fixed – X must be produced
• Cond Min – Either produce at least X units or produce none at all
• 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.

Default: Min

Constraint Period

Technology: NO

Table: AggregateProductionConstraints

Internal Name: ProductionRequirementPeriod

Type: Short Text (50)

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

Enter the time period over which the specified Constraint Value must be satisfied.

Status

Technology: NO

Table: AggregateProductionConstraints

Internal Name: AggregateProductionConstraintStatus

Type: Short Text (25)

One of Include, Exclude.

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

Notes

Technology: NO

Table: AggregateProductionConstraints

Internal Name: AggregateProductionConstraintsNotes

Type: Memo

Enter optional descriptive notes about the production constraint.