How To Fix OB155 - No matching entries in external excise duty rates table

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 155

• Message text: No matching entries in external excise duty rates table

What causes this issue?

Cannot update with values entered as no excise duty rate is maintained
for the given combination of company, plant and ED group.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Ensure that the ED rate is already maintained for the combination
for which the group update. To see existing ED rates,
<DS:TRAS.O4K5>click here</>

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message OB155 - No matching entries in external excise duty rates table ?

  The SAP error message OB155, "No matching entries in external excise duty rates table," typically occurs when the system is unable to find the relevant entries in the external excise duty rates table for the transaction you are trying to process. This can happen in various scenarios, particularly in the context of excise duty calculations for goods movements, sales, or other financial transactions.
  Causes:
  
  Missing Entries: The external excise duty rates table (often referred to as J_1IEXC) may not have the necessary entries for the specific material, plant, or transaction type you are working with.
  Incorrect Configuration: The configuration settings for excise duty may not be set up correctly, leading to the system not being able to find the appropriate rates.
  Date Validity: The entries in the excise duty rates table may not be valid for the date of the transaction. If the rates are time-sensitive, ensure that the transaction date falls within the valid range of the rates.
  Incorrect Material Master Data: The material master data may not be correctly maintained, which can lead to the system not being able to find the appropriate excise duty rates.
  Transaction Type Issues: The transaction type being used may not be configured to use the external excise duty rates.
  
  Solutions:
  
  
  Check the External Excise Duty Rates Table:
  
  Go to transaction code SE16N or SE11 and check the table J_1IEXC to see if the required entries exist for the relevant material, plant, and transaction type.
  If entries are missing, you may need to create or update them.
  
  
  
  Review Configuration:
  
  Check the configuration settings for excise duty in the SAP system. This can typically be found in the SPRO transaction under the relevant sections for excise duty.
  Ensure that the settings for the excise duty rates are correctly defined and that they correspond to the materials and transactions you are working with.
  
  
  
  Validate Dates:
  
  Ensure that the transaction date falls within the validity period of the excise duty rates. If necessary, update the rates to include the required date range.
  
  
  
  Check Material Master Data:
  
  Review the material master data for the relevant materials to ensure that they are correctly classified for excise duty purposes.
  Ensure that the appropriate tax classification and excise duty indicators are set.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on excise duty configuration and troubleshooting.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as J1IEXC (for excise duty rates), J1IEXC1 (for maintaining excise duty rates), and OB40 (for maintaining tax codes).
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on excise duty configuration and troubleshooting.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the OB155 error and implement the necessary solutions to resolve it.