Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
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
The origin for this object key cannot be found on the database or in the
archive.
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.
Applications must check for the existence of this object key in their
business-relevant data.
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.
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 the error message. Ensure that it is correctly defined and exists in the system.
- Review Metadata: Check the metadata associated with the object key. Ensure that all necessary information is present and correctly configured.
- Consistency Check: Perform a consistency check on the relevant database tables or application data to identify any discrepancies.
- Configuration Review: Review the configuration settings related to the object in question. Ensure that all necessary settings are correctly defined.
- Transport Logs: If the object was recently transported, check the transport logs for any errors or warnings that may indicate issues during the transport process.
- SAP Notes: Search for relevant SAP Notes or Knowledge Base Articles (KBAs) that may address this specific error. SAP frequently updates its documentation and may have provided specific guidance for this issue.
- Contact SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. Provide them with the error message, object key, and any relevant logs or screenshots.
Related Information:
By following these steps, you should be able to diagnose and resolve the error message S_ARC_LCM_MES085 in your SAP system.
Get instant SAP help. Sign up for our Free Essentials Plan.
S_ARC_LCM_MES084
Error while scheduling E-Discovery in background.
What causes this issue? An error occurred while trying to schedule a background job for e-discovery.System Response The system issues an error messa...
S_ARC_LCM_MES083
Updation into &1 failed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
S_ARC_TRANS001
Job could not be scheduled for &2
What causes this issue? A job could not be released for &V2&. The job name used is &V1&. The last return code (in parentheses) and th...
S_ARC_TRANS002
Job could not be released for &4
What causes this issue? A job could not be released for &V4&. The job name used is &V1&. The ID number for this job is &V2&. ...
Click on this link to search all SAP messages.