Automatic Allocation

Outcome

• Balance IDs are allocated to order lines.
• Allocated order lines get status 33=Allocated.

The primary use for automatic allocation is to be able to release orders for picking, packing and delivery to the customer as fast as possible. The process can also be used in any of the following cases:

• Prioritization in shortage situations
• More user defined rules for allocation of stock
• Customer orders can be allocated from one location and manufacturing orders from another location.
• The allocation table controls which balance identities can be selected for automatic allocation for a specific requirement based on location type.
• For the same item/warehouse: Order lines can be allocated in planning date or order priority/planning date sequence.
• The demand time fence can be overridden by order priority.
• Orders can be manually or automatically released for allocation.
• The allocation control selection tables control which stock can be allocated to specific requirements according to user defined rules.

The following changes are made in M3:

• Completely allocated order lines have their order status raised to 33.
• The allocated balance ID is stored in the MITLOC file.
• The allocated order, order line and so on are stored in the MITALO file.
• Soft allocated balance IDs (reserved) are stored in the MITBAL file.

Before you start

Settings for allocations must be made according to the selected allocation method described in this document. For further information refer to the following documents:

• Basic Settings for Automatic Allocation
• Create View and Sorting Order in (MWS410)
• Create Location Type Table (MMS057)
• Settings for Allocation Control Per Balance ID (Allocation Table Control)

Purpose

The primary use of automatic allocation is to be able to release orders for picking, packing and delivery to the customer as fast as possible.

Workflow in M3

1. Activate Allocation on Item/Warehouse

   When entering an order into the system, a reservation of the ordered item and quantity is made.

   Many events activate an auto-allocation. Among them are:

   • A new requirement is entered.
   • There is a change in the allocable balance.
   • MRP detects that the DTF date has been reached or exceeded on a demand that was previously outside t he DTF.

2. Select Orders

   

   'Allocation' (MMS920) selects the records in the MITPLO file with the need date (delivery date) inside the demand time fence. Specific demand time fence lengths for different order priorities can also be specified. A third criterion for select orders is order sequence, which can be allocation by planning date or by order priority then planning date. All of these parameters are defined in 'Warehouse. Open' (MMS005).

   If manual release for allocation is selected in 'Dispatch Policy. Open' (MWS010), then manual allocation release is done in 'Delivery Toolbox. Open' (MWS410).

   Automatic allocation is done inside the demand time fence and according to specific rules such as priority and sequence. How this is done is explained in the Setting document for allocation.

   Deallocation (MMS922) is now performed when the planning date is moved outside the demand time fence (DTF). Manual allocations and stock entrance allocations (order initiated, pre-allocations and cross-docking) are not taken into consideration. After the deallocation, the auto-allocation is triggered to allocate the deallocated quantity according to standard allocation rules.

   

3. Select Balance IDs and Sequence

   In (MMS921), balance IDs are placed in the correct sequence depending on whether user defined rules have been specified in 'Item. Connect Stock Location Type'(MMS057) and/or 'Allocation Control Selection Field. Open' (MMS123).

   Balance IDs are then checked to see if they are valid for use for each requirement according to the rules set in 'Allocation Control Selection Field. Open' (MMS123). Also the various allocations methods are managed here. These methods are defined in (MMS002/G).

4. Allocate

   Allocation is performed in 'Manage Allocation' (MMMNGALO). This create the allocation that updates balance IDs, the order lines and the material plan. The order status for a completely allocated order is 33.

Analyze allocation failure

Allocation analysis for automatic allocation is available from (MMS080) and (OIS301) via option 40. Allocation analysis is done in 'Allocation Analysis. Open' (MWS084) and (MWS085). Here you can find why the stock has not been allocated or why allocation control has held an order line. The allocation log is stored in the MMALAH and MMALAD files.

Workflow for automatic allocation with automatic release for allocation

This workflow describes automatic allocation. It describes the same workflow as in the present chapter, but with a different figure.

No manual actions are needed for the functions described below.

Automatic allocation is done inside the demand time fence according to user defined rules such as priority and sequence, if there are any.

1. Find All Inside Demand Time Fence (MMS920)

   'Allocation' (MMS920) calculates the demand time fence, activates automatic allocation and selects records to be allocated. This program also retrieves planning data from 'Material Plan. Open' (MMS080), the MITPLO file.

2. Find Balance IDs in Sequence (MMS921)

   In (MMS921), balance IDs are placed in the correct sequence depending on whether user defined rules have been specified in (MMS057) and/or (MMS123).

3. Manage Allocation (MMMNGALO)

   Allocation is performed in (MMMNGALO). Balance IDs, order lines and material plan are updated. The order status for a completely allocated order is 33.