How To Fix FDC_POSTING_001666 - Bank statement item does not exist (Short Key &1 Item &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: FDC_POSTING_001 - FI Postings

• Message number: 666

• Message text: Bank statement item does not exist (Short Key &1 Item &2)

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 FDC_POSTING_001666 - Bank statement item does not exist (Short Key &1 Item &2) ?

  The SAP error message FDC_POSTING_001666 indicates that a bank statement item does not exist in the system. This error typically occurs during the processing of bank statements, particularly when trying to post or reconcile bank statement items that are not found in the system.
  Cause:
  
  
  Missing Bank Statement Item: The specific bank statement item referenced by the short key and item number does not exist in the system. This could be due to:
  
  The item was never imported or created.
  The item was deleted or archived.
  There is a mismatch in the data being processed (e.g., incorrect bank statement file).
  
  
  
  Incorrect Configuration: There may be issues with the configuration of the bank statement processing in SAP, leading to the system not recognizing the item.
  
  
  Data Entry Errors: Manual entry errors or incorrect data mapping during the import of bank statements can lead to this error.
  
  
  Solution:
  
  
  Verify Bank Statement Import:
  
  Check if the bank statement file was successfully imported into the system.
  Ensure that the bank statement items are present in the relevant tables (e.g., FEBKO for bank statement header and FEBEP for bank statement items).
  
  
  
  Check for Deletions or Archiving:
  
  Investigate if the item was deleted or archived. If so, you may need to restore it or adjust your processing logic.
  
  
  
  Review Configuration:
  
  Ensure that the bank statement processing configuration is correct. This includes checking the settings for the bank account, house bank, and any related mapping configurations.
  
  
  
  Data Consistency:
  
  Validate the data being processed for any inconsistencies or errors. Ensure that the short key and item number being referenced are correct.
  
  
  
  Re-import the Bank Statement:
  
  If the item is missing, consider re-importing the bank statement file to ensure all items are captured correctly.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to bank statement processing for any specific guidance or known issues.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like FF67 (for manual bank statement entry) or FEBAN (for processing bank statements) to troubleshoot and manage bank statements.
  SAP Notes: Check SAP Notes for any updates or patches related to bank statement processing that might address this error.
  Support: If the issue persists, consider reaching out to your SAP support team or consulting with SAP experts for further assistance.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.