How To Fix FTVV_MESSAGES397 - No alternative payee allowed in document for customer &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FTVV_MESSAGES - Reporting Financial Assets Management

• Message number: 397

• Message text: No alternative payee allowed in document for customer &1

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 FTVV_MESSAGES397 - No alternative payee allowed in document for customer &1 ?

  The SAP error message FTVV_MESSAGES397 ("No alternative payee allowed in document for customer &1") typically occurs in the context of financial transactions, particularly when dealing with customer invoices or payment processing. This error indicates that the system does not allow the use of an alternative payee for the specified customer.
  Cause:
  
  Customer Master Data Settings: The customer master record may not be set up to allow alternative payees. This can happen if the customer is configured in such a way that it does not permit alternative payment arrangements.
  Document Type Restrictions: Certain document types may have restrictions on using alternative payees. For example, some invoice types may not support alternative payees due to business rules or compliance requirements.
  Configuration Settings: The configuration settings in the SAP system may restrict the use of alternative payees for specific customers or transaction types.
  
  Solution:
  
  
  Check Customer Master Data:
  
  Go to the customer master record (transaction code XD03 for general data or FD03 for company code data).
  Verify the settings related to alternative payees. Ensure that the "Alternative Payee" field is correctly configured.
  
  
  
  Review Document Type Settings:
  
  Check the configuration of the document type being used (transaction code OBY6 for payment documents).
  Ensure that the document type allows for alternative payees if that is required for your business process.
  
  
  
  Consult with Configuration Team:
  
  If you do not have access to the configuration settings, consult with your SAP configuration team or administrator. They can review the settings in the Financial Accounting (FI) module to ensure that the necessary configurations are in place.
  
  
  
  Use Standard Payee:
  
  If the alternative payee is not allowed, consider using the standard payee associated with the customer for the transaction.
  
  
  
  Review Business Processes:
  
  Ensure that the business processes align with the system's configuration. If alternative payees are frequently needed, it may be worth discussing with stakeholders whether the configuration should be adjusted.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling alternative payees.
  Documentation: Review SAP documentation related to customer master data and payment processing to understand the implications of using alternative payees.
  User Forums: Consider searching or posting in SAP community forums for insights from other users who may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.