How To Fix AJ221 - Rate &1 permissibility does not correspond to permissibility for &2

AJ221 - Overview

• Message type: E = Error

• Message class: AJ - Billing program

• Message number: 221

• Message text: Rate &1 permissibility does not correspond to permissibility for &2

What causes this issue?

The following combinations of validity of rate and rate type are
allowed:
Val. rate type,,Valid rate
Register,,<DS:DE.USE_REGISTER>Register,</> <DS:DE.USE_FACTS>Facts</>
Device,,<DS:DE.USE_DEVICE>Device,</> <DS:DE.USE_FACTS>Facts</>
Facts,,<DS:DE.USE_FACTS>Facts</>
The validity of rate &v1& and rate type &v2& does not correspond to one
of the allowed combinations.

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?

Select a suitable rate.
INCLUDE ISU_WEITEREINFOS OBJECT DOKU ID TX
INCLUDE ISU_BESTBILLING_SCHEMA_INC OBJECT DOKU ID TX.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AJ221 - Rate &1 permissibility does not correspond to permissibility for &2 ?

  The SAP error message AJ221 indicates that there is a mismatch in the permissibility of a rate for a specific condition type. This typically occurs in the context of pricing or cost calculations in SAP, particularly in the areas of sales and distribution (SD) or materials management (MM).
  
  Cause:
  The error message AJ221 is triggered when the system detects that the rate (e.g., a pricing condition) being applied does not meet the permissibility criteria defined for the specific condition type. This can happen due to several reasons, including:
  
  Incorrect Configuration: The condition type may not be configured correctly in the pricing procedure.
  Missing or Incorrect Master Data: The master data (such as customer master, material master, or vendor master) may not have the necessary settings or information that aligns with the rate being applied.
  Inconsistent Condition Records: There may be inconsistencies in the condition records that define the rates for specific combinations of key fields