How To Fix CNVHCM_PRESEL123 - Remove wildcard for object type in path of limit in step &1

CNVHCM_PRESEL123 - Overview

• Message type: E = Error

• Message class: CNVHCM_PRESEL - TDMS4HCM: Messages for Object Selection

• Message number: 123

• Message text: Remove wildcard for object type in path of limit in step &1

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.

CNVHCM_PRESEL123 - Details

• The SAP error message CNVHCM_PRESEL123 typically occurs during the data migration process, particularly when using the SAP HCM (Human Capital Management) module. This error indicates that there is an issue with the use of wildcards in the path of a limit for a specific object type in the migration process.
  
  Cause:
  The error is caused by the use of a wildcard character (like * or ?) in the object type path when defining limits for the data selection. Wildcards are not allowed in certain contexts, especially when the system expects a specific object type or a defined path.
  
  Solution:
  To resolve this error, you should:
  
  
  Review the Configuration: Check the configuration settings where the error is occurring. Look for any paths or limits that include wildcard characters.
  
  
  Remove Wildcards: Modify the configuration to remove any wildcard characters from the object type path. Ensure that you specify the exact object type or path without using wildcards.
  
  
  Test the