How To Fix FKKDK_MSG004 - CPR/CVR number has already been defined for BP &1 in database

FKKDK_MSG004 - Overview

• Message type: E = Error

• Message class: FKKDK_MSG - Messages for Denmark FI-CA Localization

• Message number: 004

• Message text: CPR/CVR number has already been defined for BP &1 in database

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FKKDK_MSG004 - CPR/CVR number has already been defined for BP &1 in database ?

  The SAP error message FKKDK_MSG004 indicates that a CPR (Customer Payment Request) or CVR (Customer Value Request) number has already been defined for a Business Partner (BP) in the database. This typically occurs in the context of SAP's Contract Accounts Receivable and Payable (FI-CA) module, which manages customer accounts and payment requests.
  
  Cause:
  The error is triggered when you attempt to create or process a payment request or value request for a Business Partner that already has an existing CPR or CVR number assigned. This can happen due to:
  
  Duplicate Entry: An attempt to create a new request for a BP that already has an active or previously defined request.
  Data Migration Issues: If data was migrated from another system, it may have resulted in duplicate entries.
  Incorrect Configuration: Configuration settings may allow for the creation of multiple requests for the same BP, leading to conflicts.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check