How To Fix OB039 - Excise duty default sequence indicator for company & not valid

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 039

• Message text: Excise duty default sequence indicator for company & not valid

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 OB039 - Excise duty default sequence indicator for company & not valid ?

  The SAP error message OB039, which states "Excise duty default sequence indicator for company & not valid," typically occurs in the context of excise duty configuration in SAP, particularly in the Indian version of SAP where excise duty is a significant aspect of tax management.
  Cause:
  This error usually arises due to one of the following reasons:
  
  Missing Configuration: The excise duty sequence indicator has not been defined for the specified company code in the system.
  Incorrect Sequence Indicator: The sequence indicator that has been set up is either incorrect or not valid for the company code in question.
  Data Inconsistency: There may be inconsistencies in the configuration settings related to excise duties, such as missing entries in the relevant tables.
  Company Code Not Assigned: The company code may not be properly assigned to the excise duty configuration.
  
  Solution:
  To resolve the OB039 error, you can follow these steps:
  
  
  Check Configuration:
  
  Go to the transaction code OBY6 (or navigate through the menu: SPRO > Financial Accounting > Financial Accounting Global Settings > Tax on Sales/Purchases > Basic Settings > Define Excise Duty Sequence).
  Ensure that the excise duty sequence indicator is defined for the relevant company code.
  
  
  
  Define Excise Duty Sequence:
  
  If the sequence indicator is missing, you will need to create it. Make sure to enter the correct details, including the sequence number and the relevant tax codes.
  
  
  
  Validate Entries:
  
  Check the entries in the relevant tables (e.g., TTXP for tax codes) to ensure that the excise duty settings are consistent and correctly configured.
  
  
  
  Check Company Code Assignment:
  
  Ensure that the company code is properly assigned to the excise duty configuration. This can be checked in the same configuration area.
  
  
  
  Transport Requests:
  
  If changes were made in a development environment, ensure that the transport requests are moved to the production environment correctly.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to excise duty configuration for any additional steps or considerations specific to your version of SAP.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6, OBCO (for company code settings), and OBCS (for tax codes).
  SAP Notes: Check SAP Notes for any known issues or patches related to excise duty configuration.
  User Roles: Ensure that you have the necessary authorizations to make changes to the configuration settings.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation or to reach out to SAP support for assistance.