How To Fix MN164 - Price determination error during billing doc. check run (internal error)

SAP Error Message - Details

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 164

• Message text: Price determination error during billing doc. check run (internal error)

What causes this issue?

The system could not read the price determination data after the billing
document check run. The billing document numbers and the taxes could not
be determined.

System Response

Settlement accounting was not carried out for rebate arrangement &V1&.

How to fix this error?

Contact your system administrator.

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

Check that the pricing type has been set as follows in the document flow
for billing type &V2& for the sales document type (item category B1N):
to the correct value 'G'
adopt price components unchanged
redetermine taxes

If you have the relevant authorization, you can carry out the check and
make any necessary changes directly.
<DS:SIMG.SIMG_CMMENUOLSDVBX2> Maintain copying control for billing
documents</>
ENDIF
You will find the sales document type in the Customizing facility for
the rebate arrangement type. The document types BM1 and BM3 are supplied
in the standard system.
Another possible source of the error may be the document flow for
billing type &V2& for the sales document type at the item category level
(B1N). The copying requirement should be initial ('000') or not filter
out any items.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN164 - Price determination error during billing doc. check run (internal error) ?

  The SAP error message MN164, which indicates a "Price determination error during billing document check run (internal error)," typically arises during the billing process when the system encounters issues with pricing conditions or data inconsistencies. Here are some potential causes, solutions, and related information for this error:
  Causes:
  
  Missing or Incorrect Pricing Conditions: The pricing conditions required for the billing document may be missing or incorrectly configured in the system.
  Master Data Issues: Problems with master data, such as customer master, material master, or pricing records, can lead to this error.
  Custom Pricing Logic: If there are custom pricing routines or user exits that are not functioning correctly, they may cause this error.
  Inconsistent Data: Inconsistencies in the data between the sales order and the billing document can lead to pricing determination issues.
  Configuration Issues: Incorrect configuration in the pricing procedure or condition types can also trigger this error.
  
  Solutions:
  
  Check Pricing Conditions: Verify that all necessary pricing conditions are maintained in the system. Ensure that the condition records are correctly set up for the relevant sales area, customer, and material.
  Review Master Data: Check the customer master and material master data for any inconsistencies or missing information that could affect pricing.
  Analyze Custom Logic: If there are any custom pricing routines or enhancements, review the code to ensure there are no errors or issues that could be causing the problem.
  Debugging: Use the SAP debugger to trace the pricing determination process. This can help identify where the error is occurring and what data is causing the issue.
  Check Configuration: Review the configuration settings for pricing procedures, condition types, and access sequences to ensure they are set up correctly.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on similar issues.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) to manage pricing conditions.
  Transaction for Billing: Use transaction VF01 to create billing documents and VF02 to change them. You can also use VF03 to display billing documents.
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance, especially if it appears to be a bug or requires deeper investigation.
  
  By following these steps, you should be able to identify and resolve the underlying cause of the MN164 error in your SAP system.