How To Fix 8B279 - Condition or tax type & unknown

SAP Error Message - Details

• Message type: E = Error

• Message class: 8B - Localization (Brazil)

• Message number: 279

• Message text: Condition or tax type & unknown

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 8B279 - Condition or tax type & unknown ?

  The SAP error message 8B279 ("Condition or tax type & unknown") typically occurs in the context of pricing and tax calculations in SAP, particularly when dealing with sales documents, purchase orders, or billing documents. This error indicates that the system has encountered a condition type or tax type that it does not recognize or that has not been properly defined in the system.
  Causes:
  
  Missing Configuration: The condition type or tax type may not be configured in the system. This can happen if the necessary settings have not been completed in the pricing procedure or tax configuration.
  Incorrect Master Data: The master data (such as customer or vendor records) may reference a condition or tax type that is not defined in the system.
  Transport Issues: If the configuration was recently transported from another system (like a development or quality assurance system), there may have been issues during the transport process that resulted in missing definitions.
  Custom Development: If there are custom developments or enhancements in the pricing logic, they may reference condition types or tax types that are not standard or not properly defined.
  
  Solutions:
  
  
  Check Configuration:
  
  Go to the transaction code SPRO and navigate to the relevant configuration for pricing and tax types.
  Ensure that the condition type or tax type in question is defined in the pricing procedure and that it is active.
  Verify that the tax codes are correctly set up in the tax configuration.
  
  
  
  Review Master Data:
  
  Check the master data for the relevant customer or vendor to ensure that it does not reference any undefined condition or tax types.
  Update the master data if necessary to align with the defined condition types and tax types.
  
  
  
  Transport Check:
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary objects were transported correctly.
  If something is missing, you may need to re-transport the relevant configuration.
  
  
  
  Debugging:
  
  If you have access to debugging tools, you can analyze the pricing procedure during document processing to identify where the error is occurring.
  This may help you pinpoint the exact condition or tax type that is causing the issue.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to pricing and tax configuration for any additional insights or updates that may be relevant to your version of SAP.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance. They may have specific notes or patches that address this error.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SPRO: Customizing Implementation Guide
  VK11/VK12: Create/Change Condition Records
  OB40: Maintain Tax Codes
  
  
  Pricing Procedure: Ensure that the pricing procedure assigned to the document type includes all necessary condition types.
  Tax Configuration: Review the tax configuration settings in the system to ensure compliance with local tax regulations.
  
  By following these steps, you should be able to identify and resolve the cause of the SAP error message 8B279.