How To Fix EDEREG_INV158 - Document number &1 is not in extract index (repeat run)

SAP Error Message - Details

• Message type: E = Error

• Message class: EDEREG_INV - Error Messages for Payment Management in a Deregulated Env.

• Message number: 158

• Message text: Document number &1 is not in extract index (repeat run)

What causes this issue?

The time period to be extracted was already extracted once before, so
this is a repeat run. This means that all documents from this period
have already been extracted and therefore should be located in the
extraction index of the older run.
The document &V1& could, however, not be found in the extraction index
(technical table ETAXTINVDOC), this is therefore a data inconsistency.

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?

If the cause of the data constellation can be explained logically and is
plausible, the older extract index should be deleted using the program
which is intended for that purpose, and the data affected should be
exported with a new run.

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 EDEREG_INV158 - Document number &1 is not in extract index (repeat run) ?

  The SAP error message EDEREG_INV158 indicates that a specific document number is not found in the extract index during a repeat run of a process, typically related to the extraction of data for reporting or data transfer purposes. This error can occur in various contexts, such as during the extraction of data for reporting or when trying to process documents that should have been previously extracted.
  Cause:
  
  Document Not Extracted: The document number specified may not have been extracted into the extract index during the initial run. This can happen if the document was created after the last extraction or if there was an error during the extraction process.
  Data Consistency Issues: There may be inconsistencies in the data, such as missing entries in the database or issues with the configuration of the extraction process.
  Incorrect Document Number: The document number provided in the error message may be incorrect or may not exist in the system.
  Indexing Issues: There could be issues with the extract index itself, such as corruption or misconfiguration.
  
  Solution:
  
  Check Document Existence: Verify that the document number exists in the relevant database tables. You can do this by querying the database or using transaction codes like SE16 or SE11 to check the relevant tables.
  Run Initial Extraction: If the document was created after the last extraction, you may need to run the initial extraction process again to include the new document in the extract index.
  Check Extraction Configuration: Review the configuration settings for the extraction process to ensure that it is set up correctly and that all necessary documents are being included.
  Rebuild Extract Index: If there are issues with the extract index, you may need to rebuild it. This can often be done through specific SAP transactions or programs designed for this purpose.
  Consult Logs: Check the application logs (transaction SLG1) for any additional error messages or warnings that may provide more context about why the document is not in the extract index.
  Contact SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SLG1 (Application Log), SE16 (Data Browser), and SE11 (Data Dictionary) for troubleshooting.
  Documentation: Review SAP documentation related to the specific extraction process you are working with, as there may be specific notes or guidelines for handling such errors.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.