How To Fix 64661 - Inconsistency between FI general ledger and SEC subledger (see long text)

SAP Error Message - Details

• Message type: E = Error

• Message class: 64 - Treasury Management: Securities

• Message number: 661

• Message text: Inconsistency between FI general ledger and SEC subledger (see long text)

What causes this issue?

FI documents were reversed, although entire reversal activity was
terminated due to error messages (see log).

System Response

The activity was not reversed in the subledger.
The FI documents listed in the log were, however, already reversed.
There is therefore an inconsistency between the securities subledger
and the FI general ledger, due to the fact that the activity was not
reversed in the subledger, while it was fully or partly reversed in the
general ledger.
If you attempt to reverse the activity again from the securities
subledger, the reversal will terminate with the error message that one
or more FI documents have already been reversed.

How to fix this error?

Using the daybook number specified in the reversal posting log,
identify all FI documents which are contained in the activity using the
posting journal.
Check whether these FI documents have been reversed in FI. If not,
reverse them using transaction FB08 in Financial Accounting.
Finally, reverse the entire activity from the securities subledger.
Choose the option 'only reverse in subledger' to ensure that only the
flows in the subledger are reversed. The system will no longer try to
reverse the FI documents which have already been reversed.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 64661 - Inconsistency between FI general ledger and SEC subledger (see long text) ?

  The SAP error message 64661 indicates an inconsistency between the Financial Accounting (FI) General Ledger and the Special Purpose Ledger (SEC) subledger. This inconsistency can arise due to various reasons, such as incorrect postings, missing entries, or issues during data migration or system upgrades.
  Cause:
  
  Posting Errors: Transactions may have been posted to the General Ledger without corresponding entries in the SEC subledger.
  Data Migration Issues: During data migration or system upgrades, some entries may not have been transferred correctly.
  Manual Adjustments: Manual adjustments in either the General Ledger or the SEC subledger that do not match can lead to inconsistencies.
  Configuration Issues: Incorrect configuration settings in the system can also lead to discrepancies between the two ledgers.
  
  Solution:
  
  Analyze the Inconsistency: Use transaction codes like FB03 (Display Document) or FBL3N (G/L Account Line Items) to review the entries in both the General Ledger and the SEC subledger.
  Reconcile Entries: Identify the specific entries that are causing the inconsistency. You may need to reconcile the amounts and ensure that all transactions are reflected in both ledgers.
  Adjust Entries: If you find missing entries in the SEC subledger, you may need to post the necessary adjustments to ensure that both ledgers are aligned.
  Check Configuration: Review the configuration settings for both the General Ledger and SEC subledger to ensure they are set up correctly.
  Run Reports: Use SAP standard reports to identify discrepancies. Reports like S_ALR_87012357 (G/L Account Balances) can help in identifying inconsistencies.
  Consult SAP Notes: Check for any relevant SAP Notes that may address known issues related to this error message.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE16 (Data Browser) to check table entries, and S_ALR_87012357 for reporting.
  SAP Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it involves complex configurations or data integrity issues.
  Documentation: Review SAP documentation and guides related to Financial Accounting and Special Purpose Ledger for best practices in maintaining consistency between ledgers.
  
  By following these steps, you should be able to identify and resolve the inconsistency indicated by error message 64661.