How To Fix COPC_CCON004 - CashCon selection &1 for &2 is already configured in payt. req. in Cus.

COPC_CCON004 - Overview

• Message type: E = Error

• Message class: COPC_CCON - COPC: Cash Concentration

• Message number: 004

• Message text: CashCon selection &1 for &2 is already configured in payt. req. in Cus.

What causes this issue?

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

System Response

How to fix this error?

The selection data for the given house bank account id duplicated:
A selection level is assigned to the given house bank account in the
<DS:TRAN.EPIC_FF73_SET>Cash Concentration Settings</> (EPIC_FF73_SET)
transaction, on the <zk>Selection</> screen.
In the <DS:SIMG.CM_ZA>Define Levels in Payment Requests</> Customizing
activity, the same planning level is assigned to the payment request.
Only one level assignment is necessary.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

COPC_CCON004 - Details

• The SAP error message COPC_CCON004 indicates that there is a conflict in the configuration of cash concentration (CashCon) settings for a specific payment request. The message states that the cash concentration selection for a particular combination of parameters (represented by &1 and &2) is already configured in the payment request in the customer settings.
  
  Cause:
  This error typically arises due to one of the following reasons:
  
  Duplicate Configuration: The cash concentration configuration for the specified parameters has already been set up in the system, leading to a conflict when trying to create or modify a payment request.
  Incorrect Data Entry: There may be an error in the data entry where the same cash concentration selection is being attempted for a payment request that already exists.
  System Settings: The system may have restrictions or rules that prevent the same cash concentration configuration from being applied multiple times.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check