How To Fix F2847 - Alternative payer/payee & cannot be same as Customer &

SAP Error Message - Details

• Message type: E = Error

• Message class: F2 - Master Data Maintenance: Customer, Vendor

• Message number: 847

• Message text: Alternative payer/payee & cannot be same as Customer &

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 F2847 - Alternative payer/payee & cannot be same as Customer & ?

  The SAP error message F2847 ("Alternative payer/payee & cannot be same as Customer &") typically occurs in the context of financial transactions where an alternative payer or payee is being set up in a customer master record. This error indicates that the alternative payer or payee cannot be the same as the customer itself, which is a validation rule in SAP to prevent circular references in financial transactions.
  Cause:
  
  Configuration Issue: The alternative payer or payee has been incorrectly set to the same customer number as the original customer.
  Data Entry Error: During the creation or modification of a customer master record, the user may have mistakenly entered the same customer number for both the customer and the alternative payer/payee fields.
  Business Logic: The business process may require distinct entities for billing and payment, and the system enforces this rule to maintain data integrity.
  
  Solution:
  
  
  Check Customer Master Data: Review the customer master data to ensure that the alternative payer or payee is set to a different customer number. You can do this by navigating to the customer master record in transaction code XD02 (Change Customer) or XD03 (Display Customer).
  
  
  Correct the Entry: If you find that the alternative payer/payee is the same as the customer, change it to a valid alternative payer or payee that is different from the customer.
  
  
  Review Configuration: If this error occurs frequently, it may be worth reviewing the configuration settings in the SAP system to ensure that the rules around alternative payers and payees are correctly set up according to your business requirements.
  
  
  Consult Documentation: Refer to SAP documentation or your organization's SAP support team for any specific configurations or business rules that may apply to your scenario.
  
  
  Testing: After making the necessary changes, test the transaction again to ensure that the error does not reoccur.
  
  
  Related Information:
  
  Transaction Codes: 
  
  XD01 - Create Customer
  XD02 - Change Customer
  XD03 - Display Customer
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or updates related to this error message.
  User Roles: Ensure that the user has the appropriate permissions to modify customer master data.
  Business Processes: Understand the business processes that involve alternative payers and payees to ensure compliance with organizational policies.
  
  By following these steps, you should be able to resolve the error and ensure that your customer master data is correctly configured.