How To Fix VK396 - Condition type &1 is obsolete. Condition records are not maintainable.

SAP Error Message - Details

• Message type: E = Error

• Message class: VK - Pflege und Bearbeitung von Konditionen

• Message number: 396

• Message text: Condition type &1 is obsolete. Condition records are not maintainable.

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 VK396 - Condition type &1 is obsolete. Condition records are not maintainable. ?

  The SAP error message VK396 indicates that a specific condition type is considered obsolete, meaning that it is no longer valid for use in pricing or other related processes. This can occur for various reasons, such as changes in business processes, updates to the pricing procedure, or the condition type being replaced by a new one.
  Cause:
  
  Obsolescence of Condition Type: The condition type has been marked as obsolete in the system, which means it cannot be used for new condition records.
  Configuration Changes: Changes in the pricing procedure or configuration settings may have led to the condition type being deprecated.
  Versioning Issues: The condition type may have been replaced by a newer version or a different condition type altogether.
  
  Solution:
  To resolve the VK396 error, you can take the following steps:
  
  
  Check Condition Type Configuration:
  
  Go to the transaction code SPRO (SAP Reference IMG).
  Navigate to Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Types.
  Look for the condition type mentioned in the error message and check its status. If it is marked as obsolete, you will need to identify a suitable replacement.
  
  
  
  Update Pricing Procedure:
  
  If the condition type is obsolete, you may need to update the pricing procedure to remove the obsolete condition type and replace it with a valid one.
  Go to Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Pricing Procedures and make the necessary adjustments.
  
  
  
  Create New Condition Records:
  
  If the condition type is obsolete, you will not be able to maintain records for it. Instead, create new condition records using a valid condition type.
  Use transaction code VK11 to create new condition records with the appropriate condition type.
  
  
  
  Consult Documentation:
  
  Review any documentation or release notes related to your SAP version to understand why the condition type was marked as obsolete and what alternatives are recommended.
  
  
  
  Contact SAP Support:
  
  If you are unsure about the changes or need further assistance, consider reaching out to SAP support or your internal SAP team for guidance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  VK11: Create Condition Records
  VK12: Change Condition Records
  VK13: Display Condition Records
  SPRO: Access the SAP Reference IMG for configuration.
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional information or fixes related to the condition type in question.
  
  
  Testing: After making changes, ensure to test the pricing procedure to confirm that the new condition types are functioning as expected.
  
  
  By following these steps, you should be able to address the VK396 error and ensure that your pricing processes continue to function smoothly.