How To Fix ARC_DAS_CON123 - Legal hold &1 f. BOR type &2 and obj. &3 not supported by arc. store &4

SAP Error Message - Details

• Message type: E = Error

• Message class: ARC_DAS_CON - XML DAS Connector: Messages

• Message number: 123

• Message text: Legal hold &1 f. BOR type &2 and obj. &3 not supported by arc. store &4

What causes this issue?

The legal hold is to be propagated for a collection or resource to which
an archive store is assigned which does not fulfill all functional
requirements. Specifically, the archive store is not able to propagate a
legal hold on lower-level collections and resist deletion attempts. Thus
data which, from the LEGAL HOLD Management viewpoint, ought to be
protected, is at risk of being deleted.

System Response

The operation is not performed for the BOR type and the document in this
archive store.

How to fix this error?

Check whether the archive store can obtain the requisite ILM conformity
class through a release upgrade.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ARC_DAS_CON123 - Legal hold &1 f. BOR type &2 and obj. &3 not supported by arc. store &4 ?

  The SAP error message ARC_DAS_CON123 indicates that there is an issue related to legal holds in the Archive Data Store (ARC) system. This error typically arises when a specific business object (BOR type) is not supported by the archive store you are trying to use. Here’s a breakdown of the components of the error message:
  
  Legal hold: This refers to a legal requirement to preserve certain data for compliance or litigation purposes.
  BOR type: This stands for Business Object Repository type, which is a classification of business objects in SAP.
  Obj.: This refers to the specific object that is being referenced in the error.
  Arc. store: This refers to the archive store that is being used to store the data.
  
  Cause
  The error is typically caused by one of the following:
  
  Unsupported Object Type: The specific BOR type and object you are trying to archive or apply a legal hold to is not supported by the configured archive store.
  Configuration Issues: There may be a misconfiguration in the archive settings or the archive object definitions.
  Missing Archive Object: The archive object for the specified BOR type may not be defined in the system.
  
  Solution
  To resolve this error, you can take the following steps:
  
  
  Check Archive Object Configuration:
  
  Verify that the archive object for the specified BOR type is correctly configured in the SAP system.
  Ensure that the archive object is active and properly set up to handle legal holds.
  
  
  
  Review Supported BOR Types:
  
  Consult the documentation or configuration settings to determine which BOR types are supported by the archive store you are using.
  If the BOR type is not supported, you may need to consider using a different archive store that supports the required BOR type.
  
  
  
  Update Archive Store Settings:
  
  If necessary, update the settings of the archive store to include support for the required BOR type and object.
  This may involve working with your SAP Basis or Archive Administration team to make the necessary changes.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes or updates that may address this specific error message or provide additional guidance on legal holds and archive configurations.
  
  
  
  Testing:
  
  After making any changes, perform tests to ensure that the legal hold can be applied successfully without triggering the error.
  
  
  
  Related Information
  
  SAP Documentation: Review the official SAP documentation related to archiving and legal holds for more detailed information on configuration and supported objects.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance, providing them with the error message and context for further troubleshooting.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.