How To Fix CNV_PE_CHECK390 - RFC destination &1 is in status error

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_PE_CHECK - Check Framework messages for posting engine

• Message number: 390

• Message text: RFC destination &1 is in status error

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 CNV_PE_CHECK390 - RFC destination &1 is in status error ?

  The SAP error message "CNV_PE_CHECK390 RFC destination &1 is in status error" typically indicates that there is an issue with the Remote Function Call (RFC) destination specified in the error message. This can occur during data migration or conversion processes, particularly when using the SAP Landscape Transformation (SLT) or other data migration tools.
  Cause:
  
  
  RFC Destination Configuration: The RFC destination may not be configured correctly in the SAP system. This could include incorrect connection parameters, such as the target system's hostname, system number, client, user credentials, etc.
  
  
  Network Issues: There may be network connectivity issues between the source and target systems, preventing the RFC call from being established.
  
  
  Authorization Issues: The user credentials used in the RFC destination may not have the necessary authorizations to perform the required operations.
  
  
  Target System Status: The target system may be down or not reachable, leading to an error in the RFC destination.
  
  
  Technical Issues: There could be underlying technical issues, such as problems with the SAP Gateway or other components involved in the RFC communication.
  
  
  Solution:
  
  
  Check RFC Destination Configuration:
  
  Go to transaction SM59 in the SAP GUI.
  Locate the RFC destination mentioned in the error message.
  Verify that the connection parameters (such as target host, system number, client, user, and password) are correct.
  
  
  
  Test the Connection:
  
  In transaction SM59, select the RFC destination and use the "Test Connection" option to check if the connection can be established successfully.
  
  
  
  Check Network Connectivity:
  
  Ensure that there are no network issues preventing communication between the systems. You can use tools like ping or telnet to check connectivity.
  
  
  
  Review User Authorizations:
  
  Ensure that the user specified in the RFC destination has the necessary authorizations to perform the required actions in the target system.
  
  
  
  Check Target System Status:
  
  Verify that the target system is up and running and that there are no issues with the SAP Gateway or other services.
  
  
  
  Review Logs:
  
  Check the system logs (transaction SM21) and the developer trace (transaction ST22) for any additional error messages that might provide more context about the issue.
  
  
  
  Consult SAP Notes:
  
  Look for relevant SAP Notes that might address known issues with RFC destinations or the specific error message you are encountering.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM59: Manage RFC Destinations
  SM21: System Log
  ST22: Dump Analysis
  SICF: Maintain HTTP Services (if applicable)
  
  
  
  Documentation: Refer to SAP Help documentation for more details on configuring RFC destinations and troubleshooting RFC issues.
  
  
  If the problem persists after following these steps, it may be necessary to involve your SAP Basis team or consult SAP support for further assistance.