How To Fix FIN_FB_RECON335 - Open item in BSEG, missing in BSID (but available in BSAD)


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 335

  • Message text: Open item in BSEG, missing in BSID (but available in BSAD)

  • Show details Hide details
  • What causes this issue?

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

    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_RECON335 - Open item in BSEG, missing in BSID (but available in BSAD) ?

    The SAP error message FIN_FB_RECON335 indicates that there is an open item in the BSEG table (which contains line items for accounting documents) that is missing in the BSID table (which contains open items for customer accounts) but is available in the BSAD table (which contains cleared items for customer accounts). This situation typically arises during the reconciliation process between the accounting documents and the open items in the customer accounts.

    Cause:

    1. Cleared Items: The item in question may have been cleared in the customer account, which would move it from BSID to BSAD, but the corresponding entry in BSEG may not have been updated or cleared properly.
    2. Data Inconsistency: There may be inconsistencies in the data due to manual adjustments, incorrect postings, or issues during data migration.
    3. Document Type Issues: The document type used for the transaction may not be configured correctly, leading to discrepancies between the tables.
    4. Posting Errors: Errors during posting transactions can lead to situations where the accounting entries do not match the customer account entries.

    Solution:

    1. Check Document Status: Review the status of the document in BSEG to ensure it is indeed open and has not been cleared or reversed.
    2. Reconcile Accounts: Perform a reconciliation of the customer accounts to identify discrepancies. Use transaction codes like FBL5N (Customer Line Item Display) to check the status of the customer account.
    3. Analyze the Document: Use transaction code FB03 to display the document in BSEG and check for any inconsistencies or errors in the document.
    4. Adjustments: If you find that the document should not be open, consider making the necessary adjustments to either clear the item or correct the posting.
    5. Run Reports: Use standard SAP reports or custom reports to identify and analyze discrepancies between BSEG, BSID, and BSAD.
    6. Consult SAP Notes: Check for any relevant SAP Notes that may address known issues related to this error message. SAP Notes can provide patches or guidance on how to resolve specific issues.
    7. Technical Support: If the issue persists, consider reaching out to your SAP support team or consulting with SAP support for further assistance.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as:
      • FB03: Display Document
      • FBL1N: Vendor Line Item Display
      • FBL5N: Customer Line Item Display
      • FBL3N: G/L Account Line Item Display
    • Tables:
      • BSEG: Document Segment
      • BSID: Accounting Document Segment for Open Items (Customer)
      • BSAD: Accounting Document Segment for Cleared Items (Customer)
    • Reconciliation Process: Understand the reconciliation process between the general ledger and sub-ledgers to ensure that all entries are correctly posted and cleared.

    By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant