How To Fix FIN_FB_RECON338 - Open item in BSEG_ADD, missing in FAGLBSIS, available in FAGLBSAS

SAP Error Message - Details

• Message type: E = Error

• Message class: FIN_FB_RECON - Conversion to S/4HANA: Reconciliation

• Message number: 338

• Message text: Open item in BSEG_ADD, missing in FAGLBSIS, available in FAGLBSAS

What causes this issue?

There are open line items in table BSEG_ADD which are <ZH>not</>
available in the index table FAGLBSIS but these open line items are
already available in the index table FAGLBSAS.

System Response

The system informs about this inconsistency which must be corrected in
your productive system before starting the data migration.

How to fix this error?

For more information, see
<DS:URLA.HTTPS://LAUNCHPAD.SUPPORT.SAP.COM/#/NOTES/2714344>SAP Note
2714344.</>

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FIN_FB_RECON338 - Open item in BSEG_ADD, missing in FAGLBSIS, available in FAGLBSAS ?

  The SAP error message FIN_FB_RECON338 indicates a reconciliation issue between the tables BSEG_ADD, FAGLBSIS, and FAGLBSAS. This error typically arises during the reconciliation process in financial accounting, particularly when dealing with open items in the General Ledger (G/L) and the associated sub-ledgers.
  Cause:
  
  
  Data Inconsistency: The error occurs when there is an open item in the BSEG_ADD table that is not found in the FAGLBSIS table but is available in the FAGLBSAS table. This inconsistency can arise due to various reasons, such as:
  
  Incorrect postings or missing postings in the G/L.
  Data migration issues where not all records were transferred correctly.
  Manual adjustments or corrections that were not properly reflected in all relevant tables.
  
  
  
  Document Deletion or Changes: If a document was deleted or modified after it was posted, it might lead to discrepancies between these tables.
  
  
  Configuration Issues: Incorrect configuration in the financial accounting module can also lead to such errors.
  
  
  Solution:
  To resolve the FIN_FB_RECON338 error, you can follow these steps:
  
  
  Check the Open Item: Identify the specific open item causing the error. You can do this by analyzing the BSEG_ADD table for the relevant entries.
  
  
  Reconcile Data: 
  
  Verify if the open item exists in FAGLBSIS. If it does not, investigate why it is missing. 
  Check if the item is correctly posted in the G/L and ensure that all related postings are consistent.
  
  
  
  Data Consistency Check: Use transaction codes like FB03 to view the document and FBL1N, FBL3N, or FBL5N to check the line items in the respective ledgers.
  
  
  Repost or Adjust Entries: If you find discrepancies, you may need to repost the missing entries or make necessary adjustments to ensure that all tables reflect the correct data.
  
  
  Run Reconciliation Programs: Use SAP standard reconciliation programs or reports to identify and correct inconsistencies. Programs like F.01 (G/L Account Balances) or F.13 (Automatic Clearing) can be helpful.
  
  
  Consult SAP Notes: Check for any relevant SAP Notes that might address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
  
  
  Engage Technical Support: If the issue persists, consider reaching out to your SAP support team or consulting with SAP experts who can provide deeper insights into the problem.
  
  
  Related Information:
  
  
  Tables Involved:
  
  BSEG_ADD: Contains additional line item data for accounting documents.
  FAGLBSIS: Contains line items for the new G/L accounting.
  FAGLBSAS: Contains line items for the balance sheet accounts.
  
  
  
  Transaction Codes:
  
  FB03: Display Document
  FBL1N: Vendor Line Item Display
  FBL3N: G/L Account Line Item Display
  FBL5N: Customer Line Item Display
  F.01: G/L Account Balances
  F.13: Automatic Clearing
  
  
  
  By following these steps and understanding the underlying causes, you should be able to resolve the FIN_FB_RECON338 error effectively.