How To Fix 42079 - &1 &2 is excluded

42079 - Overview

• Message type: E = Error

• Message class: 42 - Information Workbench

• Message number: 079

• Message text: &1 &2 is excluded

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.

42079 - Details

• The SAP error message "42079 &1 &2 is excluded" typically occurs in the context of pricing or condition records in SAP. This error indicates that a specific condition record (like a pricing condition) is excluded from the pricing procedure for a particular transaction or document.
  
  Cause:
  
  Condition Exclusion: The condition type specified (represented by &1) is excluded for the specific transaction or document type (represented by &2). This can happen due to configuration settings in the pricing procedure or condition records.
  Condition Records Not Maintained: The condition records for the specified condition type may not be maintained or are set to be inactive.
  Pricing Procedure Configuration: The pricing procedure may not be set up to include the specified condition type for the relevant sales document type or purchasing document type.
  
  
  Solution:
  
  
  Check Condition Records:
  
  Go to the transaction code VK13 (Display Condition) or VK11 (Create Condition) to check if the condition records for the specified condition type