===== Stock Count Data Audit =====

The **"Activate Stock Count Audit"** setting is listed in the **[[implementation:wms:cycleccontroller|Cycle Count Controller.]]**\\

**Stock Count Audit is used to log the steps of counting flows.**\\

It uses the **PMX_CCLH** table for Log Heads and the **PMX_CCLL** table for Log Lines. PMX WMS logs into two tables: the header table contains location level information while the lines table stores stock line level information gathered during the cycle count. The detailed table structure can be found in the **[[https://wiki.produmex.name/lib/exe/fetch.php?media=implementation:wms:sbo_certification_table_descriptions.html| Database Structure]].**\\

The **Log Head** contains the** Location, CycleCountKey** and **JobName** columns as well.\\ 

  * The **Location** is the counted location. 
  * The **CycleCountKey** is the foreign key to the PMX_CYCO.InternalKey column. The PMX_CYCO contains the CycleCountType which tells if the count was Registration or LostAndFound. 
  * Every count has a generated **JobName**. When creating a task on the Select Locations to Count screen, this generated **JobName** can be changed by the user before creating the task. 
  * **The use of the JobName:** users can group the logged data of multiple cycle counted location with the **JobName** if they created the Cycle Count task on the Select Locations Screen.
  * **The structure of the automatically generated JobName:** <code>{username}_yyyyMMdd_HHmmss_fff</code>. 

The **Log Line** contains the details about the counted item.\\ 

Both tables contain a **Status** column, which represents the current state of the count.\\
The state transitions can be found in the **State Diagram:**\\ 
{{ :implementation:functionalguide:cycle_count:cycle_count_log_states_1_.png?700 |}}

For summarizing the jobs, there is a sample view **PMX_CYCLE_COUNT_JOB.**\\  
This can be customized without any restrictions as this is not used by Produmex WMS. 


<callout type="warning" icon="true"> **Limitations:**\\ 

  * Processing Lost&Found counts is not logged fully. The log is only changed when the Lost&Found location doesn’t contain that Item/BatchNumber/SecondBatchNumber/BestBeforeDate anymore. This is a logical constraint of the Lost&Found counting, so this is NOT possible to solve. 

**Temporary Limitations:**\\
//(These limitations will be addressed in future releases)//  
  * Serial Numbers added during the Processing of the count are not logged. This also means that the processing of these counts are not logged fully. 
  * Partial processing of Serial Numbers is not logged fully. 
  * SerialNumbers column contains the missing/extra serial numbers in case of difference. If there is no difference during count, it contains every counted serial number.  </callout>