This website is not affiliated with, sponsored by, or approved by SAP AG.

FIXED - SHD0 or restrict user access to certain fields in SO

Development (ABAP Development WorkBench, ABAP/4 programming)

Moderators: thx4allthefish, Snowy, Gothmog, YuriT

FIXED - SHD0 or restrict user access to certain fields in SO

Postby ggsap » Fri Nov 12, 2010 8:25 am

Hi All
I have a scenario in which i need to restrict 2 users in the sales order screens VA01 and VA02.
The first user "should" be able to change the payment terms (VBKD-ZTERM) field in the VA01 and VA02 screen and the second user "should not" be able to change the payment terms (VBKD-ZTERM) field in the VA01 and VA02 screen . Both users are for order type OR
I have done the following so far.
1. I tried to creating 2 variants (ZV1 and ZV2)in SHD0 for sales order and assigned it to 2 "Z" Transactions created in SE93. But that has no effect. I am not sure why that is the case.
2. In V0V8 there is a variant attachment possible but it can take only one variant. Also it does not help as it is not user specific.
is there a specific way to do it or am i doing something wrong ?
Thanks in advance for any help
ggsap

Last edited by ggsap on Mon Dec 13, 2010 3:37 am, edited 1 time in total.
Thanks and Regards
ggsap
 
Posts: 113
Joined: Wed May 03, 2006 4:31 pm
Location: India

Re: SHD0 or restrict user access to certain fields in SO

Postby ggsap » Wed Nov 17, 2010 8:30 am

Hi there,
Any ideas or clues for me ?
Thanks
ggsap
ggsap
 
Posts: 113
Joined: Wed May 03, 2006 4:31 pm
Location: India

Re: SHD0 or restrict user access to certain fields in SO

Postby Baz » Wed Nov 17, 2010 9:30 am

you cannot have two transaction variants assigned to the same sales order type. it only allows one.

have you tried seeing if you can control it via authorisations?

i am shadowing this in the security forum as those bright sparks may shed some light on whether this is possible by Role/Authorisations.
Baz

AsPiRiNg tUlY iDiOt Image

http://www.catb.org/~esr/faqs/smart-questions.html

Image

check out my Podcasts http://dj-baz.podomatic.com
Baz
 
Posts: 4704
Joined: Fri Nov 08, 2002 5:54 am
Location: dirt box Derby

Re: SHD0 or restrict user access to certain fields in SO

Postby thx4allthefish » Wed Nov 17, 2010 9:42 am

This cries loudly for an abapper.

No way we sec-admins can do anything for you on field-level.

Try enhancements, someplace in MV45AFZZ.

:D :D Now I am shadowing this in ABAP/Security.
curiousorange wrote:I give up. Humanity isn't worth saving. Why is there never a Vogon Constructor Fleet around when you really need one?
thx4allthefish
 
Posts: 6371
Joined: Sat Oct 26, 2002 6:18 pm
Location: barolo barrel

Re: SHD0 or restrict user access to certain fields in SO

Postby Gothmog » Wed Nov 17, 2010 10:16 am

I'd agree checking an authorisation object (specific if no standad is appropriate) in a user-exit.
EXIT_SAPMV45A_004 (extension V45A0003) should do the trick.
68 74 74 70 3a 2f 2f 74 69 6e 79 75 72 6c 2e 63 6f 6d 2f 62 64 6f 37 6d 77 67
Gothmog
 
Posts: 1467
Joined: Wed Sep 12, 2007 4:46 am
Location: Probably not home

Re: SHD0 or restrict user access to certain fields in SO

Postby ggsap » Thu Nov 18, 2010 5:44 am

Hi everybody
Thanks for the update. I will check with my basis and ABAP team and see what can be done to resolve this.
Thanks
ggsap
Thanks and Regards
ggsap
 
Posts: 113
Joined: Wed May 03, 2006 4:31 pm
Location: India

FIXED - SHD0 or restrict user access to certain fields in SO

Postby ggsap » Mon Dec 13, 2010 3:39 am

Hi All
After a lot of deliberations we have deicded that it is not possible to limit the access to change the ZTERM (payment trem) for certain users through functional configuration.
We will reconvene at a later stage to discuss what can be done through ABAP coding changes.
thanks for your inputs on this.
Regrads
ggsap
Thanks and Regards
ggsap
 
Posts: 113
Joined: Wed May 03, 2006 4:31 pm
Location: India


Return to ABAP

Who is online

Users browsing this forum: Google Adsense [Bot] and 15 guests




This website is not affiliated with, sponsored by, or approved by SAP AG.