Do you have any question about this error?
Message type: E = Error
Message class: FH - General ledger module messages
Message number: 500
Message text: Internal error: Different accounts transferred
An internal error occurred. The data transferred to the update module
is inconsistent. You can only edit one G/L account at a time. A single
G/L account consists of the chart of accounts dependent data as well as
the company code dependent data, noting that all company codes have to
be assigned to the same chart of accounts. The tranferred data,
however, contains multiple G/L accounts.
The processing is not carried out.
Contact your system administrator.
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.
FH500
- Internal error: Different accounts transferred ?The SAP error message FH500, which states "Internal error: Different accounts transferred," typically occurs during the processing of financial transactions, particularly in the context of document postings or transfers between accounts. This error indicates that there is a mismatch in the accounts being used in the transaction, which can lead to inconsistencies in the financial data.
Causes:
- Account Mismatch: The most common cause is that the system is trying to transfer amounts between accounts that are not compatible or do not match the expected configuration.
- Configuration Issues: There may be issues with the configuration of the accounts in the Financial Accounting (FI) module, such as incorrect account types or settings.
- Data Inconsistencies: There could be inconsistencies in the master data for the accounts involved, such as differences in account types or currencies.
- Custom Code or Enhancements: If there are custom programs or enhancements in place, they may not be handling the account transfers correctly.
- User Input Errors: Incorrect data entry by users can also lead to this error, especially if the wrong accounts are selected during a transaction.
Solutions:
- Check Account Configuration: Review the configuration of the accounts involved in the transaction. Ensure that they are set up correctly and are compatible for the type of transaction being processed.
- Review Transaction Data: Look at the specific transaction that triggered the error. Verify that the accounts being used are correct and that there are no discrepancies.
- Analyze Custom Code: If there are any custom programs or enhancements, review the code to ensure that it is correctly handling account transfers.
- Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues.
- Test in a Development Environment: If possible, replicate the issue in a development or test environment to better understand the cause and test potential solutions without affecting production data.
- Contact SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP Support for further assistance.
Related Information:
By following these steps, you should be able to identify the root cause of the FH500 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
FH411
Table & is not active or has no fields
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FH410
Payment term & not defined
What causes this issue? Term of payment &V1& is not defined.System Response The system issues an error message and will not allow you to con...
FH501
Internal error: Action "&1" does not exist
What causes this issue? An internal error occurred. The data transferred to the update module is inconsistent. The action "&V1" is to b...
FH502
Internal error: Import of table &1 not possible
What causes this issue? An internal error occurred. The system could not read the data selected from table "&V1&".System Response ...
Click on this link to search all SAP messages.