How To Fix /EACC/MSG_ABSTR_JRNL113 - Source document persistence does not exist for data basis &1

SAP Error Message - Details

• Message type: E = Error

• Message class: /EACC/MSG_ABSTR_JRNL -

• Message number: 113

• Message text: Source document persistence does not exist for data basis &1

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 /EACC/MSG_ABSTR_JRNL113 - Source document persistence does not exist for data basis &1 ?

  The SAP error message /EACC/MSG_ABSTR_JRNL113 indicates that the source document persistence does not exist for the specified data basis. This error typically arises in the context of the SAP Environment Management or SAP Financial Accounting modules, particularly when dealing with journal entries or document postings.
  Cause:
  
  Missing Source Document: The source document that the system is trying to reference does not exist in the database. This could happen if the document was deleted or if there was an issue during the posting process.
  Data Consistency Issues: There may be inconsistencies in the database, possibly due to incomplete transactions or failed updates.
  Incorrect Configuration: The system may not be properly configured to handle the specific type of document or transaction being processed.
  Authorization Issues: The user may not have the necessary permissions to access the source document.
  
  Solution:
  
  Check Document Existence: Verify if the source document exists in the system. You can do this by checking the relevant tables or using transaction codes like FB03 (Display Document) to see if the document can be retrieved.
  Review Transaction Logs: Look into the transaction logs to identify if there were any errors during the posting process that might have led to the document not being created or saved.
  Data Consistency Check: Run consistency checks on the database to identify and rectify any inconsistencies. This may involve using transaction codes like SE11 to check table entries or using specific SAP tools for data consistency.
  Repost the Document: If the document is missing, you may need to repost the transaction that generated the document to ensure it is created correctly.
  Check Configuration: Review the configuration settings related to document posting and source document handling to ensure they are set up correctly.
  User Authorization: Ensure that the user has the necessary authorizations to access the documents in question.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03, SE11, SE16, and others that can help you investigate the issue further.
  Documentation: Review SAP documentation related to the specific module you are working with (e.g., Financial Accounting, Environment Management) for additional context on document handling and persistence.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.