How To Fix FKCHK320 - The number of assigned check numbers in payment run &1 &2 is incorrect

SAP Error Message - Details

• Message type: E = Error

• Message class: FKCHK - Check Repository Messages

• Message number: 320

• Message text: The number of assigned check numbers in payment run &1 &2 is incorrect

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FKCHK320 - The number of assigned check numbers in payment run &1 &2 is incorrect ?

  The SAP error message FKCHK320 indicates that there is an inconsistency in the number of assigned check numbers during a payment run. This typically occurs when the system expects a certain number of check numbers to be assigned to the payment documents, but the actual number does not match this expectation.
  Cause:
  
  Mismatch in Check Number Assignment: The number of check numbers assigned to the payment documents does not match the number of payment documents being processed.
  Configuration Issues: There may be issues with the configuration of the payment program or the check number range.
  Data Integrity Issues: There could be inconsistencies in the database, such as missing or duplicate check numbers.
  User Errors: Manual entries or adjustments made to the payment documents or check numbers may have led to this inconsistency.
  
  Solution:
  
  Check Payment Run Parameters: Review the parameters set for the payment run to ensure that they are correct and that the expected number of check numbers matches the number of payment documents.
  Verify Check Number Assignment: Go to the payment run log and verify the assigned check numbers. Ensure that each payment document has a corresponding check number.
  Adjust Check Number Range: If the check number range is exhausted or incorrectly configured, adjust the range in the configuration settings (Transaction code: OBPM1 for payment methods).
  Re-run the Payment Program: If the issue is resolved, re-run the payment program to see if the error persists.
  Check for Data Integrity: Use transaction codes like SE16 or SE11 to check the relevant tables (e.g., REGUH, REGUP) for any inconsistencies in the check number assignments.
  Consult SAP Notes: Check the SAP Support Portal for any relevant notes or patches that may address this specific error.
  
  Related Information:
  
  Transaction Codes: 
  
  F110: For executing the payment run.
  OBPM1: For configuring payment methods.
  SE16/SE11: For checking database tables.
  
  
  Tables Involved:
  
  REGUH: Header data for payment runs.
  REGUP: Item data for payment runs.
  
  
  SAP Notes: Always check for specific SAP Notes related to payment processing and check number assignment for any known issues or fixes.
  
  If the problem persists after following these steps, it may be necessary to involve your SAP Basis or technical team for further investigation.