Site Constraints

Internal Table Name: AggregateSiteConstraints

Site Constraints behave as count constraints, similar to Production Count Constraints. These act as "number of constraints”, enabling you to limit the number of sites used within a model structure.

Expression

Technology: NO

Table: AggregateSiteConstraints

Internal Name: ExpressionName

Type: Short Text (100)

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

Internal Name: PeriodName

Type: Short Text (50)

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

This field is not required, however if you are running a multi-period model, it will consider the entire model horizon if left blank. This field allows you to enter a specific period for the site requirement. In multi-period models, once a potential site has been opened, it cannot be closed.

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

Internal Name: SiteName

Type: Short Text (100)

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

Allows you to choose from the available sites or site sets. For the model to be feasible, included sites must be set to Consider. If you use a filter/group, you actively select how to apply the constraint:

• (All) to apply the constraint to the full group. For Site Constraints, the constraint on the Site column should be set using (All).
• (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: AggregateSiteConstraints

Internal Name: OpenSitesValue

Type: Number (Long Integer)

Specify the number of sites. This number is used as a constraint based on the Constraint Type value.

Constraint Type

Technology: NO

Table: AggregateSiteConstraints

Internal Name: OpenSitesType

Type: Short Text (100)

One of Min, Max, Fixed, Define.

Specify whether the constraint Constraint Value represents:

• Min – The minimum number of sites that must be used.
• Max – The maximum number of sites that can be used.
• Fixed – The number of sites that must be used.
• 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.

Status

Technology: NO

Table: AggregateSiteConstraints

Internal Name: AggregateSiteConstraintStatus

Type: Short Text (25)

One of Include, Exclude.

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

Notes

Technology: NO

Table: AggregateSiteConstraints

Internal Name: AggregateSiteConstraintsNotes

Type: Memo

Enter optional descriptive notes about the site constraint.