Skip to Content
avatar image
Former Member

DDIC user in report USR02

Hello All,

We are seeing DDIC user as logged on some times in security report USR02 .I want to know the reason why DDIC user is being reflecting in the security report USR02 because this user is not being used from intial stage.Only some standard BG jobs has been scheduled.If BG jobs are the reason then it should show user as periodically log on but it is being reflected only some times (irregular time intervals /not periodically)

Please let me know how to resolve this issue of DDIC user in security report USR02 or the reason why it is showing up in report.

Thanks in advance for the help,

Thanks,

raj

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Jun 01, 2010 at 08:39 AM

    I'm a bit confused... USR02 is a table... reports for users starts with RSUSR*...

    Regards

    Juan

    Add comment
    10|10000 characters needed characters exceeded

  • Jun 01, 2010 at 09:09 AM

    HI,

    Please compare DDIC login time with background jobs which ran at that time, consider only the jobs which has DDIC has its owner.

    Also use STAD or Audit logs to find out which programs or tcodes has been executed by ddic at that time.

    Regards

    prakash

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 01, 2010 at 09:44 AM

    Hi ,

    May be It's showing the DDIC user in log because you are using the DDIC in some of BG jobs.

    It's better to Enable Audilt logs through SM19 ,so that you will get the exact details like Time,Report,from which machine Etc..

    Moreover USR02 is table ,it's not a report ..

    Regards,

    Srinivas Ch.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 01, 2010 at 10:37 AM

    First you have to check whether you have protected DDIC or not?

    As USR02 is a table which can holds user login details, so forget about the background jobs first and check the user/password availability to others.

    If you felt DDIC is protected by admin/you and is not available for users, then try to find out the configured background jobs.

    Yes, i agree with above reply: Audit logs can help you in such type of situations.

    Regards,

    Nick Loy

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      So you're using the "last logon" field in USR02.

      Check table TBTC - Background Job Steps (see field AUTHCKNAM for job user).

      If you have DDIC in any of these, then this is your problem.

      You may also want to go check the following:

      - RFC connections INBOUND (i.e. log onto your other systems in the landscape and check SM59 connections).

      - Check RZ21 - CCMS background dispatching has not been configured with DDIC.

      - Any Microsoft .Net connectors in use in your environment.

      - Any other inbound connections from any other systems.

      - You could try locking the user and just monitoring all other systems.

  • avatar image
    Former Member
    Jun 01, 2010 at 01:04 PM

    You can try out by putting the trace ST01 on DDIC and probably this could help ,

    Add comment
    10|10000 characters needed characters exceeded