How To Fix ARC_DAS_CON113 - Legal hold &1 could not be propagated to BOR type &2 for report &3

SAP Error Message - Details

• Message type: E = Error

• Message class: ARC_DAS_CON - XML DAS Connector: Messages

• Message number: 113

• Message text: Legal hold &1 could not be propagated to BOR type &2 for report &3

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 ARC_DAS_CON113 - Legal hold &1 could not be propagated to BOR type &2 for report &3 ?

  The SAP error message ARC_DAS_CON113 indicates an issue related to legal holds in the context of the SAP Archive Management system. This error typically arises when there is a failure to propagate a legal hold to a Business Object Repository (BOR) type for a specific report. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Legal Hold Configuration: The legal hold may not be properly configured for the specified BOR type. This could be due to missing or incorrect settings in the legal hold configuration.
  Data Consistency Issues: There may be inconsistencies in the data that prevent the legal hold from being applied correctly.
  Authorization Issues: The user executing the operation may not have the necessary authorizations to apply the legal hold to the specified BOR type.
  System Errors: There could be underlying system errors or bugs that are causing the failure in propagation.
  
  
  Solution:
  
  
  Check Legal Hold Configuration:
  
  Verify that the legal hold is