How To Fix FDT_CHANGE_INFO158 - Class of the static method call was changed from &1 to &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_CHANGE_INFO - FDT: Changes info in object for different versions

• Message number: 158

• Message text: Class of the static method call was changed from &1 to &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 FDT_CHANGE_INFO158 - Class of the static method call was changed from &1 to &2 ?

  The SAP error message FDT_CHANGE_INFO158 indicates that there has been a change in the class of a static method call in your ABAP code. Specifically, it states that the class of the static method call has been changed from one class (&1) to another class (&2). This typically occurs when there are changes in the class definitions or when the method is moved to a different class.
  Cause:
  
  Class Modification: The class that originally contained the static method has been modified, possibly due to a transport request or changes made by another developer.
  Refactoring: The method may have been refactored or moved to a different class, which can happen during code optimization or restructuring.
  Versioning Issues: If you are working in a system with multiple versions or clients, the method may exist in different classes across those versions.
  
  Solution:
  
  Check Class Definitions: Review the class definitions for both classes (&1 and &2) to understand the changes made. You can do this by navigating to the class in the ABAP Workbench (SE80 or SE24).
  Update Method Calls: If the method has been moved to a new class, update your code to call the method from the new class. Ensure that you are using the correct class name in your static method calls.
  Check Transport Requests: If the change was made in a different system, ensure that the relevant transport requests have been imported correctly into your system.
  Consult Documentation: If available, check any documentation or change logs that might explain why the class was changed. This can provide context for the modification.
  Testing: After making the necessary changes, thoroughly test the affected functionality