topic Re: Restricting a field in Application Development and Automation Discussions

Restricting a field

Former Member — Thu, 10 Jul 2008 08:31:18 GMT

Hello everyone,

I have a question: I want to restrict a field(e.g. Tax Code, in transaction xk01), so that only users with SAPALL, would be able to see and add data in that field!

Thanks a lot!!!

Re: Restricting a field

Former Member — Thu, 10 Jul 2008 08:44:08 GMT

See whether this would help you.

SELECT-OPTIONS s_Taxcode FOR ........... NO INTERVALS

SELECT-OPTIONS: s_Taxcode for ........NO-EXTENSION NO INTERVALS

Find the code below.

REPORT ZEX_SELECTOPTIONS.

Tables: ......,

.......

Data: int_vbak type vbak occurs 0 with header line.

Select-options: s_taxcode for ....... NO-EXTENSION NO INTERVALS.

Select * INTO int_VBAK from VBAK where

VBELN in s_vbeln.

APPEND int_VBAK.

CLEAR int_VBAK.

ENDSELECT.

Loop at s_taxcode.

WRITE: / 'SIGN:', s_taxcode-sign,

'OPTION:', s_taxcode-option,

'LOW:', s_taxcode-low,

'HIGH:', s_taxcode-high.

Endloop.

loop at int_vbak.

Write:/ int_vbak-vbeln, int_vbak-AUART.

endloop.

i am not sure with these fields, please replace with your fields..

Regards

Divya

Re: Restricting a field

Former Member — Thu, 10 Jul 2008 08:44:59 GMT

Go to PFCG and remove authorization for those transactions which you do not want to give them, or create the new profile for those users.

Regards

Divya

Re: Restricting a field

Former Member — Thu, 10 Jul 2008 08:50:17 GMT

I will check all your answers. Regarding PFCG, i cannot use that, because i only want to restrict a field, not the whole transaction.

Anyway, thank you very much for your help. I'll keep in touch with solving this problem.

Regards,

George

Re: Restricting a field

Former Member — Thu, 10 Jul 2008 09:21:05 GMT

Hi George

SAP is providing us a concept called Screen Variants and Transaction variants.

Features :

Inserting default values in fields

Hiding and changing the ready for input status of fields

Hiding and changing the attributes of table control columns

Hiding individual menu functions

Hiding entire screens

Transaction variants are actually made up of a series of screen variants. The field values and field attributes for each screen in a transaction variant are stored in screen variants. Each variant is assigned to a transaction. Variants may, however, contain values for screens in multiple transactions, if transaction flow makes this necessary. The transaction the variant is assigned to serves as its initial transaction, whenever you start the variant.

Both client-specific and cross-client transaction variants exist. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction.

A specific namespace has been designated for cross-client transaction variants and screen variants and they are both automatically attached to the Change and Transport System. Client-specific transaction variants can be transported manually.

Transaction and screen variants may be created for all dialog and reporting transactions. However, there are certain restrictions that apply to their use, depending on how their corresponding transactions have been realized internally.

Transaction variants may not be created for transactions already containing pre-defined parameters (parameter transactions and variant transactions).

You can only create transaction variants for dialog transactions and reporting transactions.

Only "normal" screens, dialog boxes, and subscreens can be included in the variant.

Screen variants are automatically created anytime you create a transaction variant.

For This I am Giving The Simple Flow.

Go to Transaction SHD0.

Transaction Code: XK01

Click On transaction variants Tabs.

provide any name .

Click on Create .Then It will go to XK01

Click on Enter

Then for the field which should be greyed out tick under :Output only

Click on Save and Exit.

if Found helpfull do reward.

Regards.

Eshwar

Re: Restricting a field

Former Member — Thu, 10 Jul 2008 09:51:40 GMT

Hi,

I doubt you can suppress/hide this field, but you can do a validation or set to default value the users other than background user.

Try this user exit : EXIT_SAPMF02D_001

If the hint is usefulu2026 Say thanks by rewardu2026.

Regards,

Prabhu Rajesh

Edited by: PrabhuRajesh Janardanan on Jul 10, 2008 11:52 AM