How To Fix ICLCUST350 - Assigned benefit type tree &1 is not permitted

ICLCUST350 - Overview

• Message type: E = Error

• Message class: ICLCUST - Checking Customizing Tables

• Message number: 350

• Message text: Assigned benefit type tree &1 is not permitted

What causes this issue?

At claim header level, benefit type tree &v1& is assigned to the
specified internal claim type. However, with benefit type tree &v1& ,
the <ZK>For Coverage Type</> indicator has been set.

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:
In IMG activity <ZK>Configure Benefit Type Trees</>, in the benefit type
tree &v1& , remove the <ZK>For Coverage Type</> indicator.
In IMG activity <ZK>Configure Internal Claim Types</>, assign a
different benefit type tree to the specified internal claim type at
claim header level. This benefit type tree must be in the
<DS:GLOS.97DCAC452605D411A4910060B03C3B0E>Expenses</> category.

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 ICLCUST350 - Assigned benefit type tree &1 is not permitted ?

  The SAP error message ICLCUST350 indicates that the assigned benefit type tree (identified by &1) is not permitted in the context of the operation you are trying to perform. This error typically arises in the context of SAP's Benefits Administration or similar modules where benefit types are defined and managed.
  
  Cause:
  
  Incorrect Configuration: The benefit type tree may not be properly configured in the system. This could be due to missing entries or incorrect settings in the customizing tables.
  Authorization Issues: The user may not have the necessary authorizations to access or use the specified benefit type tree.
  Inactive Benefit Type: The benefit type tree might be inactive or not assigned to the relevant plan or program.
  Data Consistency Issues: There may be inconsistencies in the data related to the benefit type tree, such as missing dependencies or relationships.
  
  
  Solution:
  
  
  Check Configuration:
  
  Navigate to the relevant customizing transaction (e.g., SPRO) and verify the configuration of the benefit type