Reply: 1

Auto translated

S4H conversion source ledger

Hello everyone,

I urgently need an assessment of the following issue:

In step R21 of the migration, the error FINS_RECON 108 (00 1000 2012 GLT0_BCK: Balances posted to ledger 00 are not migrated) came up for certain FYs. I then adjusted the settings as follows:

Ledger 0L company code * FY 1900 source ledger 0L

Ledger 0L company code 1000 FY 2012 source ledger 00 (I added this entry)

The error was then gone and there were no errors regarding the balances, and the verification lists always matched.

The problem is that the customer never used the old general ledger and no actual values are stored in GLT0. According to (possibly incorrect) customizing, he should pull everything from 2012 onwards from GLT0 and not from FAGLFLEXT. However, it must have somehow ignored the added customizing entry and only paid attention to the entry with Quelledger 0L, as there are definitely values there and the verification lists match.

Does anyone have an explanation for this? Should the customizing be reversed shortly before the productive conversion so that only the first entry is present, since the verification lists match, or would you keep the customizing?

I'm a bit at a loss at the moment.

Thank you in advance for your assessment!

You must be logged in to post a reply.

Login now

1 Answers

  • BETA
    ChatBot
    Automated answer
    This reply was automagically generated by our Espressi A.I. Think of it as a one-off attempt to instantly solve your problem. It will not respond to further replies.

    Hello and thank you for your inquiry about the challenges during the R21 migration step in the SAP system. The situation you describe involves some specific customization details that need to be considered carefully in order to arrive at an effective solution. First, the error FINS_RECON 108 is due to the fact that balances posted in the old ledger (specified here as "00") were not migrated to the new Universal Ledger. The fact that the entry for the 2012 financial year and company code 1000 initially corrected the error is an interesting point. This indicates that a customizing entry was necessary for these balances to be migrated correctly. It is crucial to understand that if, according to your description, the customer never used the old General Ledger, and no ACTUAL values are stored in GLT0, then there is no need to migrate balances from GLT0. The fact that the verification lists are still consistent indicates that the data could be correctly pulled from FAGLFLEXT or another source. Here are a few steps you can check or consider: 1. Verify the data sources: Validate where the data is actually being pulled from. This can be done via test migrations with detailed logging of steps and data sources. 2. Customizing Reset: If it is determined that GLT0 should not be used, it may be safer to reset customizing and keep FAGLFLEXT as the primary source to avoid inconsistencies in the production implementation. 3. SAP Notes and Documentation: Look for specific SAP notes or in the SAP community or documentation for similar cases and solutions. Often these resources give a good indication of how such situations can be handled. 4. Collaborate closely with SAP Support (if available): In such specific cases, SAP Support can provide more direct and customized assistance 5. Testing: Before final changes are made, extensive test runs should be performed in a test environment to verify the results of the migration before they are implemented in the production environment. The decision to reverse customizing settings just before production conversion should be based on a solid foundation of test results and a thorough analysis of current and required data sources. It sounds like for your specific situation, thorough testing and validation is the best way forward to avoid potential problems during the production conversion.

    Need more help from our chatbot? Click here and visit our AI SAP Helper on the SAP learning platform et.training.1

    1. log in with your Espresso Tutorials account. Digital subscription or trial access required.