How To Fix LRM_BS035 - Data for determining inheriting instances &1 not created

SAP Error Message - Details

• Message type: E = Error

• Message class: LRM_BS - IRM - Business Suite

• Message number: 035

• Message text: Data for determining inheriting instances &1 not created

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_BS035 - Data for determining inheriting instances &1 not created ?

  The SAP error message LRM_BS035 indicates that the system was unable to create the necessary data for determining inheriting instances for a specific object or instance. This error typically arises in the context of SAP's Logistics or Material Management modules, particularly when dealing with master data or configuration settings.
  Cause:
  The error can be caused by several factors, including:
  
  
  Missing Configuration: The necessary configuration for the object in question may not be set up correctly. This could involve missing entries in customizing tables or incorrect settings in the relevant transaction codes.
  
  
  Data Inconsistencies: There may be inconsistencies or missing data in the master data records that are required for the system to determine inheriting instances.
  
  
  Authorization Issues: The user may not have the necessary authorizations to access or create the required data.
  
  
  Technical Issues: There could be underlying technical issues, such as problems with the database or application server.
  
  
  Incorrect Object Type: The object type being processed may not be valid for the operation being performed.
  
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration: Review the configuration settings related to the object in question. Ensure that all necessary entries are made in the relevant customizing tables.
  
  
  Validate Master Data: Check the master data records for completeness and correctness. Ensure that all required fields are filled out and that there are no inconsistencies.
  
  
  Review Authorizations: Ensure that the user has the necessary authorizations to perform the operation. You may need to consult with your SAP security team.
  
  
  Check Logs: Look at the application logs (transaction SLG1) for more detailed error messages that may provide additional context about the issue.
  
  
  Debugging: If you have access to debugging tools, you can analyze the program logic to identify where the error is occurring.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific module or transaction you are working with. There may be known issues or additional guidance available.
  
  
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP support for assistance. Provide them with the error message and any relevant details about the context in which it occurred.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in troubleshooting, such as SE11 (Data Dictionary), SE80 (Object Navigator), or SLG1 (Application Log).
  SAP Notes: Search for SAP Notes related to the error message or the specific module you are working with. SAP Notes often contain patches or workarounds for known issues.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution.