How To Fix NAA678 - Do not use exclusion indicators for condition types relevant to rebates


SAP Error Message - Details

  • Message type: E = Error

  • Message class: NAA - Subsequent settlement (Purchasing)

  • Message number: 678

  • Message text: Do not use exclusion indicators for condition types relevant to rebates

  • Show details Hide details
  • What causes this issue?

    same long text as message NAA 679, similar to 677
    Subsequent Settlement contains functionality for the subsequent updating
    of business volumes. For reasons of performance, these functions do not
    use price determination, they only simulate price determination.
    In this process, conditions (calculation schema, access sequence) are
    checked as long as internal fields of price determination are not used.
    However, it is not possible to take account of exclusive indicators, or
    condition exclusion groups and exclusion indicators.
    From a technical point of view, exclusion indicators are implemented via
    a condition using internal Price Determination field KOMP-KZNEP. In the
    subsequent business volume update, the internal field cannot be set
    correctly. It can therefore be assumed that the condition check carried
    out in the subsequent update of business volumes may lead to an
    incorrect result.

    System Response

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    How to fix this error?

    It is very difficult to get an overview of the individual
    constellations. SAP therefore urgently recommends that (for access
    sequences relevant to volume-based rebate) you do not use exclusive
    indicators or condition exclusion groups or exclusion indicators.
    Otherwise, the system may carry out unwanted updates.
    The "subsequent business volume update" function does not permit the
    functions "exclusive indicator", "condition exclusion group" and
    "exclusion indicator" (that is, you must use either the subseqeuent
    business volume update or the exclusive indicator/condition exclusion
    group/exclusion indicator)
    SAP urgently recommends that you do not use the "subsequent business
    volume update" function.
    Tip:
    A condition of type K001 with 5% for all materials from supplier
    "Supplier1", but only 3% for materials "Mat1" and "Mat2", can be mapped
    as follows: Materials "Mat1" and "Mat2" are assigned to settlement group
    "A1". Two condition records are entered:
    K001 Supplier1 5%
    K001 Supplier1/A1 -2%
    This solution means you avoid using exclusive indicators but requires
    two condition records.

    Procedure for System Administrators


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message NAA678 - Do not use exclusion indicators for condition types relevant to rebates ?

    The SAP error message NAA678, which states "Do not use exclusion indicators for condition types relevant to rebates," typically occurs in the context of pricing and rebate agreements in SAP. This error indicates that there is a configuration issue related to the use of exclusion indicators for certain condition types that are associated with rebate processing.

    Cause:

    The error is caused by the use of exclusion indicators on condition types that are relevant to rebates. In SAP, exclusion indicators are used to determine whether certain conditions should be excluded from pricing calculations. However, for condition types that are specifically designed for rebates, using exclusion indicators can lead to inconsistencies and incorrect calculations in rebate processing.

    Solution:

    To resolve this error, you should follow these steps:

    1. Identify the Condition Type: Determine which condition type is causing the error. This can usually be found in the pricing procedure or the specific transaction where the error occurred.

    2. Check Configuration: Go to the SAP configuration settings for pricing (Transaction code: SPRO) and navigate to the relevant section for condition types.

    3. Review Exclusion Indicators:

      • Open the condition type in question and check the settings for exclusion indicators.
      • Ensure that the condition type is not marked with an exclusion indicator if it is relevant to rebates.
    4. Adjust Condition Type Settings: If the condition type is indeed relevant to rebates, remove any exclusion indicators that may have been set. This can typically be done in the condition type configuration screen.

    5. Test the Changes: After making the necessary adjustments, test the pricing procedure again to ensure that the error no longer occurs and that rebate calculations are functioning correctly.

    6. Consult Documentation: If you are unsure about the implications of changing the configuration, consult SAP documentation or reach out to your SAP support team for guidance.

    Related Information:

    • Rebate Processing: Understand how rebates work in SAP, including the different types of rebate agreements (e.g., volume rebates, customer-specific rebates) and how they interact with pricing conditions.
    • Pricing Procedure: Familiarize yourself with how pricing procedures are set up in SAP, including the sequence of condition types and how they are processed during sales order creation.
    • SAP Notes: Check for any relevant SAP Notes that may provide additional insights or updates related to this error message.

    By following these steps, you should be able to resolve the NAA678 error and ensure that your rebate processing works as intended.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant