How To Fix EZ030 - Form class &1 was renamed as &2

SAP Error Message - Details

• Message type: E = Error

• Message class: EZ - Print workbench

• Message number: 030

• Message text: Form class &1 was renamed as &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 EZ030 - Form class &1 was renamed as &2 ?

  The SAP error message EZ030 indicates that a form class has been renamed. This typically occurs in the context of SAPscript or Smart Forms when a form class that is being referenced in your program or configuration has been changed to a new name. 
  Cause:
  
  Renaming of Form Classes: The form class that your program is trying to access has been renamed. This could happen due to changes made by a developer or during a system upgrade.
  Configuration Changes: Changes in the configuration or transport of objects between different SAP systems (like from development to production) may lead to this error if the form class was not properly transported or renamed in all systems.
  
  Solution:
  
  Identify the Renamed Form Class: Check the error message details to identify the old form class name (&1) and the new form class name (&2).
  Update References: Update any references in your programs, configurations, or scripts to use the new form class name. This may involve:
  
  Modifying the code in ABAP programs where the old form class is called.
  Updating configuration settings in transaction codes like SMARTFORMS or SE71 (for SAPscript).
  
  
  Check Transport Requests: If this change was made in a development environment, ensure that the transport request containing the renamed form class has been properly moved to the target environment (e.g., quality or production).
  Testing: After making the necessary changes, test the functionality to ensure that the new form class is being called correctly and that there are no further issues.
  
  Related Information:
  
  Transaction Codes: 
  
  SE71: For SAPscript forms.
  SMARTFORMS: For Smart Forms.
  SE80: Object Navigator, where you can find and manage various objects including forms.
  
  
  Documentation: Review SAP documentation or notes related to form classes and their management for best practices.
  Version Control: If you are using version control for your SAP objects, check the history of changes to understand when and why the renaming occurred.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis or development team for further assistance.