Do you have any question about this error?
Message type: E = Error
Message class: M8 - Invoice Verification/Valuation
Message number: 794
Message text: Document has been prepaid, do not enter retention
A down payment document has been posted for this invoice document. You
cannot enter retention for prepaid invoices.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
INCLUDE MM_IV_MELDUNGEN OBJECT DOKU ID TXDelete the retention values at item level.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message M8794, which states "Document has been prepaid, do not enter retention," typically occurs in the context of procurement and invoice processing within the SAP system. This error indicates that the document you are trying to process has already been prepaid, and therefore, you cannot enter retention amounts against it.
Cause:
- Prepayment Status: The document (such as a purchase order or invoice) has been marked as prepaid. This means that a payment has already been made for the goods or services, and the system does not allow for retention entries on prepaid documents.
- Retention Entry Attempt: You are attempting to enter a retention amount (a portion of the payment that is withheld until certain conditions are met) on a document that has already been fully paid or prepaid.
Solution:
- Review Document Status: Check the status of the document in question. If it is indeed marked as prepaid, you will need to adjust your approach to handling retention.
- Avoid Retention Entry: If the document is prepaid, do not attempt to enter a retention amount. Instead, process the document as it is without retention.
- Consult with Finance: If you believe that retention should be applicable despite the prepayment, consult with your finance or accounting department to clarify the business rules and determine if any adjustments can be made.
- Adjust Payment Terms: If retention is a necessary part of your procurement process, consider adjusting the payment terms in the purchase order or contract to avoid prepayment in the future.
Related Information:
If the issue persists or if you need further assistance, consider reaching out to your SAP support team or a consultant who specializes in SAP financial processes.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
M8793 Calculate Tax not allowed in combination with prepayment
What causes this issue? The <LS>Calculate Tax</> indicator must not...
M8792 Prepayment document could not be created (See messages)
What causes this issue? A prepayment has been requested for this invoice docume...
M8795 Different invoicing party &1 planned for document &2
What causes this issue? Document &V2& comes from SAP Transportation Man...
M8796 Evaluated receipt settlement active for document &1 &2
What causes this issue? Document &V1& comes from SAP Transportation Man...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.