Differences

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

--- cobi.wms:app_options [2022/03/14 15:01] – 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 12: / Line 14: @@
 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.
-==== Filters ====
+==== 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).
+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 defined on Document Header level with the name ''CWMS_Warehouse'' which is to contain a warehouse code.**
+**These filtering options require a User Defined Field to be added:**
-If the ''CWMS_Warehouse'' field of a document is filled, and filtering for that document type is enabled, then the document will only appear in the app if the device's warehouse corresponds to the document's warehouse.
+^ 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 =====
@@ Line 92: / Line 108: @@
 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.
+**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:
-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**.
+^ 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 ====
@@ Line 100: / Line 119: @@
 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)''.
+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 ====
@@ Line 106: / Line 130: @@
 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:
+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)  |              |
-  * 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''.
+An SSCC will only be generated for a package if the type of the package has the ''CWMS_NeedsSSCC'' field 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 actually generated SSCC will be stored in the ''CWMS_SSCC'' field of the Package Content table.
 ==== Delivery packing slips / Batches and Serials ====