How To Fix EK022 - Term of payment &1 is inconsistent/not planned

EK022 - Overview

• Message type: E = Error

• Message class: EK - IS-U Accounts Receivable and Payable

• Message number: 022

• Message text: Term of payment &1 is inconsistent/not planned

What causes this issue?

Payment condition &v1& used in <DS:DE.KONDZAHL>payment condition</>
&v2& is inconsistently maintained or is not planned for use in utility
companies.

System Response

Processing is terminated.

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?

Check the specified payment conditions.
Note the following for this:
The day specifications (day limits) must be ascending and cover the
whole month.
In combination with day specification 0, no further entries may exist
for the payment condition (inequal to 0 with day specification),
because day limit 0 is interpreted as the last day of the month.
When entering several day limits, you must maintain an entry for day
limit 31.
You must propose a date type (base date). It is recommended that you
use the document date or entry date. When maintaining several day
limits, only one date type may be used for each payment condition.
In utility companies, only payment conditions with a one-level discount
specification may be used.
The payment conditions with discount specification must guarantee that
the calculated net due date is not before the discount due date.

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 EK022 - Term of payment &1 is inconsistent/not planned ?

  The SAP error message EK022, which states "Term of payment &1 is inconsistent/not planned," typically occurs in the context of purchasing documents, such as purchase orders or contracts. This error indicates that the payment terms specified in the document do not match the expected or configured payment terms in the system.
  Causes:
  
  Incorrect Payment Terms: The payment terms specified in the purchasing document may not be valid or may not exist in the system.
  
  Configuration Issues: The payment terms may not be properly configured in the system, or there may be inconsistencies in the configuration settings.
  Vendor Master Data: The vendor master data may not have the correct payment terms assigned, or the payment terms may not be compatible with the purchasing document.
  Document Type Restrictions: Certain document types may have restrictions on the payment terms that can be used.
  Missing Payment Terms in the Purchase Info Record: If the purchase info record does not have