Do you have any question about this error?
Message type: E = Error
Message class: M8 - Invoice Verification/Valuation
Message number: 799
Message text: Cross-company-code transaction in document &1, item &2, company code &3
You are working in company code &V4&.
You are entering the invoice for a document &V1& that is assigned to a
different company code &V3&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check the document number you entered, and the company code in which you
are working. Correct your entries as applicable.
By default, this message is set as a warning. You can set the system
message as an error (<LB>E</>) or an information message (<LB>I</>) 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 M8799 indicates that there is a cross-company code transaction issue in a document. This error typically arises when you are trying to post a transaction that involves multiple company codes, which is not allowed in certain contexts within SAP.
Cause:
The error occurs due to the following reasons:
- Cross-Company Code Transactions: The transaction you are trying to post involves multiple company codes, which is not permitted for the specific document type or transaction type you are using.
- Configuration Settings: The system may be configured to disallow cross-company code transactions for certain types of documents or postings.
- Document Type Restrictions: The document type being used may not support cross-company code transactions.
Solution:
To resolve the M8799 error, you can consider the following steps:
Check Document Type: Ensure that the document type you are using allows for cross-company code transactions. If it does not, you may need to use a different document type that supports such transactions.
Review Configuration:
- Go to the configuration settings in SAP (Transaction SPRO) and check the settings for the relevant document types and company codes.
- Ensure that the configuration allows for cross-company code transactions if that is your intention.
Separate Transactions: If cross-company code transactions are not allowed, consider splitting the transaction into separate postings for each company code involved.
Consult with SAP Basis or Functional Consultant: If you are unsure about the configuration or how to proceed, it may be helpful to consult with an SAP Basis or functional consultant who can provide guidance based on your specific system setup.
Check User Authorizations: Ensure that the user has the necessary authorizations to perform transactions across different company codes, if applicable.
Related Information:
By following these steps, you should be able to identify the cause of the M8799 error and implement a suitable solution.
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 | ![]() |
![]() |
M8798 &1 &2 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is ...
M8797 Currency &1 in document &2 different to entered currency
What causes this issue? Document &V2& comes from SAP Transportation Man...
M8800 ************************ LIFO valuation **********************
Self-Explanatory Message Since SAP believes that this specific error message is ...
M8802 Valuation area & not defined for LIFO
Self-Explanatory Message Since SAP believes that this specific error message is ...
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.