How To Fix 6A560 - Condition type &1 does not exist for target object on date &2

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 560

• Message text: Condition type &1 does not exist for target object on date &2

What causes this issue?

You are trying to copy the amount of the condition item &V1& on date
&V2& from a source object to a target object (rental agreement or
rental unit). However this condition type does not exist for the target
object on this date.

System Response

The condition item will not be transferred.

How to fix this error?

If you still want to carry out the transfer, set the indicator
"Generate new conditions on target object" in the initial screen.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 6A560 - Condition type &1 does not exist for target object on date &2 ?

  The SAP error message 6A560 indicates that a specific condition type does not exist for a target object on a given date. This error typically arises in the context of pricing, where the system is unable to find the specified condition type for the relevant transaction or document.
  Cause:
  
  Missing Condition Type: The condition type specified in the error message is not defined in the system for the target object (e.g., sales order, purchase order, etc.) on the specified date.
  Date Validity: The condition type may exist but is not valid for the date mentioned in the error message. Condition records in SAP can have validity periods, and if the date falls outside this range, the condition type will not be found.
  Configuration Issues: There may be configuration issues in the pricing procedure or condition records that prevent the system from recognizing the condition type.
  Master Data Issues: The relevant master data (like customer, material, or vendor) may not be set up correctly, leading to the absence of the condition type.
  
  Solution:
  
  
  Check Condition Type Configuration:
  
  Go to the transaction code V/06 (for sales) or M/06 (for purchasing) to check if the condition type is defined in the pricing procedure.
  Ensure that the condition type is included in the relevant pricing procedure for the document type you are working with.
  
  
  
  Review Condition Records:
  
  Use transaction code VK11 (for sales) or VK31 (for purchasing) to check if condition records exist for the specified condition type and target object.
  Ensure that the condition records are valid for the date mentioned in the error message.
  
  
  
  Check Validity Dates:
  
  Verify the validity dates of the condition records. If the condition type is valid only for a specific period, ensure that the date you are working with falls within that range.
  
  
  
  Master Data Verification:
  
  Check the master data (customer, vendor, material) to ensure that it is correctly set up and that the relevant pricing information is maintained.
  
  
  
  Consult with Configuration Team:
  
  If you are unable to resolve the issue, consult with your SAP configuration team to ensure that the pricing procedure and condition types are set up correctly.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  V/06: Maintain Pricing Procedures
  VK11: Create Condition Records
  VK31: Create Condition Records for Purchasing
  V/02: Change Pricing Procedure
  
  
  Documentation: Refer to SAP Help documentation for detailed information on pricing procedures and condition types.
  SAP Notes: Check for any relevant SAP Notes that might address known issues related to this error message.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary corrections to resolve it.