How To Fix S_ARC_LCM_MES085 - Object key &1 has no origin determined

S_ARC_LCM_MES085 - Overview

• Message type: E = Error

• Message class: S_ARC_LCM_MES - Message Class for Legal Case Management (Subcomponent)

• Message number: 085

• Message text: Object key &1 has no origin determined

What causes this issue?

The origin for this object key cannot be found on the database or in the
archive.

System Response

For every object key of a given object type added in transaction
ILM_LHM, applications search their relevant business data for of this
object key.
If the object key does not exist in the application?s business data, ILM
reports back the status Not Found.

How to fix this error?

Applications must check for the existence of this object key in their
business-relevant data.

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 S_ARC_LCM_MES085 - Object key &1 has no origin determined ?

  The SAP error message S_ARC_LCM_MES085, which states "Object key &1 has no origin determined," typically occurs in the context of SAP Landscape Management (LaMa) or SAP Archiving. This error indicates that the system is unable to determine the origin of a specific object key, which can lead to issues in processing or managing that object.
  
  Cause:
  
  Missing Metadata: The object key may not have the necessary metadata or configuration in the system, which prevents the system from identifying its origin.
  Data Inconsistency: There may be inconsistencies in the database or application data that lead to the inability to resolve the object key.
  
  Configuration Issues: Incorrect configuration settings in the SAP system or in the specific module being used can lead to this error.
  Transport Issues: If the object was transported from one system to another, it may not have been properly configured or may be missing dependencies.
  
  
  Solution:
  
  Check Object Key: Verify the object key mentioned in