Critical issues in 2021R2 when PJM is deactivated

A huge development was released in 2021R2 to improve PJM performances.
Many functions which can be linked to projects (sales, purchases etc...) were impacted despite all the manual and automated QA tests.
3 bugs are identified, we recommend to install those 3 hotfixes on 2021R2 if PJM is deactivated 

1- When creating a sales order, a blocking error occurs if the PJM module is deactivated (activity code PJM deactivated)
Error : @X3.TRT/SUBSOHA$.adx (3222) Error 6 : Variable inexistent GLONPBU
This issue has been fixed in 2021R3 and can be fixed in 2021R2 by installing hotfix WX_248312_R090_026.dat (WX_248312_R090_026.zip) available on our ftp site. 

2- When entering in the projects function GESOPP, an error message is displayed if the PJM module is deactivated (activity code PJM deactivated)
Error : @X3.TRT/OPPOR_CSTD_EVENTS$adx(45) Error 112 : Non-existent structure member PJM
This issue has been fixed in 2021R3 and can be fixed in 2021R2 by installing the hotfix WX_248418_R090_026.dat   (WX_248418_R090_026.zip) available on our ftp site.

3- All the functions which can be linked to projects (sales, purchases etc...) may have an error when entering a value in the project field.
Error Reference PJM: Non-existent class
This error may also occur when validating the OPPOR class.
This issue has been fixed in 2021R3 and can be fixed in 2021R2 by installing the  hotfix WX_247513_R090_026.dat (WX_247513_R090_026.zip) available on our ftp site.

Anonymous