cobi.wms:known_issues
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| cobi.wms:known_issues [2022/07/05 13:45] – [Missing support for Assembly BOM] tkammer | cobi.wms:known_issues [2026/02/17 13:32] (current) – [Pre-Allocation of Batch and Serial Numbers for Pick Lists] thuth | ||
|---|---|---|---|
| Line 25: | Line 25: | ||
| For this reason, you must only allocate the batch number in the underlying Sales Order, and not directly in the Pick List. If you have several Pick Lists based on the same Sales Order, your warehouse employees will see **all** batch numbers allocated in the underlying Sales Order. | For this reason, you must only allocate the batch number in the underlying Sales Order, and not directly in the Pick List. If you have several Pick Lists based on the same Sales Order, your warehouse employees will see **all** batch numbers allocated in the underlying Sales Order. | ||
| + | |||
| + | ====== Forcing a Recreation of COBI.wms Database Views (Dropping Views) ====== | ||
| + | |||
| + | ==== Background / Use Case ==== | ||
| + | When customer-specific customizations have been made to COBI.wms or if data structures in SAP Business One have changed significantly, | ||
| + | |||
| + | ==== How does the mechanism work? ==== | ||
| + | Every time a user logs in via the MDE device (scanner), COBI.wms checks if a specific version view exists in the SAP company database (the view %%cwXX__version%%). | ||
| + | |||
| + | If this view is deleted (**" | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== 1. Identifying the correct View ==== | ||
| + | The name of the view that needs to be dropped depends on the installed COBI.wms app version (the %%XX%% represents the version number). | ||
| + | |||
| + | ^ COBI.wms Version ^ Name of the View ^ | ||
| + | | 2.38 | %%cw38__version%% | | ||
| + | | 2.40 | %%cw40__version%% | | ||
| + | | 2.42 | %%cw42__version%% | | ||
| + | | 2.43 | %%cw43__version%% | | ||
| + | |||
| + | **Note:** This naming logic will continue for future versions. | ||
| + | |||
| + | ==== 2. Dropping the View ==== | ||
| + | Depending on your database system (SAP HANA, MSSQL, or Azure SQL), execute the corresponding command against your SAP company database. | ||
| + | |||
| + | **For Microsoft SQL Server (MSSQL) & Azure SQL:**\\ | ||
| + | Open the SQL Server Management Studio (SSMS), select the respective company database, and execute the following script (Example for Version 2.43): | ||
| + | |||
| + | <code sql> | ||
| + | DROP VIEW cw43__version; | ||
| + | </ | ||
| + | |||
| + | // | ||
| + | |||
| + | **For SAP HANA:**\\ | ||
| + | Open the SAP HANA Studio, select your company schema, and open the SQL console. Execute the following script (Example for Version 2.43): | ||
| + | |||
| + | <code sql> | ||
| + | DROP VIEW " | ||
| + | </ | ||
| + | |||
| + | ==== 3. Rebuilding the Views ==== | ||
| + | Once the view has been successfully dropped from the database, take your MDE device. | ||
| + | |||
| + | - Completely close the COBI.wms app. | ||
| + | - Reopen the app and log in. | ||
| + | - The login process will take slightly longer this one time (approx. 5-15 seconds) because all views, including the latest data structures and customizations, | ||
cobi.wms/known_issues.txt · Last modified: by thuth