How To Fix FKK_PDC010 - Check &1 was already deposited with the bank

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_PDC - FI-CA: Postdated Checks

• Message number: 010

• Message text: Check &1 was already deposited with the bank

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 FKK_PDC010 - Check &1 was already deposited with the bank ?

  The SAP error message FKK_PDC010 indicates that a check (or payment) has already been deposited with the bank, and therefore, it cannot be processed again. This error typically arises in the context of financial transactions, particularly in the area of payment processing and check management.
  Cause:
  
  
  Duplicate Deposit: The primary cause of this error is that the check you are trying to process has already been marked as deposited in the system. This could happen if:
  
  The check was previously processed and deposited.
  There was an attempt to deposit the same check multiple times.
  There is a data entry error where the same check number is being used again.
  
  
  
  System Configuration: Sometimes, the configuration settings in the SAP system may not allow for the reprocessing of checks that have already been marked as deposited.
  
  
  Solution:
  
  
  Verify Check Status: Check the status of the check in the system to confirm whether it has indeed been marked as deposited. You can do this by:
  
  Navigating to the relevant transaction code (e.g., FBL1N for vendor line items) and checking the details of the check.
  Reviewing the deposit history to see if the check has already been processed.
  
  
  
  Correct Duplicate Entries: If you find that the check has been mistakenly entered multiple times, you will need to correct the entries:
  
  Remove or reverse the duplicate entry if it has not been processed yet.
  Ensure that the check number is unique for each transaction.
  
  
  
  Consult with Finance Team: If you are unsure about the status of the check or how to proceed, consult with your finance or accounting team. They may have additional insights or access to reports that can help clarify the situation.
  
  
  System Configuration Review: If this error occurs frequently, it may be worth reviewing the system configuration related to check processing to ensure that it aligns with your business processes.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FBL1N: Vendor Line Item Display
  FBL3N: G/L Account Line Item Display
  F110: Automatic Payment Transactions
  FCH5: Check Management
  
  
  
  Documentation: Review SAP documentation or help files related to check management and payment processing for more detailed guidance.
  
  
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide additional context or solutions specific to your version of SAP.
  
  
  User Roles: Ensure that you have the appropriate permissions to view and modify check transactions in the system.
  
  
  By following these steps, you should be able to resolve the error and prevent it from occurring in the future.