Do you have any question about this error?
Message type: E = Error
Message class: FIRU_VAT - VAT Russia S/4HANA
Message number: 004
Message text: According to Customizing, MM documents with such data are not corrections
You have not specified this Material document type as corrective
document. You cannot use prefix COR^ in the <ZK>Document Header Text
</>(BKTXT) field.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check your customizing settings in the
<DS:SIMG.V_T007K_RU_CI>Define Correction Invoices</> activity.
Error message extract from SAP system. Copyright SAP SE.
FIRU_VAT004
- According to Customizing, MM documents with such data are not corrections ?The SAP error message FIRU_VAT004 typically indicates that there is an issue with the VAT (Value Added Tax) processing in the context of MM (Materials Management) documents. The message suggests that the system has identified that the documents in question are not classified as corrections according to the customizing settings.
Cause:
Document Type Configuration: The document type used for the MM document may not be configured to allow for VAT corrections. This can happen if the document type is set up in a way that does not permit adjustments or corrections to VAT entries.
Incorrect Document Status: The document may be in a status that does not allow for VAT corrections. For example, if the document is already posted or has been processed in a way that prevents further changes.
Customizing Settings: The customizing settings for VAT processing may not be aligned with the requirements for handling corrections. This could involve settings in the VAT configuration or the MM document types.
Solution:
Check Document Type Settings: Review the configuration of the document type in the SAP Customizing Implementation Guide (IMG). Ensure that the document type is set up to allow VAT corrections if that is necessary for your business process.
Review Document Status: Check the status of the document in question. If it is already posted, you may need to reverse the document or create a new document to correct the VAT entries.
Adjust Customizing Settings: If the issue is related to customizing settings, you may need to adjust the VAT configuration in the IMG. This could involve settings related to tax codes, tax determination, or document types.
Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling VAT corrections in your version of SAP. This can provide insights into best practices and configuration options.
Seek Support: If the issue persists, consider reaching out to your SAP support team or consulting with an SAP expert who can provide tailored assistance based on your specific system configuration and business processes.
Related Information:
FB60
(Invoice), MIRO
(Invoice Verification), and MIGO
(Goods Movement).By addressing the underlying causes and following the suggested solutions, you should be able to resolve the FIRU_VAT004 error and ensure proper handling of VAT in your MM documents.
Get instant SAP help. Start your 7-day free trial now.
FIRU_VAT002
Could not find original accounting document &1 &2 &3 specified after &4.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FIRU_VAT001
Field &1 not found in search help FIRU_VAT_SELECT_OPCODES. Contact SAP.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FIRU_VAT005
You cannot use COR^ for SD documents, please use the standard SD flow.
What causes this issue? You entered prefix COR^ in the header of an Financial Accounting document released from Billing.System Response The system i...
FIRU_VAT006
You cannot reference this document in the document itself
What causes this issue? You entered "COR^NNNNNNNNYYYY" in the header text of document with number NNNNNNNN (field BKTXT). You cannot refere...
Click on this link to search all SAP messages.