How To Fix FIKZ_DDX070 - Original Invoice is not found in the Journal (inv: &1 date: &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: FIKZ_DDX - Message class for digital documents exchange

• Message number: 070

• Message text: Original Invoice is not found in the Journal (inv: &1 date: &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 FIKZ_DDX070 - Original Invoice is not found in the Journal (inv: &1 date: &2) ?

  The SAP error message FIKZ_DDX070 indicates that the system is unable to find the original invoice in the journal for a specified invoice number and date. This error typically arises in the context of financial document processing, particularly when dealing with invoice verification or accounting entries.
  Cause:
  
  Missing Invoice: The original invoice may not have been posted correctly or may have been deleted.
  Incorrect Invoice Number or Date: The invoice number or date provided in the transaction may be incorrect or does not match any existing records in the journal.
  Document Type Issues: The document type used for the invoice may not be configured correctly in the system.
  Authorization Issues: The user may not have the necessary permissions to view the invoice in the journal.
  Data Consistency Issues: There may be inconsistencies in the database or issues with the data migration process.
  
  Solution:
  
  Verify Invoice Details: Check the invoice number and date to ensure they are correct. Make sure that the invoice exists in the system.
  Check Document Posting: Ensure that the original invoice has been posted correctly. You can do this by checking the relevant transaction codes (e.g., FB03 for displaying documents).
  Review Journal Entries: Look into the journal entries to confirm that the invoice is recorded. Use transaction codes like FBL1N (Vendor Line Item Display) or FBL3N (G/L Account Line Item Display) to find the relevant entries.
  Check Configuration: Review the configuration settings for the document type and ensure that it is set up correctly in the system.
  User Authorizations: Ensure that the user has the necessary authorizations to access the invoice and related journal entries.
  Consult with IT Support: If the issue persists, it may be necessary to consult with your SAP support team or IT department to investigate potential data consistency issues or system errors.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FBL1N (Vendor Line Item Display), and FBL3N (G/L Account Line Item Display) for troubleshooting.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation for invoice processing and journal entries to understand the expected workflow and configurations.
  
  By following these steps, you should be able to identify the root cause of the error and take appropriate action to resolve it.