How To Fix FICO1400 - Condition types &1 and &3 have different periods of use

SAP Error Message - Details

• Message type: E = Error

• Message class: FICO1 -

• Message number: 400

• Message text: Condition types &1 and &3 have different periods of use

What causes this issue?

A problem occurred while editing a condition from the category "Amount
Limits with Period of Use" (condition type &V1&). A condition of this
condition type <DS:DE.FICO_ORELCONDTYPE>refers to</> one or more
conditions of condition type &V3&. A period component, a condition with
condition type &V1&, and a period component of a condition of condition
type &V3& coincide (at least partially). In this case, the affected
period components must have the same period of use. The period component
of the amount limit condition has the period of use &V2&, while the
period component of the reference condition has the period of use &V4&.

System Response

The setting described above is not permitted.

How to fix this error?

Change one of the vaidity periods (valid-from and/or valid-to date) or
one of the periods of use.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FICO1400 - Condition types &1 and &3 have different periods of use ?

  The SAP error message FICO1400 indicates that there is a conflict between the periods of use for two condition types in the Financial Accounting (FI) and Controlling (CO) modules. This typically occurs when you are trying to process a transaction that involves multiple condition types that have been defined with different validity periods.
  Cause:
  The error arises when:
  
  Two condition types (e.g., &1 and &3) are being used in a transaction, but they have different periods of validity defined in the system.
  The system checks the validity of these condition types and finds that they do not align, leading to the error message.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Condition Type Configuration:
  
  Go to the configuration settings for the condition types involved. You can do this by navigating to the relevant customizing transaction (e.g., SPRO).
  Look for the condition types in the pricing procedure or the relevant configuration area and check their validity periods.
  
  
  
  Align Validity Periods:
  
  If the condition types are supposed to be used together, ensure that their validity periods are aligned. You may need to adjust the start and end dates for one or both condition types to ensure they match.
  
  
  
  Review Transaction Data:
  
  Check the transaction data that is causing the error. Ensure that the condition types are being applied correctly and that there are no discrepancies in the data being processed.
  
  
  
  Consult Documentation:
  
  Review any documentation or notes related to the specific condition types and their intended use. This can provide insights into how they should be configured.
  
  
  
  Testing:
  
  After making changes, perform tests to ensure that the error no longer occurs and that the transaction processes correctly.
  
  
  
  Seek Help from SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP support or consulting with an SAP expert who can provide further assistance.
  
  
  
  Related Information:
  
  Condition Types: In SAP, condition types are used to define how pricing and discounts are calculated. They can have various attributes, including validity periods.
  Pricing Procedure: The pricing procedure in SAP defines the sequence in which condition types are applied during transaction processing.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) to manage condition types effectively.
  
  By following these steps, you should be able to identify the root cause of the FICO1400 error and implement a solution to resolve it.