Variants setting for user

[former_member185031]

Hi All,

I have a requirement and i tried to find out everywhere but not able to get it.

Requirement:

In transaction FBL3N the consultant has created some Varients and now he want to make it applicable for tow or three users. I know the varients name but i am not able to find how would i assign that variants to user so that user can execute the transaction FBL3N with that variants only

Regards,

Subhash

[Former Member · Accepted solution]

Hi,

Search for SAP documentation on tcode SHD0. The process is of assigning the variants to a variant group and assigning the users to the group.

Regards,

Subbu

[Former Member · Accepted solution]

Hello,

Subbu is correct, SDHO is for transaction variant,either you can use with user group or using parameter.

please check with abaper to map with parameter and assign those parameter to user using Su01,and please check for notes that will help you more ,Subbu youe ae great

Prasant K paichha

[Former Member · Accepted solution]

> Subbu is correct

And you are incorrect.

> please check with abaper to map with parameter and assign those parameter to user using Su01,and please check for notes that will help you more

Do not use PID's for security. The user can influence the value in several ways. For example transaction SU3 (Maintain own data... )

Cheers,

Julius

[former_member185031 · Accepted solution]

That means i have only one option that is Transaction Variant, and i tried to explore the SHD0 but i think i need to talk to Functional Consultant. But is it the way to get the output.

Regards,

Subhash

[Former Member · Accepted solution]

Oh really, let see who is better and who is correct,you and me man to man what you say julius?

be a man accept it

[Former Member · Accepted solution]

Hi Prasant,

Shall we see who can hit the yellow "Report Abuse" button faster - you against all the people who have been complaining about your posts. This is the reason for many of your posts being rejected, which sends an automatic mail to you pointing out the forum rules and I have rejected some myself as well.

> you and me man to man what you say julius?

I am not interested in being better than anyone in any forum, only contributing usefull information which has not already been stated in the thread and moderating some of them to keep the quality of the contributions at an acceptable level.

This is the security forum, not the program memory management forum => Controlling a variant / parameter which should be set for 3 users via their PID's is not secure, because the user can generally change them and other's could also set them (via their own PIDs).

Perhaps a more usefull post would be to ask which selection field is to be controlled any why? Perhaps it is better to protect a few accounts (e.g. salary and wage information) beyond the selection screen using optional account groups. That is what F_BKPF_BES is designed for (at least according to it's documentation in SU21).

Please take a read through the rules if you have not yet, and continue to contribute - but do not repeat information which has already been posted or make speculative guesses.

Is that okay?

Cheers,

Julius

[former_member181995 · Accepted solution]

>

> be a man accept it

....And what about if the User or reader of this post is Woman ? ;-(

OK.

@OP: I'm not sure if [this|; link does help or not but you might have a look.

Cheers

[Former Member · Accepted solution]

Hello,

Thanks for reminding me,sorry for not giving time to looks at query and my ego was hurt by your comments ,

i really aplogize to everyone over here esspecially julius.

i will give more time to understand query and post the perfect answers

Tnx,

Prasant

[jurjen_heeck · Accepted solution]

> i really aplogize to everyone over here

That's nice.

> i will give more time to understand query and post the perfect answers

The first part is more important than the second.

Perfect answers are not the real goal here, helping each other understanding SAP security is (in my opinion).

Happy posting!

Jurjen

[Former Member · Accepted solution]

Lets wait for Subhash to clarify. Perhaps you win the first round, but in the wrong forum.

Which means that I need to take out my pea-shooter as weapon of preferred choice, because the guest-o-blaster only works on short range...

My apologies to you as well for being blunt.

Cheers,

Julius

[former_member185031 · Accepted solution]

First of all thanks to all for the reply, and it was my opinion as per my knowledge.

@Prashant

You was right till you have answered the question

please check with abaper to map with parameter and assign those parameter to user using Su01,and please check for notes that will help you more.

I believe that you have answered as per your knowledge and Julius just comments what is the problem if i set the parameter for transaction variants it will not be useful as in my company all the users have SU3 to maintain their own data, I am not Security Expert but i am little bit familiar with SU3 and Parameter setting. So as per my understanding there is not any reason to react on Julius

No body is perfect and we all have intension here to help each other as per our knowledge.

No back to my question, my problem has been solved by the help of Abaper and FI consultant, but right now i am not aware how this has been resolved, i will keep let you know once i got the feedback from them.

So thanks to all who spend some time on my query and given me their valuable resonse.

Regards,

Subhash

Edited by: Julius Bussche on Apr 16, 2009 11:24 AM

Code => Quote to fix formatting...

[former_member185031]

This message was moderated.

[former_member185031]

This message was moderated.

[former_member185031]

Problem has been resolved by creating a Z transaction and Abaper had done some hard code in program for a vairant. This is what i got information from them.

[Former Member]

I donu2019t think we can restrict Variants because variants are client specifics the entire user can access the variants if applicable ,Even though if we restrict particular variant user can crate new variant for the same, that we canu2019t restrict. Nothing arm in this to access others variant .They can access if the needs that variant or if itu2019s fulfill the user input.

FBL3n doesnu2019t have much inputs I think this is unnecessary work for consultant

Any way Others canu2019t access the variant who donu2019t have access for that T-Code

[former_member185031]

Hi Ravi,

But my requirement is something different. i would like to use the FBL1N in two way. one with variant which will be applicable for two uesrs and rest all the users can access FBL1N as it is, so i am looking some way to do it at my level, becuase i am not a security expert so i am looking for some help, but i have discussed the same with my consultant and i am exploring the possibility. I dont know my requirement is valid or not for security point of view but this is the requirement.

Regards,

Subhash

[Former Member]

>I donu2019t think we can restrict Variants

Yes, it can be. Please check SHD0 documentation.

>variants are client specifics the entire user can access the variants if applicable

No, It can be restricted to specific set of users

>Nothing arm in this to access others variant .They can access if the needs that variant or if itu2019s fulfill the user input.

These are business requirements. If the business wants it to be restricted we have to provide a solution.

>I think this is unnecessary work for consultant

Same as above.

Regards,

Subbu

[Former Member]

> If the business wants it to be restricted we have to provide a solution.

Lets us clarify what "restricted" means here? This might also be fueling some of Prasant's irritation (in addition to me...).

1) Should this achieve any security protection of using or changing the set selection and / or the data which they are accessing.

2) Or is this only a selection preference which should be set for the 3 users, who can however use FBL3N for other purposes if they wish as well?

Cheers,

Julius