How To Fix REXCCORR021 - An error occured during saving. Check the application log.

SAP Error Message - Details

• Message type: E = Error

• Message class: REXCCORR - Correction/Reversal Invoices

• Message number: 021

• Message text: An error occured during saving. Check the application log.

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 REXCCORR021 - An error occured during saving. Check the application log. ?

  The SAP error message REXCCORR021, which states "An error occurred during saving. Check the application log," typically indicates that there was an issue when trying to save data in the system, often related to the correction or transport of data in the context of SAP's correction and transport system (CTS).
  Possible Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to perform the action.
  Data Consistency Errors: There may be inconsistencies in the data being processed, which could prevent saving.
  System Configuration Issues: Incorrect configuration settings in the system can lead to errors during data saving.
  Transport Request Issues: Problems with the transport request, such as it being locked or not properly released.
  Application Log Errors: There may be specific errors logged in the application log that provide more details about the issue.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the action. This can be done by reviewing the user's roles and permissions.
  Review Application Log: Use transaction code SLG1 to check the application log for more detailed error messages. This can provide insights into what went wrong during the save operation.
  Data Validation: Validate the data being processed to ensure there are no inconsistencies or errors. This may involve checking for missing or incorrect entries.
  Transport Request Management: If the error is related to a transport request, check the status of the transport request in transaction SE09 or SE10. Ensure that it is not locked and is properly released.
  System Configuration Review: Review the system configuration settings related to the process you are trying to execute. Ensure that all necessary configurations are in place.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates available that resolve the issue.
  
  Related Information:
  
  Transaction Codes: 
  
  SLG1: Application Log
  SE09/SE10: Transport Organizer
  
  
  SAP Support: If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. They can provide more specific guidance based on the system's configuration and logs.
  Documentation: Review SAP documentation related to the correction and transport system for best practices and troubleshooting steps.
  
  By following these steps, you should be able to identify and resolve the issue related to the REXCCORR021 error message.