Skip to Content

Logging into SAP GUI will empty the include file

Urgent:Logging into SAP GUI will empty the include file

As long as you log in to the system again, the recovered include files will be emptied again.

What should I do to find the destroyer and make the include files not empty anymore?

picture.png (5.6 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Nov 05, 2019 at 06:57 AM

    Edit in: (Geez, what happened to my comment..? I'll restore it later...)

    Edit in 2: Ok, here it goes again...

    That user - is it a dialog user? If yes, please check whether the affected system has logic in FM EXIT_SAPLSUSF_001 (Include ZXUSRU01) that tries to do something with Includes affected (like read via RFC from other system, then insert/modify the code...) .

    If there is no logic, then, depending on whether you can reproduce the behavior with your own User ID or just with the P*user, set up a Variant in transaction SAT for the user you'll be troubleshooting with, as follows:

    Then, make the user to logon, logoff, and start analyzing the Recording in SAT... What you are looking for are things like INSERT REPORT...

    Hopefully, that should help to pinpoint the culprit code, assuming it's some funny but unreliable custom code...

    Edit in 3: just checked if the login USER-EXIT will be picked up by SAT (it will) and this is the kind of stuff you should be looking for:


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 04, 2019 at 04:20 AM

    Hello ivan yee,

    Are you creating a version of your developments? Also follow the below steps to track the changes:

    Utilities-->Versions-->Version Management.

    You can also generate the version in the same path using GENERATE VERSION so that you can track the changes of your development.

    Can you please explain your requirement a bit further.


    scn.png (49.4 kB)
    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.