topic Re: Restrict delete folder option in SBWP transaction Code in Application Development and Automation Discussions

Restrict delete folder option in SBWP transaction Code

Former Member — Tue, 21 Jul 2009 16:10:08 GMT

Is there any way to restrict the delete folder option in SBWP (Business Work Place) ? The users are deleting the folders and it is causing the problem.

Please advise.

Appreciate the help.

Thanks.

Regards,

Archana

Re: Restrict delete folder option in SBWP transaction Code

Former Member — Tue, 21 Jul 2009 17:05:17 GMT

Hi,

Please check the values in auth object S_WFAR_OBJ for this. The best way to pin point the auth object to take a trace during deletion and remove activity 06 for deletion. Please check and let us know if any issue.

Regards

Aveek.

Re: Restrict delete folder option in SBWP transaction Code

Former Member — Wed, 22 Jul 2009 07:05:57 GMT

In order to restrict the user for deleting a folder ,user Authoriation object S_WFAR_OBJ

Additonally , you can also restrict access to archived documents

S_WFAR_OBJ archive objects

There are mainly 3 fields in this authorization object :OAARCHIV,OAOBJEKTE & OADOKUMENT

Defined fields

OAARCHIV

Access authorization for physical archives is checked.

OAOBJEKTE

The access authorization can be distinguished according to the object types.

OADOKUMENT

Using this authorization field, the access to document types can be checked.

ACTVT

Using activiy Access modes to archived documents can be defined. The following activities are possible:

here in activity field you can UNCHECK the 06

06: Delete

This authorization will restict the user to delete folder.

Regards

Vikas

Re: Restrict delete folder option in SBWP transaction Code

jurjen_heeck — Wed, 22 Jul 2009 07:18:31 GMT


> In order to restrict the user for deleting a folder ,user Authoriation object  S_WFAR_OBJ

If you must copy-paste from an old version of SAPhelp (http://help.sap.com/saphelp_40b/helpdata/fr/73/174b6e5733d1118b3f0060b03ca329/content.htm) please mention the original page location as well.

Re: Restrict delete folder option in SBWP transaction Code

Former Member — Thu, 23 Jul 2009 10:43:07 GMT

Also you may take Authorization trace to know the required authorizations for deleting folders... Authorizations can be restricted accordingly.

Regards,

Sandip

Re: Restrict delete folder option in SBWP transaction Code

Former Member — Thu, 22 Jul 2010 10:57:42 GMT

No, we hid some testing, by removing 06 activity in s_wfar_obj auth object. But no success. Instead we found one object s_oc_role, where we can restrict. But everything gets restricted including create, change, and all the tabs get disabled.

So as per me, there is no possible way for restricting delete folder option in SBWP.

If anybody knows then please comment on the same.

Regards,

Sourabh

IBM

Re: Restrict delete folder option in SBWP transaction Code

Former Member — Thu, 22 Jul 2010 10:57:48 GMT

No, we did some testing, by removing 06 activity in s_wfar_obj auth object. But no success. Instead we found one object s_oc_role, where we can restrict. But everything gets restricted including create, change, and all the tabs get disabled.

So as per me, there is no possible way for restricting delete folder option in SBWP.

If anybody knows then please comment on the same.

Regards,

Sourabh

IBM

Re: Restrict delete folder option in SBWP transaction Code

Former Member — Thu, 22 Jul 2010 11:57:34 GMT


> No, we did some testing, by removing 06 activity in s_wfar_obj auth object. But no success. Instead we found one object s_oc_role, where we can restrict. But everything gets restricted including create, change, and all the tabs get disabled. 
> 
> So as per me, there is no possible way for restricting delete folder option in SBWP. 
> 
> If anybody knows then please comment on the same. 
> 
> Regards,
> Sourabh
> IBM

I like to dissent.

S_OC_ROLE is the object you are looking for. By disabling the '*' or 'ADMINISTRATOR' value you restrict users so they cannot create/change/delete shared folders.

Which makes perfect sense to me - if I do not want the end-users to delete shared folders, I sure as hell do not want them to be able to change existing ones (might contain distribution list) and most decidedly I don't want them to create some! They can do that with private folders ... but not shared ones - I mean, who would regularly clean up the mess?

So, yes - you can restrict: on level of shared folders.