How To Fix FF859 - No tax posting found in BSEG for BSET entry &1 &2 &3

SAP Error Message - Details

• Message type: E = Error

• Message class: FF - FI Function Module Messages

• Message number: 859

• Message text: No tax posting found in BSEG for BSET entry &1 &2 &3

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 FF859 - No tax posting found in BSEG for BSET entry &1 &2 &3 ?

  The SAP error message FF859 "No tax posting found in BSEG for BSET entry &1 &2 &3" typically occurs during the processing of tax-related transactions in SAP, particularly when the system is trying to find tax postings in the BSEG (Accounting Document Segment) table that correspond to entries in the BSET (Tax Data Document) table.
  Cause:
  
  
  Missing Tax Posting: The most common cause of this error is that there is no corresponding tax posting in the BSEG table for the tax data entry in the BSET table. This can happen if the tax was not posted correctly or if the transaction was not saved properly.
  
  
  Incorrect Configuration: There may be issues with the configuration of tax codes or tax calculation settings in the system.
  
  
  Data Inconsistency: There could be inconsistencies in the data due to manual changes or errors during data entry.
  
  
  Document Type Issues: The document type used may not be configured to allow tax postings.
  
  
  Solution:
  
  
  Check BSET and BSEG Entries: Verify that there are corresponding entries in both the BSET and BSEG tables. You can do this by using transaction codes like SE16 or SE16N to view the data in these tables.
  
  
  Repost the Document: If the tax posting is missing, you may need to repost the document or correct the original transaction to ensure that the tax is calculated and posted correctly.
  
  
  Review Tax Configuration: Check the configuration of tax codes and ensure that they are set up correctly in the system. This includes verifying the tax calculation procedures and ensuring that the relevant tax codes are active.
  
  
  Check Document Type Settings: Ensure that the document type used for the transaction is configured to allow tax postings. You can check this in the configuration settings for financial accounting.
  
  
  Run Tax Reports: Use tax reports (like S_ALR_87012357) to check for any discrepancies in tax postings and to ensure that all tax-related transactions are accounted for.
  
  
  Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error or provide additional guidance on resolving it.
  
  
  Related Information:
  
  Transaction Codes: SE16, SE16N (for table viewing), FB03 (to display documents), FBL1N (vendor line items), FBL3N (G/L account line items).
  Tables: BSET (Tax Data Document), BSEG (Accounting Document Segment), BKPF (Accounting Document Header).
  SAP Support: If the issue persists, consider reaching out to SAP support or consulting with a functional consultant who specializes in financial accounting and tax processes.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.