====== Cycle Count Flow======

=====Overview=====

The Cycle Count flow is used when the counted differences need to be reviewed and approved before booking. It offers the following options: 
  * With task: When selecting this task, only locations with the option ‘Location needs to be counted now’ set to true are allowed.
  * Without task: When selecting this task, all locations with the option ‘Allow to be counted during cycle count’ set to true are allowed.

Note: This document only describes the steps of blind counting. During a blind count, the current inventory is not displayed on the mobile client. Users should count the physical inventory without any information about the inventory in the system. Blind counting is set if the following settings are disabled on the [[implementation:wms:cycleccontroller|Cycle Count Controller]]:
  * Allow to adjust quantity of current stock items?
  * Show current stock items 

=====Workflow=====

{{map> :implementation:wms:cycle_count:cc_flowchart.png |}}
  * [[implementation:wms:cyclec##cycle_count_no_task|Without task @380,80,585,260]]
  * [[implementation:wms:cyclec#cycle_count_with_task|With task @70,80,275,260]]
  * [[implementation:wms:cycleccount_everything|Count everything @280,340,375,375]]
  * [[implementation:wms:cyclec#count_SSCC|Count SSCC @5,340,100,435]]
  * [[implementation:wms:cyclec#count_items_on_location|Count items on location @465,340,590,375]]
  * [[implementation:wms:cyclec#scan_sscc|Scan SSCC @280,380,375,435]]
  * [[implementation:wms:cyclec#scan_item|Scan item @280,455,375,510]]
  * [[implementation:wms:cyclec#enter_batch_data|Enter batch data @280,530,375,585]]
  * [[implementation:wms:cyclec#add_quantity|Add quantity @280,605,375,660]]
  * [[implementation:wms:cyclec#identify_the_product|Identify item @480,380,577,435]]
  * [[implementation:wms:cyclec#scan_item2|Scan item @480,455,577,510]]
  * [[implementation:wms:cyclec#enter_batch_data2|Enter batch data @480,530,577,585]]
  * [[implementation:wms:cyclec#add_quantity2|Add quantity @480,605,577,660]]
  * [[implementation:wms:cc_process|Process cycle count @280,850,375,907]]
{{<map}}

===== Cycle count with task=====

====1. Office====
Tasks can be made for the cycle counting process. Tasks allow users to plan the cycle counting.

{{ :implementation:functionalguide:cycle_count:office_task.png |}}
  
The settings on this screen can be used to limit the locations that will need to be counted. After pressing the ‘Update’ button, it will set the property ‘Needs to be counted now’ on the selected location(s) to true.

{{ :implementation:functionalguide:cycle_count:office_ose.png |}}
 
//**Pick locations, non-pick locations, reception dock, shipping dock, production lines**// \\
Select the type of locations to perform the actions on.

//**Only when cycle count requirements are met**// \\
When this setting is set to true, the cycle count settings (like number of days, number of operations, …) on location and cycle count controller are checked. Only locations where these requirements are met will be used to perform the actions.

//**Warehouse**// \\
Select the warehouse. If no warehouse is selected all warehouses are used. 

//**Zone**// \\
After selecting a warehouse, all zones in this warehouse will be listed here. Select a zone to only use the locations in this zone. If no zone is selected, all zones are used. 

//**Location from... to**// \\
Select location(s) which needs to be counted.

//**Lock location for user**// \\
Select a user to lock the locations for. If no user is selected, the location(s) will not be locked. When a user is selected, the locations that are found using the entered selection criteria will be locked for this user.
This means stock on these locations cannot be used. Only the selected user can perform the cycle counting task on the handheld device.
This option can be used to divide the cycle counting task for users.

//**Item group**// \\
Select an item group. The property ‘Needs to be counted’ will be set to true on locations where the items from the group are stored.

//**Item from… to**// \\
Select item(s). The property ‘Needs to be counted’ will be set to true on locations where the selected item(s) are stored.

//**Remove count task from selected locations**// \\
If this is set to true, the property ‘Needs to be counted’ on location will be set to false.

//**Remove lock from selected locations**// \\
Remove the lock on the selected locations.

**Shopfloor** \\
<WRAP tip round> All screens regarding the cycle count will have the prefix ‘Cycle count:‘ on the screen title. This is done because when the user needs to perform cycle count during other operations, it is visually clear that he is performing a cycle count. </WRAP> 

Select the “Cycle counting” function on the handheld terminal. Select the option ‘With task’. 

{{ :implementation:functionalguide:cycle_count:cc_noz_zone.png |}}
    
If there are no locations which needs to be counted, the system will display the message ‘No more zones to count’. \\
If there are locations which needs to be counted, the system will display the list of zones where those location(s) are located. Select a zone.

{{ :implementation:functionalguide:cycle_count:cc_identifloc.png |}}
     
After selecting a zone, select a location from the list. Only locations that need to be counted and have no locking, or are locked for the current user, are displayed in the list. \\
After the user has selected the location, this location will be locked for this user. No other user will see this location in the list of locations to be counted. \\

When the cycle count type is ‘Registration’, the system will check if there are open registrations. When there are open registrations, the system asks whether to remove those registrations. Press ‘Yes’ for clearing the previous registrations. In this case only new registrations will be used. Press ‘No’ for keeping the previous registrations. In this case, new registrations will be added to the already existing registrations.

{{ :implementation:functionalguide:cycle_count:cc_openreg.png?220 |}}

Select a task:
  * Count everything: count all the items on this location. 
  * Count SSCC’s: count all full logistic units on the location. 
//Note: Full logistic units in the system are SSCC’s where no stock has been removed yet.//

====1. Count everything ====
{{page>cc_everything&noheader}}

====2. Count SSCC's ====
{{page>cc_sscc&noheader}}

=====2. Cycle count without task=====
Scan or select a location. \\
After identifying the location, select a task:
  * Count everything: count all the items on this location. 
  * Count SSCC’s: count all full logistic units on the location. 
  * Count items on location: count only a certain product on the location.

{{ :implementation:functionalguide:cycle_count:cc_no_task.png |}}

====2.1. Count everything ====
{{page>cc_everything&noheader}}

====2.2. Count SSCC ====
{{page>cc_sscc&noheader}}

====2.3. Count items on location====
{{page>cc_item_on_loc&noheader}}

===== 3. Cycle count during other operations=====
When the cycle counting needs to be done during other operations, the system will display the message ‘This location needs to be counted’. After pressing the ‘Ok’ button, a ‘Cycle count’ type process can be started.

{{ :implementation:functionalguide:cycle_count:cc_operations.png?450 |}}
   
Based on the cycle count controller configurations, the system might allow to skip the count. When the skipping is allowed, and extra ‘Skip count’ button will appear. For skipping the count, select the ‘Skip count’ button or press the left arrow button. \\
If configured, the system displays a list of reasons for the skipping. Select a reason. 

{{ :implementation:functionalguide:cycle_count:cc_skip.png |}}
     
When the skipping is not allowed, the normal ‘Cycle count’ process will be performed. When pressing the left arrow button, the system will display a warning message that the count cannot be skipped.

===== 4. Additional information=====

The PMX_CYCO table is populated when the differences are shown on the Mobile Client and the user clicks the ''Update'' button in the Select Locations to Count window to confirm that the process is completed.