2006 Nov 16 8:33 PM
We randomnly created couple of test authorization objects in a BW sandbox using RSSM and after functional test, we would like to delete the same.
We also used several functions on RSSM like " Generate Complete Authorization for User" which will create a profile with the new auth. object and will assign a profile to your id.
Hence prior to deleting the same, we have removed the same authorization object from all our roles and profiles and when i execute the "where used" it still shows the object is used in SAP_ALL profile. I cannot edit this profile using su02 because it falls in SAP Name space.Should i delete the SAP_ALL profile and regenerate the profile using the SAP programs after deleting the authorization objects.
Any more idea's on how to delete these authorization objects? I know its very easy to say using RSSM, but practically little complex.
Can we really delete the authorization objects in BW 3.5?? I know in BI7.0 using RSECADMIN we can delete it..but not able to delete it..in 3.5
Looking for your tips and recommendations and sure will award points for best answers.
-Sreeni
We randomnly created couple of test authorization objects in a BW sandbox using RSSM and after functional test, we would like to delete the same.
We also used several functions on RSSM like " Generate Complete Authorization for User" which will create a profile with the new auth. object and will assign a profile to your id.
Hence prior to deleting the same, we have removed the same authorization object from all our roles and profiles and when i execute the "where used" it still shows the object is used in SAP_ALL profile. I cannot edit this profile using su02 because it falls in SAP Name space.Should i delete the SAP_ALL profile and regenerate the profile using the SAP programs after deleting the authorization objects.
Any more idea's on how to delete these authorization objects? I know its very easy to say using RSSM, but practically little complex.
Can we really delete the authorization objects in BW 3.5?? I know in BI7.0 using RSECADMIN we can delete it..but not able to delete it..in 3.5
Looking for your tips and recommendations and sure will award points for best answers.
-Sreeni
2006 Nov 17 8:36 AM
Hi
Have you tried to delete it from transaction SU21 - I think you would be able to delete from within here, without having to delete the SAP_ALL Profile.
Regards
Morten Nielsen
2006 Nov 17 6:13 PM
Hi Morten,
I still get the same error, it says the authorization object is used in some profiles and gives me the list of all deleted profiles and the list does not contain SAP_ALL.
But the RSSM where used option shows that the authorization object is still assigned to SAP_ALL and some of the profiles which are already deleted in the system.
Regards
Sreeni
2006 Nov 17 11:39 PM
remove the fields and delete the object from RSSM. then it should automatically
generate the SAP_ALL profile. You can see the message saying SAP_ALL generated.If not just generate the SAP_ALL from SU21 and then check for the Where used list. It should work.
2006 Nov 18 6:27 PM
I found that the profiles created automatically using the same authorization object should never be deleted before deleting the authorization object. We need to just remove the users from the profiles and try deleting the authorization objects, then SAP will automatically delete the profiles and regenerates the SAP_ALL profile and deletes the authorization object.
-Sreeni