======3. Produmex Scan Settings ======

To configure the settings for the system go to Administration > Add-Ons > Produmex Scan > Produmex Scan Settings.

=====3.1. General tab=====

The following table describes the fields on the General tab of the Produmex Scan Settings screen.

{{:implementation:scan:setup:general_tab.png|General tab}}

^Field^Description/Activity^
|<wrap lo>Don't translate trace</wrap>| Obsolete setting.|
|Advanced Progress Bar | If this checkbox is checked, the system will display the Produmex Scan Advanced Progress Bar instead of the Business One Progress Bar. We recommend using the Produmex Scan progress bar, as at long processes SBO progress bar can stop.|
|<wrap lo>DisplayTimeUoM</wrap>|This setting is not in use in Produmex Scan.|
|Company Logo|The company's own logo, used in reports. Path to image file requested.|
|<wrap lo>BxBackOffice Server URL</wrap> |Obsolete setting.|
|<wrap lo>Chart XML Folder</wrap>|This setting is not in use in Produmex Scan.|
|Produmex Support Business Partner|If an error occurs, a message box is displayed with the error details. You can send the error message to Support from this message box. You will need to set a Business Partner first, and set the Contact Person's email address. Set this Contact Person's code for the Produmex Support Business Partner field. You have to set up SBO Mailer for this function to work. |
|<wrap lo>Name of last started AddOn</wrap>|Internal field, not editable.|
|<wrap lo>Date of last started AddOn</wrap>|Internal field, not editable.|
|<wrap lo>Time of last started AddOn</wrap>|Internal field, not editable.|
|Use Message Board|The message board lets add-ons communicate with each other. In some cases, events are forwarded to non-Produmex add-ons. In this case, turn this setting off, but in this case communication between Produmex add-ons will stop.|
|<wrap lo>TxSyncServer URL</wrap>|This setting is not in use in Produmex Scan.|
|<wrap lo>Seconds of last started AddOn</wrap>|Internal field, not editable.|
|Grid Row Count Decrease Number|Decrease height of form grid to allow buttons being correctly seen at the bottom of the window. Positive integer needed. Useful if you have SAP 8.8 or higher with a low resolution monitor and the buttons are in the grids.|
|Close Stucked AddOns|If enabled, the add-on kills any other instance of BXWH9AddOn.exe on start. It means that only one Produmex Scan add-on can run at a time. On terminal server environments it is recommended to disable this setting as it kills Produmex Scan add-ons run by other users as well.|
|<wrap lo>Enabe Produmex statusbar (SBO 8.8 or above)</wrap>|Obsolete setting|
|Do Not Use GetAsXml|When Produmex Scan request table information, we can use GetAsXml SAP function. Sometimes there were SAP DI errors, in this case we can use a Produmex Scan function to request the data.|
|Password for DI Connection|Modify DI connection mode to work around for SAP 9.0 pl9 hotfix 1 bug by direct DI connection|
|Copy Bitmaps Manually|If enabled, the icon image files will not be copied from the SBO installation folder when the add-on starts. Enable this setting if the user do not have writing permission for the folder set as the Pictures Folder on the Path tab of General Settings.|
|Boyum License URL|Boyum IT Offline Licensing webpage \\ For more information see [[implementation:scan:licensing#offline_solution|Licensing: Offline Solution]].|

=====3.2. SQL tab===== 
The following table describes the fields on the SQL tab of the Produmex Scan Settings screen.

{{:implementation:scan:setup:sql_tab.png|SQL tab}}

^Field^Description/Activity^
|ADO.NET SQL Username|The User name for the MS SQL database (usually sa). Scripts use this setting (for example for upgrading a database).|
|SQL Time out in seconds|SQL Timeout setting for SQL queries.|
|SQL execution duration alert in milliseconds|If the execution of a query exceeds the time defined in this setting, a warning is added to the log file.|

=====3.3. Logs tab=====
The following table describes the fields on the Logs tab of the Produmex Scan Settings screen.

{{:implementation:scan:setup:logs_tab.png|Logs tab}}

^Field^Description/Activity^
|Auto Purge Audit Logs in days|The add-on logs each database transaction in the Audit Log table. This log can be deleted automatically in the interval set here. The default setting is 30 days.|
|Keep Audit Logs in days|The system deletes the log entries, which are older than the number of days set here.|
|Log resource strings|If this checkbox is checked, the system logs every Resource String from open forms to a log file. By default log files are located in: %ProgramData%\Boyum IT\Produmex Scan (for pre-2023.06 versions it is %AppData%\Roaming\BX\Logs).|
|Logging Level|Sets which events are logged. Possible values: \\ //Errors Only// \\ //Errors and Warnings// \\ //Errors, Warnings, Information// \\ //Debug (everything)// \\ By default log files are located in: %ProgramData%\Boyum IT\Produmex Scan (for pre-2023.06 versions it is %AppData%\Roaming\BX\Logs).|
|Log Table - max number of days to keep|Log entries that exceed the specified number of days will be deleted from the "@BXPLOG" table.|
|Log Table - max number of rows to keep|Defines the maximum number of rows that are kept in the "@BXPLOG" table.|

=====3.4. Reports tab===== 
The following table describes the fields on the Reports tab of the Produmex Scan Settings screen.

{{:implementation:scan:setup:reports_tab_1.png|Reports tab}}

^Field^Description/Activity^
|Report Layout Folder|The folder which contains the RPT files for reports.|
|Report Output Folder|The folder which will contain the generated PDF files for reports.|
|Paper Size (Reports)|Paper size for reports. Example: A4, A3|
|Paper Orientation (Reports)|Paper orientation for reports. Example: portrait, landscape|
|Printer Name (Reports)|Printer name for reports.|
|Print Preview (Reports)|If enabled, the //Preview before print// checkbox is checked by default on the Select Report Layout screen.|
|Preview with Watermark|If enabled, the watermark is printed on print previews as well.|

=====3.5. UIP tab=====

The Usability Improvement Program (UIP) aims to give all Boyum IT customers
the ability to contribute to the design and development of Boyum IT products. For more information about UIP click [[https://www.boyum-it.com/sbo/uip/|here]].

{{ :implementation:scan:uip.png |UIP}}

^Field^Description/Activity^
|Usability Improvement Program|If the Usability Improvement Program is setting is enabled, the add-on automatically sends information to Boyum IT about how the product is used. The information is used to improve the related features. The gathered data sent to Boyum IT can be: \\ (1) feedback (generic information e.g. SAP version, resolution and add-on specific information e.g. number of configurations) \\ (2) error \\ <wrap em>UIP does not send any business data, confidential information or user / customer information.</wrap>|
|Scheduled Time to Send Data|The exact time of the day when information is sent|
|Send Errors Only|If the setting is enabled, only errors are sent to Boyum IT.|
|Last Date Data was Sent||
|Last Time Data was Sent||


=====3.6. Produmex Scan General tab===== 
The following table describes the fields on the Produmex Scan General tab of the Produmex Scan Settings screen.

{{ :implementation:scan:scan_general.png |Produmex Scan General tab}}

^Field^Description/Activity^
|Maximum number of documents to display per page (more than 20 may cause performance issues)|Defines the maximum number of lines displayed on one screen. If the number of the lines to be listed exceeds this number, page navigator buttons are displayed on the screen. Use these buttons to navigate between pages. \\ //Please note: The Refresh button must be pressed in order to apply the added filters even though the navigation buttons are displayed.//|
|Maximum number of serials/batches to display (more than 100 may cause performance issues)|If you work with serial/batches numbers, with this setting you can limit the number of the displayed items.|
|Maximum number of lines for stock queries to display (more than 100 may cause performance issues)|Defines the maximum number of lines displayed in the Query Stocks/Stock Info screens.|
|Don't close screens with completed quantity|If you picked all quantities on quantity screens, then Produmex Scan falls back to the document line screen by default. In this case you cannot use any customization after a //’ButtonAdd’// event. With this setting you can configure Produmex Scan to stay on the quantity screens, and you have to close it manually. This setting doesn't work in Picking function, since the quantity screen is different.|
|Don't close screen after picking delivery|After the delivery is created in Picking, Produmex Scan falls back to the select a pick list screen by default. If this checkbox is enabled, Produmex Scan stays on the pick list lines screen after the delivery is created.|
|Allow issuing more items for production than planned|If this setting is disabled, only the production order lines that have open quantities to issue are listed in the ’Issue for production’ function.|
|Allow reception for production of more products than planned|If this setting is disabled, only production orders that have open quantities to receive are listed in the ’Receipt form Production’ and ’By-Product’ functions.|
|Enable multi-item Stock Transfers|This function allows to park transactions before you post them, that is, you can add multiple items to a stock transfer before posting. \\ Once you click the ''Post'' button, however, it is possible that not only your transactions will be posted. **If there is another user creating a stock transfer to the same warehouse/bin location, the user’s transactions will be posted as well**.  \\ (If you are supposed to be allowed to post only your own transactions, please consult with the description of function //Transaction Separation for Warehouse Scanners// available in this table.) \\ If function //Enable multi-item Stock Transfers// is disabled, only single-scan-transactions are possible, that is, you are allowed to post transactions only one by one.|
|Ignore special lines when creating Documents|It is enable, the text lines of a sales order won’t be copied to a delivery. |
|Exclude Sales Orders when checking allocated quantities|If enabled, stock allocated to sales orders cannot be used when issuing stock during outgoing processes.|
|Sales return document location must be the same|Items can only be returned to the same bin location.|
|Credit note document location must be the same|Items can only be returned to the same bin location.|
|Keep base document line order for Delivery (instead of picking order)|If enabled, the Delivery document lines are added in the order of the base document, otherwise they will be added in the order of the picking.|
|Real-time Stock Counting|If enabled, Produmex Scan automatically updates the Inventory Counting document with the result of the counting after pressing the Finish button in the end of Stock counting or Quick counting. If this setting is disabled, the counting result will be stored in a user table. The synchronization can be initiated from the right-click menu on the SBO Inventory Counting document. The synchronization works if the counter employee is linked to the SAP user account and the Finish button is pressed to finish the counting.|
|Show all Stock Counting data on scanners|If enabled, already counted items are listed on the Stock Counting screen. //Please note: Items with different batch or serial number will be listed in separate lines.// \\ If disabled, only the number of the counting records is displayed.|
|Display all sheet bin locations for Quick Counting|It is enable all bin location will be displayed for quick counting.|
|Guided Quick Counting (Y/N)|If enabled, the Guided Count process can be started instead of Quick Counting.|
|Restricted zone handling in Quick Counting (Y/N)|If enabled, the counter is only allowed to count locations included in the Inventory Counting document during Quick Counting and Guided Counting.|
|Sticky destination location for Stock Transfer Requests|If enabled, the last To: location will be remembered during processing Stock Transfer Request, this can be convenient if STR items are put in the same destination location (maybe a cart, pallet, etc.)|
|Keep focus on prepared line (all processes)|If enabled: The item that just was full picked remain in focus even if it jumps to the end of the list.|
|Display completed Stock Transfer Request lines at the end of the list|At Stock Transfer Request process the processed lines will be shown in the bottom of the list.|
|Goods Receipt PO quick refresh mode|During reception, Goods Receipt PO lines can be set to refresh data only on the current line, not the whole list.|
|Copy user fields from base line to Serial/Batch Details (Goods Receipt PO only)|Enable this setting to copy the UDF value from the purchase order lines to the matching Serial/Batch detail field when the Goods Receipt PO is created.  \\ //Please note: The value will be copied only if the UDF and the Serial/Batch detail has the exact same name. //|
|Timeout for messages (except for errors, seconds)|Warnings, Information messages, are closed automatically after the time set at this field.|
|Diagnostic Client Log settings|Special option for collecting error logs from the mobile client. Only use when instructed by Produmex support.|
|Don't show icons on main menu (use buttons instead)|Display only simply buttons with no icons.|
|Detailed mobile log|Only for picking and stock transfer. More details are recorded in to table:  @BXPLMSMOBLOG|
|Enable SAP DI API logging|If this setting is enabled, a new log file is created under "c:\ProgramData\Boyum IT\Produmex Scan\Service Broker\". The file name is SAP-DIAPI-//yyyy-mm-dd//.log|
|Alternative Item Name field|To display alternative item names on the scanner, add the OITM table field name where the alternative name of the item is stored to this field. Please note: In order to add user defined fields, insert the ‘U_’ prefix. Restart the Service Broker to apply the Alternative Item Name.|
|Transaction Separation for Warehouse Scanners|Using this function is reasonable only if you enable function //Enable multi-item Stock Transfers// (the description of the function is available in this table). \\ If function //Transaction Separation for Warehouse Scanners// is enabled, you can add multiple items to a stock transfer before posting, however, when you click the ''Post'' button, **only your transactions will be posted**.|
|Transaction Separation for Production Receipt|The setting is recommended to be used if more than one employee works on the same purchase order. If the setting is enabled, the Receipt from Production Flow separates the transactions based on the employees who have been working on the purchase order. \\ Produmex Scan displays the number of purchase order lines that have been received by the given employee and the purchase order lines can be posted based on the separate transactions. \\ E.g. 6/9/10 pack means that altogether 10 packs should be received, out of which 9 packs have already been received and 6 packs have been received by the given employee. It means that 3 other packs have been received by (an)other employee(s). These transactions now can be posted separately.|
|Transaction Separation for Production Issue|The setting is recommended to be used if more than one employee works on the same production order. If the setting is enabled, the Issue for Production Flow separates the transactions based on the employees who have been working on the production order. \\ Produmex Scan displays the number of production order lines that have been issued by the given employee and the production order lines can be posted based on the separate transactions. \\ E.g. 6/9/10 pack means that altogether 10 packs should be issued, out of which 9 packs have already been issued and 6 packs have been issued by the given employee. It means that 3 other packs have been issued by (an)other employee(s). These transactions now can be posted separately.|
|Copy UDF Values to Target Document \\ (workaround for an SAP Business One bug, for more information click [[https://launchpad.support.sap.com/#/notes/1382856 |here]])|If the setting is enabled, the UDF values of the base document are copied to the target document when the target document is being created. The data copy is applied on a head and line level as well. The setting applies to the following cases: \\ * Purchase Order > Goods Receipt PO \\ * A/P Reserve Invoice > Goods Receipt PO \\ * Sales Order > Delivery\\ * A/R Reserve Invoice > Delivery\\ * Pick List > Delivery\\ * Inventory Transfer Request > Inventory Transfer\\ * Sales Order > Inventory Transfer\\ * Delivery > Sales Return\\ * A/R Invoice > A/R Credit Memo \\ <wrap em>Exception</wrap>: \\ If a UDF is filled in on the base document and it is also configured as a custom field on the Produmex Scan client, **user queries must be created** to have the default value of the UDF copied from the base document to the target document. \\ <wrap em>Important:</wrap> \\ By default, the setting is disabled because it causes a loss in performance. If you use UDF values on a head and/or line level and they are copied while using Produmex Scan, make sure that you **enable the setting to avoid potential data loss**.|

=====3.7. Produmex Scan Scanning tab=====
The following table describes the fields on the Produmex Scan Scanning tab of the Produmex Scan Settings window.

{{ :implementation:scan:produmex_scan_settings.png |Produmex Scan Scanning tab}}

^Field^Description/Activity^
|Item code or item barcode must be scanned for Sales Order|If this option is enabled, then the item code or the item’s bar code must be scanned when delivering the sales; otherwise the item is prefilled and doesn’t need to be scanned.|
|Item code or item barcode must be scanned during Picking|If this option is enabled, then the item code or the item’s bar code must be scanned during picking; otherwise the item is prefilled and doesn’t need to be scanned.|
|Prefill quantities for Goods Receipt PO|Prefill 	quantities 	(separate 	options 	for 	different processes):\\ **None**: No prefill will be used for this task. \\ **Open**: The system will fill in the quantities of all receives as the full expected or full remaining expected quantity. For example: if the order is 20 and 5 have been received, the system will default the next receive for 15. \\ **Unit**: The system will fill in the quantities with one unit.|
|Prefill quantities for Stock Transfer Request|:::|
|Prefill quantities for Picking|:::|
|Prefill quantities for Issue for Production|:::|
|Prefill quantities for Receipt from Production|:::|
|Prefill quantities for Return Components|:::|
|Prefill unique batches (outgoing processes)|If this setting is enabled, an there is only one batch in stock for the item, the batch is automatically filled during outgoing processes.|
|Prefill unique batches for Stock Counting|If this setting is enabled, an there is only one batch in stock for the item, the batch is automatically filled during stock counting.|
|Post the corresponding quantity when scanning item bar code in quantity field|When scanning an item’s bar code into a quantity field, a quantity of 1 for the corresponding UoM is pre-filled; if this option is enabled, the quantity is automatically posted/added, otherwise the user has to press the Add/Update/Post button.|
|Auto book unit when scanning normal item for Stock Counting|When doing inventory counting, scanning a barcode automatically counts a unit (eg. 1 piece, 1 carton) for the item|
|Barcode scanner prefix \\ Barcode scanner suffix |If the barcodes contain prefix/suffix characters that should be removed before processing it, you can specify it here. Eg. if you have a ( and ) prefix/suffix, the printed item barcode can look like (A1000) which will be processes as A1000. |
|GS1-128 barcode group separator|Group separator character for GS1-128 type barcodes. Example: $|
|Code ID type|For GS1-128, there are two international standards, the Symbol standard and the AIM standard. With Symbol CodeID, the scanned input text is prefixed with (K for GS1128. Currently only None value is supported.|
|Allow selecting locations from Find Stocks screen (outgoing processes)|If enabled, the Find Stocks button allows to select an location.|
|Allow selecting batches from Find Stocks screen (outgoing processes)|If enabled, the Find Stocks button allows to select an existing batch.|
|Optimized mixed serial/bin handling (Goods Receipt PO, Stock Transfer Request)|If enabled, the bin location and the serial number can be added on the GR/PO lines screen.|
|Audio directory for scanning (Service Broker directory)|The path of the sound files that Produmex Scan can use for playing a sound when scanning barcodes. See the related settings [[implementation:scan:client_configuration#sounds|here]].|

=====3.8. Produmex Scan Picking tab=====
The following table describes the fields on the Produmex Scan Picking tab of the Produmex Scan Settings screen.

{{:implementation:scan:setup:picking_tab.png|Produmex Scan Picking tab}}

^Field^Description/Activity^
|Allow working on already taken Pick Lists|It is advised for an extend pick list. More than one user is allowed to pick the items included in the list.|
|Real-time Picking (post instantly after picking an item)|If enabled (default) every picking action instantly updates the SAP Pick List document.|
|Allow changing bin/batch/serial allocations for Picking|If enabled, the bin/batch/serial numbers are allowed to be different than what is specified in the Pick List.|
|Speed Picking (Real-time Picking must be disabled)|If it is enabled, the lines from the selected picklist are loaded only once, when the Picking screen is first opened for that pick list. The selection automatically jumps onto the next un-picked line following the line last picked; this is another improvement to simplify the picking process.|
|Sequential Picking (‘Speed Picking’ must be enabled)|If it is enabled, the entire control stays basically in the Picking Line Details screen, and the control jumps back to the Pick List screen only after the last line has been picked. The user can always jump back with the Back button, of course.|
|Streamlined Picking|Enables a special POS-like mode for picking where all items are picked from a single bin location or non-bin warehouse. In this case, scanning an item code or barcode automatically adds a quantity of 1 (can be changed on the screen) to the picked quantity. The settings is applicable for normal items.|
|Pick List lines quick refresh mode|When picking from a non-bin warehouse the Pick List - lines screen can be set to only refresh the current line data (quantities), not the whole list.|
|Release active Pick List on timeout|During picking, the Pick List is allocated to the working employee. If there is a timeout and the worker is forced to the main menu, if this option is set the pick list will be reset to be available to others.|
|Timeout interval for Picking (seconds)|If specified, the worker is forced to the main menu from picking after this many seconds of inactivity.|

=====3.9. Produmex Scan Strategies tab=====
The following table describes the fields on the Produmex Scan Strategies tab of the Produmex Scan Settings screen.

{{:implementation:scan:setup:strategies_tab.png|Produmex Scan Strategies tab}}

^Field^Description/Activity^
|Incoming strategies user query name|The user query name used for the incoming strategy.|
|Incoming strategies frequency (seconds)|Number of seconds to run the incoming strategy periodically. 0 = disabled.|
|Replenishment strategies user query name|The user query name used for the replenishment strategy.|
|Replenishment strategies frequency (seconds)|Number of seconds to run the replenishment strategy periodically. 0 = disabled.|
|Allow changing target Bin Location allocation for Stock Transfer Draft|If the function is enabled, you are allowed to use a target bin location different from the one that is allocated on the Stock Transfer Draft.|