How To Fix FICO1164 - &3: Date category &2 not defined in Customizing for condition type &1

SAP Error Message - Details

• Message type: E = Error

• Message class: FICO1 -

• Message number: 164

• Message text: &3: Date category &2 not defined in Customizing for condition type &1

What causes this issue?

The condition data entered does not agree with Customizing
for this condition type..
Such errors may oocur due to a retroactive change in Customizing or due
to incorrect BAPI data.

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?

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 FICO1164 - &3: Date category &2 not defined in Customizing for condition type &1 ?

  The SAP error message FICO1164 typically indicates that there is an issue with the configuration of a condition type in the Financial Accounting (FI) or Controlling (CO) module. Specifically, the error message states that a date category is not defined for a particular condition type in the system.
  Cause:
  The error occurs when:
  
  A condition type is being used in a transaction (like pricing, discounts, or other financial calculations) that requires a specific date category.
  The date category has not been defined in the Customizing settings for that condition type.
  
  Solution:
  To resolve this error, you need to define the missing date category for the specified condition type in the Customizing settings. Here are the steps to do this:
  
  
  Access Customizing:
  
  Go to the SAP Easy Access screen.
  Navigate to the Customizing menu: SPRO -> SAP Reference IMG.
  
  
  
  Find the Relevant Configuration:
  
  Depending on the context of the condition type, navigate to the appropriate section. For example, if it’s related to pricing, you might go to:
  
  Financial Accounting (New) -> Accounts Receivable and Accounts Payable -> Basic Functions -> Pricing -> Define Condition Types.
  
  
  
  
  
  Define Date Category:
  
  Locate the condition type that is causing the error (indicated by &1 in the error message).
  Check the settings for the condition type and look for the option to define the date category.
  If the date category is not defined, you will need to create or assign a valid date category.
  
  
  
  Save Changes:
  
  After making the necessary changes, save your configuration.
  
  
  
  Test the Transaction:
  
  Go back to the transaction that triggered the error and test it again to ensure that the issue has been resolved.
  
  
  
  Related Information:
  
  Date Categories: In SAP, date categories are used to determine how dates are handled for various conditions. They can affect how pricing, discounts, and other financial calculations are applied based on the date.
  Condition Types: Condition types are used in SAP to define how different pricing elements are calculated. Each condition type can have specific settings, including date categories, which dictate how they behave in transactions.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBY6 for financial accounting settings or VK11 for maintaining condition records, depending on the context of the error.
  
  If you continue to experience issues after following these steps, it may be helpful to consult with your SAP support team or refer to SAP documentation for more detailed guidance on condition types and date categories.