Do you have any question about this error?
Message type: E = Error
Message class: FAGL_REORGANIZATION - Reorganization
Message number: 063
Message text: No account was transferred for object &1; see long text
The balance of an object included in the reorganization needs to be
transferred to an account.
However, this account has <ZH>not</> been transferred from the object
type implementation to the transfer program.
The balance to be transferred <ZH>cannot</> be saved.
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.
The SAP error message FAGL_REORGANIZATION063 indicates that during the reorganization of the General Ledger (G/L) accounts, no account was transferred for a specific object. This typically occurs in the context of the reorganization of G/L accounts in the New General Ledger (New GL) environment.
Cause:
The error can be caused by several factors, including:
- Missing Account Assignments: The account that is supposed to be transferred may not have been assigned correctly in the system.
- Incorrect Configuration: There may be issues with the configuration of the G/L accounts or the reorganization settings.
- Data Inconsistencies: There could be inconsistencies in the data that prevent the transfer of accounts.
- Object Not Found: The object specified in the error message may not exist or may not be relevant for the reorganization process.
Solution:
To resolve this error, you can take the following steps:
Check Account Assignments: Verify that the account in question is correctly assigned and exists in the system. Ensure that it is active and has the necessary configurations.
Review Configuration Settings: Go through the configuration settings for the G/L accounts and the reorganization process. Make sure that all necessary parameters are set correctly.
Analyze the Object: Look into the object specified in the error message. Ensure that it is valid and that there are no discrepancies in the data related to that object.
Run Consistency Checks: Use transaction codes like
OB52
(for fiscal year variant) orFAGL_REORGANIZATION
to check for inconsistencies in the G/L accounts and perform necessary corrections.Consult Long Text: The error message suggests checking the long text for more details. You can do this by navigating to the error message in the SAP system and reading the long text for additional context and guidance.
SAP Notes and Documentation: Check for any relevant SAP Notes or documentation that may address this specific error. SAP frequently updates its knowledge base with solutions for common issues.
Contact SAP Support: If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance. Provide them with the error details and any steps you have already taken.
Related Information:
FAGL_REORGANIZATION
for running the reorganization process and FBL3N
for displaying G/L account line items.By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.
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 | ![]() |
![]() |
FAGL_REORGANIZATION062 Structure name &1 not supported
What causes this issue? An attempt was made to read include &V1& for th...
FAGL_REORGANIZATION061 Structure &1 could not be read for the reorganization
What causes this issue? Preparation of the balance transfer entails reading val...
FAGL_REORGANIZATION064 No company code was transferred for object &1; see long text
What causes this issue? The balance of an object included in the reorganization...
FAGL_REORGANIZATION066 Internal error: Reorganization date was not transferred
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.