How To Fix MN100 - Condition record (header) period &-& not copied

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 100

• Message text: Condition record (header) period &-& not copied

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN100 - Condition record (header) period &-& not copied ?

  The SAP error message MN100, which states "Condition record (header) period &-& not copied," typically occurs in the context of pricing or condition records in SAP. This error indicates that there is an issue with the copying of condition records, particularly related to the validity period of the condition records.
  Cause:
  
  Invalid Validity Period: The validity period of the condition record you are trying to copy does not match the period of the target document or the source document.
  Missing Condition Records: The condition records that are supposed to be copied do not exist or are not maintained for the specified period.
  Configuration Issues: There may be configuration issues in the pricing procedure or condition types that prevent the copying of the condition records.
  Document Type Restrictions: The document type you are working with may not allow the copying of certain condition records.
  
  Solution:
  
  Check Validity Period: Verify the validity period of the condition records in the source document and ensure that they match the target document's period.
  Maintain Condition Records: Ensure that the necessary condition records are created and maintained for the relevant period. You can do this by navigating to the condition records in the relevant transaction (e.g., VK11 for creating condition records).
  Review Configuration: Check the configuration of the pricing procedure and condition types to ensure that they are set up correctly to allow copying of condition records.
  Document Type Settings: Review the settings for the document type you are using to ensure that it allows the copying of the required condition records.
  Use Transaction Codes: Use transaction codes like VK13 (Display Condition) to check existing condition records and their validity periods.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), VK13 (Display Condition), and VK31 (Maintain Condition Records in Mass).
  Pricing Procedure: Understand the pricing procedure configuration in your SAP system, as it defines how condition records are processed.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to the MN100 error message.
  Documentation: Refer to SAP documentation or help files for detailed information on condition records and pricing procedures.
  
  By following these steps, you should be able to identify the cause of the MN100 error and implement the necessary solutions to resolve it.