How To Fix EDX_SIS_MC035 - Package ZIATA doesn't exists

SAP Error Message - Details

• Message type: E = Error

• Message class: EDX_SIS_MC - EDX_SIS: Message class

• Message number: 035

• Message text: Package ZIATA doesn't exists

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 EDX_SIS_MC035 - Package ZIATA doesn't exists ?

  The SAP error message EDX_SIS_MC035 indicating that "Package ZIATA doesn't exist" typically arises in the context of SAP's transport management system or when dealing with custom developments. Here’s a breakdown of the potential causes, solutions, and related information:
  Cause:
  
  Non-Existent Package: The package ZIATA may not exist in the SAP system. This could be due to it not being created, or it may have been deleted or not transported correctly.
  Transport Issues: If the package was supposed to be transported from another system (like Development to Quality or Production), there may have been an issue during the transport process.
  Authorization Issues: The user may not have the necessary authorizations to access the package or the objects within it.
  Incorrect Configuration: The system might be incorrectly configured to look for a package that is not relevant or has been misnamed.
  
  Solution:
  
  
  Check Package Existence:
  
  Go to transaction SE80 (Object Navigator) or SE21 (Package Builder) and check if the package ZIATA exists.
  If it does not exist, you may need to create it or check with your development team to see if it was supposed to be created.
  
  
  
  Transport Management:
  
  If the package is supposed to exist but does not, check the transport logs to see if there were any errors during the transport process.
  Ensure that the transport requests containing the package were released and imported correctly.
  
  
  
  Authorization Check:
  
  Verify that the user encountering the error has the necessary authorizations to access the package. This can be done by checking the user roles and authorizations in transaction SU01.
  
  
  
  Correct Configuration:
  
  If the package name is being referenced incorrectly in custom code or configuration, correct the references to point to the correct package.
  
  
  
  Consult Documentation:
  
  If the package is part of a third-party solution or an SAP add-on, consult the relevant documentation or support channels for guidance on how to resolve the issue.
  
  
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide additional troubleshooting steps.
  Community Forums: SAP Community and other forums can be useful for finding similar issues faced by other users and the solutions they found.
  Development Team: If you are not the developer, it may be beneficial to involve your development team to investigate the issue further, especially if it relates to custom code or packages.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution. If the issue persists, consider reaching out to SAP support for further assistance.