How To Fix /ACCGO/UIS_MSG262 - On Account Of and Vendor are the same

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/UIS_MSG -

• Message number: 262

• Message text: On Account Of and Vendor are the same

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 /ACCGO/UIS_MSG262 - On Account Of and Vendor are the same ?

  The SAP error message /ACCGO/UIS_MSG262 indicates that there is an issue with a transaction where the "On Account Of" (OAO) and the vendor are the same. This typically occurs in the context of financial transactions, particularly in accounts payable or receivable processes.
  Cause:
  The error arises when a transaction is being processed that involves a payment or an invoice where the "On Account Of" entity (which could be a customer or another vendor) is the same as the vendor being paid. This situation is generally not allowed because it can lead to confusion in accounting records and may violate business rules or internal controls.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review the Transaction: Check the details of the transaction that triggered the error. Ensure that the "On Account Of" and vendor fields are correctly populated.
  
  
  Change the "On Account Of" Entity: If the transaction is indeed meant to be processed for a different entity, update the "On Account Of" field to reflect the correct entity that is not the same as the vendor.
  
  
  Consult Business Rules: Verify with your finance or accounting team if there are specific business rules that dictate how these transactions should be handled. There may be policies in place that prevent such transactions for a reason.
  
  
  Check Configuration: If you believe that the transaction should be allowed, check the configuration settings in SAP. There may be validation rules set up that prevent this type of transaction. You may need to adjust these settings, but this should be done with caution and typically requires authorization.
  
  
  Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting the SAP community for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may be involved in processing payments or invoices, such as FB60 (Enter Incoming Invoices) or F-53 (Post Outgoing Payments).
  Documentation: Review SAP documentation or help files related to accounts payable and the specific module you are working with to understand the implications of this error.
  User Exits or BAdIs: If your organization has custom developments, check if there are any user exits or BAdIs that might be affecting the behavior of the transaction.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.