How To Fix VH602 - Maximum no. of accesses in the access sequences being used

SAP Error Message - Details

• Message type: E = Error

• Message class: VH - SD pricing

• Message number: 602

• Message text: Maximum no. of accesses in the access sequences being used

Accesses in access sequences
Each access in an access sequence means reading the background
condition table. Possibly, all access sequences must be carried out.
Alternative
Smaller pricing procedures
If records in a condition table used by an access table only apply to
certain customers/materials, you could use several smaller pricing
procedures instead of a single, general pricing procedure. These
pricing procedures could be made customer-specific or transaction-
specific (order type, billing type, own customer determination
procedure, own document determination procedure)
Using the preconditions
If you know the preconditions governing the condition records, then you
can use this knowledge to avoid unnecessary accesses to the condition
tables (inquiry from customer master fields, material master fields,
poss. use of the additional information in the customer master and the
material master).
Note:
This increases the amount data maintenance carried out in Customizing.
System modification, Customizing
<DS:SIMG.SIMG_XXMENUOLSDMODAX> New fields for pricing</>
<DS:CHAP.SIMG_CMMENUOLSDFPS> Pricing control</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VH602 - Maximum no. of accesses in the access sequences being used ?

  Certainly! Here's a detailed explanation of the SAP error message VH602 - Maximum no. of accesses in the access sequences being used:
  
  Error Message: VH602
  Text: Maximum no. of accesses in the access sequences being used
  
  Cause:
  This error occurs in the Pricing Procedure during pricing determination in Sales and Distribution (SD) module. Specifically, it happens when the system tries to access condition records through access sequences, but the number of condition table accesses exceeds the maximum allowed limit.
  
  Each access sequence consists of multiple condition tables.
  SAP has a system limit on the number of condition tables (accesses) that can be processed in a single pricing procedure.
  When the total number of accesses in the access sequences used in the pricing procedure exceeds this limit, the system throws the VH602 error.
  This is often due to overly complex or too many condition tables in the access sequences assigned to the pricing procedure.
  
  
  Where it occurs:
  
  During pricing determination in SD (Sales and Distribution) when the system reads condition records.
  In the access sequence configuration for condition types.
  When the pricing procedure calls multiple condition types with complex access sequences.
  
  
  Solution:
  
  
  Reduce the number of condition tables in access sequences:
  
  Review the access sequences assigned to the condition types in the pricing procedure.
  Remove unnecessary or redundant condition tables.
  Simplify the access sequences to reduce the total number of accesses.
  
  
  
  Optimize the pricing procedure:
  
  Check if all condition types and their access sequences are necessary.
  Remove or deactivate condition types that are not used.
  
  
  
  Check for custom access sequences:
  
  Sometimes custom access sequences have many condition tables.
  Simplify or optimize these custom access sequences.
  
  
  
  SAP Note / OSS:
  
  Check if there is an SAP Note related to increasing the maximum number of accesses allowed.
  Sometimes SAP provides a parameter or patch to increase the limit, but this is generally not recommended as it can impact performance.
  
  
  
  Technical workaround (not recommended unless advised by SAP):
  
  Increase the system limit for maximum accesses by adjusting relevant parameters or applying SAP Notes.
  This should be done only after consulting SAP support.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  V/07 - Maintain Access Sequences
  V/08 - Maintain Condition Tables
  V/06 - Maintain Pricing Procedure
  VK11 / VK12 / VK13 - Maintain Condition Records
  
  
  
  SAP Modules:
  
  Sales and Distribution (SD)
  Pricing and Condition Technique
  
  
  
  SAP Notes:
  
  Search for SAP Notes related to VH602 or maximum number of accesses in access sequences.
  Example: SAP Note 0000000 (hypothetical) might provide guidance or patches.
  
  
  
  Performance Consideration:
  
  Having too many condition tables/accesses can degrade system performance.
  Simplifying access sequences improves pricing determination speed.
  
  
  
  
  Summary:
  
  
  
  Aspect
  Description
  
  
  
  
  Cause
  Number of condition table accesses in access sequences exceeds system limit during pricing.
  
  
  Effect
  Pricing determination fails with error VH602.
  
  
  Solution
  Simplify access sequences, reduce condition tables, optimize pricing procedure.
  
  
  Related Tcodes
  V/07, V/08, V/06, VK11, VK12, VK13
  
  
  Notes
  Check SAP Notes for possible parameter changes or patches.
  
  
  
  
  If you need help identifying which access sequences or condition tables are causing the issue, you can debug the pricing procedure or analyze the pricing logs to see which condition types and access sequences are being processed.
  
  Let me know if you want guidance on how to analyze or modify access sequences!