Produmex Scan Complete Configuration Guide
It is recommended to avoid the asterisk (*), pipe (|) and apostrophe (’) characters in Produmex or SBO master data because these characters have a special role in Produmex products.
1. Configure Produmex Scan
When starting Produmex Scan for the first time on your device, the Configuration screen opens up. To change the configuration after the first use, run the Configure Produmex Scan application.
1.1. General tab
On the General tab determine the connection settings and the language of the application.
- Add the Server URL of the server where the client application will connect. The server URL consist the IP address of the server where the Service Broker runs and the port number. The port number is 50231 by default. Tap the
…button to scan for servers. - After the Server URL has been added, the active databases assigned to the Service Broker are listed on the box. Select the company database from the list. If the application cannot connect to the server, an error message is shown.
- Select the language of the client application from the Language dropdown menu.
- Tap the
IDbutton to see the device ID.
1.2. Advanced tab
Go to the Advanced tab and set up the configurations.
Don't Use Built-in OS Buttons
If you want to use the built-in operating system default control buttons, check the Don't Use Built-in OS Buttons checkbox. It is recommended to disable the built-in buttons on Windows CE, in desktop mode or when using remote desktop connection.
Customization Assist Mode
For customization purposes the Customization Assist Mode can be enabled by ticking the checkbox. For more information about customization see Produmex Scan Customization Guide.
Win. Layout
Select a Windows layout from the dropdown menu. Possible values:
- Normal: recommended in desktop mode
- Maximized Borderless: recommended in Windows CE
- Desktop Fullscreen: recommended when using remote desktop connection
Timeout (sec)
An initial timeout setting for the Client application. The Client application requests its configuration (including the Kill Time value) from the application server and for this first-time communication the Client application uses the Timeout setting.
- If the application server does not respond within the time limit defined by the Timeout setting, the Client application aborts the connection.
- If this first communication is successful, that is, the application server responds to the Client application within the time limit, the Kill Time setting is applied to define the timeout for future communication among the Client application, the application server and the database.
- The default value of the Timeout setting is 15 seconds. If your application or database server is slow, it is recommended to change the value to a higher number.
Note: The Tester Mode is for internal testing purposes only. Make sure that you do not enable it.
1.3. Diagnostics tab
On the Diagnostics tab network and process performance diagnostic tests can be ran.
Click the OK button to apply the configurations.
1.4. Sounds
On the Sounds tab you can define if you want Produmex Scan to play a sound whenever a barcode has been scanned successfully or a problem has occured while scanning.
If you enable the Play Sound setting, you can also set the success and the fail sound in the drop-down menus. In case of the success sound, the no sound option is also available.
If the setting is enabled and Produmex Scan displays a message, it displays the following sound:
- error: fail sound
- warning: fail sound
- info: success sound
Note: If the setting is enabled, Produmex Scan also plays a success sound when you leave a field where a barcode has been scanned successfully, for example when you tap the Add or the Update button.
The path of the sounds files Produmex Scan displays in the drop-down menus can be defined with the Audio directory for scanning (Service Broker directory) setting, see documentation here.
2. Setting Up Master Data in Produmex Scan
To be able to use the mobile application you have to set up the master data in the Produmex Scan add-on.
First set up the employees who can use the mobile application and determine their rights for the specific mobile functions.
In order to print labels from the mobile application, configure the printers and set up the label layouts you would like to use.
2.1. Printing
2.1.1. Defining the Layouts
You can define the layouts at Administration>Setup>Inventory>Produmex Scan>Printing Layout Sets.
On the Printing Layout Sets form you can define which layout files should be used for the specific labels at printing.
- The Description is the label name displayed on the mobile device.
- On the Bin Code Layout File field add the report file of the label version for bin locations.
- On the Stock Normal Label Layout File field add the report file of the label version for stock that is not managed by batches or serials.
- On the Stock Batch Label Layout field add the report file of the label version for stock that is managed by batches.
- On the Stock Serial Label Layout File field add the report file of the label version for stock that is managed by serial numbers.
Define the path to the report files at the Report Layout Folder setting on the Reports tab of Produmex Scan settings. It is recommended to use a network folder.
It is also possible to define an output folder for reports at the Report Output Folder setting on the Reports tab of Produmex Scan settings.
2.1.2. Layout formats
2.1.2.1. Crystal Reports
Regular Crystal Reports RPT files which can contain one or more of the documented parameters. The report can connect to and read from the database. The database logon parameters (username, password, server, company name) are set by Warehouse before executing the report.
You can download example report files from here: Label examples
Use the HanaReportSettingTool to configure the correct connection of the report file in HANA environment. You can read more about the tool in the UserGuide
Copy the reports to the Report Layout Folder set on Produmex Scan settings. Open the reports and adjust the datasource location.
Bin Code Layout
Crystal report file is run once with the mask as the parameter.
| Mandatory parameters: |
|---|
| BinCodeMask – Bin code mask with * eg. 01-A-1-1* |
Stock Normal Label, Batch Label, Serial Label Layout
| Mandatory parameters: |
|---|
| ItemCode BatchNumber SerialNumber Quantity |
In case you would like to use other parameters as well, then you can use the custom printing solution.
2.1.2.2. Zebra ZPL
Zebra ZPL files (or CPCL files) are text files which can contain one or more Placeholder strings.
The placeholders will be replaced by Produmex Scan before it is sent to the (networked TCP/IP or local printer on the server) Zebra printer.
Here is a sample Stock Label ZPL file (text file). This sample file contains the following placeholders:
- {Quantity}
- {OITM.InvtryUom}
- {OITM.ItemCode}
- {OITM.ItemName}
^XA
^PW632
^LL0472
^CWD,E:ARI000.FNT
^CFD,24
^FT434,270^FDItem;^FS
^CFO,24^BY3,3,95^FT135,170^BCN,,Y,N
^FD{Quantity}{OITM.InvtryUom}^FS
^FT492,270^FD{OITM.ItemCode}{OITM.ItemName}^FS
^PQ1,0,1,Y^XZ
Bin Code Layout
ZPL file is printed for every bin location found for the given mask.
| Placeholders: |
|---|
| {OBIN.BarCode} {OBIN.BinCode} … (Every field including user fields are available from OBIN table, reference it with the database column names) |
Stock Normal Label, Batch Label, Serial Label Layout
| Placeholders: |
|---|
| { {OOIITTMM..IItteemmCNaodmee} } {OITM….} … {Quantity} {OBTN.BatchNumber} {OBTN.CreationDate} {OBTN….} … {OSRN.MnfSerial} {OSRN.DistNumber} {OSRN….} …. Every field (including user fields) available from OITM table For batches only: every field (including user fields) available from OBTN table For serials only: every field (including user fields) available from OSRN table |
2.1.3. Setting Up Printers
To set up printers navigate to Administration > Setup > Inventory > Produmex Scan > Printers Setup.
Both local and network printers can be configured.
- To configure a local printer, make sure that the ‘Is Network Printer’ checkbox is not checked. Enter the name of the printer to the Local Printer Name field.
- To configure a network printer, check the ‘Is Network Printer’ checkbox. Fill in the IP Address and the Port Number fields.
- If the network printer type is Crystal, fill in the Local Name field. If the field is empty, the printing happens on the default Windows printer. If an incorrect local name is provided, the system displays an error message.
- If the network printer type is Zebra, the IP address is used.
In case of network printers, Local System users usually do not have the right to print, therefore, make sure that in the Run As User setting of the Produmex Service Broker you indicate a user who has printing rights.
2. Indicate whether the printer is active or not with the ‘Is Active’ flag. Only active printers can be selected on the mobile application.
3. Select the type of the label file from the Printer Type drop-down menu. The following file types are supported:
- Crystal (RPT)
- Zebra CPCL
- Zebra ZPL
4. It is possible to assign layouts that can be used with the printer. Select the line of the printer and choose the Select Layouts option from the right-click menu.
On the opening form select the layout(s) from the dropdown menu on the Layout Set Code field. With the Visual Order it is possible to determine the order of the layouts on the list.
Default printer properties
The printing is processed via the Produmex Service Broker. By default Produmex Service Broker runs in a context of the LocalSystem account therefore it takes its printing settings from the default properties. Meanwhile, Crystal Reports takes its printing settings from the user-specific properties.
In order to change the printing settings for Produmex Scan, change the user specific and the default printing properties as well.
To change the user specific settings, open ’Printing preferences’ of the printer. You can change the user specifc setting on the ’Options’ tab.
To change the default properties, select the ’Printing Properties’ option. On the opening screen go to the ’Advanced’ tab and click on the ’Printing Defaults’ button to change the default printing preferences.
2.2. Setting Up Employees
The user specific settings for Produmex Scan users can be configured on the Employee Master Data. The following settings can be configured:
- User authorization
- User password
- Favorite menus
- Printers
2.2.1. Authorization fields
To authorize a functionality for the employee, set the corresponding UDF to ‘Yes’. The employee will only see the authorized functions on the main menu of the client application.
The ‘Query stocks’ function is authorized for every employee by default. It does not have an authorization UDF.
2.2.2. Default Printer
On the Default printer UDF the printer used in customization can be defined. This printer will only be used in customization, it will not be listed among the printers defined for the user.
2.2.3. User password
Set the user password on the Mobile Password UDF.
2.2.4. PIN Code
By default the user can login with the Employee No.. If there is a PIN code set, it is possible to log in with the PIN code as well.
2.2.5. Mobile User Preferences
To configure the favorite menus for a user, select the ‘Mobile User Preferences’ option from the right-click menu or click on the ‘Mobile User Preferences’ button on the ‘Administration’ tab.
The ‘Mobile User Preferences’ form will open up. On the header of the form the Employee ID and the Employee Name are shown.
Select a menu point from the dropdown list on the ‘Mobile Menu ID’ column then define the sequence of the menu buttons on the ‘Visual Order’ column. Menu points with the smallest visual order number will be shown first.
Click on the ‘Update’ button to apply the changes.
The favorite menu buttons will be displayed on the top of the main menu of Produmex Scan.
2.2.6. Mobile User Printer
On the Employee Master Data select the ‘Mobile User Printers’ option from the right-click menu or click on the ‘Mobile User Printers’ button on the ‘Administration’ form.
The ‘Mobile User Printers’ form will open up. On the header of the form the Employee ID and the Employee Name are displayed.
Select the printer from the dropdown menu. Every printer defined on the Printers table is listed.
Add the sequence of the printer on the visual order column.
The printer with the lowest ‘Visual Order’ value will be shown as the default printer on the Login screen or before printing. It is possible to change the default printer. Press the ‘…’ button then select a printer from the list. Every printer defined for the user on the ‘Mobile User Printers’ form will be listed. The order of the list depends on the ‘Visual Order’ value.
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.
| Field | Description/Activity |
|---|---|
| Don't translate trace | 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. |
| DisplayTimeUoM | This setting is not in use in Produmex Scan. |
| Company Logo | The company's own logo, used in reports. Path to image file requested. |
| BxBackOffice Server URL | Obsolete setting. |
| Chart XML Folder | 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. |
| Name of last started AddOn | Internal field, not editable. |
| Date of last started AddOn | Internal field, not editable. |
| Time of last started AddOn | 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. |
| TxSyncServer URL | This setting is not in use in Produmex Scan. |
| Seconds of last started AddOn | 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. |
| Enabe Produmex statusbar (SBO 8.8 or above) | 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 Licensing: Offline Solution. |
3.2. SQL tab
The following table describes the fields on the SQL tab of the Produmex Scan Settings screen.
| 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.
| 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.
| 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 here.
| 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 UIP does not send any business data, confidential information or user / customer information. |
| 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.
| 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 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 Exception: 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. Important: 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.
| 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 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.
| 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.
| 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. |
4. Produmex Service Manager
The Produmex Service Manager can handle the Produmex Service Broker and other Produmex services. Service parameters, connection data to the database server, and the connection data to the company database/schema can also be modified on the Service Manager.
The Service Manager needs to be started in Administrator mode because it has to be able to start/stop/modify the ProdumexServiceBroker Windows service.
4.1. Set up/Modify Connection to the SAP company
1. Click on the Setup Companies button.
2. On the opening screen enter the connection data to your SAP company database/schema.
- MSSQL
- Server: Enter the name or IP address of the server.
- Port: Enter the port on which the application can connect to the database server. It is usually 1433, but if you have a named instance in the SQL server, the actual port must be checked.
- MSSQL Version: Select the MSSQL version number in the drop-down menu.
- Language: The language of the DI API transactions can be modified in the field.
- SQL User: Enter the SQL Server user name.
- SQL Password: Enter the SQL Server password.
How to check the port number on SQL
Open the SQL Server Configuration Manager. Select the SQL Server instance and right-click on TCP/IP on the right side. Click on Properties and on the displayed form go to the bottom and check the port number.
Note: In this example there are no instances and the port is the default value of 1433.
- HANA
- Server: The database server name must be added with the exact same format as it was added during the installation of the SAP Business One client.
- Single-Database: Enter the name or the IP address of the database server to the field.
- Multi-Database: The DATABASENAME parameter must be used: DBA@< >. Example:
- Database Port: Enter the database port on which the application can connect to the server.
- Single-Database: The default port is 30015.
- Multi-Database: The default port is 30013.
- MSSQL version: Select HANADB in the dropdown menu
- Language: The language of the DI API transactions can be modified in the field.
- SQL User: Enter the SQL Server user name.
- SQL Password: Enter the SQL Server password.
- When working on SAP B1 Cloud, add the domain username to the Domain user name field and enter the password to the Domain password field.
If you click Test DB Connection, the Service Manager tries to connect to the server with the given data. If the connection can be established, you will get the message Database connection test – success!
4.2. Add new database
Click on the Setup Companies button.
On the opening ‘Setup companies’ screen check the connection data. If you would like to add a database from a different database server, modify the connection parameters then click on the ‘Test DB Connection’ button to test the connection. The modification of the connection parameters does not affect the connection settings of the already added databases.
Click on the ‘+’ icon to add a new database/schema.
If the company is modified and saved by the save button, it updates the connection with the database information section!
On the ’Database Setup’ window select the database/schema from the dropdown menu.
Enter an SBO User and its password to create the connection to the database/schema. SAP employees are used for log in the mobile device. Transactions initiated by the employees will be posted by the SAP user defined for the Service Broker. The SBO user must have the authorizations to create stock related bookings in SAP Business One (Delivery, Goods Receipt PO, Stock Transfer, etc.) The SBO user also need at least an SAP Indirect Access license type as of SBO 9.2. PL08.
Click on the ‘Save’ button then close the window. You can close now Setup Companies and go back to the Service Manager main screen.
Now you have to assign your companies to the Produmex Service Broker and other Produmex services.
Click on the ‘Companies…’ button and select the company database/schema on the opening ‘Select Companies’ screen.
4.3. Configure Produmex Service Broker
The Produmex Service Broker can work together with different Produmex add-ons, therefore in the Service Manager you have to configure which add-on you want to use. To do that, click on the ‘Configure…’ button or select it from the line of the Service Broker.
General tab
Service Broker service has to be restarted after changing a setting.
If you set the 'Debug writeline log' parameter to true, it will write a log about each command the Service Broker processes. Only set it to true, if Produmex support asks you to do that.
Kill time: If a Service Broker process does not finish within this time limit, it will be aborted. The setting depends on your server. If you have a quick server, set it to a small number, if you have a slow server, set it higher. The default value is 30 seconds.
'Modules to load' is the module of the add-on to which the service broker connects. It is automatically done by the module installer for you.
At the 'Port to listen on' you can set which port is used by the service broker to communicate with the clients. The default is 50231. Make sure that the port you set here is not blocked by any firewall or antivirus software.
The 'Server Discovery Enable' turns on the feature that the client can look up the running service broker server automatically. It makes setting up the clients easier.
You have to assign an administrator user to the service in the Windows Service Manager, otherwise the Service Broker cannot connect to SBO and cannot write to its log files. If the Service Broker stops right after starting it, and in the log file you have access denied errors, then the cause is that you have not assigned the administrator user to the service.
License check
From product version 2022.01, the Produmex Service Broker checks the client application license.
The Produmex Service Broker retrieves the application license based on the installation number and the system number. These numbers can be configured in Produmex Service Manager > Produmex Service Broker service configuration window.
If the installation number and the system number are not provided, the system retrieves these numbers from a license already downloaded by the add-on.
The license download happens in every 12 hours. If the license cannot be downloaded, the system tries the download process in every 5 minutes.
Produmex Service Broker tab
On the Produmex Service Broker tab you can see the loaded modules, and you can remove/install new modules if needed.
If you see a check icon before the module name, it means it could be loaded successfully. If a problem arises, you will see error beside the module name.
4.4. Start Produmex Service Broker
After you have set all settings and installed the server module, you can start the Service Broker service in the Service Manager by selecting first the service then clicking on the ‘Start’ button. If you want to stop a service, click on the ‘Stop’ button.
You can also stop or start the services from windows service manager, but you cannot change the Produmex settings there. It is recommended that you set the service to Automatic start and that you set the recovery options to Restart at Recovery in Service Properties for the service.
4.5. Start Produmex Service Broker in console mode
The Service Broker can be started from the command window as well. Only one instance can be started at the same time and the Service Broker service must be stopped. The use of the command window is recommended for debugging purposes and in production environment the use of the service is more efficient.
The Service Broker in console mode can be started by running the following .exe file in Administrator Mode: C:\Program Files (x86)\Produmex\ServiceBroker\BxServiceBroker.Console.exe
