How To Fix CNV_MBT560 - User & is excluded by default

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_MBT - PCL message class

• Message number: 560

• Message text: User & is excluded by default

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_MBT560 - User & is excluded by default ?

  The SAP error message "CNV_MBT560 User & is excluded by default" typically occurs in the context of data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or similar tools. This error indicates that a specific user is excluded from the migration process due to default settings or configurations.
  Cause:
  
  User Exclusion Settings: The user in question may be excluded from the migration process due to predefined settings in the migration tool or project configuration.
  Authorization Issues: The user may not have the necessary authorizations to participate in the migration process.
  Configuration Parameters: Certain parameters in the migration cockpit or project settings may be set to exclude specific users or roles.
  
  Solution:
  
  
  Check User Exclusion Settings:
  
  Review the migration project settings to see if the user is explicitly excluded. This can often be found in the configuration or settings of the migration tool.
  If the user is listed as excluded, you may need to remove them from the exclusion list.
  
  
  
  Review User Authorizations:
  
  Ensure that the user has the necessary authorizations to perform the migration tasks. This may involve checking roles and profiles assigned to the user.
  If the user lacks the required permissions, you may need to assign the appropriate roles or consult with your SAP security team.
  
  
  
  Modify Configuration Parameters:
  
  If the exclusion is due to configuration parameters, you may need to adjust these settings to include the user in the migration process.
  Consult the documentation for the specific migration tool you are using to understand how to modify these parameters.
  
  
  
  Consult Documentation:
  
  Refer to the SAP Help Portal or relevant documentation for the migration tool you are using. This can provide insights into default settings and how to modify them.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. They can provide guidance based on the specific context of your migration project.
  
  
  
  Related Information:
  
  Migration Cockpit: Familiarize yourself with the SAP S/4HANA Migration Cockpit, as it is a common tool used for data migration and may have specific settings related to user exclusions.
  User Roles and Authorizations: Understanding SAP's role-based access control can help in troubleshooting authorization-related issues.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to include the user in the migration process.