|
|
Algorithm
|
Description
|
|
1
|
Storage Locations
|
Put-away looks for locations in the item’s storage location group, or list of SLGs, with the locations selected in popularity code order within each SLG.
|
|
2
|
Empty Storage Locations
|
Put-away looks for empty locations in the item’s storage location group, or list of SLGs, with the locations selected in popularity code order within each SLG.
|
|
3
|
Storage Locations–Merge with Part
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. locations must already contain the item being put away. The locations are selected in popularity code order within each SLG.
|
|
4
|
Storage Locations–Merge with Lot/Serial
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain the lot/serial and item being put away. The locations are selected in popularity code order within each SLG.
|
|
5
|
Storage Locations–Merge with Reference
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain the reference, lot/serial, and item being put away. The locations are selected in popularity code order within each SLG.
|
|
6
|
Storage Locations–Merge with Any
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain inventory and are selected in popularity code order within each SLG.
|
|
7
|
Storage Locations–Merge with Rules
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain inventory and are selected in popularity code order within each SLG. Additional validation is performed to ensure that the merging rules are satisfied.
|
|
8
|
Storage Locations–Merge with Unit of Measure
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain inventory with the alternate UM being put away, and are selected in popularity code order within each SLG.
|
|
9
|
Storage Locations–Merge with UM and Part
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain the item being put away with the same alternate UM as this put away, and are selected in popularity code order within each SLG.
|
|
10
|
Storage Locations–Merge with UM and Rules
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain inventory with the alternate UM being put away, and are selected in popularity code order within each SLG. Additional validation is performed to ensure that the merging rules are satisfied.
|
|
11
|
Storage Locations–Merge with Part and Rules
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain the item being put away. The locations are selected in popularity code order within each SLG. Additional validation is performed to ensure that the merging rules are satisfied.
|
|
15
|
Multi-Item Pallet split and Put-Away
|
When multi-item pallets, this algorithm makes put-away for each of the components of the pallet, and not put-away the pallet as a whole. Each item could eventually go in another location.
|
|
16
|
Multi-Item Pallet split and Put-Away − No Partial
|
When multi-item pallets, this algorithm makes put-away for each of the components of the pallet, and not put-away the pallet as a whole. Each item could eventually go in another location, but for a given item, it must go completely in one single location
|
|
21
|
Replenished Locations
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence.
|
|
22
|
Empty Replenished Locations
|
Put-away looks for empty locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence.
|
|
23
|
Replenished Locations–Merge with Part
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence. Locations must already contain the item being put away.
|
|
24
|
Replenished Locations–Merge with Lot/Serial
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence. Locations must already contain the lot/serial and item being put away.
|
|
25
|
Replenished Locations–Merge with Reference
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence. Locations must already contain the reference, lot/serial, and item being put away.
|
|
26
|
Replenished Locations–Merge with Any
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence. Locations must already contain inventory.
|
|
27
|
Replenished Locations–Merge with Rules
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence. Locations must already contain inventory. Additional validation is performed to ensure that the merging rules are satisfied.
|
|
28
|
Replenished Locations–Merge with Unit of Measure
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence. Locations must already contain inventory with the same alternate UM as this put away.
|
|
29
|
Replenished Locations–Merge with UM and Part
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence. Locations must already contain the item being put away, with the same alternate UM as this put away.
|
|
30
|
Replenished Locations–Merge with UM and Rules
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence. Locations must already contain inventory with the same alternate UM as this put away. Additional validation is performed to ensure that the merging rules are satisfied.
|
|
31
|
Replenished Locations–Merge with Part and Rules
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence. Locations must already contain the item being put away. Additional validation is performed to ensure that the merging rules are satisfied.
|
|
41
|
Reverse-Replenished Locations
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick-level sequence.
|
|
42
|
Empty Reverse-Replenished Locations
|
Put-away looks for empty locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick level sequence.
|
|
43
|
Reverse-Replenished Locations–Merge with Part
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick level sequence. Locations must already contain the item being put away.
|
|
44
|
Reverse-Replenished Locations–Merge with Lot/Serial
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick-level sequence. Locations must already contain the lot/serial and item being put away.
|
|
45
|
Reverse-Replenished Locations–Merge with Reference
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick-level sequence. Locations must already contain the reference, lot/serial, and item being put away.
|
|
46
|
Reverse-Replenished Locations–Merge with Any
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick-level sequence. Locations must already contain inventory.
|
|
47
|
Reverse-Replenished Locations–Merge with Rules
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick-level sequence. Locations must already contain inventory. Additional validation is performed to ensure that the merging rules are satisfied.
|
|
48
|
Reverse-Replenished Locations–Merge with Unit of Measure
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick-level sequence. Locations must already contain inventory with the same alternate UM as this put away.
|
|
49
|
Reverse-Replenished Locations–Merge with UM and Part
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick-level sequence. Locations must already contain the item being put away, with the same alternate UM as this put away.
|
|
50
|
Reverse-Replenished Locations–Merge with UM and Rules
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick-level sequence. Locations must already contain inventory with the same alternate UM as this put away. Additional validation is performed to ensure that the merging rules are satisfied.
|
|
51
|
Reverse-Replenished Locations–Merge with Part and Rules
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick-level sequence. Locations must already contain the item being put away. Additional validation is performed to ensure that the merging rules are satisfied.
|
|
61
|
Storage Locations by Popularity Code
|
Put-away looks for locations in the item’s storage location group, or list of SLGs, with the locations selected in popularity code order within each SLG. Additional validation is performed to ensure that the selected locations are in the correct popularity code range.
|
|
62
|
Empty Storage Locations by Popularity Code
|
Put-away looks for empty locations in the item’s storage location group, or list of SLGs, with the locations selected in popularity code order within each SLG. Additional validation is performed to ensure that the selected locations are in the correct popularity code range.
|
|
63
|
Replenished Locations by Popularity Code
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick level sequence. Additional validation is performed to ensure that the selected locations are in the correct popularity code range.
|
|
64
|
Empty Replenished Locations by Popularity Code
|
Put-away looks for empty locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick-level sequence. Additional validation is performed to ensure that the selected locations are in the correct popularity code range.
|
|
65
|
Storage Locations by Descending Popularity Code
|
Put-away looks for locations in the item’s storage location group, or list of SLGs, with the locations selected in descending popularity code order within each SLG. Additional validation is performed to ensure that the selected locations are in the correct popularity code range.
|
|
66
|
Empty Storage Locations by Descending Popularity Code
|
Put-away looks for empty locations in the item’s storage location group, or list of SLGs, with the locations selected in descending popularity code order within each SLG. Additional validation is performed to ensure that the selected locations are in the correct popularity code range.
|
|
67
|
Replenished Locations by Descending Popularity Code
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in descending popularity code order within each SLG, which are selected in pick-level sequence. Additional validation is performed to ensure that the selected locations are in the correct popularity code range.
|
|
68
|
Empty Replenished Locations by Descending Popularity Code
|
Put-away looks for empty locations in the item’s replenished location groups, with the locations selected in descending popularity code order within each SLG, which are selected in pick-level sequence. Additional validation is performed to ensure that the selected locations are in the correct popularity code range.
|
|
69
|
Merge with Part−Ascending Popularity Code
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain the item being put away. The locations are selected in popularity code order within each SLG. Additional validation is performed to ensure that the selected locations are in the correct popularity code range.
|
|
70
|
Merge with Part and Lot− Ascending Popularity Code
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain the item and lot being put away. The locations are selected in popularity code order within each SLG. Additional validation is performed to ensure that the selected locations are in the correct popularity code range.
|
|
81
|
Storage Locations–Preferred Unit of Measure
|
Put-away looks for locations in the item’s storage location group, or list of SLGs, with the locations selected in popularity code order within each SLG. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
82
|
Empty Storage Locations–Preferred Unit of Measure
|
Put-away looks for empty locations in the item’s storage location group, or list of SLGs, with the locations selected in popularity code order within each SLG. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
83
|
Replenished Locations–Preferred Unit of Measure
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick level sequence. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
84
|
Empty Replenished Locations–Preferred UM
|
Put-away looks for empty locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick level sequence. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
85
|
Reverse-Replenished Locations–Preferred UM
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick level sequence. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
86
|
Empty Reverse-Replenished Locations–Preferred UM
|
Put-away looks for empty locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in descending pick level sequence. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
87
|
Storage Locations by Popularity Code–Preferred UM
|
Put-away looks for locations in the item’s storage location group, or list of SLGs, with the locations selected in popularity code order within each SLG. Additional validation is performed to ensure that the selected locations are in the correct popularity code range. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
88
|
Empty Storage Locations by Popularity Code–Preferred UM
|
Put-away looks for empty locations in the item’s storage location group, or list of SLGs, with the locations selected in popularity code order within each SLG. Additional validation is performed to ensure that the selected locations are in the correct popularity code range. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
89
|
Replenished Locations by Popularity Code–Preferred UM
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick level sequence. Additional validation is performed to ensure that the selected locations are in the correct popularity code range. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
90
|
Empty Replenished Locations by Popularity Code–Preferred UM
|
Put-away looks for empty locations in the item’s replenished location groups, with the locations selected in popularity code order within each SLG, which are selected in pick level sequence. Additional validation is performed to ensure that the selected locations are in the correct popularity code range. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
91
|
Storage Locations by Descending Popularity Code–Preferred UM
|
Put-away looks for locations in the item’s storage location group, or list of SLGs, with the locations selected in descending popularity code order within each SLG. Additional validation is performed to ensure that the selected locations are in the correct popularity code range. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
92
|
Empty Storage Locations by Descending Popularity Code–Preferred UM
|
Put-away looks for empty locations in the item’s storage location group, or list of SLGs, with the locations selected in descending popularity code order within each SLG. Additional validation is performed to ensure that the selected locations are in the correct popularity code range. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
93
|
Replenished Locations by Descending Popularity Code–Preferred UM
|
Put-away looks for locations in the item’s replenished location groups, with the locations selected in descending popularity code order within each SLG, which are selected in pick level sequence. Additional validation is performed to ensure that the selected locations are in the correct popularity code range. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
94
|
Empty Replenished Locations by Descending Popularity Code–Preferred UM
|
Put-away looks for empty locations in the item’s replenished location groups, with the locations selected in descending popularity code order within each SLG, which are selected in pick level sequence. Additional validation is performed to ensure that the selected locations are in the correct popularity code range. The system considers only locations with a preferred UM the same as the UM of this put away.
|
|
95
|
Merge with same Part − Preferred UM
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain the item being put away. Only locations with a preferred UM, the same as the item being put-away, are considered.
|
|
96
|
Merge with same Lot/Serial − Preferred UM
|
Put-away looks for locations in the item’s storage location group, or list of SLGs. Locations must already contain the item and lot/serial being put away. Only locations with a preferred UM, the same as the item being put-away, are considered.
|
|
101
|
Empty Dedicated Storage Locations
|
Put-away looks for empty dedicated locations in the item’s storage location group, or list of SLGs, with the locations selected in popularity code order within each SLG.
|
|
102
|
Dedicated Storage Locations–Merge with Part
|
Put-away looks for dedicated locations in the item’s storage location group, or list of SLGs. The locations must already contain the item being put away, and are selected in popularity code order within each SLG.
|
|
103
|
Dedicated Storage Locations–Merge with Any
|
Put-away looks for dedicated locations in the item’s storage location group, or list of SLGs. The locations must already contain inventory, and are selected in popularity code order within each SLG.
|
|
104
|
Dedicated Storage Locations − Merge with Part and Lot
|
Put-away looks for dedicated locations in the item’s storage location group, or list of SLGs. The locations must already contain the item and lot/serial, and are selected in popularity code order within each SLG.
|
|
106
|
Empty Dedicated Storage Locations − Ascending Popularity Code
|
Search for an empty dedicated location in the item’s storage location group, or list of SLGs. Locations are selected in popularity code order within each storage location group. Additional validation is performed to ensure that selected locations are in the correct popularity code range.
|
|
107
|
Dedicated Storage Location − Merge with Part − Ascending Popularity Code
|
Search for dedicated locations in the item SLG or the item list of SLG but locations that already contain the same item as the one being put-away. The locations are selected in popularity code order within each storage location group. Additional validation is done to ensure that the selected locations are in the correct popularity code range.
|
|
109
|
Dedicated Storage Location–Merge with part and lot − Ascending Popularity Code
|
Search for dedicated locations in the item SLG or the item list of SLG but locations that already contain the same item & lot as the one being put-away. Locations are selected in popularity code order within each storage location group. Additional validation is done to ensure that the selected locations are in the correct popularity code range.
|
|
111
|
Consume Reference Forecast
|
Consume any receipt forecasts that identify the specific order line, item number, lot/serial, and reference being received. The locations are selected in popularity code order within each SLG. Generally, this is used when all of the receipts details are known ahead of time, probably on an ASN.
|
|
112
|
Consume Lot/Serial Forecast
|
Consume any receipt forecasts that identify the specific order line, item number, and lot/serial being received. The locations are selected in popularity code order within each SLG.
Generally, this is used when the lot/serial details are known ahead of time, probably on an ASN, but not details of specific pallets, containers, and so on. Any reference detail on the receipt or the forecast is ignored.
|
|
113
|
Consume Order Line Forecast
|
Consume any receipt forecasts that identify the specific order line being received. The locations are selected in popularity code order within each SLG.
Generally, this is used when no details apart from the quantity are known ahead of time. Any lot/serial or reference detail on the receipt or the forecast is ignored.
|
|
121
|
Merge with Reference Forecast
|
This functions as per algorithm 111, except that the forecast is not consumed. The forecast quantity is left open. The forecast is simply used to identify the location.
|
|
122
|
Merge with Lot/Serial Forecast
|
This functions as per algorithm 112, except that the forecast is not consumed. The forecast quantity is left open. The forecast is simply used to identify the location.
|
|
123
|
Merge with Order Line Forecast
|
This functions as per algorithm 113, except that the forecast is not consumed. The forecast quantity is left open. The forecast is simply used to identify the location.
|
|
124
|
Merge with Order Forecast
|
This algorithm allows inventory received on an order line to be placed into a location with a forecast for the same order but a different order line. The locations are selected in popularity code order within each SLG.
No consumption can occur as the forecast is for a different item with, potentially, different rules for sizing.
|
|
133
|
Merge with Item Outside of Storage Location Groups
|
Put-away looks for locations outside the item’s storage location group, or list of SLGs. Locations must already contain the item being put away. The locations are selected in popularity code order within each SLG.
|
|
134
|
Use Last Item Number Transaction
|
The system looks for the last similar transaction for this item—transactions with the same from site, warehouse, and SLG as this put away. The destination location from that transaction is used for this put away.
|
|
135
|
Use Last Lot/Serial Transaction
|
The system looks for the last similar transaction for this lot/serial—transactions with the same from site, warehouse, and SLG as this put away. The destination location from that transaction is used for this put away.
|
|
136
|
Use Last Reference Transaction
|
The system looks for the last similar transaction for this reference—transactions with the same from site, warehouse, and SLG as this put away. The destination location from that transaction is used for this put away.
|
|
137
|
Use Storage Location Group From Last Item Number Transaction
|
Search for the location that was used with the last transaction referring to same item number. Look for location inside the same SLG starting from the location found.
|
|
138
|
Use Storage Location Group from Last Lot/Serial Transaction
|
Search for the location that was used with the last transaction referring to same lot/serial. Look for location inside the same SLG starting from the location found.
|
|
139
|
Use Storage Location Group from Last Reference Transaction
|
Search for the location that was used with the last transaction referring to same reference. Look for location inside the same SLG starting from the location found.
|
|
140
|
Storage Location by Popularity Code–UM in Capacity
|
Search for locations in the item SLG or the item list of SLG. The locations are selected in popularity code order each storage location group. Additional validation that the selected locations are in the correct code range. Only locations with a capacity defined for this UM are considered.
|
|
142
|
Storage Locations by Full%–UM in Capacity
|
Search for locations in the item SLG or the item list of SLG. The locations are selected in Full% order each storage location group. Additional validation that the selected locations are in the correct code range. Only locations with a capacity defined for this UM are considered.
|
|
150
|
Detail Overflow Location Put-Away–EXACT NEED
|
Put-away in the Overflow storage location group. Only the needed quantity is put-away.
|
|
151
|
Detail Overflow Location Put-Away–INFINITE CAPACITY
|
Put-away in the Overflow storage location group. Capacity in destination location is Infinite, so the total quantity is put-away in the location, for instance a full pallet, even if the requirement is less.
|
|
170
|
Storage Locations Merge with same Item/Lot in SLG
|
Search for locations in the item SLG or the item list of SLG. The locations are selected in popularity code order within each storage location group. Only select storage location containing same item/lot.
|
|
171
|
Storage Locations Merge with same Item in SLG
|
Search for locations in the item SLG or the item list of SLG. The Locations are selected in popularity code order within each storage location group. Only select storage location containing same item.
|
|
172
|
Storage Locations. Consider Only Empty SLGs
|
Search for locations in the item SLG or the item list of SLG. The locations are selected in popularity code order within each storage location group. Only select empty storage location.
|