Please be aware that we have identified issues with SAP B1 v10 PL3 (aka FP2008) and SAP B1 v10 PL4 (aka FP2011) when running Produmex WMS add-on (other 3rd party Add-ons are also affected).
At the moment, we advise not to upgrade version 10 to patch level 3 (FP2008) or patch level 4 (FP2011) and to postpone any such upgrade.
Produmex WMS works without issues on SAP B1 v10 PL2.
The problem only affects installations using SAP B1 version 10 with either PL3(FP2008) or PL4(FP2011). Other SAP versions do not have issues. Also, Produmex Scan is not affected.
Unfortunately, this is an issue caused by SAP B1 10, and not by Produmex WMS code, and therefore cannot be solved from our side. We are working with SAP to resolve this as soon as possible.
These are the identified issues so far:
- FP2011 (PL4) - In the Business Partner Master Data windows, some SAP tabs do not appear (e.g. Contact Persons, Addresses, Properties, Attachments). The Produmex tab appears and works as expected.
Item Master data works as expected, and shows all tabs, including Produmex sub-tabs.
- FP2008 (PL3) - In the Item Master Data, the Produmex tab does not show.
- FP2008 (PL3) Hotfix1- In the Item Master Data, the Produmex tab does show, but all the Produmex sub-tabs are missing.
All of these issues affect only the SAP B1 office client. It does not impact the WMS mobile client and the DI-API functions work correctly, so operations in the warehouse floor are not impacted.
Our current recommendation is not to upgrade SAP 10 to FP2008 or FP201 (aka PL3 and PL4).
In case a customer must upgrade, then they should upgrade to FP2011. They will lose some SAP Business Partner Master Data tabs on office PCs running the WMS add-on. In that case, we suggest having one or more SAP B1 office clients running without the WMS add-on for any office operation needed on the Business Partner Master Data.
An alternative to having a separated client running SAP B1 without WMS is to stop/unload the add-on, then edit the Busines Partner as need, and then restart/load the add-on.
Our team is working on this, as the highest priority, and in close contact with SAP.
However, this is a complicated problem, and so an exact timeline is not known at the moment.
We will keep this article updated with further information as we progress.
Update: 7th December 2020
We have identified issues with FP2011 (PL4) with WMS on the window of Business partner Master Data - some SAP tabs are missing when the add-on is loaded.
Item Master data issues are fixed, with a minor cosmetic issue that the Produmex Tab is now pushed to the last position.
Update: 3rd December 2020
SAP has published FP2011 (PL4), and we are currently testing it.
SBO 10 PL3 (FP2008) will remain incompatible with WMS, customers planning to upgrade to SAP B1 10 PL3 should consider skipping PL3.
WMS 2020.12, planned for release in 21st of December, will be tested against SBO 10 FP2011.
Update: 25th November 2020
The latest FP2011 preview appears to solve all issues, with the minor esthetic exception of the tab order not being followed. FP2011 is planned to be released by SAP on 27th of November.
Update: 10th November 2020
Currently, the planned FP2011 release still does not fix all current issues. We continue to work with SAP to have this solved as soon as possible. For the moment, FP2008 and FP2011 release are not supported and should not be used in a live/production environment when Produmex WMS is needed.
Update: 28th October 2020
SAP development department is working on a solution. We currently do not have an ETA yet.
Update: 19th October 2020
SAP has released a new hotfix, unfortunately, whilst that solves the initial issue, it does not fully resolve all issues. Therefore, for the moment, PL3 is still not compatible with WMS.
We will continue to work with SAP to have a solution to this as soon as possible.
Update: 6th October 2020
SAP has quickly responded to us, and we have tested a new B1 version. This version solved the issues we identified. We are now expecting an SAP release date for the hotfix.
Update: 30th September 2020
We have reported this to SAP. SAP is currently reviewing this, as this potentially affects other add-ons of SAP.