How To Fix 6A564 - Condition type &1 does not exist at contract start (basic rent)

SAP Error Message - Details

• Message type: E = Error

• Message class: 6A - Real estate messages rent adjustment

• Message number: 564

• Message text: Condition type &1 does not exist at contract start (basic rent)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 6A564 - Condition type &1 does not exist at contract start (basic rent) ?

  The SAP error message "6A564 Condition type &1 does not exist at contract start (basic rent)" typically occurs in the context of contract management, particularly in the Real Estate Management (RE-FX) module. This error indicates that the system is unable to find a specified condition type (in this case, related to basic rent) at the start of a contract.
  Cause:
  
  Missing Condition Type: The specified condition type (represented by &1) is not defined in the system for the contract start date.
  Incorrect Configuration: The condition type may not be properly configured in the pricing procedure or may not be assigned to the relevant contract type.
  Contract Start Date Issues: The contract start date may not align with the validity period of the condition type.
  Data Entry Errors: There may be a typo or incorrect entry in the contract setup that references the condition type.
  
  Solution:
  
  
  Check Condition Type Configuration:
  
  Go to the configuration settings in SAP and verify that the condition type exists and is correctly set up for the relevant pricing procedure.
  Ensure that the condition type is valid for the contract type you are working with.
  
  
  
  Review Contract Start Date:
  
  Ensure that the contract start date is within the validity period of the condition type. If the condition type is not valid on the start date, you may need to adjust the dates or create a new condition type.
  
  
  
  Assign Condition Type:
  
  If the condition type is missing, you may need to create it or assign it to the relevant contract type in the pricing procedure.
  
  
  
  Check for Data Entry Errors:
  
  Review the contract details for any typos or incorrect entries that may be causing the system to look for a non-existent condition type.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on managing condition types in your version of SAP.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like RECN (for contract management) or SPRO (for configuration) to access the relevant settings.
  Condition Types: Familiarize yourself with the standard condition types used in your organization and their configurations.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify and resolve the issue related to the error message "6A564 Condition type &1 does not exist at contract start (basic rent)."