How To Fix CNV_PE540 - Either provide include name or exit class name, not both

CNV_PE540 - Overview

• Message type: E = Error

• Message class: CNV_PE - General messages for posting engine

• Message number: 540

• Message text: Either provide include name or exit class name, not both

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_PE540 - Details

• The SAP error message CNV_PE540 typically occurs during the execution of a conversion program or during data migration processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that there is a conflict in the parameters being passed to the program, specifically that both an include name and an exit class name have been provided, which is not allowed.
  
  Cause:
  The error arises when the system expects either an include name or an exit class name to be specified, but both have been provided in the configuration or during the execution of the program. This can happen due to:
  
  Incorrect Configuration: The settings in the migration or conversion program may have been incorrectly configured, leading to both parameters being filled.
  Custom Code Issues: If there is custom code involved in the migration process, it may be incorrectly passing both parameters.
  Data Migration Template Issues: If you are using a template