How To Fix VT660 - Access sequence &1 inconsistent; target field &3 missing in access &2

SAP Error Message - Details

• Message type: E = Error

• Message class: VT - Vertriebstabellen

• Message number: 660

• Message text: Access sequence &1 inconsistent; target field &3 missing in access &2

What causes this issue?

Access sequence &V1& is inconsistent. Target field &V3& is missing in
access &V2&.

System Response

The changed data has not been saved, because this action was cancelled.

How to fix this error?

Correct the inconsistent access and save the data again.
To correct the inconsistency, first delete the inconsistent access and
then add it again.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VT660 - Access sequence &1 inconsistent; target field &3 missing in access &2 ?

  The SAP error message VT660 indicates that there is an inconsistency in the access sequence configuration for a condition type in the pricing procedure. Specifically, it means that a target field that is expected to be present in the access sequence is missing.
  Cause:
  
  Missing Target Field: The error typically arises when the access sequence is configured to use a target field that is not defined in the access sequence. This can happen if the access sequence was modified, or if the condition type was changed without updating the access sequence accordingly.
  Incorrect Configuration: There may be a misconfiguration in the access sequence or the condition records that reference it.
  Transport Issues: If the access sequence was transported from one system to another (e.g., from development to production), it may not have been transported correctly, leading to inconsistencies.
  
  Solution:
  
  
  Check Access Sequence Configuration:
  
  Go to the transaction code V/07 (for access sequences) and check the access sequence mentioned in the error message.
  Ensure that all required fields are correctly defined in the access sequence.
  
  
  
  Verify Target Fields:
  
  Check the target fields that are supposed to be included in the access sequence. Make sure that the field mentioned in the error message is indeed part of the access sequence.
  
  
  
  Adjust Condition Type:
  
  If the condition type has been changed, ensure that the access sequence is updated to reflect these changes. You can do this in the transaction code V/06 (for condition types).
  
  
  
  Recreate Access Sequence:
  
  If the access sequence is severely misconfigured, consider recreating it from scratch, ensuring that all necessary fields are included.
  
  
  
  Transport Check:
  
  If the issue arose after a transport, check the transport logs to ensure that all objects related to the access sequence were transported correctly.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific condition type and access sequence for any additional guidance or known issues.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  V/06: Condition Types
  V/07: Access Sequences
  V/08: Condition Records
  
  
  SAP Notes: Check for any relevant SAP Notes that might address known issues with specific condition types or access sequences.
  Debugging: If the issue persists, consider debugging the pricing procedure to identify where the inconsistency occurs.
  
  By following these steps, you should be able to resolve the VT660 error and ensure that your access sequence is correctly configured.