How To Fix EZ358 - DDIC structure or table &1 do not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: EZ - Print workbench

• Message number: 358

• Message text: DDIC structure or table &1 do not exist

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 EZ358 - DDIC structure or table &1 do not exist ?

  The SAP error message EZ358 indicates that the Data Dictionary (DDIC) structure or table specified by &1 does not exist in the system. This error can occur in various scenarios, such as when trying to access a table or structure that has not been created, has been deleted, or is not available in the current client.
  Causes:
  
  Non-existent Table/Structure: The specified table or structure has not been created in the SAP system.
  Incorrect Name: There may be a typo or incorrect naming in the table or structure reference.
  Transport Issues: The table or structure may exist in a different system (e.g., development) but has not been transported to the current system (e.g., production).
  Client-Specific Data: The table or structure may exist in another client but not in the current client you are working in.
  Authorization Issues: The user may not have the necessary authorizations to access the table or structure.
  
  Solutions:
  
  Check Existence: Verify if the table or structure exists in the Data Dictionary (transaction SE11). If it does not exist, you may need to create it or check with your development team.
  Correct Naming: Ensure that the name of the table or structure is spelled correctly in your code or configuration.
  Transport Check: If the table or structure exists in another system, ensure that the transport request containing the definition has been moved to the current system.
  Client Check: Make sure you are in the correct client. You can switch clients and check if the table or structure exists in another client.
  Authorization Check: Verify that you have the necessary authorizations to access the table or structure. You may need to contact your security team for assistance.
  Rebuild or Restore: If the table or structure was deleted accidentally, you may need to restore it from a backup or recreate it based on the specifications.
  
  Related Information:
  
  Transaction Codes: 
  
  SE11: Data Dictionary (to check tables/structures)
  SE80: Object Navigator (to check for related objects)
  SE03: Transport Organizer (to check transport requests)
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific table or structure.
  Documentation: Review the documentation for the specific module or functionality you are working with to ensure that the table or structure is part of the expected configuration.
  
  If the issue persists after checking the above points, it may be helpful to consult with your SAP Basis or development team for further investigation.