Do you have any question about this error?
Message type: E = Error
Message class: M8 - Invoice Verification/Valuation
Message number: 795
Message text: Different invoicing party &1 planned for document &2
Document &V2& comes from SAP Transportation Management (SAP TM).
You entered an invoice with reference to TM documents.
In TM document &V2&, invoicing party &V1& is entered. You are now
posting the invoice to the invoicing party &V3&.
This can be due to one of two reasons:
You have entered the invoicing party &V3& and TM document &V2&.
You entered a multiple assignment. The first item refers to a TM
document with invoicing party &V3&. Another item refers to TM document
&V2&. The system copies the invoicing party from the first item to all
items, in this case &V3&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check your entries and make any necessary corrections.
By default, this message is set as a warning. In this case, all items
are selected.
If you want to prevent items with a different invoicing party being
selected, set the system message as an error (<LB>E</>) in Customizing
for <LS>Logistics Invoice Verification</> under
<DS:SIMG.SIMG_CFMENUOLMROMRM>Define Attributes of System Messages</>.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message M8795, which states "Different invoicing party &1 planned for document &2," typically occurs in the context of logistics and invoicing processes. This error indicates that there is a mismatch between the invoicing party specified in the document and the one that is expected or configured in the system.
Cause:
- Inconsistent Data: The invoicing party defined in the purchase order or sales order does not match the invoicing party defined in the related document (e.g., delivery or invoice).
- Master Data Issues: There may be discrepancies in the master data for customers or vendors, such as incorrect or outdated information.
- Configuration Settings: The system configuration for the invoicing party may not align with the business requirements or the specific transaction being processed.
- Document Flow Issues: If the document flow is not properly maintained, it can lead to inconsistencies in the invoicing party.
Solution:
- Check Document Details: Review the details of the document (e.g., purchase order, sales order) to ensure that the invoicing party is correctly specified.
- Verify Master Data: Ensure that the master data for the customer or vendor is accurate and up-to-date. This includes checking the customer/vendor master records for the correct invoicing party.
- Adjust Configuration: If necessary, adjust the configuration settings in the SAP system to ensure that the invoicing party is correctly defined for the relevant transactions.
- Document Flow Review: Check the document flow to ensure that all related documents are correctly linked and that there are no discrepancies.
- Consult with Business Users: Engage with business users to understand the intended invoicing process and ensure that the system is configured to meet those requirements.
Related Information:
If the issue persists after following these steps, it may be beneficial to involve your SAP support team or consult with an SAP expert for further assistance.
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 | ![]() |
![]() |
M8794 Document has been prepaid, do not enter retention
What causes this issue? A down payment document has been posted for this invoic...
M8793 Calculate Tax not allowed in combination with prepayment
What causes this issue? The <LS>Calculate Tax</> indicator must not...
M8796 Evaluated receipt settlement active for document &1 &2
What causes this issue? Document &V1& comes from SAP Transportation Man...
M8797 Currency &1 in document &2 different to entered currency
What causes this issue? Document &V2& 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.