Do you have any question about this error?
Message type: E = Error
Message class: FIN_FB_RECON - Conversion to S/4HANA: Reconciliation
Message number: 130
Message text: Ledger &3 is marked as average balance ledger of &4 for table GLT0
The system checks table GLT0 to see if it contains entries for other
ledgers that are neither 00 nor multi-currency ledgers.
Ledger &V3& is defined for totals table GLT0 with sub-application &V2&
as an average balance ledger of ledger &V4&. This constellation is not
supported in SAP S/4HANA Accounting because this ledger will no longer
be updated.
The data is still available after migration but not in its current form.
If you want to continue to see the data in its current form, clarify in
a customer-specific project before migration to SAP S/4HANA Finance as
to how you want to handle the data.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
For more information, see
<DS:URLA.HTTPS://LAUNCHPAD.SUPPORT.SAP.COM/#/NOTES/2714344>SAP Note
2714344.</>
Error message extract from SAP system. Copyright SAP SE.
FIN_FB_RECON130
- Ledger &3 is marked as average balance ledger of &4 for table GLT0 ?The SAP error message FIN_FB_RECON130 indicates that there is an issue with the configuration of the ledger in relation to the average balance ledger settings. Specifically, it suggests that the ledger you are trying to use is marked as an average balance ledger, which may not be appropriate for the operation you are attempting to perform.
Cause:
- Ledger Configuration: The ledger (&3) is configured as an average balance ledger for the company code (&4) in the system. This means that it is set up to handle average balance calculations, which may not be compatible with certain transactions or postings that require a different ledger type.
- Transaction Type: The transaction you are trying to execute may not support average balance ledgers, leading to this error.
- Data Consistency: There may be inconsistencies in the data or configuration settings related to the ledger.
Solution:
Check Ledger Configuration:
- Go to the configuration settings for the ledgers in your SAP system (Transaction Code: OB22).
- Verify if the ledger is indeed marked as an average balance ledger and assess whether this is appropriate for your business needs.
Change Ledger Type:
- If the ledger should not be an average balance ledger, you may need to change its configuration. This can involve unchecking the average balance ledger option or creating a new ledger that is not marked as such.
Review Transaction:
- Ensure that the transaction you are trying to execute is compatible with the ledger type. If it requires a different type of ledger, consider using the appropriate ledger for that transaction.
Consult Documentation:
- Review SAP documentation or help resources for more details on average balance ledgers and their intended use cases.
Contact SAP Support:
- If you are unable to resolve the issue through configuration changes, consider reaching out to SAP support for assistance.
Related Information:
By following these steps, you should be able to address the FIN_FB_RECON130 error and ensure that your ledger configuration aligns with your business processes.
Get instant SAP help. Start your 7-day free trial now.
FIN_FB_RECON111
Documents in ledger &1 are incorrectly created in table &4
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FIN_FB_RECON110
Balances in ledger &1 are incorrectly created in table &4
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FIN_FB_RECON132
Ledger &3 is maintained for table GLT0 with subapplication &2
What causes this issue? Ledger &V3& is maintained inconsistently in customizing. It is defined for totals table GLT0 with sub application &am...
FIN_FB_RECON139
Field KSL of &2 does have a non initial Amount (Ledger &3)
What causes this issue? There are entries in the table &V2& for which at least one of the fields KSLVT, KSL01, KSL02, KSL03, KSL04, KSL05, KS...
Click on this link to search all SAP messages.