User Tools

Site Tools


implementation:wms:moveablelocation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
implementation:wms:moveablelocation [2018/07/19 11:27]
csuhaa ose screenshots
implementation:wms:moveablelocation [2019/04/30 14:55] (current)
vise Cycle Count updated
Line 1: Line 1:
-====5.2.8. Moveable location settings====+====5.2.7. Moveable location settings====
  
 A moveable location is an intermediate storage location: this can be a cart, a movable rack, etc. A moveable location allows the operator to pick one or more orders and pack them onto a logistic carrier at another location (packing station). ​ A moveable location is an intermediate storage location: this can be a cart, a movable rack, etc. A moveable location allows the operator to pick one or more orders and pack them onto a logistic carrier at another location (packing station). ​
  
-===5.2.8.1. General=== +===5.2.7.1. General=== 
-{{ :​implementation:​wms:​ose:​07_movloc1.png |}}+{{ :​implementation:​wms:​ose:​07_movloc1.png |General Tab}}
  
 In the organization structure it is possible to set the code and name of a moveable location and define whether or not it is active. ​ In the organization structure it is possible to set the code and name of a moveable location and define whether or not it is active. ​
Line 10: Line 10:
 Stock on movable locations is not taken in account to create pick list (proposals). Stock on movable locations is not taken in account to create pick list (proposals).
  
-===5.2.8.2. Cycle count===+===5.2.7.2. Cycle count===
 A moveable location can also be used in the cycle counting and has the same settings as a bin location. A moveable location can also be used in the cycle counting and has the same settings as a bin location.
  
-{{page>implementation:​wms:​cyclecountsettings&​noheader&​noeditbtn}}+{{ :implementation:​wms:​ose:​movable_location_cycle_count.png |Cycle Count Tab}} 
 + 
 +**//Allow location to be counted during cycle count//** \\ 
 +Is the location allowed to be counted? 
 + 
 +**//Allow location to be counted during other operations//​** \\ 
 +Is the location allowed to be counted during other operations? This means that when this location is used on certain flows, the system will check if a count is needed. If so, the system will ask the user to perform a count. 
 + 
 +**//​Locations needs to be counted now//** \\ 
 +When this option is enabled, the location will be counted, regardless of the other settings (Number of days, number of operations, …) 
 + 
 +**//Count after X days//** \\ 
 +When a location has not been counted for the number of days defined here, the location needs to be counted. If the number is 0, this setting is not taken in account, and the setting on company level is taken. 
 + 
 +**//Count after X operations//​** \\ 
 +If the number of operations since the last count exceeds the defined number of operations, the location needs to be counted. If the number is 0, this setting is not taken in account and the setting on company level is taken. 
 + 
 +**//Locked by (read-only field)//** \\ 
 +This field shows the key of the user that is locking the location, because he needs to count the location or is currently in process to count the location. \\ 
 +When a location is locked, it cannot be used in other processes. \\ 
 +The location is released by clicking the ‘unlock’ button. \\ 
 +Stock on locked locations is not taken in account to create pick list (proposals). 
 + 
 + 
implementation/wms/moveablelocation.txt · Last modified: 2019/04/30 14:55 by vise