How To Fix FKKINV668 - *** &1 source documents could not be processed

SAP Error Message - Details

• Message type: E = Error

• Message class: FKKINV - Invoicing in Contract Accounts Receivable and Payable

• Message number: 668

• Message text: *** &1 source documents could not be processed

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 FKKINV668 - *** &1 source documents could not be processed ?

  The SAP error message FKKINV668 indicates that certain source documents could not be processed in the context of the contract accounts receivable and payable (FI-CA) module. This error typically arises during the processing of invoices or billing documents, and it can be caused by various factors. Here’s a breakdown of the potential causes, solutions, and related information:
  Causes:
  
  Missing or Incomplete Data: The source documents may have missing or incomplete data that prevents them from being processed.
  Document Status: The source documents might be in a status that does not allow processing (e.g., blocked, archived, or already processed).
  Configuration Issues: There may be configuration issues in the FI-CA module that affect how documents are processed.
  Authorization Issues: The user may not have the necessary authorizations to process the documents.
  Technical Errors: There could be underlying technical issues, such as database inconsistencies or system errors.
  
  Solutions:
  
  Check Document Status: Review the status of the source documents to ensure they are eligible for processing. You can do this by checking the document in the relevant transaction (e.g., FPL9, FBL5N).
  Review Data Completeness: Ensure that all required fields in the source documents are filled out correctly. This includes checking for missing customer data, amounts, or other critical information.
  Authorization Check: Verify that the user has the necessary authorizations to process the documents. This can be done by checking the user roles and authorizations in the SAP system.
  Configuration Review: Consult with your SAP FI-CA configuration team to ensure that the settings related to document processing are correctly configured.
  Error Logs: Check the system logs (transaction SLG1) for any additional error messages or details that can provide more context about the issue.
  Reprocessing: If the documents were previously processed and are now causing issues, consider reversing or reprocessing them as needed.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error message. SAP frequently releases notes that provide fixes or workarounds for known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FPL9 (Display Document), FBL5N (Customer Line Item Display), and SLG1 (Application Log).
  Documentation: Review SAP documentation related to FI-CA for more insights into document processing and error handling.
  Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  By following these steps, you should be able to identify the cause of the FKKINV668 error and implement a suitable solution.