How To Fix FR355 - Screen control for & & is not correct

SAP Error Message - Details

• Message type: E = Error

• Message class: FR - Messages for FI Reporting

• Message number: 355

• Message text: Screen control for & & is not correct

What causes this issue?

The internal screen control for the specified posting key and for the
special G/L indicator was not defined correctly. The screen sequence
cannot be determined.

How to fix this error?

Check your screen control.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FR355 - Screen control for & & is not correct ?

  The SAP error message FR355, which states "Screen control for & & is not correct," typically indicates an issue with the screen control settings in the SAP system. This error can occur in various contexts, often related to the configuration of screen elements or the way transactions are set up.
  Causes:
  
  Incorrect Screen Control Settings: The screen control settings for a particular transaction or program may not be configured correctly.
  Missing or Incorrect Screen Variants: If screen variants are not defined properly or are missing, it can lead to this error.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access certain screens or transactions.
  Custom Development Issues: If there are custom screens or enhancements, they may not be implemented correctly, leading to this error.
  Transport Issues: If the transport of screen changes was not successful, it could lead to inconsistencies.
  
  Solutions:
  
  Check Screen Control Settings: Review the screen control settings in the transaction or program. Ensure that the screen numbers and flow logic are correctly defined.
  Verify Screen Variants: If screen variants are used, check that they are correctly defined and assigned to the relevant user roles.
  Review Authorizations: Ensure that the user has the necessary authorizations to access the transaction or screen. You can use transaction SU53 to analyze authorization issues.
  Debugging: If you have access to debugging tools, you can debug the program to identify where the screen control is failing.
  Check Custom Code: If there are custom developments, review the code for any issues related to screen control.
  Transport Management: If the issue arose after a transport, check the transport logs for errors and ensure that all necessary objects were transported correctly.
  
  Related Information:
  
  Transaction Codes: You may want to check transactions like SE80 (Object Navigator) or SE11 (Data Dictionary) to review the screen definitions and related objects.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Community Forums: Consider checking SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or development team for further assistance.