How To Fix MN558 - Period condition record adopted but deletion flag set

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 558

• Message text: Period condition record adopted but deletion flag set

What causes this issue?

A period condition record was adopted in the extended rebate arrangement
&V1& but deactivated because the associated main condition record is
inactive (i.e. carries a deletion flag).
The deletion flags in the period condition record and the main condition
record differ.
This is not allowed.

System Response

Provided that no other messages were issued, the rebate arrangement has
been extended.

How to fix this error?

Check the conditions belonging to rebate arrangement &V1&.
Contact your system administrator. The above situation should not have
arisen and it is likely that a program error has occurred.
The period condition record of the rebate arrangement to be extended (
&V2&) has the (internal) number &V3&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN558 - Period condition record adopted but deletion flag set ?

  The SAP error message MN558 ("Period condition record adopted but deletion flag set") typically occurs in the context of condition records in the pricing procedure, particularly when dealing with period conditions in the SAP system. This message indicates that there is a condition record that has been adopted for a pricing condition, but it has a deletion flag set, which prevents it from being used in pricing calculations.
  Cause:
  
  Deletion Flag Set: The condition record has been marked for deletion. This can happen if the record was previously flagged for deletion in the condition maintenance transaction (e.g., using transaction code VK11, VK12, or VK13).
  Period Condition: The error often arises in the context of period conditions where the system expects a valid condition record for the specified period, but the flagged record cannot be used due to the deletion status.
  Data Inconsistency: There may be inconsistencies in the condition records, especially if changes were made to the pricing conditions or if the records were not properly maintained.
  
  Solution:
  
  
  Check Condition Records:
  
  Use transaction code VK13 to display the condition record in question.
  Verify if the deletion flag is indeed set. If it is, you will need to remove the deletion flag if the record is still valid and should be used.
  
  
  
  Remove Deletion Flag:
  
  If the condition record is still relevant, you can use transaction code VK12 to change the condition record and remove the deletion flag.
  Ensure that the record is correctly maintained and that all necessary fields are filled out.
  
  
  
  Create New Condition Record:
  
  If the condition record is no longer valid or needed, you may consider creating a new condition record that meets the requirements for the pricing procedure.
  
  
  
  Check Validity Period:
  
  Ensure that the validity period of the condition record aligns with the transaction date. If the record is outside the valid date range, it may not be adopted correctly.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP support team for specific guidance related to your configuration and business processes.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  VK11: Create Condition Record
  VK12: Change Condition Record
  VK13: Display Condition Record
  
  
  Condition Types: Understand the specific condition type that is causing the issue, as different condition types may have different rules and behaviors.
  Pricing Procedure: Familiarize yourself with the pricing procedure configuration in your SAP system, as it may provide insights into how conditions are processed.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or consult SAP Notes for any known issues or patches related to this error message.