How To Fix FKC_MIG006 - Document &1 was not found

SAP Error Message - Details

• Message type: E = Error

• Message class: FKC_MIG - FI-CAC: Migration Messages

• Message number: 006

• Message text: Document &1 was not found

What causes this issue?

For a dunning line, you have transferred a document as well as
(optionally) a line item and a due date. The system could not determine
any open items on the basis of these parameters.
No open item was determined for the following combination:
Document number: &V1&
Line item &V2&
Due date: &V3&

For a dunning line (IT_DUN_MAVS), you have transferred a document number
(OPBEL), as well as (optionally) a line item (OPUPK) and a due date
(FAEDN). The system could not determine any open items on the basis of
these parameters.
No open item was determined for the following combination:
Document number: &V1&
Line item &V2&
Due date: &V3&

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

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 FKC_MIG006 - Document &1 was not found ?

  The SAP error message FKC_MIG006: Document &1 was not found typically occurs during the migration of financial documents or when trying to access a document that the system cannot locate. This error can arise in various contexts, such as during data migration processes, document postings, or when executing specific financial transactions.
  Causes:
  
  Missing Document: The document referenced by the number (&1) does not exist in the system. This could be due to deletion, incorrect document number, or the document not being created in the first place.
  Incorrect Migration Settings: If you are migrating data, the settings or mapping used during the migration might not be correct, leading to references to non-existent documents.
  Data Inconsistencies: There may be inconsistencies in the database, such as missing entries in related tables that are required for the document to be found.
  Authorization Issues: The user may not have the necessary permissions to view or access the document, leading to the system not being able to retrieve it.
  
  Solutions:
  
  Verify Document Number: Check the document number you are trying to access. Ensure that it is correct and exists in the system.
  Check Migration Logs: If this error occurs during a migration process, review the migration logs for any errors or warnings that might indicate why the document was not created or found.
  Data Consistency Check: Run consistency checks on the relevant tables to ensure that all necessary data is present and correctly linked.
  Authorization Check: Ensure that the user has the appropriate authorizations to access the document. You may need to consult with your SAP security team.
  Recreate Document: If the document was deleted or not created, you may need to recreate it manually or through a batch process, depending on the context.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you might be using transaction codes like FB03 (Display Document), FBL1N (Vendor Line Item Display), or others related to financial document management.
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance, providing them with the error message details and any relevant logs or screenshots.
  Documentation: Review SAP documentation related to financial document management and migration processes for best practices and troubleshooting tips.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.