Solution : https://service.sap.com/sap/support/notes/1707062 (SAP Service marketplace login required)
Summary :
When multiple processes of an SAP instance try to generate a GUI status, only the first succeeds in updating the database, while subsequent processes perform inline generation without updating the database. Memory used in this operation is freed at the next database commit. To prevent unnecessary locks on D347T and EUDB tables, it is essential to implement the corrections from SAP Note 1721936. Furthermore, to resolve issues with menu bar question marks, employing a disp+work package at the specified SP Patch Level is recommended.
Key words :
processes generate inline, avoid unrequired locks, terms question marks, menu bar solution, disp+work package, sp patch level, patch level, gui status, database update, memory required
Related Notes :
| 1778620 | |
| 1761468 | |
| 1761297 | |
| 1738305 | |
| 1725469 | |
| 1721936 | GUI status inline generation (ABAP part) |
| 1698960 | Message 00 264 is not output |
| 1608273 | Deadlock on D342L and D345T |
| 1566845 | Deadlock on D342L and D345T |