Reply: 2

Auto translated

Change G/L account context in multiple languages with LSMW

Is it possible to change several texts of several G/L accounts in several languages (also in the chart of accounts language) using LSMW? Or is there another possibility? LSMW with FST2 does not work because the chart of accounts language cannot be changed here. FSP0 does not work either. Changing the texts manually is not desirable as it affects too many G/L accounts.

You must be logged in to post a reply.

Login now

2 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.

    In SAP, there are actually different ways to make mass changes to G/L accounts, especially when it comes to maintaining texts in different languages. LSMW (Legacy System Migration Workbench) is a common tool for such mass data changes, but you will encounter limitations, as you have correctly noticed, especially when it comes to changing texts in the chart of accounts language. ### Alternative methods for mass changes to G/L account texts: 1. SAP Mass Maintenance (MASS Transaction): The MASS transaction allows you to make mass changes to a variety of objects, including G/L accounts (FI-GL). With this transaction you can change fields such as account description (texts) in different languages. The advantage here is that using MASS is often easier than LSMW, and it could be more effective when it comes to editing texts in different languages. 2. Writing directly to the database tables: This can be done via an ABAP program written specifically for mass updating these texts according to certain criteria. This route should be considered with caution as direct changes to the SAP database tables (e.g. SKAT for G/L account descriptions) carry risks and require test runs in a sandbox environment before being deployed in a production environment. 3. eCC Data Migration Workbench (eCATT):** Another tool that can be used is eCATT, which can be used effectively for complex data migrations and mass change requests. eCATT provides the flexibility to create test scenarios that can then be used for mass data processing. 4. SAP S/4HANA Migration Cockpit: If you are using SAP S/4HANA, the Migration Cockpit provides pre-built migration objects that can be used for mass data migration. For more specific requirements like yours, customer-specific migration objects can be configured ### Recommendations: - Check the possibilities and limitations of each method: Each method has its advantages and disadvantages. For example, MASS offers a simple user interface and possibly a no-coding solution, while ABAP programming offers great flexibility but requires more technical expertise - Always perform tests: Regardless of which method you choose, you should always perform extensive testing in a non-production environment to ensure that the changes are applied correctly and that there are no unintended side effects.

    • Documentation:** Make sure that all changes are well documented to ensure traceability and compliance. By considering these options, you can find a suitable solution for mass updating G/L texts in multiple languages without having to resort to manual processes.

    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.

  • User #45159
    User #45159 (Author)

    Hello,

    I have now solved it with OB_GLACC13. Do not enter anything in the upper fields for the mass change (where the mass change, e.g. field status change for several G/L accounts, is normally specified) and copy and paste into the lower fields for each language.

    LG