Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: BE - General document entry
Message number: 213
Message text: Activity not allowed across company codes
WBS elements &V1& and &V2& belong to different company codes.
In principle, fixed price agreements across company codes or business
areas are allowed, but you need to bear certain organizational
considerations in mind to avoid errors in the balance sheet.
If the message is an error message, processing stops.
You can switch off this error message if you:
Make organizational arrangements to ensure that the fixed price
agreements/allocations in Profitability Analysis are not settled to
Financial Accounting
To do this, use a results analysis version for fixed price profitbility
analysis which is not copied to Financial Accounting.
Switch off this message in the general Controlling Implementation
Guide, step <DS:SIMG.SIMG_CFMENUORK3OBA5>Change message control</>.
Enter application BE and maintain the entry for message number 213. If
you do not specify a user here, the setting you enter affects all
users.
You calculate work in process using fixed prices. The WBS elements
involved belong to different company codes. Settlement to Financial
Accounting would result in an incorrect balance sheet. The balance
shown in one company code would be too high, the balance shown in the
other too low.
Error message extract from SAP system. Copyright SAP SE.
BE213
- Activity not allowed across company codes ?The SAP error message BE213, which states "Activity not allowed across company codes," typically occurs when there is an attempt to perform a transaction or activity that involves multiple company codes, which is not permitted in the current configuration. This error is common in scenarios involving financial transactions, intercompany postings, or when trying to allocate costs or revenues across different company codes.
Cause:
- Company Code Configuration: The system is configured to restrict certain activities across different company codes. This is often a result of the organizational structure in SAP, where each company code is treated as a separate legal entity.
- Transaction Type: The specific transaction being executed may not support cross-company code activities. For example, certain financial postings or allocations are designed to be executed within a single company code.
- Master Data Issues: The master data (like cost centers, profit centers, etc.) may not be set up correctly to allow cross-company code transactions.
- Authorization Issues: The user may not have the necessary authorizations to perform actions that involve multiple company codes.
Solution:
- Check Configuration: Review the configuration settings for the company codes involved. Ensure that the necessary settings for intercompany transactions are enabled if they are required.
- Use Correct Transaction Codes: Ensure that you are using the correct transaction codes that support cross-company code activities, if applicable.
- Review Master Data: Check the master data for the entities involved in the transaction. Ensure that they are correctly set up to allow for intercompany transactions.
- User Authorizations: Verify that the user has the appropriate authorizations to perform the intended transaction. If not, work with your SAP security team to obtain the necessary permissions.
- Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on handling transactions that involve multiple company codes.
Related Information:
If the issue persists after checking the above points, it may be beneficial to consult with an SAP expert or your internal SAP support team for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
BE212
Activity not allowed for statistical WBS element &
What causes this issue? Fixed prices are not permitted for statistical WBS elements.System Response INCLUDE NA_ALLG_NOVERARBEITUNG OBJECT DOKU ID TX...
BE211
WBS elements & and & both belong to subproject &
What causes this issue? Fixed price agreements are only possible between different <GL:subproject>subprojects</>. WBS element &V1&...
BE214
Transaction not valid across business areas
What causes this issue? WBS elements &V1& and &V2& belong to different business areas. Because business area balance sheets are to be...
BE220
Enter a version for the fixed price document update
What causes this issue? You have not created a fixed price version, which you must do before you can enter a fixed price agreement.System Response I...
Click on this link to search all SAP messages.