Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix FU826 - Copying of old archive administration data started


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FU - Utilities

  • Message number: 826

  • Message text: Copying of old archive administration data started

  • Show details Hide details
  • What causes this issue?

    The old archive administration data from the F040 transaction is
    transferred to the new archive administration tables for transaction
    SARA. In this process, tables TR01 and RFDT are read and then written
    to the SARA administration tables, ADMI_RUN and ADMI_FILES. The
    administrative entries made in table TR01 are deleted after the
    transfer.

    System Response

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    How to fix this error?


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message FU826 - Copying of old archive administration data started ?

    The SAP error message FU826, which states "Copying of old archive administration data started," typically indicates that there is an issue related to the archiving process in SAP. This message is not necessarily an error but rather an informational message that indicates that the system is attempting to copy old archive administration data.

    Cause:

    1. Archiving Process: The message may appear during the archiving process when the system is trying to access or copy old archive data.
    2. Data Volume: Large volumes of archived data can lead to longer processing times, which may trigger this message.
    3. System Configuration: Incorrect configuration of the archiving settings or parameters may lead to issues during the archiving process.

    Solution:

    1. Monitor the Process: If the message appears, monitor the archiving process to see if it completes successfully. It may take some time depending on the volume of data.
    2. Check Logs: Review the application logs (transaction SLG1) for any additional messages or errors that may provide more context about the archiving process.
    3. Configuration Review: Ensure that the archiving configuration is set up correctly. This includes checking the archiving object settings and ensuring that the necessary authorizations are in place.
    4. Database Performance: If the archiving process is taking too long, consider checking the database performance. Indexing or optimizing the database may help improve performance.
    5. SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific message or provide guidance on archiving issues.

    Related Information:

    • Archiving Objects: Familiarize yourself with the specific archiving objects you are working with, as each object may have its own set of rules and configurations.
    • Transaction Codes: Common transaction codes related to archiving include:
      • SARA: Archive Administration
      • SARI: Archive Information System
      • SARI: Archive Object Management
    • Documentation: Refer to the official SAP documentation for detailed information on archiving processes and best practices.

    If the issue persists or if you encounter additional error messages, it may be beneficial to consult with your SAP Basis team or reach out to 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. Sign up for our Free Essentials Plan.


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 simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant