How To Fix FICO1326 - Basis condition not found for markup condition for &1

FICO1326 - Overview

• Message type: E = Error

• Message class: FICO1 -

• Message number: 326

• Message text: Basis condition not found for markup condition for &1

What causes this issue?

You have created or processed a markup condition for which the system
could not find a suitable basis condition.
Use case 1: You have edited a condition group that has a markup
condition without a suitable basis condition.
Use case 2: You have triggered a mixed operation of multiple condition
lists, for example, by activating a multi-tiered product price list that
has a markup condition without a suitable basis condition.
This constellation can mean that if you also use conditions for a
specific contract, the system cannot find a basis condition to match the
markup condition that you specify.
Example 1
In a business partner pricing agreement for business partner G, you
created a markup condition for credit interest in EUR. However, this
pricing agreement does not contain a basis condition for credit interest
in EUR. The system issues a warning message when you save the pricing
agreement. Product P1 has a product pricing list in which there is a
basis condition for credit interest in EUR. Product P2 also has a
product pricing list, but this does not contain a basis condition. If
you create a contract for business partner G and product P1, the system
applies the markup to the basis condition that is suitable. If you
create a contract for business partner G and product P2, an error
occurs. The markup cannot be used.
Example 2
In a business partner pricing agreement for business partner G2, you
created a cross-currency credit interest basis condition, and a credit
interest markup condition in EUR. The system issues the warning when you
save the pricing agreement. If you create a contract for partner G2 and
currency EUR, the system uses the markup. When you create a contract for
partner G2 and currency USD, an error occurs and the system cannot use
the markup.

System Response

The two situations above do not necessarily cause errors because pricing
involves multitiered merging operations where the system can still
assign a suitable basis condition for the markup condition. However, the
system cannot determine this at the time of checking. Therefore, the
system issues this warning to inform you of the situation described
above.
If this constellation of errors occurs when you use the conditions for a
specific contract, the system does not use the markups.

How to fix this error?

Ensure that the system can find a basis condition for the markup
condition when you use the conditions, for example, when you create a
contract. After this, you can ignore the error.

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 FICO1326 - Basis condition not found for markup condition for &1 ?

  The SAP error message FICO1326, which states "Basis condition not found for markup condition for &1," typically occurs in the context of pricing and condition records in the SAP system, particularly within the Financial Accounting (FI) and Controlling (CO) modules. This error indicates that the system is unable to find a basis condition for a markup condition that is required for pricing calculations.
  
  Cause:
  
  
  Missing Condition Records: The most common cause of this error is that the necessary condition records for the pricing procedure are not maintained in the system. This could be due to missing entries in the condition tables or incorrect configuration of the pricing procedure.
  
  
  Incorrect Configuration: The pricing procedure may not be correctly configured to include the necessary condition types or may not be linked properly to the relevant sales document types or transaction types.
  
  
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data that prevent