Do you have any question about this error?
Message type: E = Error
Message class: NAA - Subsequent settlement (Purchasing)
Message number: 360
Message text: No access to condition table &1 was successful
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) was blank
The key combination (validity area) did not match
The access condition was not fulfilled.
The system does not perform a business volume update (recompilation).
Either Customizing settings were changed (not allowed) or the situation
described in Note 153577 occurred.
If the situation described in Note 153577 did not occur, please correct
the Customizing settings.
Error message extract from SAP system. Copyright SAP SE.
NAA360
- No access to condition table &1 was successful ?The SAP error message NAA360 "No access to condition table &1 was successful" typically occurs in the context of pricing and condition records in SAP. This error indicates that the system was unable to find any valid access sequence for the specified condition table, which means that the pricing procedure could not retrieve the necessary condition records for the transaction.
Cause:
- Missing Condition Records: There may be no condition records maintained for the specified condition table.
- Access Sequence Configuration: The access sequence associated with the pricing procedure may not include the condition table in question.
- Incorrect Condition Table: The condition table specified in the error message may not be correctly defined or may not be relevant for the current transaction.
- Authorization Issues: The user may not have the necessary authorizations to access the condition records for the specified table.
- Data Inconsistencies: There may be inconsistencies in the master data or transaction data that prevent the system from accessing the condition records.
Solution:
Check Condition Records: Verify that the necessary condition records exist for the condition table mentioned in the error message. You can do this using transaction codes like
VK11
(Create Condition) orVK12
(Change Condition).Review Access Sequence: Check the access sequence assigned to the pricing procedure. Ensure that the condition table is included in the access sequence. You can do this using transaction code
V/07
(Access Sequences).Validate Condition Table: Ensure that the condition table is correctly defined and relevant for the pricing procedure being used. You can check this in the configuration settings.
User Authorizations: Ensure that the user has the necessary authorizations to access the condition records. This may involve checking the user's roles and authorizations in transaction
PFCG
.Data Consistency: Check for any inconsistencies in the master data (like customer or material master) that might affect the pricing. Ensure that all relevant data is correctly maintained.
Debugging: If the issue persists, consider debugging the pricing procedure to identify where the access is failing. This may require technical expertise.
Related Information:
VK11
, VK12
, V/07
, and V/08
for managing condition records and access sequences.If the problem continues after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in pricing and conditions.
Get instant SAP help. Start your 7-day free trial now.
NAA359
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 ty...
NAA358
No access is defined for condition table &1
What causes this issue? The condition record is assigned to condition table &V1&. However, access sequence &V3& of condition type &am...
NAA361
Access is not defined for condition table &1
What causes this issue? The condition record is assigned to condition table &V1&. However, access sequence &V3& of condition type &am...
NAA362
The requested function was terminated
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.