This feature is compatible with Cycle Count flow and the new Recount flow. The Lost & Found and Registration count types are also supported. The Stock Count Data Audit is compatible with all kind of configurations like jobs with or without tasks, counts with difference or no difference.

Important note: The Stock Count Data Audit does NOT apply to Direct Cycle Count.

Default setting: Deactivated!
It logs when a counting task was:

• Created
• Started
• Stopped
• Processed

With this feature, you get full traceability. Every stock count is logged, even when no variances are found. It tracks who performed the count, when it was done, and the quantities recorded and improved visibility into your inventory processes as well.

Implementing Recount flow - The Recount is a new kind of Cycle Count job which can recount a single/multiple lines within a location which has been previously counted. The Recount Flow is utilized when you want to verify the accuracy of your initial count or when you identify a discrepancy in the counting process.

Important note: The Recount Flow is ONLY compatible with the Registration Cycle Count type. The feature is based on non-blind counting. During the Recount Flow you can ONLY enter the number of items!

UI changes on the Processing Cycle Count form. New columns: 

• “Difference” column: The “Quantity” column has been renamed to “Differences”
• “System” column: This column displays the system quantity.
• “Last Count” column: This column shows the current quantity. If the mouse cursor is moved to the cell in the “Last Count” column of the specified row, the history of the counts (and recounts) becomes visible.
• “Status” column: This shows the statuses of the count task. The value can be “O, R or empty” based on the status of the recount task.

• Validating inserted values on “Forward” Click - The extended Customization Framework now allows you to validate inserted values on the “Forward” click. Use a custom query in the Mobile Client within the Customization Framework solution to validate inserted values as you move forward in the flow. The extended Customization Framework now includes new event types like “ListDataLoad” and “ValidationOnNext”. If the query returns a “ValidationError” result column, the next button execution is stopped. 

• Sorting and/or truncating in “Select from a List” screen types - The extended Customization Framework is adding a possibility to filter and/or sort displayed data in the Mobile Client with customization. On “Select from a List” screens, you can now apply custom business logic to truncate or sort lists either before displaying them or immediately after. A new “Next Event” field has been added to the customization window to manage user query names effectively.