How To Fix MN013 - Period-sp. conditions created without condition units (please remaintain)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 013

• Message text: Period-sp. conditions created without condition units (please remaintain)

What causes this issue?

Period condition records exist for quantity-dependent conditions with
missing units of measure.

System Response

The system will not allow you to save inconsistent data.

How to fix this error?

Branch directly to the maintenance of period condition records and
process the relevant condition records.
Maintain the settlement material on the detail screen of the main
condition.
Branch to the maintenance of period conditions.
In this case, the system will suggest a condition unit that is valid
for the settlement material, provided that one has been maintained in
the material master record.
Adopt or change this condition unit.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN013 - Period-sp. conditions created without condition units (please remaintain) ?

  The SAP error message MN013 ("Period-sp. conditions created without condition units (please remaintain)") typically occurs in the context of pricing and conditions in SAP, particularly when dealing with period-specific conditions in pricing procedures. This error indicates that there are conditions that have been created without specifying the necessary condition units, which are essential for the correct calculation of pricing.
  Cause:
  
  
  Missing Condition Units: The primary cause of this error is that the condition records for certain pricing conditions do not have the required condition units defined. Condition units are necessary for the system to understand how to apply the pricing conditions over a specific period.
  
  
  Incorrect Configuration: There may be an issue with the configuration of the pricing procedure or the condition types being used. If the condition type is set up to require units but they are not provided, this error will occur.
  
  
  Data Entry Errors: During the creation or maintenance of condition records, users may inadvertently leave out the condition units.
  
  
  Solution:
  
  
  Maintain Condition Records: 
  
  Go to the transaction code VK11 (Create Condition) or VK12 (Change Condition) to maintain the condition records.
  Ensure that the condition units are specified for the relevant condition types. This may involve entering the correct unit of measure (e.g., pieces, kilograms, etc.) for the conditions.
  
  
  
  Check Pricing Procedure:
  
  Review the pricing procedure assigned to the relevant sales document type. Ensure that the condition types that are supposed to have units are correctly configured.
  You can check this in the transaction code V/08 (Maintain Pricing Procedures).
  
  
  
  Review Condition Type Settings:
  
  Use transaction code V/06 to check the settings of the condition types. Ensure that the "Condition Unit" field is correctly set up for the condition types that are causing the error.
  
  
  
  Recreate Condition Records: If the condition records are corrupted or incorrectly set up, it may be necessary to delete and recreate them with the correct settings.
  
  
  Consult Documentation: If you are unsure about the correct settings, refer to SAP documentation or consult with your SAP functional consultant for guidance on the specific condition types and their requirements.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VK11 - Create Condition
  VK12 - Change Condition
  VK13 - Display Condition
  V/08 - Maintain Pricing Procedures
  V/06 - Maintain Condition Types
  
  
  
  Condition Types: Understand the specific condition types being used in your pricing procedure and their requirements regarding condition units.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on configuration.
  
  
  By following these steps, you should be able to resolve the MN013 error and ensure that your pricing conditions are correctly maintained in SAP.