How To Fix FKCHK318 - Assignment to payment run &1 &2 contains different sequence numbers

SAP Error Message - Details

• Message type: E = Error

• Message class: FKCHK - Check Repository Messages

• Message number: 318

• Message text: Assignment to payment run &1 &2 contains different sequence numbers

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 FKCHK318 - Assignment to payment run &1 &2 contains different sequence numbers ?

  The SAP error message FKCHK318 indicates that there is a mismatch in the sequence numbers during the assignment of documents to a payment run. This typically occurs when you are trying to process a payment run that includes documents with different sequence numbers, which is not allowed in SAP.
  Cause:
  
  Different Sequence Numbers: The primary cause of this error is that the documents you are trying to include in the payment run have different sequence numbers. In SAP, each payment run is assigned a unique sequence number, and all documents included in that run must share the same sequence number.
  Incorrect Document Selection: The selection criteria used to choose documents for the payment run may have inadvertently included documents with different sequence numbers.
  Manual Changes: If there were manual changes made to the documents or payment run settings, it could lead to inconsistencies in sequence numbers.
  
  Solution:
  
  Check Document Selection: Review the documents selected for the payment run. Ensure that all documents have the same sequence number. You can do this by checking the payment document details in the relevant transaction (e.g., F110).
  Recreate Payment Run: If you find that there are documents with different sequence numbers, you may need to recreate the payment run. Ensure that you only select documents with the same sequence number.
  Use Payment Run Parameters: When setting up the payment run, ensure that the parameters are correctly configured to avoid selecting documents with different sequence numbers.
  Consult with SAP Support: If the issue persists, consider reaching out to SAP support for further assistance, especially if you suspect there may be a system issue or bug.
  
  Related Information:
  
  Transaction Codes: Common transaction codes related to payment runs include F110 (Automatic Payment Transactions) and F111 (Manual Payment Transactions).
  Documentation: Refer to SAP Help documentation for detailed information on payment processing and error handling.
  User Exits and BAdIs: If you have custom developments, check if any user exits or BAdIs are affecting the payment run process.
  
  By following these steps, you should be able to resolve the FKCHK318 error and successfully process your payment run.