How To Fix FS685 - Check number &1 does not originate from check lot &2

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 685

• Message text: Check number &1 does not originate from check lot &2

What causes this issue?

You are using the Payment Medium Workbench (PMW) to print checks. In
transaction <DS:TRAN.OBPM3>OBPM3</>, you have enhanced the format so
that check numbers are determined at event 06. This has failed due to a
conflict. In transaction FCHI, for at least one check lot, the payment
method entered requires the PMW to determine check numbers using its own
logic.

System Response

The program terminates because the check number determined, &V1&, does
not originate from the check lot specified, &V2&. No checks were
printed. However, entries have been generated in the check register.

How to fix this error?

In transaction <DS:TRAN.FCHI>FCHI</>, remove the PMW payment method for
checks from check lots.
In transaction <DS:TRAN.FCHD>FCHD</>, delete the current payment run
from the check register.
Use program <DS:REPN.RFPAYM_RESET>RFPAYM_RESET</> to reset the PMW data
for the current payment run.
Restart the check printing job for the current payment run using
transaction <DS:TRAN.FBPM>FBPM</>.

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 FS685 - Check number &1 does not originate from check lot &2 ?

  The SAP error message FS685, which states "Check number &1 does not originate from check lot &2," typically occurs in the context of financial transactions involving checks. This error indicates that the check number being processed does not match the expected check lot from which it was issued. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  
  Mismatch of Check Number and Check Lot: The check number you are trying to process does not belong to the specified check lot. This can happen if:
  
  The check number was entered incorrectly.
  The check number was issued from a different check lot.
  The check lot has been closed or is no longer valid.
  
  
  
  Data Entry Errors: Manual entry errors when inputting check numbers or check lots can lead to this issue.
  
  
  System Configuration Issues: There may be configuration issues in the check management settings in SAP.
  
  
  Solution:
  
  
  Verify Check Number and Lot:
  
  Double-check the check number and the check lot you are using. Ensure that the check number is indeed part of the specified check lot.
  You can do this by checking the check lot details in the SAP system.
  
  
  
  Check Lot Status:
  
  Ensure that the check lot is still open and valid. If the check lot has been closed, you may need to create a new check lot or re-open the existing one if possible.
  
  
  
  Correct Data Entry:
  
  If there was a data entry error, correct the check number or check lot in the transaction you are processing.
  
  
  
  Consult with Finance Team:
  
  If you are unsure about the check lot or number, consult with your finance or accounting team to confirm the correct details.
  
  
  
  SAP Configuration:
  
  If the issue persists, it may be necessary to review the configuration settings related to check management in SAP. This may require assistance from an SAP consultant or your IT department.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like FCHN (Check Management) to view and manage check lots and check numbers.
  Documentation: Refer to SAP documentation or help files for more detailed information on check management and error handling.
  Support: If the problem cannot be resolved internally, consider reaching out to SAP support for assistance.
  
  By following these steps, you should be able to identify the cause of the FS685 error and implement a solution to resolve it.