Do you have any question about this error?
Message type: E = Error
Message class: FAGL_DB - Messages for Package FAGL_DB_PERSISTENCY
Message number: 230
Message text: Postings cannot be made to ledger group &1 in current fiscal year &2
You are assigning a ledger group exclusively containing a subsequently
implemented ledger to a valuation area and have activated this valuation
area for postings to General Ledger Accounting.
However, the time of implementation (the migration date) of ledger &V1&
for company code &V3& falls after the current fiscal year in Asset
Accounting (&V2&).
It is <ZH>not yet</> possible to write Asset Accounting postings for
this valuation area to General Ledger Accounting because the ledger
assigned for the current fiscal year in Asset Accounting has <ZH>not yet
</> been activated in General Ledger Accounting. In this case, you
receive error message <DS:NA.FAGL_MIG115>FAGL_MIG 115</>.
It is not possible to perform depreciation runs or to switch fiscal
years in Asset Accounting.
Only assign a posting indicator that allows postings (posting indicator
<> 0) to the valuation area to be written to the subsequently
implemented ledger once the fiscal year preceding the implementation of
the ledger has been closed in Asset Accounting.
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.
FAGL_DB230
- Postings cannot be made to ledger group &1 in current fiscal year &2 ?The SAP error message FAGL_DB230 indicates that postings cannot be made to a specific ledger group in the current fiscal year. This error typically arises in the context of financial accounting when there are restrictions on posting to certain ledgers or periods.
Cause:
- Closed Fiscal Year: The fiscal year for the ledger group has been closed, preventing any further postings.
- Posting Periods: The posting period for the current fiscal year may be closed or not open for the specific ledger group.
- Configuration Settings: The configuration settings for the ledger group may restrict postings in certain scenarios.
- Document Type Restrictions: Certain document types may not be allowed for posting in the current fiscal year.
Solution:
Open the Posting Period:
- Navigate to the transaction code OB52 (Change Posting Periods).
- Check if the posting period for the ledger group is open for the current fiscal year. If it is closed, you may need to open it for the required period.
Check Fiscal Year Status:
- Ensure that the fiscal year is not closed in the configuration. You can check this in the transaction code OBY6 (Fiscal Year Change).
- If the fiscal year is closed, you may need to reopen it, but this should be done with caution and typically requires authorization.
Review Ledger Group Configuration:
- Go to the configuration settings for the ledger group in SPRO (SAP Reference IMG).
- Check if there are any specific settings that restrict postings for the current fiscal year.
Document Type Settings:
- Review the document type settings in OBY6 or OBA7 to ensure that the document type you are using allows postings in the current fiscal year.
Consult with Finance Team:
- If you are unsure about making changes to the posting periods or fiscal year settings, consult with your finance team or SAP administrator to ensure compliance with accounting policies.
Related Information:
By following these steps, you should be able to resolve the FAGL_DB230 error and successfully post to the ledger group in the current fiscal year.
Get instant SAP help. Start your 7-day free trial now.
FAGL_DB020
Inconsistency: Items not found in general ledger view
What causes this issue? For line item &V1&/&V2& (fiscal year &V3&, company code &V4&), there are no corresponding rec...
FAGL_DB018
Document &1 / &2 / &3 not found in ledger &4
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAGL_EMU001
Error during database insert/update: Table=&1, ledger=&2, company code=&3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FAGL_EMU002
Object key not found: Ledger=&1, object table=&2, account=&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.