12-02-2015 10:45 AM
Hi All,
We have an security requirement in IE03 ,in IE03 after entering the equipment no and after that pressing enter button ,it will be open icon i.e. Service for objects .
Once after expanding the service for objects button ,attachment option is there,in that create, delete ,change option is there ,we have maintained in IE03 role only activity 03-display type .
Now we are unable to change or delete options in service for objects ,but still we are able to create ,we are unable to find any authorization objects to restrict creation.
Any one faced this type of issue or guide me how to achieve this .
Advance Thanks
12-02-2015 1:44 PM
Check out note http://service.sap.com/sap/support/notes/2244234 - for general setup of GOS (Generic Object Services) -related do's and don'ts search the the marketplace with Terms "GOS authorizations" .
12-02-2015 2:20 PM
Trx SHD0 Transaction/Screen Variants could be helpful for this usecase. You can try to deactivate the create icon.
12-02-2015 2:26 PM
Yes. Always a way out. Open a can full of worms with standard transaction variants where a simple authorization would do perfectly.
You do realize that GOS is part of dozens of transactions throughout the whole system and not only IE03, do you? Would you suggest creating a transaction variant for every transaction that is GOS-enabled?
12-02-2015 2:44 PM
Suggested SHD0 only for this particular transaction as an alternative way to solve requirement. But if you could recommend an appropriate authorization object is it the better solution.
12-03-2015 4:36 AM
Hi,
I have tried SHD0 still we are unable to control the create attachment option.
12-03-2015 4:37 AM
12-03-2015 11:34 AM
12-03-2015 2:01 PM
12-03-2015 2:06 PM
12-03-2015 2:44 PM
By researching the topic in question and finding out, how it works. Like in note 1539457. After the research is done, one can experiment/test.
EDIT: as for CREATE - if you disable this, you'll face serious problems in case you Exchange IDOC's that create/change equipments, because the realtionship between sender/receiver IDOC's is documented in GOS. As are several other things. I'd be ever so careful to disable this.