How To Fix FIN_FB_RECON336 - Open item in BSEG, missing in BSIK (but available in BSAK)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 336

• Message text: Open item in BSEG, missing in BSIK (but available in BSAK)

What causes this issue?

There are open line items in table BSEG which are <ZH>not</> available
in the index table BSIK but these open line items are already available
in the index table BSAK.

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_RECON336 - Open item in BSEG, missing in BSIK (but available in BSAK) ?

  The SAP error message FIN_FB_RECON336 indicates that there is an inconsistency between the open items in the BSEG (Accounting Document Segment) table and the BSIK (Accounting Document Segment: Open Items) table. Specifically, it means that there is an open item in BSEG that is not found in BSIK, but it is available in BSAK (Accounting Document Segment: Cleared Items).
  Cause:
  
  
  Data Inconsistency: This error typically arises due to inconsistencies in the data between the tables. It can occur if:
  
  An open item was created in BSEG but not properly updated in BSIK.
  There was a manual intervention or a custom program that did not maintain the integrity of the data.
  A transaction was reversed or cleared incorrectly, leading to discrepancies.
  
  
  
  Clearing Issues: If an item was cleared in BSAK but not reflected in BSIK, it can lead to this error. This might happen if the clearing process was interrupted or if there were issues during the posting of clearing documents.
  
  
  Custom Developments: Custom programs or enhancements that manipulate financial data can sometimes lead to inconsistencies if they do not follow the standard SAP processes.
  
  
  Solution:
  
  
  Check the Open Item: Identify the specific open item causing the error. You can do this by running a report or using transaction codes like SE16N to view the BSEG, BSIK, and BSAK tables.
  
  
  Reconcile the Data: 
  
  If the open item exists in BSEG but not in BSIK, you may need to manually create the corresponding entry in BSIK.
  If the item should be cleared, ensure that the clearing document is posted correctly.
  
  
  
  Use Transaction Codes: 
  
  Use transaction code FB03 to display the document in BSEG and check its status.
  Use FBL1N or FBL3N to check the open items for vendors or G/L accounts.
  
  
  
  Run Reports: Use standard SAP reports to identify discrepancies. Reports like S_ALR_87012086 (for open items) can help in identifying issues.
  
  
  Consult SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide guidance on how to resolve it.
  
  
  Data Correction: If necessary, you may need to use transaction FBRA (to reverse a document) or FB08 (to reverse a clearing) to correct the entries.
  
  
  Consult with SAP Support: If the issue persists and you cannot resolve it, consider reaching out to SAP support for assistance.
  
  
  Related Information:
  
  BSEG: This table contains line items for accounting documents.
  BSIK: This table contains open items for vendor accounts.
  BSAK: This table contains cleared items for vendor accounts.
  Transaction Codes: Familiarize yourself with relevant transaction codes for viewing and managing financial documents (e.g., FB03, FBL1N, FBL3N).
  
  By following these steps, you should be able to identify the cause of the FIN_FB_RECON336 error and take appropriate action to resolve it.