10-16-2006 10:07 PM
Can some one please tell me how to set PID and values(Parameter ids) which will default upon every user creation.
thnx.
10-17-2006 8:02 AM
hi syed,
You can fill fields on screens with default values from SAP memory using parameter IDs. It is the same as SPA and GPA.
Parameter IDs are stored in the table <b>TPARA</b>. They can be created from <b>SE80</b>. Choose Edit Object->Choose tabstrip "More" and then choose the radiobutton Set/Get Parameter ID
Below example is from <b>SAP Help</b>.
For example, a user only has authorization for company code 0001. By entering the value '0001' in field COCD in the Parameter register in this user’s master record (SU01), the system automatically fills the field Company code with the value ‘0001’ on all screens he or she calls. If this company code is not predetermined using a parameter ID in the user master record, the system automatically adopts the first value entered by the user at the beginning of the transaction for the rest of the current terminal session. However, this value has to be re-entered the next time the user logs on to the system.
Regards
Alfred
<points_begging_removed_by_moderator>
Message was edited by: Julius von dem Bussche
10-17-2006 8:02 AM
hi syed,
You can fill fields on screens with default values from SAP memory using parameter IDs. It is the same as SPA and GPA.
Parameter IDs are stored in the table <b>TPARA</b>. They can be created from <b>SE80</b>. Choose Edit Object->Choose tabstrip "More" and then choose the radiobutton Set/Get Parameter ID
Below example is from <b>SAP Help</b>.
For example, a user only has authorization for company code 0001. By entering the value '0001' in field COCD in the Parameter register in this user’s master record (SU01), the system automatically fills the field Company code with the value ‘0001’ on all screens he or she calls. If this company code is not predetermined using a parameter ID in the user master record, the system automatically adopts the first value entered by the user at the beginning of the transaction for the rest of the current terminal session. However, this value has to be re-entered the next time the user logs on to the system.
Regards
Alfred
<points_begging_removed_by_moderator>
Message was edited by: Julius von dem Bussche
10-17-2006 12:57 PM
10-17-2006 10:45 AM
The users can do this themselves either by using a transaction (some of them will "remember" the PID for subsequent transactions), or, via SU3 (System -> User Profile -> Own data).
By implication, they might also change the PID's if you set it for them.
10-18-2006 11:04 AM
Well, it is important to point out that the "user parameters" (aka "GET/SET parameters") must <u>not</u> be used for access control purposes (authorizations). They are just an offer of the system to memorize (frequently used) entry values.
Technically it works like this:
Dynpro field => data element => parameter ID => lookup in current session context (which will be prefilled during logon with the persisted user parameters)
Cheers, Wolfgang
09-21-2007 9:49 PM
Wolfgang,
> Well, it is important to point out that the "user
> parameters" (aka "GET/SET parameters") must
> <u>not</u> be used for access control purposes
> (authorizations).
I agree with you and wonder why SAP chose parameter SD_VARIANT_MAINTAIN to grant authorization to save user or system variants.
Is there any way to prevent users from adding or changing this parameter in SU3?
Matthias
12-18-2013 3:38 PM
> Is there any way to prevent users from adding or changing this parameter in SU3?
No, if you allow to maintain user parameters, e.g. using transaction SU2 or SU3, than the user can choose all of them.
There are no checks restricting parameter names or user exits in module READ_TC_PARAM in include LSUU5I01.
Kind regards
Frank