Differences

This shows you the differences between two versions of the page.

--- cobi.wms:faq [2022/05/05 09:58] – [Is it possible to register the devices to a specific warehouse?] tkammer
+++ cobi.wms:faq [2026/06/15 13:01] (current) – thuth
@@ Line 3: / Line 3: @@
 ===== General =====
+==== Does COBI.wms support SSL/TLS encrypted connections to MS SQL Server? ====
+Yes. COBI.wms supports SSL/TLS encrypted connections to Microsoft SQL Server (MSSQL), e.g. for accessing the Management Database.
+If SSL/TLS is configured on the SQL Server side, you can enforce encryption in COBI.wms by setting **Optional fields → Encryption** to **`require`**. This ensures COBI.wms will only connect if the connection is encrypted.
+**Note:** We recommend using a valid server certificate that matches the SQL Server hostname (DNS name) and is trusted by the client environment.
 ==== Which versions of SAP Business One are supported? ====
@@ Line 25: / Line 33: @@
   * English
   * Spanish
+  * French
   * German
+  * Polish
   * Turkish
   * Finnish (partial)
@@ Line 34: / Line 44: @@
 ==== Is it possible to register the devices to a specific warehouse? ====
-Yes, this is possible.  Please see the [[Options]] documentation page.
+Yes, this is possible.  Please see the [[App Options]] documentation page.
 In the Options, you can also configure which modules should filter the shown documents on basis of the selected warehouse.
@@ Line 72: / Line 82: @@
 In partner-hosted or SAP-hosted public-cloud deployments, the app usually has to do all communication over Service Layer. Sadly, this significantly degrades the performance when transmitting large amounts of data, so the app may not be able to load the item list at all. Scanning barcodes will still work the same.
+===== Batch Numbers / Serial Numbers =====
+==== Is "On Release Only" supported? ====
+Yes, the app supports the "on release only" management method for batch/serial numbers, however there are some caveats.
+For serial numbers, you must enable the checkbox **Automatic Serial Number Creation on Receipt**.  This means that empty serial number entries will be added to the database when an inbound/receipt transaction is made for the item.  During outbound/release transactions, the app will transparently update those entries with the user-provided serial numbers, and then use them for the transaction.
+For batch numbers, if "on release only" is chosen, the only way to release batch numbers is to generate them in the SAP Business One client at some point, then use them in the app.  There is unfortunately no other way to support this method due to limitations in the SAP Business One programming interface.
@@ Line 81: / Line 103: @@
 The supported barcode types depend on the scanning hardware that is being used.  So long as the hardware supports it, COBI.wms can read any type of barcode, including 2D codes such as QR Code and DataMatrix.
-COBI.wms also supports the GS1 standard; see next question.
+COBI.wms also supports [[GS1 Barcodes]]; see next question.
@@ Line 88: / Line 110: @@
 When a barcode is connected to a specific UoM in the barcodes table of the item master data, then COBI.wms will automatically select the right UoM for the scanned barcode.
-Using the GS1 standard, COBI.wms also supports reading batch and serial numbers, production and expiry date, quantity, and so on from the scanned barcode and automatically fills in the relevant fields.
+Using [[GS1 Barcodes]], COBI.wms also supports reading batch and serial numbers, production and expiry date, quantity, and so on from the scanned barcode and automatically fills in the relevant fields.
+===== Picking & Packing =====
-===== Inventory counting =====
+==== How can you prevent two pickers from working on the same picking list? ====
-==== Can two employees work on the same counting list at the same time? ====
+COBI.wms provides a supporting feature for this scenario.
-No, this is not supported. The employees would be overwriting each other’s inputs. Instead, two different counting lists should be created for the employees to be able to work in parallel.
+By enabling the option “Show if a picking list has been started”, the system can indicate whether a picking list is already being processed.
+Behavior when enabled:
+  * A user can actively “start” a picking list
+  * A corresponding flag (UDF) is set in SAP
+  * Other devices will see the list as already in progress (highlighted in green)
+Important:
+  * This is not a strict system lock
+  * The feature is intended to provide transparency and process guidance
+  * Technically, multiple users could still open and work on the same list
+===== Inventory =====
+==== Can multiple users work on the same inventory list at the same time? ====
+Yes, this is possible with the current COBI.wms version.
+Starting from version 2.43, the inventory logic has been significantly improved by introducing an external inventory service.
+How it works:
+  * All counting data is initially collected from devices by the external service
+  * The service centrally gathers inputs from multiple users
+  * Values are consolidated (summed up)
+  * The final results are then transferred to SAP Business One
+Advantages:
+  * Multiple users can work on the same inventory list simultaneously
+  * Improved stability, especially for large inventory counts
+  * No blocking of the Service Layer during counting processes
+  * Reduced risk of data being overwritten
+Note:
+  * Final values are consolidated by the service before being posted to SAP
 ===== Label printing =====
@@ Line 104: / Line 158: @@
 ==== Can we import different label sizes to the app? ====
-The label templates imported into the app can have any size. Additionally, the label printer has to be configured correctly for the desired label size.
+The [[Label Templates]] imported into the app can have any size. Additionally, the label printer has to be configured correctly for the desired label size.
 ==== Can we automatically print labels when a booking is made? ====
-For this, Coresuite Remote Print is needed. It does not work with the app’s own direct printing feature. The app can make use of an additional Windows Service from COBISOFT (the COBI.wms Print Helper) to automatically create the Coresuite Remote Print files when a booking is made.
+For this, Coresuite Remote Print is needed. It does not work with the app’s own direct printing feature. The app can make use of an additional Windows Service from COBISOFT, called the [[Print Service]], to automatically create Coresuite Remote Print files when a booking is made.
@@ Line 123: / Line 177: @@
 ===== Licensing =====
-==== Is one license for device or for a person? How can we manage licenses? ====
+==== What kind of SAP Business One Licenses are needed to use the app? ====
+Apart from the COBI.wms Licenses that you acquire from COBISOFT, you may also need to purchase additional SAP Business One Licenses from your SAP Partner.
+According to the latest licensing guidelines of SAP Business One (as of May 2023), **every individual employee (person)** who interacts with SAP Business One through any means (including third-party applications such as COBI.wms) must have some kind of SAP Business One License.
+If an employee who will use COBI.wms already has an SAP Business One License, such as Professional or Limited Logistics, then they don't need an additional SAP Business One License to be allowed to use COBI.wms.
+However, if the employee doesn't normally use SAP Business One and therefore doesn't have any SAP Business One License, then they will need (at minimum) an SAP Business One Indirect Access User License.
+==== Are COBI.wms Licenses for devices or for users? How can we manage licenses? ====
+A COBI.wms license can be assigned to an Android device **or** to a COBI.wms user.
+If an Android device is licensed, any person can log in on that device and use it.  Users don't require licenses in this case.
+If a COBI.wms User is licensed, they can user their username and password log in to COBI.wms on any Android device.  In this case, the devices don't need to be licensed.
+Licenses can be freely swapped between devices and users.  We support both models of licensing for the sake of convenience.
+Generally, licensing devices is the easier option, especially since you won't have to deal with COBI.wms User Management.  If you license your devices, and don't set up any COBI.wms Users, your warehouse employees can simply grab any Android device and log in without having to enter a username and password.
-A COBI.wms license can be assigned to a device or to a COBI.wms user. If a device is licensed, any person can log in to that device and use it. If a user is licensed, then they can log in to COBI.wms on any device, even if the device itself is not licensed. Licenses can be freely swapped between devices and users. We support both models of licensing for the sake of customer convenience.
+See [[COBI.wms:Management Database]] for details on how to manage users and licenses.