Authorisation restriction for rules in OOCU_RESP

[Edward Diehl]

Hi Karl,
Using transaction SHD0 create a transaction variant for OOCU_RESP for each responsibility rule to be maintained.  Then using SE93 created a custom transaction and select "Transaction with variant" and specify transaction OOCU_RESP and the variant you just created.
 
Then you can assign the custom transaction to the appropriate security role(s) and nobody ever executes OOCU_RESP directly.
 
I do this all the time with SM30 for custom table maintenance.  
 
Hope this helps.
Ed



Subject: Authorisation restriction for rules in OOCU_RESPDate: Tue, 5 Aug 2008 11:41:51 +1000From: Karl.Nietz at BHPBilliton.comTo: sap-wug at mit.edu

Hi,
Is it possible to limit access to specific rules when using OOCU_RESP?  We have a business scenario whereby nominated users need to update a specific rule in an environment, but should not be allowed to update any other rules within that environment due to data sensitivity.  I could not easily find an authorisation object that related to workflow rules.
Thanks.
Karl NietzGSAP Workflow Architect  & Support Team LeaderCSC MelbournePh:   61 3 86951157Mob: 61 434 181303 




This message and any attached files may contain information that is confidential and/or subject of legal privilege intended only for use by the intended recipient. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, be advised that you have received this message in error and that any dissemination, copying or use of this message or attachment is strictly forbidden, as is the disclosure of the information therein. If you have received this message in error please notify the sender immediately and delete the message.
_________________________________________________________________
Get more from your digital life.  Find out how.
http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home2_082008
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080805/25e81a2e/attachment.htm