Solved: Field exit is not working for a user

Former Member · ‎2011 Jul 29

Hi,

We have implemented a field exit in ME12 to change the purchase info record short description. It is working fine for most of the users except for some users. I just wanted to know is there any way we can restrict the field exits based on Authorization

Did any one faced this kind of issues

Bhanu

Former Member · ‎2011 Aug 01

Hi,

Thanks for the reply, yes we have checked SU53 and found authorization failed for VA03 display but am not sure how PIR is linked to VA03 display and how this can restrict a Field exit trigger?

We are working on this authorization issue, will update if this gets resolved by adding VA03 display.

Is there any other reason for this?

Thanks,

Bhanu

madhu_vadlamani · ‎2011 Jul 29

Hi Bhanu,

Check this link [;

Regards,

Madhu.

Former Member · ‎2011 Aug 01

Thanks, Madhu for your reply.

The link which you gave me is very help full, but my issue is not solved. I tried activating the trace for the user for activity to find out the authorization objects involved but it is also not much helpful. Only diff i can see is the field exit is not part of trace in P system. am not sure about the exact problem here. Since it is happening only for some users...and it is becoming major now ..

is any one can help me to give any ideas in this to me?

Thanks,

Bhanu

Former Member · ‎2011 Aug 01

hello,

as i know you can't implicitly add authorization check (just writing the code/check inside your field exit). I think it could be related with roles assigned to specific user. Did you check SU53 tcode after unsuccessful attempts to activate your custom field exit.

br,

dez_

Former Member · ‎2011 Aug 01

Hi,

Thanks for the reply, yes we have checked SU53 and found authorization failed for VA03 display but am not sure how PIR is linked to VA03 display and how this can restrict a Field exit trigger?

We are working on this authorization issue, will update if this gets resolved by adding VA03 display.

Is there any other reason for this?

Thanks,

Bhanu

Sandra_Rossi · ‎2011 Aug 01

Hi,

Reason could be that users are logged on different servers : check that profile parameter abap/fieldexit is set equally in all application servers.

If it's okay, then you'll find the reason only by tracing 2 users, one which is okay, the other not, doing exactly the same thing. To do that, use SE30 with a variant with "no aggregation", as Olga explains in her blog ([SDN blog: ABAP Runtime Analysis (SE30) - How to analyze ABAP program flow|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4847/17050 [original link is broken] [original link is broken] [original link is broken] ]). Then you compare the 2 traces to see from which point execution differs. You can use SAT transaction, available from 7.0, to compare 2 traces far more quickly.

BR

Sandra

Former Member · ‎2011 Aug 02

Thanks for reminding me this Sandra. I have cross checked all the servers and instance profiles, only one instance profile does not have the parameter and user is using the same app server. We have changed it and everything is working as expected. Thank you very much for making me to cross check all the instance profile parameters.

Thanks,

Bhanu