How To Fix CNV_10020155 - &1 &2: SDetObject &3 is flagged as "exclude"

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV_10020 - Message class for package 10020

• Message number: 155

• Message text: &1 &2: SDetObject &3 is flagged as "exclude"

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_10020155 - &1 &2: SDetObject &3 is flagged as "exclude" ?

  The SAP error message CNV_10020155 typically occurs during data migration or conversion processes, particularly when using the SAP S/4HANA Migration Cockpit or other data migration tools. This error indicates that a specific object (in this case, a "SDetObject") is flagged for exclusion, meaning that it is not included in the current migration or conversion process.
  Cause:
  The error message is triggered when:
  
  The object you are trying to process is marked as "exclude" in the migration settings or configuration.
  This could be due to a manual setting where certain objects are intentionally excluded from the migration process, possibly because they are not relevant for the current migration or because they are being handled separately.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Migration Settings:
  
  Review the migration settings or configuration to see if the object in question is indeed marked for exclusion. This can usually be done in the migration cockpit or the relevant transaction code used for the migration.
  
  
  
  Modify Exclusion Flags:
  
  If the object should not be excluded, you can modify the settings to remove the exclusion flag. This may involve changing the configuration in the migration tool or adjusting the relevant settings in the source system.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation or migration guides specific to the version you are using. This can provide insights into why certain objects might be excluded and how to manage them.
  
  
  
  Check Dependencies:
  
  Ensure that there are no dependencies or prerequisites that need to be addressed before including the object in the migration process.
  
  
  
  Testing:
  
  After making changes, perform a test migration to ensure that the object is now included and that the error does not reoccur.
  
  
  
  Seek Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP support or consulting with an SAP expert who can provide guidance based on your specific scenario.
  
  
  
  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 object exclusions.
  Error Logs: Check the error logs for more detailed information about the migration process and any other related errors that may provide context for the exclusion.
  SAP Notes: Look for relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.