This settings document explains how to execute a move order between locations using a planned move order.
These settings determine if the planned move order will be released automatically or manually to a requisition order (move order).
Used for defining the rules for filling smaller workstation locations from the main location (buffer location).
|Program ID/Panel||Field||The field indicates …|
… the storage method for each item/warehouse and determines how the item is distributed at different locations.
The valid alternatives are:
1 = Single location
2 = Multiple location
3 = Multiple location where reorder points are used.
If alternative 1 is specified, the item can only be stored at one approved location (status 2). This must be specified for each item/warehouse.
If alternative 2 is specified, the item can be stored in an unlimited number of locations.
Alternative 3 is the same as alt. 2, but in addition certain combinations contain a reorder point level that is automatically monitored.
…. how allocation is carried out for each item/warehouse combination.
For replenishment orders (transaction type 92), allocation methods 3 or 4 are automatically switched to allocation method 2.
|(MMS002/G)||Second allocation method||
… the allocation method to use if the first allocation method does not allocate enough quantity.
Note: The 'Allocation method' field must be set to 2, in order to make 'Second allocation method' to work.
|(CRS200)||Stock transaction type||
… that you can distinguish different stock transactions in M3. For this setting the following transaction type is used:
92 = Replenishment move order issue.
|(CRS783)||01 Order type||
… an order type, which is a combined identity for a number of rules that control how an order will be treated at entry and beyond in the order flow.
Order types are defined per order category in the following programs:
Order Category Program
1 = Manufacturing Order PMS120
2 = Purchase Order PPS095
3 = Customer Order OIS010
4 = Requisition Order CRS200
5 = Distribution Order CRS200
7 = Service Order SOS010
8 = Project Order POS010.
Enter the order type (transaction type 92) created in (CRS200).
|(CRS783)||05 Automatic update of replenishment order||
… whether replenishment orders should be
|(MMS065/B)||Location||… the location to which the items should be moved.|
|(MMS065/B)||From date||… the date from which the registered data becomes valid.|
… which method is to be used to fill a location when a shortage occurs.
The valid alternatives are:
1 = Kanban
2 = Reorder point with automatic control
3 = Manual replenishment without automatic control.
Method 2 means that M3 automatically generates a requisition order when stock reaches the reorder point, according to the rules defined in (CRS783)
|(MMS065/E)||Order type||… an order type entered here will override the order type entered in (CRS783).|
… the quantity that initiates the reorder process.
When the item location's on-hand balance is equal to or less than the reorder point, replenishment of the item location's order quantity is initiated.
|(MMS065/E)||Critical reorder point||… the critical stock level. This should be a value less than the reorder point value.|
… the order quantity, which is to be used for replenishment of the item's location.
The order quantity method determines how the quantity is to be calculated.
|(MMS057/E)||Exclude for order category||
… order categories that are excluded from the stock location type allocation table. The allocation table controls allocation according to location type.
0 = 'No automatic update of planned orders'. You have to release the planned order to a requisition order manually in 'Planned Move Order. Process' (MMS170).
1 = 'Yes, Automatic update of planned orders'. The auto-start job (MMS940) creates a requisition order from the planned order.
Infor recommends that you set this field to 1.