How To Fix NAA629 - Access sequence &1 of condition type &2 contains an exclusive ID

NAA629 - Overview

• Message type: E = Error

• Message class: NAA - Subsequent settlement (Purchasing)

• Message number: 629

• Message text: Access sequence &1 of condition type &2 contains an exclusive ID

What causes this issue?

Access sequence &V1& of condition type &V2& contains an "exclusive"
indicator.
During subsequent business volume update, "exclusive" indicators cannot
always be taken into account correctly.

System Response

Unwanted updates may take place.

How to fix this error?

Check whether the update was carried out correctly. If necessary, you
can determine the update transaction by using the analysis function.

Procedure for System Administrators

SAP urgently recommends:
If you use the subsequent business volume update, or plan to do so in
future, you should not use "exclusive" indicators. The option of being
able to carry out a subsequent business volume update should be
retained.
If you use "exclusive" indicators, you cannot use the subsequent
business volume update functions. In this case, only carry out new
compilations of business volume data.
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.

Smart SAP Assistant

• What is the cause and solution for SAP error message NAA629 - Access sequence &1 of condition type &2 contains an exclusive ID ?

  The SAP error message NAA629 indicates that there is an issue with the access sequence of a condition type in the pricing procedure. Specifically, it states that the access sequence contains an exclusive ID, which means that the access sequence is set up in a way that it cannot be used in conjunction with other access sequences or condition types that have overlapping or conflicting criteria.
  
  Cause:
  
  Exclusive Access Sequence: The access sequence defined for the condition type is marked as exclusive. This means that when this access sequence is used, it cannot be combined with other access sequences that also have exclusive IDs.
  
  Configuration Issues: There may be a misconfiguration in the pricing procedure or the access sequence setup, leading to conflicts.
  Incorrect Condition Type Assignment: The condition type may be incorrectly assigned to a pricing procedure or may not be compatible with the other condition types in use.
  
  
  Solution:
  
  Review Access Sequence: Check the