Do you have any question about this error?
Message type: E = Error
Message class: LRM_BS - IRM - Business Suite
Message number: 073
Message text: Fig. ILM obj.->BOR obj.ty. for destruct. of attachment &1 already exists
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
LRM_BS073
- Fig. ILM obj.->BOR obj.ty. for destruct. of attachment &1 already exists ?The SAP error message LRM_BS073 typically indicates that there is an issue related to the Information Lifecycle Management (ILM) object, specifically when trying to delete or manage attachments. The message suggests that there is already an existing object type for the destruction of the specified attachment.
Cause:
The error can occur due to several reasons:
- Duplicate Entries: There may be an attempt to create a destruction object for an attachment that already has an existing destruction object.
- Configuration Issues: The configuration settings for ILM or the specific object type may not be set up correctly.
- Data Integrity Issues: There may be inconsistencies in the data that are causing the system to believe that the object already exists.
Solution:
To resolve the error, you can take the following steps:
Check Existing Objects:
- Use transaction codes like SARA or ILM to check if a destruction object for the attachment already exists. If it does, you may need to manage or delete that object before proceeding.
Review Configuration:
- Ensure that the ILM configuration is set up correctly for the object type in question. This includes checking the settings for the retention periods and destruction processes.
Data Cleanup:
- If there are duplicate entries or inconsistencies, you may need to clean up the data. This could involve deleting unnecessary or duplicate destruction objects.
Consult Documentation:
- Refer to SAP documentation or notes related to ILM and the specific object type to ensure that you are following the correct procedures.
SAP Support:
- If the issue persists, consider reaching out to SAP support for assistance. They may provide specific notes or patches that address the issue.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
LRM_BS072
Fig. ILM obj.->BOR obj.ty. for destruct. of attachment &1 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
LRM_BS071
Attachment: Fig. &1 ILM obj. -> BOR ob.ty. cannot be deleted
What causes this issue? The mapping of the ILM object to the BOR object type for the destruction of attachment &V1& cannot be deleted.System ...
LRM_BS081
Data for value determination for time offset &1 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
LRM_BS082
Data for value determination of time offset &1 already exists
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.