Do you have any question about this error?
Message type: E = Error
Message class: NAA - Subsequent settlement (Purchasing)
Message number: 136
Message text: An error occurred during price determination
An error occurred during price determination for item &V1&. A flag is
set indicating that price determination for the item is incomplete.
Settlement documents cannot be created for arrangement &V2&.
As a rule, this can only be due to an error in the calculation of tax,
as only the taxes are determined in price determination. Check the
Customizing settings for tax.
In other cases, see any additional messages. Contact your system
administrator, so that the cause of the error can be investigated.
This relates to arrangement &V2&.
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.
NAA136
- An error occurred during price determination ?The SAP error message NAA136, which states "An error occurred during price determination," typically occurs during the pricing process in SAP, particularly in the context of sales and distribution (SD) or materials management (MM). This error can arise due to various reasons related to pricing conditions, master data, or configuration settings.
Causes:
- Missing or Incorrect Pricing Conditions: The pricing procedure may not have the necessary condition records for the relevant pricing elements (like discounts, surcharges, taxes, etc.).
- Master Data Issues: Problems with master data, such as incorrect material master records, customer master records, or info records, can lead to pricing determination errors.
- Configuration Issues: The pricing procedure may not be correctly configured in the system, or there may be missing or incorrect settings in the condition types or access sequences.
- Currency Issues: If there are discrepancies in currency settings between the sales order and the pricing conditions, it can lead to errors.
- User Authorizations: Lack of proper authorizations for accessing certain pricing conditions can also trigger this error.
Solutions:
Check Pricing Conditions:
- Go to the transaction code
VK13
(Display Condition) to verify if the necessary condition records exist for the relevant pricing elements.- Ensure that the condition types are correctly maintained and active.
Review Master Data:
- Check the material master (
MM03
), customer master (XD03
), and vendor master (XK03
) for any inconsistencies or missing data that could affect pricing.- Ensure that the relevant info records are maintained correctly.
Verify Pricing Procedure Configuration:
- Use transaction code
V/08
to review the pricing procedure configuration.- Ensure that the access sequence is correctly defined and that the condition types are properly assigned to the pricing procedure.
Check Currency Settings:
- Ensure that the currency settings in the sales order match those in the pricing conditions.
- Verify that the currency conversion settings are correctly configured.
Review User Authorizations:
- Check if the user has the necessary authorizations to access the pricing conditions. This can be done by reviewing the user's roles and authorizations.
Debugging:
- If the issue persists, consider debugging the pricing determination process to identify the exact point of failure. This may require technical expertise.
Related Information:
If the problem continues after following these steps, it may be beneficial to consult with an SAP functional consultant or technical support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
NAA135
Bus. vol. update for document &1, item &2 cannot be carried out
What causes this issue? Document &V1&, item &V2& (&V3&) is relevant for the subsequent settlement of a condition record of ar...
NAA134
Business volume data for arrangement &1 could not be compiled
What causes this issue? Error messages were issued.System Response The business volume for arrangement &V1& could not be created.How to fix ...
NAA137
A document condition for the condition type &1 to be settled is inactive
What causes this issue? A document condition of condition type &V1& (for which settlement accounting is to be performed) was deactivated duri...
NAA138
Tax condition type &2 is missing in settlement schema &1
What causes this issue? Tax condition type &V2& is missing in settlement schema &V1&. It is therefore not possible to calculate the t...
Click on this link to search all SAP messages.