User Tools

Site Tools


implementation:wms:cycleccontroller

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
implementation:wms:cycleccontroller [2019/06/11 14:02]
vise
implementation:wms:cycleccontroller [2019/11/15 09:41] (current)
vise
Line 1: Line 1:
-===5.1.3.9. Cycle count controller===+===5.1.3.10. Cycle Count Controller===
  
-//Controls the cycle counting//+Extension: ​Controls the cycle counting
  
-{{:​implementation:​wms:​ose:​05_cyclecount.png|}}+It controls the [[implementation:​wms:​cycle_count|cycle count flows]] and [[implementation:​wms:​cycle_count#​cycle_count_during_other_operations1|cycle count during other operations]]. Performing cycle count during other operations means that the system may ask the user to count the items while performing an operation different from cycle count, for example picking. 
 + 
 +{{ :​implementation:​wms:​ose:​extensions:​cycle_counting.png |Cycle Count Controller}}
  
 **//Allow to adjust quantity of current stock items?//** \\ **//Allow to adjust quantity of current stock items?//** \\
-If this option is enabled, ​and the option 'Show current stock items' is enabled, the Cycle Count flow will allow to select ​currect ​stock and adjust the quantity instead of performing a 'blind' ​count.+If this setting ​and the //Show current stock items// setting are enabled, the user can  ​select ​the current ​stock on the scanner, the available stock quantity is displayed, ​and the user can adjust the quantity instead of performing a blind count. If the setting is disabled, the displayed value on the scanner is the default value (1).
  
 **//Allow to select account in case of perpetual inventory?//​** \\ **//Allow to select account in case of perpetual inventory?//​** \\
-If this option ​is enabled, the accounts ​numbers ​need to be selected during the cycle count processing ​process ​if the option ‘Perpetual inventory’ is set.+If the setting ​is enabled ​and //Perpetual Inventory// is used, the account ​numbers ​must be selected during the cycle count step [[implementation:​wms:​cycle_count#​process|Process]].
  
 **//Allow user to skip count//** \\ **//Allow user to skip count//** \\
-When performing ​cycle count during other operations, the user is allowed to skip the count.+If the setting is enabled, whenever the system prompts the user to perform ​cycle count during other operations, the user is allowed to skip cycle count.
  
 **//Auto handle batch?//** \\ **//Auto handle batch?//** \\
-When this option ​is set, no batch needs to be entered ​in the cycle count process. ​The system ​will try to fill in the batch. If there is only batch on the location, the system ​will take that batch. If there are multiple batches, the system ​will take the youngest ​batch. If no batch is on the location, the system ​will take the batch defined in the ‘Default batch on auto handle batch.+If the setting ​is enabled, no batch needs to be entered ​during ​the cycle count process. ​Instead, the system ​tries to fill in the batch. If there is only one batch on the location, the system ​takes that batch. If there are multiple batches, the system ​takes the latest ​batch. If there is no batch on the location, the system ​takes the batch defined in setting //Default batch on auto handle batch//.
  
 **//Auto move SSCC//** \\ **//Auto move SSCC//** \\
-When an SSCC is counted on a location, it is possible that for the system it is stored on another location. ​These options set what actions should happen when this occurs+The setting is available for type //Lost and Found//​. ​When an SSCC is counted on a location, it is possible that in the system it is stored on another location. ​The following ​options ​can be set to define ​what the system needs to do in this case
-  * No move  +  * No move: The SSCC is not moved to this new location and remains recorded in the system in the original location.  ​ 
-  * Ask user  +  * Ask user: The system asks if the SSCC needs to be moved. ​ 
-  * Auto move +  * Auto move: The system automatically moves the SSCC to this new location.
-Option is available for type 'Lost and Found'+
  
 **//Auto select batch/BBD when monolot pallet//** \\ **//Auto select batch/BBD when monolot pallet//** \\
-When cycle counting a monolot ​pallet ​//(a pallet with only item and lot number)//, the system ​will auto select ​the batch and BBD instead of the user that needs to fill it in.+When cycle counting a mono pallet (a pallet with only one item code and lot number), the system ​automatically selects ​the batch and BBD instead of asking ​the user to select them.
  
 **//Count after number of days//** \\ **//Count after number of days//** \\
-When a location has not been counted for the number of days defined here, the location ​needs to be counted. ​This setting ​is only used if on location level this setting ​is not set. \\ +The number of days after which cycle counting must be performed. A zero means that this location ​always has to be counted. ​The setting ​can be used only if it is not set location ​level (Organizational structure elements > Cycle Count tab).
-A zero means that this location ​will always have to be counted.+
  
 **//Count after number of operations//​** \\ **//Count after number of operations//​** \\
-If the number of operations ​since the last count exceeds the defined number of operations, the location ​needs to be counted. ​This setting ​is only used if the setting ​is not set on location level.\\ +The number of operations ​after which cycle counting must be performed. A zero means that this location ​always has to be counted. ​The setting ​can be used only if it is not set location level (Organizational structure elements > Cycle Count tab).
-A zero means that this location will always have to be counted.+
  
 **//Count location when it becomes empty//** \\ **//Count location when it becomes empty//** \\
-Count the location if the used location becomes empty //​(count ​during other process)//+If the setting is enabled, cycle count must be performed when the used location becomes empty during other operations.
  
 **//Count type cycle count//** \\ **//Count type cycle count//** \\
-The type of cycle count to use when doing cycle count. \\ +The type of cycle count to use when performing ​cycle count. \\ 
-Possible ​values:  +Possible ​options:  
-  * Lost and FoundAn actual theoretical ​location where differences are stored. This option ​will correct ​the stock on the counted location. +  * Lost and Found: ​A virtual ​location where differences are recorded. This option ​corrects ​the stock on the counted location. 
-  * Registration: Differences are stored ​in a table. With this option the stock on the counted location remains the same until the count is processed.\\ +  * Registration:​ Differences are recorded ​in a table. With this option the stock on the counted location remains the same until the count is processed.\\
-//Please note that differences for serial numbers will always use type '​Registration',​ regardless of the selected type.//+
  
 +Note: In case of differences for items with serial number, this setting is ignored and the system uses type //​Registration//​.
  
 **//Count type other operations//​** \\ **//Count type other operations//​** \\
-The type of cycle count to use when doing cycle count during other operations. \\+The type of cycle count to use when performing ​cycle count during other operations. \\
 Possible values: ​ Possible values: ​
-  * Lost and FoundAn actual theoretical ​location where differences are stored. This option ​will correct ​the stock on the counted location. +  * Lost and Found: ​A virtual ​location where differences are recorded. This option ​corrects ​the stock on the counted location. 
-  * Registration: Differences are stored ​in a table. With this option the stock on the counted location remains the same until the count is processed.\\ +  * Registration:​ Differences are recorded ​in a table. With this option the stock on the counted location remains the same until the count is processed.\\
-//Please note that differences for serial numbers will always use type '​Registration',​ regardless of the selected type.//+
  
 +Note: In case of differences for items with serial number, this setting is ignored and the system uses type //​Registration//​.
  
 **//Default batch on auto handle batch//** \\ **//Default batch on auto handle batch//** \\
-The batch number to use when there is no batch on the counted location, and if the ‘auto ​handle batch’ option is set to true.+The batch number to use when there is no batch on the counted location. To use this setting ​the //​Auto ​handle batch?// setting must be enabled.
  
 **//Dummy serial number format//** \\ **//Dummy serial number format//** \\
-When using the lost & found method for cycle countand processing the cycle count for lost serial numbers on release only, dummy serial numbers might need to be generated in order to be issued.\\ +When using cycle count type //Lost and Found// ​and processing the cycle count for lost serial numbers ​managed with //on release only// method, dummy serial numbers might need to be generated in order to be issued. ​With this setting a fix part for all dummy serial numbers ​can be entered and then the system amends the entered ​value with incrementing numbers ​to generate unique dummy serial numbers.
-In this setting ​you can enter a fix part for all dummy serial numbers. Incrementing ​ numbers will be appended to this value to generate unique dummy serial numbers.+
  
 **//Enter reason on direct cycle count?//** \\ **//Enter reason on direct cycle count?//** \\
-Does the user need to enter a reason ​during direct cycle counting?+If the setting is enabled, during the Direct Cycle Count flow the ​user must select ​a reason ​why there is a difference between the counted items and the items recorded in the system. The reasons can be defined on the [[implementation:​wms:​reasons|Reasons]] tab of the Organization Structure.
  
 **//Enter reason when skipping count?//** \\ **//Enter reason when skipping count?//** \\
-Does the user need to enter a reason when skipping ​a count? A count can only be skipped ​during other operations.+If the setting is enabled, ​the user must enter a reason when skipping ​the count during other operations.
  
 **//​Manually set price on processing the count//** \\ **//​Manually set price on processing the count//** \\
-This allows ​the user to enter the price that needs to be used when making the goods issue/​receipt. ​\\ +If this setting is enabled, ​the user can enter the price that needs to be used when creating ​goods issue/​receipt ​documents. By defaultthe new price is the value indicated in the //Item Cost// ​column ​of the [[implementation:​wms:​cc_process|Processing Cycle Count]] screen. \\
-By default the new price will be the value from the column ​'item cost'. \\+
 For catch weight items a price per weight can be entered. For catch weight items a price per weight can be entered.
 +
 +Note: If the setting is enabled, settings //Price List for Goods Issue// and //Price List for Goods Receipt// are ignored for any price calculation.
  
 **//Price list for goods issue//** \\ **//Price list for goods issue//** \\
 The price list to use when the cycle count needs to perform a goods issue. Possible values: ​ The price list to use when the cycle count needs to perform a goods issue. Possible values: ​
   * An SBO price list (OPLN.ListNum)   * An SBO price list (OPLN.ListNum)
-  * -1 for last purchase price +  * -1 for the last purchase price 
-  * -2 for last evaluated price+  * -2 for the last evaluated price 
 + 
 +Note: If setting //Manually Set Price on Processing the Count// is enabled, setting //Price List for Goods Issue// is ignored during any price calculation. In this case it is only used by the system to put the price list number on the header of Goods Issue documents.
  
 **//Price list for goods receipt//** \\ **//Price list for goods receipt//** \\
Line 83: Line 84:
   * -1 for last purchase price   * -1 for last purchase price
   * -2 for last evaluated price   * -2 for last evaluated price
 +
 +Note: If setting //Manually Set Price on Processing the Count// is enabled, setting //Price List for Goods Receipt// is ignored during any price calculation. In this case it is only used by the system to put the price list number on the header of Goods Issue documents.
  
 **//Propose default quantity on logistic unit//** \\ **//Propose default quantity on logistic unit//** \\
-If set, the system ​will automatically ​fill in the default quantity on a logistic unit.+If the setting is enabled, the system automatically ​fills in the default quantity on a logistic unit.
  
 **//​Registration:​ Store lines with no difference//​** \\ **//​Registration:​ Store lines with no difference//​** \\
-If set, the system ​will also store lines in the registration table where the counted difference is zero. This option is only taken in account when the 'Count type' = Registration.+The setting applies to cycle count type //​Registration//​. ​If the setting is enabled, the system also records ​lines in the registration table where the counted difference is zero.
  
 **//Show current stock items//** \\ **//Show current stock items//** \\
-If set, the system ​will show the current items in stock for the selected location when the counting starts.+If the setting is enabled, the system ​displays the //Items on Location// screen and shows the current items in stock for the selected location when the counting starts. If the setting is disabled, the screen is not displayed.
  
 **//Show differences during cycle count//** \\ **//Show differences during cycle count//** \\
-After counting a location ​it is possible to show the differences between the counted items and the items in the system. This is shown on the device during cycle count.+If the setting is enabled, after counting a location ​the scanner shows the differences between the counted items and the items recorded ​in the system.
  
 **//Show differences during other operations//​** \\ **//Show differences during other operations//​** \\
-After counting a location during other operations, ​it is possible to show the differences between the counted items and the items in the system. ​This is shown on the device during cycle count. +If the setting is enabled, after counting a location during other operations, ​the scanner shows the differences between the counted items and the items recorded ​in the system.
implementation/wms/cycleccontroller.1560261729.txt.gz · Last modified: 2019/06/11 14:02 by vise