How To Fix 60536 - Condition date must be after &

SAP Error Message - Details

• Message type: E = Error

• Message class: 60 - Real Estate

• Message number: 536

• Message text: Condition date must be after &

What causes this issue?

A validity date is assigned to every condition item. This date must be
after the &V1& (rental start or valid-as-from date in the condition
header).

System Response

You must make a correct entry.

How to fix this error?

Enter a validity date which is after the &V1&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 60536 - Condition date must be after & ?

  The SAP error message 60536, which states "Condition date must be after &," typically occurs in the context of pricing conditions in SAP, particularly when working with sales documents, purchase orders, or other transactions that involve condition records.
  Cause:
  This error arises when the condition date specified in a pricing condition is not valid because it is set to a date that is either the same as or earlier than a reference date (the "&" in the message). The reference date could be the validity start date of the condition record or the document date of the transaction.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Condition Records:
  
  Go to the condition records for the relevant pricing condition (using transaction codes like VK11, VK12, or VK13).
  Verify the validity dates of the condition records. Ensure that the condition date you are trying to use is after the validity start date of the condition record.
  
  
  
  Adjust the Condition Date:
  
  If you are entering a condition date manually, make sure to set it to a date that is after the reference date indicated in the error message.
  
  
  
  Review Document Dates:
  
  Check the document date of the sales order, purchase order, or other relevant documents. Ensure that the condition date aligns with the document date and is valid according to the pricing procedure.
  
  
  
  Consult Pricing Procedure:
  
  Review the pricing procedure assigned to the document type. Ensure that the condition types and their sequence are correctly configured to avoid conflicts with date validations.
  
  
  
  Test with Different Dates:
  
  If you are unsure about the correct date, try using a future date to see if the error persists.
  
  
  
  Check for Custom Logic:
  
  If there are any custom enhancements or user exits that might affect the pricing logic, review them to ensure they are not causing the issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) for managing condition records.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation on pricing procedures and condition records for a deeper understanding of how dates are managed in pricing.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.