Default Value for org field

[Former Member]

Hi Gurus,

There is a org level field GSBER (Object F_BKPF_GSB) whose value should be set to * by default everytime the t-codes, which contains this object, are added to any role in PFCG. I had read it somewhere thats its possible but i dont know how it can be done. Is it a good practice to manipulate the field values this way?

Please help!!!!

Currently the default value is set to $GSBER.

I thought we could change it in Su24 but it doesnt allow you to modify the org filed there. Only the activity defaults can be changed.

Thanks,

Vinaya

[Former Member]

Hi Gurus,

There is a org level field GSBER (Object F_BKPF_GSB) whose value should be set to * by default everytime the t-codes, which contains this object, are added to any role in PFCG. I had read it somewhere thats its possible but i dont know how it can be done. Is it a good practice to manipulate the field values this way?

Please help!!!!

Currently the default value is set to $GSBER.

I thought we could change it in Su24 but it doesnt allow you to modify the org filed there. Only the activity defaults can be changed.

Thanks,

Vinaya

[Former Member]

> I thought we could change it in Su24 but it doesnt allow you to modify the org filed there. Only the activity defaults can be changed.

It is either one or the other (or manually :-).

You could simply set the Org Level value in the roles to *. This should not be a problem, unless you have a crows nest of roles.

Another option would be to consider removing the "Proposal" indicators for the objects using this field in SU24 and adding a * once to a central role for all users.

But GSBER is optional if I remember correctly, so if the field does not have any values in the data or is not activated in customizing you can also simply ignore it completely.

Cheers,

Julius

[Former Member]

Hi Julius,

Actually we have some 250 roles in the system which contain this object and the business wants that we give * value in the GSBER field in all the roles with t-code FS10N. Also any role created in future with FS10N should have the * value in this field.

Therefore i was wondering if we can change the proposal value in Su24 for this field for t-code FS10N. Currently in Su24, there is no edit option for this field.

Also, if the above option does not exist, is there any other option to do this change other than manually going to each role?

Thanks for your help,

Vinaya

[Former Member]

> ... in all the roles with t-code FS10N.

That's different to what you have originally stated.

[jurjen_heeck]

>

> > ... in all the roles with t-code FS10N. 
> That's different to what you have originally stated.

And not only different, even if you would be able to edit a proposal value, for these roles you would have to go through them anyway. Changing proposals does not automatically change values in existing roles (luckily, in my opinion).

My advice is to focus on keyboard shortcuts and/or function keys in PFCG to speed up the role change process:

Enter rolename
F6
TAB
3 x RIGHT ARROW
ENTER
4 x TAB
ENTER
CTRL-F8
Change org values
ENTER
SHIFT-F5
2 x F3

This can speed you up to more than one role per minute which makes 250 roles a less than one day job, including sufficient coffee breaks

[Former Member]

Julius,

I mentioned the t-code here because for FS10N, the proposal indicator is set to yes in SU24 and the field values dont change.

And thanks for the short cuts....I should get going with the task now without looking for any more shortcuts !

But i still wonder if we can set default values for org fields for certain transactions.......so that we dont have to maintain them everytime the t-code is added in the role!!!!

Thankyou for your help...

Regards,

Vinaya

[Former Member]

> But i still wonder if we can set default values for org fields for certain transactions.

So now it is different again: Not all transactions, nor 1 single one, but rather a set of them on a list which you have...

Anyway, there is no such intended thing to my knowledge.

As a once-off dirty-trick it can be done using an (now) obsolete transaction to delete the org field, maintain SU24, do a merge and then create the org field again without adjusting the roles again. But this has nasty side-effects later on for others who might need to maintain this concept, so go for Jurjen's advise (and have a coffee at halftime :-).

Cheers,

Julius

[Former Member]

Hi Vinaya,

Can you please confirm that these 250 roles having only one Tcode FS10N or there are other Tcodes also ?

I would like to advise you one solution. Maintain a Master (Parent) role and assign the Org. Value as "*". After that derive/inherit the child role from master and later on you can remove the parent child relationship, this will make the child independent role.

Hope this will help.

Thanks

Lokendra