How To Fix >9105 - Post office account and bank account are mutually exclusive

SAP Error Message - Details

• Message type: E = Error

• Message class: >9 - Messages for TAS

• Message number: 105

• Message text: Post office account and bank account are mutually exclusive

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 >9105 - Post office account and bank account are mutually exclusive ?

  The SAP error message "9105 Post office account and bank account are mutually exclusive" typically occurs in the context of financial transactions or settings where both a post office account and a bank account are being used or referenced simultaneously, which is not allowed in the system.
  Cause:
  This error arises when:
  
  Configuration Issue: The system is configured to require either a post office account or a bank account, but not both. If both are filled in or referenced in a transaction, the system will throw this error.
  Data Entry Error: During data entry, both fields for post office account and bank account may have been populated inadvertently.
  Master Data Setup: The vendor or customer master data may have both account types set up, leading to conflicts during transaction processing.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Transaction Data:
  
  Review the transaction or document that triggered the error. Ensure that only one of the fields (either post office account or bank account) is filled in.
  If both fields are populated, remove one of them based on your business requirements.
  
  
  
  Review Master Data:
  
  Go to the vendor or customer master data (transaction codes like XK02 for vendors or XD02 for customers).
  Check the account details and ensure that only one of the account types is maintained. If both are present, decide which one is appropriate and remove the other.
  
  
  
  Configuration Settings:
  
  If you have access to configuration settings, check the settings related to payment methods and account types in the Financial Accounting (FI) module.
  Ensure that the configuration aligns with your business processes and that it allows for the correct usage of either account type.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on handling account types in your version of SAP.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB60 (Enter Incoming Invoice), F110 (Automatic Payment Transactions), and others where this error might occur.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Roles: Ensure that users have the appropriate roles and permissions to make changes to master data and transaction entries.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.