How To Fix SDEST058 - basXML conversion requires transaction SM59 in dialog

SAP Error Message - Details

• Message type: E = Error

• Message class: SDEST - Messages for RFC Destinations

• Message number: 058

• Message text: basXML conversion requires transaction SM59 in dialog

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 SDEST058 - basXML conversion requires transaction SM59 in dialog ?

  The SAP error message SDEST058 indicates that there is an issue with the conversion of a BAS XML (Business Application Services XML) document, specifically that it requires a configuration in transaction SM59. This error typically arises when the system is trying to perform a remote function call (RFC) and the necessary settings for the RFC destination are not properly configured.
  Cause:
  
  Missing RFC Destination: The error often occurs when the RFC destination required for the BAS XML conversion is not defined in transaction SM59.
  Incorrect Configuration: The RFC destination may exist but could be incorrectly configured, leading to communication issues.
  Network Issues: There may be network connectivity issues preventing the SAP system from reaching the specified RFC destination.
  Authorization Issues: The user may not have the necessary authorizations to access the RFC destination.
  
  Solution:
  
  
  Check RFC Destination:
  
  Go to transaction SM59.
  Check if the required RFC destination is defined. If it is not, you will need to create it.
  If it exists, verify that the configuration is correct (e.g., target host, system number, client, user credentials).
  
  
  
  Test the RFC Connection:
  
  In SM59, select the RFC destination and use the "Connection Test" option to ensure that the connection can be established successfully.
  If the test fails, check the error messages for more details.
  
  
  
  Review Network Settings:
  
  Ensure that there are no firewall or network issues preventing the SAP system from reaching the RFC destination.
  Check if the hostname or IP address is correct and reachable from the SAP server.
  
  
  
  Check Authorizations:
  
  Ensure that the user executing the transaction has the necessary authorizations to access the RFC destination.
  
  
  
  Consult SAP Notes:
  
  Look for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  
  
  Related Information:
  
  Transaction SM59: This transaction is used to manage RFC destinations in SAP. It allows you to create, modify, and test RFC connections.
  BAS XML: This refers to Business Application Services XML, which is used for various integrations and data exchanges in SAP.
  RFC (Remote Function Call): A protocol used in SAP for communication between different SAP systems or between SAP and non-SAP systems.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.