Do you have any question about this error?
Message type: E = Error
Message class: GLE_MCA - Multicurrency Accounting
Message number: 128
Message text: Cross-company postings in transaction &1 are not allowed
You are trying to post a cross-company MCA transaction. This is only
allowed for the MCA transaction <AB>MC1</>.
The system issued a warning and changed the company code of all lines to
be identical to the company code in the transaction header fields
If you need to create cross-company code postings requiring the MCA
<AB>MC2</> or <AB>MC3</> logic, use an intermediate account, and then
create an <AB>MC1</> posting to transfer between company codes.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
GLE_MCA128
- Cross-company postings in transaction &1 are not allowed ?The SAP error message GLE_MCA128 indicates that cross-company postings are not allowed in the specific transaction you are trying to execute. This error typically arises in the context of financial accounting and controlling when you attempt to post transactions that involve multiple company codes, which is not permitted under the current configuration.
Cause:
- Configuration Settings: The system is configured to disallow cross-company code postings for the specific transaction type you are using. This is often a deliberate design choice to maintain the integrity of financial reporting within individual company codes.
- Transaction Type Restrictions: Certain transactions, such as specific journal entries or intercompany transactions, may have restrictions based on the company code settings.
- Master Data Issues: The master data for the accounts or cost centers involved may not be set up to allow cross-company transactions.
Solution:
Check Configuration: Review the configuration settings in the SAP system to determine if cross-company postings are allowed for the transaction type you are using. This can typically be found in the Financial Accounting (FI) or Controlling (CO) module settings.
- Navigate to SPRO ? Financial Accounting ? General Ledger ? Master Data ? Define Company Code and check the settings related to cross-company code postings.
Use Appropriate Transaction: If cross-company postings are not allowed, consider using a different transaction that supports intercompany postings, such as intercompany billing or specific intercompany journal entries.
Adjust Master Data: If necessary, update the master data for the accounts or cost centers involved to allow for cross-company transactions. This may involve changing settings in the account master records or cost center configurations.
Consult Documentation: Review SAP documentation or consult with your SAP support team to understand the specific restrictions and how they apply to your business processes.
User Authorization: Ensure that the user executing the transaction has the necessary authorizations to perform cross-company postings if they are allowed.
Related Information:
If the issue persists after checking these areas, it may be beneficial to engage with your SAP support team or a consultant who specializes in SAP Financial Accounting for further assistance.
Get instant SAP help. Start your 7-day free trial now.
GLE_MCA127
Rate types for positions different from header rate types
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GLE_MCA126
Insert errors in the table &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GLE_MCA129
No position config. for G/L acct &1 (co.code &2,pos.cat. &3, pos.type &4)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GLE_MCA130
Need two rates for comparison; currency &1 to &2 currency &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.