Do you have any question about this error?
Message type: E = Error
Message class: FAGL_REORGANIZATION - Reorganization
Message number: 114
Message text: This function is only supported in new General Ledger Accounting
You want to perform a <DS:GLOS.499009CE70113942E10000000A421948>
reorganization</>.
This function is only supported in new General Ledger Accounting.
However, new General Ledger Accounting is <ZH>not</> activated.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If necessary, activate new General Ledger Accounting. For this, note the
<DS:TX.FAGL_ACTIVE>further information on activating new General Ledger
Accounting</>.
Error message extract from SAP system. Copyright SAP SE.
FAGL_REORGANIZATION114
- This function is only supported in new General Ledger Accounting ?The SAP error message FAGL_REORGANIZATION114 indicates that a specific function or operation you are trying to perform is only supported in the New General Ledger (New G/L) Accounting. This error typically arises when you are attempting to execute a transaction or function that is not compatible with the Classic General Ledger (Classic G/L) setup.
Cause:
- Classic G/L Usage: The system is configured to use the Classic General Ledger, which does not support certain functionalities that are available in the New G/L.
- Transaction Attempt: You may be trying to execute a transaction that is designed for the New G/L, such as certain types of reorganizations or reporting functions.
- System Configuration: The company code or the client may not be fully migrated to the New G/L, leading to this error when trying to access New G/L features.
Solution:
Check G/L Configuration: Verify if your company code is set up for New G/L. You can do this by checking the configuration in the SAP system:
- Go to transaction code
OBY6
to check the settings for your company code.- Ensure that the New G/L is activated for the company code in question.
Migration to New G/L: If your organization intends to use the functionalities of the New G/L, consider migrating from Classic G/L to New G/L. This involves:
- Planning the migration process.
- Running the necessary migration programs (e.g., transaction code
SFIN_MIGRATE
).- Testing the migration in a sandbox or development environment before applying it to production.
Use Alternative Transactions: If migration is not an option, look for alternative transactions or reports that are compatible with the Classic G/L. Consult the SAP documentation or your SAP support team for guidance on available functionalities.
Consult SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions related to this error. You can search for notes in the SAP Support Portal.
Related Information:
If you continue to face challenges, consider reaching out to your SAP Basis or functional consultant for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FAGL_REORGANIZATION113
Grouping information is inconsistent
What causes this issue? This is a technical error occurring within the object implementation for object type &V1&. One of the following prere...
FAGL_REORGANIZATION112
Plan type &1 is active for reorganization of fixed assets
What causes this issue? For reorganization plan type &V1&, the reorganization of fixed assets is activated.System Response You <ZH>can...
FAGL_REORGANIZATION115
Account assignment with the value * is not permitted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAGL_REORGANIZATION116
All account assignment elements apart from one must have the value *
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.