How To Fix FZ604 - > Pmnt method "&" in the document should not be considered in this run

SAP Error Message - Details

• Message type: E = Error

• Message class: FZ - Payment Transactions

• Message number: 604

• Message text: > Pmnt method "&" in the document should not be considered in this run

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 FZ604 - > Pmnt method "&" in the document should not be considered in this run ?

  The SAP error message FZ604 indicates that a specific payment method in a financial document is not valid for processing in the current run. This error typically arises during the payment run process when the system encounters a payment method that is either not configured correctly or is not allowed for the current payment run.
  Cause:
  
  Payment Method Configuration: The payment method specified in the document may not be configured for the payment run. This could be due to settings in the payment method configuration (transaction code OBVCU).
  Document Status: The document may be in a status that does not allow it to be processed with the specified payment method.
  Company Code Settings: The payment method may not be valid for the company code associated with the document.
  Payment Run Parameters: The parameters set for the payment run may exclude the specified payment method.
  Master Data Issues: The vendor or customer master data may not have the payment method assigned or may have restrictions.
  
  Solution:
  
  
  Check Payment Method Configuration:
  
  Go to transaction code OBVCU and verify the configuration of the payment method. Ensure that it is set up correctly for the relevant company code and payment run.
  
  
  
  Review Payment Run Parameters:
  
  When executing the payment run (transaction code F110), check the parameters to ensure that the payment method is included in the selection criteria.
  
  
  
  Verify Document Status:
  
  Check the status of the document in question. Ensure that it is eligible for payment processing.
  
  
  
  Check Master Data:
  
  Review the vendor or customer master data to ensure that the payment method is correctly assigned and that there are no restrictions.
  
  
  
  Consult with Configuration Team:
  
  If you are unsure about the configuration settings, consult with your SAP configuration team or a functional consultant who can provide insights into the payment method settings.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  F110: Automatic Payment Transactions
  OBVCU: Configuration of Payment Methods
  FK03: Display Vendor Master Data
  FD03: Display Customer Master Data
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on payment methods and their configuration.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to payment methods and error messages.
  
  
  By following these steps, you should be able to identify the cause of the FZ604 error and implement the necessary changes to resolve it.