Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 370
Message text: PO history (invoice verification) has no tax code
The purchase order history for purchasing document &V1&, item &V2&, for
invoice verification document &V3&, item &V4&, has no tax code. This is
probably due to a program error.
The function has been performed. However, any later attempt to carry out
settlement accounting with regard to the condition record will result in
an error, since settlement accounting involving supplier business volume
data without a tax code is not possible.
Contact your system administrator.
Check the supplier business volume data. It may be necessary to correct
the data with regard to the missing tax code.
Error message extract from SAP system. Copyright SAP SE.
MN370
- PO history (invoice verification) has no tax code ?The SAP error message MN370 indicates that there is an issue with the purchase order (PO) history related to invoice verification, specifically that there is no tax code associated with the transaction. This can occur in various scenarios, such as when processing invoices or during the goods receipt process.
Cause:
- Missing Tax Code: The most common cause of this error is that the tax code has not been maintained in the purchase order or the invoice.
- Incorrect Configuration: The tax configuration in the system may not be set up correctly, leading to missing tax codes for certain transactions.
- Document Type Issues: The document type used for the invoice may not be configured to allow tax codes.
- Master Data Issues: The vendor master data or material master data may not have the necessary tax information.
Solution:
Check Purchase Order:
- Go to the purchase order in question and check if the tax code is maintained in the item details. If it is missing, you can add the appropriate tax code.
Review Invoice:
- If you are processing an invoice, ensure that the invoice document has the correct tax code entered. You can do this in the invoice entry screen.
Configuration Check:
- Verify the tax configuration in the system. This includes checking the tax codes in the configuration settings (Transaction Code: SPRO) under Financial Accounting > Tax on Sales/Purchases > Basic Settings.
Vendor and Material Master Data:
- Check the vendor master data (Transaction Code: XK03) and ensure that the tax information is correctly maintained.
- Similarly, check the material master data (Transaction Code: MM03) to ensure that the tax classification is set correctly.
Document Type Settings:
- Review the settings for the document type used for the invoice to ensure that it allows for tax codes. This can be checked in the configuration settings.
Consult with SAP Support:
- If the issue persists after checking the above points, it may be beneficial to consult with SAP support or your internal SAP team for further investigation.
Related Information:
Transaction Codes:
SAP Notes:
Documentation:
By following these steps, you should be able to identify and resolve the issue related to the MN370 error message in SAP.
Get instant SAP help. Start your 7-day free trial now.
MN369
Business volume data without tax code exists for condition record
What causes this issue? Supplier business volume data to which no tax code has been assigned exists for this condition record. This is probably due t...
MN368
List output contains data on version '&', not the actual data '000'
What causes this issue? The supplier business volume data, settled income, and provisions for income are stored in the Purchasing Information System ...
MN371
No list output generated (internal error)
What causes this issue? Although &V1& rebate arrangements satisfy the selection criteria, no list output has been generated.System Response ...
MN372
Subtotal missing in calculation schema &, step & (see long text)
What causes this issue? No valid subtotal could be determined for step &V2& of calculation schema &V1&, usage &V3&, applicati...
Click on this link to search all SAP messages.