How To Fix M8673 - Inconsistency: RSEG for client &, doc.no. &, FY &, & does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: M8 - Invoice Verification/Valuation

• Message number: 673

• Message text: Inconsistency: RSEG for client &, doc.no. &, FY &, & does not exist

What causes this issue?

Logistics invoie document item does not exist in client &V1& with the
invoice number &V2&, fiscal year &V3& and item number &V4&. A data
inconsistency has occurred.

System Response

The invoice document item cannot be processed further. You can continue
with the other items.

How to fix this error?

check that the entries in tables RSEG and RBDIFFME are correct for the
key field mentioned. You can re-start the XPRA report as any time, as
it restarts where it left off.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message M8673 - Inconsistency: RSEG for client &, doc.no. &, FY &, & does not exist ?

  The SAP error message M8673 indicates an inconsistency in the system related to the document flow in the Materials Management (MM) module. Specifically, it suggests that there is a missing entry in the RSEG table (which stores purchasing document item data) for a specific client, document number, fiscal year, and item.
  Cause:
  The error can occur due to several reasons, including:
  
  Data Inconsistency: The purchasing document might have been deleted or not properly created, leading to missing entries in the RSEG table.
  Database Issues: There could be issues with the database that prevent the proper retrieval of data.
  Transport Issues: If changes were transported between systems (e.g., from development to production), inconsistencies might arise if the transport was not executed correctly.
  Custom Development: Custom programs or enhancements that manipulate purchasing documents may lead to inconsistencies if not properly coded.
  
  Solution:
  To resolve the M8673 error, you can take the following steps:
  
  
  Check Document Existence:
  
  Use transaction codes like ME23N (Display Purchase Order) to check if the document exists in the system.
  Verify the document number, client, and fiscal year to ensure you are looking for the correct entry.
  
  
  
  Database Consistency Check:
  
  Run the report RM07ML00 to check for inconsistencies in the material documents and purchasing documents.
  Use transaction code SE11 to check the RSEG table directly for the specific document number and fiscal year.
  
  
  
  Recreate Missing Entries:
  
  If the document is missing, you may need to recreate it or restore it from a backup if available.
  If the document exists but is not linked correctly, you may need to adjust the entries manually or through a program.
  
  
  
  Check for Custom Code:
  
  Review any custom developments that may affect purchasing documents to ensure they are functioning correctly and not causing inconsistencies.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide patches.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance.
  
  
  
  Related Information:
  
  Transaction Codes: ME23N (Display Purchase Order), SE11 (Data Dictionary), SE38 (ABAP Program Execution).
  Tables: RSEG (Document Item Data), EKKO (Purchasing Document Header), EKPO (Purchasing Document Item).
  SAP Notes: Always check for the latest SAP Notes related to your version of SAP, as they may provide specific fixes or workarounds for known issues.
  
  By following these steps, you should be able to identify the cause of the M8673 error and implement a solution to resolve it.