Do you have any question about this error?
Message type: E = Error
Message class: 37 - Screen Painter
Message number: 134
Message text: Table control & can already be resized vertically; not executed
You are trying to assign attribute "Resize vertically" to a table
control, or the attribute "Variable steploop" to a steploop. Attribute
"Resize vertically" has already been assigned to a table control.
Vertical resizing can only be assigned to one object.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message "37134: Table control & can already be resized vertically; not executed" typically occurs in the context of SAP GUI when working with table controls in screen programming (dynpro). This error indicates that the system is trying to resize a table control that is already set to be resizable vertically, which is not allowed.
Cause:
- Redundant Resize Attempt: The error is triggered when there is an attempt to resize a table control that has already been defined as resizable in the screen layout.
- Screen Attributes: The attributes of the table control in the screen definition may already allow for vertical resizing, and the program is trying to apply a resize operation again.
Solution:
- Check Screen Definition: Go to the screen painter (SE80 or SE41) and check the properties of the table control. Ensure that the "Resizable" property is set correctly.
- Remove Redundant Code: If your ABAP code is trying to resize the table control using the
RESIZE
statement or similar, you may need to remove or comment out that part of the code if the control is already resizable.- Review Program Logic: Ensure that the logic in your program does not attempt to resize the table control multiple times unnecessarily.
- Debugging: If the issue persists, use the debugger to trace the execution flow and identify where the resize attempt is being made.
Related Information:
If you continue to experience issues after following these steps, consider consulting SAP documentation or reaching out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
37133 Table control & can already be resized horizontally (not executed)
What causes this issue? You want to assign attribute "Horizontal resizing&...
37132 Dynpro & & was generated in display mode
What causes this issue? The unchanged screen was generated in display mode, i.e...
37135 Loop contains an illegal element. Operation not performed
What causes this issue? Areas for subscreens must always be defined in a blank ...
37136 You cannot insert a line in this area
What causes this issue? By inserting a line, you have changed the subscreen are...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.