How To Fix RESCAJ021 - &1: condition type could not be read in Customizing

SAP Error Message - Details

• Message type: E = Error

• Message class: RESCAJ - Adjustment for Conditions of SCS

• Message number: 021

• Message text: &1: condition type could not be read in Customizing

What causes this issue?

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

System Response

How to fix this error?

Procedure for System Administrators

INCLUDE REFX_CA_PROT_CUST_MESSAGE 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 RESCAJ021 - &1: condition type could not be read in Customizing ?

  The SAP error message RESCAJ021 indicates that a condition type could not be read in Customizing. This typically occurs in the context of pricing or condition records in SAP, particularly when working with the SAP Sales and Distribution (SD) module or the SAP Materials Management (MM) module.
  Cause:
  
  Missing Customizing Settings: The condition type may not be defined in the Customizing settings. This can happen if the condition type was deleted or not properly configured.
  Authorization Issues: The user may not have the necessary authorizations to access the condition type or the related customizing settings.
  Transport Issues: If the condition type was recently transported from another system (e.g., from a development to a production environment), there may have been issues during the transport process.
  Incorrect Configuration: The condition type may be incorrectly configured or linked to the wrong pricing procedure.
  
  Solution:
  
  
  Check Customizing Settings:
  
  Go to the SAP Customizing Implementation Guide (SPRO).
  Navigate to the relevant area (e.g., Sales and Distribution > Basic Functions > Pricing > Pricing Control).
  Verify that the condition type in question is defined and properly configured.
  
  
  
  Review Condition Records:
  
  Use transaction codes like VK11 (Create Condition) or VK12 (Change Condition) to check if the condition records exist for the condition type.
  Ensure that the condition records are maintained correctly.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the condition type and related customizing settings. This may involve checking user roles and authorizations.
  
  
  
  Transport Management:
  
  If the condition type was recently transported, check the transport logs for any errors or issues.
  Ensure that all necessary objects related to the condition type were included in the transport request.
  
  
  
  Check Pricing Procedure:
  
  Verify that the condition type is correctly assigned to the pricing procedure being used in the sales document or purchase order.
  Go to the pricing procedure configuration and ensure that the condition type is included in the correct sequence.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO, VK11, VK12, VK13 (Display Condition), and V/06 (Maintain Pricing Procedures).
  SAP Notes: Check for any SAP Notes related to the specific condition type or error message for additional guidance or patches.
  Documentation: Review SAP documentation or help files for detailed information on condition types and pricing procedures.
  
  If the issue persists after checking these areas, it may be beneficial to consult with your SAP Basis or functional team for further investigation.