How To Fix 1G090 - Field control was saved

SAP Error Message - Details

• Message type: E = Error

• Message class: 1G - BKK: Konditionen

• Message number: 090

• Message text: Field control was saved

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 1G090 - Field control was saved ?

  The SAP error message "1G090 Field control was saved" typically indicates that there is an issue with the field control settings in a particular transaction or screen. This message is often related to the way fields are configured in the SAP system, particularly in relation to their input/output properties.
  Cause:
  
  Field Control Settings: The error usually arises when there is a mismatch or conflict in the field control settings for a specific field. This can happen if the field is set to be mandatory, but the required data is not provided, or if the field is set to be hidden or read-only when it should be editable.
  Screen Variants: If screen variants are used, they may not be configured correctly, leading to issues with field visibility or input requirements.
  Custom Development: If there are custom enhancements or modifications in the SAP system, they may inadvertently affect the field control settings.
  
  Solution:
  
  Check Field Control Settings: Review the field control settings for the affected fields in the relevant transaction or screen. Ensure that the settings align with the intended behavior (e.g., mandatory fields should be filled, and read-only fields should not be editable).
  Review Screen Variants: If screen variants are being used, check their configuration to ensure that they are set up correctly and do not conflict with the field control settings.
  Debugging: If the issue persists, consider using the SAP debugger to trace the execution of the program and identify where the field control settings are being applied or overridden.
  Consult Documentation: Refer to SAP documentation or notes related to the specific transaction or module to see if there are known issues or additional configuration steps required.
  Contact SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for assistance, especially if it appears to be a bug or a more complex issue.
  
  Related Information:
  
  Transaction Codes: Depending on the context of the error, you may want to check transaction codes related to configuration (e.g., SPRO for customizing).
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide guidance on field control issues.
  User Forums: Consider checking SAP community forums or user groups for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the "1G090 Field control was saved" error and implement a suitable solution.