How To Fix KE774 - Entries were reset to the SAP standard settings

SAP Error Message - Details

• Message type: E = Error

• Message class: KE -

• Message number: 774

• Message text: Entries were reset to the SAP standard settings

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 KE774 - Entries were reset to the SAP standard settings ?

  The SAP error message KE774, which states "Entries were reset to the SAP standard settings," typically occurs in the context of controlling (CO) module settings, particularly when dealing with cost centers, internal orders, or profit centers. This message indicates that certain settings or entries have been reverted to the default SAP settings, which can happen for various reasons.
  Causes:
  
  Configuration Changes: If there have been recent changes to the configuration settings in the controlling area, it may lead to the resetting of entries.
  Transport Requests: If a transport request was moved from one environment to another (e.g., from development to production), it might overwrite existing settings with standard values.
  Data Consistency Issues: Inconsistencies in the data or settings can trigger the system to revert to standard settings to maintain integrity.
  User Authorizations: Lack of proper authorizations for users to make changes can lead to the system reverting to standard settings.
  System Upgrades or Patches: Upgrading the SAP system or applying patches can sometimes reset certain configurations to their defaults.
  
  Solutions:
  
  Review Configuration Settings: Check the configuration settings in the controlling area to ensure they are set up correctly. You can do this through transaction codes like OKKP (Controlling Area) or OKEQ (Cost Element).
  Check Transport Requests: If the issue arose after a transport, review the transport logs to see if any relevant settings were overwritten. You may need to reapply the necessary configurations.
  Data Consistency Check: Run consistency checks to identify any discrepancies in the data. Use transaction codes like KAH1 (Cost Center) or KSB1 (Cost Centers: Actual Line Items) to analyze the data.
  User Authorizations: Ensure that users have the necessary authorizations to make changes in the controlling area. You may need to consult with your SAP security team.
  Reapply Custom Settings: If the settings were reset, you may need to reapply any custom configurations that were previously in place.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on similar issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OKKP, OKEQ, KAH1, and KSB1 for managing controlling settings.
  SAP Documentation: Refer to SAP Help documentation for detailed information on controlling settings and error messages.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.