How To Fix CM_EHHSS_RAS_COMMON142 - Ad hoc control &1 is not considered in the evaluation

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHHSS_RAS_COMMON - Common Messages for Risk Assessment

• Message number: 142

• Message text: Ad hoc control &1 is not considered in the evaluation

What causes this issue?

Control &V1& was selected for evaluation. However, this control is an ad
hoc control without control catalog entry and control master data.
Therefore, it cannot be evaluated.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

The system does not evaluate this control.

How to fix this error?

You can perform the evaluation, but the system evaluates only the
standard controls. Therefore, ad hoc control &V1& does not appear in the
evaluation.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_EHHSS_RAS_COMMON142 - Ad hoc control &1 is not considered in the evaluation ?

  The SAP error message CM_EHHSS_RAS_COMMON142, which states "Ad hoc control &1 is not considered in the evaluation," typically occurs in the context of the SAP Environment, Health, and Safety (EHS) module, particularly when dealing with risk assessment or compliance evaluations.
  
  Cause:
  This error message usually indicates that the specific ad hoc control (identified by &1) is not included in the evaluation process. This can happen for several reasons:
  
  Control Not Active: The ad hoc control may not be active or properly configured in the system.
  Evaluation Criteria: The evaluation criteria set for the assessment may not include the specific ad hoc control.
  Data Inconsistency: There may be inconsistencies or missing data related to the ad hoc control in the system.
  Authorization Issues: The user may not have the necessary authorizations to view or evaluate the ad hoc control.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Control Configuration:
  
  Verify that the ad hoc control is correctly