How To Fix /SMB/DEFINITION058 - Fields have been removed from table, definition is updated

SAP Error Message - Details

• Message type: E = Error

• Message class: /SMB/DEFINITION -

• Message number: 058

• Message text: Fields have been removed from table, definition is updated

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 /SMB/DEFINITION058 - Fields have been removed from table, definition is updated ?

  The SAP error message /SMB/DEFINITION058 Fields have been removed from table, definition is updated typically indicates that there has been a change in the structure of a database table in the SAP system. This can occur during updates or modifications to the system, such as when a new version of a software component is installed or when a custom development is made.
  Cause:
  
  
  Table Structure Change: The error suggests that certain fields have been removed from a table, which means that the table definition has been updated. This could be due to:
  
  A software upgrade or patch that modifies the database schema.
  Custom development that alters the table structure.
  Data model changes in the underlying application.
  
  
  
  Inconsistency: The error may also arise if there are inconsistencies between the application layer and the database layer, especially if the application is trying to access fields that no longer exist in the database.
  
  
  Solution:
  
  
  Check Table Definition: Verify the current structure of the table in question. You can do this using transaction codes like SE11 (Data Dictionary) to see the current fields and their definitions.
  
  
  Adjust Custom Code: If you have custom code (ABAP programs, reports, etc.) that references the removed fields, you will need to update this code to remove references to those fields or to handle the changes appropriately.
  
  
  Re-activate Objects: If the error is related to a specific object (like a report or a function module), try re-activating the object in the ABAP Workbench (SE80) to ensure it is in sync with the current database structure.
  
  
  Transport Requests: If the changes were made in a development environment, ensure that the relevant transport requests are moved to the quality and production environments to maintain consistency.
  
  
  Consult Documentation: Review any release notes or documentation related to the software update or changes that were made to understand the implications of the changes.
  
  
  Database Consistency Check: Run consistency checks on the database to ensure that there are no other discrepancies that could lead to similar issues.
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific version of the software you are using. SAP Notes can provide guidance on how to resolve specific errors.
  Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance. They can provide insights based on the specific version and configuration of your SAP system.
  Backup: Always ensure that you have a backup of your data and custom developments before making significant changes to the system.
  
  By following these steps, you should be able to address the error message and ensure that your SAP system is functioning correctly.