How To Fix VK795 - KONH and KONP also checked

SAP Error Message - Details

• Message type: E = Error

• Message class: VK - Pflege und Bearbeitung von Konditionen

• Message number: 795

• Message text: KONH and KONP also checked

What causes this issue?

The check selected requires data that can only be procured via tables
KONH and KONP. For this reason, the system also carries out consistency
checks for these tables.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VK795 - KONH and KONP also checked ?

  The SAP error message VK795 typically relates to issues with condition records in pricing, specifically when dealing with the KONH (Condition Header) and KONP (Condition Item) tables. This error can occur in various scenarios, such as during pricing determination in sales orders, quotations, or billing documents.
  Cause of VK795 Error
  
  
  Missing Condition Records: The error often indicates that the system cannot find the necessary condition records for the pricing procedure being executed. This could be due to missing or incorrectly maintained condition records in the relevant pricing tables.
  
  
  Incorrect Condition Types: If the condition types used in the pricing procedure are not set up correctly or are not relevant for the transaction, this can lead to the VK795 error.
  
  
  Inconsistent Data: There may be inconsistencies in the data between the KONH and KONP tables, such as missing entries or mismatched keys.
  
  
  Pricing Procedure Configuration: The pricing procedure may not be configured correctly, leading to issues in how conditions are applied.
  
  
  Access Sequence Issues: The access sequence defined for the condition type may not be able to find the appropriate records due to incorrect configuration or missing access entries.
  
  
  Solutions to VK795 Error
  
  
  Check Condition Records: 
  
  Use transaction code VK11 to check if the necessary condition records exist for the relevant condition types. If they are missing, create them.
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure assigned to the sales document type or billing type. Ensure that the condition types are correctly configured and relevant for the transaction.
  
  
  
  Access Sequence Verification:
  
  Verify the access sequence for the condition types involved. Ensure that the access sequence is correctly set up to retrieve the necessary condition records.
  
  
  
  Data Consistency Check:
  
  Use transaction codes like SE16 to check the KONH and KONP tables for any inconsistencies. Ensure that the keys match and that there are no missing entries.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the pricing procedure to identify where the error occurs. This can provide insights into which condition records are being accessed and why they are failing.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific error message for any additional guidance or known issues.
  
  
  
  Related Information
  
  
  Transaction Codes:
  
  VK11: Create Condition Record
  VK12: Change Condition Record
  VK13: Display Condition Record
  V/06: Maintain Pricing Procedures
  V/07: Maintain Access Sequences
  
  
  
  Tables:
  
  KONH: Condition Header
  KONP: Condition Item
  
  
  
  SAP Notes: Check SAP Notes for any updates or patches related to pricing issues or the VK795 error.
  
  
  By following these steps, you should be able to identify and resolve the VK795 error in SAP. If the problem persists, consider reaching out to your SAP support team for further assistance.