How To Fix ARC_DAS_CON120 - Archive store &1 does not conform to ILM_AL (BOR type &2 / doc. type &3)

ARC_DAS_CON120 - Overview

• Message type: E = Error

• Message class: ARC_DAS_CON - XML DAS Connector: Messages

• Message number: 120

• Message text: Archive store &1 does not conform to ILM_AL (BOR type &2 / doc. type &3)

What causes this issue?

The operation was executed 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
the expiration date to lower-level collections and resist deletion
attempts. Thus data which, from the ILM (Information Lifecycle
Management) view, ought to be protected, is at risk of being deleted.

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

System Response

The expiration date was not set in the resource of the processed BOR
type and the document type.

How to fix this error?

Check whether the archive store can obtain the requisite ILM conformity
class through a release upgrade. The storage date can then be set by
restarting the report.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ARC_DAS_CON120 - Archive store &1 does not conform to ILM_AL (BOR type &2 / doc. type &3) ?

  The SAP error message ARC_DAS_CON120 indicates that there is a mismatch or inconsistency between the archive store and the Information Lifecycle Management (ILM) settings. Specifically, it suggests that the archive store does not conform to the expected ILM settings for the specified Business Object Repository (BOR) type and document type.
  
  Cause:
  
  Incompatible Archive Store: The archive store you are trying to access or use does not meet the requirements set by the ILM configuration for the specified BOR type and document type.
  Incorrect Configuration: There may be a misconfiguration in the ILM settings or the archive object settings that leads to this inconsistency.
  Data Migration Issues: If data has been migrated from another system or if there have been changes in the archive settings, this could lead to discrepancies.
  Version Mismatch: The version of the archive store may not be compatible with the current ILM settings or the SAP system version.
  
  
  Solution:
  
  Check Archive Store Configuration: Verify