How To Fix OB042 - No excise duty values have been created; check Excise duty parameters

SAP Error Message - Details

• Message type: E = Error

• Message class: OB - IS-OIL Downstream TDP messages

• Message number: 042

• Message text: No excise duty values have been created; check Excise duty parameters

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 OB042 - No excise duty values have been created; check Excise duty parameters ?

  The SAP error message OB042, which states "No excise duty values have been created; check Excise duty parameters," typically occurs in the context of excise duty processing in SAP, particularly in modules related to materials management (MM) or financial accounting (FI). This error indicates that the system was unable to calculate or find the necessary excise duty values for a transaction, which can be due to several reasons.
  Causes of OB042 Error
  
  
  Missing Configuration: The excise duty parameters may not be properly configured in the system. This includes settings related to excise duty types, rates, and conditions.
  
  
  Incorrect Master Data: The material master or vendor master data may not have the necessary excise duty information. For example, the material may not be classified correctly for excise duty purposes.
  
  
  Transaction Type Issues: The transaction type being used may not be set up to handle excise duties, or the relevant excise duty conditions may not be active for that transaction.
  
  
  Document Type Settings: The document type used for the transaction may not be configured to allow for excise duty calculations.
  
  
  Missing Excise Duty Condition Records: The condition records for excise duty may not exist or may not be valid for the transaction being processed.
  
  
  Solutions to OB042 Error
  
  
  Check Excise Duty Configuration:
  
  Go to the configuration settings for excise duties in SAP (usually found in SPRO under Financial Accounting or Materials Management).
  Ensure that the excise duty types, rates, and conditions are correctly defined and active.
  
  
  
  Review Master Data:
  
  Check the material master data to ensure that the excise duty information is correctly maintained.
  Verify that the vendor master data includes the necessary excise duty details.
  
  
  
  Validate Transaction Type:
  
  Ensure that the transaction type being used is configured to handle excise duties.
  Check if the relevant excise duty conditions are active for the transaction type.
  
  
  
  Document Type Configuration:
  
  Review the document type settings to ensure that they allow for excise duty calculations.
  Make adjustments if necessary to include excise duty processing.
  
  
  
  Create or Update Condition Records:
  
  If condition records for excise duty are missing, create or update them using transaction codes like VK11 (Create Condition) or VK12 (Change Condition).
  Ensure that the records are valid for the relevant materials and vendors.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test transaction to see if the error persists.
  Monitor the system for any additional error messages that may provide further insight.
  
  
  
  Related Information
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  OB40: Maintain Excise Duty Types
  J1ID: Excise Invoice
  J1IEX: Excise Duty Adjustment
  VK11/VK12: Create/Change Condition Records
  
  
  
  Documentation: Refer to SAP documentation or help files for detailed guidance on excise duty configuration and processing.
  
  
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert who specializes in excise duty processing.
  
  
  By following these steps, you should be able to identify and resolve the cause of the OB042 error in your SAP system.