SU01 - User and Role Change Documents show conflicting information

[Former Member]

We have an issue with our audit group.

In SU01 - the Display Change Document for Role Administration shows that a new role was created on 9/4/08.

In SU01 - the Change Documents for Users shows that the profile for the new role was added to a user on 8/21/08, which is prior to the role being created.

How could this happen? Any ideas?

Thanks!

[charmaine_greene]

Hi

In SU01 - the Change Documents for Users shows that the profile for the new role was added to a user on 8/21/08, which is prior to the role being created.

I recall seeing something similar in a recent thread which suggest maybe this is in US format and should read 21/08/08 - but I don't understand why the change document date formats should be different for users and roles yet

Check out the thread Link: [can you add a profile to user that has already been deleted? ]

Regards

Charmaine

[Former Member]

Please take note that upgrading to the metric system might be offered as a conversion service in future as well...

Cheers,

Julius

[Former Member]

Hi Margaret,

This is possible...

Suppose as an example, if you have a role Z:ABC in your QA client & you upload the same role in Development client, that already exists, you will get a red light indicating that the role already exists. If you still choose to overwrite it, the role in Development client will take the date of the uploaded date (as in role creation) but the profile's date does not change in Development client for the role, the profile will still carry the old date. Hence you see this date problem. There is no issue with date formats as in US or the rest of the World.

Hope it helps

Also, you must be seeing this change in SUIM & not in SU01

Regards,

Siddhartha

Edited by: Siddhartha Varma on Jan 16, 2009 4:34 PM

[Former Member]

I had this happen after a client copy. If the role data is copied but the user data isn't this could occur.

[Former Member]

Its probably a case where role has been overlaid somehow ..

possible ways can be :-

because of client copy

because somebody uploaded and downloaded the roles from somether system, where role was created later.

[Former Member]

Good observation!