cobi.wms:faq
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cobi.wms:faq [2022/09/01 10:10] – [Can we automatically print labels when a booking is made?] tkammer | cobi.wms:faq [2026/06/15 13:01] (current) – thuth | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== General ===== | ===== 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? ==== | ==== Which versions of SAP Business One are supported? ==== | ||
| Line 27: | Line 35: | ||
| * French | * French | ||
| * German | * German | ||
| + | * Polish | ||
| * Turkish | * Turkish | ||
| * Finnish (partial) | * Finnish (partial) | ||
| Line 104: | Line 113: | ||
| + | ===== 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, | ||
| + | |||
| + | ===== 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 ===== | ===== Label printing ===== | ||
| Line 136: | Line 177: | ||
| ===== Licensing ===== | ===== 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? ==== |
| - | A COBI.wms | + | Apart from the COBI.wms |
| - | If a device is licensed, any person | + | 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 a user is licensed, they can log in to COBI.wms on any Android device. | + | 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' | ||
| + | |||
| + | ==== 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 | ||
| + | |||
| + | 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 | ||
| Licenses can be freely swapped between devices and users. | Licenses can be freely swapped between devices and users. | ||
| + | |||
| + | Generally, licensing devices is the easier option, especially since you won't have to deal with COBI.wms User Management. | ||
| + | |||
| + | See [[COBI.wms: | ||
cobi.wms/faq.1662019830.txt.gz · Last modified: by tkammer