How To Fix FDT_CHANGE_INFO537 - Created a new procedure call for database procedure &1

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 537

• Message text: Created a new procedure call for database procedure &1

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_INFO537 - Created a new procedure call for database procedure &1 ?

  The SAP error message FDT_CHANGE_INFO537 typically indicates that there has been a change in the database procedure that is being referenced in your SAP system. This error is often related to the use of the SAP Fiori Data Transformation (FDT) framework, which is used for data manipulation and transformation tasks.
  Cause:
  The error message FDT_CHANGE_INFO537 is triggered when:
  
  A new procedure call has been created for a database procedure that was previously defined.
  There may have been changes in the underlying database structure or the procedure itself, which could include modifications to the procedure's parameters, return types, or the logic within the procedure.
  The system is unable to reconcile the changes made to the database procedure with the existing references in the SAP application.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Database Procedure: 
  
  Review the database procedure that is causing the issue. Ensure that it is correctly defined and that any changes made to it are valid.
  Verify the parameters and return types of the procedure to ensure they match what is expected in the SAP application.
  
  
  
  Update References:
  
  If the procedure has been modified, you may need to update any references to it in your SAP application. This could involve updating function modules, programs, or other objects that call this procedure.
  
  
  
  Rebuild or Refresh:
  
  If applicable, rebuild or refresh the data model or transformation logic that relies on the database procedure. This may involve regenerating the relevant objects in the SAP system.
  
  
  
  Check for Dependencies:
  
  Investigate if there are any dependencies or related objects that might also need to be updated due to the changes in the database procedure.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the FDT framework and the specific database procedures you are using. There may be specific guidelines or best practices for handling changes.
  
  
  
  Testing:
  
  After making the necessary changes, thoroughly test the application to ensure that the error has been resolved and that the application behaves as expected.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance on handling changes to database procedures.
  FDT Framework Documentation: Familiarize yourself with the FDT framework and its components, as understanding how it interacts with database procedures can help in troubleshooting.
  Database Logs: Review database logs for any additional error messages or warnings that might provide more context about the issue.
  
  If the problem persists after following these steps, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the context in which it occurs.