Settings for Fair Share, Allocation Priority Rules and Allocation Priority with Fair Share

This document explains how you set the batch allocation rules for fair share, allocation priority rules and allocation priority with fair share.

When you use batch allocation, this is the second step for setting up the parameters. The first step is defining the basic batch allocation settings.

Outcome

You have set up the parameters for the batch allocation method you will use in one of these cases:

  • Fair share

    Fair share is used to distribute a fair share to equal priorities when stock shortages occur.

  • Allocation priority rules

    Allocation priority rules are used to prioritize demand order lines when stock shortages occur.

  • Allocation priority with fair share

    Allocation priority model with fair share is used to prioritize demand order lines when stock shortages occur. When allocatable net is not enough to fulfill demand quantity within an allocation priority group (demand lines having same priority according to the model), fair share will be used among those demand lines. This method can be used for customer orders, distribution orders and requisition orders.

    Batch allocation limits are used to validate and adjust the redistributed allocated quantities.

Before you start

Basic batch allocation rules are set. See these documents:

Follow These Steps for Fair Share Settings

Note: The only settings for fair share are the basic batch allocation settings are described in the document, Basic Batch Allocation Settings.

However, every time you run the batch allocation program (MMS189) you have to define some settings. These are described in this section:

  1. Start 'Allocation. Distribute Quantities' (MMS189). The E panel is the opening panel.

    • The 'Planning date' field indicates the date when the scheduled transaction is expected to take place. You can use it to override the demand time fence. If you leave this field blank, then the demand time fence is used for calculating the planning date.
    • Enter the appropriate priority retrieved from the customer order in the 'Priority' From and To fields. The priorities are displayed in the material plan (MMS080). Priority selection is used in cases of shortages.
    • Enter the actual warehouse or warehouses that should be selected in the 'Warehouse' From and To fields.
    • The 'Style no' field indicates a comprehensive term for a number of similar items. This is not mandatory and is frequently used in the fashion industry.
    • Enter the actual item or items that should be batch allocated in the 'Item number' From and To fields.
    • After entering all the desired fields on the E panel, click Next.
    • On the F panel, select the 'Include SCO' check box if demand order lines with supply chain order links should be included in the batch allocation run.
    • Enter '1-Fair share' in the 'Distribution method' field.
    • Select the 'Check allocation limits' check box if batch allocation limits should be validated in the batch allocation run.
    • Adjust maximum allocated quantity.
    • After entering all the desired fields on the F panel, click Next.
  2. Fair share is calculated as:

    (Selected requirements total allocated quantity + Allocable net) (Selected requirements planned quantity)

Follow These Steps for Allocation Priority Rules Settings

Set Priority

  1. To set Priority Per Order Type, start order type:

    • 'Req/Distr Order Type. Open' (CRS200/H)
    • 'CO Type. Update Field Selection' (OIS014/E)
    • 'Manufacturing Order Type. Open' (PMS120/F).
  2. Fill in the 'Default Priority' field. This field indicates priority per order type. It can be overridden by priority per customer (CRS610) or by allocation priority (MMS156, MMS157).

  3. To set Priority Per Customer, start 'Customer. Open' (CRS610). Fill in the Priority field on the F Panel.

Allocation Priority (Calculated According to Various Factors Related to the Customer)

  1. Start 'Settings – Allocation Priority' (MMS156/E).

  2. The 'Factor number' field determines the sequence during the calculation and display of the allocation priority. The factors are entered in an open subfile where the user specifies the factor values (0–99).

  3. Settings for each factor are entered in the 'Field/value' fields.

    These fields contain specific objects, numeric values or specific values, which are displayed in a table in 'Field Group. Display Permitted Fields' (CRS109). The numeric values can be positive or negative. Special values can be set. They are:

    &NPER = Number of periods a customer has purchased

    &RETN = Number of customer returns in a period

    &RETV = Value of customers returns in a period.

  4. The Operand field can be set to *, /, + and -.

    The total sum of the calculation results is the final priority value. The maximum priority value is 999,999 and any value above that is set to 999,999.

Allocation Priority Calculation

  1. Start 'Allocation Priority. Open' (MMS157). On the E panel, indicate the selection for the allocation calculation.

  2. Fill in the From and To fields for 'Customer', 'Customer group' and 'Date' to select the transactions to be included.

  3. Enter the ID of the information that you want to be retrieved in the 'Dataset' field.

  4. Fill in the 'Updated by division' and 'Divided by zero' fields.

  5. Press Enter. The system checks that the dataset exists and includes the following:

    • Status 20 (in the OSSSET-file)
    • Customer number as the first key (in a non-MUC installation)
    • Divisions plus customer number as the first two keys (in a MUC installation)
    • Customer group, if this is selected (in the OSSELE-file).

      The fields used in the calculation (as set in MMS157, file VAPRA) are included in the dataset (OSSELE for values and OSSSEE for other information, such as reason code).

Allocation Priority Model

  1. Start 'Allocation Priority Model. Open' (MMS181) to create a model ID.

  2. Start Object control parameter programs, 'Available Object Ctrl Parameters. Open' (CMS016) and 'Generic Object Control Table. Open' (CMS017) to create an object control selection table for program 'Allocation Priority Model Selection Table. Open' (MMS182). The available objects in the selection table are controlled by field group MMAP2.

  3. In 'Allocation Priority Model Selection Table. Open' (MMS182), set the allocation priority for a specific set of selection object values.

    Note: Low value in the allocation priority field indicates a higher priority.

Batch allocation run

  1. Start 'Allocation. Distribute Quantities' (MMS189).

    • On the E panel, fill in the selections for demand lines.
    • On the F panel, select 'Include SCO' to include demand order lines with supply chain order links to be included in the batch allocation run.
    • Select '2=Allocation prio' in the 'Distribution method' field.
    • Select the 'Check allocation limits' check box if batch allocation limits should be validated.
    • Adjust maximum quantity allocated.
    • Select allocation priority hierarchy in the 'Allocation priority hierarchy' fields.
    • If '6-Alloc prio model' is selected in first 'Allocation priority hierarchy' field, enter a value in the 'Allocation prio model' field.

Follow These Steps for Allocation Priority with Fair Share

Allocation Priority Model

  1. Start 'Allocation Priority Model. Open' (MMS181) to create a model ID.

  2. Start Object control parameter programs 'Available Object Ctrl Parameters. Open' (CMS016) and 'Generic Object Control Table. Open' (CMS017) to create an object control selection table for program 'Allocation Priority Model Selection Table. Open' (MMS182). The available objects in the selection table are controlled by field group MMAP2.

  3. In 'Allocation Priority Model Selection Table. Open' (MMS182), set allocation priority for a specific set of selection object values.

    Note: Low value in the allocation priority field indicates a higher priority.

Batch allocation run

  1. Start 'Allocation. Distribute Quantities' (MMS189).

    • On the E panel, fill in the selections for demand lines.
    • On the F panel, select 'Include SCO' to include demand order lines with supply chain order links in the batch allocation run.
    • Select '3-Prio mod, fair share' in the 'Distribution method' field.
    • Select the 'Check allocation limits' check box if batch allocation limits should be validated.
    • Adjust maximum allocated quantity.
    • Select '6-Alloc prio model' in the first 'Allocation priority hierarchy' field.
    • Enter a value in the 'Allocation prio Model' field.
  2. Within the group of demand lines sharing the same priority (according to the allocation priority model), fair share is calculated as:

    (Selected requirements total allocated quantity + Allocable net) (Selected requirements planned quantity)

Parameters to Set

Program ID/Panel Field The field indicates ...
(MMS189/E) Style

… a comprehensive term for a number of similar items. This is not mandatory and is frequently used in the fashion industry.

Style is set in 'Style. Open' (MMS016), 'Style. Connect Feature' (MMS017), 'Style. Create Item' (MMS276), 'Feature. Open' (PDS055), 'Feature. Distribute Option' (PDS071) and a few more programs.

See documentation 'Style Settings'.

(MMS189E) Planning date … the date when the scheduled transaction is expected to take place. You can use it to override the demand time fence. If you leave this field blank, then the demand time fence is used for calculating the planning date.
(MMS189/E) Priority … the appropriate priority retrieved from the customer order. Priorities are displayed in the material plan (MMS080).
(MMS189/F) Only deallocate … that only deallocation of included demand order lines will be initiated.
(MMS189/F) Include SCO

…whether demand order lines with supply chain order (SCO) links should be included in the batch allocation run.

If this setting is not checked, demand order lines with SCO links will not be processed even if they are included in the selection.

Note: Only demand order lines with an SCO policy that have the setting 'Link existing order' with value 1 or 2 is processed.
(MMS189/F) Distribution method

… how to distribute the allocated quantity. The valid alternatives are:

1 = According to a calculated percentage of ordered quantity (fair share).

2 = According to allocation priority and allocation order.

3 = According to allocation priority with fair share.

(MMS189/F) Allocation priority hierarchy …how to sort the different demand lines before reallocation is done when distribution method 2 or 3 is used.
(MMS189/F) Check allocation limits …if validation of batch allocation limits (MMS154) are to be included

(CRS200)

(OIS014)

(PMS120)

Default priority …priority per order type. It can be overridden by priority per customer (CRS610) or by allocation priority (MMS156, 157).
(CRS610) Priority … the priority per customer.
(MMS156/E) Factor number … the sequence during calculation and display of the allocation priority. The factors are entered in an open subfile where the user specifies the factor values (0–99).
(MMS156/E) Operand … mathematical operation and can be set to *, /, + and -. The calculation results are totaled into the final priority value. The maximum priority value is 999,999 and any value above that is set to 999,999.
(MMS157/E) Dataset

… the contents and search paths for a specific budgeting and/or reporting level for key information from customer orders. Datasets are defined in 'Dataset. Open' (OSS401).

The system checks that the dataset exists and includes the following:

  • Status 20 (in the OSSSET-file) and
  • Customer number as the first key (in a non-MUC installation)
  • Divisions plus customer number as the first two keys (in a MUC installation).
  • Customer group, if this is selected (in the OSSELE-file).

The fields used in the calculation (as set in MMS157, file VAPRA) are included in the dataset (OSSELE for values and OSSSEE for other information, such as reason code).

(MMS157/E) Updated by division

… whether to update the allocation priority per division. The valid alternatives are:

0 = No. The allocation priority should only be updated on the central level. The priority is totaled for selected divisions.

1 = Yes. The allocation priority should be updated per division.

(MMS157/E) Divided by zero

… how divisions should be processed when the denominator equals 0. The valid alternatives are:

0 = The denominator is set to 1.

1 = The quotient is set to 0

2 = The calculation is aborted and the values that have not yet been calculated will not receive any value.

If alternative 2 is selected, values that will use the results of unfinished calculations are left open for manual correction. The results that are already calculated will be used as usual, and the values where they are used will be closed. This alternative should always be used if the result of alternative 0 or 1 is too unpredictable.

You can perform manual division by zero using formula lines with Boolean operands (conditional statements) if none of the above can be used.

(CMS016/E) Object control parameter … if allocation priority model is used as an allocation priority hierarchy. Then object control program MMS182 must be created in CMS016
(CMS017/B) Object control selection table …create a selection table for an allocation priority model.
(MMS181) Allocation priority model. Open …create an allocation priority model ID
(MMS182) Allocation priority model selection table. Open …define which allocation priority to be used for a specific combination of objects from the selection table.
(CMS016/E) Object control parameter … if validation of batch allocation limits is included. Then object control program MMS154 must be created in CMS016
(CMS017/B) Object control selection table …create a selection table for an allocation limit.
(MMS154) Allocation min/max limits Sel Table. Open …define batch allocation limits to be used for a specific combination of objects from the selection table.