How To Fix JBD_FOBJ_ARCH006 - Transaction with OBJNR &1 still has an entry in table RDBRA_REC_HEADER


SAP Error Message - Details

  • Message type: E = Error

  • Message class: JBD_FOBJ_ARCH - Message Class for Object FOBJ_ARCH

  • Message number: 006

  • Message text: Transaction with OBJNR &1 still has an entry in table RDBRA_REC_HEADER

  • 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 JBD_FOBJ_ARCH006 - Transaction with OBJNR &1 still has an entry in table RDBRA_REC_HEADER ?

    The SAP error message JBD_FOBJ_ARCH006 indicates that there is an issue with archiving a business object because the transaction associated with the object number (OBJNR) still has an entry in the table RDBRA_REC_HEADER. This typically occurs during the archiving process when the system detects that there are still references or entries related to the object that need to be addressed before the archiving can proceed.

    Cause:

    1. Existing Entries: The primary cause of this error is that the object number (OBJNR) you are trying to archive has existing entries in the RDBRA_REC_HEADER table. This table is used to store header information for records that are still active and not yet archived.
    2. Incomplete Deletion: There may be related records or dependencies that have not been fully deleted or processed, preventing the archiving of the main object.
    3. Incorrect Archiving Process: The archiving process may not have been followed correctly, or there may be a misconfiguration in the archiving settings.

    Solution:

    To resolve this error, you can follow these steps:

    1. Check for Existing Entries:

      • Use transaction SE16 or SE11 to view the contents of the RDBRA_REC_HEADER table.
      • Search for entries with the specific OBJNR that is causing the error.
    2. Delete or Process Related Entries:

      • If you find entries related to the OBJNR, determine if they can be deleted or if they need to be processed first.
      • Ensure that all related transactions or records are completed or removed.
    3. Check Dependencies:

      • Investigate if there are any dependencies or linked objects that need to be addressed before archiving.
      • Ensure that all related business processes are finalized.
    4. Re-run the Archiving Process:

      • After addressing the entries in the RDBRA_REC_HEADER table, attempt to re-run the archiving process for the object.
    5. Consult Documentation:

      • Review SAP documentation or notes related to archiving for the specific business object you are working with. There may be specific guidelines or prerequisites for archiving.
    6. Contact SAP Support:

      • If the issue persists after following the above steps, consider reaching out to SAP support for further assistance. They may provide additional insights or solutions based on the specific context of your system.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (Archive Administration) and SARI (Archive Information System) for managing archiving processes.
    • Archiving Objects: Understand the specific archiving objects related to your business processes, as each may have unique requirements and configurations.
    • SAP Notes: Search for SAP Notes related to archiving issues, as they may contain patches or updates that address known problems.

    By following these steps, you should be able to resolve the error and successfully archive the business object in question.

    • 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 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