Flow Allocation Constraints

Internal Table Name: DistributionAllocationConstraints

Use this table to formulate allocation constraints relating the two flow expressions in terms of percent. The first flow expression is defined by Source, Destination, Product, Period, and Mode column while the filter flow expression is constructed by Source Filter, Destination Filter, Product Filter, Period Filter, and Mode Filter.

The constraint type can be:

• Min – First flow expression is at least X % of the filter flow expression.

• Max – First flow expression is at most X % of the filter flow expression.

• Fixed – First flow expression is fixed at X % of the filter flow expression.

• Cond_Min – First flow expression is either at least X % or 0 % of the filter flow expression.

• Cond_Fixed – First flow expression is either fixed at X % or 0 % of the filter flow expression.

For example, you can define a constraint that requires:

The flow quantity through the sites specified by MexicoSites must be at least 40% of the flow quantity through all sites.

In this case you define a set containing the sites in Mexico and evaluate it against a filter column where the value contains all sites. The constraint is defined with a Percentage (the set compared to the filter), a constraint Type (Min, Max, Fixed, Cond_Min, Cond_Fixed) and a Basis (Quantity, Weight, or Volume).

Expression Name

Technology: NO

Table: DistributionAllocationConstraints

Internal Name: Expression

Type: Short Text (100)

This is an optional name for the Flow Allocation Constraint.

Period

Technology: NO

Table: DistributionAllocationConstraints

Internal Name: PeriodName

Type: Short Text (100)

One of (ALL_Periods), period name, period group, period filter.

Select the period(s) to be added to the first flow expression. This is used with the Period Filter, Percent, Type and Basis to define the constraint in terms of periods. For example, assume the Flow Allocation Constraint has the following populated:

The flow quantity during the periods specified by Q1 has to be at least 60% of the flow quantity in all periods.

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 group/filter
• (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: DistributionAllocationConstraints

Internal Name: SourceName

Type: Short Text (100)

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

Select the source site(s) or customer(s) to be added to the first flow expression. This is used with the Source Filter, Percent, Type and Basis to define the constraint in terms of source sites. For example, assume the Flow Allocation Constraint has the following populated:

The flow quantity through the sites specified by MexicoSites has to be at least 40% of the flow quantity through all sites.

When there is no value provided for Source, it is effectively using 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/filter
• (Each) to apply the constraint per group/filter 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: DistributionAllocationConstraints

Internal Name: DestinationName

Type: Short Text (100)

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

Select the destination site(s) or customer(s) to be added to the first flow expression. This is used with the Destination Filter, Percent, Type and Basis to define the constraint in terms of destination sites. For example, assume the Flow Allocation Constraint has the following populated:

The flow quantity to the customers specified by MexicoCustomers has to be at least 40% of the flow quantity to all customers.

When there is no value provided for Destination, it is effectively using all destination locations.

If you use a filter/group, you actively select how to apply the constraint:

• (All) to apply the constraint to the full group/filter
• (Each) to apply the constraint per group/filter 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: DistributionAllocationConstraints

Internal Name: ProductName

Type: Short Text (100)

One of (ALL_Products), product name, product group, product filter.

Select the product(s) to be added to the first flow expression. This is used with the Product Filter, Percent, Type and Basis to define the constraint in terms of products. For example, assume the Flow Allocation Constraint has the following populated:

The flow quantity of products specified by CaseProducts has to be at least 55% of the flow quantity of all products.

When there is no value provided for Product, it is effectively using 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/filter
• (Each) to apply the constraint per group/filter 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: DistributionAllocationConstraints

Internal Name: ModeName

Type: Short Text (100)

One of (ALL_Modes), mode name, mode group, mode filter.

Select the mode(s) to be added to the first flow expression. This is used with the Mode Filter, Percent, Type and Basis to define the constraint in terms of modes. For example, assume the Flow Allocation Constraint has the following populated:

The flow quantity using the modes specified by TruckModes has to be at least 40% of the flow quantity using all modes.

When there is no value provided for Mode, it is effectively using all modes.

If you use a filter/group, you actively select how to apply the constraint:

• (All) to apply the constraint to the full group/filter
• (Each) to apply the constraint per group/filter 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.

Period Filter

Technology: NO

Table: DistributionAllocationConstraints

Internal Name: PeriodFilter

Type: Short Text (100)

One of (ALL_Periods), period name, period group, period filter.

Select the period set that the Period will be evaluated against. The Period Filter is treated as (All). This is added to the filter flow expression. It is used with the Period, Percent, Type and Basis to define the constraint in terms of periods. For example, you can define a constraint that requires:

The flow quantity during the periods specified by Q1 must be at least 60% of the flow quantity in all periods.

In this case the Period Filter is the set containing all periods.

Source Filter

Technology: NO

Table: DistributionAllocationConstraints

Internal Name: SourceFilter

Type: Short Text (100)

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

Select the source location set that the Source will be evaluated against. The Source Filter is treated as (All). This is added to the filter flow expression. It is used with the Source, Percent, Type and Basis to define the constraint in terms of source sites. For example, you can define a constraint that requires:

The flow quantity through the sites specified by MexicoSites must be at least 40% of the flow quantity through all sites.

In this case the Source Filter is the set containing all sites.

Destination Filter

Technology: NO

Table: DistributionAllocationConstraints

Internal Name: DestinationFilter

Type: Short Text (100)

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

Select the destination location set that the Destination will be evaluated against. The Destination Filter is treated as (All). This is added to the filter flow expression. This will be used with the Destination, Percent, Type and Basis to define the constraint in terms of destination locations. For example, you can define a constraint that requires:

The flow quantity to the customers specified by MexicoCustomers must be at least 40% of the flow quantity to all customers.

In this case the Destination Filter is the set containing all customers.

Product Filter

Technology: NO

Table: DistributionAllocationConstraints

Internal Name: ProductFilter

Type: Short Text (100)

One of (ALL_Products), product name, product group, product filter.

Select the product set that the Product will be evaluated against. The Product Filter is treated as (All). This is added to the filter flow expression. It is used with the Product, Percent, Type and Basis to define the constraint in terms of products. For example, you can define a constraint that requires:

The flow quantity of products specified by CaseProducts must be at least 55% of the flow quantity of all products.

In this case the Product Filter is the set containing all products.

Mode Filter

Technology: NO

Table: DistributionAllocationConstraints

Internal Name: ModeFilter

Type: Short Text (100)

One of (ALL_Modes), mode name, mode group, mode filter.

Select the mode set that the Mode will be evaluated against. The Mode Filter is treated as (All). This is added to the filter flow expression. It is used with the Mode, Percent, Type and Basis to define the constraint in terms of modes. For example, you can define a constraint that requires:

The flow quantity using the modes specified by TruckModes must be at least 40% of the flow quantity using all modes..

In this case the Mode Filter is the set containing all modes.

Percent

Technology: NO

Table: DistributionAllocationConstraints

Internal Name: Percent

Type: Short Text (100)

RNE Eligible

Enter the percentage (0 to 100) the populated entities (Period, Source, Destination, Product, Mode) are applied to their corresponding filters, based on the Type. For example, if you want the flow quantity of Product value to be exactly 40% of the Product Filter value, you could create a constraint such as:

Type

Technology: NO

Table: DistributionAllocationConstraints

Internal Name: Type

Type: Short Text (25)

One of Min, Cond_Min, Max, Fixed, Cond_Fixed.

Choose the constraint type. This defines how the constraint Percent is used.

• Min – First flow expression is at least X % of the filter flow expression.

• Max – First flow expression is at most X % of the filter flow expression.

• Fixed – First flow expression is fixed at X % of the filter flow expression.

• Cond_Min – First flow expression is either at least X % or 0 % of the filter flow expression.

• Cond_Fixed – First flow expression is either fixed at X % or 0 % of the filter flow expression.

Status

Technology: NO

Table: DistributionAllocationConstraints

Internal Name: Status

Type: Short Text (10)

One of Include, Exclude.

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

Default: Include

Notes

Technology: NO

Table: DistributionAllocationConstraints

Internal Name: Notes

Type: Short Text (100)

Enter optional descriptive notes about the flow allocation constraint.