How To Fix FARR_CONTRACT_DB058 - Error while saving reconciliation history to database


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FARR_CONTRACT_DB - Revenue Accounting - Contract DB Access

  • Message number: 058

  • Message text: Error while saving reconciliation history to database

  • Show details Hide details


  • 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 FARR_CONTRACT_DB058 - Error while saving reconciliation history to database ?

    The SAP error message FARR_CONTRACT_DB058 typically occurs in the context of the Asset Accounting (FI-AA) module, particularly when there are issues related to saving reconciliation history data to the database. This error can arise due to various reasons, including data inconsistencies, database issues, or configuration problems.

    Causes:

    1. Data Inconsistencies: There may be inconsistencies in the data being processed, such as missing or incorrect entries in the reconciliation history.
    2. Database Locking Issues: The database table may be locked by another process, preventing the current transaction from saving data.
    3. Configuration Issues: Incorrect configuration settings in the Asset Accounting module can lead to errors when trying to save data.
    4. Authorization Issues: The user may not have the necessary authorizations to perform the action, leading to a failure in saving the data.
    5. Database Errors: There could be underlying database issues, such as corruption or connectivity problems.

    Solutions:

    1. Check Data Consistency: Review the data being processed for any inconsistencies or missing entries. Ensure that all required fields are filled correctly.
    2. Database Lock Check: Use transaction codes like SM12 to check for any locks on the relevant database tables. If locks are found, you may need to wait for the other processes to complete or resolve the locks.
    3. Review Configuration: Verify the configuration settings in the Asset Accounting module to ensure they are set up correctly. This may involve checking the settings for reconciliation accounts and asset classes.
    4. Authorization Check: Ensure that the user has the necessary authorizations to perform the action. You can check this using transaction SU53 to see if there are any authorization failures.
    5. Database Health Check: If the issue persists, perform a health check on the database. This may involve checking for corruption or connectivity issues. You may need to involve your database administrator for this.
    6. SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve the issue.
    7. Debugging: If you have access to debugging tools, you can analyze the program flow to identify where the error occurs and gather more information about the root cause.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as SE80 (Object Navigator), SE37 (Function Module), and SE11 (Data Dictionary) for further investigation.
    • SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
    • Documentation: Review SAP documentation related to Asset Accounting and reconciliation processes for additional insights.

    If the problem persists after trying the above solutions, it may be necessary to contact SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker