Differences

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

--- cobi.wms:faq [2022/05/05 09:49] – [How well does the app work with a large number of Items in SAP Business One?] tkammer
+++ cobi.wms:faq [2023/05/23 13:46] (current) – tkammer
@@ Line 25: / Line 25: @@
   * English
   * Spanish
+  * French
   * German
+  * Polish
   * Turkish
   * Finnish (partial)
@@ Line 34: / Line 36: @@
 ==== Is it possible to register the devices to a specific warehouse? ====
-Yes, this is possible. Please see the Options page of the COBI.wms documentation.
+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.
+==== Can I see which device or warehouse employee made a booking? ====
+Yes, if you correctly configure the connection settings.
+In on-premises or private-cloud environments, where you can set up the [[Management Database]], you can define a different SAP User for each COBI.wms device or COBI.wms user by filling out the apiUser and apiPass columns in the users table.
+In public-cloud environments, where you cannot use a Management Database, you can instead directly configure each COBI.wms device to use a different SAP User by entering it directly in the app's settings.
+When everything is set up correctly, you can use the "Change Log" window in SAP Business One to see who made a booking or who edited a document.
@@ Line 59: / Line 74: @@
 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 68: / Line 95: @@
 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 75: / Line 102: @@
 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.
+===== Pick & pack =====
+==== How to avoid two pickers accidentally working on the same pick list? ====
+You can fill in the "Picker" field of pick lists in SBO, and it will be displayed in the app, but that is all.  Any attempts at solving this issue via additional features poses significant challenges.
+Variant 1: Only let pickers open pick lists assigned to them.  This has the problem that the warehouse loses flexibility.  Often the employee who should take care of a pick list will change ad-hoc, and technical limitations on who can open a pick list only leads to confusion and frustration.
+Variant 2: Lock a pick list once it’s been opened by someone.  Let's see how this would need to be implemented, after which the problems with it will become apparent:
+  * There needs to be an additional UDF on the pick list that says “locked”
+  * Every time you open a pick list in the app, it needs to:
+    - Run a query to make sure the pick list is currently unlocked.
+    - Send an update to change the UDF value to locked.
+    - When you close the pick list, send an update to change the UDF value to unlocked.
+We would now be faced with the following issues:
+  * Opening/closing is too slow:  Employees may want to quickly look into a few pick lists without really beginning to work on any of them, and if the app has to execute the query/lock/unlock steps every time, this will become too slow.
+  * Unlocking is unreliable:  An employee may open a pick list, not really start working on it, but leave it open on the device.  (Either because the user was not instructed properly that this causes issues, or because they were distracted and forgot to close the list.)  This again leads to confusion and frustration.
+For these reasons the app doesn't attempt to solve the problem where two pickers may accidentally start working on the same pick list.  The employees must communicate with each other to make sure this doesn't happen.
@@ Line 91: / Line 143: @@
 ==== 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 110: / Line 162: @@
 ===== 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.