How To Fix /SAPCND/GENERATOR795 - Inconsistent entry in table &1 for condition table ID &2.

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPCND/GENERATOR -

• Message number: 795

• Message text: Inconsistent entry in table &1 for condition table ID &2.

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 /SAPCND/GENERATOR795 - Inconsistent entry in table &1 for condition table ID &2. ?

  The SAP error message /SAPCND/GENERATOR795 indicates that there is an inconsistency in the condition table specified in the error message. This typically occurs in the context of condition management, where the system is trying to access or generate data related to pricing conditions, and it finds an inconsistency in the underlying data structure.
  Cause:
  
  
  Inconsistent Data: The error usually arises when there are inconsistencies in the entries of the condition tables. This could be due to:
  
  Missing entries in the condition table.
  Corrupted or incomplete data.
  Changes made to the condition table structure that have not been properly updated in the database.
  
  
  
  Custom Development: If there are custom developments or modifications in the pricing procedure or condition tables, they might not align with the standard SAP behavior, leading to inconsistencies.
  
  
  Transport Issues: If the condition tables were transported from one system to another (e.g., from development to production), there might have been issues during the transport process that led to inconsistencies.
  
  
  Solution:
  
  
  Check Condition Table Entries: 
  
  Use transaction codes like VK13 (Display Condition) or VK12 (Change Condition) to check the entries in the condition table specified in the error message.
  Ensure that all necessary entries are present and correctly configured.
  
  
  
  Rebuild Condition Tables: 
  
  If the condition table is corrupted, you may need to rebuild it. This can often be done through the transaction SDBA (Database Utility) or by using specific SAP programs designed to regenerate condition tables.
  
  
  
  Check Custom Code: 
  
  Review any custom code or enhancements that may affect the condition tables. Ensure that they are correctly implemented and do not introduce inconsistencies.
  
  
  
  Transport Management: 
  
  If the issue arose after a transport, check the transport logs for errors. You may need to re-transport the condition tables or manually correct the inconsistencies.
  
  
  
  SAP Notes: 
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues related to this error message.
  
  
  
  Consult SAP Support: 
  
  If the issue persists and you cannot identify the cause, consider reaching out to SAP Support for assistance. Provide them with the error message details and any relevant logs or screenshots.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to condition management, such as VK11 (Create Condition), VK12, VK13, and VK31 (Maintain Condition Records).
  Condition Tables: Understand the structure and purpose of condition tables in SAP, as they are crucial for pricing and discount management.
  Debugging: If you have access to debugging tools, you can analyze the program flow to identify where the inconsistency is occurring.
  
  By following these steps, you should be able to identify and resolve the inconsistency causing the /SAPCND/GENERATOR795 error.