Solution : https://service.sap.com/sap/support/notes/311393 (SAP Service marketplace login required)
Summary :
In SAP environments using docking controls, the resizing issues arise as the screen fails to utilize all available space and the subscreen editor does not adjust correctly until a subsequent data release. This problem is managed by the Control Framework (CFW), which only allocates GUI window areas to the screen processor not occupied by dockers during PBO processing. Historically, this required additional communications between frontend and kernel up to Release 4.6B. Post 4.6C updates have enabled CFW to adjust dynamically to docker size changes, eliminating the need for extra roundtrips. Correct application design and resizing strategy, particularly in handling dockers, are crucial to addressing these issues effectively.
Key words :
additional key words docking container, control framework functions required, control-framework basically consists, size adjustment generally requires, cfw constantly informs, change table views, abap source code, downward-compatible kernel, processed loop step', correct application design
Related Notes :
| 397360 | GANTT chart does not fill screen completely |
| 394228 | M/AM: Missing areas in the customer-subscreen |
| 357241 | Scrollbar for lists with docking control |
| 351685 | Screen objects resized incorrectly when window is enlarged |
| 203023 | Understanding screen compression and resizing |