COBI.wms supports a number of options that change the behavior of the app. Following is the list of supported options with their explanation.

You can assign each Android device to a specific warehouse. Select the warehouse for this device from this drop-down or select “none” to not assign it to a specific warehouse.

If the Android device is assigned to a warehouse, and you're booking a document based on another document (e.g. a delivery based on a sales order, or a goods receipt based on a purchase order), then the warehouse codes specified in the lines of the base document will be ignored, and the warehouse of the device used instead.

This option needs to be enabled if you wish to use a Bluetooth-connected barcode scanner which presents itself as a keyboard to the operating system.

Note: Even then, not all such scanners might work properly, especially if you want to use them with GS1 barcodes such as GS1-128 or GS1-DataMatrix. Using a built-in barcode scanner instead is strongly advised; see Recommended Devices for recommended Android scanners.

Normally, the app prevents you from entering quantities in goods issuing documents (such as Delivery or Issue for Production) if the entered quantity is not on hand. If you enable this option, such quantity checks will be disabled.

Note: SAP Business One might still block the booking of such documents if you haven't configured the system correctly.

Enable this option to show the following additional batch number fields in screens where you add a new batch number:

• Batch attribute 1
• Batch attribute 2
• Notes

Enable this option to show the following additional serial number fields in screens where you add new serial numbers:

• Lot number
• Manufacturer serial number
• Notes

If this option is enabled, you cannot add a new batch number without filling in the expiry date field.

Normally after a document is booked, the app will show you an overview of the document that was booked. In this screen you can see the document number that was assigned by SAP Business One to the new document, and have labels printed for the lines of the document.

If you have no use of that screen and wish the app to skip it, enable this option.

If this option is enabled, the first screen of the Picking module that shows the overview of pick lists will also list the lines of each pick list under it. You might want to enable this if your pick lists have very few lines each, otherwise it makes little sense to enable this.

If this option is enabled, scanning an item while a pick list is open will set the corresponding line's picked quantity to the correct quantity immediately. This means that your workflow might become more error-prone, but faster.

Normally, whenever a delivery note is booked from the app, the Due Date field of the booked delivery note will be set to the current date. If this option is enabled, and the delivery that you're booking is based on a sales order, then the Due Date field of the sales order will be copied to the Due Date field of the delivery note.

Enabling this option will allow you to fill in a packing slip for delivery notes you create.

Note: COBI.wms allows you to enter a weight for packaging units, but this does not use the standard weight field in SAP Business One, because it's automatically calculated and cannot be edited.

For the weight input in the app to work, you have to add a UDF under Marketing Documents → Package Content with name CWMS_Weight and data type Numeric(11). The value is stored in grams.

This option allows you to merge together the picking and packing workflows inside the Delivery module. (The Picking module becomes practically obsolete if you use this.)

Using this option requires a UDF on the the packing slip table called CWMS_Stack of type Numeric (11).

With this option, you can have the app generate SSCC codes for each packing unit added to the packing slip.

Using this requires a number of UDTs/UDFs:

• A UDF on the package types table called CWMS_NeedsSSCC of type Alphanumeric (1) with valid values Y and N. An SSCC will only be generated for package types for which this value is set to Y.
• A UDF on the packing slip table called CWMS_SSCC of type Alphanumeric (18). This is where the generated SSCC will be stored.
• A UDT called CWMS_SSCC of type No object with auto-increment.
• A UDF on the CWMS_SSCC UDT called UUID of type Alphanumeric (36).

The CWMS_SSCC UDT is only used internally by the app to record the SSCC numbers that were already generated and make sure no duplicates are used. The table does not contain any information relevant for the SAP Business One users.

The packing slips in SAP Business One cannot contain information about which batch/serial numbers were packed in which packing units. Enabling this option allows you to record that information, for which you need to create a UDT called CWMS_PACK_BSN of type No object with auto-increment and the following UDFs:

The final booking screen of the Receipt From Production module normally allows the user to check a checkbox to close the production order for which the receipt is being booked. Enabling this option will hide that checkbox so COBI.wms users cannot close production orders.

Theoretically, the same serial number can coincidentally appear for two different types of items. For example, you could have a PC monitor and a printer that coincidentally have the same serial number. If you enable this option, the app will assume that this is impossible and let you uniquely identify items by scanning only their serial numbers.

This could be useful, for example, if you have a number of items in SAP Business One that share the same GTIN because they are different variants of the same trade item. This would render the GTIN in a scanned GS1 barcode insufficient to identify an item. Another use-case would be if you don't have GS1 barcodes but want to identify items by scanning a single serial number only.

Normally when you scan an item, the app asks you for the quantity, so you could scan an item and enter 5 to add that many units of that item to the document you're creating. If you enable this option, the quantity field will automatically contain the number 1, and each subsequent scan of the same item will increase it by 1. So you could scan five of the same item instead of scanning it once and manually entering the number.

This works well in conjunction with units of measurement. If you have one EAN number for a box of 5 pieces and another EAN number for a crate of 20 pieces of an item, you can scan these one after another and the app will automatically calculate the various units together, yielding the correct number of total pieces. Of course, the units and their corresponding barcodes have to be configured correctly in SAP Business One first.

If a GS1 barcode with a quantity field is scanned, it will be counted in as well. For instance if you scan a GS1 barcode containing the GTIN for a box of 5 pieces and containing a quantity field of 3, the app will know that this means 15 pieces in total.