Define Settings for Allocation Priority Model

This document explains how you create and maintain the allocation priority model.

Before you start

The settings for batch allocation must be defined. Refer to these documents:

See Batch Allocation Settings

See Basic Batch Allocation Settings

Follow these steps

Create an object control table

  1. Start 'Available Object Control Parameters. Open' (CMS016). Select Allocation Priority and select option 11=Object table detailed lines.

  2. 'Generic Object Control Table. Open' (CMS017/B) is started.

    Set the 'Panel sequence' field to E (T) 1.

  3. Enter program ID (MMS182).

  4. On the E panel enter:

    • The valid allocation priority model for this object table.
    • Status 20.
    • Priorities from 0 to 9 in the Sequence field. By default, sequence 10 corresponds to priority 0, 20 to priority 1, and so on up to sequence 100, which corresponds to priority 9.
    • The 'Field 1 (2, 3, 4 or 5)' fields with the selected fields from the field group. Press F4 twice to select fields. This starts 'Field Group. Display Permitted Fields' (CRS109).
  5. On the (CRS109/B) panel, in the 'Field group' field, enter MMAP2 – Allocation prio model. Selection.

  6. Select fields and redisplay (CMS017/E).

  7. Press Enter until you start 'Allocation Priority Model Selection Table. Open (MMS182).

Create values for the object control table

  1. On the (MMS182/B) panel, define values for the fields in each priority.

  2. The 'Start value 1 (2, 3, 4 and 5)' fields are the first, second, third, fourth and fifth values to be compared with the contents of a control object. Fill in these fields and open the E panel.

  3. If applicable, enter a valid to date on the E panel.

  4. Enter the allocation priority that should be used for start values.

Parameters to set

Program ID/Panel

Field

The field indicates…

(MMS181/B)

Alloc prio mod

...is the ID of a specific allocation priority model. The ID must first be created in MMS181 to be able to be used in CMS017.

(CMS016/B)

Object control parameter

...the available object control parameter, where you can define your objects and values.

(CMS017/B)

Program name

… the program that is used for the object control table. In this case, enter MMS154 here.

(CMS017/E)

Alloc prio mod

…is the allocation priority model ID. Must exist in MMS181.

(CMS017/E)

Priority

… the sequence in which each information field should be displayed.

To change the sequence, switch the numbers. To add new information fields, enter the numbers and names of the desired information fields.

Example:

To add a new information field between 10 and 20, assign this new field a number between 11 and 19. Press ENTER. The new field is then placed in the correct order.

(CMS017/E)

Field 1, 2, 3, 4, 5

… a field or data element from a specific file.

It is used to create keys or search paths for user-defined tables and also to create the contents of user-defined files.

These fields will be protected if entries are found in (MMS182). That means that you cannot enter these fields if they are 'in use'.

(CMS017/E)

Status

… the status for the generic object control table.

The valid alternatives are:

10 = Preliminary

20 = Definite

90 = Blocked/expired.

(CRS109/B)

Field group

… a grouping of several fields from different files that regulate matrix entries. In this case, the MMAP2 field group will be selected.

Field groups are system-defined and cannot be changed.

(MMS182/B)

Priority

… the table priority from the table in (CMS017). When searching for allocation priority, tables are searched in order of pri-ority for a set of rules that correspond to the specified object values. These sets of rules are displayed below as 1, 2 or 3 fields called the 'Start value 1, 2, 3, 4, 5' field.

(MMS182/B)

Start value 1, 2, 3, 4, 5

… the first, second, third, fourth and fifth valid value to be compared with the contents of a control object. If the contents are greater than or equal to this start value, the record will be accepted.

If there are several start values, the one that is the closest to the lowest value is valid.

Example:

Start value 1 could be 'Product group'. Select a product group by pressing F4=Prompt.

Start value 2 could be 'Item no'. Select an item number by pressing F4.

Start value 3 could be 'Customer no.' Select a customer number by pressing F4.

(MMS182/E)

Allocation priority

…is a value that sets the order of performing allocation between selected demand lines in a specific batch allocation run.

Example 1:

Demand order line 1 will get allocation priority 4000 from one record in MMS182 while demand order line 2 will get allocation priority 2000 from another record in MMS182. The result will be that demand order line 2 will be selected for allocation before demand order line 1.

…is also to be seen as allocation priority group. If distribution method 3 (allocation priority with fair share) is selected in MMS189, then the allocation priority is used as both a priority value (see above) but also as an allocation priority group value.

Example 2:

All demand order lines with the same allocation priority will be seen as one allocation priority group. When batch allocation is run, a validation is performed if allocatable net is enough to fulfill all demand lines within an allocation priority group. If so, all demand lines will be fully allocated as normal. If not, then fair share distribution will be used among these demand order lines to spread the remaining allocatable net. For the following demand order lines (connected to a lower prioritized allocation priority group) will not be allocated at all.

Note: The allocation priority group functionality is only valid if distribution method 3 (allocation priority with fair share) is used.

Outcome

A generic object control table is created with allocation priority.

The following tables are updated:

A generic control table is used to set an allocation priority for each demand order line that is selected to be included in a batch allocation run. These rules are user defined.

Related topics