Do you have any question about this error?
Message type: E = Error
Message class: LRM - Customizing
Message number: 035
Message text: ILM object with business key &1 cannot be deleted
The available start time &V1& can only be deleted only if no further
dependencies exist. There are, however, still dependent <ZK>available
time offsets</>.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
First delete the dependent <ZK>available time offsets</>.
Error message extract from SAP system. Copyright SAP SE.
LRM035
- ILM object with business key &1 cannot be deleted ?The SAP error message LRM035 indicates that an Information Lifecycle Management (ILM) object with a specific business key cannot be deleted. This error typically arises in the context of data archiving and ILM processes, where certain objects are protected from deletion due to various reasons.
Causes of the Error LRM035
- Object Locking: The ILM object may be locked due to ongoing processes or transactions that are still referencing it.
- Retention Period: The object may be within a defined retention period, meaning it cannot be deleted until that period has expired.
- Dependencies: There may be dependencies or relationships with other objects that prevent deletion.
- Authorization Issues: The user may not have the necessary authorizations to delete the ILM object.
- Status of the Object: The object may be in a status that does not allow deletion (e.g., archived but not yet eligible for deletion).
Solutions to the Error LRM035
- Check Object Status: Verify the status of the ILM object. If it is still within the retention period, you will need to wait until it is eligible for deletion.
- Release Locks: Ensure that there are no active processes or transactions that are locking the object. You may need to check for any ongoing jobs or transactions that reference the object.
- Review Dependencies: Investigate if there are any dependencies with other objects. If so, you may need to address those dependencies before attempting to delete the object.
- Authorization Check: Ensure that the user attempting to delete the object has the necessary authorizations. You may need to consult with your SAP security team to verify this.
- Consult ILM Configuration: Review the ILM configuration settings to ensure that the object is configured correctly for deletion.
- Use ILM Tools: Utilize SAP ILM tools or transaction codes (like ILM_OBJECTS) to get more information about the object and its status.
Related Information
If the issue persists after trying the above solutions, it may be beneficial to consult with SAP support or your internal SAP team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
LRM034
Assigned audit area "&1" cannot be deleted
What causes this issue? This allowed audit area can only be deleted if no further dependencies exist. There are, however, still dependent <ZK>P...
LRM033
ILM object type &1 already active for audit area &2
What causes this issue? The GENERAL audit area is a general audit area with special runtime logic. Within an <ZK>available policy category</...
LRM040
Object with business key "&1" cannot be accessed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
LRM051
Constant type &1 not allowed
What causes this issue? Only the fixed values of domain LRM_CONSTANT_TYPE are allowed.System Response The system issues an error message and will no...
Click on this link to search all SAP messages.