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

CNV_PE355 - Overview

• 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.

CNV_PE355 - Details

• 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