How To Fix FB765 - Doc. & &: No input exists for account determination

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 765

• Message text: Doc. & &: No input exists for account determination

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 FB765 - Doc. & &: No input exists for account determination ?

  The SAP error message FB765 ("Doc. & &: No input exists for account determination") typically occurs during the posting of financial documents when the system cannot find the appropriate account determination for the transaction. This can happen in various scenarios, such as during the posting of invoices, payments, or other financial transactions.
  Causes:
  
  Missing Configuration: The account determination settings for the specific transaction type or account group may not be configured in the system.
  Incorrect Document Type: The document type being used may not have the necessary account determination settings.
  Missing Master Data: The relevant master data (like customer or vendor master records) may not be set up correctly, leading to the absence of account determination.
  Transaction Type Not Defined: The transaction type being used may not be defined in the account determination configuration.
  Posting Keys: The posting keys used in the transaction may not be linked to the correct accounts in the configuration.
  
  Solutions:
  
  
  Check Account Determination Configuration:
  
  Go to the configuration settings in SAP (Transaction Code: SPRO).
  Navigate to Financial Accounting (New) > General Ledger Accounting (New) > Account Determination.
  Ensure that the account determination for the specific transaction type is correctly set up.
  
  
  
  Review Document Type Settings:
  
  Check the document type being used for the transaction.
  Ensure that the document type has the necessary account determination settings.
  
  
  
  Verify Master Data:
  
  Check the customer or vendor master records to ensure that they are correctly set up and linked to the appropriate accounts.
  Ensure that the relevant fields for account determination are filled in.
  
  
  
  Check Posting Keys:
  
  Review the posting keys being used in the transaction.
  Ensure that they are correctly configured to link to the appropriate accounts.
  
  
  
  Test with Different Scenarios:
  
  Try posting a similar transaction with a different document type or account to see if the issue persists.
  This can help isolate whether the problem is with a specific configuration or a broader issue.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SPRO (to access configuration settings)
  FB50, FB60, FB70 (for posting documents)
  
  
  Documentation: SAP Help Portal and community forums can provide additional insights and troubleshooting steps.
  Support: If the issue persists after checking the above configurations, consider reaching out to your SAP support team or consulting with an SAP expert.
  
  By following these steps, you should be able to identify and resolve the cause of the FB765 error message in SAP.