How To Fix >A139 - &1 obsolete administrative data records (reversal runs) were &2

SAP Error Message - Details

• Message type: E = Error

• Message class: >A -

• Message number: 139

• Message text: &1 obsolete administrative data records (reversal runs) were &2

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 >A139 - &1 obsolete administrative data records (reversal runs) were &2 ?

  The SAP error message A139 typically indicates that there are obsolete administrative data records related to reversal runs in the system. This message is often encountered in the context of financial accounting or controlling modules, where reversal documents or transactions are processed.
  Cause:
  The error message A139 is triggered when the system detects that there are outdated or obsolete administrative records associated with reversal runs. This can happen due to various reasons, such as:
  
  Data Inconsistencies: There may be inconsistencies in the database where the administrative records are stored.
  Incomplete Processing: Reversal runs may not have been completed properly, leaving behind obsolete records.
  System Upgrades or Changes: Changes in the system configuration or upgrades may lead to discrepancies in the data.
  Manual Deletions: If records were manually deleted or altered without following the proper procedures, it could lead to this error.
  
  Solution:
  To resolve the A139 error, you can take the following steps:
  
  
  Check for Inconsistencies: Use transaction codes like SE16 or SE11 to check the relevant database tables for inconsistencies. Look for tables related to financial documents and reversal runs.
  
  
  Run Cleanup Programs: SAP provides standard programs to clean up obsolete records. You can run programs like RFSEPA00 or RFSEPA01 to remove obsolete administrative data.
  
  
  Review Reversal Runs: Check the reversal runs that have been processed. Ensure that all necessary steps were completed and that there are no pending or incomplete transactions.
  
  
  Consult SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error. There may be patches or updates that resolve known issues.
  
  
  Contact SAP Support: If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance. Provide them with the error message details and any relevant transaction logs.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to financial document processing, such as FB08 (Reverse Document) and FBRA (Reset Cleared Items).
  Database Tables: Understand the relevant database tables that store administrative data for financial transactions, such as BKPF (Accounting Document Header) and BSEG (Accounting Document Segment).
  Documentation: Review SAP documentation and user guides related to financial accounting and reversal processes for best practices and troubleshooting tips.
  
  By following these steps, you should be able to identify the cause of the A139 error and implement a solution to resolve it.