How To Fix MN806 - Provisions for income for cond. type & not allowed (have been deleted)

SAP Error Message - Details

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 806

• Message text: Provisions for income for cond. type & not allowed (have been deleted)

What causes this issue?

The indicator "Provision" (provisions for accrued rebate income) has not
been set for condition type &V1&. You have nevertheless passed on
provisions for income in a data record relating to external supplier
business volumes.
This is not allowed.

System Response

The external supplier business volume data has been updated (except in
the case of a test run). However, the transferred data on the provisions
for income was not taken over but set to the value '0' instead.

How to fix this error?

Please look into this matter.
If necessary, maintain the indicator "Provision" for condition type &V1&
.
If the updating of the supplier business volume data has already been
carried out, you must post the provisions for accrued rebate income
retrospectively (i.e. you must create and post an external data file
containing just this data - no supplier business volumes or rebate
income).
Alternatively, you can cancel the update and repeat the latter after
changing the indicator.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN806 - Provisions for income for cond. type & not allowed (have been deleted) ?

  The SAP error message MN806 ("Provisions for income for condition type & not allowed (have been deleted)") typically occurs in the context of pricing and condition types in SAP, particularly when dealing with sales and distribution (SD) or materials management (MM) modules. This error indicates that a specific condition type that was expected to be used for pricing or revenue recognition has been deleted or is no longer valid.
  Cause:
  
  Deleted Condition Type: The condition type referenced in the error message has been deleted from the system. This could happen due to changes in pricing procedures or configuration adjustments.
  Incorrect Configuration: The pricing procedure may not be correctly configured to handle the condition type, leading to inconsistencies.
  Master Data Issues: The master data (like customer or material master) may not be set up correctly to include the necessary condition types.
  Document Type Settings: The document type being used may not be configured to allow the specific condition type.
  
  Solution:
  
  Check Condition Type: Verify if the condition type mentioned in the error message exists in the system. You can do this by navigating to the condition type configuration in the SAP system (Transaction code: V/06 for sales or M/06 for purchasing).
  Restore Condition Type: If the condition type has been deleted and is still needed, you may need to restore it or create a new condition type with the same settings.
  Review Pricing Procedure: Ensure that the pricing procedure assigned to the relevant sales document or purchasing document includes the condition type. You can check this in the configuration settings (Transaction code: V/08 for sales or M/8 for purchasing).
  Check Master Data: Review the master data for the relevant customer or material to ensure that it is set up to use the correct pricing procedure and condition types.
  Document Type Configuration: Check the configuration of the document type being used to ensure it allows the condition type in question.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as V/06, V/08, M/06, and M/8 for condition types and pricing procedures.
  SAP Notes: Check for any SAP Notes related to this error message for additional guidance or patches that may address the issue.
  Consult Documentation: Review SAP documentation or help files for detailed information on pricing procedures and condition types.
  Testing: After making changes, conduct thorough testing to ensure that the issue is resolved and that the pricing behaves as expected.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in the relevant module.