How To Fix VK817 - No block has been marked.

SAP Error Message - Details

• Message type: E = Error

• Message class: VK - Pflege und Bearbeitung von Konditionen

• Message number: 817

• Message text: No block has been marked.

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 VK817 - No block has been marked. ?

  The SAP error message VK817 "No block has been marked" typically occurs in the context of pricing and condition records in SAP. This error is often encountered when trying to process or change condition records in transaction codes related to pricing, such as VK11, VK12, or VK13.
  Cause:
  The error message VK817 usually indicates that there are no condition records selected for processing. This can happen for several reasons:
  
  No Condition Records Exist: There may be no existing condition records for the specified condition type, material, or customer.
  Selection Criteria: The selection criteria used to retrieve condition records may not match any existing records.
  User Permissions: The user may not have the necessary permissions to view or modify the condition records.
  Incorrect Transaction: The transaction being used may not be appropriate for the action being attempted.
  
  Solution:
  To resolve the VK817 error, you can take the following steps:
  
  
  Check Condition Records:
  
  Use transaction code VK13 (Display Condition) to check if any condition records exist for the specified condition type, material, or customer.
  Ensure that you are using the correct selection criteria.
  
  
  
  Create or Modify Records:
  
  If no records exist, you may need to create new condition records using transaction code VK11 (Create Condition).
  If you need to modify existing records, ensure you are using VK12 (Change Condition) and that the records are available for editing.
  
  
  
  Review User Permissions:
  
  Ensure that your user role has the necessary permissions to access and modify condition records. You may need to contact your SAP administrator for assistance.
  
  
  
  Check Transaction Type:
  
  Make sure you are using the correct transaction for the action you want to perform. For example, if you are trying to change a record, ensure you are in the change mode (VK12) and not in display mode (VK13).
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to pricing and condition records for additional guidance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  VK11: Create Condition
  VK12: Change Condition
  VK13: Display Condition
  
  
  Condition Types: Understand the specific condition types you are working with, as they can affect how records are created and modified.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP community forums for further assistance.