How To Fix LRM_BS036 - Data for determining BOR key &1 not created

SAP Error Message - Details

• Message type: E = Error

• Message class: LRM_BS - IRM - Business Suite

• Message number: 036

• Message text: Data for determining BOR key &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_BS036 - Data for determining BOR key &1 not created ?

  The SAP error message LRM_BS036 indicates that the system was unable to create the necessary data for determining the BOR (Business Object Repository) key for a specific object. This typically occurs in the context of Business Object processing, where the system expects certain data to be available but cannot find it.
  Cause:
  The error can be caused by several factors, including:
  
  Missing Configuration: The necessary configuration for the Business Object may not be set up correctly in the system.
  Data Inconsistencies: There may be inconsistencies or missing entries in the underlying data that the BOR key relies on.
  Authorization Issues: The user may not have the necessary authorizations to access the data required for the BOR key determination.
  System Bugs: There could be bugs or issues in the specific version of SAP you are using that affect the creation of BOR keys.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration: Ensure that the configuration for the Business Object is complete and correct. This may involve checking transaction codes related to the specific Business Object you are working with.
  
  
  Data Validation: Verify that all necessary data entries exist and are consistent. This may involve checking related tables or entries in the SAP system.
  
  
  Authorization Check: Ensure that the user has the necessary authorizations to access the data. You can check this using transaction SU53 to see if there are any authorization issues.
  
  
  Debugging: If you have access to debugging tools, you can try to debug the process to see where it fails. This may provide more insight into what data is missing or what configuration is incorrect.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that resolve known issues.
  
  
  Consult Documentation: Review the official SAP documentation for the Business Object you are working with to ensure that all prerequisites and configurations are met.
  
  
  Contact SAP Support: If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE80 (Object Navigator), SE11 (Data Dictionary), and SE37 (Function Module) to investigate the underlying objects and data.
  Business Object Repository: Understanding how the BOR works and its dependencies can help in troubleshooting issues related to BOR keys.
  SAP Community: Engaging with the SAP Community forums can provide insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution.