Do you have any question about this error?
Message type: E = Error
Message class: NAA - Subsequent settlement (Purchasing)
Message number: 643
Message text: Condition type &1 is used in calc. schema &2 in an exclusion group
Condition type &V1& is used in an exclusion group with reference to
calculation schema &V2& (usage &V3&, application &V4&).
During subsequent business volume updating, exclusion groups cannot be
taken into account correctly.
An unwanted update may take place.
Check whether the update was carried out correctly. If necessary, you
can determine the update transaction by using the analysis function.
SAP urgently recommends:
If you use the subsequent business volume update, or plan to do so in
future, you should not use exclusion groups in conjunction with
condition types of subsequent settlement. The option of being able to
carry out a subsequent business volume update should be retained.
If you use exclusion groups for condition types of subsequent
settlement, you cannot use the subsequent business volume update
functions. In this case, only carry out new compilations of business
volume date.
Otherwise, there may be unwanted effects, as the system does not carry
out a price determination (due to performance reasons).
As a result, exclusion indicators, exclusion groups, and "exclusive"
indicators must not be used.
Error message extract from SAP system. Copyright SAP SE.
NAA643
- Condition type &1 is used in calc. schema &2 in an exclusion group ?The SAP error message NAA643 indicates that a specific condition type (denoted as &1) is being used in a calculation schema (denoted as &2) that is part of an exclusion group. This typically occurs in the context of pricing or condition management in SAP, particularly in the Sales and Distribution (SD) module or the Materials Management (MM) module.
Cause:
- Exclusion Group: The condition type is part of an exclusion group, which means that it is set up to exclude certain conditions from being applied if other conditions are met. This is often used to prevent double discounts or conflicting pricing conditions.
- Incorrect Configuration: The condition type may have been incorrectly configured to be part of an exclusion group when it should not be, or it may be conflicting with other condition types that are also part of the same group.
- Usage in Calculation Schema: The calculation schema is designed to determine how pricing is calculated for a transaction. If a condition type is incorrectly included in an exclusion group, it can lead to conflicts in pricing calculations.
Solution:
- Review Configuration: Check the configuration of the condition type and the calculation schema in the SAP system. Ensure that the condition type is correctly assigned to the appropriate exclusion group.
- Go to the transaction code
V/06
(for pricing procedure) orV/07
(for condition types) to review the settings.- Modify Exclusion Group: If the condition type should not be part of the exclusion group, modify the exclusion group settings to remove it.
- Check Condition Records: Ensure that there are no conflicting condition records that might be causing the issue. You can check this using transaction codes like
VK13
(Display Condition) orVK11
(Create Condition).- Test Changes: After making changes, test the pricing procedure to ensure that the error no longer occurs and that the pricing is calculated correctly.
Related Information:
V/06
: Pricing Procedure ConfigurationV/07
: Condition Type ConfigurationVK11
: Create Condition RecordsVK13
: Display Condition RecordsIf the issue persists after following these steps, it may be beneficial to consult with an SAP functional consultant who specializes in pricing and condition management for further assistance.
Get instant SAP help. Start your 7-day free trial now.
NAA642
Update date was changed to date &1
What causes this issue? The update date is changed to date &V1&.System Response The update date is changed to date &V1&. The busines...
NAA641
Update date &1 is in a period for which settlement is already carried out
What causes this issue? Update date &V1& falls in a period (&V3& to &V4&) of arrangement &V2& for which settlement ac...
NAA644
The function "Suggest entries" is not available
What causes this issue? The function "Suggest entries" is not available for object type &V1& for object usage &V2&.System R...
NAA645
No entries could be selected
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.