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

SAP Error Message - Details

• 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.

Smart SAP Assistant

• What is the cause and solution for SAP error message COPC_CCON004 - CashCon selection &1 for &2 is already configured in payt. req. in Cus. ?

  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 Existing Configurations:
  
  Navigate to the relevant configuration settings in SAP and check if the cash concentration selection for the specified parameters is already configured.
  If it is, review the configuration to ensure it is correct and meets your requirements.
  
  
  
  Modify or Delete Duplicate Entries:
  
  If you find that there are duplicate entries, you may need to modify or delete the existing configuration that is causing the conflict.
  Ensure that any changes made do not affect other processes or configurations.
  
  
  
  Review Payment Request:
  
  Check the payment request that is causing the error. Ensure that it is not referencing a cash concentration selection that is already in use.
  If necessary, create a new payment request with a different cash concentration selection.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources related to cash concentration and payment requests for additional guidance on configuration and troubleshooting.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you are unable to resolve it, consider reaching out to SAP support for assistance. They can provide more specific guidance based on your system configuration and version.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBPM1 (for cash concentration configuration) and F110 (for payment processing) to navigate the system effectively.
  SAP Notes: Check for any SAP Notes related to cash concentration errors or the specific error message for potential patches or updates that may address the issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, providing insights or solutions from other users' experiences.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.