Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 889
Message text: Tax code (tax-exempt tranaction output tax) missing for company code &
Tax calculation using the tax jurisdiction code is active for company
code &V1&.
In this case, business volumes are updated for customer rebate
arrangements in <DS:GLOS.3526C095AFAB52B9E10000009B38F974>subsequent
settlement</> with the tax code for non-taxable transactions (output
tax) of the company code.
The tax code for non-taxable transactions (output tax) is not
maintained for company code &V1&.
The business volume data is not updated.
&WHAT_TO_DO& for System Administrators
Enter the missing data in Customizing, and post the missing data using
the "Subsequent business volume update" function.
<ds:SIMG.SIMG_CFMENUORFBOBCL>Allocate non-taxable transactions to
company code</>
ENDIF
The condition record concerned has (internal) number &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.
MN889
- Tax code (tax-exempt tranaction output tax) missing for company code & ?The SAP error message MN889 indicates that there is a missing tax code for tax-exempt transactions in the specified company code. This error typically arises during the processing of transactions that are exempt from tax, and it can prevent the successful posting of documents.
Cause:
- Missing Tax Code Configuration: The tax code for tax-exempt transactions has not been defined in the system for the specified company code.
- Incorrect Tax Code Assignment: The tax code may not be correctly assigned to the relevant transaction types or master data.
- Company Code Settings: The company code may not have the necessary settings to handle tax-exempt transactions.
Solution:
Define Tax Code:
- Go to the SAP transaction code OBYZ (or navigate through the menu: SPRO > Financial Accounting > Tax on Sales/Purchases > Basic Settings > Check Tax Codes).
- Ensure that a tax code for tax-exempt transactions is defined for the relevant company code.
- If it is missing, create a new tax code and ensure it is set up correctly for tax-exempt transactions.
Check Tax Code Assignment:
- Verify that the tax code is assigned to the relevant master data (e.g., customer/vendor master records) and transaction types.
- Ensure that the tax code is included in the tax determination procedure for the relevant company code.
Review Company Code Settings:
- Check the configuration settings for the company code to ensure that it is set up to handle tax-exempt transactions.
- Ensure that the tax settings in the company code are correctly configured to allow for tax-exempt transactions.
Testing:
- After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
Related Information:
Transaction Codes:
Documentation: Refer to SAP Help documentation for detailed steps on configuring tax codes and handling tax-exempt transactions.
Consulting with SAP Support: If the issue persists after checking the configuration, consider reaching out to SAP support or consulting with an SAP FI (Financial Accounting) expert for further assistance.
By following these steps, you should be able to resolve the MN889 error and ensure that your system can handle tax-exempt transactions correctly.
Get instant SAP help. Start your 7-day free trial now.
MN888
Item &2 of settlement document &1 has no input tax code
What causes this issue? Item &V2& of settlement document &V1& does not have an input tax code. It is not possible to update business ...
MN887
Item &2 of settlement document &1 has no output tax code
How to fix this error? This situation should not occur. INCLUDE ISR_SYSTEMFEHLER OBJECT DOKU ID TXProcedure for System Administrators The system iss...
MN890
No default plant is assigned to company code &1 for updates
What causes this issue? A document entry (settlement document or supplier billing document) relevant to <DS:GLOS.3526C095AFAB52B9E10000009B38F974&...
MN891
Document index contains invalid data records (internal error)
What causes this issue? When documents were read during determination of business volume data for arrangement &V1&, data records for Settleme...
Click on this link to search all SAP messages.