How To Fix FS655 - Check lot & is not sequential for the valid banks


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FS - Messages from Tax Routines / Prenumbered Checks

  • Message number: 655

  • Message text: Check lot & is not sequential for the valid banks

  • Show details Hide details
  • What causes this issue?

    The specified check lot is defined as a non-sequential lot for all
    valid banks.
    This transaction, however, requires a check lot that contains
    sequential check numbers.

    How to fix this error?

    See how your check lot has been defined, and then enter here a check
    lot that uses sequential number assignment.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message FS655 - Check lot & is not sequential for the valid banks ?

    The SAP error message FS655 ("Check lot & is not sequential for the valid banks") typically occurs in the context of managing checks and bank transactions within the SAP system. This error indicates that the check lot number being used is not in the expected sequential order for the specified bank. Here’s a breakdown of the cause, potential solutions, and related information:

    Cause:

    1. Non-Sequential Check Lot Numbers: The check lot numbers assigned to checks for a specific bank are expected to be sequential. If there are gaps or if the check lot number is not in the expected sequence, this error will be triggered.
    2. Configuration Issues: The configuration settings for the check lot management in the bank master data may not be set up correctly.
    3. Manual Entry Errors: If check lot numbers are entered manually, there may be human errors leading to non-sequential entries.
    4. Multiple Users: If multiple users are processing checks simultaneously, it may lead to conflicts or non-sequential entries.

    Solution:

    1. Check the Check Lot Configuration:

      • Go to the bank master data and verify the check lot settings. Ensure that the check lot numbers are configured to be sequential.
      • Check the settings in transaction code OBV2 (for check lot management) to ensure that the sequence is correctly defined.
    2. Review Existing Check Lots:

      • Use transaction code FCHI (Check Management) to review the existing check lots for the bank in question. Look for any gaps or inconsistencies in the check lot numbers.
      • If you find any non-sequential numbers, you may need to adjust them or create a new check lot.
    3. Create a New Check Lot:

      • If the current check lot is problematic, consider creating a new check lot with a proper sequential number. This can be done in the check management area.
    4. Consult with Your SAP Administrator:

      • If you are unable to resolve the issue, consult with your SAP administrator or support team. They may have access to additional tools or logs that can help diagnose the problem.
    5. User Training:

      • Ensure that users involved in check processing are trained on the importance of maintaining sequential check lot numbers and the correct procedures for entering them.

    Related Information:

    • Transaction Codes:
      • FCHI: Check Management
      • OBV2: Check Lot Management
      • OBPM1: Bank Master Data
    • Documentation: Refer to SAP Help documentation for detailed information on check management and bank configuration.
    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.

    By following these steps, you should be able to identify the cause of the FS655 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