Differences

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

--- cobi.wms:app_options [2022/07/04 12:02] – tkammer
+++ cobi.wms:app_options [2023/11/23 12:22] (current) – [Document filtering] tkammer
@@ Line 1: / Line 1: @@
 ====== App Options ======
-COBI.wms supports a number of options that change the behavior of the app.  Following is the list of supported options with their explanation.
+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.
@@ Line 16: / Line 18: @@
 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.**
+**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.
-  * Open **Tools -> Customizing Tools -> User Defined Fields - Management**.
+**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.
-  * Open **Marketing Documents** and select **Title**.
-  * Click on the ''[Add]'' button at the bottom right.
-  * Enter **CWMS_Warehouse** into the Title field.  For the Description field, use whatever you like.
-  * Option 1: For Validation, select **Linked to Entities** and then **Link to System Object** and choose **OWHS - Warehouses**
-  * Option 2: If Link to System Object is not available, then disable the Validation, and set the data type to **Alphanumeric / Size 8**.
-Afterwards, when you open any type of document, such as Purchase Order or Sales Order, you can enable the UDF display (//View -> User-Defined Fields//) and choose the Warehouse from a list (Option 1) or manually fill in the **Warehouse Code** (Option 2).
+**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 Relocation module of the app), the From Warehouse and To Warehouse fields are used.
+  * 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 on the document-header, such as Purchase Order and Sales Order.
+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 =====
@@ Line 125: / Line 128: @@
 ==== 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.  Using this requires the addition of a UDT and a number of UDFs.
+With this option, you can have the app generate SSCC codes for each packing unit added to the packing slip.
-Required UDT:
+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** |
-Required UDFs:
+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 ^
@@ Line 138: / Line 148: @@
 | Marketing Documents -> Package Content  | ''CWMS_SSCC''       | Alphanumeric (18)  |              |
 | User Tables -> CWMS_SSCC                | ''UUID''            | 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.
 An SSCC will only be generated for a package if the type of the package has the ''CWMS_NeedsSSCC'' field set to ''Y''.