Solution : https://service.sap.com/sap/support/notes/1035436 (SAP Service marketplace login required)
Summary :
When using the JNet/JGantt Java applet, an urgent update requires a new JAR file installation, not included in the standard transport cycle. Users must manually update the global MIME repository by uploading and replacing JAR files through transaction SE80. The specific paths and procedures are detailed, and files like "com_sap_tc_webdynpro_network(N).jar," "JNetAppGantt(S).jar," and "y.jar" need to be updated together. Additionally, different versions of these files exist for different SAP Basis Releases, and post-update, a cache deletion on client machines might be necessary to reflect changes.
Key words :
sap/bc/webdynpro/sap/public/bc/ssr/uuielibs/active_component, jnet/jgantt java applet, jnet/jgantt applet, urgent problem requires, normal transport-cycle, call transaction se80, upload/download->upload, default ui manager, java runtime environment, signed versions apply
Related Notes :
| 1559125 | Incorrect display in Gantt of tasks with duration of zero |
| 1509091 | QGM: General note for Quality Gate Management 7.1 |
| 1256490 | QGM: General note for Quality Gate Management 7.0 |
| 1046896 | Gantt applet does not start |