How To Fix CNV_PE355 - &1 no RFC call at all - not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_PE - General messages for posting engine

• Message number: 355

• Message text: &1 no RFC call at all - not allowed

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_PE355 - &1 no RFC call at all - not allowed ?

  The SAP error message CNV_PE355 with the description "no RFC call at all - not allowed" typically occurs during data migration or conversion processes, particularly when using the SAP Landscape Transformation (SLT) or other data migration tools. This error indicates that an RFC (Remote Function Call) is not being executed as expected, which can halt the data transfer or conversion process.
  Causes:
  
  Configuration Issues: The RFC destination may not be properly configured in the SAP system. This could include incorrect settings in the RFC destination or missing authorizations.
  Network Issues: There may be network connectivity problems between the systems involved in the RFC call.
  Authorization Problems: The user executing the migration may not have the necessary authorizations to perform the RFC call.
  System Settings: Certain system settings or parameters may restrict RFC calls, especially in a production environment.
  Technical Errors: There could be underlying technical issues, such as system performance problems or bugs in the migration tool.
  
  Solutions:
  
  
  Check RFC Configuration:
  
  Go to transaction SM59 and verify the configuration of the RFC destination. Ensure that it is correctly set up and that the connection is working.
  Test the RFC connection to ensure it is functioning properly.
  
  
  
  Review Authorizations:
  
  Ensure that the user executing the migration has the necessary authorizations to perform RFC calls. Check roles and profiles assigned to the user.
  
  
  
  Network Connectivity:
  
  Verify that there are no network issues preventing the RFC call. This may involve checking firewalls, network routes, and connectivity between the systems.
  
  
  
  System Parameters:
  
  Check system parameters related to RFC calls. Ensure that there are no restrictions in place that would prevent RFC calls from being executed.
  
  
  
  Logs and Traces:
  
  Review system logs (transaction SM21) and traces (transaction ST22 for dumps) for any additional error messages or information that could provide more context about the issue.
  
  
  
  Consult Documentation:
  
  Refer to SAP Notes and documentation related to the specific migration tool or process you are using. There may be known issues or additional configuration steps required.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. Provide them with detailed information about the error and the context in which it occurs.
  
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes that may address this specific error or provide guidance on troubleshooting.
  Migration Tools Documentation: Review the documentation for the specific migration tool you are using (e.g., SAP S/4HANA Migration Cockpit, SLT) for any specific requirements or configurations.
  Community Forums: Check SAP Community forums or other online resources where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the cause of the CNV_PE355 error and implement a solution to resolve it.