cobi.wms:app_options
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cobi.wms:app_options [2025/06/02 14:25] – thuth | cobi.wms:app_options [2025/10/27 11:38] (current) – [Document filtering] thuth | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| ===== Warehouse ===== | ===== Warehouse ===== | ||
| + | |||
| + | ==== Hide inactive warehouses ==== | ||
| + | |||
| + | When enabled, this option hides all warehouses marked as inactive in SAP Business One from warehouse selection lists. | ||
| + | Note: The warehouse(s) must be set to " | ||
| + | |||
| + | ==== Show inactive bin locations ==== | ||
| + | |||
| + | When enabled, bin locations that are marked as inactive in SAP Business One will still be shown in selection lists within COBI.wms. \\ | ||
| + | Note: The bin location must be flagged as " | ||
| + | |||
| + | ==== Warehouse ==== | ||
| You can assign each Android device to a specific warehouse. | You can assign each Android device to a specific warehouse. | ||
| Line 28: | Line 40: | ||
| **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 **'' | **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 **'' | ||
| - | **Note:** In newer versions of COBI.wms, the view ''< | + | **Note:** In newer versions of COBI.wms, the view ''< |
| Note that the UDF is not actually used for all document types. | Note that the UDF is not actually used for all document types. | ||
| Line 102: | Line 114: | ||
| When enabled, purchase or delivery orders assigned to DropShip warehouses will be excluded from the list. This helps to avoid confusion and ensures that only relevant stock-related orders are displayed in the receipt process. | When enabled, purchase or delivery orders assigned to DropShip warehouses will be excluded from the list. This helps to avoid confusion and ensures that only relevant stock-related orders are displayed in the receipt process. | ||
| + | |||
| + | ==== Show subnumber of purchase order ==== | ||
| + | |||
| + | When enabled, COBI.wms displays the subnumbers of purchase orders during goods receipt. \\ | ||
| + | This helps users clearly identify and distinguish between multiple positions on a single purchase order. | ||
| ===== Picking ===== | ===== Picking ===== | ||
| Line 143: | Line 160: | ||
| When enabled, items in the pick list are grouped and displayed according to their originating base documents (e.g. sales orders or production orders). In the case of consolidated pick lists, multiple base document numbers will be shown. | When enabled, items in the pick list are grouped and displayed according to their originating base documents (e.g. sales orders or production orders). In the case of consolidated pick lists, multiple base document numbers will be shown. | ||
| Users can tap on a specific base document number to view only the items associated with that document, making it easier to track and process grouped deliveries. | Users can tap on a specific base document number to view only the items associated with that document, making it easier to track and process grouped deliveries. | ||
| + | |||
| + | ==== Show if pick list is already started ==== | ||
| + | |||
| + | A green 'In Progress' | ||
| + | If another user tries to open a list that is already in progress, a warning message appears: 'This list is already being worked on. Continue?' | ||
| + | This helps warehouse staff avoid duplicate processing and improves transparency during ongoing operations. | ||
| + | |||
| + | UDF definition: | ||
| + | |||
| + | ^ Category | ||
| + | | Inventory -> Pick List | '' | ||
| + | |||
| + | |||
| + | ==== Picking with unit ==== | ||
| + | |||
| + | A new 'Pick Unit' button allows users to add or scan a pick unit, enabling picking based on predefined packaging units. \\ | ||
| + | This improves efficiency when handling bulk or standardized packaging units. | ||
| + | |||
| + | ==== Show text lines from sales orders ==== | ||
| + | |||
| + | When enabled, text lines from the original sales order will be displayed during picking. \\ | ||
| + | This provides useful information for the picker, such as special handling instructions or customer notes. | ||
| + | Note: Text lines are read from SAP Business One and displayed for reference only. | ||
| + | |||
| + | ==== Show transport type ==== | ||
| + | |||
| + | Displays the transport or shipping method (e.g. "UPS Express" | ||
| + | This helps logistics personnel prepare for packing and shipping according to customer preferences. \\ | ||
| + | Note: The transport type must be defined in the sales order in SAP Business One. | ||
| + | |||
| + | ==== Group similar articles ==== | ||
| + | |||
| + | Groups identical items within the pick list to avoid duplicate lines. \\ | ||
| + | This simplifies the picking process and reduces unnecessary repetition for the warehouse staff. \\ | ||
| + | Note: Only articles with matching item codes and units are grouped. | ||
| ===== Delivery ===== | ===== Delivery ===== | ||
| Line 149: | Line 201: | ||
| 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. | 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. | ||
| + | |||
| + | ==== Don't show documents for DropShip-Warehouses ==== | ||
| + | |||
| + | When enabled, delivery documents linked to DropShip warehouses are hidden in COBI.wms. This ensures that only relevant warehouse-based deliveries are shown, preventing confusion when handling virtual or supplier-managed stock. | ||
| + | Note: A warehouse must be marked as a " | ||
| ==== Delivery packing slips ==== | ==== Delivery packing slips ==== | ||
| Line 217: | Line 274: | ||
| When enabled, the system allows delivery documents to include line items with a quantity of 0. This can be useful for retaining item structure or references in the document, even if no quantity is being delivered for specific lines. | When enabled, the system allows delivery documents to include line items with a quantity of 0. This can be useful for retaining item structure or references in the document, even if no quantity is being delivered for specific lines. | ||
| - | Perfekt! Hier ist der vollständige englische Beschreibungstext für die Option **" | + | ==== Choose shipping address for delivery ===== |
| - | --- | + | Allows the user to manually select the shipping address during the delivery process. \\ |
| + | This is useful when multiple delivery addresses exist or when a different address is required than the one stored in the sales order. \\ | ||
| + | Note: By default, the shipping address from SAP Business One is pre-filled but can be adjusted here. | ||
| ==== Hide inactive Package Types (requires UDF) ==== | ==== Hide inactive Package Types (requires UDF) ==== | ||
| - | When enabled, this option hides package types that are marked as inactive using a specific User-Defined Field (UDF). This helps to simplify selection lists by displaying only active and relevant packaging options. | + | When enabled, this option hides package types that are marked as inactive using a specific User-Defined Field (UDF). |
| - | + | ||
| - | **UDF Setup Instructions in SAP Business One:** | + | |
| To activate this feature, a UDF must be created in SAP Business One: | To activate this feature, a UDF must be created in SAP Business One: | ||
| - | * **Location: | + | ^ Category ^ Title ^ Data Type ^ Valid values |
| - | Go to `Tools > Customization Tools > User-Defined Fields – Management` | + | | Master Data → Package Types | '' |
| - | Navigate to: `Master Data > Package Types` | + | |
| - | * **Field Configuration: | + | ===== Purchase Return ===== |
| - | * **Title:** `WMS_Active` | + | ==== Don't show documents for DropShip-Warehouses ==== |
| - | * **Type:** `Alphanumeric` | + | |
| - | * **Length:** `1` | + | |
| - | * **Validation: | + | |
| - | * `Y` – Yes (Active) | + | Hides all purchase return documents that are linked to DropShip warehouses. \\ |
| - | * `N` – No (Inactive) | + | This ensures that only relevant returns from physical warehouses are visible, avoiding confusion when working with supplier-managed deliveries. \\ |
| - | * **Set Default Value:** `Y` | + | Note: The warehouse must be marked as a " |
| - | * **Mandatory Field:** Checked | + | |
| + | ===== Sales Return ===== | ||
| + | |||
| + | ==== Don't show documents for DropShip-Warehouses ==== | ||
| + | |||
| + | When enabled, sales return documents related to DropShip warehouses are hidden in COBI.wms. \\ | ||
| + | This helps users focus only on returns processed through physical warehouses and avoids unnecessary document clutter. \\ | ||
| + | Note: The warehouse must be flagged as a " | ||
| ===== Issue for Production ===== | ===== Issue for Production ===== | ||
| Line 250: | Line 310: | ||
| When enabled, the system verifies if all required materials for the production are available in stock. If not, a warning icon (exclamation mark) is shown to indicate that the production receipt cannot be completed due to missing stock quantity. | When enabled, the system verifies if all required materials for the production are available in stock. If not, a warning icon (exclamation mark) is shown to indicate that the production receipt cannot be completed due to missing stock quantity. | ||
| + | |||
| + | ==== Show when an output has been made ==== | ||
| + | |||
| + | Displays a indicator when a production output has already been posted for the related production order. \\ | ||
| + | This gives warehouse staff immediate visibility into whether materials have already been issued. \\ | ||
| + | Note: This information is based on the production status in SAP Business One. | ||
| ===== Receipt from Production ===== | ===== Receipt from Production ===== | ||
| Line 256: | Line 322: | ||
| 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. | 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. | ||
| + | |||
| + | ==== Automatically close production orders on reaching or exceeding open quantity ==== | ||
| + | |||
| + | Automatically closes a production order in SAP Business One once the reported quantity equals or exceeds the remaining open quantity. \\ | ||
| + | This ensures that completed orders are finalized without manual intervention, | ||
| + | |||
| + | ===== Item Info ===== | ||
| + | |||
| + | ==== Show item picture ==== | ||
| + | |||
| + | Displays the item’s image (if available) during item selection or lookup. \\ | ||
| + | This supports quick visual identification, | ||
| + | Note: The image must be stored in the item master in SAP Business One. | ||
| + | |||
| + | ==== Show item barcode ==== | ||
| + | |||
| + | Shows the item’s barcode number(s) during lookup. \\ | ||
| + | This helps verify correct scanning and supports barcode-based operations. \\ | ||
| + | Note: Barcodes must be defined in the item master data in SAP Business One. | ||
| + | |||
| + | ==== Show item price ==== | ||
| + | |||
| + | Displays the current item price based on the selected price list. \\ | ||
| + | This is helpful for verifying pricing during operations or customer interactions. \\ | ||
| + | Note: Prices are retrieved from the SAP Business One price list linked to the user or warehouse. | ||
| + | |||
| + | ==== Show item weight ==== | ||
| + | |||
| + | Displays the weight of the item as defined in SAP Business One. \\ | ||
| + | Useful for shipping, packing, and load planning. \\ | ||
| + | Note: The weight must be defined in the item master data in SAP Business One. | ||
| + | |||
| + | ==== Show item dimensions ==== | ||
| + | |||
| + | Shows the dimensions (length, width, height) of the item. \\ | ||
| + | This is useful for packaging, space planning, and transport calculations. \\ | ||
| + | Note: Dimensions must be maintained in SAP Business One item master data. | ||
| + | |||
| + | ==== Show default bin ==== | ||
| + | |||
| + | Displays the default bin assigned to the item. \\ | ||
| + | This helps pickers or stockers quickly locate the item within the warehouse. \\ | ||
| + | Note: The default bin must be set in SAP Business One if bin location management is enabled. | ||
| + | |||
| + | ==== Show serials/ | ||
| + | |||
| + | Shows the serial or batch number details for the selected item. \\ | ||
| + | This is critical for traceability and quality control in regulated industries. | ||
| + | Note: The item must be marked as serialized or batch-managed in SAP Business One. | ||
| + | |||
| + | ==== Show item description ==== | ||
| + | |||
| + | Displays the item’s full description, | ||
| + | This gives users additional context beyond the item code. | ||
| + | Note: Pulled directly from the item master data. | ||
| + | |||
| + | ==== Show item stocks ===== | ||
| + | |||
| + | Displays current stock levels per warehouse or bin location. \\ | ||
| + | |||
| + | ==== Show linked items ==== | ||
| + | |||
| + | Shows linked items (e.g. components) defined in SAP Business One. \\ | ||
| + | This is useful for assemblies, multi-part products, or items involved in production processes. \\ | ||
| + | ==== Show linked documents ==== | ||
| + | |||
| + | Shows related SAP documents, such as open sales orders or purchase orders associated with the item. \\ | ||
| + | This gives users a full context of item activity. | ||
| + | Note: Based on document relationships in SAP Business One. | ||
| ===== Miscellaneous ===== | ===== Miscellaneous ===== | ||
| Line 269: | Line 404: | ||
| ==== Negative stock allowed ==== | ==== 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.\\ | + | 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' | + | Note: SAP Business One might still block the booking of such documents if you haven' |
| ==== Negative bin location allowed ==== | ==== Negative bin location allowed ==== | ||
| - | Allows stock levels in bin locations to go negative during transactions.\\ | + | Allows stock levels in bin locations to go negative during transactions. \\ |
| - | //Note: This option must also be enabled in SAP Business One to take effect.// | + | Note: This option must also be enabled in SAP Business One to take effect. |
| ==== Negative Quantity allowed ==== | ==== Negative Quantity allowed ==== | ||
| - | Permits entering negative quantities in transactions, | + | Permits entering negative quantities in transactions, |
| - | //Note: This option must also be enabled in SAP Business One to take effect.// | + | Note: This option must also be enabled in SAP Business One to take effect. |
| ==== Auto-select default bin location of item ==== | ==== Auto-select default bin location of item ==== | ||
| Line 292: | Line 427: | ||
| ==== Username as document remarks ==== | ==== Username as document remarks ==== | ||
| - | Automatically adds the logged-in user's name as a remark in the document.\\ | + | Automatically adds the logged-in user's name as a remark in the document. |
| - | //Note: If the scanner is configured with a device ID, the device ID will be used as the username instead.// | + | Note: If the scanner is configured with a device ID, the device ID will be used as the username instead. |
| ==== Skip screen showing booked document ==== | ==== Skip screen showing booked document ==== | ||
| Line 312: | Line 447: | ||
| Actively blocks transactions that would violate defined minimum or maximum inventory levels.\\ | Actively blocks transactions that would violate defined minimum or maximum inventory levels.\\ | ||
| //Note: Minimum and maximum inventory levels must be defined in SAP Business One.// | //Note: Minimum and maximum inventory levels must be defined in SAP Business One.// | ||
| + | |||
| + | |||
| + | ==== Warning when min.max. inventory is exceeded or undershot per warehouse ==== | ||
| + | |||
| + | Displays a warning if the inventory level in a specific warehouse goes below the minimum or above the maximum threshold. \\ | ||
| + | This helps users maintain stock levels within defined limits and avoid overstocking or stockouts. | ||
| + | Note: The min./max. inventory thresholds must be set in the item master per warehouse in SAP Business One. | ||
| + | |||
| + | ==== Blocking of exceed or undershoot of min./max. inventory per warehouse ==== | ||
| + | |||
| + | Prevents transactions that would result in exceeding or falling below the defined minimum or maximum inventory level in a specific warehouse. \\ | ||
| + | This ensures strict adherence to stock level rules. | ||
| + | Note: This restriction only applies if min./max. values are configured in SAP Business One for the item per warehouse. | ||
| ==== Show item images ==== | ==== Show item images ==== | ||
| Line 320: | Line 468: | ||
| Shows the “FreeText” field from the document line, useful for custom notes or additional item information. | Shows the “FreeText” field from the document line, useful for custom notes or additional item information. | ||
| + | |||
| + | ==== Hide inactive business partners ==== | ||
| + | |||
| + | Hides all business partners (customers, vendors) that are marked as inactive in SAP Business One. \\ | ||
| + | This helps streamline selection lists and prevents accidental use of deactivated records. | ||
| + | Note: The business partner must be marked as “inactive” in SAP Business One. | ||
| ===== Session timeout (minutes) ===== | ===== Session timeout (minutes) ===== | ||
cobi.wms/app_options.1748867101.txt.gz · Last modified: by thuth