How To Fix ICLCUST072 - Benefit type &1 object type &2: Type of evaluation &3 not defined

ICLCUST072 - Overview

• Message type: E = Error

• Message class: ICLCUST - Checking Customizing Tables

• Message number: 072

• Message text: Benefit type &1 object type &2: Type of evaluation &3 not defined

What causes this issue?

You want to assign the evaluator type &V3& to the combination of benefit
type &v1& / object type &V2&, but evaluator type &V3& has not been
defined.

System Response

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

How to fix this error?

Perform one of the following activities:
Delete the line with the assignment of evaluator type &V3&.
Create evaluator type &V3& (see below "Procedure for System
Administration").

Procedure for System Administrators

INCLUDE ICL_MESSAGE_CUST OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ICLCUST072 - Benefit type &1 object type &2: Type of evaluation &3 not defined ?

  The SAP error message ICLCUST072 typically indicates that there is a configuration issue related to the benefit type and evaluation type in the SAP system, particularly in the context of the SAP Benefits Administration module. Here’s a breakdown of the cause, potential solutions, and related information for this error:
  
  Cause:
  
  Undefined Evaluation Type: The error suggests that the evaluation type specified for a particular benefit type and object type is not defined in the system. This could happen if the configuration for benefits has not been completed correctly or if there are missing entries in the relevant customizing tables.
  Incorrect Configuration: The benefit type or object type may not be properly set up in the system, leading to the inability to find the corresponding evaluation type.
  Data Inconsistency: There may be inconsistencies in the data related to the benefit types or evaluation types, possibly due to changes in configuration or data migration issues.
  
  
  Solution:
  
  
  Check Configuration:
  
  Navigate