Do you have any question about this error?
Message type: E = Error
Message class: AA - Messages for Asset Accounting
Message number: 390
Message text: Transaction type &1 not possible (posting to affiliated company)
For the current document, you specified either implicitly (via the
customer/vendor), or explicitly (with a manual entry), that this
posting is to an affiliated company. In this case, Asset Accounting
requires you to use special transaction types. This enables the system
to separately identify such transactions.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check the line items that you have already entered, and the transaction
type you entered.
Error message extract from SAP system. Copyright SAP SE.
AA390
- Transaction type &1 not possible (posting to affiliated company) ?The SAP error message AA390, which states "Transaction type &1 not possible (posting to affiliated company)," typically occurs in the context of Asset Accounting (FI-AA) when you attempt to post a transaction type that is not allowed for affiliated companies. This can happen in various scenarios, such as when trying to transfer assets or post transactions between affiliated companies.
Cause:
- Transaction Type Restrictions: The transaction type you are trying to use is not configured to allow postings to affiliated companies. Each transaction type in SAP can have specific settings that determine whether it can be used for intercompany transactions.
- Configuration Settings: The configuration for asset accounting may not allow postings to affiliated companies for the specific transaction type you are using.
- Company Code Settings: The company codes involved may not be set up correctly to allow intercompany transactions.
Solution:
Check Transaction Type Configuration:
- Go to the configuration settings for Asset Accounting (Transaction code: SPRO).
- Navigate to Financial Accounting (New) > Asset Accounting > Integration with General Ledger > Define Transaction Types.
- Check the settings for the transaction type you are trying to use and ensure that it is allowed for postings to affiliated companies.
Review Company Code Settings:
- Ensure that the company codes involved in the transaction are set up correctly for intercompany transactions.
- Check the settings under Financial Accounting (New) > General Ledger Accounting > Master Data > G/L Accounts > Prepare G/L Account Master Data to ensure that the accounts are configured for intercompany postings.
Use a Different Transaction Type:
- If the transaction type you are trying to use is not allowed for affiliated companies, consider using a different transaction type that is configured for such postings.
Consult Documentation:
- Review SAP documentation or consult with your SAP support team for specific guidance on the transaction type and its allowed configurations.
Testing:
- After making any changes, perform a test transaction to ensure that the error is resolved.
Related Information:
If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or consult with an SAP expert for further assistance.
Get instant SAP help. Start your 7-day free trial now.
AA389
Transaction type &1 not possible (no affiliated company specified)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
AA388
You cannot post this document (Area & is managed in another currency)
The system issues an error message and will not allow you to continue with this transaction until the error is resolved. ...
AA391
Enter amount with + sign
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
AA392
You cannot post to this asset (Area & does not exist)
What causes this issue? According to Table TABWA, postings have to be made to area &V1&. This depreciation area, however, is not managed in t...
Click on this link to search all SAP messages.