How To Fix /PLMI/ECR_BO089 - No record type is customized

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMI/ECR_BO -

• Message number: 089

• Message text: No record type is customized

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 /PLMI/ECR_BO089 - No record type is customized ?

  The SAP error message /PLMI/ECR_BO089 No record type is customized typically occurs in the context of the SAP PLM (Product Lifecycle Management) module, particularly when dealing with Engineering Change Requests (ECRs) or Engineering Change Orders (ECOs). This error indicates that the system cannot find a customized record type for the operation you are trying to perform.
  Cause:
  
  Missing Customization: The most common cause of this error is that the required record type has not been defined or customized in the system. This could be due to a lack of configuration in the relevant customizing settings.
  Incorrect Configuration: There may be an issue with the configuration settings in the system, such as missing entries in the customizing tables.
  Transport Issues: If the configuration was recently transported from another system, it may not have been transported correctly, leading to missing entries.
  
  Solution:
  
  
  Check Customizing Settings:
  
  Go to the SPRO transaction (SAP Reference IMG).
  Navigate to the relevant section for PLM and check the settings for record types under Engineering Change Management.
  Ensure that the necessary record types are defined and properly configured.
  
  
  
  Define Record Types:
  
  If the required record type is missing, you may need to create it. This can typically be done in the customizing settings where you define record types for ECRs or ECOs.
  Make sure to assign the appropriate attributes and settings to the new record type.
  
  
  
  Review Transport Requests:
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included and successfully imported.
  If something is missing, you may need to re-transport the relevant customizing settings.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific version of PLM you are using. There may be specific instructions or known issues related to record types.
  
  
  
  Contact SAP Support:
  
  If you are unable to resolve the issue through the above steps, consider reaching out to SAP support for assistance. They may provide additional insights or solutions based on your specific system configuration.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO, SE11 (Data Dictionary), and SE80 (Object Navigator) for checking and modifying configurations.
  SAP Notes: Search for SAP Notes related to the error message or the specific functionality you are working with. SAP Notes often contain fixes or workarounds for known issues.
  User Forums: Consider checking SAP community forums or other user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.