COBISOFT Documentation

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== App Options ======

COBI.wms supports a number of options that change the behavior of the app.  These are stored locally on each Android device on which COBI.wms is installed, so each device can have a different configuration.

Following is the list of supported options and their explanation.


===== Warehouse =====

You can assign each Android device to a specific warehouse.  Select a warehouse from the drop-down menu in the options screen to assign the Android device to that warehouse, or select "none" to remove the assignment.

==== Use selected warehouse regardless of base document ====

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.

==== Document filtering ====

Documents can be filtered based on the warehouse the device is assigned to.  This filtering can be enabled on a per-module basis (in other words, for different document types) by checking each of the **Filter: ...** options.

**These filtering options require a User Defined Field to be added:**

^ Category                      ^ Title              ^ Validation                               ^
| Marketing Documents -> Title  | ''CWMS_Warehouse'' | Link to System Object: OWHS - Warehouses |

If the option "Link to System Object" is not available, then disable the Validation and set the data type to Alphanumeric and Length to 8.

**If you added the UDF after already having installed COBI.wms, an additional step is needed to make COBI.wms recognize it:** Execute the SQL command **''DROP VIEW <nowiki>cwms__version</nowiki>''** on your SAP Business One company database (like ''SBODEMODE''), and restart the app.

**Note:** In newer versions of COBI.wms, the view ''<nowiki>cwms__version</nowiki>'' has been renamed to ''<nowiki>cwXX__version</nowiki>'' where ''XX'' stands for the current COBI.wms **minor** version, e.g. ''<nowiki>cw38__version</nowiki>'' for Version ''2.38''.  In this case, the correct SQL command would be ''DROP VIEW <nowiki>cw38__version</nowiki>''.

Note that the UDF is not actually used for all document types.  For example:

  * For Inventory Transfer Requests (in the Inventory Transfer module of the app), the From Warehouse and To Warehouse fields are used.
  * For Production Orders (in the Issue for Production and Receipt from Production modules), the standard Warehouse field is used.
  * For Pick Lists, the app actually queries the lines of each pick list and checks if there is a line matching the correct warehouse.

In those cases, the UDF value is ignored.  The UDF is only used for document types that don't have a standard way of assigning them to a warehouse via fields of the document header, such as Purchase Order (OPOR) and Sales Order (ORDR).

===== Barcode Scanning =====

==== Barcode scan via Bluetooth keyboard ====

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.

==== Scan to add quantity ====

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.


===== Batches and Serials =====

==== Batch number details ====

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

==== Serial number details ====

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

==== Expiry date is mandatory ====

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

==== Global serials ====

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.


===== Picking =====

==== Pick list lines in overview ====

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.

==== Quick picking ====

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.

==== Stay in pick list after picking is completed ====

Normally, once all lines of a pick list are fully picked and the data is transmitted, the app automatically returns to the overview of all pick lists.  Enable this option to stay in a pick list even after it's finished.  (Typical use-case: transmitting the finished picking data triggers a remote print for shipping labels, after which the labels are put on the packaged goods and a photo attachment added to the pick list.)


===== Delivery =====

==== Delivery date is due date of order ====

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.

==== Delivery packing slips ====

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 that field is automatically calculated and cannot be edited.  For the weight input to work, you have to add the following UDF to your system:

^ Category                                ^ Title           ^ Data type    ^
| Marketing Documents -> Package Content  | ''CWMS_Weight'' | Numeric (11) |

The weight value will be stored into this UDF in **grams**, as an integer value.

==== Delivery packing slips / Unified workflow ====

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 the following UDF on the the packing slip table, to support grouping together multiple packaging units, e.g. pallet stacks:

^ Category                                ^ Title           ^ Data type    ^
| Marketing Documents -> Package Content  | ''CWMS_Stack''  | Numeric (11) |

The UDF is called "Stack" because it was originally added with the idea of supporting "sandwich pallets" (stacked pallets), but it could represent any kind of group.  E.g. you could have smaller boxes inside of larger crates, and in that case the larger crates would be identified by the "Stack" value.

==== Delivery packing slips / SSCC generation ====

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

There are a number of requirements for this option to work:

  - Set your company's GLN number under: Administration -> System Initialization -> Company Details
  - Create the following UDT and UDFs:

=== Required UDT ===

^ Table name   ^ Object type                       ^
| CWMS_SSCC    | No object **with auto-increment** |

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

=== Required UDFs ===

^ Category                                ^ Title               ^ Data type          ^ Valid values ^
| Master Data -> Package Types            | ''CWMS_NeedsSSCC''  | Alphanumeric (1)   | Y / N        |
| Marketing Documents -> Package Content  | ''CWMS_SSCC''       | Alphanumeric (18)  |              |
| User Tables -> CWMS_SSCC                | ''UUID''            | Alphanumeric (36)  |              |

An SSCC will only be generated for a package if the type of the package has the ''CWMS_NeedsSSCC'' field set to ''Y''.

The actually generated SSCC will be stored in the ''CWMS_SSCC'' field of the Package Content table.

==== Delivery packing slips / Batches and Serials ====

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:

^ Title            ^ Type                  ^ Mandatory? ^
| ''DocEntry''     | ''Numeric (11)''      | ✓          |
| ''LineNum''      | ''Numeric (11)''      | ✓          |
| ''PackageNum''   | ''Numeric (11)''      | ✓          |
| ''ItemCode''     | ''Alphanumeric (50)'' | ✓          |
| ''UomEntry''     | ''Numeric (11)''      | ✓          |
| ''BatchNumber''  | ''Alphanumeric (36)'' |            |
| ''SerialNumber'' | ''Alphanumeric (36)'' |            |
| ''Quantity''     | ''Quantity''          | ✓          |


===== Receipt from Production =====

==== Disallow closing of production orders ====

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.


===== Miscellaneous =====

==== Negative stock allowed ====

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.

==== Skip screen showing booked document ====

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.