How To Fix F5804 - Internal document no.in G/L acct table not in document header table

SAP Error Message - Details

• Message type: E = Error

• Message class: F5 - Document Editing

• Message number: 804

• Message text: Internal document no.in G/L acct table not in document header table

What causes this issue?

While scanning the FI interface table for G/L accounts, the system
found (in an item) an internal document number which is not in the
document header.

System Response

Data cannot be processed.

How to fix this error?

This is a system error in the calling application.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message F5804 - Internal document no.in G/L acct table not in document header table ?

  The SAP error message F5804, which states "Internal document no. in G/L acct table not in document header table," typically occurs when there is a mismatch between the General Ledger (G/L) account entries and the document header entries in the SAP system. This can happen due to various reasons, such as data inconsistencies, incomplete postings, or issues during data migration.
  Causes:
  
  Data Inconsistency: The internal document number exists in the G/L account table (e.g., BSEG) but does not have a corresponding entry in the document header table (e.g., BKPF).
  Incomplete Postings: A transaction may have been partially posted, leading to missing entries in the document header.
  Data Migration Issues: If data was migrated from another system, there may have been errors in the migration process that resulted in missing or inconsistent data.
  Database Corruption: In rare cases, database corruption can lead to missing entries.
  
  Solutions:
  
  Check Document Existence: Use transaction codes like SE16 or SE11 to check the entries in the BKPF (document header) and BSEG (document line items) tables. Verify if the internal document number exists in both tables.
  Repost Transactions: If the document is incomplete, you may need to repost the transaction to ensure that both the header and line items are correctly recorded.
  Data Consistency Check: Run the SAP program RFSEPA00 or RFBLG00 to check for inconsistencies in the financial documents and correct them.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on how to resolve it.
  Database Repair: If you suspect database corruption, consult your database administrator or SAP support for assistance in repairing the database.
  Custom Programs: If the issue persists, consider developing a custom ABAP program to identify and rectify the inconsistencies between the tables.
  
  Related Information:
  
  Transaction Codes: 
  
  SE16 or SE11 for table browsing.
  FB03 to display documents.
  FBRA for document reversal.
  
  
  Tables Involved:
  
  BKPF: Document Header Table
  BSEG: Document Segment Table
  
  
  SAP Notes: Always check for relevant SAP Notes that may provide specific fixes or patches related to this error.
  
  If the issue continues after trying the above solutions, it may be necessary to engage with SAP support or a qualified SAP consultant for further investigation and resolution.