How To Fix KE773 - Initial entries were reset during save

SAP Error Message - Details

• Message type: E = Error

• Message class: KE -

• Message number: 773

• Message text: Initial entries were reset during save

What causes this issue?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

During save, the system sets initial entries in the <LS>PA Transfer
Structure</> column to the SAP default values.

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KE773 - Initial entries were reset during save ?

  The SAP error message KE773 ("Initial entries were reset during save") typically occurs in the context of CO (Controlling) module transactions, particularly when dealing with internal orders, cost centers, or profit centers. This error indicates that there was an issue with the data being processed during a save operation, leading to the reset of initial entries.
  Causes:
  
  Data Inconsistency: The data being saved may have inconsistencies or errors that prevent it from being processed correctly.
  Missing Required Fields: Certain mandatory fields may not have been filled out, leading to the inability to save the entries.
  Authorization Issues: The user may not have the necessary authorizations to perform the save operation.
  Technical Issues: There could be underlying technical issues, such as database locks or system performance problems.
  Configuration Issues: Incorrect configuration settings in the CO module can lead to this error.
  
  Solutions:
  
  Check Data Entries: Review the entries you are trying to save for any inconsistencies or missing mandatory fields. Ensure that all required fields are filled out correctly.
  Review Authorizations: Ensure that the user has the necessary authorizations to perform the action. If not, contact your SAP security administrator to grant the required permissions.
  Check for Locks: Use transaction codes like SM12 to check for any database locks that might be preventing the save operation. If locks are found, they may need to be released.
  Consult Logs: Check the application logs (transaction SLG1) for more detailed error messages that can provide insights into what went wrong during the save operation.
  Configuration Review: If the issue persists, review the configuration settings in the CO module to ensure they are set up correctly. This may require the assistance of an SAP consultant or a functional expert.
  System Performance: If the system is experiencing performance issues, consider checking with your IT team to ensure that the SAP system is running optimally.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as KE51 (Create Internal Order), KE52 (Change Internal Order), and KE53 (Display Internal Order) to navigate through the CO module effectively.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to the CO module for best practices and guidelines on data entry and configuration.
  
  If the problem persists after trying the above solutions, it may be beneficial to escalate the issue to your SAP support team or consult with an SAP expert for further assistance.