Do you have any question about this error?
Message type: E = Error
Message class: 37 - Screen Painter
Message number: 077
Message text: Maximum screen limits (&1 lines, &2 columns) exceeded
When the screen was being read from the database, the system found that
one or several screen elements do not fit into the maximum screen area
of 200 lines and 255 columns.
Typically, this kind of constellation can occur when the screen field
has a reference to the Dictionary, but the respective Dictionary object
has meanwhile received a larger output length.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The system resets the determined values for the screen attributes
"Number of Occupied Lines/Columns" down from the maximum values 200 and
255 in order not to have to interrupt work in the Screen Painter.
This check is repeated in the Screen Painter each time the edit screen
changes. The message will possibly be sent several times.
Check immediately which screen fields go beyond the maximum allowed
screen area. Since the Layout Editor cannot fully display these screen
elements or even display them at all, switch to the element list. You
can also switch the the editing screen "Properties" and, if necessary,
increase the attributes "Maintain Lines/Columns" to increase the current
screen area.
If a screen field goes beyond the lower screen limit or even only begins
at a line with a line number > 200, then delete the screen field.
If a screen field goes beyond the right screen limit, you generally do
not need to delete it, but you can set the attribute "Scrollable" and
then reduce the displayed length.
Remember that working in the Layout Editor can be dangerous as long as
this error situation persists. Loss of data and systerm termination
cannot be fully avoided.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message 37077, which states "Maximum screen limits (&1 lines, &2 columns) exceeded," typically occurs when the output of a report or transaction exceeds the maximum allowable limits for the screen display in SAP. This can happen in various scenarios, such as when displaying large datasets or when the layout of a report is not optimized for the screen.
Cause:
- Excessive Data: The report or transaction is trying to display more lines or columns than the SAP GUI can handle.
- Screen Configuration: The screen layout or configuration may not be optimized for the amount of data being displayed.
- Custom Programs: Custom ABAP programs may not have been designed with screen limits in mind, leading to excessive output.
Solution:
Limit Output: Modify the report or transaction to limit the number of lines or columns displayed. This can be done by:
- Adding selection criteria to filter the data.
- Using pagination to break the output into smaller, manageable chunks.
Change Layout: If you are using a custom report, consider adjusting the layout to reduce the number of columns or lines displayed at once.
Use ALV Grids: If applicable, consider using ALV (ABAP List Viewer) grids, which can handle larger datasets more effectively and provide better user interaction.
Check SAP Notes: Look for any relevant SAP Notes that may address this issue or provide patches or updates that could help.
Increase Screen Size: If you have control over the SAP GUI settings, you might be able to increase the screen size, but this is generally not a recommended solution as it may not be feasible in all environments.
Consult with ABAP Developers: If the issue arises from a custom program, consult with ABAP developers to optimize the code and ensure it adheres to SAP's screen limits.
Related Information:
By addressing the underlying causes and implementing the suggested solutions, you should be able to resolve the error message 37077 effectively.
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 | ![]() |
![]() |
37076 Target block overlaps with loop lines
What causes this issue? The cursor position to which you want move or copy the ...
37075 Assign a name to the line selection field
What causes this issue? You are editing a table control with a line selection c...
37078 Selection overlaps with loop lines
What causes this issue? You have chosen either the <LS>Select block end&l...
37080 Place the fields by selecting
What causes this issue? On the <LS>Copy Dictionary/Program Fields</>...
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.