How To Fix LRM_BS072 - Fig. ILM obj.->BOR obj.ty. for destruct. of attachment &1 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: LRM_BS - IRM - Business Suite

• Message number: 072

• Message text: 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 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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message LRM_BS072 - Fig. ILM obj.->BOR obj.ty. for destruct. of attachment &1 does not exist ?

  The SAP error message LRM_BS072 indicates that there is an issue related to the Information Lifecycle Management (ILM) object and its associated Business Object Repository (BOR) object type when attempting to destruct an attachment. Specifically, the error message states that the specified BOR object type for the destruction of the attachment does not exist.
  Cause:
  
  Missing BOR Object Type: The primary cause of this error is that the system is trying to reference a BOR object type that has not been defined or does not exist in the system.
  Configuration Issues: There may be configuration issues in the ILM settings or the BOR settings that lead to this inconsistency.
  Data Integrity Issues: If the data related to the attachment or its lifecycle management has been corrupted or improperly configured, it can lead to this error.
  
  Solution:
  
  
  Check BOR Object Type:
  
  Verify that the BOR object type referenced in the error message exists in the system. You can do this by using transaction SWO1 (Business Object Builder) to check if the object type is defined.
  If it does not exist, you may need to create it or correct the reference in the ILM configuration.
  
  
  
  Review ILM Configuration:
  
  Go to the ILM configuration settings and ensure that the object types and their relationships are correctly defined.
  Use transaction SARA to access ILM settings and check the configuration for the specific ILM object.
  
  
  
  Check Attachment Settings:
  
  Ensure that the attachment settings are correctly configured and that the attachments are properly linked to the relevant ILM objects.
  
  
  
  Consult Documentation:
  
  Review SAP documentation related to ILM and BOR to ensure that you are following the correct procedures for managing attachments and their lifecycle.
  
  
  
  SAP Notes and Support:
  
  Check for any relevant SAP Notes that may address this specific error. You can search the SAP Support Portal for notes related to ILM and BOR issues.
  If the problem persists, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  ILM (Information Lifecycle Management): A framework in SAP that helps manage the lifecycle of data, including retention and destruction policies.
  BOR (Business Object Repository): A repository in SAP that defines business objects and their methods, events, and attributes.
  Transaction Codes:
  
  SWO1: Business Object Builder
  SARA: Archive Administration
  
  
  SAP Notes: Regularly check for updates or patches that may resolve known issues related to ILM and BOR.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.