How To Fix /OSP/MSG021 - Book Keeping Entry not updated

SAP Error Message - Details

• Message type: E = Error

• Message class: /OSP/MSG -

• Message number: 021

• Message text: Book Keeping Entry not updated

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 /OSP/MSG021 - Book Keeping Entry not updated ?

  The SAP error message /OSP/MSG021 Book Keeping Entry not updated typically indicates that there was an issue with updating a bookkeeping entry in the system. This can occur in various scenarios, such as during the posting of financial transactions, adjustments, or during the execution of certain programs that involve financial data.
  Possible Causes:
  
  Data Inconsistencies: There may be inconsistencies in the data being processed, such as missing or incorrect information in the required fields.
  Authorization Issues: The user may not have the necessary authorizations to perform the bookkeeping entry update.
  System Configuration: There may be configuration issues in the financial module or related settings that prevent the update from being processed.
  Technical Errors: There could be underlying technical issues, such as database locks, system performance problems, or bugs in the SAP system.
  Posting Period Issues: The posting period may be closed or not open for the transaction type being processed.
  
  Solutions:
  
  Check Data: Review the data being entered for completeness and correctness. Ensure that all mandatory fields are filled out and that the data adheres to the expected formats.
  Review Authorizations: Verify that the user has the necessary authorizations to perform the action. This can be done by checking the user roles and permissions in the SAP system.
  Check Configuration: Consult with your SAP configuration team to ensure that the financial settings are correctly configured. This includes checking the settings for the relevant company codes, posting periods, and document types.
  System Logs: Check the system logs (transaction codes like SLG1) for any additional error messages or warnings that could provide more context about the issue.
  Open Posting Periods: Ensure that the posting period is open for the transaction type you are trying to process. You can check this in the transaction code OB52.
  Technical Support: If the issue persists, consider reaching out to your SAP Basis or technical support team to investigate any underlying technical issues or bugs.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB01 (Post Document), FB02 (Change Document), and OB52 (Open/Close Posting Periods).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide patches and updates.
  Documentation: Review SAP documentation related to financial postings and bookkeeping entries for best practices and troubleshooting steps.
  
  If the problem continues after trying the above solutions, it may be necessary to escalate the issue to SAP support for further investigation.