How To Fix MN585 - To date of condition record incompatible with period conditions

SAP Error Message - Details

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 585

• Message text: To date of condition record incompatible with period conditions

What causes this issue?

The "To" date &V2& of the main condition record is earlier than the
"From" date &V1& of the last period condition. In the case of rebate
arrangements with a settlement calendar, conditions cannot be
physically deleted once they have been created - they can only be
limited or flagged for logical deletion.

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?

Procedures:
Limit the current condition to the "From" date &V1& of the last period
condition.
If necessary, delete the provisions for income and the condition data
for the main condition as well as the period conditions you no longer
need. When the desired validity end date of the condition has been
reached, carry out partial or interim settlement accounting and then
set the deletion indicator.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN585 - To date of condition record incompatible with period conditions ?

  The SAP error message MN585, "To date of condition record incompatible with period conditions," typically occurs when there is a mismatch between the validity period of a condition record and the period conditions defined in the system. This error is often encountered in the context of pricing conditions, where the validity dates of the condition records do not align with the expected periods.
  Cause:
  
  Invalid Date Range: The "to date" of the condition record is set to a date that does not fall within the expected validity period for the pricing conditions.
  Period Conditions: The condition record may be defined with specific period conditions (e.g., monthly, quarterly) that require the dates to align with those periods.
  Overlapping Records: There may be overlapping condition records that conflict with the validity of the new record being created or modified.
  
  Solution:
  
  Check Condition Record Dates: Review the validity dates of the condition record in question. Ensure that the "to date" is set correctly and falls within the expected period.
  Adjust Period Conditions: If the condition record is meant to align with specific periods, adjust the dates to match the defined periods in the system.
  Delete or Modify Conflicting Records: If there are overlapping condition records, consider deleting or modifying them to resolve the conflict.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on setting up condition records and understanding period conditions.
  Use Transaction Codes: Utilize transaction codes like VK11 (Create Condition) or VK12 (Change Condition) to review and adjust the condition records as necessary.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, VK13 (Display Condition) for managing condition records.
  Condition Types: Understand the condition types being used and their specific requirements regarding validity periods.
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address known issues.
  User Roles and Authorizations: Ensure that you have the necessary authorizations to create or modify condition records, as restrictions may lead to errors.
  
  By following these steps, you should be able to resolve the MN585 error and successfully manage your condition records in SAP.