How To Fix NAA359 - Access to condition table &1 not successful

SAP Error Message - Details

• Message type: E = Error

• Message class: NAA - Subsequent settlement (Purchasing)

• Message number: 359

• Message text: Access to condition table &1 not successful

What causes this issue?

The condition record is assigned to condition table &V1&. No accesses of
access sequence &V3& of condition type &V2& were successful.
One of the following prerequisites was not met for each of the access
attempts:
A field (e.g. supplier, material) is blank
The variable key does not match
The access condition is not fulfilled.

System Response

The system does not perform retrospective updating. The document item is
not relevant for the condition record.

How to fix this error?

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

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 NAA359 - Access to condition table &1 not successful ?

  The SAP error message NAA359, which states "Access to condition table &1 not successful," typically occurs in the context of pricing or condition records in SAP. This error indicates that the system was unable to access a specific condition table, which is used for pricing, discounts, or other condition-based calculations.
  Causes:
  
  Missing Condition Records: The condition table specified in the error message may not have any records defined for the relevant key combination.
  Authorization Issues: The user may not have the necessary authorizations to access the condition table.
  Incorrect Configuration: The condition table may not be properly configured in the system, or the access sequence may not be set up correctly.
  Data Inconsistencies: There may be inconsistencies or issues with the data in the condition table.
  Inactive Condition Types: The condition type associated with the condition table may be inactive or not properly maintained.
  
  Solutions:
  
  Check Condition Records: Verify that the condition records exist for the specified condition table. You can do this by navigating to the relevant transaction (e.g., VK11 for creating condition records) and checking if records are present.
  Review Authorizations: Ensure that the user has the necessary authorizations to access the condition table. This can be checked in the user roles and profiles.
  Validate Configuration: Check the configuration of the condition table and access sequence in the SAP customizing settings (transaction SPRO). Ensure that the condition table is correctly defined and linked to the appropriate access sequence.
  Data Consistency Check: Run data consistency checks to identify any issues with the condition records. This may involve using transaction codes like SE16 or SE11 to inspect the underlying database tables.
  Activate Condition Types: If the condition type is inactive, activate it in the configuration settings. This can be done in the pricing procedure settings.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition Records), VK12 (Change Condition Records), VK13 (Display Condition Records), and SPRO (SAP Customizing Implementation Guide).
  Access Sequences: Understand how access sequences work in SAP pricing and how they determine the order in which condition records are accessed.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message. You can search for notes in the SAP Support Portal.
  Documentation: Review SAP documentation related to pricing and condition management for a deeper understanding of how condition tables function.
  
  If the issue persists after checking these areas, it may be beneficial to consult with your SAP support team or a technical consultant for further investigation.