Settings for Allocation Control Per Balance ID (Allocation Table Control)

This settings document explains how to define an allocation table that is used for automatic allocation and for batch allocation in connection with allocation methods two and five.

Note: If you use batch allocation with fair share you must be aware that the rules you apply here, for controlling balance IDs, and the rules you have set for fair share, to control customer priority, do not interfere with each other.

Outcome

The allocation table determines which balance identities can automatically be allocated for a specific requirement, and from which locations.

The settings can be used for the following:

Allocation table is stored in the MADSET and MADMTX files.

Before you start

Basic settings for automatic allocation must be done. See Basic Settings for Automatic Allocation.

Follow These Steps

Define Allocation Control Fields

  1. Start 'Allocation Control Selection Field. Enter' (MMS123/B).

    The allocation rules determine which stock is to be allocated against which orders, depending on factors related to the order.

    Up to three fields per priority can be selected. Up to ten priorities can be defined.

    Example: For priority one, there are two fields to select from: Warehouse (MWHLO) and 'Customer number' (OACUNO). This determines which warehouse and for which customer numbers there will be specific allocation rules.

    The system starts by looking at priority one to find a match. If no match is found, the system will continue with priority 2 and so on. The valid alternatives for the Status field are:

    10 = Not active

    20 = Active.

  2. Pressing F14 starts 'Allocation Control Selection Table. Open' (MMS124).

Defining Allocation Rules

  1. Start 'Allocation Control Selection Table. Open' (MMS124).

  2. On the (MMS124/B) panel, the values for the selected control fields are entered.

    Example: When an order at Warehouse 010 and Customer 10001 occurs, this rule will be active.

    Note: An allocation selection table is valid for the entire company. If different allocation rules are valid in different warehouses, it is necessary to have "Warehouse" as one of the keys in the priority table in (MMS123).

  3. Rules are defined on the (MMS124/E) panel.

  4. The 'Alloc dev pct', 'Allocation dev years', 'Alloc dev mths', and 'Alloc dev days' fields are only valid for items with lot and expiration date control.

  5. The 'Alloc min pct' field indicates the minimum percentage of the requirement that must be allocated to perform allocation. If this percentage is not reached, no allocation will be performed.

  6. The 'Object parameter' field is used to make a selection of balance identities that can be used in the allocation. If no objects are entered, all balance identities are included in the allocation.

Parameters to Set

Program ID/Panel Field The field indicates …
(MMS123/E) Status

… the status for the allocation control table. The valid alternatives are:

10 = Not activated

20 = Activated.

(MMS123/E) Field 1, 2 ,3

… information that refers to a field or data element from a specific file.

It is used to create keys or search paths for userdefined tables and to create the contents of userdefined files.

(MMS124/B) Priority

… the table priority. Values between 1–10 can be specified.

Example:

If the Warehouse (MOWHLO) and 'Customer number' (OACUNO) fields are specified for priority 1 in (MMS123/E), then these two fields are displayed when priority 1 is selected in (MMS124/B).

If the 'Customer group' (OKCUCL) field is specified for priority 2 in (MMS123/E), then this field is displayed when priority 2 is selected in (MMS124/B).

If an appropriate value is not found on priority 1, then the table with priority 2 is searched and so on. A priority between 1 and 10 can be specified, with 1 being the highest.

(MMS124/B) Value 1, 2 ,3

… the value for the selected control fields.

Example:

If the Warehouse field (MOWHLO) is defined in (MMS123/E) for priority 3, then you select priority 3 in (MMS124/B) and then press F4 with the cursor in the Warehouse field. This starts 'Warehouse. Open' (MMS005). Enter the Warehouse ID you want in the allocation control table.

(MMS124/E) Allocation deviation – percentage

… the percentage of the expiry and sales periods left before the expiry and last sales dates.

Calculating a new expiry/sales date adjusted by this percentage creates the deviation check. The information for the calculation is retrieved from the item/warehouse (MITBAL) file.

The percentage cannot be entered if deviation years, months or days are entered.

The field is only valid for items with lot and expiry date control as defined in (MMS001).

(MMS124/E)

Allocation deviation

  • years
  • month
  • days

… the number of years/month/days left until the expiry and last sales dates (or the number of years/month/days that have passed if the value is negative). The deviation check is based on the date allocation is carried out.

The field is only valid for items with lot and expiry date control.

(MMS124/E) Allocation minimum percentage … the minimum percentage of the requirement that must be allocated to perform allocation. If this percentage is not reached, no allocation will be performed.
(MMS124/E) Object parameter … a selection of balance identities that can be used in the allocation. If no objects are entered, all balance identities are included in the allocation.
Related topics