‎2007 Mar 02 5:36 PM
Our FI team is asking me whether we can, without modification of standard code, protect two fields from entry on a standard screen (in this case ME22N and fields indicating tax exemption). I have been unable to find any authorization objects being checked at the field level in that transaction. I think I recall hearing once that all fields could be protected, however. Is this possible without code modification? If so, can you point me to the documentation?
Thanks,
Terry
‎2007 Mar 30 1:27 PM
Terry,
You could use a screen variant to hide a field on the screen. You can also use GuiXT as well. Has any of your FI configurators looked at the IMG to see if they can change the configuration? Have you run an authorization trace to see what objects are being checked?
‎2007 Mar 30 1:27 PM
Terry,
You could use a screen variant to hide a field on the screen. You can also use GuiXT as well. Has any of your FI configurators looked at the IMG to see if they can change the configuration? Have you run an authorization trace to see what objects are being checked?
‎2007 Mar 30 3:19 PM
Thanks, Ryan. I will pass on the suggestions to the functional team.
Yes, I ran an authorization trace, but it did not show anything different being checked when we accessed those fields against when we did not access those fields.
‎2007 Mar 30 3:45 PM
Terry,
You could also do a source code search for "screen-invisible" or "screen-active" and try to locate the area of code that can turns this field on or off. Once you locate the area that does this you can see what determines if whether it is off or on. You might even as an ABAPer to help you if you are not familiar with ABAP.