=====Produmex WMS 2023.10=====

[[http://www.produmex.name/PmxVersions.php|Produmex download page]] \\
[[http://builds.produmex.name/ProdumexWMS/2023.10/|Download version 2023.10]]

<WRAP round info>

**Tested SAP Business One versions**
  * SAP B1 10.0 FP2208 HF2 64-bit MSSQL 2019
  * SAP B1 10.0 FP2208 HF2 64-bit HANA 2.00.044.00
//Note: Older and newer SAP Business One versions usually also work, but have not been specifically tested in this version.//
</WRAP>

<WRAP center round important 100%>
Make sure that you do not use SBO10 PL3 (FP2008) or PL4 (FP2011) including any of their hotfixes with Produmex WMS. If you are about to upgrade SAP Business One to a  PL higher than the one we have tested Produmex WMS on, make sure that you always test your Produmex WMS processes in a test SAP environment before performing the SAP PL upgrade on the live environment. For more information click [[https://support.boyum-it.com/hc/en-us/articles/360013784058-Warning-WMS-with-SAP-Business-One-PL3-and-PL4-aka-FP2008-and-FP2011-|here]].</WRAP> 

=== DB version: 764 ===
=== DB Branch version: 0 ===
=== Required Add-On Loader version: 22 ===
----
**Additional features**



  * ** Overriding and Reinstating Beas Work Order lock for new location at all AdHoc moves**

In the Beas-WMS integration feature, WMS can now reallocate Beas WO locks for storage locations with Full and Multiple SSCCs. When choosing AdHoc Movement for either Full, Multiple or Partial Logistic Units on the WMS mobile client, it is possible to override the Beas lock on the selected SSCC and have it reinstated for a new location.

//In a real-life scenario it is useful to know throughout the production - and logistic - process where all items (including all production raw materials or items, too) are positioned within the warehouse at any given point. For enhanced efficiency and accessibility for production, placing a lock or reservation on certain items can be key so that they are 'locked' into their designated storage location within the warehouse and not transferred accidentally. However, in certain situations, locked materials might need to be moved from their allocated position by logistics e.g. due to lack of storage space. In this scenario it is possible to override the production lock on the logistics side and reallocate it for the item at a different storage location, so that the repositioned items can be found instantly and easily by production - creating a new, allocated storage space.//

In this process, when confirming an AdHoc move for the selected, locked SSCC on the WMS mobile client, WMS removes the Beas WO lock in order for the SSCC to be moved and notifies Beas about the transfer. Beas then reinstates the lock for the new location after the move has been performed. [[implementation:wms:adhoc_moves&#beas-wms_lock_reservation_override|See documentation]].



  * ** Memory Cleaner for Mobile Client (MC²)** 

Fully automated Memory Cleaner for Mobile Client (MC²) introduced in Produmex WMS 2023.10.

The memory usage of every Mobile Client instance is strictly optimized and ideally lowered by hundreds of MBs or even a GB. (E.g. if 50 Mobile Client instances are used on a terminal server, it means that the freed up memory can easily reach 50GB or more depending on the workload. Note: one Mobile Client instance means one //Produmex.Sbo.Logex.Execute.FatClient.exe// instance in the memory.) [[implementation:wms:app_config#fat_client|See "MemoryCleanerFrequencyInSeconds" in "Fat Client" in documentation]].

  * **Consolidation of (Remaining) Default Qantity displayed for Purchase on mobile client**

A checkbox ('Remaining quantity by default? (Y/N)') to the [[implementation:wms:purchasedeliverygen|Purchase Delivery Generator]] and a drop-down menu ('Remaining Quantity by Default?') added to the [[implementation:wms:imd_pmxpurchase|Produmex Purchase tab]] to set the open quantity on base document as default to be displayed on the mobile client for Reception in Purchase. [[implementation:wms:reception_flow#add_the_number_of_items|See documentation]].


**Bug fixes**
^Ticket^Description^
|201927|Changes in functionality to the default quantity of PO receipts[[http://builds.produmex.name/ProdumexWMS/2023.10/2023.10.00/|2023.10.00]]|
|174391|Produmex  Item Master Data - Purchase Goods Receipt shows different quantity when entering itemcode as a barcode[[http://builds.produmex.name/ProdumexWMS/2023.10/2023.10.00/|2023.10.00]]|
|191001|Quantity displayed on scanner is not 1 but the quantity of the purchase order line[[http://builds.produmex.name/ProdumexWMS/2023.10/2023.10.00/|2023.10.00]]|
|201415|The default quantity on receiving of PO on the scanner cannot be set up to 0 instead of the PO line[[http://builds.produmex.name/ProdumexWMS/2023.10/2023.10.00/|2023.10.00]]|
|200155|Expiry date not calculated when doing bulk reception[[http://builds.produmex.name/ProdumexWMS/2023.10/2023.10.01/|2023.10.01]]|
|192384|Other operations branch off to Cycle counting even when setting is disabled[[http://builds.produmex.name/ProdumexWMS/2023.10/2023.10.01/|2023.10.01]]|
|205489|Cycle count form crashes[[http://builds.produmex.name/ProdumexWMS/2023.10/2023.10.01/|2023.10.01]]|
|207696|WMS not respect BEAS reservation at PLP creation[[http://builds.produmex.name/ProdumexWMS/2023.10/2023.10.01/|2023.10.01]]|
|200690|Picking for Production error when user scans an SSCC with out the required itemcode[[http://builds.produmex.name/ProdumexWMS/2023.10/2023.10.01/|2023.10.01]]|