How To Fix EAMS_SP072 - Call type of maintenance plan not supported

SAP Error Message - Details

• Message type: E = Error

• Message class: EAMS_SP - EAMS: Service Provider Layer

• Message number: 072

• Message text: Call type of maintenance plan not supported

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 EAMS_SP072 - Call type of maintenance plan not supported ?

  The SAP error message EAMS_SP072 indicates that there is an issue with the call type of a maintenance plan that is not supported. This error typically arises in the context of SAP's Plant Maintenance (PM) module when trying to execute or schedule a maintenance plan that has been incorrectly configured.
  Cause:
  
  Incorrect Call Type: The maintenance plan may have been set up with a call type that is not valid or supported in the current context. For example, it might be set to a type that is not applicable for the specific maintenance strategy or scheduling method being used.
  Configuration Issues: There may be configuration issues in the maintenance plan settings or in the overall system settings that prevent the execution of the maintenance plan.
  Missing Data: Required data for the maintenance plan might be missing or incorrectly entered, leading to the system being unable to process the call type.
  Version Compatibility: If there are updates or changes in the SAP version, certain call types may have been deprecated or modified.
  
  Solution:
  
  Check Maintenance Plan Configuration: Review the configuration of the maintenance plan in transaction IP02 (Change Maintenance Plan) or IP01 (Create Maintenance Plan). Ensure that the call type is valid and supported.
  Review Call Type Settings: Verify the settings for the call type in the configuration. You can check the configuration in the following path:
  
  SPRO ? Plant Maintenance and Customer Service ? Maintenance Planning ? Maintenance Plans ? Define Call Types
  
  
  Correct Missing Data: Ensure that all required fields and data are filled out correctly in the maintenance plan. This includes checking the maintenance strategy, scheduling parameters, and any other relevant settings.
  Consult Documentation: Refer to SAP documentation or notes related to the specific version you are using to see if there are any known issues or changes regarding call types.
  Testing: After making changes, test the maintenance plan again to see if the error persists. You can also try creating a new maintenance plan with a different call type to see if it works correctly.
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide insights based on the specific version and configuration of your SAP system.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as IP01, IP02, IP03 (Display Maintenance Plan), and IP10 (Schedule Maintenance Plan).
  SAP Notes: Search for SAP Notes related to EAMS_SP072 for any patches or updates that may address the issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.