How To Fix COPC_CCON003 - CashCon selection &1 for &2 is already configured in bank G/L account

COPC_CCON003 - Overview

• Message type: E = Error

• Message class: COPC_CCON - COPC: Cash Concentration

• Message number: 003

• Message text: CashCon selection &1 for &2 is already configured in bank G/L account

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 transaction <DS:TRAN.FS00>Display G/L Account Centrally</> (FS00),
the same planning level is assigned to the bank G/L account.
Only one level assignment is necessary.

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 COPC_CCON003 - CashCon selection &1 for &2 is already configured in bank G/L account ?

  The SAP error message COPC_CCON003 indicates that there is a configuration issue related to cash concentration in the context of bank G/L accounts. Specifically, it suggests that a cash concentration configuration for a particular cash concentration account (represented by &1) and a specific bank G/L account (represented by &2) has already been set up in the system.
  
  Cause:
  
  Duplicate Configuration: The error typically arises when there is an attempt to configure a cash concentration account that has already been assigned to a bank G/L account. This can happen if the same cash concentration account is being configured multiple times for the same bank account.
  Incorrect Data Entry: There may be a mistake in the data entry where the same parameters are being used inadvertently.
  System Migration or Updates: If there have been recent migrations or updates to the system, it might have led to duplicate entries or inconsistencies in the configuration.
  
  
  Solution:
  
  
  Check Existing Configurations: 
  
  Navigate