How To Fix EAM_LACD_MSGS002 - No customization maintained for Priority Type &1 and Priority &2

SAP Error Message - Details

• Message type: E = Error

• Message class: EAM_LACD_MSGS - Message class for Enterprise Asset Managament LACD

• Message number: 002

• Message text: No customization maintained for Priority Type &1 and Priority &2

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 EAM_LACD_MSGS002 - No customization maintained for Priority Type &1 and Priority &2 ?

  The SAP error message EAM_LACD_MSGS002 indicates that there is no customization maintained for a specific priority type and priority in the Enterprise Asset Management (EAM) module. This error typically arises when the system is trying to process a task or transaction that requires a defined priority but cannot find the necessary configuration.
  Cause:
  
  Missing Customization: The primary cause of this error is that the priority type and priority combination has not been defined in the system. This can happen if the configuration settings for the EAM module have not been properly set up.
  Incorrect Priority Assignment: The priority type or priority being used in the transaction may not exist in the system, leading to this error.
  Transport Issues: If the configuration was recently transported from another system, it may not have included the necessary priority settings.
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Customization Settings:
  
  Go to the SAP Easy Access screen and navigate to the following path:
  SPRO -> SAP Reference IMG -> Plant Maintenance and Customer Service -> Maintenance and Service Processing -> Maintenance Processing -> Define Priority Types
  
  Ensure that the priority type and the specific priority you are trying to use are defined in the system.
  
  
  
  Create or Modify Priority:
  
  If the priority type or priority does not exist, you will need to create it. You can do this in the same configuration area mentioned above.
  If it exists but is not correctly configured, modify it to ensure it meets your requirements.
  
  
  
  Check for Transport Issues:
  
  If the configuration was recently transported, verify that all necessary objects were included in the transport request. You may need to re-transport the missing configurations.
  
  
  
  Testing:
  
  After making the necessary changes, test the transaction again to ensure that the error no longer occurs.
  
  
  
  Consult Documentation:
  
  If you are unsure about the correct settings, refer to SAP documentation or consult with your SAP Basis or EAM functional team for guidance.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like SPRO for configuration and SE11 for checking table entries related to priorities.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance on configuring priority types.
  User Roles: Ensure that you have the necessary authorizations to make changes to the configuration settings.
  
  By following these steps, you should be able to resolve the error message EAM_LACD_MSGS002 and ensure that the necessary customization for priority types and priorities is maintained in your SAP system.