How To Fix S_ARC_DESTRUCTION085 - Could not find the BOR key for resource &1&2&3&4

SAP Error Message - Details

• Message type: E = Error

• Message class: S_ARC_DESTRUCTION - ILM: Data Destruction Message Class

• Message number: 085

• Message text: Could not find the BOR key for resource &1&2&3&4

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 S_ARC_DESTRUCTION085 - Could not find the BOR key for resource &1&2&3&4 ?

  The SAP error message S_ARC_DESTRUCTION085 indicates that the system could not find the Business Object Repository (BOR) key for a specified resource. This error typically occurs in the context of SAP Archive Management or when dealing with archived data.
  Cause:
  The error can be caused by several factors, including:
  
  
  Missing or Incorrect BOR Key: The BOR key for the specified resource (indicated by placeholders &1, &2, &3, &4) may not exist in the system. This could happen if the object was not properly defined or registered in the BOR.
  
  
  Data Inconsistency: There may be inconsistencies in the data, such as missing entries in the relevant tables that link the archived data to the BOR.
  
  
  Configuration Issues: The configuration settings for the archiving object may not be set up correctly, leading to issues in retrieving the BOR key.
  
  
  Transport Issues: If the archiving object or related configurations were transported from one system to another, there may be missing dependencies or incomplete transport.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check BOR Configuration:
  
  Use transaction SWO1 to check the Business Object Repository and ensure that the object type corresponding to the resource is correctly defined.
  Verify that the BOR key exists for the specified resource.
  
  
  
  Review Archiving Object Settings:
  
  Go to transaction SARA and check the settings for the archiving object related to the error. Ensure that all necessary configurations are in place.
  
  
  
  Data Consistency Check:
  
  Perform a consistency check on the archived data. You can use transaction SARA to check for inconsistencies in the archiving object.
  
  
  
  Check Transport Logs:
  
  If the issue arose after a transport, review the transport logs to ensure that all necessary objects were transported correctly.
  
  
  
  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 logs.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SARA: Archive Administration
  SWO1: Business Object Builder
  
  
  Documentation: Review SAP documentation related to Archive Management and Business Object Repository for more detailed information on configuration and troubleshooting.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution.